[Q] Phone App Doesn't Say "Busy" for Busy Calls - Nexus 4 Q&A, Help & Troubleshooting

I don't know if this is something about Jelly Bean or ParanoidAndroid (the rom) I'm using, but when I make a call and get a busy signal, instead of getting a message that says the line is busy (like I used to with Gingerbread on my Nexus One), the call just abrubtly terminates the second I place it and says " call ended." This makes it seem like there's something wrong with my network and the call didn't go through at all.
Is this how the phone app is supposed to work in Jelly Bean?

cb474 said:
I don't know if this is something about Jelly Bean or ParanoidAndroid (the rom) I'm using, but when I make a call and get a busy signal, instead of getting a message that says the line is busy (like I used to with Gingerbread on my Nexus One), the call just abrubtly terminates the second I place it and says " call ended." This makes it seem like there's something wrong with my network and the call didn't go through at all.
Is this how the phone app is supposed to work in Jelly Bean?
Click to expand...
Click to collapse
I have the same thing with the Nexus 4 on 4.2.2. Tested it with Galaxy Nexus with 4.2.2 and it worked properly, so I think this is an issue with the Nexus 4.

Tomaxda said:
I have the same thing with the Nexus 4 on 4.2.2. Tested it with Galaxy Nexus with 4.2.2 and it worked properly, so I think this is an issue with the Nexus 4.
Click to expand...
Click to collapse
Are you using stock Jelly Bean or a custom rom? Just trying to figure out if this issue is introduced by Paranoid Android or is part of AOSP.

cb474 said:
Are you using stock Jelly Bean or a custom rom? Just trying to figure out if this issue is introduced by Paranoid Android or is part of AOSP.
Click to expand...
Click to collapse
I'm using stock JB, so I think it is part of AOSP.

Tomaxda said:
I'm using stock JB, so I think it is part of AOSP.
Click to expand...
Click to collapse
Thank. It's funny that this is a hardware specific problem, since you don't see it on the galaxy nexus.

cb474 said:
Thank. It's funny that this is a hardware specific problem, since you don't see it on the galaxy nexus.
Click to expand...
Click to collapse
Well guess what guys, android 4.4 on a stock Nexus 4.... no call busy when you call someone, just disconnects "Call Ended"
Absolute fail ever since launch!!!

istiaquechoudhury said:
Well guess what guys, android 4.4 on a stock Nexus 4.... no call busy when you call someone, just disconnects "Call Ended"
Absolute fail ever since launch!!!
Click to expand...
Click to collapse
Thanks for the info. It's weird that such a basic and simple bug can persist for so long. I guess calling is just irrelevant on phones these days.

UK nexus 4 16gb on the latest 4.4.2 sw , still no busy notification

I recently switched from PA to Cyanogen 11 (KitKat), but still have this problem. If I call someone who is on the phone, I do not get a busy tone and I do not see the "busy" message on the screen. Instead the call terminates and I get a messages saying the call ended. This is confusing, because there's no way to tell that the call didn't just drop or fail to complete, rather than that the line you're calling is busy.
I see people mentioning in the Google forums that this problem exists on stock Android and even in Lollipop.
Anyone know of a solution? When I first got the Nexus 4 I did not have this issue.

Related

Call Receiving Delay Poll

As the call receiving delay bug (the caller cannot hear you for about 3 sec. after one has answered the call) is a common problem it seems, I am wondering how many people actually have this problem and with which configuration.
I didn't have this problem until I upgraded to 4.2.2 .
I am now on CFX 12.5 with franco.kernel 86 (4.2.2). As I said I didn't have the problem on CFX 11 with franco.kernel 72 (4.2.1).
Please feel free to answer the poll and comment on anything which comes to mind.
!EDIT!: Please everybody post their configuration in your posts.
I have this problem since day 1, for me it's not a 4.2.2 issue
I don't have this issue, neither on 4.2.1 or on 4.2.2.
I think one of the earlier pa builds had it fixed already
Sent from my Nexus 4 using Tapatalk 2
I had this on Galaxy S3 three months ago and then on the Iphone 5. I think its Att bug, because right now on Tmobile I do not have it
moldovanos said:
I had this on Galaxy S3 three months ago and then on the Iphone 5. I think its Att bug, because right now on Tmobile I do not have it
Click to expand...
Click to collapse
I don't think so lol, I'm from Ecuador and have it
AW: Call Receiving Delay Poll
Just flashed Stock 4.2.2 and it seems that the delay bug is gone. Will make some other tests and tell my findings.
Sent from my Nexus 4 using xda app-developers app
rikmer said:
Just flashed Stock 4.2.2 and it seems that the delay bug is gone. Will make some other tests and tell my findings.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I flashed franco.kernel 86 and the problem still is NOT reappearing. So in my case it was definitely a ROM issue.
I will stay on Stock 4.2.2 for some time just updating the kernel to see if this configuartion is stable. Also will report to CFX that there is a bug.
[email protected]:
Google LG NEXUS 4 - CPU-BIN:nominal - BOB Austria
Rom ---------------------- Stock 4.2.2 (SuperSU, S-Off, deodexed)
Kernel ------------------- franco.Kernel - r86 (4.2.2)
Radio -------------------- M9615A-CEFWMAZM-2.0.1700.48
Custom Recovery -- CWM Recovery Touch v6.0.2.3
Do you guys honestly just click answer and start talking I don't say **** for two seconds anyway Lol..yea I don't have a catchy pick up line I say every time but still come on the amount of threads I've read about this and the non seriousness of the issue I'd think I'd be gone by now
Sent from my Nexus 4 using xda app-developers app
icecicle said:
Do you guys honestly just click answer and start talking I don't say **** for two seconds anyway Lol..yea I don't have a catchy pick up line I say every time but still come on the amount of threads I've read about this and the non seriousness of the issue I'd think I'd be gone by now
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
What is your problem?
I am seriously hating this bug! It is really annoying if you answer a call and the first word you say never is received.
I was looking through the forums but never got a real answer for where this bug comes from. So now I am trying to get some data on this issue.
Perhaps for nothing but nevertheless I try.
The weird part is, when you call, you can talk from the very beginning
calanizzle said:
I have this problem since day 1, for me it's not a 4.2.2 issue
Click to expand...
Click to collapse
Same here, had it on stock and on custom roms... I hope flashing 4.2.2 will solve this, because it seriously annoys me..
Bug present on Para21.Feb and Franco r86 all Radio and Boot 4.2.2
I know that it was fixed on para 4.2.1 but apparently not anymore on 4.2.2 what ever the dev thought by that... could someone of you provide me a link to the fix? (I searched, but if you search "call delay nexus 4" on google ...)
AW: Call Receiving Delay Poll
C0qRouge said:
I know that it was fixed on para 4.2.1 but apparently not anymore on 4.2.2 what ever the dev thought by that... could someone of you provide me a link to the fix? (I searched, but if you search "call delay nexus 4" on google ...)
Click to expand...
Click to collapse
I don't know if there is a fix for custom 4.2.2 ROMs already. I only don't have this bug with Stock 4.2.2 ROM (kernel independent).
Hopefully there will be a general fix for this.
It annoys the crap out of me!
Sent from my Nexus 4 using xda app-developers app
Also just tested the last CM 10.1 nightly without other modifications and I have the bug again. It is really strange that apparently some experience the bug and some dont, even if on the same configuration.
I have this problem but only for a second or so. You have to be really quick to notice it.
I had the same problem with the nexus one as well. That one was a good 3 seconds.
I found out what possibly could be the problem. At least for me as I only experience this bug when I am not on the 4.2.2 factory image (!=AOSP) .
According to rascarlo the developer of rasbeanjelly the device and hardware tress were not pushed to 4.2.2 AOSP yet [1] [2]. There is also an official google developer thread concerning the hardware/device tress [3].So all 4.2.2 Roms up to now are using binaries from the 4.2.1 release. This could explain my issues. Hopefully this is really the problem.

[Q] Delayed Notifications in Nexus 4 - Really a 4.2.2 problem?

First of all, I'm sorry because I know this is a recurrent topic, but I have my Nexus 4 for less than a week and the only issue (a big one) is these delayed notifications.
I've asked in more than a place about it and everyone say it is a 4.2.2 problem.
My question is why this does not happen in my Galaxy S3 with Cyanogen 10.1 (ie, android 4.2.2)? Any ideas?
I'm also currently using Cyanogen 10.1 in my Nexus 4, but problem persists. I got it while using stock too.
PS: I have installed Push Notification Fixer and set interval to 5 minutes. Delay remains.
This is a known problem for the nexus 4.
My old galaxy s is also running 4.2.2 and does not have this problem.
The problem is at Googles side.
However, you could try to flash a kernel with the wifi notification fix.
Link
I personally have not tried it yet.
Well, the S3 will have different WiFi drivers, for a start.
Sent from my Nexus 4
steviewevie said:
Well, the S3 will have different WiFi drivers, for a start.
Sent from my Nexus 4
Click to expand...
Click to collapse
I have this problem over 3G as well
Well, so it's a Nexus problem, not a 4.2.2 problem. That makes sense!
respider said:
I have this problem over 3G as well
Well, so it's a Nexus problem, not a 4.2.2 problem. That makes sense!
Click to expand...
Click to collapse
same here evn i hav this problem over 3g as well as 2g..did u find a solution yet??

[Q] Any reason not to install 4.3 jelly bean?

Only reason i can think of not to install the update would be for rooting purposes - i will almost definitely want to root, probably sometime soon. But just got it and I'm playing around with it a bit before first.
Just wondering if there's any reason to hold off on applying the update?
So you have a '13 N7, that you are using AND has 4.2 on it!!!???
SwiftKey'ed from my White Sprint Note 2 using XDA Premium
stanglifemike said:
So you have a '13 N7, that you are using AND has 4.2 on it!!!???
SwiftKey'ed from my White Sprint Note 2 using XDA Premium
Click to expand...
Click to collapse
My bad - it does have 4.3 on it already. But when i click on the system update, it says and i quote:
"This software update will upgrade your nexus 7 to android 4.3 jelly bean..."
To me that certainly sounds like 4.3 isn't on there right now, even though when i check the system properties it is showing 4.3. I guess this is just a minor update, with some poorly chosen descriptive text.
merkk said:
My bad - it does have 4.3 on it already. But when i click on the system update, it says and i quote:
"This software update will upgrade your nexus 7 to android 4.3 jelly bean..."
To me that certainly sounds like 4.3 isn't on there right now, even though when i check the system properties it is showing 4.3. I guess this is just a minor update, with some poorly chosen descriptive text.
Click to expand...
Click to collapse
That's because it is an update to the 4.3 already on the device. It contains bug fixes without adding anything major so that's why the version doesn't change. Go ahead and update; there's no downside.
Yea there are a few final updates you have to do when you pull it out of the box.
Sent from Nexus 7 FHD from XDA Premium HD
Thanks
player911 said:
01011001011011110111010100100000010101110110111101 10111000100001
Click to expand...
Click to collapse
[offtopic]What did I win? [/offtopic]
merkk said:
Only reason i can think of not to install the update would be for rooting purposes - i will almost definitely want to root, probably sometime soon. But just got it and I'm playing around with it a bit before first.
Just wondering if there's any reason to hold off on applying the update?
Click to expand...
Click to collapse
If you don't like the new maps it comes with it by default. You can always install a different version though.
Rooting is the same either way.

No quick reply/ delete/mark read in notification area for text?

Hey, I thought this was standard on all Jellybean and up devices? I had it on galaxy nexus when I got Jelly Bean, I've seen other phones have it. I know this G2 has a POP UP message where you can quick reply but that is massively not the same. Much preffered in the notification area like all phones I know of. Am I not seeing the option? please tell me there is a way. I know that If you miss a call, you get the quick options in notification like call back and message...
litobirdy said:
Hey, I thought this was standard on all Jellybean and up devices? I had it on galaxy nexus when I got Jelly Bean, I've seen other phones have it. I know this G2 has a POP UP message where you can quick reply but that is massively not the same. Much preffered in the notification area like all phones I know of. Am I not seeing the option? please tell me there is a way. I know that If you miss a call, you get the quick options in notification like call back and message...
Click to expand...
Click to collapse
Cmon, nobody? I'm assuming then it's not possible on the stock rom then?
I've yet to see that feature come standard on any skin except stock builds. Correct me if I'm wrong but I thought that was actually a feature CM or AOKP added onto the expandable notifications, I didn't think stock android or any skin actually have that by default. Again I could be wrong
Sent from my HTCONE using xda app-developers app
Yea,it definitely came with jelly bean,quick reply and something.then roms would add more options.so I'm very surprised that lg might not have that feature

Ok Google Touchless is not waking up Nexus 7

Hello!
A friend of mine, and i, each have a 16GB WiFi Nexus 7 2013.
While the screen is OFF (Nexus sleeping), my friend's nexus can be woken up by saying "Ok Google".
Mine ONLY works if my nexus has the screen on already (I dont have lock screen enabled).
His is completely bone stock and recently updated OTA with Kit Kat 4.4 KRT16S already.
I have TWRP recovery, and had 4.3 Stock Root.
NOW, i kept the custom recovery, but i flashed Stock Kit Kat 4.4 KRT16S NO ROOT.
and jealous (and lazy).. and i want my nexus to operate just like my friends... so either somethings wrong or maybe lemme know what i gotta flash. Thank you for your time.
Weird that your friends can wake even when the screen is not on... Never heard of that ( unless you have another app.)
What's launcher does your friend have installed? And make sure he does not have any other apps that enable him to do this. Check out "open mic+"
dragonboydbboy said:
Weird that your friends can wake even when the screen is not on... Never heard of that ( unless you have another app.)
What's launcher does your friend have installed? And make sure he does not have any other apps that enable him to do this. Check out "open mic+"
Click to expand...
Click to collapse
He is using the stock launcher that came with Kit Kat.
I couldn't even get it to work on the stock launcher, so i decided to look for and install the Google Launcher. I even tried reinstalling Google Now. I have looked at Open Mic+ in the past when i had a custom ROM, but i rather have the real thing from Google.
ElihuRodriguez said:
He is using the stock launcher that came with Kit Kat.
I couldn't even get it to work on the stock launcher, so i decided to look for and install the Google Launcher. I even tried reinstalling Google Now. I have looked at Open Mic+ in the past when i had a custom ROM, but i rather have the real thing from Google.
Click to expand...
Click to collapse
Well the real thing from the moto x (always listening) would require source code to be merged to work.
prshosting.org
Your friend isn't running stock. Stop making up stories.
ElihuRodriguez said:
He is using the stock launcher that came with Kit Kat.
I couldn't even get it to work on the stock launcher, so i decided to look for and install the Google Launcher. I even tried reinstalling Google Now. I have looked at Open Mic+ in the past when i had a custom ROM, but i rather have the real thing from Google.
Click to expand...
Click to collapse
If he is using the stock launcher that came with the nexus 7 and 4.4, he should not even be able to wake the device from thee home screen, much less a locked device... Only from Google now.
Only the moto x (and other Motorola phones with the special chip) should be able to wake from locked device. Not even nexus 5 can do that... Don't know what's up with your friends tablet
Try this:
https://play.google.com/store/apps/details?id=com.RSen.OpenMic.Pheonix
Saythis said:
Try this:
https://play.google.com/store/apps/details?id=com.RSen.OpenMic.Pheonix
Click to expand...
Click to collapse
And say goodbye to your battery :silly:
Either troll, or is being trolled by said friend
Sent from my Nexus 7 using xda app-developers app
Pfeffernuss said:
And say goodbye to your battery :silly:
Click to expand...
Click to collapse
He's not asking about battery life. He wants MotoX-like voice commands while it's asleep.
Saythis said:
He's not asking about battery life. He wants MotoX-like voice commands while it's asleep.
Click to expand...
Click to collapse
Yup, that's the point, it won't sleep anymore. Anyway, just saying, to each his own.

Categories

Resources