Hi all. First I want to clarify that I am using a translator to write this, since I am Argentine and my English is half basic.
I have in my hands a Xiaomi m9t two months ago, which I bought again as an importer. After a few weeks I realized that I had a gyroscope fault in which the z axis was at a constant speed of 1 rad / s. I tried doing a wipe which had no solution. An important fact is that when I used image stabilization for video, it inclined it and with a few small strokes in the cameras sector, the z-axis speed was reduced ...
Then I tried reinstalling the firmware again and I was able to calibrate the gyroscope, however it has very little sensitivity with respect to the other x and y axes, it practically remains at 0 all the time. Anyone know any solution to this or rule out what is hardware? I saw that some modifying a persist file managed to solve.
AxelVonka said:
Hi all. First I want to clarify that I am using a translator to write this, since I am Argentine and my English is half basic.
I have in my hands a Xiaomi m9t two months ago, which I bought again as an importer. After a few weeks I realized that I had a gyroscope fault in which the z axis was at a constant speed of 1 rad / s. I tried doing a wipe which had no solution. An important fact is that when I used image stabilization for video, it inclined it and with a few small strokes in the cameras sector, the z-axis speed was reduced ...
Then I tried reinstalling the firmware again and I was able to calibrate the gyroscope, however it has very little sensitivity with respect to the other x and y axes, it practically remains at 0 all the time. Anyone know any solution to this or rule out what is hardware? I saw that some modifying a persist file managed to solve.
Click to expand...
Click to collapse
I had sensors problem (but wasn't so specific as yours, all sensors didn't work) and the only fix was flash a new persist partition.
BUT.. you will lose L1 DRM if you do so. so idk, if you can send it back it's better
Same problem here unfortunately ? did you manage to get it fixed somehow?
I have the same problem here. I tried flashing new persist.img but that didn't help.
I also modified calibration values in /persist/sensors/registry/registry/icm4x6xx_0_platform.gyro.fac_cal.bias but that didn't make any difference.
It's only the gyro z axis which is strange, the other axis works fine.
Did OP sort this out in the end?
cyferc said:
I have the same problem here. I tried flashing new persist.img but that didn't help.
I also modified calibration values in /persist/sensors/registry/registry/icm4x6xx_0_platform.gyro.fac_cal.bias but that didn't make any difference.
It's only the gyro z axis which is strange, the other axis works fine.
Did OP sort this out in the end?
Click to expand...
Click to collapse
have u managed to solve the problem?
elrolaso said:
have u managed to solve the problem?
Click to expand...
Click to collapse
Sorry for late reply, no I didn't solve it. Still looking for a way to fix this...
Related
I've just started with Android apps and having a tiny little device like this Flipout, the most obvious first app for me to try was a compass.
I tried several of the free ones, all of which worked fine on my Desire Z, but were 'screwy' at best on the Flipout.
Supposedly, the Flipout has Accelerometer, Altimeter, Digital Compass and GPS sensors, yet the compass apps not only are strangely oriented but plain don't work - They don't point North and even away from all possible interference sources just jump around.
Are Flipouts normally just screwy, or is there something I can do to fix this issue?
Thanks,
Dylan.
Also now finding the tilt mechanism is reversed, ie left & right functions only happen when I tilt the device forward and back.
Can anyone please help with this?
DylanKeyne said:
Also now finding the tilt mechanism is reversed, ie left & right functions only happen when I tilt the device forard and back.
Can anyone please help with this?
Click to expand...
Click to collapse
The sensors appear to be screwed up because the default orientation of the flipout/charm is landscape whereas most other phones have portrait mode as default orientation. Hence most applications are built for portrait orientations.
Hence there although the display might be shown in portrait mode, the sensor values are obtained from the landscape orientation.
Some application detect this issue and assign sensor values appropriately but that only a small minority.
I would suggest that you use a Display Orientation Changer available on Google Play and hence force the application to run in landscape mode.
Regards
HSR
My thanks to you HSR, but alas I have no luck so far.
Are there any particular orientators you'd recommend? I've tried four different orientator apps on all available settings. None have fixed the issue and one just outright crashes.
I'm using Smart Compass and Penguin Skiing as test apps, as I know they work perfectly and precisely on my Desire Z
Is this a hardware issue?
Using the orientators seemed to change not only the screen orientation, but the sensor's as well. In short, it turned everything 90º, rather than just the bits I needed.
DylanKeyne said:
My thanks to you HSR, but alas I have no luck so far.
Are there any particular orientators you'd recommend? I've tried four different orientator apps on all available settings. None have fixed the issue and one just outright crashes.
I'm using Smart Compass and Penguin Skiing as test apps, as I know they work perfectly and precisely on my Desire Z
Is this a hardware issue?
Using the orientators seemed to change not only the screen orientation, but the sensor's as well. In short, it turned everything 90º, rather than just the bits I needed.
Click to expand...
Click to collapse
Hey, try this. it seems to work for me.
http://forum.xda-developers.com/showthread.php?p=28022264&highlight=orient#post28022264
http://forum.xda-developers.com/showpost.php?p=24844428&postcount=953
Nope... :crying:
I've tried that one, both the version here and the one on Google Play.
Tried two more this evening as well. No luck.
Some of them do turn the display but the sensors alter with them, so whichever way the screen is, the compass moves North 90º from where it should be and the game controls are still twisted.
From the links I posted, try the one from the forum and force the display to landscape. Try the free version of doodle jump and check if it alters properly.
Doodle Jump - Este elemento no es compatible con tu dispositivo...
Is there another that is compatible?
Really starting to regret this Flipout - Tried 4 different unlocking shops in town today and none have been successful!
DylanKeyne said:
Doodle Jump - Este elemento no es compatible con tu dispositivo...
Is there another that is compatible?
Really starting to regret this Flipout - Tried 4 different unlocking shops in town today and none have been successful!
Click to expand...
Click to collapse
:s oh, try any motion sensor app which runs only in portrait mode, in forced landscape mode using the app in the 2nd link I posted.
By unlocking you mean carrier unlocking?
I tried several more with the forum orientator you linked to - Same result, I'm afraid.
The screen orients back and forth just fine, but when you change that, the tilt sensor maintains the same crossways alignment.
Sorry, yes I meant Carrier Unlock (Orange UK).
The first 3 shops came back with 8 digit codes of failure. The 4th one got a 16 digit code but it also failed to work. They're trying something else which will take 2-3 days, apparently...
DylanKeyne said:
I tried several more with the forum orientator you linked to - Same result, I'm afraid.
The screen orients back and forth just fine, but when you change that, the tilt sensor maintains the same crossways alignment.
Sorry, yes I meant Carrier Unlock (Orange UK).
The first 3 shops came back with 8 digit codes of failure. The 4th one got a 16 digit code but it also failed to work. They're trying something else which will take 2-3 days, apparently...
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1376037
This is for Charm but you could try this for sim unlock.
Regarding orientation issue, have your tried with the keyboard opened and with keyboard closed.
Any difference then?
Sorry that some things I told do not work, its probably because im a moto charm user and the keyboard swivel must be invoked in different ways.
No, no difference with the phone open or closed. Tried that each time I changed something else as well.
Will try that unlock when I get back home, though.
Update - Phone is SIM unlocked. The helpful shop texted through a code that they guaranteed would work, which it clearly did.
No closer to resolving the sensor orientation issue though.
Is it just me being stupid/missing something/having this problem on the Flipout, or does anyone else have it?
The compass does Not work correctly on 2 i9505 black...
Any people more?
Sorry for my bad english ...
oriolas said:
The compass does Not work correctly on 2 i9505 black...
Any people more?
Sorry for my bad english ...
Click to expand...
Click to collapse
test the sensor on *#0*#
I've solved it ... I have given two full turns to mobile and it seems that it is calibrated
Thankyou
oriolas said:
I've solved it ... I have given two full turns to mobile and it seems that it is calibrated
Thankyou
Click to expand...
Click to collapse
Hi
recently am facing issues with this s view.
I am not using a s view cover but still the phone shifts to s view suddenly. But only for a second or so and again comes back to normal.
this happens quite often for me when am just holding the phone. Or trying to make a call.this is annoying.
Is my s4 broke.. am worried.
please help me out to solve this
You have to move your phone in a figure 8 position in the air about three times to calibrate your compass for it to work properly.
The flip view cover contains a magnet which screws with the compass, rendering it useless. If you're using the cover remove it and see if it helps.
krico said:
You have to move your phone in a figure 8 position in the air about three times to calibrate your compass for it to work properly.
Click to expand...
Click to collapse
Was that answer for me.... please let me know... how to work this out and how does this work
No dude. It was for the person trying to calibrate their compass.
Calibrations doesn't help ...
I've got CM 5.1 + newest GAAPS and calibration of compass last only for few seconds-2/3 minutes tops and then it's gone and compass again showing wrong directions not even restarting Google Maps - (usually 180* degree opposite to the actual direction). Funny thing, when I downgraded to original Orange Kit Kat 4.4.2 compass worked precise so It assured me, that there is not problem with hardware only software. I cannot use: *#0*# because my I9505 says "Problem with the connection or wrong MMI code" (translating from polish).
All other things including GPS, accelerometer and other sensors works perfectly well.
Anybody know the solution?
Hi,
I flashed my i9505 with a 4.3 GPE ROM and have no issues, save one.
When using Photosphere in the Camera App I can't get a proper picture done because the "frame" (white rectangle) drifts slowly to the right.
Everything elese works, I have been unable to find any definite fault with the sensors (although it's hard to be sure...) and already sent my phone back for replacement once. the new one has the same issue, only it's drifting to the right instead of the left this time.
I really hope somebody here can help me fix this since I love the Photoshpere function (used it a lot on my Galaxy Nexus) and really don't want to send the second phone back and hope the third one is going to be OK...
CPU-Z gives me slightly strange values for linear acceleration and 4-Axis Accelerometer, but I had that on the first S4 as well, so not sure it's a phone issue.
My Linear Acceleration Sensor tends to show -0.9ms² when the phone is lying flat on the table, my first one showed a steady -0.6m/s² in the same situation. Not sure if this has anything at all to do with the problem though.
I'd be extremely grateful if somebody could help me out here!
Thanks.
EDIT: Just found this thread at rootzwiki http://rootzwiki.com/topic/36213-42-tips-on-photosphere/ where there is a video that describes the problem quite well.
Does nobody else have this issue?
Hi, I want to ask something. I have a problem with my accelerometer. So in the gpsstatus, it always shows g ~ 0.49 (https://www.dropbox.com/s/ylqclmxp71s1085/Screenshot_2014-08-25-23-49-06.png?dl=0)
I am not sure since when it happened. Then I download the system monitor, and only the Z accelerometer that gives wrong value (I guess it shouldbe close to 9.8??). Also from *#0*# looks like the Z value is wrong.
What is the number in your devices?
Is there anyway to reset/calibrate this number, specially without rooting?
Thanks!
motfis said:
Hi, I want to ask something. I have a problem with my accelerometer. So in the gpsstatus, it always shows g ~ 0.49 (https://www.dropbox.com/s/ylqclmxp71s1085/Screenshot_2014-08-25-23-49-06.png?dl=0)
I am not sure since when it happened. Then I download the system monitor, and only the Z accelerometer that gives wrong value (I guess it shouldbe close to 9.8??). Also from *#0*# looks like the Z value is wrong.
What is the number in your devices?
Is there anyway to reset/calibrate this number, specially without rooting?
Thanks!
Click to expand...
Click to collapse
Anyone here know how to fix this problem?
there could be only 2 possible causes for this: software or hardware.
For software issue you could reset the phone to factory or even wipe it clean and reload stock firmware to see if that helps.
If it's a hardware then the only thing I could think off is to make sure all the connectors are clean and make good contact, but I don't remember if sensors are on separate module like vibration or cam modules or are they build onto motherboard. If they are on separate board then check connectors and look for replacement, if they're on MB, then no connectors to worry, but fixing it gets more complex.
I can't remember ever seeing calibration for accelerometers, sorry.
What issues do you have, outside of showing wrong on gps status? Is it worth the trouble of fixing it? Samsung repair service is probably best bet, if that's an option.
ps
my gps status shows 0 unless moved, so there is something wonky there
Hello there to all.
I´m newly registered to the forum, although i´ve been using it to search, learn and use roms in my Samsung s3 for some time now.
I´ve bought recently a used S4 i9506. At the time i tested several key points of the device to check if it was all working, however (and don´t ask me why because i cant explain it), i completely forgot to test the cameras.
My problem is the following. Everytime i try to access the camera it says that camera failed or something like server connection failed. I´ve tried every single resolution i could find on the internet and so far all failed to solve it. The problem seems to be in both cameras, i think, because when i try the code *#0*# both Mega cam and front cam give error. Here´s what i tried so far:
- Soft Reset/Hard Reset/factory reset;
- Cleared cache both from boot and manually erasing cache from com.sec.android.gallery3d;
- Tried 3rd party camera apps from GooglePlay;
- Tried the RestartCamera.apk;
- Tried 3 different firmwares for i9506;
- Tried rooting it and then flashed several different roms;
- Switched the rear camera with a new i9506 rear camera module that i bought;
- I cant also test the cameras, because when i use the code *#34971539# they bring a menu on which i can´t use almost every option (see image);
http : / / rghost.net/6Zby4zXFD/image . png
Anyone have any other possible resolution?
I´m thinking on maybe buying a front camera module. Could that do the trick? Could the front facing camera not working properly make the rear camera fail as well?
Thank you for the attention to all who took the time to read.
So far 60 people read and nobody answered. ... is it because you don´t know what else i can do? I´ve been reading the problem may be from the motherboard. What can i do on the motherboard to make things right?
Thanks again
Be patient my friend someone will answer soon
Hi,
I've got the same problem with my s4mini. Both cameras aren't working and all the solutions you explained don't solve it.
I'm thinking about buying another S4mini with broken Display in order to change the motherboard. This might be the only possibility to solve this......
Greetings from Germany
DMmdW said:
Hi,
I've got the same problem with my s4mini. Both cameras aren't working and all the solutions you explained don't solve it.
I'm thinking about buying another S4mini with broken Display in order to change the motherboard. This might be the only possibility to solve this......
Greetings from Germany
Click to expand...
Click to collapse
Hey there m8.
I know the feeling, right?!
The thing is that for a faulty i9506 model i could almost buy myself another motherboard and mount it, but i was hoping to find some other solution, maybe even some electronics expert opinion on what i could do in the motherboard to make it work again. There are some videos on youtube that teaches how to change some components on the motherboard to solve problems like dead smartphone or constant auto reboots. Also, finding a faulty i9506 model isn´t as easy as finding a regular S4. :crying:
Thx for sharing the problem and for the opinions,
and greetings from Portugal
Today i've changed the mainboard aaaaaaand -> cameras still not working
So i started to change the front cramera and the ear-brightness-sensor from the old s4 mini with the broken screen into my working one. And now both cameras are working again!:good:
I think the cause is most likely the brightness sensor which is combined with the ear speaker. This could explain why both cameras are not working.
I'm not completely sure due to i changed the front camera also. However changing the main camera did not do anything as mentioned above.
Maybe i should mention: A few weeks ago i've changed the earspeaker-brightness-unit because the speaker wasn't working anymore. Right after this both cameras stopped working.
DMmdW said:
Today i've changed the mainboard aaaaaaand -> cameras still not working
So i started to change the front cramera and the ear-brightness-sensor from the old s4 mini with the broken screen into my working one. And now both cameras are working again!:good:
I think the cause is most likely the brightness sensor which is combined with the ear speaker. This could explain why both cameras are not working.
I'm not completely sure due to i changed the front camera also. However changing the main camera did not do anything as mentioned above.
Maybe i should mention: A few weeks ago i've changed the earspeaker-brightness-unit because the speaker wasn't working anymore. Right after this both cameras stopped working.
Click to expand...
Click to collapse
Thank you for the update on your situation m8. That could be some relevant information there. Can anyone confirm if the sensor is the same for all s4 models? If so i could find more easily one from another s4 model and try it, for the sake of desperation.
cheers