Last days I started to setup my new Nvidia Shield K1. I like to use tis for flying a DJI Mavic Pro and rely on functioning sensors. I also have installed AndroSensor and GPS Status. If I start one of this Apps the ACC sensor is working for a seconds and then the signals are completely freezing. After this I only get it back to work after and complete reboot of the Tablet. Also the Gyro and the Mag sensor does not look to be working at all. I have never seen any data on this. AndroSensor is waiting for an event for this two sensors and GPS Status shows some initial movement on the level sensor but never any reaction on the compass. Sometimes I even seen the orientation is not working anymore and the screen will not adjust anymore. In most of the cases the orientation is still working even with the frozen sensor output in the two Apps. Im using this two apps with a few of my other Android devices without having issues. My actual version is Android 6.0.1 with Shield software 1.5(24.3.70.8). I already have done a complete factory reset but after this the problem is the same. Any feedback is appreciated. I may need to RMA the device.
I got an replacement K1 yesterday and set it up again. With stock Android version all sensors are working fine for a day. Than i made the OTA update to latest (same as above). Now ACC and Gyro is still working but not the MAG. The problem looks to be at least partial related to the firmware. Mag sensor problems are reported also in the past for the K1 already. Also MAG calibration will not make any change. Androsensor is reporting "waiting for event" and GPS Status shows and wrong compass direction (was fine with the initial firmware before OTA). Not sure what can be done here. I was expecting when i invest in an tablet of an reputable vendor (which is also not very cheap) i get something working well. Now i either have a second bad tablet or there is still something wrong with the firmware. It would be good if someone with the latest OTA update can confirm this behavior or can confirm that everything is working as expected. Many thanks.
Here is some more information for the case: _https://forums.geforce.com/default/topic/986542/shield-tablet/sensors-gyro-acc-mag-work-in-an-erratic-way-on-my-new-k1-shield/?offset=7
As the title says, face recognition doesn't work (model SM-A750FN) after updating to Android Q. Front camera works fine, but when you are on the lock screen or trying to register your face again it asks for a reboot, which does not fix this issue.
Probably a factory reset would make it work again, but I don't want to try it — because of laziness. Or maybe a new update would fix it. I am wondering if I am the only one experiencing this issue.
My firmware belongs to the Spain (PHE) provider.
Not recommended to upgrade from 9 to 10 because 10 is buggy.
I had the same problem but i solve it by factory reseting a7 2018 and face recognition work great after reseting it.
Xperia XZ3 (H9493) - 52.1.A.0.672 - RU version
Notification seek bar bug - STILL!!! – If I’m playing media through chrome, soundcloud or another app, the notification seek bar does not work in most situations. This has been a bug since the initial Android 10 roll out and I’m still shocked that we’re still going through this.
Swipe up from the lock screen – I’ve noticed this since the update from Android 9 to 10. It used to be a quick flick of the thumb where I could go from the notifications on the lock screen to the security pattern. Now since the A10 update, I can’t do that anymore. It is a longer swipe, more exaggerated swipe to get to the security options. It was easier with 1 hand before and it needs to go back to whatever it was in Android 9
Camera – Still gives error unknown error. It’s MUCH EASIER to fix than the first and second android 10 releases but it still shouldn’t be like this. It’s at the point where I don’t know if it’s an actual software or hardware problem. And with everything that’s going on, I probably won’t be able to confirm for the next 6 months. I'll probably end up wasting$200 fixing the hardware, that was really a software issue all along.
Fingerprint – Good, I believe either at or close to Android 9 speed
Battery – Good
Networking issues – I believe better than the last update. It seems good so far so
No idea why the software version has to be in the notification quick settings. That doesn’t need to be there. It’s out of place/doesn't add value by being there
I am so frustrated by Sony. They’re taking steps to fix this but damn you should have been on the ball. I do a clean install each update because I don't trust Sony to do this correctly.
This phone is like the Renault Formula 1 team. It's a great product and each update is a step further but holy **** you all should have been a lot farther along by now. Now Mclaren (One Plus) is starting to pass you.
Edit: I forgot to add this earlier. I found a bug by random. In dark mode, About phone -> Emergency Information, the notification bar text is black. So you've got a dark screen with black text.
I still have not received an air update on my H9493. my software version is still 532.
Wa1ker_ru said:
I still have not received an air update on my H9493. my software version is still 532.
Click to expand...
Click to collapse
I too haven't received an update since December on my xz3 h9493 my version is 532
kaderzaim said:
I too haven't received an update since December on my xz3 h9493 my version is 532
Click to expand...
Click to collapse
In the morning I received an update with the numbers 618
Wa1ker_ru said:
In the morning I received an update with the numbers 618
Click to expand...
Click to collapse
I too received it this morning and I'm still waiting for the 672
supervf1s said:
Xperia XZ3 (H9493) - 52.1.A.0.672 - RU version
Notification seek bar bug - STILL!!! – If I’m playing media through chrome, soundcloud or another app, the notification seek bar does not work in most situations. This has been a bug since the initial Android 10 roll out and I’m still shocked that we’re still going through this.
Swipe up from the lock screen – I’ve noticed this since the update from Android 9 to 10. It used to be a quick flick of the thumb where I could go from the notifications on the lock screen to the security pattern. Now since the A10 update, I can’t do that anymore. It is a longer swipe, more exaggerated swipe to get to the security options. It was easier with 1 hand before and it needs to go back to whatever it was in Android 9
Camera – Still gives error unknown error. It’s MUCH EASIER to fix than the first and second android 10 releases but it still shouldn’t be like this. It’s at the point where I don’t know if it’s an actual software or hardware problem. And with everything that’s going on, I probably won’t be able to confirm for the next 6 months. I'll probably end up wasting$200 fixing the hardware, that was really a software issue all along.
Fingerprint – Good, I believe either at or close to Android 9 speed
Battery – Good
Networking issues – I believe better than the last update. It seems good so far so
No idea why the software version has to be in the notification quick settings. That doesn’t need to be there. It’s out of place/doesn't add value by being there
I am so frustrated by Sony. They’re taking steps to fix this but damn you should have been on the ball. I do a clean install each update because I don't trust Sony to do this correctly.
This phone is like the Renault Formula 1 team. It's a great product and each update is a step further but holy **** you all should have been a lot farther along by now. Now Mclaren (One Plus) is starting to pass you.
Edit: I forgot to add this earlier. I found a bug by random. In dark mode, About phone -> Emergency Information, the notification bar text is black. So you've got a dark screen with black text.
Click to expand...
Click to collapse
Same here like a attached photo
Camera unknown error most of the time
Very sometime good again .but I can't
find anyway to slove that problem.I tried to clear cached clear data forced stop disabled
and restart still have that unknown error
After that I flashed stock ftf 10.0
again with full wiped and then repair software with PC suited also wasting time
Please give me any ideas guys thz
PS Xz3 H9493 .618
kokokmt said:
Same here like a attached photo
Camera unknown error most of the time
Very sometime good again .but I can't
find anyway to slove that problem.I tried to clear cached clear data forced stop disabled
and restart still have that unknown error
After that I flashed stock ftf 10.0
again with full wiped and then repair software with PC suited also wasting time
Please give me any ideas guys thz
PS Xz3 H9493 .618
Click to expand...
Click to collapse
It's possible it's a hardware problem. It happens to me too but it was worse with the initial A10 update. My understanding is if you squeeze beside the camera when turning the phone, it can solve the issue. This is because it's a possible loose ribbon.
The initial A10 release was terrible so flash up to .672 and it may fix the problem (if it's a software issue)
supervf1s said:
It's possible it's a hardware problem. It happens to me too but it was worse with the initial A10 update. My understanding is if you squeeze beside the camera when turning the phone, it can solve the issue. This is because it's a possible loose ribbon.
The initial A10 release was terrible so flash up to .672 and it may fix the problem (if it's a software issue)
Click to expand...
Click to collapse
I really appreciated your reply I'm so confused that problem is hardware or not.Coz I got back my camera very sometime but after few days
It happened again ??? and also I found
another user reported that bugs at Sony'
Discussion and any other places when they upgraded to A10.Another problem is
My device is H9394 Dual So latest ver
Of A10 is .618 . Ver 672 is not yet for my
Region thz
PS Now I tried to downgraded android 9
If Downgrade is fix this problem I will
let you know
kokokmt said:
I really appreciated your reply I'm so confused that problem is hardware or not.Coz I got back my camera very sometime but after few days
It happened again and also I found
another user reported that bugs at Sony'
Discussion and any other places when they upgraded to A10.Another problem is
My device is H9394 Dual So latest ver
Of A10 is .618 . Ver 672 is not yet for my
Region thz
PS Now I tried to downgraded android 9
If Downgrade is fix this problem I will
let you know
Click to expand...
Click to collapse
Hey I am also facing this problem on my xz3 dual. Failed to restart the camera is consistently occuring in the past few weeks but restarting the phone worked then. But now its been almost 2 days, camera app says unknown error, I tried everything mentioned above but still unable to resolve the issue. Kindly let me know if downgrading the firmware resolves the issue.
Thank you
Camera unknown error issue
Splinter07 said:
Hey I am also facing this problem on my xz3 dual. Failed to restart the camera is consistently occuring in the past few weeks but restarting the phone worked then. But now its been almost 2 days, camera app says unknown error, I tried everything mentioned above but still unable to resolve the issue. Kindly let me know if downgrading the firmware resolves the issue.
Thank you
Click to expand...
Click to collapse
Of course
I am waiting to downgrade 9
But it was delay coz of covid 19
I can not go to any service center.
Because I can't downgrade it myself .
I hope that problem is software issue .
After downgrade to android 9
That problem can fix or not I will
let you know
Thank you
It is not a software problem for my device
Splinter07 said:
Hey I am also facing this problem on my xz3 dual. Failed to restart the camera is consistently occuring in the past few weeks but restarting the phone worked then. But now its been almost 2 days, camera app says unknown error, I tried everything mentioned above but still unable to resolve the issue. Kindly let me know if downgrading the firmware resolves the issue.
Thank you
Click to expand...
Click to collapse
Today I downgrade my Xz3 H9493 to android
9 but my camera didn't get back.So I decided
to check hardware.that is really sad.
Coz I have to take out all water proof
Seal from my back cover .After that I found
my Camera connector is loose.That's why
occurring unknowm error and after
2 or 3 days is good again.At last that is
not a software error at all.
I got error while enabling tethering
Anyone else?
I'm having signal issues. Dropping connection all the time. Latest firmware hurt this badly.
Same SIM on a Samsung A30S on android 9 works fine.
Hello guys. I need your help finding 52.1.A.0.618 for H9436
I cant get NFC to work properly. My phone is able to read cards and tags in NFC mode but it doesnt emit anything. E.g. google pay is not working.
I have ArrowOS 11 with latest MIUI firmware.
I tried with my wifes NFC phone and my Poco can register signal from her phone but not the other way around.
Im thinking firmware issues or something with ArrowOS?
Any ideas?
I've got a similar issue, I can't get NFC payments to work. Also using Arrow OS 11 (latest release) with the newest miui firmware. Tried to root my phone with Magisk 24 to see if this works but until now without any success. Any help would be great.
I was able to get mine to work yesterday using an apple 12 as reciever.
The signal is insanely weak, i literally had to use a precise angle at a certain spot on the iphone to get a registration.
There is no way to get a card terminal to register anything this NFC emits. Seems it has to be closer than a few millimeters apart to get any registration.
Which is strange because i can scan tags/cards that are a few cm away without issue..
Im thinking this is a hardware issue
ndb055 said:
I've got a similar issue, I can't get NFC payments to work. Also using Arrow OS 11 (latest release) with the newest miui firmware. Tried to root my phone with Magisk 24 to see if this works but until now without any success. Any help would be great.
Click to expand...
Click to collapse
Install Magisk 23, hide the Magisk app (it will get a different icon and a different package name), hide Magisk from Google Play, Google Pay and your banking apps, install GPay SQLite Fix v2.6 from here:
Releases · stylemessiah/GPay-SQLite-Fix
A magisk module that ONCE allowed Google Pay to work on rooted phones - stylemessiah/GPay-SQLite-Fix
github.com
Ever since my wife and I updated our Pixel 3a phones to Android 12, we've experienced random hard-locks that require holding the Power and Volume Down buttons at the same time for 30 seconds to force restart our phones. Occasionally, a second force restart is necessary because the phone locks up again almost immediately after restart. Our phones worked great on Android 11 and there's no discernible pattern to the lockups.
I recently switched from stock Android to LineageOS 19, but the random lockups persist.
My phone is rooted with Magisk installed, so I may have access to additional testing and troubleshooting methods (such as log capture, maybe?) that my wife's Pixel 3a running stock Android 12 doesn't.
Since a full wipe and reload didn't resolve the issue, what troubleshooting methods are left to identify the root cause of these issues?
I doubt it's a hardware issue because my wife and I both started experiencing the issues around the same time.
It is a F2FS driver bug that Google refuses to fix. You need to use a custom kernel such as MVK.
Systemless hosts may result in system freezes (F2FS driver bug) · Issue #3171 · topjohnwu/Magisk
yujincheng08 EDIT: This should have been fixed by #6805 topjohnwu EDIT: This is caused by an F2FS driver issue that unfortunately Magisk is unable to fix. The only way around it is to use a custom ...
github.com
mulperi said:
It is a F2FS driver bug that Google refuses to fix. You need to use a custom kernel such as MVK.
Systemless hosts may result in system freezes (F2FS driver bug) · Issue #3171 · topjohnwu/Magisk
yujincheng08 EDIT: This should have been fixed by #6805 topjohnwu EDIT: This is caused by an F2FS driver issue that unfortunately Magisk is unable to fix. The only way around it is to use a custom ...
github.com
Click to expand...
Click to collapse
I had rooted my phone, but my wife's phone was 100% stock and up to date. Could the F2FS driver bug affect her phone as well?
On a related note, I discovered that when the phone appears to hard-lock, it hasn't completely locked--but the user interface has. I only made this discovery after running adb commands to read logcat while the phone was locked up. Unfortunately, I still wasn't able to identify a root cause.
But in the end, it may all prove irrelevant (to me, at least) as my wife and I opted to trade in our Pixel 3a phones for $300 each and pick up Pixel 6a phones instead. Now you might see my name pop up in threads about issues with the 6a's fingerprint reader. :/
Tek70x7 said:
trade in our Pixel 3a phones for $300 each
Click to expand...
Click to collapse
Good deal.
That's more than I bought mine used 2 years ago.