Related
Hello everyone,
Since getting my SX56 last week and I've upgraded the ROM and the Radio Stack...
Upgraded the ROM to PW10A1-ENG-4.00.05
and the Radio Stack to RA.20.10
I'm using this SX56 on Rogers AT&T in Canada (Mississauga) yet I cannot seem to get any good signal strength for my phone. It's always displaying the antenna image with only the smallest strength bar beside it and most often there are NO strength bars appearing.
Any suggestions or help would be appreciated.
Some times the PPC indicates weak signal, but the point is: do you face problems making or receiving phone calls ?
Yes. I do experience problems with dropped calls, poor reception and broken conversations. There have even been a number of times when it was unable to complete a call.
The problem here, is that this SX56 is new to me, so I'm not sure what the expected performance level should be, because I haven't had anything to compare it to.
My previous Motorola T720 was experiencing similar issues with poor reception and broken conversations, but not to this extent.
I think that the antennas seem to just do a poor job. I can sit in my office with 2 phones side by side (a nokia, and the sx56) and the nokia shows a half signal and has no problems receiving or making calls. The sx56 on the other hand either has 1 or no bars and goes into random searches for signal. I love the device, but their antenna is seriously lacking
I am new here and dont know where to post this. My question is if anyone has the problem with when someone calls the phone lights up but then only rings the last 5 seconds the same with it just on viberate so I barley have enough time to answer the phone. I have had this problem on three roms kaos v37, tazz vinilla v20 and tazz sense 2.2.1
Sent from my Eris using XDA App
Eris dialer lag... my only "solution" to this problem that i've run across...
changed your default "low" clock to 480... (most ROM's around here will probably default to 245)...
however, that will tend to lead to worse battery life. if you are using a Sense-based ROM, it will probably be worse.
maybe someone else has a better solution
To add to that, even with the minimum at 480, this still does happen.
Take note at how long it takes the phone to really get into the ring, with the ringtone and all, if you're, say, web browsing with your phone, or using The Weather Channel App, or YouTube.
The phone has slow internal memory (the processor is not the bottleneck at 528mhz, usually, and definitely not overclocked at 710mhz+ like most ROMs are) and the processor DOES ramp up its speed pretty quickly when a ring comes in.
Neither here nor there, there's not a WHOLE lot you can do to fix it. It's an Eris thing. HTC Hero has the same situation. It's my experience that SenseUI 2.1 ROMs come to a full, answerable ring faster than Froyo ROMs, but I haven't seen if that changes with the newer kernels and ROMs around.
Call Verizon and have them extend your ring from 30 seconds to 40+ seconds. I have mine at 40 seconds (8 rings) instead of 30 (default - 6 rings), and that extra 2 rings makes it so I virtually never miss a phone call.
I highly recommend that. Works perfectly.
You could also (with a SenseUI or Stock ROM) reduce your Slot Cycle Index.
Dial ##778 (call)
Edit
Pw: 000000
Modem
Slot Cycle Index.
Stock, the slot cycle index is at 2, which means your phone 'pages' the tower for new calls/texts/voicemails every 5.12 seconds. So in other words, it could be up to 5.11+ seconds that someone else is calling you, before your phone even pages the tower and KNOWS that someone's calling you. So they easily could be on the second ring before your phone 'sees' the ring. Then, your phone has to react. Cut data connection. Pause whatever process it's in the middle of. Free up some memory if necessary. Pull up the 'answer' screen... etc.
The point is, that by putting your Slot Cycle index at 1, you're cutting that 5.12 seconds down to 2.56 seconds. If you put it at 0, you're cutting that time to 1.28 seconds.
Having a lower Slot Cycle Index drains more battery (somewhat notciably at 0, but 1 is a good compromise), but your phone will ring faster (earlier in the call) and you will be less likely to miss it.
If you change the value to 1 or 0 or something, after you change it push
Menu >>
Committ modifications
(your phone will reboot to make the change.)
I put my gf's phone on 0 because she's on Cricket - and Cricket only gives you 4 rings (20 seconds) to answer the call. So that thing has to ring FAST, or you miss the call. With Verizon, I have mine at 40 seconds, so I just leave my slot cycle at 2, and it works just fine.
Isn't it kind of funny how all those old dumb phones ring just about instantly (as soon as they page the tower), and these smart phones have all this process to go through just to answer? Kind of silly, a little bit.
But a necessary 'evil' to have a fully functional computer in your hand, IMHO.
pkopalek said:
Call Verizon and have them extend your ring from 30 seconds to 40+ seconds. I have mine at 40 seconds (8 rings) instead of 30 (default - 6 rings), and that extra 2 rings makes it so I virtually never miss a phone call.
I highly recommend that. Works perfectly.
You could also (with a SenseUI or Stock ROM) reduce your Slot Cycle Index.
Dial ##778 (call)
Edit
Pw: 000000
Modem
Slot Cycle Index.
Stock, the slot cycle index is at 2, which means your phone 'pages' the tower for new calls/texts/voicemails every 5.12 seconds. So in other words, it could be up to 5.11+ seconds that someone else is calling you, before your phone even pages the tower and KNOWS that someone's calling you. So they easily could be on the second ring before your phone 'sees' the ring. Then, your phone has to react. Cut data connection. Pause whatever process it's in the middle of. Free up some memory if necessary. Pull up the 'answer' screen... etc.
The point is, that by putting your Slot Cycle index at 1, you're cutting that 5.12 seconds down to 2.56 seconds. If you put it at 0, you're cutting that time to 1.28 seconds.
Having a lower Slot Cycle Index drains more battery (somewhat notciably at 0, but 1 is a good compromise), but your phone will ring faster (earlier in the call) and you will be less likely to miss it.
If you change the value to 1 or 0 or something, after you change it push
Menu >>
Committ modifications
(your phone will reboot to make the change.)
I put my gf's phone on 0 because she's on Cricket - and Cricket only gives you 4 rings (20 seconds) to answer the call. So that thing has to ring FAST, or you miss the call. With Verizon, I have mine at 40 seconds, so I just leave my slot cycle at 2, and it works just fine.
Isn't it kind of funny how all those old dumb phones ring just about instantly (as soon as they page the tower), and these smart phones have all this process to go through just to answer? Kind of silly, a little bit.
But a necessary 'evil' to have a fully functional computer in your hand, IMHO.
Click to expand...
Click to collapse
Sorry to bump an old thread, but this issue has been plaguing me for some time now. I have my cpu set at 480MHz min, 604MHz max & my phone still seems to lag when there is an incoming call. The screen takes a long time to turn on, and only rings a few times before I miss the call. I am currently running Condemned v17 S2H, but have experienced this issue on other roms as well. Is there any way I can perform the ##778 procedure on a non-stock/non-sense ROM? If not, are there any other fixes out there?
Edit: This doesn't happen to me on every single call. Sometimes the phone seems to respond quicker than others. However, when it does occur, it is usually two rings or so (tested from a landline at work) before I hear my ringtone & the screen turns on.
CondemnedSoul may have found a solution to this issue. See his post here
WARNING: ANYTHING YOU DO TO THE BUILD PROP IS DONE AT YOUR OWN RISK!! IT IS NOT RECOMMENDED TO MODIFY THIS FILE! DO NOT ATTEMPT THIS UNLESS YOU ARE SURE YOU KNOW WHAT YOU'RE DOING!!
With that said, however, I made the change to the build prop that he specified. I had a chance to make a few test calls before I left work, and it did seem to improve my phone's response speed. However, it was only a small sample size. I should be able to give a better answer in a few days after further testing, but for now, I think we are good! I'll keep everyone posted.
PillClinton said:
CondemnedSoul may have found a solution to this issue. See his post here
WARNING: ANYTHING YOU DO TO THE BUILD PROP IS DONE AT YOUR OWN RISK!! IT IS NOT RECOMMENDED TO MODIFY THIS FILE! DO NOT ATTEMPT THIS UNLESS YOU ARE SURE YOU KNOW WHAT YOU'RE DOING!!
With that said, however, I made the change to the build prop that he specified. I had a chance to make a few test calls before I left work, and it did seem to improve my phone's response speed. However, it was only a small sample size. I should be able to give a better answer in a few days after further testing, but for now, I think we are good! I'll keep everyone posted.
Click to expand...
Click to collapse
Based on what I've seen to this point, it seems that there is still some lag on the first phone call received after a reboot. However, every subsequent call after that has been much quicker to respond. Overall, a definite improvement on my phone. If anything changes, I'll let you know.
For another possible solution, check this thread here & the original thread from the Samsung Galaxy Ace S5830 Development Forum.
I used the above link yesterday and can't be happier. Seems to have made things smoother and rings much snappier...
Had the same problem and it was mostly due to the cpu being underclocked. moving it to 480 helped but still wasn't a fix.
there was a post, looking for it now, in the mod section about a script that would reduce the ringer delay. I installed that and my phone rings on my end after/during the second ring on the other end.
Problem is sometimes after 30 seconds someone is calling me I can't hear him from call speaker. When I switch to back speaker I can hear him. Sometimes is always after 30 seconds, sometimes I can't hear anything from beginning of call. Usually I can hear a whisper, but it's like 2 times more quiet than minimum volume.
Is this a hardware? Software?
I back to EFSv1 (I think), problem is still here
I upgread to newset rom problem is still here
I do not know is this a hardware or software problem but this happen suddenly, I think after Installing CM or 4.2 beta (I was testing some rom's). I think this happen after I install League of Shadows but I don't think this is a game fault since I do not this game, clean my phone and problem is still here. Sometimes is everything fine until I play some game for longer time.
Maybe it's something with connector from call speaker, should I tear down (this no problem to me)? My phone is on warranty
So over the past month or so I have noticed that randomly people cannot hear me unless I have my phone on speaker. It does not do it every time I make a call, or receive. I honestly am not sure if it has happened when I initiate the call, but I know it does at times when I receive. It probably happens 25 to 40 percent of the time (I don't make a lot of calls with my personal cell so it's hard to tell).
I've had this phone for about 3 months (Asurion warranty replacement).
Any ideas of what I should check/try?
twiz0r said:
So over the past month or so I have noticed that randomly people cannot hear me unless I have my phone on speaker. It does not do it every time I make a call, or receive. I honestly am not sure if it has happened when I initiate the call, but I know it does at times when I receive. It probably happens 25 to 40 percent of the time (I don't make a lot of calls with my personal cell so it's hard to tell).
I've had this phone for about 3 months (Asurion warranty replacement).
Any ideas of what I should check/try?
Click to expand...
Click to collapse
Try cleaning your proximity sensor--I had a similar issue where the person on the other end would randomly not be able to hear me when I was talking, and I'm pretty sure this is it. I had a ton of dust under here.
https://www.youtube.com/watch?v=JteGDhl-oXQ
Either 1 of 2 things is going on with your s4. I've seen several of them exhibit this exact same issue. Either your microphone is going bad which is very easy to replace since it is on a flex cable along with the charge port and is a simple modular piece, or your audio chip is failing. I have seen several s4s that sometimes will have no speaker or microphone while in a call and it is due to that audio chip. Also saw it on several s3s. If your audio chip is failing, one way to fix it without replacing your logic board is to take the logic board out and heat that audio chip to 350-375 degrees. I have done this to about a dozen s4s and 10 of them worked 100% after.
When you call granny, does she keep saying "Huh?! Wut?!" or does the conversation flow pretty well? Rate this thread to express how you feel about the Asus ZenFone Max Pro M1's call quality. A higher rating indicates that calls are clear and crisp, and that regardless of background noise, you can hear the other party clearly (and with ample volume) and they can hear you.
Then, drop a comment if you have anything to add!
frequent disconnections and loss of network
Did not expected this low quality network reception, also the phone looks buggy. you don't receive call many times, and you only realize this when other person informs you. need to restart to get it back. happened more that 3-4 times in 10 days of usages.
Sometimes i Can't hear what my girlfriend says. Her phone is good as I known. Any mod or fix to get over this problem
Yes same here call quality is not good many time other person cannot hear me properly
No problem at all! Indeed i have a very good quality audio in call. Which variant do you have? There are 2 on the asus site, A and B. I suppose mine is A version. On the box i have "4A-Phone" wrote on, and the A version is the only with lte band 20, necessary in Italy.
Yeah it happens sometimes with me too.
I am on stock v326 on 6gb version.
I tried holding where the mic can get sound exposure but what worked was kind of silly.
Just blow mildly into the mouthpiece and suck out mildly. The issue gets resolved. Earpiece too.
Whenever i find it happening for the earpiece and mouthpiece, I do this and surprisingly it works.
Maybe it will work for you.
Intially i thought i was covering the mic with my finger or due to the case that we put on.
Can't do anything for the network reception part unless Asus solves that part with better firmware. Wifi connectivity in long range especially is weird compared to flagships (obviously) but also to RMN5 pro and RN4 (both on miui though).
Maybe our software isn't optimized.
No issues at all for me
I do have the same issue. Everyone is complaining that they can't hear me well or the call quality is so poor or static...any way to fix this issue? I am starting to think I should have gone for some other phone choosing this Asus 6gb Zenfone max pro 1.
It's strange that I don't experience such low quality call. My phone is 3 GB version and can retrieve call all the time, though the sound I receive is a little bit crappy.
+1
aldeetropolis said:
It's strange that I don't experience such low quality call. My phone is 3 GB version and can retrieve call all the time, though the sound I receive is a little bit crappy.
Click to expand...
Click to collapse
Same here..
Any solutions on stock.. i tried to reduce volume and use.. better in that way.. (kernel tweaking may resolve?)
Prefer stock as i bought on 27/10/2018
Also updated to latest.
kamalsomani said:
Did not expected this low quality network reception, also the phone looks buggy. you don't receive call many times, and you only realize this when other person informs you. need to restart to get it back. happened more that 3-4 times in 10 days of usages.
Click to expand...
Click to collapse
I'm also use latest version stock ROM. But because I rarely make/receive call so I don't mind it anyway.
My wife and I have the same model of the ZenFone max plus 1, and my sound quality for calls is very bad. When I get a call they say they can barely hear me even on speaker. Hers on the other hand really good. What we both experience is we do not get calls all the time. People have to text to let us know they call at times because it goes straight to voice mail and have a long pause before the call connects.
Asus Zenfone Max Pro M1 supports EVS codec in Volte network, Jio does not have EVS and Airtel has EVS so call quality is excellent on stock ROM on all Indian networks except JIO.
Sent from my ASUS_X00TD using Tapatalk
I do not call so often, but every call has quality problems. Unfortunately, this is not a strong point of this phone.