sensors not working (was Moto Display not working) - X Style (Pure) Q&A, Help & Troubleshooting

I've rooted my moto x style 5.1 and installed xposed and gravitybox and moto display was working fine, but after a reboot it stopped working so I tried to uninstall xposed and it started working again but sometimes it stopped working again after a reboot
I've tried to install trupurexmm and again same problem, sometimes it worked and sometimes it didn't but I can't pinpoint the cause, I've also tried to go back to 5.1 and upgrade to stock 6.0 but it's still not working
I don't think it's a hardware issue because when I wave my hand in front of the phone I get this error in logcat
Code:
IRSensorHub: Exception talking to sensorhub, request: 2: com.motorola.actions
IRSensorHub: java.io.IOException: Bad address: com.motorola.actions
IRSensorHub: at com.motorola.actions.ir.SensorHub.nativeSetIRDisabled(Native Method):
IRSensorHub: at com.motorola.actions.ir.SensorHub.-wrap3(SensorHub.java): com.motorola.actions
IRSensorHub: at com.motorola.actions.ir.SensorHub$1.handleMessage(SensorHub.java:223): com.motorola.actions
IRSensorHub: at android.os.Handler.dispatchMessage(Handler.java:102): com.motorola.actions
IRSensorHub: at android.os.Looper.loop(Looper.java:148): com.motorola.actions
IRSensorHub: at android.os.HandlerThread.run(HandlerThread.java:61): com.motorola.actions
also after downgrade to 5.1 I'm getting baseband: (not found) in fastboot

Did you do a clean wipe before the ROM install? I had trouble with my WiFi doing a dirty flash from LP. I'd recommend a wipe before an install. Even reverting back from MM to LP, my problems still persisted. Only fix was a clean wipe/install.
Edit: I'm now running MM TruPureX without issue.

bw03 said:
Did you do a clean wipe before the ROM install? I had trouble with my WiFi doing a dirty flash from LP. I'd recommend a wipe before an install.
Click to expand...
Click to collapse
yeah I did multiple times

another thing I've noticed in logcat
Code:
MOTOSH : Failed to switch STM to bootloader mode
MOTOSH : : I/O error
SensorhubService: JNI Error: MOTOSH_IOCTL_GET_VERSION_STR returned -1: com.motorola.slpc
SensorhubService: JNI write err: -14: com.motorola.slpc
SensorhubService: updateSensorhubListeners_Locked err writing sensorhub: com.motorola.slpc

I've found out that it's not just the ir sensors, the compass, accelerometer, gyro etc.. dont' work either
is there a firmware like the modem one but for the sensors that I can try to flash?

Solution
verunks said:
I've found out that it's not just the ir sensors, the compass, accelerometer, gyro etc.. dont' work either
is there a firmware like the modem one but for the sensors that I can try to flash?
Click to expand...
Click to collapse
Hey did you find a solution to this problem I am having the same problem

aakashverma0007 said:
Hey did you find a solution to this problem I am having the same problem
Click to expand...
Click to collapse
no, I got it replaced by amazon

Any solution?

Related

[Q] Auto-rotate not working

Hi, hoping someone can offer some advice/help here. First, my setup:
A500 with the v7 Bootloader, Thor's R169 Rom, Recovery 1.7.3 all of which are working just fine.
The problem I have, is the auto-rotate function does not work. I have tried all the suggested fixes I can find on both here and the Tegra Owners forums (and indeed every other link I can find through Google) and none of them work. I have also checked that the hardware switch is OK and it is functioning as it should. This problem has only appeared since installing ICS and applies to any Rom I try, with the auto-rotate not working in any Rom, or with any bootloader.
I have, of course, tried different bootloaders, different roms, full wipes, full formats of all partitions, factory resets, the pinhole reset and a number of different auto-rotate applications from the market. None of them make the slightest bit of difference and auto-rotate continues to be non-functional. Logcat shows continual "MLUpdateData error (code26)" errors with the hardware switch in the on position, and when I then switch it to the off position, shows "Error: illegal state transition from ML_STAT_SERIAL_CLOSED to ML_STATE_DMP_OPENED", followed by "vendor/3rdparty/Invensense/libservers/mlsdk/mllite/mldmp.c|MLDmpStop|161 returning 25
I am satisified from using a program called AdvancedTools from the market, that the sensors are functioning and responding to restart requests, although restarting the sensors using this app still makes no difference. Auto-rotate remains non-functional and nothing I have tried seems to change that.
To a layman like me, it seems like it may be a driver issue or perhaps a kernel issue. Anyone here able to help at all please ?
Hmmm....
60+ views and not a single response. Is it fair to assume that nobody has any idea what is causing this ? Am I the only person seeing this issue ?
phlashbios said:
60+ views and not a single response. Is it fair to assume that nobody has any idea what is causing this ? Am I the only person seeing this issue ?
Click to expand...
Click to collapse
I have the same issue, I do not know what to
Same issues here...
Take a look here:
http://forum.xda-developers.com/showthread.php?t=1690905
The only way that worked for me so far is:
Turn the auto rotation switch off
Power off
Power on
Put the auto rotation switch on
If I turn off the tablet with the switch ON none of the sensors works and you'll have to try a lot of times to make it work again..
Other users solved the problem:
- installing a HC bootloader
- Installing ICS V4 bootloader
- Performing real format before flashing the rom
Let me know what you've tried, we must find a solution!!!
OK, here's the current situation. I installed a stock HC ROM (Acer_A500_4.010.38_COM_GEN1) but left the v7 Bootloader still in place. ROM booted fine and works, but still no sensors working.
I then reflashed the Bootloader with a stock HC Bootloader and all the sensors work again.
This is clearly a Bootloader issue by the looks of it.
I am currently upgrading the Honeycomb 3.1 ROM as an OTA to 3.2.1 and will then update all apps, check all is working again and if so, install the Acer Update Updater and then do the OTA upgrade to ICS and check if all working again on stock ICS. Will report back later as to how things go.
OK, latest update following on from above.
Installed the Acer Update utility from the Marketplace
Updated OTA to stock 3.2. No issues, all working including sensors.
Updated OTA to stock 3.2.1. No issues, all working including sensors.
Updated existing systems Apps to current versions. No issues, all working including sensors
Updated OTA to stock ICS. Tablet boots, all OK and working, including sensors.
Reboot tablet, get a brief message that says Bootloader updating and then it boots into ICS. Sensors now stop working and no amount of fiddling with the rotation lock or factory resets or pinhole resets will make the sensors work again.
This to me is clearly an ICS Bootloader issue ? Anyone disagree ?
How on earth do I/we get this fixed ?
Well, after many hours of messing about, I have managed to get Thor's R169 ROM working and with the sensors working too. It has however required the use of the HC 3.01 Bootloader to have the sensors still working.
For the benefit of others who are facing similar difficulties, can I suggest the following course of action:
Install the APX drivers if you haven't already got them on your PC.
1. Put Thors ROM and Gapps on your SD card or on the Tab's own internal storage
2. Downgrade your existing setup to the unstable 3.01 Honeycomb
3. Use the AfterOTA v1.7 tool to install CWM on the old Honeycomb setup.
4. Boot into CWM Recovery and do the usual Factory Reset and wipe everything you can, including the Flexrom, Dalvik etc.
5. Install Thors ROM from your SD card/storage
6. Install Gapps from your SD card/storage
7. Reboot the tab into normal mode
Voila ! A working Thor ROM with working sensors.
What all my efforts tell me is that there is an issue with the ICS Bootloader and some tablets. Whether it is causing a race condition and not giving drivers time to start up, I am not sure, but restarting the drivers for the sensors makes no difference once the ICS Bootloader is installed. Any ICS Bootloader, including the stock one and all of Skrilax's from versions 3 through to 8, all result in no sensors working for me. This is clearly nothing to do with Skrilax, it is something inherent in the behaviour of the ICS Bootloaders.
For people using ICS ROM's other than Thor's, you will need to check whether they will behave with a HC Bootloader before installing them.
I can only pray that Thor and others continue to release ICS ROM's that are compatible with HC Bootloaders while someone, hopefully is able to figure out what is causing the ICS Bootloader issue.
Thanks all for those that offered advice and guidance. Your help is and will continue to be appreciated.
I am aware that references to Thor are not welcome in these forums. As I have not provided any links, or posted any attachments, I am hopeful that the mods here will see that I am trying to both seek help and indeed offer help to others rather than cause any issues. It could be any ROM this applies to, it just happens to be Thor's I am using.
use same rom thor169 bootloader v3 never botherd to upgrade to 4-5-6or 7
on mine rotation works with a ics v3 bootloader
Hmmm... that's very interesting, because mine definitely does not. My sensors do not work with the stock ICS Bootloader, or any of Skrillax's from v3 --> v8
I have also recently had some problems in this area. Started out as auto-rotate sticking whenever using an app that forced portrait. Then this morning went to flash v170 after being on flex rf1 v3 and auto-rotate quit completely. Tried twice with no luck. Over the past couple of days I have done multiple complete wipes and data formats. Did this again and did not work. So I restored a v169 backup and everything fine again. Flashed v170 and it's working fine. Possibly restoring to an older backup that worked (even if it was honeycomb) might help you. Oh yah, I was on bootloader v6 through all of this.
Hi all,
i has the same problem, sometimes works and sometimes not. now i have the v8 Bootloader, Recovery 1.7.3 and Tegraowners ICS ROM v170.
any ideas?
If you install a HC 3.01 Bootloader, I am pretty confident that will fix it, however, that's not really the answer to the problem, it's just a workaround. So far, nobody with the necessary skills seems to be interested in sorting out what's causing the problem when using the ICS Bootloader.
phlashbios said:
If you install a HC 3.01 Bootloader, I am pretty confident that will fix it, however, that's not really the answer to the problem, it's just a workaround. So far, nobody with the necessary skills seems to be interested in sorting out what's causing the problem when using the ICS Bootloader.
Click to expand...
Click to collapse
No one with the skills has the problem.. no one with the problem is providing real debugging information. (a logcat + dmesg just after boot might give a hint)
Many experience installing an ICS rom with the unlocked bootloader, and having the rotate fail on the first boot; however ensuring rotate is not locked and rebooting solved it for most users (and it never shows again).. If after this reboot its still failing you need to provide the logs above if you want a dev to have any chance.. and provide info that we are sure you have done this reboot. (and not just blindly downgraded to HC or another rom)
Also it helps to be sure what rom is being run..
ezterry said:
No one with the skills has the problem.. no one with the problem is providing real debugging information. (a logcat + dmesg just after boot might give a hint)
Many experience installing an ICS rom with the unlocked bootloader, and having the rotate fail on the first boot; however ensuring rotate is not locked and rebooting solved it for most users (and it never shows again).. If after this reboot its still failing you need to provide the logs above if you want a dev to have any chance.. and provide info that we are sure you have done this reboot. (and not just blindly downgraded to HC or another rom)
Also it helps to be sure what rom is being run..
Click to expand...
Click to collapse
Reset doesn´t help.
E/Sensors ( 144): MLUpdateData error (code 26)
I/ActivityManager( 144): START {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10000000 pkg=org.jtb.alogcat cmp=org.jtb.alogcat/.LogActivity bnds=[784,52][880,148]} from pid 366
I/dalvikvm( 1348): Turning on JNI app bug workarounds for target SDK version 11...
E/Sensors ( 144): MLUpdateData error (code 26)
I/ActivityManager( 144): Start proc org.jtb.alogcat for activity org.jtb.alogcat/.LogActivity: pid=1348 uid=10108 gids={1007, 1015}
D/OpenGLRenderer( 366): Flushing caches (mode 1)
E/Sensors ( 144): MLUpdateData error (code 26)
D/OpenGLRenderer( 366): Flushing caches (mode 0)
E/Sensors ( 144): MLUpdateData error (code 26)
E/Sensors ( 144): MLUpdateData error (code 26)
E/Sensors ( 144): MLUpdateData error (code 26)
E/Sensors ( 144): MLUpdateData error (code 26)

Rotation not working....

SOLVED....Reflashied BOOTLOADER...
hassam_tariq2003 said:
SOLVED....Reflashied BOOTLOADER...
Click to expand...
Click to collapse
Could you please elaborate on the original problem and provide us with the version of the bootloader you flashed?
I'm asking because rotation stopped working on my N7 after the 4.3 upgrade (I installed it OTA) so I tired going back to 4.2 installing the bootloader that comes with the 4.2 official firmware and rotation is still does not work. Next thing I tried was to do a full wipe on everything and install 4.3 from scratch and my N7 still won't rotate.
I also noticed that is not only the gyroscope sensor but also the magnetic field sensor has stopped working.
TIA
bbaaxx said:
Could you please elaborate on the original problem and provide us with the version of the bootloader you flashed?
I'm asking because rotation stopped working on my N7 after the 4.3 upgrade (I installed it OTA) so I tired going back to 4.2 installing the bootloader that comes with the 4.2 official firmware and rotation is still does not work. Next thing I tried was to do a full wipe on everything and install 4.3 from scratch and my N7 still won't rotate.
I also noticed that is not only the gyroscope sensor but also the magnetic field sensor has stopped working.
TIA
Click to expand...
Click to collapse
I was running Vanir rom android 4.2.2 bootloader 4.18 when i had this problem.....I then made a backup Of my in recovery and formatted everything (System, Data, Cache, Dalvik-Cache)...then i download the bootloader4.18.img file and flashed it in fastboot mode.....went into recovery and wiped eveything again...After that i restored my data and BAM....Everything was fine.....

No sensors on g4 plus

DELETED-- If you face the same problem (No sensors working), flash the following file through TWRP. It is attached to the end of the post.
https://forum.xda-developers.com/showpost.php?p=71360979&postcount=2717
Are you on a custom ROM and have flashed a different kernel?
Please provide more details.
--DELETED--
PATAboy said:
Hello everyone, my sensors have been failing since last saturday.
---Info: ---
*Phone: G4 Plus - xt1641 - 32GB Dual Sim
*OS: Lineage OS 14.1 1st May Nightly Update
*Kernel: (I think it was installed when sensors started failling) ElementalX Kernel 1.05 for Lineage OS
(As of now,12 of may, 8 Hours and a half after this was posted) V. 1.06 for Lineage is installed. Still not working
Never had a problem with any of them
***Problem: Sensors not working (Accelerometer , Gyroscope, Light and Proximity Sensors, Headphones Detection)
Cant get readings from Sensor Data Apps
Cause: Theres no apparent cause. Phone never fell to floor nor nothing like that. It happened after playing a game. No overheating while playing.
**Actions taken:
-Re-Flashed Lineage OS many times, with no succes (Wiped everything but sdcard and usb otg)(With and without ElemntalX)
NO SUCCES
-Flashed Stock Rom, with sensors working momentarily. They worked for 30 secs after one day of the Stock Rom install. Didnt work after that. Reflashed Stock, didnt work. (I believe that ElementalX was installed, version 1.04 for Stock Rom)
MOMENTARY SUCCES
-Flashed Lineage,
NO SUCCES
-Tried using ADB to execute:
*Sensor.qcom
* and sensorsevice
From /system/bin/
NO SUCCES
-Erased hmac.key (the only file) from /data/system/sensor_service
NO SUCCES
I grabbed a logcat, but I'll grab one from boot, so Im not uploading this one.
Click to expand...
Click to collapse
Look for SensorHub-N.zip and flash it in TWRP. This should be flashed after flashing ElementalX Kernel.
--DELETED--
--DELETED--
PATAboy said:
Do you know where to get it? I dont seem to find anything
Click to expand...
Click to collapse
You'll find a TWRP flashable sensorhub firmware zip file here: https://forum.xda-developers.com/showpost.php?p=71360979&postcount=2717
By the way, with flashing the stock ROM, have you flashed/updated your device to Nougat at any point, before flashing Lineage OS?
--DELETED--
PATAboy said:
Yes, when I updated from MM to Nougat, i Flashed Nougat stock rom with fastboot to update it. The I used it for a while, till I found Resurrection Remix. No problems. But I wanted to try CyanogenMod. I ended knowing that Lineage was kinda the new Cyanogen, so I installed it. No problems for about a month and a half.
Also, do i need to reflash lineage and the kernel with it, or just reflash kernel and then sensorhub-n.zip??
Click to expand...
Click to collapse
Hmm, then that's odd sensors have failed when you've been running with no issue.
Don't think you have to reflash L-OS or the kernel, flash the sensorhub in TWRP (you may wish to wipe cache/Dalvik) and reboot - the sensorhub firmware should flash into /etc/firmware. You could re-flash the kernel if you wanted to.
--DELETED--
PATAboy said:
Hello everyone, my sensors have been failing since last saturday.
---Info: ---
*Phone: G4 Plus - xt1641 - 32GB Dual Sim
*OS: Lineage OS 14.1 1st May Nightly Update
*Kernel: (I think it was installed when sensors started failling) ElementalX Kernel 1.05 for Lineage OS
(As of now,12 of may, 8 Hours and a half after this was posted) V. 1.06 for Lineage is installed. Still not working
Never had a problem with any of them
***Problem: Sensors not working (Accelerometer , Gyroscope, Light and Proximity Sensors, Headphones Detection)
Cant get readings from Sensor Data Apps
Cause: Theres no apparent cause. Phone never fell to floor nor nothing like that. It happened after playing a game. No overheating while playing.
**Actions taken:
-Re-Flashed Lineage OS many times, with no succes (Wiped everything but sdcard and usb otg)(With and without ElemntalX)
NO SUCCES
-Flashed Stock Rom, with sensors working momentarily. They worked for 30 secs after one day of the Stock Rom install. Didnt work after that. Reflashed Stock, didnt work. (I believe that ElementalX was installed, version 1.04 for Stock Rom)
MOMENTARY SUCCES
-Flashed Lineage,
NO SUCCES
-Tried using ADB to execute:
*Sensor.qcom
* and sensorsevice
From /system/bin/
NO SUCCES
-Erased hmac.key (the only file) from /data/system/sensor_service
NO SUCCES
I grabbed a logcat, but I'll grab one from boot, so Im not uploading this one.
Click to expand...
Click to collapse
Well it is for xt1643 but should work for u too. See the instructions n u will have a customer service rom flash at ur home. It should definitely solve ur problem
---------- Post added at 09:58 AM ---------- Previous post was at 09:57 AM ----------
DgnrtnX said:
Well it is for xt1643 but should work for u too. See the instructions n u will have a customer service rom flash at ur home. It should definitely solve ur problem
Click to expand...
Click to collapse
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1643-updated-signed-t3460695

[Request] Persist.img for ZC551KL

Hello,
I've been without sensors nor camera for a while now (almost a year), got broken because an OTA update. Tried downgrading, didn't work.
Yesterday I managed to root and install TWRP, did some research and heard about ''persist'' partition. I've been searching for similar cases but no luck. Also tried deleting sns.reg
Can someone provide me the persist.img stock file? So I can finally fix my sensors.
Broken sensors:
Gyroscope
Ambient light
Accelerometer
Proximity
Fingerprint
Camera Flash isn't working either.
Foxxo990 said:
Hello,
I've been without sensors nor camera for a while now (almost a year), got broken because an OTA update. Tried downgrading, didn't work.
Yesterday I managed to root and install TWRP, did some research and heard about ''persist'' partition. I've been searching for similar cases but no luck. Also tried deleting sns.reg
Can someone provide me the persist.img stock file? So I can finally fix my sensors.
Broken sensors:
Gyroscope
Ambient light
Accelerometer
Proximity
Fingerprint
Camera Flash isn't working either.
Click to expand...
Click to collapse
Solved, download the firmware version you have here and look for persist.img. The firmware comes with it but the install script doesn't use it. Just flash it:
Code:
fastboot devices
fastboot erase persist
fastboot flash persist persist.img
fastboot reboot
Hello friend,i have similar problems,apart from fingerprint sensor,all my sensors and cameras,camera light are not working,will i loose imei numbers if i flash the persist img ? i dont know how to flash persist img,can you help me please?
Edit: hi i actually fixed my problem by flashing persist.img, all sensors and cameras are working now
Thank you so much
I would like to thank you for this solution, finally, after 2 days trying I have my ZS570KL alive and working faster, I had to try rooting, then it was bricked for some hours, finally I got it rooted, but after deleting that persist/sensors/and.reg it was the same... until i found this thread, everything works good!!! thank you very much
3sgebeams said:
I would like to thank you for this solution, finally, after 2 days trying I have my ZS570KL alive and working faster, I had to try rooting, then it was bricked for some hours, finally I got it rooted, but after deleting that persist/sensors/and.reg it was the same... until i found this thread, everything works good!!! thank you very much
Click to expand...
Click to collapse
Did you also have broken sensors issue and it is fixed now? I want to try it on my ZS570KL too, but is there a persist.img for this phone?
DIXES said:
Did you also have broken sensors issue and it is fixed now? I want to try it on my ZS570KL too, but is there a persist.img for this phone?
Click to expand...
Click to collapse
Depending on your OS version yes, contact me on Telegram @GuerrillaRadi0 (the last character is zero) maybe I can help you, after I fixed the problem I configured fingerprint security and the problem came back, so I tried to flash persist.img again and it didn't work, so I got the raw rom of the Oreo version I have; WW-15.0210.1810.73, which comes with its own ADB, and flashed from there, the same raw rom has the persist.img. After that all sensors worked again, so I configured fingerprint security again just to be sure, and again I lost all the sensors, but after deactivate fingerprint again everything worked fine, I guess I have some hardware issue related to fingerprint sensor, I guess it was because a technician opened the phone to replace screen and battery 2 months ago. I always used fingerprint so I need to go back to pattern.
Good luck
After some days without any issue the problem came back, I flashed persist.img twice and it worked, but about 3 days ago I can't solve this flashing persist.img, I tried wiping everything, downgrading to Nougat, then flashing Oreo, with TWRP and via flashtool, no solution, any other idea?? all sensors are not working.
Thanks in advance

Redmi Error with TWRP (A rare one )

Hi everybody,
As i installed TWRP through the fastboot mode and tried to remove the Data/Delvik Cache, The error said
Error Opening : /data/data/com.instagram.android/cache/images/13118ca1.clean (I/O error)
I have tried deleting through the file manager but it still gives the same error, I cant flash a new rom as well as my Original stock rom is already screwed. Anybody has Idea regarding that ?
Try different version of TWRP
anyway I'm using latest one and it works calmly without any issue
HashanR said:
Try different version of TWRP
anyway I'm using latest one and it works calmly without any issue
Click to expand...
Click to collapse
I have tried TWRP every version and the error still remains the same. Its something related to the I/O of the phone, Which i couldnt figure out.

Categories

Resources