Related
In LG Optimus One endcall function does not work, so do not work correctly call blocker apps. Can this be fixed in a custom ROM?
telephonyService.endCall() function BUG
Hi everyone!
I confirm that there is a bug with telephonyService.endCall() function which consist in passing call to this function to nowhere, thus making ALL call blocking software useless, because they can't discard unwanted calls.
Can anyone fix this problem? I believe in you, GURU, take a look on this problem please.
With respect and hope, Max.
I really think this topic deserves a bump. And a solution.
Same problem here. End call function simply doesn't do anything on this phone making call blockers completely useless. I tried all O1 roms and even the original rom with the latest update and still doesn't work. Every call blocker says that call was blocked while you are watching it ringing.
By the way until someone comes with a fix, i found a temporary solution which requires Tasker or Settings Profile application.
If you want to send the blocked number to the voicemail, simply program Tasker to switch to airplane mode on and off or if you want to do the pick up and hang up action program Tasker to accept the call first then switch to airplane mode on and off.
As you can tell it will disconnect you from your network temporarily but Tasker is quite fast doing it so you will be on again very quickly. Putting your phone into airplane mode will end the call very quickly which call blockers can't do for this phone right now. You can do all these with Settings Profile too with the same steps.
Until a software fix, any other ideas are more than welcome.
(Unknown and private number value for Tasker is 0).
I have had the same problem and confirmed with Tasker developer that this is bug in LG Optimus One. Airplane mode is good solution if you do not protect your sim card with pin code. Else, after airplane mode is switched on and off, you will be prompted to insert pin and until you do so, your phone will not be reachable
I would prefer different solution...
I think we need to ask the guru to fix this problem. I said two weeks ago with mik_os about this issue, he replied that he might look, if not occupied by another.
Bump
This is something that is important as we cannot handle unknown calls.
If anybody has some solution, it would be appreciated.
I'm working on that.
For now I'd found by debugging phone with adb that endcall function really do something, but it seems that at the wrong time:
[ 02-16 20:27:52.451 1589:0x635 D/PhoneInterfaceManager ]
[PhoneIntfMgr] CMD_END_CALL: no call to hang up
Click to expand...
Click to collapse
That message appeared two seconds after we got the call (it's a mystery what phone was doing during those 2 secs), but before the framework starts to search corresponding contact to the calling number.
May be we have to wait several seconds after we get the call to invoke the encall() function again?
I'm a starter with android and I have not so much time for that, but I'm now trying to write a little program that will invoke endcall() function any time a want to prove/disprove my theory.
If anyone had written such program already, you can share sources with me to let me test that condition, or try it yourself.
UPDATE:
I've just tested it: there is no matter when you invoke endcall() function, the result is the same "[PhoneIntfMgr] CMD_END_CALL: no call to hang up". So digging deeper.
Last information from Android sources (how it should be in Android and doesn't work on our phone):
method handleMessage(Message msg) of class MainThreadHandler in PhoneInterfaceManager.java doesn't call method hangup(CallManager cm) of class PhoneUtils in PhoneUtils.java
Digging deeper...
First of all, that's environment I have:
- LGP500 device )
- "void" custom firmware
As I mentioned before, method handleMessage(Message msg) of class MainThreadHandler in PhoneInterfaceManager.java doesn't call method hangup(CallManager cm) of class PhoneUtils in PhoneUtils.java.
To check what's wrong I tracked that method to Phone.apk in /system/app/ directory of "void" custom firmware, which was grabbed from original LGP500 2.2 firmware, unpacked it and dedexed classes.dex file from it. To my great surprise I've found that it really omits call to hangup method of PhoneUtils class and do many things, that doesn't cross with Android sources. So LG programmers did their own "Android" with their own bugs. I have to say that it omits call to hangup method only for GSM call, but it has to be done for CDMA calls well.
I'll try to build Phone.apk from Android sources. This may take a while (maybe a week or so). Or maybe I'll edit dex file and repack Phone.apk with a new one. We'll see when I finally get some sleep
FYI, there is another way to block calls by diverting some call numbers to voice-mail. This is built-in Android function. That could be done in your phonebook by selecting a contact, pressing menu button, selecting options and checking "Incoming calls, Send calls directly to voicemail" checkbox. This way works more quickly than any other methods, used in callblocker software. So blocked caller immediately hear busy tone. I'll dig in sources how it works and maybe will find a better way for callblocking software.
Sorry for my English.
Thanks for your efforts noteb. The main reason that I want this function to work is to hangup on unknown caller id using Tasker. I am using company phone and cannot change my number. Let me know if you need any help.
Sent from my LG-P500 using Tapatalk
vault1965 said:
Thanks for your efforts noteb. The main reason that I want this function to work is to hangup on unknown caller id using Tasker. I am using company phone and cannot change my number. Let me know if you need any help.
Sent from my LG-P500 using Tapatalk
Click to expand...
Click to collapse
Of course I need help. What kind of help can you offer? Do you know how to build Android on Ubuntu 10.10? I've read couple of articles about that, but still it would be great if somebody familiar with that can join that topic. I'm familiar with linux only in network services administration and a little with programming in couple of languages.
BTW, I've found another bug in our LG firmware - Skype (and another one program, that I can't remember name of) can't switch sound to speaker. Instead it always playing sound (I mean voice of person you're talking with) through loud speaker. And again I think the problem is somewhere in standard *.apk files, which are Android framework.
Had anybody tried gingerbread?
Had anybody tried gingerbread from that topic http://forum.xda-developers.com/showthread.php?t=909242 ? Does it solve the problem? I'm currently reading that topic when I have time (there are a lot of words not in my native language) to decide whether it worth to be deployed on my device. Because of that currently I had stopped further investigation to solve the problem on froyo.
If anybody has some experience with that gingerbread build, let us know please.
I have flashed my phone with mik's Cyanogen rom and end call is working fine using tasker cyanogen-only press hardware key. End call will not be available in 2.3 as Google has removed call api's (read more on Tasker forum).
vault1965 said:
I have flashed my phone with mik's Cyanogen rom and end call is working fine using tasker cyanogen-only press hardware key. End call will not be available in 2.3 as Google has removed call api's (read more on Tasker forum).
Click to expand...
Click to collapse
Hardware EndCall works on our froyo with key remap also. I was asking is it API "endcall" function working (you can test it with simple "CallFilter" program from the market)?
BTW, that API works fine on Nexus One recently upgraded to gingerbread. So information about removing call api's is a fake. Also I can refute that information as I saw this API's in gingerbread sources with my own eyes.
I can confirm the API endcall function works perfectly in 2.3. Using CM7 for the ls670/optimus s.
cigman said:
I can confirm the API endcall function works perfectly in 2.3. Using CM7 for the ls670/optimus s.
Click to expand...
Click to collapse
Thanks for information.
Is there a solution for froyo? Or the problem can be solved only with cyanogen? I really wanted to block unknown callers :/
Sent from my LG-P500 using XDA App
migueel said:
Is there a solution for froyo? Or the problem can be solved only with cyanogen? I really wanted to block unknown callers :/
Click to expand...
Click to collapse
Try Gingerbread at http://forum.xda-developers.com/showthread.php?t=909242
It has to solve the problem
Bought the Atrix last week and unlocked it with the help from the webshop as I'm in Belgium, no problem connecting to Mobistar wich is my provider and data connections works great. But I'm having real problems making phonecalls and recieving calls; the phone reboots or the dialer hangs and it looks like a call is going on when it's not, phone still works but flashing green in the notification area and it's impossible to hang up, need to reboot. This happens like 80% of the times I try to make a call. After a reboot it works fine to call and hang-up one or two times then it crashes again.
Also noted that my Dialer often runs twice in the Running Apps manager - is that normal??
Anyone having the same issues or know what to do, reinstall the Dialer app --> if so how? Is it a hardware or software problem??
A little more info: when I recieved the device it was in a sealed Atrix box but the phone was used and already had an active Blur account so I had to do a hard reset to be able to use it... --> was it returned 'cause of faulty dialer or radio... then resold to me... not nice if so...?
Tried to install dialer one app but it seems only to skin the original dialer...
It's a greate device and works great othervice but in the end it's still a phone... which should be able to make calls...
Help
Ive got an unlocked Atrix too and now in Germany, I have the same problem. Motorola should definitely look into this.
Here's a quick fix for it thou, (not permanent)....
1. type *#*#4636#*#* on the dialer
2. Chose Phone Information
3. Set preferred network to GSM only
Viola...its fixed
problem with this fix is that you wont be able to use your 3G network but the dialer should be working.
Thanks Nazrin (for both replies) !!
It sure did the trick, though no data access is not acceptable on a phone like this!!!
So this meens that all unlocked Atrix's in european GSM networks have the same problems? Haven't seen any others reporting this and there are quite a few in use I've noted in other forums.
Was thinking of trying to have mine replaced (which probably won't be easy and take long time...) but that won't change anything then??
We have to wait for the european version of Atrix rom I suppose??
Any others with the same problem??
No problems buddy, glad it worked..and i have to agree with you..this bug is unacceptable...it seems the phone just ***** up everytime it calls on utms (3g)...im sure there is more people with this problem...
Sent from my Supercharged MOTO ATX
I have the same problem
Hi guys, I have the same exact issue (I'm also in Belgium, on Mobistar). I'm somewhat glad to hear this is a generic issue, and not an issue with my specific phone. At least I can be fairly certain replacing it won't solve this issue then.
I made another post here before I came across this one, has a bit more info: we are seeing modem panics when using 3G + outbound call. I've also contacted Motorola support to no avail:
http://forum.xda-developers.com/showthread.php?t=1028771
You can also read there that I tried another operator, and it did not crash with that one (although 3G did disconnect).
Hopefully Motorola/Qualcomm will start to notice the bug when they release the phone globally, and release a fix.
Either that, or we all have phones from the same bad batch
This bug is really bad for users in europe....cant call on utms...
I really hope motorola takes this seriously cos if there's no fix via software updates then its moto gone for me
Guys, you are all on unlocked att atrix right? I do believe it is a simmiliar software glitch/bug/lock that you have porblems using it on non att networks as the problem with the wifi that it stops working for some of us (check the thread about it for more info). As all suggests there it is a config file problem, unfortunately i or anyone else doesnt know yet which one....
Yeah maybe..but funny thing is wifi is working without a glitch...will have to read that forum later...
Workaround options
So, since it seems we're not gonna get this fixed until there is a new radio/modem firmware available for flashing (and even then..), I've been looking for a workaround.
Found two potential applications that could do what we need: disable data completely when making an outgoing call, or switch to 2G:
- Sanity
- Superpower
I've tested the first (Sanity), and it does not work (fully). It does seem to disable data, but the bands aren't switched so our problem remains. I've contacted the developer here: http://tagliamonte.net/forum/thread-10.html. He seems to be very responsive, so given enough interest, I think he would add the functionality we require.
The second app I only came across today, and have not tried yet. It does not have a function to specifically switch bands when making an outgoing call, but it has a trigger for "Foreground application", so if we make that the dialer/contacts... Question remains if it will be able to do the switch.
Hopefully one of these will lead to a decent workaround for all of us!
Well done unknown...i will try these apps... but the real fix should be from moto...im always reading the net for anything that can solve this issue
reboots on incoming and outgoing calls
Same in Russia on Megafon network, I had to enter 4636 menu and use it as "GSM only". Even this does not fully solve problems, e.g. call forwarding does not show the new destination number while it does actually make the phone divert calls correctly.
My hope is that UK release will trigger new software version which will address this issue. ANYONE has news on this?
FIXED!
YAY! I just fixed this issue
What you need to do: flash the radio from this thread:
http://forum.xda-developers.com/showthread.php?t=1052914
You have to use RSD-lite, since sbf_flash will not work. Flash the 1.87 baseband and enjoy working HSPA (including unlocked upload speeds ^^)
Now I can finally appreciate this phone fully
Enjoy guys!
_unknown said:
YAY! I just fixed this issue
What you need to do: flash the radio from this thread:
http://forum.xda-developers.com/showthread.php?t=1052914
You have to use RSD-lite, since sbf_flash will not work. Flash the 1.87 baseband and enjoy working HSPA (including unlocked upload speeds ^^)
Now I can finally appreciate this phone fully
Enjoy guys!
Click to expand...
Click to collapse
Worked for me as well..brilliant!!!! its working here in germany.....but I wonder the telstra radio will work in my home country with frequencies of 900/2100
Motorola Atrix restart when placing a call
I just got the same exact Dialer problem now, but the flash radio file is gone* in the pointed post, and I don't know exactly how to flash the radio.
Someone can help me? I need the radio file and step by step instruction to how to flash it.
BTW my Atrix 4G works perfect for a year till this Dialer problem started past week.
I also use my phone as a full Linux computer when docked, and it works very fine.
Thanks
* The file was on megaupload, that was closed
No answer
Why I never got an answer of any post I did?
There is something wrong?
Eli
elijacob said:
I just got the same exact Dialer problem now, but the flash radio file is gone* in the pointed post, and I don't know exactly how to flash the radio.
Someone can help me? I need the radio file and step by step instruction to how to flash it.
BTW my Atrix 4G works perfect for a year till this Dialer problem started past week.
I also use my phone as a full Linux computer when docked, and it works very fine.
Thanks
* The file was on megaupload, that was closed
Click to expand...
Click to collapse
Forget about those ways
klingsurf said:
Bought the Atrix last week and unlocked it with the help from the webshop as I'm in Belgium, no problem connecting to Mobistar wich is my provider and data connections works great. But I'm having real problems making phonecalls and recieving calls; the phone reboots or the dialer hangs and it looks like a call is going on when it's not, phone still works but flashing green in the notification area and it's impossible to hang up, need to reboot. This happens like 80% of the times I try to make a call. After a reboot it works fine to call and hang-up one or two times then it crashes again.
Also noted that my Dialer often runs twice in the Running Apps manager - is that normal??
Anyone having the same issues or know what to do, reinstall the Dialer app --> if so how? Is it a hardware or software problem??
A little more info: when I recieved the device it was in a sealed Atrix box but the phone was used and already had an active Blur account so I had to do a hard reset to be able to use it... --> was it returned 'cause of faulty dialer or radio... then resold to me... not nice if so...?
Tried to install dialer one app but it seems only to skin the original dialer...
It's a greate device and works great othervice but in the end it's still a phone... which should be able to make calls...
Help
Click to expand...
Click to collapse
[Sorry for problem in speaking]
i had that problem too , im using CM13 with Marshmallow Version of android
So . the easy way is :
***** search "Default" in settings. then choose " System dialer" as Default ! just it ****
but if there is no search bar in your setting . try this patch:
Android 6 : Setting/Apps then click the setting icon on top(may be diffrent in your case) , then Click on "default ...." then choose " System dialer" as Default! :fingers-crossed:
but in some cases that it didnt work . they have to reinstall gapps .
Or in official Roms , reset will be usefull
any quastions?
I just received this tablet with 3g stick - i would use it also for voice call not in internet but through the sim because i had a full phone plan with voice and internet -
i know that other tablet like sam.... with a software patch had enabled voice function -
we have to wait for a software upgrade or there is an hardware problem ?
in this case there is another usb modem with this function ?
thanks for your attention
newmave said:
I just received this tablet with 3g stick - i would use it also for voice call not in internet but through the sim because i had a full phone plan with voice and internet -
i know that other tablet like sam.... with a software patch had enabled voice function -
we have to wait for a software upgrade or there is an hardware problem ?
in this case there is another usb modem with this function ?
thanks for your attention
Click to expand...
Click to collapse
Hi There,
As far as I know the Archos 3G Stick is lacking voice capability at an hardware level so that is a no go, It theoretically possible using a Patched Huawei Dongle, I got it to successfully connect a silent call when I was playing around with it, It could be just a case of wiring up the audio policies in Android or something vastly more complex, I didn't bother investigating further. You also need to patch your framework-res.apk to make the rom voice_capable, you can also make it sms_capable as well, this allows you to use the stock mms app for sending and receiving messages
You might want to do a search before posting, because this question has been asked before and there's a couple of development threads regarding it, One is linked from my signature.
Thanks
trevd said:
Hi There,
As far as I know the Archos 3G Stick is lacking voice capability at an hardware level so that is a no go, It theoretically possible using a Patched Huawei Dongle, I got it to successfully connect a silent call when I was playing around with it, It could be just a case of wiring up the audio policies in Android or something vastly more complex, I didn't bother investigating further. You also need to patch your framework-res.apk to make the rom voice_capable, you can also make it sms_capable as well, this allows you to use the stock mms app for sending and receiving messages
You might want to do a search before posting, because this question has been asked before and there's a couple of development threads regarding it, One is linked from my signature.
Thanks
Click to expand...
Click to collapse
Correct. Sim cards do not have the phone radio in them. Its the device itself. Therefore, other than using voip phone apps there is no way to make voice call on the tablets, besides my galaxy note.
Sent from my ARCHOS 80G9 using xda app-developers app
Can someone assist me in seeing if this phone has built in support for Work Profiles (required for Android for Work using Google's MDM)? Google has an app that will tell you if the phone supports Work Profiles. Trying to find a device that is dual sim, with LTE ability with either sim (obviously only one at a time), that also has support for Android for Work. The Zenfone 2 supports it, but only has LTE ability on one sim. The Zenfone 2 Laser has LTE on both sims, but doesn't support Work Profiles. I've discovered the P8 Lite does support it via the Marshmallow beta, but I'd rather get this device.
Google's app in the Play Store to use to test is: Test DPC. You would only need to proceed through the setup to where you either get a message saying the phone doesn't support work profiles, or stop at the place where the next step is "Encrypt." If you get to the latter place, the phone supports Work Profiles -- at this point you can just cancel out and no setup or changes will take place.
If you aren't familiar with Android for work: http://arstechnica.com/information-t...es-to-android/
Appreciate any help.
elessarelfstar said:
Can someone assist me in seeing if this phone has built in support for Work Profiles (required for Android for Work using Google's MDM)? Google has an app that will tell you if the phone supports Work Profiles. Trying to find a device that is dual sim, with LTE ability with either sim (obviously only one at a time), that also has support for Android for Work. The Zenfone 2 supports it, but only has LTE ability on one sim. The Zenfone 2 Laser has LTE on both sims, but doesn't support Work Profiles. I've discovered the P8 Lite does support it via the Marshmallow beta, but I'd rather get this device.
Google's app in the Play Store to use to test is: Test DPC. You would only need to proceed through the setup to where you either get a message saying the phone doesn't support work profiles, or stop at the place where the next step is "Encrypt." If you get to the latter place, the phone supports Work Profiles -- at this point you can just cancel out and no setup or changes will take place.
If you aren't familiar with Android for work: http://arstechnica.com/information-t...es-to-android/
Appreciate any help.
Click to expand...
Click to collapse
With the Test Dac app i can get to the encrypt stage on the Honor 5x US model
deadman96385 said:
With the Test Dac app i can get to the encrypt stage on the Honor 5x US model
Click to expand...
Click to collapse
Awesome. Really appreciate you taking the time to check that.
elessarelfstar said:
Can someone assist me in seeing if this phone has built in support for Work Profiles (required for Android for Work using Google's MDM)? Google has an app that will tell you if the phone supports Work Profiles. Trying to find a device that is dual sim, with LTE ability with either sim (obviously only one at a time), that also has support for Android for Work. The Zenfone 2 supports it, but only has LTE ability on one sim. The Zenfone 2 Laser has LTE on both sims, but doesn't support Work Profiles. I've discovered the P8 Lite does support it via the Marshmallow beta, but I'd rather get this device.
Google's app in the Play Store to use to test is: Test DPC. You would only need to proceed through the setup to where you either get a message saying the phone doesn't support work profiles, or stop at the place where the next step is "Encrypt." If you get to the latter place, the phone supports Work Profiles -- at this point you can just cancel out and no setup or changes will take place.
If you aren't familiar with Android for work: http://arstechnica.com/information-t...es-to-android/
Appreciate any help.
Click to expand...
Click to collapse
My device is encrypted. It went all the way through to the end with the badged Test DPC. Looks like everything works.
wimbet said:
My device is encrypted. It went all the way through to the end with the badged Test DPC. Looks like everything works.
Click to expand...
Click to collapse
Thanks so much for checking that on your phones. One more question -- if you have experience using dual sim on this phone, what is the behavior of when an MMS is send to the sim that is not set for LTE? Is it the normal behavior of getting an sms notification with download button (then pressing download, which makes to phone switch to the other sim)? If it works something like this, that will be all the info I need to make the decision to buy the Honor 5x
Again, appreciate you using your time to assist me.
elessarelfstar said:
Thanks so much for checking that on your phones. One more question -- if you have experience using dual sim on this phone, what is the behavior of when an MMS is send to the sim that is not set for LTE? Is it the normal behavior of getting an sms notification with download button (then pressing download, which makes to phone switch to the other sim)? If it works something like this, that will be all the info I need to make the decision to buy the Honor 5x
Again, appreciate you using your time to assist me.
Click to expand...
Click to collapse
Honor 5X supports dual standby, so you can receive calls and texts on both numbers.
The Dual SIM Management settings let you pick the primary card for 4G/3G, default mobile data, default calls/messages for 3rd party apps, and call forwarding settings.
Thanks. I've not used a Dual Standby devices before (or DSDA device for that matter). If an MMS (something that requires data) comes in on the line that I don't have data enabled for, does a notification still come through to let me know a MMS is waiting"? My understanding is that this is how it works on a DSDA device (Zenfone 2 Laser, for example), but want to make sure DSDS works similarly (apart from not being able to take calls on both sims at the same time).
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.