Hi,
I received my N9 this last Friday. I'm very happy with it except when it's charging. I'm having two issues:
Ticking noise: A few minutes after plugging it to the charger, the tablet makes a ticking noise coming from the speaker. Imagine water drops dripping repeatedly like in a chinese water torture.
Lockscreen goes crazy / UI crash: when I try to unlock the tablet while it's charging the lockscreen is constantly trying to refresh in a loop. I can't get it out of it. I have to turn off the tablet and restart it. Then when I unlock it, I get a message the UI system crashed.
Has anyone else experienced this?. I supposed it's a defective unit. I will be asking for a replacement. What do you think?
I don't have this problem, very likely it's defective
Yeah, definitely nothing like that going on with mine. I've seen a couple of other people complaining about the ticking but the wonky UI thing is a new one. I would definitely be sending that one back if I were you.
I have the same lockscreen loop issue when charging, if I unplug the charger, the device work again, no need to reboot, but I can't use the device while it's charging.
For the noise issue, I notice that each time I close the camera app I can hear a sound from the top speaker but not when charging.
I really like this tablet but I will return mine, light bleed, top volume rocker not clicky like the lower one, screen flicker even if the auto luminosity is turn off, get really hot and the lockscreen issue... My n9 is a white 32gb version from the play store in Canada.
My colleague bought 2 Nexus 9 from Google Play Canada and both of them have the lockscreen loop issue the systemui crash issue and the ticking noise issue when charging. As soon as he unplugs the charger all the problems are gone. I am guessing it is a problem with the firmware....
I've have the same issue (Nexus 9, 32G, WIFI only, from Canadian Play Store).
Same "clicking" nose and lock screen bug while charging, making the device unusable. Everything looks fine when on battery.
While charging, I changed the system language from French Canadian to English US, and the bug seamed to disappear...
I'm wondering if I should return the device, since everything else seams to be working without problem (no noticeable light bleed, etc).
Try another cable.
Interesting. Mine too is from Google Play Canada and I have the language set to French. I'll try setting it to English and see if the problems disappear.
Anyway, I called Google and they're sending me a replacement.
Sent from my Nexus 9 using XDA Free mobile app
munza7 said:
Interesting. Mine too is from Google Play Canada and I have the language set to French. I'll try setting it to English and see if the problems disappear.
Anyway, I called Google and they're sending me a replacement.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Just let me know when you try, since I might wait a bit if it's a software issue, as the replacement might not be any better.
lemieulp said:
Just let me know when you try, since I might wait a bit if it's a software issue, as the replacement might not be any better.
Click to expand...
Click to collapse
I switched it to English and both issues dissapeared. So it's a software bug.
Have you tried flashing the stock image ?
I tried a factory reset, but it made no difference.
Sent from my Nexus 9 using XDA Free mobile app
I had the same issue with mine, coming also from Google Play Canada.
As I saw here, I changed the language from French (Canada) to English (US) and the problem vanished.
I then tried to change language to French (France) and still no problem.
I also noticed this difference in the Google search bar:
- With language set to french-canada, text is: Dites "1$s"
- With language set to english-us, text is: Say "OK Google"
- With language set to french-france, text is: Dites "OK Google"
Also, the UI crash loop appears when turning on the "OK Google detection always on" feature. So it might be a Google Now Launcher issue.
I also have this issue. Buy from Play Store Canada, doesn't really matters 'cause it's ship from US. Nexus 32G white, french canadien input.
I' ll disable the ok Google command and wait to see if happen again.
I'll post the result here.
MGanador said:
I had the same issue with mine, coming also from Google Play Canada.
As I saw here, I changed the language from French (Canada) to English (US) and the problem vanished.
I then tried to change language to French (France) and still no problem.
I also noticed this difference in the Google search bar:
- With language set to french-canada, text is: Dites "1$s"
- With language set to english-us, text is: Say "OK Google"
- With language set to french-france, text is: Dites "OK Google"
Click to expand...
Click to collapse
I was going to write exactly this ! It seems to be an issue with the Canadian-French translation in Android 5.0.
When changing from Canadian-French to any langage there is no more ticking noise when charging.
Dwiguy said:
I also have this issue. Buy from Play Store Canada, doesn't really matters 'cause it's ship from US. Nexus 32G white, french canadien input.
I' ll disable the ok Google command and wait to see if happen again.
I'll post the result here.
Click to expand...
Click to collapse
Ok it works fine. No more issues if Google ok! is off.
Who is going to tell Google about that?
Works here to, my colleague says thanks. I am sure Google will fix this in future update
Related
Hi guys,
I hope that this is the proper forum, if not please direct me to the correct one.
I am currently using a Sprint Samsung Galaxy S6, non-rooted.
My problem started about 48 hours ago while I was voice dictating a test message.
I was doing my regular texting with the SwiftKey keyboard microphone (problem also replicates with the Samsung Keyboard as well) and the box at the bottom of the screen would not go away. I tried to X it out, hit the back button and the home button but nothing gets rid of it other than restarting the phone.
This all seemed to start happening after the Google App update.
I rolled back to the old version and it seemed to work fine. Last night, it updated itself again and problem was back.
I have included an image of what I am talking about.
If anyone has any suggestions, I would be very appreciative!
Thanks
Mikeinstlouis
I have to same issue that just happened and same as the screenshot.
Same issue...
This is so freaking ridiculous! A Google update that does this crap?!
I too own a S6 Edge Verizon 128GB and I noticed a couple of things.
If you bring up text to speak and then power off your phone.. Once you come back... you have locked it (Until restart)
I tried the following...
1) Reset the Dalvik Cache .. No luck.
2) tried force closing TTS and samsung text to speech.. no go.
3) Uninstalling latest update to the high quality voice. .. No Go.
4) Tried holding both buttons at the Same Time... No go..
5) For quibs and giggles.. Held down the close "X" for 5 whole minutes.
********************************************
What I think is going on is a time out error in the code.
So how i am able to get around it RARELY is..
Bring it up with the microphone button
Say what I need to say then hit the X to close it as FAST AS I CAN!!
I know that with all of our phone hackers, crackers and experts that we can ALL reach a Fix on this.
Damn Google...
mikeinstlouis said:
Hi guys,
I hope that this is the proper forum, if not please direct me to the correct one.
I am currently using a Sprint Samsung Galaxy S6, non-rooted.
My problem started about 48 hours ago while I was voice dictating a test message.
I was doing my regular texting with the SwiftKey keyboard microphone (problem also replicates with the Samsung Keyboard as well) and the box at the bottom of the screen would not go away. I tried to X it out, hit the back button and the home button but nothing gets rid of it other than restarting the phone.
This all seemed to start happening after the Google App update.
I rolled back to the old version and it seemed to work fine. Last night, it updated itself again and problem was back.
I have included an image of what I am talking about.
If anyone has any suggestions, I would be very appreciative!
Thanks
Mikeinstlouis
Click to expand...
Click to collapse
Latest update have little bugs
Sent from my Nexus 5 using Tapatalk
I am also having this issue on my Galaxy S4.
---------- Post added at 02:56 PM ---------- Previous post was at 02:46 PM ----------
mrneoz81 said:
This is so freaking ridiculous! A Google update that does this crap?!
I too own a S6 Edge Verizon 128GB and I noticed a couple of things.
If you bring up text to speak and then power off your phone.. Once you come back... you have locked it (Until restart)
I tried the following...
1) Reset the Dalvik Cache .. No luck.
2) tried force closing TTS and samsung text to speech.. no go.
3) Uninstalling latest update to the high quality voice. .. No Go.
4) Tried holding both buttons at the Same Time... No go..
5) For quibs and giggles.. Held down the close "X" for 5 whole minutes.
********************************************
What I think is going on is a time out error in the code.
So how i am able to get around it RARELY is..
Bring it up with the microphone button
Say what I need to say then hit the X to close it as FAST AS I CAN!!
I know that with all of our phone hackers, crackers and experts that we can ALL reach a Fix on this.
Damn Google...
Click to expand...
Click to collapse
One way I found that I can close it is by opening the menu that has active apps, then going to RAM, next turn the phone on its side (<--- yes do that), then hit clear memory a few times. And done its gone.
Thanks! That worked on my Sprint S4! (restarting phone has also worked for me, but this is easier.)
After holding down Home button to open the menu that has active apps, the options were still covered by the text to speak box. So I had to FIRST turn phone on its side to make visible the pie chart icon on bottom left, THEN then going to RAM tab and hiting clear memory a few times. When I turned it back to portait orientation, the text to speak box was gone. Thanks!
This has been happening to me all day long. so frustrating. I am also not the tech savy one in the house and hubby is not around. So thanks for the quick answer to get rid of it until he can uninstall the new update. Thanks
What is the pie chart menu option? What is the RAM tab? And will just be a little easier for Google to fix this? Lol
same problem here
Galaxy S6, same problem, started last night (September 24, 2015) . I do know that some updates were performed last night, not sure what. How do I uninstall the update? Which one is it? Help! I use voice typing constantly, and my phone is a brick when this thing locks up. It covers all my buttons. "Restart" doesn't clear it, I have to totally power off and back on. Right now, I have disable my voice key on my keyboard so that I don't accidentally touch it while waiting for solution.
Me too - just started today after some updates yesterday.
Same here....has anyone responded with a fix yet??
THANKS!
Glad it's not just me and my Note 3, but where does google get off sending out this kind of crap? It's enough to drive me to a windows phone.
Having the same issue only way I can get ride of it is to turn off my phone
same issue on moto droid mini; have to turn off phone too! poor QA google!!!!!
Me too. Galaxy S4. Have to shut the phone down and restart it to resolve the issue.
Piece of crap
Note 4 same problem started on the 24th
Same issue, Note 4
Same issue, Samsung Note 4.
Yep me too Verizon Galaxy s6
Sent from my SM-G920V using Tapatalk
My wife and I each have the T-Mobile LG V10. Mine works great! Hers does not.
Her sounds will not work consistently. This includes the ringtone and notification sounds. I contacted T-Mobile and they said they have not heard of this issue and I should exchange it. I looked online and found no similar issues. I exchanged it and a day later my wife is having the issues again!! What are the odds??? The only constant between the two phones is the SIM card and Google account info.
Has anyone else had this issue or have any additional ideas on what could be causing the problem?
I have already double and triple checked the notification settings, including the priority calls and interruption settings. I have also performed the factory data reset.
dnourie said:
My wife and I each have the T-Mobile LG V10. Mine works great! Hers does not.
Her sounds will not work consistently. This includes the ringtone and notification sounds. I contacted T-Mobile and they said they have not heard of this issue and I should exchange it. I looked online and found no similar issues. I exchanged it and a day later my wife is having the issues again!! What are the odds??? The only constant between the two phones is the SIM card and Google account info.
Has anyone else had this issue or have any additional ideas on what could be causing the problem?
I have already double and triple checked the notification settings, including the priority calls and interruption settings. I have also performed the factory data reset.
Click to expand...
Click to collapse
Are her ringtones / media files on an sd card? I'm thinking SD card faulty? Or using stock internal sounds? Then my theory don't fly.
Another test, reset hers stock, pop in your SIM and use your account. Troubleshoot those.
clockcycle said:
Are her ringtones / media files on an sd card? I'm thinking SD card faulty? Or using stock internal sounds? Then my theory don't fly.
Another test, reset hers stock, pop in your SIM and use your account. Troubleshoot those.
Click to expand...
Click to collapse
Thanks for replying. No SD card installed. Could the SIM cause a ringer issue????
Maybe a smart setting sound profile?
When you exchanged phones, this you or T-Mobile backup and restore stuff? I know the lg backup will bring old settings back. After the Factory reset, how did you restore the phone?
Does it still happen in safe mode?
Sent from my LG-H901 using Tapatalk
blackhemi4x4 said:
Maybe a smart setting sound profile?
When you exchanged phones, this you or T-Mobile backup and restore stuff? I know the lg backup will bring old settings back. After the Factory reset, how did you restore the phone?
Does it still happen in safe mode?
Sent from my LG-H901 using Tapatalk
Click to expand...
Click to collapse
Great idea, however, I did not use the LG Backup feature. I did check the smart settings, which are all "Off". How do I enter safe mode?
dnourie said:
Great idea, however, I did not use the LG Backup feature. I did check the smart settings, which are all "Off". How do I enter safe mode?
Click to expand...
Click to collapse
Press and hold power button for the power menu. The press and hold the power off icon and it will prompt safe mode.
Sent from my LG-H901 using Tapatalk
Set her phone back up as a "new phone" dont restore or sync her account. Check from there.
UPDATE: Exchanged phone again. This is her 3rd LG V10. Guess what happened a few hours later? Ringer and notification sounds stopped working! Then, they came back on again shortly thereafter. Then they stopped working again! This phone has the same issues as the previous ones...only at least the sound works more often than the previous phones! Hopefully this is a software glitch and LG will fix it. I am very surprised my wife has had three phones in a row with the issue and yet I haven't found any threads with others having this problem.
Have you tried getting her a new Sim card? This seems like an issue that is more user related than phone, since it seems she is the only one we know of with that issue.
I'm not saying it couldn't be the phone, but the chances of getting three bad phones in a row with what seems to be a very rare error is pretty slim.
Sent from my VS990
I completely agree, very unlikely. This time I made sure we got a new sim card. If it is not the phone, the only other option is a software glitch, but the only app she uses that I do not is Candy Crush. I doubt that is messing with the ringtones and notifications...but she isnt willing to part with it long enough to find out!
At least this one works slightly better than the previous two...so far.
dnourie said:
My wife and I each have the T-Mobile LG V10. Mine works great! Hers does not.
Her sounds will not work consistently. This includes the ringtone and notification sounds. I contacted T-Mobile and they said they have not heard of this issue and I should exchange it. I looked online and found no similar issues. I exchanged it and a day later my wife is having the issues again!! What are the odds??? The only constant between the two phones is the SIM card and Google account info.
Has anyone else had this issue or have any additional ideas on what could be causing the problem?
I have already double and triple checked the notification settings, including the priority calls and interruption settings. I have also performed the factory data reset.
Click to expand...
Click to collapse
My wife and I have the same phones and hers after she plays a game the ringer and notification sound will not play. I have check all the settings but can't come up with a reason for it. If she restarts the phone it will work till the next time. I was going to take it back today after work, but after reading this post I don't know if that would do any good.
eddyjr1 said:
My wife and I have the same phones and hers after she plays a game the ringer and notification sound will not play. I have check all the settings but can't come up with a reason for it. If she restarts the phone it will work till the next time. I was going to take it back today after work, but after reading this post I don't know if that would do any good.
Click to expand...
Click to collapse
You are correct, I'm not sure it would help. After my wife had the issue with a third phone, she finally had enough and traded for a Note 5. Interesting note, the only difference between her and I was that she played games a lot...specifically Candy Crush games. Perhaps there is a compatibility issue with those or one of her other games. Hopefully this issue is resolved for you, because the phone was great otherwise!
Two of the games she plays when this happens are hearts and candy crush saga. I turned on vibration with sound and vibration will still work when sound profile doesn't. Haven't found connection yet.
I lost ringtone but still had notifications and message sounds. Don't know what happened but a restart fixed it for now. I don't have any games on my phone at all.
Sent from my LG-H901 using Tapatalk
dnourie said:
I completely agree, very unlikely. This time I made sure we got a new sim card. If it is not the phone, the only other option is a software glitch, but the only app she uses that I do not is Candy Crush. I doubt that is messing with the ringtones and notifications...but she isnt willing to part with it long enough to find out!
At least this one works slightly better than the previous two...so far.
Click to expand...
Click to collapse
That game always causes problems for my wife's phones.
Same issue!!!!
dnourie said:
My wife and I each have the T-Mobile LG V10. Mine works great! Hers does not.
Her sounds will not work consistently. This includes the ringtone and notification sounds. I contacted T-Mobile and they said they have not heard of this issue and I should exchange it. I looked online and found no similar issues. I exchanged it and a day later my wife is having the issues again!! What are the odds??? The only constant between the two phones is the SIM card and Google account info.
Has anyone else had this issue or have any additional ideas on what could be causing the problem?
I have already double and triple checked the notification settings, including the priority calls and interruption settings. I have also performed the factory data reset.
Click to expand...
Click to collapse
I am having the SAME issue with mine. I have had it since November 2015 and got my husband the same phone for Christmas. His works just fine and mine does not. It will NOT alert me for my text messages for anything. I have checked and rechecked ALL settings.
I too am having this issue and yes I think it's candy crush. This morning I had a full lives notification icon in the task bar and no alarm clock tone just vibration.
I'm having this issue as well. I do not play or have candy crush. My issue started after the last forced update. This is my 2nd phone that has done this. I also have at&t
Hi Guys,
i have a elephone p9000E...watch out the roms of p9000 (without E) will not working on this model. By needroom you can find some roms, if you need, and they are working 100%
I have a question, is there a way to improve the battery performance? i meand without grenify and that kind of apps?
Also a way to get notifications? this phone has no led notifications so it would be fine to could see something on the screen when you get a whatsapp message or email.
Thanks.
erdoctor1981 said:
Hi Guys,
i have a elephone p9000E...watch out the roms of p9000 (without E) will not working on this model. By needroom you can find some roms, if you need, and they are working 100%
I have a question, is there a way to improve the battery performance? i meand without grenify and that kind of apps?
Also a way to get notifications? this phone has no led notifications so it would be fine to could see something on the screen when you get a whatsapp message or email.
Thanks.
Click to expand...
Click to collapse
Is your handset branded as a P9000E in the "About Phone" section? Does it have QI/wireless charging and NFC?
warface said:
Is your handset branded as a P9000E in the "About Phone" section? Does it have QI/wireless charging and NFC?
Click to expand...
Click to collapse
In model it is only P9000 but in buld number see it is E
Hi,
No is branded as P9000 but I bought it as a P9000E.
Stock rom offline P9000 works but no fingerprint.
I don t have wireless charge and NFC. Even any led notification.
Same as my handset. I think I got ripped off, as the qi charging was the main reason I went with this handset.
New P9000E
I have a brand new P9000E direct from the Elephone Aliexpress shop (delivered to UK).
It's a stock rom and updated as soon as it booted to;
Elephone_P9000_E_20170401
It also has P9000 as the model and also has a working fingerprint scanner.
Anyone need any info from it ?
My only issue is the default browser...... when did Android force the default browser to need access to every permission? Am I missing something.
poulsej said:
I have a brand new P9000E direct from the Elephone Aliexpress shop (delivered to UK).
It's a stock rom and updated as soon as it booted to;
Elephone_P9000_E_20170401
It also has P9000 as the model and also has a working fingerprint scanner.
Anyone need any info from it ?
My only issue is the default browser...... when did Android force the default browser to need access to every permission? Am I missing something.
Click to expand...
Click to collapse
Does yours have QI/wireless charging?
Do you have a notification LED for ANYTHING?
The default browser sucked hard. I just installed chrome....
So this is the item in their shop.
https://www.aliexpress.com/item/Ori...32811199926.html?spm=2114.13010608.0.0.wUpvxT
https://www.youtube.com/watch?v=E7dCHlOkzGs
-Does yours have QI/wireless charging?
I don't think it can do wireless charging. Don't have a charger to test.
Certainly doesn't mention it anywhere in the docs/specs.
-Do you have a notification LED for ANYTHING?
No LEDs at all as far as I can see, although the touch button at the bottom might possibly have some form of led in it.
I guess it's possible this android build doesn't have it activated.
-The default browser sucked hard. I just installed chrome....
Completely agree. I've seen the same issue on a lot of chinese android 6. And yet Samsung don't enforce any permissions on the default browser. Just makes me suspicious about why they would do this.
- Also no factory reset from the Factory Mode.... only auto test/test report/gps/version
Overall I think the phone is brilliant but maybe there are some updates to come.
i bought a new amazfit verge us version (a1811) and updated its fw to 3.2.2.0. everything is fine but when the screen is off, notification beep sounds like sizzling and bad. all other sounds are normal. do you have the same problem? how can i fix it?
stu35 said:
i bought a new amazfit verge us version (a1811) and updated its fw to 3.2.2.0. everything is fine but when the screen is off, notification beep sounds like sizzling and bad. all other sounds are normal. do you have the same problem? how can i fix it?
Click to expand...
Click to collapse
A1811 is not US version it's international version, included US market. No i did not noticed any sounds problem. But if say honest most time i using only vibrate notifications without any sounds Sounds is in smartphone
several people in the forum came across the same problem. is it a condition that I need to send to the warranty? Is it solved by software update? I also sent a notification from the feedback section of amazfit watch.
stu35 said:
several people in the forum came across the same problem. is it a condition that I need to send to the warranty? Is it solved by software update? I also sent a notification from the feedback section of amazfit watch.
Click to expand...
Click to collapse
As i mentioned usually i using notifications without sound, only vibration is activated. When i did factory reset notifications sounds fine to me. But that was once, maybe two time when i used notifications with sound at all after these updates. So i can't confirm it's issues/bugs or not. But one advise which i got from Amazfit support when i asked about battery life which after update is shorter, they advised me to first do factory reset. So i can advise you the same. If problem will be the same you can try to chat before you will bring watch to seller or authorized service to Amazfit support and when after you will talk with support do what they will advise you or bring to service or seller. Factory reset if say honest most time fixing small problems in many devices (if there is no biggest violations): smartphones, smart watches and ect. Without detail review hard to say it's software problem or soundspeaker I have problem with wifi in my smartphone, when is turned on bluetooth wifi dropping, usually internet wokring fine in others device, dropping is not often, but when i turning off bluetooth works fine. Manufactor supporting gave me some advices which did not helped to me, need to test in others device or with others wifi connections, but i can't to do right now that. So it's conflict between wifi and bluetooth or just others reason it's hard to say. The same is with yours situation, about problem can confirm some costumers.users, but for others can work fine. So i posted my advises, i think the best right now is just to talk with Amazfit support before you return it to seller or bring it to authorized service or do factory reset, which by the way i recommend to do before connect with Amazfit support, cos i'm sure they will ask about that
thanks for the reply. i will try the factory reset. i hope it will fix it. thank you.. :good:
i did factory reset to watch and sent test notifications from amazfit watch app. nope. still continues same problem.. after all i set warning tone volume silent and only vibration. i hope it will be fixed with a firmware update.
stu35 said:
i did factory reset to watch and sent test notifications from amazfit watch app. nope. still continues same problem.. after all i set warning tone volume silent and only vibration. i hope it will be fixed with a firmware update.
Click to expand...
Click to collapse
This is support with chat option - https://support.amazfit.com/hc/en-us (if you can't see help/chat option, then scroll down with mouse and you will see chat window in left side of computer/smartphone), check from time to time are they online, coz they often are diconnected from chat. I can chat with they only when is evening in my country. I guest they are in US and connecting only in day time, maybe after lunch time
This is support via mail - https://en.amazfit.com/support.html, you can write from mail anytime, they will answer to you soon when they will can, probably
There is nothing to thank, I trying to help as much as I can. Sad that factory reset did not helped, try to chat with support (live or via mail, you probably just sent feedback from app, in feedback they don't react, i mean they will not answer to you)
I saw a post in Reddit from a Huami global support person in the Amazfit subreddit and i have mentioned to him about the sound problem as well as other things. He say it is a known problem and it is worked on. So hopefully with the next firmware we will get a fix for that.
Sent from my LG-H870 using XDA Labs
PsychoTribe said:
I saw a post in Reddit from a Huami global support person in the Amazfit subreddit and i have mentioned to him about the sound problem as well as other things. He say it is a known problem and it is worked on. So hopefully with the next firmware we will get a fix for that.
Sent from my LG-H870 using XDA Labs
Click to expand...
Click to collapse
Yep, and i wrote that here somewhere and on FB and other places. Its being worked on.
A problem with the sound is two months to me. The manufacturer is made to "cuckoo" - refuses to recognize the problem. A problem with sound exists in all - Europe, Russia, America.
I tried everything, settings, restart, unlock, new installation, Chinese version, factory settings - did not fix a problem.
There is an update rolling out at the moment that says it is fixing the problem. It is 3.2.3.0 if i remember correctly. Just have some patience. Should be here any time now.
PsychoTribe said:
There is an update rolling out at the moment that says it is fixing the problem. It is 3.2.3.0 if i remember correctly. Just have some patience. Should be here any time now.
Click to expand...
Click to collapse
I can confirm, i got update today was written the same
Got the update last night. Tried to check voicemail morning and was greeted with Alvin & The Chipmunks blabbing at me. It's like the speed of the call is x20 speed or something. It's completely unusable. Phone sluggish as hell, too.
Anyone know what's going on with the voice speed? I've never heard of anything like this.
I'm supposed to get a callback for a job interview I had yesterday. Pretty crappy timing. How is Google going to push an update that breaks calls like this? Absurd.
its nokia that pushed the update they did not make the rom right
Same here I told nokia about it and they told me to wait for a bug fix. I told them I wanted to downgrade since your firmware bug broke my phone.
Just wait for a bug fix? So use a Phone that cant make calls right?
So payed a guy to unlock my boot loader to try to flash a rom so i can just make the phone usable.
I spend about 6 hours try to get the rom to work. With little to no luck I was able to get into twrp a few times.
So ya Im in the same boat. I just got this phone back 3 weeks ago from a rma due to a bad chargeing port. Now Im forced to pay some one to unlock the boot loader and try to get a custom rom Just to be able to call
If I cant get the rom working Im going to have to go spend like $200 on a new phone today just sucks
fisterkev said:
Got the update last night. Tried to check voicemail morning and was greeted with Alvin & The Chipmunks blabbing at me. It's like the speed of the call is x20 speed or something. It's completely unusable. Phone sluggish as hell, too.
Anyone know what's going on with the voice speed? I've never heard of anything like this.
I'm supposed to get a callback for a job interview I had yesterday. Pretty crappy timing. How is Google going to push an update that breaks calls like this? Absurd.
Click to expand...
Click to collapse
Same thing happened to me with the sped up chipmunk-y sound. It happened during the dial and after someone picks up. Though it didn't seem to happen every time. Also, I didn't notice it on any incoming calls, just outgoing.
I tried a few things to fix it--rebooting, clearing some app caches, etc. Nothing seemed to work.
My next step was to try a factory reset, but then all of a sudden the issue disappeared. No new update was released/installed, so I just assumed the issue had been on my provider's end (T-Mobile), and they fixed whatever the problem was.
As for sluggishness of the phone after the update: I agree. It seems a little sluggish to me too. Not anything that is making the phone unusable. But it is noticeably more sluggish than when 9.0 was installed.
Have you guys modified the phone in any way like unlocking the bootloader or rooting?
gumbyx84 said:
Have you guys modified the phone in any way like unlocking the bootloader or rooting?
Click to expand...
Click to collapse
I haven't. Just using whatever over the air OS Nokia pushes to the phone.
yes I did pay to unlock the boot loader I used linage from the rom section
it has all the bugs of the stock rom. Cant call out or with out the loud noise bug and no voip apps work
I did get the Android 9 based rom to work. it has a few bugs but its usable.
I more or less gave up im looking at a iphone now.
I spend 20 hours or more trying to get this phone to work
first the usb port goes out and I cant charge.
2 weeks after having the phone back I got a magnetic cable so the usb port would not brake any more cable. That was like $20
After 2 weeks android 10 more or less bricks the phone (a phone that cant make calls)
Then I have to spend like $15 to pay the poor guy to unlock my boot-loader (he did a great job)
I spend a lot more time loading the linage android 10 rom for it to have the same bugs ( in no way is it the devs fault im sure he did not know).
... can unlock your bootloader for a small fee.
I would say all android 10 based rom will have those kind of problems. I can only confirm it on the android 10 linage one
When I flash twrp most of the time the twrp would just freeze if booting form the phone.
I had no problem loading it with fastboot works evey time. So I would only use it install the rom and just boot it when you need it. I would not suggesting flashing it to recovery as it only worked some of the time for me.
Hope all that info helps
QUOTE=gumbyx84;81261583]Have you guys modified the phone in any way like unlocking the bootloader or rooting?[/QUOTE]
---------- Post added at 06:48 PM ---------- Previous post was at 06:44 PM ----------
The calling problem goes in and out. Some times it works some times it dose not. Facebook message outgoing calls the mic will not work, Same with google voice.
if i make calls with out google voice it works 1/2 the time. all the people have the same problem
https://community.phones.nokia.com/discussion/54374/android-10-after-update-on-nokia-7-1
diggeryo said:
Same thing happened to me with the sped up chipmunk-y sound. It happened during the dial and after someone picks up. Though it didn't seem to happen every time. Also, I didn't notice it on any incoming calls, just outgoing.
I tried a few things to fix it--rebooting, clearing some app caches, etc. Nothing seemed to work.
My next step was to try a factory reset, but then all of a sudden the issue disappeared. No new update was released/installed, so I just assumed the issue had been on my provider's end (T-Mobile), and they fixed whatever the problem was.
As for sluggishness of the phone after the update: I agree. It seems a little sluggish to me too. Not anything that is making the phone unusable. But it is noticeably more sluggish than when 9.0 was installed.
Click to expand...
Click to collapse
How to fix the phone call problems
To everyone having calling issues (distortion / squealing, or other people can't hear them), try this: Turn off Voice over LTE. You go to Settings -> Wireless and Networks -> Mobile Networks -> VoLTE, and turn that setting off. This fixed the problem for all 3 Nokia 7.1 phones in our family, when nothing else seemed to work.
Turning off VoLTE and wifi calling works, but VoLTE is important in my area with TMobile. Without it, too many dropped and missed calls. I actually downgraded from an Xperia XZ1 just to get VoLTE, now this happens.
I have TA-1085 running Android 10 that was pushed OTA on 12/25, while I do not have calling issues (from native call app) initially, calling from all 3rd party app (e.g. Messenger or Wechat) are not working: I can hear other side, while the other side can not hear me.
In addition to disabling VoLTE, I also changed the 'preferred network type' (see posting from author 'fiumaxx' on nokia's user forum, search there using android-10-after-update-on-nokia-7-1 as search string). I changed it to LTE/CDMA which works well for me.
Normal call sound is back to normal but 3rd party calling still not working.
zhou68000 said:
I have TA-1085 running Android 10 that was pushed OTA on 12/25, while I do not have calling issues (from native call app) initially, calling from all 3rd party app (e.g. Messenger or Wechat) are not working: I can hear other side, while the other side can not hear me.
In addition to disabling VoLTE, I also changed the 'preferred network type' (see posting from author 'fiumaxx' on nokia's user forum, search there using android-10-after-update-on-nokia-7-1 as search string). I changed it to LTE/CDMA which works well for me.
Normal call sound is back to normal but 3rd party calling still not working.
Click to expand...
Click to collapse
This worked for me:
Go to Settings/Apps and Notifications and then tap on where it says See All xx Apps. Scroll down until you see the Google app and tap on that. On the next screen you see, tap on Permissions and then tap on Microphone. A small window will pop up, and you must change the setting from Allow to Deny.
After changing this setting, Google Assistant won't work (no Hey Google), but the fix is persistent after reboots. This makes me think the real problem may be with the Google app. We'll see.
ikijibiki said:
This worked for me:
Go to Settings/Apps and Notifications and then tap on where it says See All xx Apps. Scroll down until you see the Google app and tap on that. On the next screen you see, tap on Permissions and then tap on Microphone. A small window will pop up, and you must change the setting from Allow to Deny.
After changing this setting, Google Assistant won't work (no Hey Google), but the fix is persistent after reboots. This makes me think the real problem may be with the Google app. We'll see.
Click to expand...
Click to collapse
Thank you so much for sharing! Works like a charm
Unfortunately denying microphone for the Google app did not work for me. I also noticed no one can hear me when making videos calls (Hangouts, Duo, Facebook messenger).
I then decided to factory reset, but did not help. Both VoLTE and video calling still not working.
Anyone else with video calling mic issues?
zhou68000 said:
I have TA-1085 running Android 10 that was pushed OTA on 12/25, while I do not have calling issues (from native call app) initially, calling from all 3rd party app (e.g. Messenger or Wechat) are not working: I can hear other side, while the other side can not hear me.
Click to expand...
Click to collapse
I had the same symptom on normal phone call (other side could not hear me). In my case, it was the Google Assistant not releasing the microphone, and here what worked: open the system settings, go to Google (service&preferences)/Account services/Search, Assistant&Voice/Voice/Voice Match. Them make sure Access With Voice Match is ticked off.
Or try opening settings, searching at the top for "Voice" and open "Voice Match", and tick off "Access with Voice Match".
ikijibiki said:
This worked for me:
Go to Settings/Apps and Notifications and then tap on where it says See All xx Apps. Scroll down until you see the Google app and tap on that. On the next screen you see, tap on Permissions and then tap on Microphone. A small window will pop up, and you must change the setting from Allow to Deny.
After changing this setting, Google Assistant won't work (no Hey Google), but the fix is persistent after reboots. This makes me think the real problem may be with the Google app. We'll see.
Click to expand...
Click to collapse
Confirm this recipe works for my TA-1085. Thanks much.
I solved my random voice problems (others can't hear me on Duo video call, duplex voice on the other side etc.) with the voice match assistant workaround until hopefully gets fixed in a next update. Don't know for sure if the thing is only on Nokia's side or Google app's as well on Android 10, since disabling Hey Google solves all issues
Will have to try/catch on future google app updates as well to find out
Sly_North said:
I had the same symptom on normal phone call (other side could not hear me). In my case, it was the Google Assistant not releasing the microphone, and here what worked: open the system settings, go to Google (service&preferences)/Account services/Search, Assistant&Voice/Voice/Voice Match. Them make sure Access With Voice Match is ticked off.
Or try opening settings, searching at the top for "Voice" and open "Voice Match", and tick off "Access with Voice Match".
Click to expand...
Click to collapse
Under "Voice Match" I don't see any "Access With Voice Match" setting. What I do see is "Hey Google," which says "Access your Assistant any time you say "Hey Google" when your screen is on." Perhaps this is what your mean?
I tried this solution and it works, too. I think it also has the advantage of not completely shutting down Assistant's access to the microphone. Just waking up Assistant by voice. Much less of a price. Thanks!
Has anyone heard anything about a real fix for this issue? I've gotten two Android updates since the upgrade to Android 10, but this issue has not been fixed yet.
After extensive talks and inside info on Nokia's community forums, seems like a Maintenance update (MR) is on the way for May, which they say fixes -among others- both voice bugs. That is, the echo on calls plus sound distortion in some games (e..g Monument Valley 2 for me)
Cross your fingers everyone for a quick release and confirmation of the fixes!
Today was the day at last....! MR update showed up rolling out globally and echo during calls plus crackling sounds in games are finally gone
Better late than never NOKIA
dbal said:
Today was the day at last....! MR update showed up rolling out globally and echo during calls plus crackling sounds in games are finally gone
Better late than never NOKIA
Click to expand...
Click to collapse
Yes, they seem to have fixed the voice call problems with Whatapp, Wechat, Hangouts and etc since the Android 10 update.