I don't know what kind of developers HMD hires but, the software is half baked and not optimized properly.
Am I too late in saying that they should atleast provide bootloader unlock, so that we can have a better and more optimized software.
Blast Sarvikas, HMD and Nokia Mobiles on twitter and ask them either to optimize the software or provide bootloader unlock.
Problems right now:
1. Try locking phone using hardware button on an app with white screen, you will see a reddush hue when the screen turns off.
2. Very bad animation and laggy animations. App switching by double tapping recents used to be a breeze but now it's laggy af and sometimes doesn't even works.
3. Incompatibility with a lot of apps even after those apps are optimized for Android 9; Sound indictor sticks on the screen for more than one minute, phone heats a lot, battery draining, etc. One such app, that cause these problem is Lastpass.
4. Fingerprint problem; sometimes it doesn't works or is too late.
I agree with 1,2 and 4.
I have no such problems.
Model TA1055 November update
Pepousek67 said:
I have no such problems.
Model TA1055 November update
Click to expand...
Click to collapse
No issues like that on mine either.
I did not have such problems with my Nokia 7 plus. Everything is snappy and works very fast.
The only thing I noticed was crazy switching of the adaptive brightness and notifications that do not fit well the text.
Some of them are addressed in the November patch.
Coming from a phone that would never get a security update, I think this phone is heaven.
Hello! For some reason my phone has these weird dark spots that jump around whenever there's something dark on my phone (Reddit dark mode, twitter, discord, dark spots on youtube/netflix) and I tried to use a screen recorder to capture it but it doesn't show up on the video, so I assume I just have a faulty screen? Or is this a bug with Android Pie? I only got the phone a few days ago, no drops or thuds on it.
It's a known issue that was introduced in the February security update.
https://forum.xda-developers.com/mi-a2/how-to/poll-screen-flickering-poor-grey-t3904670
ivanosky said:
It's a known issue that was introduced in the February security update.
https://forum.xda-developers.com/mi-a2/how-to/poll-screen-flickering-poor-grey-t3904670
Click to expand...
Click to collapse
Well, I guess I'm happy my screen isn't broken but this also means I don't know how to fix it.. Have they announced that they know this? Once I update my phone to pie (The day I got it sadly) I've noticed so many issues with it, and I can't go back to Oreo :/
People have reported it but no official response from Xiaomi yet. We'll have to wait and see if the March security update fixes it.
ivanosky said:
It's a known issue that was introduced in the February security update.
https://forum.xda-developers.com/mi-a2/how-to/poll-screen-flickering-poor-grey-t3904670
Click to expand...
Click to collapse
Thanks for these details. I almost accepted the update but declined.
It's going to take a lot for me to purchase a Mi A3. Quality control on this device is horrid.
Hi guys is any of you guys has new firmware? 4_22B?
if you do how tp get it?
https://ibb.co/nbkqdfs
echocae said:
Hi guys is any of you guys has new firmware? 4_22B?
if you do how tp get it?
https://ibb.co/nbkqdfs
Click to expand...
Click to collapse
How to get it... apply for a job @ Nokia.... learn the definition of the last character of the firmware build... it says B guess what it means.
So unless it gets leaked, which most likely won't happen, you've to wait for an A
Hawkysoft said:
How to get it... apply for a job @ Nokia.... learn the definition of the last character of the firmware build... it says B guess what it means.
So unless it gets leaked, which most likely won't happen, you've to wait for an A
Click to expand...
Click to collapse
well if B is Beta.. then A.. is Alpha... so we need F.. Full Version...:laugh:
That looks legit and could be the new release. I wouldn't pay much attention to the letters. There's new builds of touch and camera firmware, which could mean lesser issues with the fingerprint sensor and the camera errors.
Apparently nokia said via Twitter that they had some one time issue in getting the security release on time. That we should expect a FM this week. Not sure if it is true. But I'm disappointed that they don't honor the Android One promise
I'd much rather prefer they get the update right in terms of fixing whatever camera issues/fingerprint sensor they resolved than getting it sooner half-baked that will require yet another update.
My stable version has a F in the end
isopure said:
I'd much rather prefer they get the update right in terms of fixing whatever camera issues/fingerprint sensor they resolved than getting it sooner half-baked that will require yet another update.
Click to expand...
Click to collapse
Yeah for the camera I don't mind to wait. But for the security updates I do mind to wait as this is a separate update that has nothing to do with camera
There is updateV.4.22C .Just instaling ( in Poland )
Netherlands as well
India!
Also in Spain.
New update build number
I just updated to the latest update, fingerprint enrollment hasbeen update, Its quite reliable and has a more success rate, still slow but I don't mind it since not tell me to press harder like before, hope it gets better with future updates.:laugh:
Never mind fingerprint. Camera is what most people bought this phone, and it was horiblle also ( I mean app ).Lot's of bugs
Any release notes?
Just applied update
Fingerprint reader is now perfect though aesthetically the small brackets around the thumbprint distract. Can't say anything about camera.
250Mb. Took a very long time to install over a fast wifi connection. I was afraid that I had bricked my phone.
United States. T-Mobile. Unlocked phone.
The bug in translation in Camera app still present (bokeh). Fingerprint sensor almost as ****ty as it was. I deleted all fingerprints and added four new. Press harder...
FP still ****.. maybe due to screen protector too thick...
Camera is improve littlebit Manual still have bug eventhou u set the shutter speed still go automatic
Pro mode is still buggy i think..When cam set to "ISO prority" ( ISO set on 100 ) assuming, that camera mesures exposition automatically, the time suppose to be selected in auto position, and it all suppose to give proper exposition. But when ISO is set , time goes itself to 1/33 sec, that gives total underexposition. Time has to set manually based on the display preview to have things to work. So does it mean, that in Pro mode exposition hase to be set manually, or it is another bug? Timer sound in Cam app ,still not working correctly
No... In pro mode everything is manual
The fingerprint sensor on my Mi A2 is not working for the most part. It takes around 4-5 trys to unlock when the screen is off. If you turn the screen on first, then it might work in 2-3 trys.
The response time is also very slow. Feels like a whole second. Is anyone else having the same issue?
The phone is not rooted. I am on August update.
Same here. I thought that I have scratches on my finger which make it hard to be recognized. I tried adding new fingerprint but it gave a warning that fingerprint sensor is dirty.
alperdemir32 said:
Same here. I thought that I have scratches on my finger which make it hard to be recognized. I tried adding new fingerprint but it gave a warning that fingerprint sensor is dirty.
Click to expand...
Click to collapse
This is not the case for me. I am able to add new fingerprint. It never says fingerprint sensor is dirty. Once or twice it won't recognise the finger while adding as well.
TheUnknownDude said:
This is not the case for me. I am able to add new fingerprint. It never says fingerprint sensor is dirty. Once or twice it won't recognise the finger while adding as well.
Click to expand...
Click to collapse
is your system updated with august security patch?
ixyco96 said:
is your system updated with august security patch?
Click to expand...
Click to collapse
Yes
I sometimes have this problem, especially when recharging the phone or when it has gotten a little hot.
do you use the official charger?
Also try to reboot your phone if it's been a long time you don't shutdown the phone ?
After a few days with the Pixel 7, sadly, I decided to return it.
The biggest reason is the fingerprint reader just didn't work right. 3 out of 4 finger presses don't work. I don't know if it's just a faulty phone that I got, but I got tired of redoing the fingerprint scans.
I have Pixel 6 and the fingerprint reader works very reliably.
The Face Unlock works but I found a bug that if the face unlock is enabled, then for all of the 3rd party apps that use biometric login, the fingerprint unlock stops working and these apps don't support the face unlock.
I had a terrible time getting mine registered and working. I have dry fingers and after moisturizing a little, the enrollment went in one go and the fingerprint works as fast as any other phone.
I have no idea how I got it fixed but I was having the same issue as you. I disabled verity and verification to flash custom kernel (wiped phone after verity) and after that the FP reader is working with 100% accuracy. It was night and day for me.
The fingerprint reader seems to be worse on the Pixel 7 than it was on my Pixel 6. It's fast but has a much higher failure rate.
Has anyone seen a difference with the animation speeds changed in developer options?
My son has my old pixel 6 and the fingerprint reader is working great.
{Mod edit: Quoted post has been deleted}
I tried it in any way I could think of. Dry, wet, sanitized with alcohol, greasy, dirty, you name it. Did not work.
feligoni said:
I have no idea how I got it fixed but I was having the same issue as you. I disabled verity and verification to flash custom kernel (wiped phone after verity) and after that the FP reader is working with 100% accuracy. It was night and day for me.
Click to expand...
Click to collapse
If I pay $600 for the phone and have to do ADB "contortions" to get the FP scanner to work, then I don't need the phone like that.
A "cheap" inlocked Chinese POCO phone with under screen FP reader works 100% of the time without disabling dm-verity.
Wow I find my Pixel 7 to be much better on the FP scanner than my P6 was, I even added a screen protector after enrolling my prints. I also now use the face unlock and have no issues with Apps that use the FP biometric option. This phone is way better than my P6.
xela19115 said:
If I pay $600 for the phone and have to do ADB "contortions" to get the FP scanner to work, then I don't need the phone like that.
A "cheap" inlocked Chinese POCO phone with under screen FP reader works 100% of the time without disabling dm-verity.
Click to expand...
Click to collapse
Agree - I'm fairly familiar with Xiaomi phones and their FP readers are pretty reliable. I'm surprised how poorly my Pixel 7's reader is. In this day and age, we shouldn't have to compromise on what's supposed to be a stable technology after paying $600.
I do notice something interesting though - the failure rate is very high when I try to unlock it after a little while (a little while being >15m). But, if I fail and enter my passcode, every subsequent try is super fast. It's almost as if the phone realizes it's not doing a good job a the initial recognition, adjusts its stored FP data, and then gets better for a while. Anyone else notice this?
xela19115 said:
After a few days with the Pixel 7, sadly, I decided to return it.
The biggest reason is the fingerprint reader just didn't work right. 3 out of 4 finger presses don't work. I don't know if it's just a faulty phone that I got, but I got tired of redoing the fingerprint scans.
I have Pixel 6 and the fingerprint reader works very reliably.
The Face Unlock works but I found a bug that if the face unlock is enabled, then for all of the 3rd party apps that use biometric login, the fingerprint unlock stops working and these apps don't support the face unlock.
Click to expand...
Click to collapse
Really? I have not had that problem - any conflict between face unline and Finger for Biometric apps. Face unlock is outstanding. Fingerprint reader is meh, ok, sometimes
a1b2c3d4444 said:
Agree - I'm fairly familiar with Xiaomi phones and their FP readers are pretty reliable. I'm surprised how poorly my Pixel 7's reader is. In this day and age, we shouldn't have to compromise on what's supposed to be a stable technology after paying $600.
I do notice something interesting though - the failure rate is very high when I try to unlock it after a little while (a little while being >15m). But, if I fail and enter my passcode, every subsequent try is super fast. It's almost as if the phone realizes it's not doing a good job a the initial recognition, adjusts its stored FP data, and then gets better for a while. Anyone else notice this?
Click to expand...
Click to collapse
I have noticed that same thing on my 7 Pro although for me it's more like an hour+ where it gets bad... It will be fine all day then I set my phone down for awhile, pick it up later, and it will instantly fail all three times and then start working again after my PIN goes in. Very strange. Probably can be fixed with software.
No problems here, had the phone for a week now. I don't think I've had any failed reads, maybe one or two. Very reliable and fast, perfect combo with the face scanner.
Mine was failing like crazy. Tried everything. Took it back and exchanged for a new one and the new one is working great. Definitely some faulty hardware out there
a1b2c3d4444 said:
Agree - I'm fairly familiar with Xiaomi phones and their FP readers are pretty reliable. I'm surprised how poorly my Pixel 7's reader is. In this day and age, we shouldn't have to compromise on what's supposed to be a stable technology after paying $600.
I do notice something interesting though - the failure rate is very high when I try to unlock it after a little while (a little while being >15m). But, if I fail and enter my passcode, every subsequent try is super fast. It's almost as if the phone realizes it's not doing a good job a the initial recognition, adjusts its stored FP data, and then gets better for a while. Anyone else notice this?
Click to expand...
Click to collapse
similarly
Mine works flawlessly every time. The only thing I don't like is using it at night, and not covering it with my entire finger. When it scans, it's so freakin' bright! LOL
My 7 Pro's sensor worked great, my regular 7's is just plain awful. And I know about the dry hands issue, I've been preaching that people moisturize their hands since under-display sensors came out.
At the first time with my pixel 7 the i had your same issue, fp wasnt working 9 time on 10 but then, after registered it again correctly (reading the on screen instruction while do it) is started to work flawlessly every time. Now it is always unlocking the phone, with more light or in the dark (at night for example) and with low or high brightness.
a1b2c3d4444 said:
I do notice something interesting though - the failure rate is very high when I try to unlock it after a little while (a little while being >15m). But, if I fail and enter my passcode, every subsequent try is super fast. It's almost as if the phone realizes it's not doing a good job a the initial recognition, adjusts its stored FP data, and then gets better for a while. Anyone else notice this?
Click to expand...
Click to collapse
This was the case with my P7 too. But since past few days, it started to work like 10/10. I haven't noticed any failure since yesterday. Never changed the fingerprint data too.
Update!
I returned the phone. I waited until I got the refund, took a train ride to NYC, and went to Google's Chelsea store. I bought a new Pixel 7 128 GB, traded my Pixel 6, and spend about 2 hours setting up everything in the store. Another advantage of going to the store is that I don't have to pay $600 + tax immediately and then wait 2-3 weeks for a $490 trade-in credit. They take the trade-in and I paid the difference.
If the fingerprint scanner on the new phone would have given me the same issues, I would have at least dealt with it in the store.
And it did start giving me issues initially, but then I asked for assistance and they (store tech support) admitted that Pixel 7's have fingerprint reader problems. He changed the sensitivity setting on the phone and it works (for now).
So clearly I had a bad, faulty phone before. Now, with a phone that I got over the weekend, everything works.
xela19115 said:
Update!
I returned the phone. I waited until I got the refund, took a train ride to NYC, and went to Google's Chelsea store. I bought a new Pixel 7 128 GB, traded my Pixel 6, and spend about 2 hours setting up everything in the store. Another advantage of going to the store is that I don't have to pay $600 + tax immediately and then wait 2-3 weeks for a $490 trade-in credit. They take the trade-in and I paid the difference.
If the fingerprint scanner on the new phone would have given me the same issues, I would have at least dealt with it in the store.
And it did start giving me issues initially, but then I asked for assistance and they (store tech support) admitted that Pixel 7's have fingerprint reader problems. He changed the sensitivity setting on the phone and it works (for now).
So clearly I had a bad, faulty phone before. Now, with a phone that I got over the weekend, everything works.
Click to expand...
Click to collapse
which sensitivity setting ?
The scanner is bad, that's all. The crucial thing to make it usable is the right inital scan, if it records your fingers flawlesly it will work (but not the way we expect, only in an acceptable way).
There is no sensitivity setting, he probably mean the display setting.