Glad to be back to XDA after all this years. I just want to put this thread because of the difficulties I have with my Mi 11 Ultra (China Rom) and what I've surpassed and not. I'm loving this phone and I have almost everything working or with some workarounds and now that I have everything installled and functional don't want to reeinstall everything.
This is the problems I current have:
WearOS - bought a new GW5 LTE had a hole afternoon to setup the watch and pair but now it's working. The problem is I can't add a card to google wallet on wearOS. I press the + sign and show the loading circle and comes back to add a card. Simply won't communicate with the phone to insert the cvv. I tried with my old Mi 9 and paired flawless. I have all google services but seems something missing to wake up the watch app to validate de CVV.
This is my major problem right now.
I've surpassed:
- Add google pay to the phone and is working
- Pairing GW5 and having ECG and BP
I still have two more anoying problems:
- Screen cast simply isn't working and I think is because rear screen
- Nova launcher after restarts don't come app with last open apps WORKAROUND: is to turn on and off rear screen pass to default launcher and the returning default to Nova, works untill you restart again.
- the behaviour is strange because when it happens rear screen turns on and shouws recent apps even if you had it deactivateded.
If you have any problem that I can help that I passed I will be glad to help and if anyone can help me trying something to add a card to Gpay please help because I dind't want to Install and configure everything again and have manual updates.
Related
I have a moto x pure connected with chevy volt using android auto. It used to work perfect with the stock rom.
Recently I have installed the orionos custom rom, and the screen resolution in the car is totally wrong. I can only see the very top left portion of the screen, I think it is a screen resolution issue, but do not know how to solve it.
Any help is appreciated.
same issue
I have a brand new Skoda connected to an LG Optimus G updated to Android 6.0.1 and exactly the same issue. The screen is completeley screwed up and showing only the top left quarter of the screen way too large (huge fonts, etc.) Is there a way to fix this? Would even be good to know if this is a bug in the phone, in the car system or in the Android Auto app.
Anyone else facing this?
Is it possible you may have downloaded a 1024x600 rom instead of a 800x480?
I have a HTC 10, completely stock rom and a Pioneer head unit. Maps always worked perfectly in over a year with this phone and previous phone.
About a week ago I started to have this same issue. Maps is totally useless since.
I will try and get a photo tomorrow and reply again with it.
Just to let you know not only one.
I could fix my display issue by upgrading my phone to an Android 7 custom ROM.
duflez said:
I have a HTC 10, completely stock rom and a Pioneer head unit. Maps always worked perfectly in over a year with this phone and previous phone.
About a week ago I started to have this same issue. Maps is totally useless since.
I will try and get a photo tomorrow and reply again with it.
Just to let you know not only one.
Click to expand...
Click to collapse
Same thing here, HTC10, but with stock+magisk/xposed, same issue in Maps - until I saw this I thought that is because of one of xposed module. I cleanup the storage data several times, reinstalled aa also, disabled magisk/xposed, played with app settings xposed module in order to try to change the screen dp. Could not find the issue.
Interesting part is that on the same car but with different phone (moto x 2nd, xposed, same aa version, same google maps version) the Maps is displayed properly.
I have the same problem after updating my rom to a 1024x600. My unit was 800x480 and thats why the screen is cut off. What can i do?
In my case issue was related to Boost+ app "optimization", see this post https://forum.xda-developers.com/htc-10/help/android-auto-google-maps-issue-t3533388
So this randomly started happening the other day, whenever I try and open my camera through any method, double tap power, use the app, from the lockscreen etc... it loads than says "Warning: Camera Failed" and there' an OK button that exit's the app. I've tried everything I've found online, factory reset twice, wiped cache partition, and safe mode. It also doesn't work with other camera apps. Another thing I've noticed is that the flashlight is highlighted with a light blue in quick settings but you can't turn it off or on, same with NFC. I didn't drop it or anything, I also bought it used and when I got on Samsung support the person said that they couldn't find the IMEI in their system so it's probably not available for service. Any suggestions? The only idea that I have left is that one of the third party camera apps that I downloaded said something about the camera being in use by another application, any possibility this is actually correct and I can find out what's using it? Other than that I really have no ideas
Did you dropped your phone? There's a possibility that the camera cable got disconnected form the mainboard
try the camera without your sd card. I had same issue on s7, caused by faulty sd card
Vialeb said:
Did you dropped your phone? There's a possibility that the camera cable got disconnected form the mainboard
Click to expand...
Click to collapse
I didn't drop it but I'm thinking this might be the case somehow as much as I don't want to admit it. Samsung support (however useless they were) were pretty adamant that it was a software issue.
This is becoming a widespread issue:
https://us.community.samsung.com/t5...lfie-camera-on-Note-8-not-working/td-p/208206
This may have been caused by the CRHA update that added AR Emoji and Super Slow-mo:
https://www.gsmarena.com/samsung_ga...super_slowmotion_and_ar_emojis-news-33243.php
1.*#34971539# Do you get a menu? and is the phone to cam FW Write greyed out?
2.*#0*# Mega cam test works fine?
This issue is so strange, I have note 8 with same problem when phone is on full Stock Rom even *#0*# cam test fails reads 0 cam. However when I installed Combination Rom (Factory Binary) The camera/flash works fine in the *#0*# and even in more extensive testing menus(Its stock in combination ROM or you can use Info phone Sam app), But I don't know how to flash FW for cameras , since the options are greyed out , I believe I have to place camera FW files (get them from system image?) in a certain folder in root directory(using root explorer) then initiating *#34971539# to enable Phone ---> Cam write, anyone who had this done successfully or experimenting too, your input is appreciated.
Note: When I flash stock rom back, the same problem occurs.
Hello! I recently got the Mi A2, and I've loved it so far (except for issues with upgrading to 9 from 8.1.0, and not being able to flash back) and I decided to try out the Google assistant for the first time, it works fine when my phone is unlocked, it does everything, but when my phone screen is off it doesn't work? It'll listen when I turn the screen on and it's still locked, but if I have to grab my phone to turn the screen on it defeats the purpose of a voice activated assistant. Is this an issue with android pie, or is my phone just broken?
The Mi A2 is not able to do this, it's a hardware limitation.
My 4XL face unlock not work,
So I delete my face unlock and add new again.
But I can't setup. It show fit your face in the inner frame. I try my face to inner frame, not work.
Patch is July.
Help me please.
You are in root ?
Sent from my Pixel 4 XL using Tapatalk
I haven't root brother
Same here, face unlock suddenly stopped working a couple of hours ago, I deleted face data and tried setting it up again - receiving error message that face unlock enrollment didn't work
Is it fixed?
Facing this problem too.
Zero issues on my Pixel 4 or 4 XL. I've never had issues. Might be hardware
vonDubenshire said:
Zero issues on my Pixel 4 or 4 XL. I've never had issues. Might be hardware
Click to expand...
Click to collapse
I have the Pixel 4 XL and it's been working fine until I had to get it replaced because of the 50% battery issue. The replacement phone the face lock setup doesn't work. I've loved the phone so far and was really considering getting the Pixel 6 when it comes out. But these two issues so close together have made me begin to question. I'll never buy another Samsung, so I guess that leaves Apple.
Mine just started doing this after a factory reset. It was driving me crazy. I was able to finally get it to work. Before it gets to the point of scanning your face there will be a place you can click on asking if you have trouble moving your head. Once you click that it will still say the same thing about fitting your face but you will not have to move your head around. Just keep moving your phone in and out and it will eventually take when it finds the sweet spot. I haven't had any issues using face unlock after setting it up.
Had the same problem and apparently it was because of my screen protector. If you have one on, try removing it and test
Solved this problem!
Bakstory: I have Pixel 4XL not locked on carrier's network. I was running Andorid 11 (build from Jun 2021) since the moment I've bought the phone and I have never updated it to the newest versions of Andorid till this days, cause I've read that many Pixel users expirenced problems after update (like not working wireless charging and problems with Face Unlock). Last few month I've noticed that Face Unlock recognized me with 50% chance, I've experinced it earlier and usually I was able to fix it by deletting the face and setting up Face Unlock once more. This time it did not work. I've deleted the face data and was not ale to set it up once more. It was saying "fit your face in inner frame", It was detecting my face, cause it was reacting when I was turning the head and it was sayin "turn your head less" or was reacting when I was moving away from phone by saying "move closer". I've also upgraded to Andoid 13 from push update and problem was not resolved.
Solution: I've rolled back to Andorid 10 (build QD1A.190821.011.C4, Oct 2019), before installing back up your files, cause during the process you will basically reset your phone to factory settings. And on Android 10 Face Unlocked works like charm! It succesfully set up and worked. After that I've upgarded to Android 13 from push update and Face Unlock still works! BUT, DO NOT TRY TO DELETE FACE DATA AFTER ANDROID UPDATE,IN MY CASE IT WOULD NOT SET UP BACK, I HAD TO ROLL BACK TO Andorid 10 TO SET UP FACE.
I had screen protector and the mentioned above problem is not because of it, because I was trying to set up Face Unlock without screen protector for 3 hours straight. I've even downloaded HedgeCam2 to check how Infrared Camera works with it and without it, no difference.
That's definetly software problem, not hardware, greetings to Google Developers
Sorry for grammar mistakes, English is not my primary language. I hope you understood me and I've managed to describe my problem and how I solved it.
Hello
I bought Asus Rog 3 (android 12) after replacing the screen. He has this problem:
- Only the front camera works, when I try to switch to the rear camera, the camera freezes for a moment and switches back to the front camera.
However, if I turn on the google camera in the options, the rear camera works normally.
- Doesn't read fingerprints. Scanner turns on but does not scan any lines.
I thought android 12 broke and I uploaded android 11 from Asus and it's the same. After a while, it updated itself again to android 12.
I have no idea how the fault could be.
Anyone have any advice on this problem?
Are you sure the device re-assembled properly? I've replaced the display in my ROG 3 before, all worked out very smoothly. Nothing special involved beyond making sure motherboard, fingerprint reader, cameras and everything else are all connected back together correctly...
Andrologic said:
Are you sure the device re-assembled properly? I've replaced the display in my ROG 3 before, all worked out very smoothly. Nothing special involved beyond making sure motherboard, fingerprint reader, cameras and everything else are all connected back together correctly...
Click to expand...
Click to collapse
Thanks for the answer.
I was also wondering about it, to be honest, but since the rear camera works in the "google camera" mode and the white line scanner also, but it does not scan the line, the problem is probably in the software.
In fastbootd mode it displays something like this, I do not know if it is correct because it is my first Rog 3
I don't want to open it while it's possible. Therefore, I am asking if any of my honorable colleagues had this or a similar problem.
IrCio36 said:
Thanks for the answer.
I was also wondering about it, to be honest, but since the rear camera works in the "google camera" mode and the white line scanner also, but it does not scan the line, the problem is probably in the software.
In fastbootd mode it displays something like this, I do not know if it is correct because it is my first Rog 3
I don't want to open it while it's possible. Therefore, I am asking if any of my honorable colleagues had this or a similar problem.
Click to expand...
Click to collapse
The screenshot doesn't tell much. However, you won't be able to RAW flash this device from there. Check that your have correct Fastboot access from the bootloader (without navigating to above). Then do a RAW flash to one of the A10 or A11 versions that works.
Andrologic said:
The screenshot doesn't tell much. However, you won't be able to RAW flash this device from there. Check that your have correct Fastboot access from the bootloader (without navigating to above). Then do a RAW flash to one of the A10 or A11 versions that works.
Click to expand...
Click to collapse
Why should I flash in RAW format? What will this change?
Menu, które wkleiłem, to podmenu fastboot.
I downgraded the software from the Asus website to:
- Android 10 (front / rear camera is working properly, fingerprint scanner is not working)
- Android 11 (rear camera not working, fingerprint scanner not working)
- Android 12 (rear camera not working, fingerprint scanner not working)
I don't know where the problem is. I have already written to Asus about this. We'll see what they write back.
I checked the phone's serial numbers on the Asus website and everything is correct.
The phone was not unlocked and rooted. FOTA is working properly.
Just got the latest version dated 01.08.2022
The problem remained.
Hello
As I wrote above.
Asus spoke very quickly. The phone was sent to service in RMA mode. I don't know what they did, but very fast and everything works as it is supposed to.
I contacted the previous owner and it turned out that the screen was replaced on the Asus service. Guarantee until the end of October
And I was so tempted to open it
It's good that I did not do it because it is a little 16/512GB baby girl
Topic to be closed.
Regards
IrCio36 said:
Hello
As I wrote above.
Asus spoke very quickly. The phone was sent to service in RMA mode. I don't know what they did, but very fast and everything works as it is supposed to.
I contacted the previous owner and it turned out that the screen was replaced on the Asus service. Guarantee until the end of October
And I was so tempted to open it
It's good that I did not do it because it is a little 16/512GB baby girl
Topic to be closed.
Regards
Click to expand...
Click to collapse
I am having similar issue my fingerprint was not working after screen replacement but now after few months my front came stopped working it was working three days back on android 10 and 11 i updated firmware from 10 to 11 to 12 and than degraded from 12 to 11 to 10 but issue still exists my front came and whatsapp video call not working back came is working but when i try to switch to front it freezes and screen turns black until cache clears