Database Users

Sensors and MCU not working

Hi guys,
New owner of a S4 (GT-I9505 international) here with a problem. 2 days ago I noticed the screen wasn't rotating anymore. I used to rotate it portrait/landscape in applications like Camera or Internet (browser). The moment when it started to bother me was when looking at pictures with the phone in portrait and the image was landscape. Trying to rotate the phone didn't help. It was frozen. I called a buddy of mine who has some experience with Samsung devices and told me to verify the "Auto-Rotation" settings. It was all OK and enabled. Then he suggested turning the phone off and pulling out the battery and SIM card for 5 minutes and putting it all back. This didn't help either. Finally we got to the point where he told me to enter *#0*# in the Phone dialing application. As you might already know, this code gives you access to the "testing" hidden utility. There I tested all the options available. Everything was fine except for the Sensors and SensorHub Selftest.
In the Sensors section, all the tests failed, starting with the Accelerometer and ending with the Temperature. I uploaded screenshots taken during the tests. Please remember this started 2 days ago. Before this it was working perfectly. I don't recall making and major changes like updating any OS components or installing/running stress utilities related to sensors or device behavior. After doing some research online and reading about other people's similar problems I got to the point where I started to suspect a problem with the MCU (Micro Controller Unit). This component, according to Samsung, controls all the sensors and reads raw data from them without accessing the AP (Application Processor) this way extending the battery life. I believe the problem is here because it seems odd that none of the sensors are working all of a sudden. Can this component put the sensors into a sleep state and shut them down completely? Might this be the case here?
Below are the solutions I tried in order to revive the MCU and finally the sensors. I was all without success:
1) Turned off the phone and pulled the battery and SIM out. Put the back in after about 5 minutes. Result: sensors not working.
2) Reset to factory-settings from the settings option while the phone was in the working state (turned on). Result: sensors not working.
3) Rooted the phone, installed Clockwork Recovery, made a full system and applications backup and then installed custom ROM (two actually: PACMan, Google Play Edition (4.3)). I did this in order to exclude a problem related to drivers in the stock Samsung ROM, even if it was logical that Samsung being the owner and manufacturer of the device might have the "best" drivers and applications for inquiring the device components/sensors. I am aware this ended the warranty for me, but can I know it can easily be undone. Result: sensors not working.
4) Restored the original stock Samsung ROM. Result: sensors not working.
The utilities used for sensor testing were: Sensor Kinetics and Sensor Tester. Both can be found in the Play Store. On my wives phone, which is an old HTC Desire, both utilities picked up the available sensors and created graphs with the results. On my S4, I only got blank charts/graphics/results. In Sensor Kinetics for the Gyro for example, the message was "Waiting for the Gyroscope sensor...", just that, stuck.
If there are any other guys (or ladies!) out there who encountered this awful experience, please reach out and tell me if you found any practical solution, any other then just taking the device back to warranty. I'm open to any suggestions.
Best regards,
Andrei

Most likely a defective device ... can't you claim warranty and sent it back?

Sounds like hardware failure. This would be an issue for Samsung to solve.
Sent from my GT-I9505

AvelonTs said:
Most likely a defective device ... can't you claim warranty and sent it back?
Click to expand...
Click to collapse
Unfortunately I bought it second-hand and it does not have any warranty. I guess it's one of those moments I wish I had patience and gathered more cash to buy a new one from the store. Anyway, it's my bad luck. I had it working perfectly for weeks after buying it. I will use it like this for the time being..

i´ve got the exact same problem since yesterday...
i think i´ll take it to the shop for warranty

I've got the exact same issue. All sensors are having the same issue. None are working,
I found out because my camera app was not switching between landscape and portait any more. All pictures are saved as landscape...
Called Samsung Netherlands and they told me to wipe my phone (still latest original stock ROM) and try again.
Making a backup now using Kies... and will hard reset it afterward and check the sensors.again.
Probably not going to work... So I have to send it in...

darklord said:
I've got the exact same issue. All sensors are having the same issue. None are working,
I found out because my camera app was not switching between landscape and portait any more. All pictures are saved as landscape...
Called Samsung Netherlands and they told me to wipe my phone (still latest original stock ROM) and try again.
Making a backup now using Kies... and will hard reset it afterward and check the sensors.again.
Probably not going to work... So I have to send it in...
Click to expand...
Click to collapse
Hi there. I had same problem with sensors and MCU test failed, so i took phone to service. They said its hardware failure and replaced main board. Im picking phone tommorow and we will see...

Hi guys,
I took mine to a local phone service, not the official one, but they are an affiliate. They could not figure out exactly what the problem was so they replaced the logic/main board just for testing. It was all working fine. They called and informed me of the findings. Given the fact I don't have warranty for it, they suggested to send it to our main service in Bucharest where they have a more sophisticated testing equipment. It is possible to get a more precise answer regarding the defective component and maybe a less pricey solution to the problem. At this time, the only viable option is to get a new logic board in place, which is about to set me back 250 USD. I will get an answer from Samsung in Bucharest by tomorrow or the day after tomorrow.
I will get back to you with my final solution... hopefully something not so expensive
@darklord, @eweu: please post back you findings. Maybe in the future when some other unfortunate owner finds his way in here, will have a better understanding of whats on the plate for him.
Thanks,

Hard reset did not work as expected. Going to drop it off at a local official repair center....

S4 Sensors failing
I have the same problem with my S4 GT-I9505 device not auto-rotate, air gestures with gyroscope and accelerometer tests failing. S4 been back for 3 weeks to Samsung for repair came back and failed again after 1 week

KSal7506 said:
I have the same problem with my S4 GT-I9505 device not auto-rotate, air gestures with gyroscope and accelerometer tests failing. S4 been back for 3 weeks to Samsung for repair came back and failed again after 1 week
Click to expand...
Click to collapse
After installing some other ROM's and playing with different CSC's I have no sound and even no wireless and only Edge speeds on some ROM's. Restoring from backups, wireless came back and HSDPA+ also, but no luck with sound what so ever. Now, I have a tablet more or less. Thanks Samsung, this is great!

canaris1780 said:
After installing some other ROM's and playing with different CSC's I have no sound and even no wireless and only Edge speeds on some ROM's. Restoring from backups, wireless came back and HSDPA+ also, but no luck with sound what so ever. Now, I have a tablet more or less. Thanks Samsung, this is great!
Click to expand...
Click to collapse
Flashed I9505XXUDMH8_I9505OXXDMHA_BTU, sound and wlan working again. Previous problem with MCU/sensors still there.

i'm tired
canaris1780 said:
Flashed I9505XXUDMH8_I9505OXXDMHA_BTU, sound and wlan working again. Previous problem with MCU/sensors still there.
Click to expand...
Click to collapse
really i'm tired to solve this issue.
when i install new stock software the sensors work fine just a few minutes only yhen return to fail again.
i think its software issue and i'll solve it :good::good::good:

Sensors work again
:laugh: :victory:
Its work right now by itself
:crying:
after uploading the pictures its fail again

abdali_m2 said:
:laugh: :victory:
Its work right now by itself
:crying:
after uploading the pictures its fail again
Click to expand...
Click to collapse
I have the same thing here
all sensors are broken because of SensorHub BIN FW Version: AT0199999
then i try to update firmware with *#2663# it failed.

I have the same problem with my S4 GT-I9505.
Suddenly the device do not auto-rotate, and no air gestures with gyroscope and accelerometer are working.
The SensorHubTest end with FAIL.
Mid december I got one OTA firmware update and I didn't notice any problems first.
A few days after newyear I notice that my auto-brightness adjustment did not work properly.
Can't remember if auto-rotate didn't work when I notice the auto-brightness problem.
But finally I am here because I searched for sensors problems.
I did the SensorsHub Test with *#0*# and it ends with FAIL.
It seems that there is a problem with the 4.3x firmware.
With 4.2x all was fine.
Can anybody confirm my thoughts - that the firmware is broken and not the MCU itself?
What can we try? Downgrade? I read that one was lucky with "factory reset" but it didn't helped to revive the MCU of my device.
Thanks for reading
and answering
___
DK

Hi, i am a owner of a sch-i545 phone, and i have the same problem with the phone: no response of any sensor and a fail on test (or upgrade firmware) of the sensorhub.
At this time i was tried a lot of solutions: i was flashed stock firmware, custom firmware, and of course a factory reset (by the way, the first time with this problem was when i did it a single factory reset), its still broken the communication with the sensors.
I get back to life the phone when i upgrade the phone from 4.2 to 4.3 (sadly) and get lost when i update the binaries in super su (previously rooted with vroot).
Yesterday i give the phone to a technician (a close friend of another best friend), he will test the phone on this weekend to determine what is the problem to try to fix it.
When He fix this phone, i will post any news!
Regards.

remy1004 said:
At this time i was tried a lot of solutions: i was flashed stock firmware, custom firmware, and of course a factory reset (by the way, the first time with this problem was when i did it a single factory reset), its still broken the communication with the sensors.
I get back to life the phone when i upgrade the phone from 4.2 to 4.3 (sadly) and get lost when i update the binaries in super su (previously rooted with vroot).
Regards.
Click to expand...
Click to collapse
Thanks for your answer. I have hope that the next firmware will fix it.
What is strange that none of any reseller/privers know this problem. It seems that also Samsung has no knowledge about this special error.
Well if the next firmware didn't fix the problem, I can replace my model with a working one, that is what the guy at the phone shop offers to me.
___
DK

Same Problem Here
Hi guys, I'm new to this forum so be nice :angel:
I am having the same problem in that none of the sensors are working which indicates that it is a connection issue or the actual hub not working or the firmware and not the individual sensors themselves. I have thought about this and looked around and to me it seems like there are only 3 possibilities for the problem:
1) The SensorHub BIN FW Version is out of date and needs to be updated manually (not through *#2663 as it doesn't work)
2) There is a connection issue e.g. the cable from the sensorhub to the motherboard is loose or broken
3) The sensorhub is broken (not the sensors)
I will try to find the firmware files and see if I can do a manual update. If that fails I will open up the phone and see if the cable is connected/broken. If I still cannot solve the issue, I will have to take it to the shop and hope I can fix it off warranty (I bought it second hand)
Dan

shadowsoulxp said:
Hi guys, I'm new to this forum so be nice :angel:
I am having the same problem in that none of the sensors are working which indicates that it is a connection issue or the actual hub not working or the firmware and not the individual sensors themselves.
[...]
I will try to find the firmware files and see if I can do a manual update. If that fails I will open up the phone and see if the cable is connected/broken. If I still cannot solve the issue, I will have to take it to the shop and hope I can fix it off warranty (I bought it second hand)
Dan
Click to expand...
Click to collapse
Thanks Dan for your reply.
I assume that your S4 shows the same behaviour as my one and the phone is still working fine.
The sensorhubtest failed and your light sensor for automatic adjusting and the sensor for turning the display are not working.
What is really strange that I went to a vodafone shop in Hamburg and ask them if there is any other one having problems with the S4.
You know the answer? They where wondering and telling me that this is wierd and they heard the first time of such an issue from me.
I showed them the device and showed them how I test the sensors. *#0*# funny they didn't know this combo
I hope that you succeed and share your knowledge,
with best regards.
___
DK

Fingerprint reader stopped working and screenlock later

Hi,
my fingerprint reader stopped working (not recognizing finger) so i had to use pattern. A day later the security setup changed - even though the fingerpring & pattern was required, any button normaly turns on screen and vibrates as if I touched the reader. Fingerprint patterns are still present but I cannot add any as the reader doesn't recognize the finger.
I didn't do any system updates or changes. Running version 12.1-YOG4PAS3OH
Anybody with this issue?

iamx82517 said:
Anybody with this issue?
Click to expand...
Click to collapse
The device forum is full with threads and posts about the fingerprint issue. Please have a look. Therefore you'll find lots of tips that maybe help you out.

iamx82517 said:
Hi,
my fingerprint reader stopped working (not recognizing finger) so i had to use pattern. A day later the security setup changed - even though the fingerpring & pattern was required, any button normaly turns on screen and vibrates as if I touched the reader. Fingerprint patterns are still present but I cannot add any as the reader doesn't recognize the finger.
I didn't do any system updates or changes. Running version 12.1-YOG4PAS3OH
Anybody with this issue?
Click to expand...
Click to collapse
1st Don't Panic.
Try other ROMs or from recovery mode do a factory reset (Only if you cannot find any solutions..

AndroidGod1987 said:
(Only if you cannot find any solutions..
Click to expand...
Click to collapse
There are multiple solutions in zuk forum which sometimes work(delete database, delete credentials) or not and then it's a hardware failure. It's all documented and can be easily find with Google or forum search.

strongst said:
There are multiple solutions in zuk forum which sometimes work(delete database, delete credentials) or not and then it's a hardware failure. It's all documented and can be easily find with Google or forum search.
Click to expand...
Click to collapse
Thanks, I tried those of course before creating this thread. the difference is I din't change/update the system nor did any other change, removed the smart lock settings etc. I am afraid only thing to try is the factory reset.

iamx82517 said:
Thanks, I tried those of course before creating this thread. the difference is I din't change/update the system nor did any other change, removed the smart lock settings etc. I am afraid only thing to try is the factory reset.
Click to expand...
Click to collapse
It's essential to tell what you've done before requesting for help, otherwise you see replies like that
Hardware issue with fp reader is very common. A friend of mine has also dead fp reader. My zuk has defective digitizer. As good as the hardware looks on paper, the quality is very bad compared to the device's sold.

same here it's a hw problem, i was on cos like you and after i went to cm13 (so much better btw) but still doesn't work. i'm waiting for the fingerprint replacement I ordered.

Nexus 6P angler-userdebug 8.1.0 question

hello, my first post, I bought a Nexus 6P from ebay. It has an unlocked bootloader (I get the warning when I turn it on) and the os build number is "angler-userdebug 8.1.0 OPM3.171019.01445.3998 dev-keys". there are applications that are not uninstallable: Better Bug, Nexus Logger, Traceur, and Volta. My question is, is this device suitable for personal use the way it is? any other information and/or suggestions are appreciated.

sarmid said:
hello, my first post, I bought a Nexus 6P from ebay. It has an unlocked bootloader (I get the warning when I turn it on) and the os build number is "angler-userdebug 8.1.0 OPM3.171019.01445.3998 dev-keys". there are applications that are not uninstallable: Better Bug, Nexus Logger, Traceur, and Volta. My question is, is this device suitable for personal use the way it is? any other information and/or suggestions are appreciated.
Click to expand...
Click to collapse
I am not sure about the rom version.
https://developers.google.com/android/images#angler
It sounds like somebody sold you a former test model from Huawei.
I can obly assume, that they sold remaining units, but after I searched a bit about those applications I can, like I said, only give you a vague assumption.
The important questions are -
Is the phone functional?Meaning: bootloop, sudden reboots, battery problems?
Are you able to use adb/fastboot? - > Is your phone being recognized by the command 'fastboot devices'?
Did you get a notification that is your system can be updated?
The unlocking of a bootloader isn't a reason to be distinctively suspicious?
But, if you are not satisfied with the phone in whatever way, you can demand to be refunded in regard of the unlocked bootloader with the argument, that the seller has tampered with it and should wrote it in the description.
I bought a phone a while ago and were unsatisfied with it, so I argued with the above mentioned and got my money back.
This was even from somebody private and there are no refund policies, besides the buyer protection.
If you have not passed thr chance and don't want to have a phone, which somebody has used most likely to flash a custom rom or recovery to root same phone, then go for it.
It is not a 100% bulletproof argument, but ebay excepted it, at leat in my case.
If you are okay with the device and adb/fastboot are working, in a way that you for example can test some commands, whicj you have to look up, but __don't flash anything__ as long as you are unsure of the condition.
If you want to remove these apps, you have to look them up, which is expandable and which isn't, before removing them.
And lastly - if you want to remove them, you have to root your phone (tutorials find you here en mass, the same goes for adb/fastboot usage).
But the same goes here for testing a ADB and fastboot usability, please.
If you decide to keep it, then you can remove system apps (>before a search if you phone goes boom..), aith this app for example
https://www.apkmirror.com/apk/jumobile/system-app-remover-root/system-app-remover-root-7-1-release/
With this, you are able to backup the apps if you want to remove them.
Some apps, especially the so-called 'bloatware' is from now on then, quite resistant.Just empty the trash, which you find in the app's menu.
Titanium Backup, a very, very versatile application, is fir example capable of backing up your entire apps including data, but I think, you have "some" pointers now and can give it (with carefulness) your own try.
Have fun & good luck

Please HELP get Redmagic 5G NFC GPay fix: Takes 10m of time!

Guys - the easiest way to get development started on a new device is to NOTIFY the device manufacturer that there is a NEED for the company to fix issues. The first issue is THE BOOTLOADER UNLOCK METHOD BREAKS THE FINGERPRINT SENSOR. This is obviously highly undesirable for anyone who wants ROOT. *** NOTE THIS CAN BE AVOIDED ENTIRELY THROUGH THE ROOT BYPASS METHOD (FP STILL WORKS), AND A USER HAS FOUND HOW TO RECALIBRATE THE FP SENSOR AFTER A BL UNLOCK, XDA POS: https://forum.xda-developers.com/nu.../guide-calibration-finger-print-loss-t4132961
The main issue is Google Pay does NOT WORK with NA and Global ROMs. It reports 2 cards instead of 1 card when you go to a terminal, so you can NEVER make a payment!!!
So how can we fix this issue? COMPLAIN!!! We got source this way already (THANK YOU FOR YOUR HELP GUYS WE DID IT!)
METHOD #1
EMAIL Nubia customer support (probably our best path) at [email protected]
You can simply report the issue similar to this message in your email:
Google Pay does not work with NFC which your Global and North American ROM claim to support. It reports 2 cards at the terminal instead of 1 card so payment fails EVERY time. This is an issue across the world for everyone with Google Pay. WE NEED THIS FIXED AS IT IS A LISTED FEATURE OF THE PHONE THAT DOES NOT WORK.
Please fix as soon as possible.
Signed,
[YOUR NAME / Country / Phone Model]
METHOD #2:
https://github.com/ztemt/NX659J_Q_kernel/issues/2
Post something like I did here - GOOGLE PAY DOES NOT WORK. FIX NFC ON GLOBAL AND NA VARIANT ROMS ASAP.
Please start posting comments here to release the source code so we can begin custom kernel and ROM development as soon as possible! Thank you everyone who contacted [email protected] or posted to the original GitHub issue, now we just need them to follow through!!! WE HAVE STRENGTH IN NUMBERS.

I have done as advised let's hope they fix this
Sent from my GM1913 using Tapatalk

I just did it too(both ways), but I don't know how much they care about the emails, I sent 3 before, for other things, without any reply

How much pay?

Guys! They do care about the device! I've emailed them three times, and I've got replies everytime!

ZTE released the source code for the Red Magic 5G... hopefully this will kick start development for this phone because it has so much potential.

nexuses said:
Guys! They do care about the device! I've emailed them three times, and I've got replies everytime!
Click to expand...
Click to collapse
Try asking about an older device that they dont produce/sell anymore. If they eager to answer they might care about devices that are older than 1 or 2 months

xabierd said:
Try asking about an older device that they dont produce/sell anymore. If they eager to answer they might care about devices that are older than 1 or 2 months
Click to expand...
Click to collapse
Well, the future updates are the only reason that hold me back from buying this phone! So I'll give it sometime to see what happens.. We will see..

Keep contacting guys..
Nevermind you closed the one with the new title ... Keeps this alive. Thanks Admins.... I don't see why closing this and opening another that resolves remaining ones is a problem. When I link it elsewhere it still looks like the original issue where we fixed or worked around 2 of them and now the last to address is GPay.

mslezak said:
Guys - the easiest way to get development started on a new device is to NOTIFY the device manufacturer that there is a NEED for the company to fix issues. The first issue is THE BOOTLOADER UNLOCK METHOD BREAKS THE FINGERPRINT SENSOR. This is obviously highly undesirable for anyone who wants ROOT. The second issue is Google Pay does NOT WORK with NA and Global ROMs. It reports 2 cards instead of 1 card when you go to a terminal, so you can NEVER make a payment!!!
So how can we fix this issue? COMPLAIN!!! We got source this way already (THANK YOU FOR YOUR HELP GUYS WE DID IT!)
METHOD #1
EMAIL Nubia customer support (probably our best path) at [email protected]
You can simply report the issue similar to this message in your email:
Google Pay does not work with NFC which your Global and North American ROM claim to support. It reports 2 cards at the terminal instead of 1 card so payment fails EVERY time. This is an issue across the world for everyone with Google Pay. WE NEED THIS FIXED AS IT IS A LISTED FEATURE OF THE PHONE THAT DOES NOT WORK.
Also, the bootloader unlock on the Redmagic 5G disables the fingerprint sensor completely - the error message says to contact Nubia support. The device will not even allow a fingerprint to be added. The Android installation detects the sensor on the "back of the phone" i.e. missing the Goodix in-screen fingerprint location, so it can not be added. Later trying to add an FP results in an error:
Loss of fingerprint calibration data
Loss of fingerprint calibration data was detected.
Currently unable to complete fingerprint entry,
please contact Nubia after-sales support via
4007006600
Please fix as soon as possible.
Signed,
[YOUR NAME / Country / Phone Model]
METHOD #2:
https://github.com/ztemt/NX659J_Q_kernel/issues/2
Post something like I did here - GOOGLE PAY DOES NOT WORK. FIX NFC ON GLOBAL AND NA VARIANT ROMS ASAP.
Please start posting comments here to release the source code so we can begin custom kernel and ROM development as soon as possible! Thank you everyone who contacted [email protected] or posted to the original GitHub issue, now we just need them to follow through!!! WE HAVE STRENGTH IN NUMBERS.
Click to expand...
Click to collapse
You can enter *#*#9959#*#* on the dial pad to enter fingerprint calibration mode, and then calibrate the fingerprint, it will return to normal

johnny886 said:
You can enter *#*#9959#*#* on the dial pad to enter fingerprint calibration mode, and then calibrate the fingerprint, it will return to normal
Click to expand...
Click to collapse
Sorry, it does not work here. I dialed the code but It doesn't do anything.

johnny886 said:
You can enter *#*#9959#*#* on the dial pad to enter fingerprint calibration mode, and then calibrate the fingerprint, it will return to normal
Click to expand...
Click to collapse
Johnny can you explain the calibration steps for everyone with this issue? We've seen the factory calibration device that no one can find for sale anywhere. But some have managed with using their finger, a piece of dark paper, and the back of a fingernail. But that doesn't seem to work for all.

mslezak said:
Johnny can you explain the calibration steps for everyone with this issue? We've seen the factory calibration device that no one can find for sale anywhere. But some have managed with using their finger, a piece of dark paper, and the back of a fingernail. But that doesn't seem to work for all.
Click to expand...
Click to collapse
You can use special fingerprint calibration weights to calibrate fingerprints. You can use weights to calibrate at some professional repair points.

johnny886 said:
You can use special fingerprint calibration weights to calibrate fingerprints. You can use weights to calibrate at some professional repair points.
Click to expand...
Click to collapse
That dial code doesn't work for some reason.

Anyways the code is *#9959# to start calibration off the TG group it works. Although what to do after launching it I have no idea.

I keep getting hung up here

viper98 said:
I keep getting hung up here
Click to expand...
Click to collapse
Same here...

My NFC Works now with Google pay only 1 out of 100 times ? it shows the message: present only one card at the terminal.

What to do with new 7t pro?

Just got this, and it upgraded me to oos 11. Fingerprint doesn't work well, though I have a screen protector. Seemed to work ok before the upgrade. Trying to figure out what to do. Of course, I don't know which info here is up to date. Normally I'll ditch the stock os, but oos is actually pretty good and customizable enough. I'd still like root, and would like the option to try out a ROM and go back to stock if needed. I'm sim unlocked currently, not sure if the bootloader is unlocked (though I assume not since I got an otan upgrade). What's the best course of action. Bonus points if I can do a reasonable backup without root (or root and then backup)

Did you try simply deleting your fingerprint(s) and re-creating them? Also, try it without the screen protector, especially if it's not the original screen protector from the manufacturer (when programming new fingerprints and when using FP)
You don't have any issues with persist.img (or anything else) or the FP sensor wouldn't work at all (you'd receive an error saying FP hardware not found or something extremely similar)
Edit: Please,please, please make a backup of your persist.img before it eventually gets corrupted and with no backup you could wind up with a paperweight that even loses its IMEI.