Accelerometer issue

[nacron]

Been having issues with my sensors locking up. I'm running stock rooted with a few xposed mods. I tried turning off all the mods and I still got it intermittently. Thought it was the gear manager for my Galaxy gear. Stopped having the issues after uninstalling the gear manager but it came back. When the auto rotation stops working I check the sensors with *#0*# and it shows the accelerometer is locked and occasionally other sensors fail like barometer and magnetic. A few searches find other phones with this issue sometimes gets fixed with a reflash. Anyone else have this issue?

Sent from my SM-N900P using Tapatalk

 

[micmars]

Been having issues with my sensors locking up. I'm running stock rooted with a few xposed mods. I tried turning off all the mods and I still got it intermittently. Thought it was the gear manager for my Galaxy gear. Stopped having the issues after uninstalling the gear manager but it came back. When the auto rotation stops working I check the sensors with *#0*# and it shows the accelerometer is locked and occasionally other sensors fail like barometer and magnetic. A few searches find other phones with this issue sometimes gets fixed with a reflash. Anyone else have this issue?

Sent from my SM-N900P using Tapatalk

I just did a Google search of the topic, and I'm finding a full wipe and reinstall appear to be the agreed upon solution for many. I hate those types of answers, since doing it is a lot of work, and if it doesn't solve your issue, you have just wasted a ton of time for little benefit.

Have you tried uninstalling the Xposed modules and framework completely, rebooting, and wiping cache and dalvik partitions? That's the only other thing I can think of that could fully test your theory of it being an Xposed issue.

Sent from my SM-N900P using Xparent BlueTapatalk 2

 

[nacron]

I just did a Google search of the topic, and I'm finding a full wipe and reinstall appear to be the agreed upon solution for many. I hate those types of answers, since doing it is a lot of work, and if it doesn't solve your issue, you have just wasted a ton of time for little benefit.

Have you tried uninstalling the Xposed modules and framework completely, rebooting, and wiping cache and dalvik partitions? That's the only other thing I can think of that could fully test your theory of it being an Xposed issue.

Sent from my SM-N900P using Xparent BlueTapatalk 2

Haven't tried removing xposed but I have done cache wipes and fix permissions with no result. Is there a file that's being corrupted somewhere? Had a similar issue on my Galaxy S (original) and wipe fixed that also but in that case it was directly after a game crashed in landscape

Sent from my SM-N900P using Tapatalk

 

[micmars]

Haven't tried removing xposed but I have done cache wipes and fix permissions with no result. Is there a file that's being corrupted somewhere? Had a similar issue on my Galaxy S (original) and wipe fixed that also but in that case it was directly after a game crashed in landscape

Sent from my SM-N900P using Tapatalk

I have no idea as to whether the file is corrupted, as I'm not experiencing your issue. None of the items I read mentioned corrupted files and accelerometers. They did mention running script commands (ie, pinging the sensor to awaken it, but that's above my knowledge base).

I would recommend deleting all Xposed modules and framework if you want to properly test your theory. You can backup the settings on those and just reinstall the apps if it fixes it, and you are going to be reinstalling them anyway if you wipe data. It's the only option of which I can think.

Hope this helps.

Sent from my SM-N900P using Xparent BlueTapatalk 2

 

[nacron]

I have no idea as to whether the file is corrupted, as I'm not experiencing your issue. None of the items I read mentioned corrupted files and accelerometers. They did mention running script commands (ie, pinging the sensor to awaken it, but that's above my knowledge base).

I would recommend deleting all Xposed modules and framework if you want to properly test your theory. You can backup the settings on those and just reinstall the apps if it fixes it, and you are going to be reinstalling them anyway if you wipe data. It's the only option of which I can think.

Hope this helps.

Sent from my SM-N900P using Xparent BlueTapatalk 2

Removed the framework and uninstalled exposed, still getting sensor lockups. If reflashing works after removing all these mods, there has to be a system file that's messing up right? I uninstalled lux also and disabled greenify. It was working fine up until a month ago.


Sent from my SM-N900P using Tapatalk

 

[micmars]

Removed the framework and uninstalled exposed, still getting sensor lockups. If reflashing works after removing all these mods, there has to be a system file that's messing up right? I uninstalled lux also and disabled greenify. It was working fine up until a month ago.


Sent from my SM-N900P using Tapatalk

Agreed, but I would speculate that the reason I found no answer beyond reflashing or pinging the sensors is that you could be searching for the proverbial needle in the haystack.

If wiping data and installing a new rom is the consensus solution, with no guarantee of success, then that is likely your only option.

It takes me hours to get a new rom up and running exactly the way I want, so I feel ya. At this point, I'm also out of answers.

If another can help, perhaps they can chime in.

Sent from my SM-N900P using Xparent BlueTapatalk 2

 

[nacron]

Uninstalled a bunch of stuff and now the sensors lock up within 10 min of boot. Barometer no longer registers any data. I'll thinking this GN3 has bad hardware

Sent from my SM-N900P using Tapatalk

 

[kingdazy]

Uninstalled a bunch of stuff and now the sensors lock up within 10 min of boot. Barometer no longer registers any data. I'll thinking this GN3 has bad hardware

Sent from my SM-N900P using Tapatalk

funny, after reading this thread, and seeing mic being stumped, i was wondering... do you have this issue on stock? old habit from my computer repair jobs which is rarely applicable to an android issue is "check HW first".

 

[nacron]

I'm running stock rooted, didn't flash any roms on this, believe me, I'm using all my troubleshooting resources. It's frustrating when a simple thing can mess up an entire device

Sent from my SM-N900P using Tapatalk

 

[micmars]

I'm running stock rooted, didn't flash any roms on this, believe me, I'm using all my troubleshooting resources. It's frustrating when a simple thing can mess up an entire device

Sent from my SM-N900P using Tapatalk

So do you have recovery or otherwise trip Knox? If no, reflash via Odin or Mobile Odin the full rom (see Skunk Ape1 thread), reinject root, then you'll know.

I'd go a step further and aver that, based on what you've written, one way or the other reflashing stock MJ4 is the direction this is headed.

Ya take the phone back, it's out-of-the-box clean, and you're likely going to want to do it anyway. Ya don't take the phone back in the hope you find a fix, you still might flash stock MJ4 to eliminate a potential fix. It doesn't work, your phone is that much closer to being brought back for a return.

Unless there is a more targeted solution, this is perhaps your best course of action.

Sent from my SM-N900P using Xparent BlueTapatalk 2

 

[nacron]

It seems more stable now. It's super weird, for almost all today the barometer read 0 and the other sensors world lock up about 10 min after boot. This was after removing all the mods and clearing cache and fixing permission. We'll see how stable it is tomorrow.

Sent from my SM-N900P using Tapatalk