Description : Loud distortion on calls. You even notice it on the ring when doing outgoing calls.
I have it on vikingXrom. Even when doing a fresh install, full wipe... I make a call and it's there.
But people do also have it on RonenRom and I had it sometimes on Wanams.
Only some people have it.
What I already tried : flashing modem again, flashing other kernel... Distortion stayed. Who is also noticing this? And on which Rom?
For people having it, please respond with what ROM on what network and make a test with another sim from a friend on another(/same) carier.
----------------------
update 20121010:
For people having this problem. It seems a combination of some Roms with some Network carriers.
Problems :
Telenet(Belgium) / VIKINGxROM
Telenet(Belgium) / RonenRom
No Problem :
Telenet(Belgium) / Wanam
Telenet(Belgium) / checkRom
Proximus / VIKINGxROM
So note that when I put in another SIM from another carrier in vikings I have no problem.
Also, please give vikingxrom a try. It is the only JB rom I have tested that is real snappy and always fluent and fast!
Vikgin gave an update 7.3 with some changes in CSC, however without result for me.
------------
update 20121011:
Yesterday I tried with another SIM of a friend but also with the same carrier (Telenet)... Result : NO DISTORTION...
Ok, that was new. So what now? Was my SIM defective?
I went to the store to get another SIM. That was no problem.
Result. Still distortion. Very strange.
Now, are there any options I can set for my number???
Could this all be a network carrier problem? Special network settings the carrier is using that colides with settings in the roms?
Do you have any possibility to try another network carrier with your actual phone/rom? E.G. a prepaid card or trying national romaing?
huuub said:
Description : Loud distortion on calls. You even notice it on the ring when doing outgoing calls.
I have it on vikingXrom. Even when doing a fresh install, full wipe... I make a call and it's there.
But people do also have it on RonenRom and I had it sometimes on Wanams.
Only some people have it.
What I already tried : flashing modem again, flashing other kernel... Distortion stayed. Who is also noticing this? And on which Rom?
Click to expand...
Click to collapse
I am using the same rom but it is all good on my side. I think maybe it can be related with your operator or maybe fast dormancy stuff. Siyah kernel has fast dormancy switch on off, maybe you should try that
---------- Post added at 08:19 AM ---------- Previous post was at 08:16 AM ----------
as_usual150 said:
I am using the same rom but it is all good on my side. I think maybe it can be related with your operator or maybe fast dormancy stuff. Siyah kernel has fast dormancy switch on off, maybe you should try that
Click to expand...
Click to collapse
I find this page while I was searching maybe it could help
"Just a tip for those people who are experiencing bad quality. I recently ordered two Verizon Samsung Galaxy S3 phones (both had update stickers on their box which I'm guessing the software on the phone has been updated recently) both with the stock ROM. Specifically, my family and friends would complain about the call quality. They had a hard time hearing me. My voice would sound muffled and faint. There were also complaints about static. This would happen whether I was on the handset, headset, or speakerphone.
I tried a few things to fix the issue. I called Verizon. They tried refreshing the VLR on their end. I have no idea what that does but it didn't help me. I then looked on the Internet for any ideas. I tried disabling voice privacy (Phone > Call Settings > uncheck Voice Privacy) which seemed to help a little. I also tried disabling noise reduction when in handset mode (Phone > Call Settings > Additional Settings > uncheck noise reduction). That had no effect.
I then read on a web page that a factory reset was supposed to help. So I also did a factory reset (Menu > Settings > Back up and reset > Factory data reset). That did not work either.
However, I then wondered if the person who suggested a factory reset might have also implicitly expected me to clear the cache partition, too. I booted into recovery mode by simultaneously pressing on the up volume key, the home button, and the power button. In recovery mode, I then performed the following:
select "wipe cache partition"
select "wipe data/factory reset"
select "reboot system now"
After I did this, I believe the call quality improved immensely (at least that's what my friends and family are telling me). I wonder if I even had to do the factory reset - maybe all I needed to do was to clear the cache partition.
Hope this helps others who were in a panic because the call quality problem is a dealbreaker for me. If people can't hear me talking, then I would have returned my S3s. And I would have hated to do that since this phone is awesome - infinitely better than my craptastic Samsung Moment... Some people may already know this solution, but I certainly didn't and I'm certainly not an Android expert. "
Thanks but since I already did a lot of full wipes and reinstalls, it did not help...
I also switched to another SIM. The same problem .
edit: I switched to another SIM but the same carrier. When I switched to another SIM with another Carrier the distortion was gone!!!! (explained in later posts)
as_usual150 said:
I am using the same rom but it is all good on my side. I think maybe it can be related with your operator or maybe fast dormancy stuff. Siyah kernel has fast dormancy switch on off, maybe you should try that
---------- Post added at 08:19 AM ---------- Previous post was at 08:16 AM ----------
I find this page while I was searching maybe it could help
"Just a tip for those people who are experiencing bad quality. I recently ordered two Verizon Samsung Galaxy S3 phones (both had update stickers on their box which I'm guessing the software on the phone has been updated recently) both with the stock ROM. Specifically, my family and friends would complain about the call quality. They had a hard time hearing me. My voice would sound muffled and faint. There were also complaints about static. This would happen whether I was on the handset, headset, or speakerphone.
I tried a few things to fix the issue. I called Verizon. They tried refreshing the VLR on their end. I have no idea what that does but it didn't help me. I then looked on the Internet for any ideas. I tried disabling voice privacy (Phone > Call Settings > uncheck Voice Privacy) which seemed to help a little. I also tried disabling noise reduction when in handset mode (Phone > Call Settings > Additional Settings > uncheck noise reduction). That had no effect.
I then read on a web page that a factory reset was supposed to help. So I also did a factory reset (Menu > Settings > Back up and reset > Factory data reset). That did not work either.
However, I then wondered if the person who suggested a factory reset might have also implicitly expected me to clear the cache partition, too. I booted into recovery mode by simultaneously pressing on the up volume key, the home button, and the power button. In recovery mode, I then performed the following:
select "wipe cache partition"
select "wipe data/factory reset"
select "reboot system now"
After I did this, I believe the call quality improved immensely (at least that's what my friends and family are telling me). I wonder if I even had to do the factory reset - maybe all I needed to do was to clear the cache partition.
Hope this helps others who were in a panic because the call quality problem is a dealbreaker for me. If people can't hear me talking, then I would have returned my S3s. And I would have hated to do that since this phone is awesome - infinitely better than my craptastic Samsung Moment... Some people may already know this solution, but I certainly didn't and I'm certainly not an Android expert. "
Click to expand...
Click to collapse
huuub said:
Thanks but since I already did a lot of full wipes and reinstalls, it did not help...
I also switched to another SIM. The same problem .
Click to expand...
Click to collapse
Have you tried playing around with the call quality settings. Go to dialer and then go to call settings > additional settings , and try enabling/disabling noise suppression and see if there is a difference. By default, it is enabled.
yes I did, didn't help either...
did a fresh install of InsertCoin, do not have distortion...
Is the distortion also there when you call using wifi?
Sent from my GT-I9300 using xda app-developers app
I am not using wifi to call... (I guess you mean IP calls)
By google talk are calls ok...
huuub said:
yes I did, didn't help either...
Click to expand...
Click to collapse
I noticed something though, there has to be in call eq settings in call settings. But there is not after I flash this rom
I think it would be a messy but helpfull thing that a dev try's to comapre two roms (viking and one that doesn't have the issue).
There MUST be any difference. We all know the vikingrom is stripped down heavily, perhaps there has been removed a system app which now causes the issue?!
Hi perhapps you could try to push and replace those apk in V7.zip
http://dl.free.fr/f4kjkchfb
you will loose call recording mod but i have some probleme too i did that and all its ok now .
perhaps its work for you too :fingers-crossed:
Aaarrggh, put them in the 7.2 update, installed, wiped cache/dalvik...
Retried... Again distortion
Getting tired of this....
F3nr1s said:
Hi perhapps you could try to push and replace those apk in V7.zip
http://dl.free.fr/f4kjkchfb
you will loose call recording mod but i have some probleme too i did that and all its ok now .
perhaps its work for you too :fingers-crossed:
Click to expand...
Click to collapse
Mika83AC said:
I think it would be a messy but helpfull thing that a dev try's to comapre two roms (viking and one that doesn't have the issue).
There MUST be any difference. We all know the vikingrom is stripped down heavily, perhaps there has been removed a system app which now causes the issue?!
Click to expand...
Click to collapse
Nah I don't cut out stuff which I don't know function off, but I never say never. Plus since it doesnt happen to all users I'm very confused :cyclops:
Still researching about the problem...
v6 and v7 is pretty identical so its hard for me to solve since I didn't really change much other than rebasing to XXDLIB.
schoolsux said:
Nah I don't cut out stuff which I don't know function off, but I never say never. Plus since it doesnt happen to all users I'm very confused :cyclops:
Still researching about the problem...
v6 and v7 is pretty identical so its hard for me to solve since I didn't really change much other than rebasing to XXDLIB.
Click to expand...
Click to collapse
Yes, you're right. It can't be a general app issue, because then every user should have the issue.
In any case it must be related to the phone itself (different hw release then the other users?) or the carrier network settings. But as huub said, he already tried changing the sim to a different carrier ...
Going to try another SIM with an other telephone company later!
However keep in mind, a clean install of other ROM's doesn't give me the issue neither.
App related : no, since I didn't install anything
Phone related HW : no, I should have it always no matter what ROM
Rom related: seems like it, but it must be "a combination" of things, since most people don't have the issue
For the moment I am back on ICS and I must say it still has the best battery life
- But I miss the NOTE2 gallery the most -
Ok... I tried with another SIM on the Proximus network in Belgium and guess what...
It did NOT distort!
So on this ROM I have distortion with Telenet network and not with Proximus network.
But what now?
huuub said:
Ok... I tried with another SIM on the Proximus network in Belgium and guess what...
It dit NOT distort!
So on this ROM I have distortion with Telenet network and not with Proximus network.
But what now?
Click to expand...
Click to collapse
Ha, strike :highfive:
Ok, i think now we (or schoolsux) need to have a look at the csc's used in the rom? As far as i know, this is the carrier related stuff, but i'm not realy sure about this.
We could need an expert now.
So I found another ROM where I have the problem :
[ROM][XXDLIB][30.09] HyperLight v0.8 - stripped & tweaked [3 Flavours]
I used the Compatible version.
Maybe GETRIL could be part of the solution.
This is showing in mine :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Could a few people post theirs?
(it is a free app in the appstore)
Screenshot : HOME + POWER for few seconds
Related
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?
Hi,
[I'm posting here because I'm new at xda-developers forum and it won't let me post into the development threads.]
Yesterday I installed a new Beanstalk ROM (with Android 4.4.2) on my Samsung Galaxy S2 (GT-I9100). Everything worked well from the beginning except... that incoming calls could not be answered. The phone rings, and a rectangle shows at the bottom of the screen, without the number / picture of the caller (even though it knows the caller because it's in the contacts). It seems like the screen stops responding the moment the phone begins to ring. Also, there are no "Accept / Reject" buttons to drag the rectangle to. The only thing I can do is press the Power button to lock the phone, but it doesn't help - pressing it again to wake the phone brings me back to the same state - phone still rings, but nothing can be done.
A google search revealed that the same problem existed on a Nexus 5 device, and Google suggested to do a factory reset. So I did... and after that, I could answer incoming calls. But a few hours have passed, and I made a couple of reboots (manually), and again - can't answer incoming calls. Does anyone have a solution?
There was another small issue, which is much less important - after logging in to my gmail account, the apps weren't automatically downloaded, as with other ROMs.
Thanks,
Shlomy
sreinst1 said:
Hi,
[I'm posting here because I'm new at xda-developers forum and it won't let me post into the development threads.]
Yesterday I installed a new Beanstalk ROM (with Android 4.4.2) on my Samsung Galaxy S2 (GT-I9100). Everything worked well from the beginning except... that incoming calls could not be answered. The phone rings, and a rectangle shows at the bottom of the screen, without the number / picture of the caller (even though it knows the caller because it's in the contacts). It seems like the screen stops responding the moment the phone begins to ring. Also, there are no "Accept / Reject" buttons to drag the rectangle to. The only thing I can do is press the Power button to lock the phone, but it doesn't help - pressing it again to wake the phone brings me back to the same state - phone still rings, but nothing can be done.
A google search revealed that the same problem existed on a Nexus 5 device, and Google suggested to do a factory reset. So I did... and after that, I could answer incoming calls. But a few hours have passed, and I made a couple of reboots (manually), and again - can't answer incoming calls. Does anyone have a solution?
There was another small issue, which is much less important - after logging in to my gmail account, the apps weren't automatically downloaded, as with other ROMs.
Thanks,
Shlomy
Click to expand...
Click to collapse
1) reboot to recovery and then do wipe cache and Dalvik cache and then reboot the phone and see
2) Also open the phone app and go to it settings (press the menu key for the same) and once there Scroll down to 'Interface' heading and there uncheck 'Non Intrusive' and see
Sun90 said:
1) reboot to recovery and then do wipe cache and Dalvik cache and then reboot the phone and see
2) Also open the phone app and go to it settings (press the menu key for the same) and once there Scroll down to 'Interface' heading and there uncheck 'Non Intrusive' and see
Click to expand...
Click to collapse
Thanks a lot for the quick answer! Is this supposed to solve the problem entirely? The factory reset solved it for limited time...
Can you also please provide a link that explains this?
sreinst1 said:
Thanks a lot for the quick answer! Is this supposed to solve the problem entirely? The factory reset solved it for limited time...
Can you also please provide a link that explains this?
Click to expand...
Click to collapse
There is no link ma8, ALways a wipe cache/Dalvik will solve many issue's for u, give it a try and see.
Also u can check other KK based roms like 'Slimkat' or 'Omni' for instance and see
Sun90 said:
There is no link ma8, ALways a wipe cache/Dalvik will solve many issue's for u, give it a try and see.
Also u can check other KK based roms like 'Slimkat' or 'Omni' for instance and see
Click to expand...
Click to collapse
Well... I did (1), and it didn't solve the issue. I'm not sure what it was good for - when I install a new ROM, does it come with a cache? I thought all these custom ROMs come with no cache (and Dalvik cache) at all and these are filled-up when booting the ROM for the first time.
I also did (2), and this solved the issue indeed (giving up the non-intrusive interface which I don't need anyway). Thanks a lot for your replies!
I don't like to check other KK ROMs as long as this one is okay. I think the ROM is really great.
Thanks again!
Shlomy
sreinst1 said:
Well... I did (1), and it didn't solve the issue. I'm not sure what it was good for - when I install a new ROM, does it come with a cache? I thought all these custom ROMs come with no cache (and Dalvik cache) at all and these are filled-up when booting the ROM for the first time.
I also did (2), and this solved the issue indeed (giving up the non-intrusive interface which I don't need anyway). Thanks a lot for your replies!
I don't like to check other KK ROMs as long as this one is okay. I think the ROM is really great.
Thanks again!
Shlomy
Click to expand...
Click to collapse
Although (2) solved the main issue - I can now accept or reject calls - I am still interested to know why the "non-intrusive" dialog doesn't work for me, while it works for others using the same ROM on the same device. I see the incoming call card, with an icon (that should show the picture of the caller), but nothing else in this card, it is just white with no buttons.
Hi guys
I have a really annoying issue with my galaxy s2. It seems to be stuck on emergency calls only and will not let me send texts, call people, etc. I have tried everything- restore stock firmware, factory reset, repair apps and nothing has worked. My IMEI number is not null and it matches the one on my phones box. I dont know what else to try so any help would be very much appreciated
Carrier-side I reckon. Call them to ensure there's nothing at their end responsible. Given what you're already tried, and given your IMEI hasn't gone away, seems a bit curious you'd lose connectivity all of a sudden like that (unless it's a hardware issue).
MistahBungle said:
Carrier-side I reckon. Call them to ensure there's nothing at their end responsible. Given what you're already tried, and given your IMEI hasn't gone away, seems a bit curious you'd lose connectivity all of a sudden like that (unless it's a hardware issue).
Click to expand...
Click to collapse
I checked and there is no carrier issue and it works fine in other phones
In case and if you're using stock firmware:
1. Boot into Recovery Mode
2. Perform a full factory reset by wiping /data partition.
3. Reboot and see if it fixes the problem
However, try and use a custom firmware in case your OS is causing the problem. When it comes to me, the hardware doesn't have to be necessarily damaged or affected in such a case since the phone app is on emergency calls, so it's fully accessible. I recommend checking the app settings again (maybe tapped on something accidently), but nevertheless, I prefer trying a custom Rom to verify that it's a software issue, or simply flash your stock firmware through ODIN to fix any issue if persisted.
I'm having issues with my calls ever since I changed my S3 configuration (ROM, kernel, apps, framework…).
On most of them, I get a soft reboot at the start or in the middle of the conversation.
I've tried changing the modem but there were no results.
How can I diagnose the problem?
Thanks.
P.D: You can see my config on my signature
It just happened again. I have read the logs but I can't figure out the problem.
Any help?
Thanks.
eXtremeDevil said:
It just happened again. I have read the logs but I can't figure out the problem.
Any help?
Thanks.
Click to expand...
Click to collapse
If you have overclocked then lower the frequency I had the same issue on another device and doing so resolved it
We'll see if that's the issue. Thanks for the tip, I'll keep you guys informed.
Have you tried changing kernels, it happened to me once from a custom kernel
Well, I'm very happy with my kernel, but if the problem persist I will consider it.
Thanks!
The problem persists. May be that I installed BusyBox from Play Store when I had it already from the ROM & Kernel?
Yeah most likely thats the problem, try flashing your rom again
Sent from my SM-G900F using XDA Free mobile app
I have uninstalled BusyBox, reflashed the ROM and changed the kernel. I'll keep you guys informed.
So far so good, the system was even better (a lot more stable) and no call reboots. But just now I've had the first one. I guess the number of call reboots have decreased (I'm not sure because it is a ramdom thing) and that's good but, again, any way of diagnose the problem?
Thanks!
EDIT
I often lose my APN settings and I had to reboot the device (a soft reboot is valid as well), may that problem be linked to the other?
I've performed a full wipe and started all over again. Let's see if this time everything works well...
Unbelievable. I did every single thing from scratch and the phone was perfect. Today I make my first call after all the mess and configuration and AGAIN, a soft reboot.
I'm 100% out of ideas here. Is there something, ANYTHING I can do to confront the problem? Some kind of log or monitoring action so I can know a litte bit more about this??
Please, I'm REALLY desperate right now…
I've installed the app SIM Card Manager and the phone field was unkwown. I rebooted and my phone showed up correctly. Maybe the app's fault or my SIM is half-broken? Or is it the phone lector?
Tomorrow I'm changing my SIM for a new one and let's see what happens, really out of ideas right now...
I think I found the cause of the problem.
This modification along with the Xposed app StatusbarVolume seems to cause the reboot when I try to change the volume when in a call.
I can't be 100% sure this is the faliure scenario because the bug is a little bit random, but I am 99% sure anyway.
EDIT
Not sure if the cause is the volume unlink, or the Statusbarvolume overlay failing to show up in call if it has never been invoked outside of a call before since the phone startup. May be a mix of the two things.
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.