IssueTracker

Same to me. Nexus 4, stock android 4.3 JWR66V + root GSM disappear when wifi connected.

Can either of you take a bug report when this happens?

I have a bug report on disk (from adb bugreport). Should I upload here, or send directly to you? I'm a bit worried that it might contain sensitive data, and it's a bit large for me to audit before sending.

I have the same problem. Sometimes I have to turn the airplane mode on/off to get the signal back. I am on stock kernel+rooted with SU.

I have the same problem, I am stock kernel.

Same problem here. I'm Dutch and use Tele2 (virtual provider on the T-Mobile network). The largest Dutch tech forum is filled with this complaint.

It happens completely random. Sometimes when I'm using the device, sometimes when the device is sleeping. Sometimes once a day, sometimes 3 times per minute.

My device is a stock Nexus 4 from Germany, no rooting or anything.

I'm not entirely sure but it started around the update to 4.3.

Also, when I try to use the simtool, the app just hangs now (worked for a while) and doesn't respond (top right shows this loading circle).

The provider suggested setting the simtool to manually dutch. Didn't work.
Several people tried resetting the phone to factory default. Didn't help.
I tried running it in safe mode. Didn't help.
Several people flashed the stock baseband to 4.2.2 and that seems to solve the issue.
Removing the pin code from the sim at least allows the device to automatically log back in when it happens so you won't be off-line for hours (this is not a fix however).

How do I upload a bug report?

I'm on Tele2 in Norway, which is "roaming" on Netcom's infrastructure.

Like you, I tried flashing the 4.3 ROM again, with no luck. And like you, I tried safe mode, again with no luck.

I have gathered a bug report from both "normal mode" and safe mode, but as I mentioned earlier, I'm a bit hesitant to upload to a public forum. If this is the only way you'll look at the report, I will try to redact some info before uploading.

Thanks for the baseband tip. Maybe I'll try to flash the previous version. This is getting unbearable.

Bug 36949180 filed against the radio vendor.

You can also send bugreports to me at rgreenwalt@google.com.  I understand
the hesitation on uploading here.

The problem occurred before (about 3to4day when the OTA was first pushed) the 4.3 upgrade.
Im from Holland and the problems seem the be mainly with the Tele2 provider simcards.
If you have simlock-code active then you have to enter the code again.
The strangest thing about this problem is that its always occurs around 14:00 to 14:05 (GMT+1) even when you have screen on and doing some things.

(ps sorry for the bad English)

I'd like to make an additional note that it also drains the battery at (more than) twice the normal rate. Today I didn't use it more than normal but just an hour ago it was at 8% where normally it would be at 50-60%. I could easily survive on one charge for two days but now I can barely make the evening.

Same problem. Radio dies randomly and causes battery drain. Does not occur when radio is set to wcdma only instead of wcdma preferred...

Issue started after 4.3 update. Nexus bought online in play store. Non root stock rom.

I also had this problem, I flashed the radio that came with the stock 4.2.2 ROM and that stopped the random SIM card locking.

Before that I was using the default 4.3 radio and I got SIM locks all the time. This happened before and after I rooted the device.

I am also on Tele2 in the Netherlands.

An additional observation: The device often feels very hot (as if running an intensive application like a game) even though it has been sleeping and unused for hours. Doesn't seem too healthy imo.

Also, why is this being marked as small priority? Seems that a phone that can't call is a big issue to me. I'm considering returning the device as defective at this stage.

I'm having the same issues: random simlocks, random singal loss, extreme battery drain and bad sound quality when making calls. I'm also on Tele 2 in the Netherlands and my device is stock and unrooted. Issues first started a few days before the 4.3 update, but have intensified since then.

Experiencing the same issues with stock rom nexus 4 on french carrier Free Mobile which has roaming between carrier native network and Orange France when Freemobile signal is not available.

I got seemlocks and network disconnections... Disabling the pin code temporary solved the problem

I also have the exact same issue on my Nexus 4 running stock 4.3. A few times a day I notice I have to enter my SIM unlock code. Happened only after the OTA update a couple of days ago.

It sounds like your phone is crashing.  Can any of you take a bugreport
right when the sim unlock code is prompted?

I have the exact same problem. Netherlands - Tele 2 - double battery drain and seemingly random radio drops. Sometimes up to 3 times a day (it might indeed be related to wireless networks).

The SIM unlock prompt seems to happen when the screen is off so it's hard to pinpoint the exact moment. If I could be directed to some instructions on how to create logs I'd be happy to experiment some more.

Download the SDK: http://developer.android.com/sdk/index.html
If you're using Windows, you might also need the USB driver: http://developer.android.com/sdk/win-usb.html

Open a console / command prompt and navigate to platform-tools in the SDK. From there you run: ./adb bugreport >logfile.txt (use .\adb if you're on Windows). Run this command right after the radio dies.

Here is some more help on adb if you need it:
http://developer.android.com/tools/help/adb.html
http://forum.xda-developers.com/showthread.php?t=2266638

Hi,

I was using my phone as GPS for holliday car travel yestarday and I noticed that when radio dies, phone disconnects network and GPS signal is lost at the same time.
Radio problems are confirmed.

Also have battery drain.

Can somebody not scale this problem to priority high because there are a lot of users heaving this problem

I also experience the following problems with my nexus 4 and android 4.3:
Problem 1: random sim locking when radio is set to 'wcmnda prefered'. The problem does not occur when i was at android 4.2.2. Also the problem does not occur when the radio is set to 'wcdma only' (code *#*#4636#*#* call). I also use the dutch provider tele2. The problem also only occurs when the phone comes out of standby.
Problem 2: Battery drain problem when the radio set on 'wcdma prefered'. The drain does not occur when i set the radio to ' wcdma only'. The phone can last for almost two days since i set the radio to wcdma only. Unfortunately, the phone resets itself to wcdma prefered when i reboot.
Problem 3: Frequent signal loss when radio was is set to 'wcdma prefered'. When set to 'wcdma only' The signal is very stable and the internet speed is good.

All problems seem to relate to the radio. People that flased the radio back to 4.2.2. don't experience problem 1 anymore.

 
 

Internal bug created: 10183577.  Two bugreports have been forwarded to the radio vendor.

More bugreports welcome - send them to me at rgreenwalt@gmail.com

Hi,

Is there any way to follow up the radio vendor bugreport bugreport progress ?
Is there is any ETA (or estimation) for the bugifx ?

Thanks

I have the exact same problem. Using Free Mobile in France and can't understand we have this critical regression on the radio in an official release...

Same exact problem it's stranger because I was always completely stock never rooted and on my first device I didn't have this issue on 4.3 but got another device through warranty due to what I thought was an issue this week and I'm currently experiencing this problem on my 2nd nexus 4 I'm on AT&T

Also when downloading apps from the play store it's ridiculously slow

Does flashing the 4.2.2 baseband also help with the battery drain?

I got the phone to day in the mail. Same problem here, but already with 4.2.2. Thus, right out of the box. 'wcdma only' did not help, neither after the 4.3 update. I'm also on the Tele2 network in the Netherlands.

Same issue here on french provider Free mobile.
Got this since my 4.3 upgrade.
I send my bug report to rgreenwalt@gmail.com

Regards,

That should be rgreenwalt@google.com

Same here. T-mobile uk. Radio dies. Need to re scan for mobile networks to make it find a cell. Often have to re-enter my sim pin.

No pattern yet as to when/why to capture logs

Sorry, message sent to the correct email.


Regards,

Went abroad the last couple of days, could not make contact with any network.

Maybe this problem is related to the European wide T-mobile issues? Does anybody here have the problem outside Europe and/or on a network that is not T-mobile/virtual host?

Not entirely sure if related but my Galaxy Y Android 2.3 phone (my backup phone) just gave me a simlock screen at random as well. It's on a T-mobile prepaid card.

I am also in the Netherlands and I use Vodafone. Randomly I have got loss of GSM signal.

2 dans ago, I reflashed radio with 4.2.2 version and I have no more radio deaths, battery drains etc...
So I advice to reflash 0.48 radio version from factory default image to avoid this issue

Same problem here in Austria (carrier is Yesss): System randomly asks for SIM pin. No problem with 4.2.2 on Nexus 4 before upgrade.

Phone app has another problem: Last calls list is not updated with time correctly: Requires a phone call to update.

Same problem here Also German Nexus 4 and Tele2 Provider

One small note: after trying to downgrade with official Nexus 4 Android 2.2  image realised that EFS partition with IMEI number and stuff like that is totally screwed. Not sure if it's related. But it MIGHT be.

This should be high priority, too many users finding this since update to 4.3.  Not acceptable on a new phone and needs Google to either re issue 36903753.2 again or fix problem .  We shouldn`t need to be mucking around with a new phone looking for a fix.

I agree about priority, I wish I hadn't applied the update, it's causing me serious issues and an inability for people to get in touch as I get my phone out of my pocket after a few hours to discover no signal and a sim lock screen.

I wish there was an easy way to roll back to 4.2.2

For now I telling my friends not to update when they get prompted. Doesn't give the best impression :(

This is hitting a small percentage of users.  It depends on your particular carrier and SIM.  It has been fixed internally and I'm lobbying for an OTA, but that's out of my control

Hopefully soon then. I just looked at my phone and no network again for the second time today. Im on the O2 Network/Giffgaff  UK. I need my phone to be on all the time for my business.  So how can we speed up the OTA ?    

If no ota. Is it easy to patch onto the phone? Would love a fix!

You can flash the 4.2.2 radio version waiting for thé new release. I did it and ni problèm anymore.
Maybe thé new radio could be published as a firmware flash if not available as OTA.

Part of the fix is in the android framework, part of it is in the radio
vendor's code.

Is there a way we van download thé fix to beta test it ?

Same here - NL Tele2 and radio reboot every day. This is really annoying, the 4.3 radio seems to give better signal, bit the reboots are a real pain in the. Why is this particular to this provider?

There was code added to support MVNOs (
http://en.wikipedia.org/wiki/Mobile_virtual_network_operator) and if a
record on the SIM and details from the carrier are badly matched we can get
a crash in telephony.  It's not particular to *one* provider, but probably
a set of providers or a set of SIMs.

Ok, could you specify this in a little more detail so I can talk to our
Tele2 rep on this?

Verstuurd vanaf mijn mobiele toestel, excuses voor eventuele typefouten.
Op 19 aug. 2013 23:01 schreef <android@googlecode.com> het volgende:

The AOSP fix:
https://android-review.googlesource.com/#/c/63561/

Note this is being redone as it was pointed out we lost case-insensitivity,
but this does fix one of the crashes (the one that's carrier/SIM specific).
 The other was in the radio/RIL and is not carrier/SIM specific.

Can anyone explain how to apply this AOSP fix?

thanks in advance

http://source.android.com/source/building.html :-)

Good luck!

I'm having the same issue in the UK. I'm using the GiffGaff network (which runs on the O2 network, but as a separate entity).

Very weak signal, drops the carrier and half the time I can't get it to find one afterwards. Also massive battery drain issues.

4.3 has been terrible since I first upgraded, I wish I hadn't been so eager to upgrade! My wifi connection has got the same problems.

I'm using a stock nexus 4 (developer unlocked but not rooted) running 4.3

My GSM signal turns off once in a while . 3-4 times a day. Then i have to manually register the network. Nexus 4 Andorid 4.3

Do you know if JWR66Y version fix these issues?

JWR66Y has the same version of the radio as JWR66V.

Same issue here with Tele2 NL.
randomly (around 6-8 times a day) pin code is requested.
I'm also experiencing signal loss (or perhaps better described as a signal 'freeze') where calling is not possible and the signal bar remains in a freeze state (no change in signal strength when I check the phone Status).

I hope the fix will be released soon.

Same problem on Free Mobile in France. Not too often but sometimes.

Just read on Tweakers.net that disabling Sim pin may be a workaround. Worth a try.

I have the same issue when the network mode is 3G preferred (02, Germany)...The connection just freezes and doesn't recover unless I either manually turn on and off the network, or restart the phone itself...Such a basic issue, and can't believe this came bundled with the 4.3 update :( I really hope they fix this issue soon...
(I use a work around for this issue, which is to set network preference to use "only 2G network"... though the internet speed sucks, at least I can stay connected ! )

Jep, same trouble here after OTA 4.3 update.

I'm using the app Light Flow (paid) and reacted an action with a repeating sound+vibration reminder every 15 seconds when the phone has host network signal. This is the only way to discover that the phone module has crashed. I'm not looking at my phone the whole day...

As described on tweakers I now disabled my SIM pin, hope this helps.

I'm using a Tele2 SIM. Tele2 is a virtual operator on the T-Mobile network in NL.

If you know how to, flashing the radio from 4.2 seems like a better idea than removing the SIM lock. I haven't had any dropped calls or other issues since downgrading the radio.

I'm not having any problems with Hollandse Nieuwe...

Same issues for Dutch virtual provider Ben NL (using T-Mobile network). Another bug that possibly occurs since my latest upgrade is sudden warnings of sim card removal. After an reboot (no hardware changes) the warning is gone.

Possibly helpful for fixing the issue.

I also experiece the sim locks (and then need to reenter my pin). Already received a new nexus 4 from Belsimpel.nl and a new sim from Tele2, as they didmt know of this bug (and me neither). Both the new sim and new phone didnt solve the problem for me.

Same thing here, signal drops and battery drain. USA carrier Verizon. Is there any workaround that can be used until the fix is released other than the compiling and flashing ideas that are listed here?

Yes, I'm also having these problems. Nexus 4 with 4.3 and MVNO 'Hollands Nieuwe'.

Also having the same issues on the Belgian Mobile Vikings network.

Dutch provider Tele2, same problem here with 4.3.

And hey congrats! This problem made it all the way to the biggest Dutch tech site Tweakers.net! (see: http://tweakers.net/nieuws/90867) :-)

Issue is still there in JWR66Y...
Le 24 ao�t 2013 01:33, <android@googlecode.com> a �crit :

same problem in belgium (proximus), gsm and wifi keeps dropping and i have to enter pin code again sometimes. it started after 4.3

Same problem in Poland (Play/P4) radio signal jumps from 100% to 0 in 2 min cycle. Also noticed that my battery dies after one day (4.2.2 could hold for even 2 days).

Same problem here (Phone getting hot - battery drain) and poor/lost signal.
JWR66Y (upgraded from 4.2.2 vanilla)
Virgin Mobile Canada

What does it take to escalate this to an OTA update?

Is there something we/vendor can do to the SIM to fix the issue?

Is there a place to vote for an OTA update? Or is the only thing we can do post as many complaints as possible? :p

I just received an OTA but I can say if there is any chance

I have also received an OTA after I had mentioned the problem in this topic (#18). But I can say the the problem persists after the update: I still get about 2 radio crashes per day.

I have JWR66Y as well but it still crashes all the time. If this carries on
much longer I will consider the device defective and return it. :(

I did a factory reset and re-flashed android 4.2.2, which has solved all the problems. My issues with 4.3 got worse - phone shutting down without warning, weird camera problems (rolling picture), plus constant network dropping and extremely weak/fragile wifi. 4.2.2 is working fine, 4.3 is a disaster as far as I can tell and the lack of prompt updates to fix the issues makes me seriously question Google's customer commitment. I wasted so many hours trying to sort out the 4.3 problems before getting rid of it completely.

I have also this problem with my nexus 4.
Sometimes network resets.

Same issue on my side, on nexus 4 JWR66V with Free Mobile Provider in France.
Mobile randomly loses network and asks for SIM code at wake up.

Since the 4.3 update my Nexus 4 loses cell connectivity several times a day (no locking  or crashing though). Recovers by itself after some time (varies widely) and also after toggling airplane mode. Running Android build JWR66V and using Dutch virtual operator Simyo.

Good to know that it's already fixed, but could we get the update ASAP? This isn't just some minor defect, it ruins the elemental functions of the phone that even $20 devices perform flawlessly.

Same problem on dutch Telfort network(MVNO), loosing data connection all the time and huge battery drain (msm_hsic_host holds a wakelock). However I am not facing the problem that I have to enter the PIN again. Changing the network to "WCDMA only" solved the loss in data connection and reduced the battery drain, but now I have less coverage and I have the feeling the drain is still more then it was on 4.2.2. Is there a way of returning to 4.2.2 without loosing the settings/apps?

very strange.... I have had many problems with disconnecting/connecting 3g. I've tried everything. After the update to jwr66y nothing changed. Until yesterday, I changed the setting to WCDMA only (i've tried before without success on jwr66v) and suddenly all works perfect!
(vodafone in the netherlands)

With vodafone the same issus.
Cyanogenmod have implement the fix:

https://github.com/CyanogenMod/android_frameworks_opt_telephony/commit/3f548cb6dcbacc6dbaa062322a12674fe8f4c734

I received an OTA yesterday and I was hoping it'd have solved the issues. Battery drain seems to be solved for the most past but I still get SIM locks.

Which build number did you receive?

JWR66Y

The problem keeps escalating. Today it turned out that my phone was functional except that nobody could call me. Pretty awesome when you're one of the lead programmers 2 days before the deadline. It's been weeks now and still no word implementation. :(

10 days since last news of this AOSP fix, any update for the faisability of an OTA to correct this issue please?

Any update on this? Is there an ETA for an OTA update? This was reported almost a month ago ...

This might be only hitting a small number of users (not so sure about that, since many people will probably be thinking that this is a network provider issue and thus not reporting it) but it is a critical issue for us. My phone is simply unusable right now.

Please google fix our phones

My network connection drops out about every 10 mins if browsing all that time. If I stop browsing then later resume it will drop out after a while. It's almost as if it allows a certain amount of traffic, then kills itself. Disconnecting Mobile Data then reconnecting fixes it for a while. Australia Amaysim (Optus reseller). Build JWR66Y. OEM, unlocked, not rooted.

same problem with nexus 4 in austria (orange / Hutchison Drei Austria (they are merging right now and the problems just gets worse and worse, massive battery drain also. when 3G internet is activated and I' starting chrome + opening a website it instantly losses its signal to no carrier / no signal. If it reconnects and happens again for a few times (around 5-10 times) the nexus 4 display gets dark (I think it crashes) I have to start(boot) the device again. So now I switched of the 3G and I hope it will work a little bit better..

(First time the problems appeared at 4.3 after the OTA, then I tested a cfw, then a 4.2.2 and now returned to a fresh OTA over the fresh 4.2.2 - evertime the same. old baseband from 4.2.2 wasnt the solution - "crashed" too.)

Google have pretty much crippled the Nexus 4 with the 4.3 update for a lot of people. Now they've dropped the price by $100. I think they should offer all affected users a FREE Nexus 5 upgrade to compensate them for the huge inconvenience of giving them a phone that effectively hasn't been able to reliably carry out the most basic functions for over a month! That's assuming the Nexus 5 will run ok on 4.3...

re comment #99. That would seem a fair thing to do, and would at least show Google customers that they really do care. But for next time, when I decide I need a new phone, will I buy a Nexus??? Hmmm, that might depend on what happens re compensation....

Same problems here: carrier signal vanish randomly, battery drops from 30%-80% to zero.
Stock 4.3 with the German provider "deutschlandsim" which use the O2 network.

and after 5 days, the problem returned after i have restarted the phone. Please Google, solve this problem. Now I know it isnt a hardware problem but a software problem!

After reading all the reactions first thing comes to mind is - HOW THE HELL DO WE CONTACT GOOGLE TO SPAM THE HELL OUT OF THEM FOR A QUICK FIX! Even Apple has more clear support channels, I can walk right into a store or contact Apple either thru web or email. Google? Here in most parts of Europe? Hell no, no way to contact them it seems... anyone any suggestions on how to put some pressure on G?

I have the same problem, Telfort the Netherlands. I understand that there is a solution/ fix for this software problem in Android but Google don't see the urge to implement this. I don't understand why they don't give us the update because now the most basic functionality of my phone, calling, is not werking. In my opinion this is a shame and shows a lack of attention tot their customers. Google please show us that you can do beter than this an implement the solution as soon as possible!

I hate to say it but I am really disappointed. Google clearly think this only effects a small number of people and is therefore not worth an ota (see Google comment #45. So the only way this will get fixed I'd to up it's profile.

Publicise the bug, send it as a story to gadget sites, complain to your operator, get anyone you know who had this issue to come here and comment.

Personally this is embarrassing I have recommended the nexus 4 to many people all of whom now have this issue. Given the lack of fix I'll have to think twice before recommending Google things in things in three future.

I should also add that ironically one of my reasons for recommendation of the nexus 4 as opposed to say a Samsung galaxy was the fact that you got ask the android updates promptly :-(

I fixed the problem on my n4 device. my battery was f**up (1 month after the 6-month warranty period has expired) - and now everything works fine. no big battery drain, no sim pin questions anymore. maybe its just coincidence that the 4.3 ota was at the same time..

Same here,

but I'm not asked to reenter the pin. The only thing to get my gsm working again, is to reboot the phone and then enter the pin.

@comment #107: How did you discovered the battery was like this?
That's pretty disturbing...
Please Google, quickly do something for N4 users with these issues (Pin code  and battery drain)!

I have the same problem here. Big battery drain when I have a network connection, normal drain when my radio crashes and my network connection is disabled (untill I put my PIN in again).

I also find the battery very hot when I use my Nexus4 a lot, much much hotter than before these problems. I'm thinking the picture from comment #107 shows a battery that overheated, causing that damage.

Google, you have to fix this problem ASAP or Nexus4 devices will start damaging themselves.

@ #109: my n4 shuts down even at 70% battery status in the last 15-20 days (don't know when exactly it starts). I can't definitely say that it's because of 4.3 or a faulty original loader or the summer-heat during my vacations. I bought a new original battery via ebay and replaced it yesterday night - where I discovered that the battery got a "cut" in the covering. Another possible explanation could be the fact, that my n4 got its frontdisplay replaced by a (non google!) company - and I think (by the look on the blue tape, that wasn't glued over the wireless cable anymore (like in fix-it tutorials described)) they "touched" the battery. So I don't have an clear explanation how this sharp "cut" occured. maybe #110 is right and it "just overheated". I'll now load the new battery with an ipad2 charger (2.1A) instead of the original, because since I've bought the nexus4 the original charger got a weird buzz sound (I'd read about it in the past) and I'm not sure if this is normal or a indication for a faulty charger..

@ #111. I've never used the Google supplied charger. Considering it's a USB cable, mine has always been charged of my PC, it being used as my 'net connection as well. And btw, it doesn't matter if I'm USB or hotspot tethered, it still drops out after 10 to 30 minutes.

I am from India.. Facing same problems since last 15-20 days of network error, battery drain etc.. Anyone suggest is there any solution like going back to 4.2.2 or battery change?

Further to my comment #112 above. I'm beginning to think there are two separate issues / faults: A software issue and a hardware issue.The software issue has been discussed extensively, and a potential work around first suggested by #14 above. The second issue is the overheating and failed batteries. I find it hard to believe a large number of faulty batteries were placed in LG assembly process. Possible but unlikely. It might be that the power plug it self is failing and producing an output unacceptable to the phone. That might explain why the phones are getting hot and are damaged as #107 has shown. Even though software and hardware have to work in harmony, I don't believe, in this case, that JB4.3 has caused the battery issues. I do think that the two issues are coincidental unfortunately.

I am also experiencing poor reception with both WiFi and gsm connectivity.  Often the bars representing the signal strengths are grey or no bars at all.
This is quite unacceptable.

My Nexus 4 continually loses the signal and at the end of every call reboots itself.

#116 I guess It's because of a faulty battery. I've experienced the same until I replaced the battery by myself.

@zed.melody
I have a Samsung Galaxy Nexus and suffer from radio signal loss multiple times per day. My Battery works perfectly and I have not the overheating issue like users with Nexus 4. So IMHO it is not a battery but a software issue.


                  Ceterum censeo Hangouts esse delendam.

@#118 Bonus unus

Dropout update. As of 10:50 2/8/13 Australian EST, the system has been stable - no internet failures from 06:30 this morning. Yesterday was terrible with dropouts every 10 mins or so. On 30/8/13 I took a note of the Baseband, Kernel and Build (JWR66Y). They are still the same. There has been no notification (on the phone) of an update. Just posting this because it's a change in the way the phone is behaving, and may or may not be significant.

More dropout update. Spoke too soon. #$%^&*()!

I have the same problem. Every 2 to 3 hours signal loss. And then I have to enter my PIN again. Of course you can switch to 2G only under settings, mobile networks, more. But then you have a very slow internet connection. And I feel that still the signal drops out. I find this really sucks. Hopefully they fix this soon.

[Comment deleted]

Same reception problems on brand new Nexus 4. Quire frankly this is ridiculous. How can the provider of an OS not even have it function correctly on THEIR OWN device. First and last Nexus adventure. Fuming with rage.

[Comment deleted]

Let me share my breakthrough discovery here. That "EMERGENCY CALL" message appearing at the bottom of the PIN unlock screen, right under the operator name, is not a message at all, and it doesn't say "EMERGENCY CALLS ONLY". Instead, it's a button that lets one make an emergency call. Simple and stupid as that.

Geez Google. How difficult is it to put out an interim update reverting some code back to 4.2.2? Call it what ever you like: 4.3.1, 4.3.0a, 4.3 sorry we stuffed it. I think I can speak for most of the people here: We don't care, JUST FIX IT FOR US so we have a product suitable for the purpose it was intended.

Our release team thinks this is not a very common problem.  Please call the
call center to register your complaint: 1-855-836-3987.  Apparently that
adds weight to the issue.

Why not an online form? Not everyone lives in the US...

Just don't try to call that number from your 4.3 Nexus :D

Can't they read this blog/forum/whatever-this-is? Even if we are the only ones with this problem (which I very much doubt because a lot of people won't even see the connection between the problems and the update and even more won't find this page), it is still a major bug which can even damage the hardware (as seen on the picture of the guy with the broken battery) and completely disable the standard use of a phone: being able to CALL people without it crashing all the time!

I'm very disappointed in this, I bought a Nexus assuming I would get the best support, but clearly buying a Nexus results in you getting the f*cked up bugs as one of the first people...

Also, how the hell am I supposed to call that number? I'm not from the US and my phone isn't able to place a freaking call!!!

Sorry folks.  Check for your local call center number - I pulled it from
https://support.google.com/nexus <https://support.google.com/nexus/?hl=en> but
that may give a different # for non-US lookups.

nice... no hardware support from google in the netherlands. And a lot of users in the Netherlands have this problem. It was even on main page of the biggest Tech Site in the Netherlands!!!!

(source: http://tweakers.net/nieuws/90867/bug-in-android-43-op-nexus-4-laat-mobiel-signaal-wegvallen-en-accu-leeglopen.html ) Of course google can use their own translate application. (if it works :-( )

GOOGLE WAKE UP

Had an update waiting when i woke up. Im going to apply simlock again and hope thuis problem is fixed.

The support phone number in Australia is: 1800 093 181. It's a VOIP service answered in good 'ol USA. Note that there is about a 2 second delay in conversation and voice quality is only reasonable. Hope that helps.

As suggested by the Project Manager #128 & #132 above, I reported my problem to the support centre. They asked me to do a Factory Reset and get back to them if the problem still exists. I did the reset, and now my N4 won't connect to the net - no data service. Great! So now I've upgraded to my simple Huawei Sonic for a phone. I'm now investigating how to return my phone to 4.2.2. After the reset it came up as JB 4.3 JWR66Y.

I had The same thing after a reset, just reenter tour APN settings again.

Thanks klaasbram. You'll like this! I changed the sim back to the N4. Rebooted. Network came up. Yea. Entered APN settings. No network. Bugger. Back to humble Sonic. I have a question. Can anyone advise an unusual way to brick my phone? Pictures taken of course. Grrrrrrrrrrr. I'm getting too old for this crap!!!

Philippines here, same issue using SUN Cellular.

Stil received a simlock today, nut only 1 zo far. Thats less then before

Wellll, after lots of dramas, and a HUGE learning curve I finally downgraded to 4.2.2. Immediately after I did lots of things didn't work. The short version: no charging via USB - rebooted PC (Vista). Still no internet. Put in carrier APN, would not 'stick' at first but finally did - didn't change things. Switched to 2 G only. Yeah, that worked but s l ooo w. Played around with 2G/3G for a while - nothing. Played with WiFi. I don't know what happened but shortly after that it started working correctly, and has been for a few hours. But then I rebooted the phone. All back to square 1 - no network! After playing around again, it seems it could be related to the APN. Hmmmmm

On another note, I noticed under System Updates, there is a 4.3 System Update. In greyed out text it says "Waiting to download 169.3MB" and "Via Wi-Fi only until 8 Sept". Could this be a prelude to the roll out of KitKat 4.4? Any comments Robert?

I've posted this on XDA - there must be a dev that is more capable and willing than google?!

http://forum.xda-developers.com/showthread.php?p=45371944#post45371944

Does anyone know how to do this radio flashing? I'm really annoyed now and it sounds like, from the XDA forum post, that "flashing .48". But I have no idea where to start with doing that. I'm reasonably technical though so can follow instructions :)

Does anyone have a good pointer to some instructions on how I downgrade my radio to .48 so my phone will work and allow me to actually receive calls rather than spending its day sitting on SIM lock without me realizing?

Download the factory 4.2 image from here:
https://developers.google.com/android/nexus/images#occam

Make sure you have the SDK installed (see also #21) and hook up your phone with a micro USB cable to your PC. Then unpack the factory image and use fastboot from the SDK to flash the radio:

./fastboot reboot-bootloader
(wait for the device to enter the bootloader)
./fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.48.img

I have not had issues with the radio after flashing the old version, as stated by others in this thread.

One more thing : if your device bootloader is not unlocked, you must unlock it before flashing the radio otherwise your phone won't let you flahs.

The command to unlock bootloader is :  fastboot oem unlock
Please note this command will erase all your data from your phone, so you'll have to reinstall all your data. Backup before flashing.

Happy flashing

Take in account that downgrading is not always the solution.

Update: Downgraded to 4.2.2 over the weekend. The absolute easiest way is to use "Nexus Root Kit" by WugFresh. It does it all for you. The program only works for Nexus devices and stock images. The only hiccup I had was sometimes I had to manually select USB Tethering. Read XDA's description http://forum.xda-developers.com/showthread.php?t=1766475. And to Dennis.v, you are right. The solution to the issues described in this thread is for Google to publish updated code, hopefully in KK4.4. Until then, we have to use a work around. Going back to 4.2.2 is a short term solution. Add smiley face here.

Same problem here, Tele 2, The Netherlands

Flashed to cyanogenmod + the .48 radio. Looks like it fixed all problems. Thanks to for the devs in here that at least respond. But I shouldn't be forced to hack the device in order to fix it.

Google's behaviour on the other hand has been ridiculous and by far the worst that I have ever seen from any company. The complete lack of service info in this country is absurd and in violation with consumer protection laws. I was very happy to run stock android but will never again buy a google product after this experience.

I've been experiencing this same problem on AT&T in the US. I just got my phone yesterday and had a new micro SIM installed.

I've had to use Airplane Mode at least 10 times while at work today. Signal bar shows full service however data transfer does not take place. Only way to get data working again is to use turn airplane mode on and off.

This seems to happen every time the screen turns off.

My phone is bootloader unlocked and rooted. I've tried various other modems and none seem to cure this.

I also had no connection at all for 2 days. I tried some settings, but nothing worked. Today I restarted my phone and took out the sim card and it worked afterwords. Here are the steps I took to get my connection back:
 - Settings > More.. > Mobile networks > Use only 2G networks > true (on)
 - Airplane mode > true (on)
 - Shutdown the phone
 - Took out my sim and put it in an other phone and connected.
 - Put the sim back in your phone.
 - Boot the phone
 - Waited a few minutes till he is fully booted.
 - Airplane mode > false (off)
 - Settings > More.. > Mobile networks > Use only 2G networks > false (off)

Now my phone is normally connected. (didn't try it again, don't want to lose my connection again) It doesn't disconnect after sending messages of calling.

I don't know if this was helpful. I hope it was.

{
android version: 4.3 (JWR66Y) (stock android, no mods)
Baseband version: M9615A-CEFWMAZM-2.0.1700.84
County: Belgium
}

Google, any update?

Save your breath, google doesn't give a shit and clearly has no plans to fix this (despite the efforts of the helpful folks here). Instead, do what I did and relatively easily fix your problem yourself.

Download the 0.48 radio from here -> http://forum.xda-developers.com/showthread.php?t=2087227

Download and install fastboot from here -> http://wiki.cyanogenmod.org/w/Doc:_fastboot_intro (note: check your device manager, if your nexus 4 icon has a warning symbol, install the drivers supplied with the SDK)

Unlock and install a recovery zip from here -> http://wiki.cyanogenmod.org/w/Install_CM_for_mako
(note: you can go through the whole 3 phases and install cyanogenmod but your don't have to. Only phase one and two.)
(note: after installing the recovery zip, you need to go into recovery without rebooting. Some devices will undo what you do upon reboot.)

Use the 0.48 radio that you downloaded in step one. Job done, problem completely solved.

Note: In my country it's legal to do this without warranty issues (if you know what you're doing), be sure that it is in yours as well. This might wipe all data on your device. This will root your phone. Although unlikely, you might brick your phone or do other damage. Use at your own risk.

See http://forum.xda-developers.com for more help.

Clarification: Of course you would have to do phase 3 but instead of cyanogenmod, you would use the radio. Or both (be sure to get gapps as well in that case).

Guys - ofcourse this will work, but do not forget this is a DOWNGRADE instead of an upgrade. Why the hell did we get a Nexus device then? Would be better of buying some bloated Samsung or HTC, at least they TEST AND FIX before releasing crap updates. Oh and don't forget; they offer SUPPORT. Very very disappointed, no more Nexus devices for me for sure!

Indeed - it does very much feel like the Nexus 4 has been totally forgotten about and they're simply focussing on MotoX and the forthcoming Nexus 5 (which is rumoured to be another LG device, which I won't buy based on the poor quality of the nexus 4 build and the inability of google or LG to agree on who is responsible for the device)

You can flash the 0.48 radio without need to root your phone.
Just download android SDK (to get fastboot), nexus 4 jelly bean 4.2.2 factory image to get 0.48 radio version. Unlock bootloader by using "fastboot unlock oem", and then flash radio using "fastboot flash radio radio.img".

Otherwise, this part is for Google staff : it is said this problem is fixed internally, so if there is no plan for an OTA fix, why not publishing new radio on this thread, so users can download and flash their phones ? I'm sure this is not very difficult and would be very apreciated by users.

Thanks in advance.

Flashing a different radio has not helped for me. Have constant data drop (with full bars showing) at work.

As mentioned in my previous post, running 4.3 with an AT&T SIM card (brand new SIM w/ no change in data plan).

I can confirm that flashing a different radio did not help. It even makes it more worse.

I am not surprised that flashing a different radio doesn't help.  There were two known issues - one an mvno issue in the android system and one a RIL (radio interface layer) bug identifiable by:

08-02 08:57:34.952   849   923 E RILQ    : (0/849): [main] qcril_free: *****ASSERTION FAILED*****
08-02 08:57:34.952   849   923 E RILQ    : (0/849): [main] qcril_free: Cond: mem_ptr != ((void *)0)
08-02 08:57:34.952   849   923 E RILQ    : (0/849): [main] qcril_free: **************************

Both of these require new system images, not radio images.

I am in Turkey and I use AVEA. After installing android 4.3 I keep losing the signal randomly.

Same problem problem after upgrading to 4.3.
Thanks Google for pushing a buggy rom!!!!

Same here, also n4, tele2, netherlands. Please fix it...

Since Google doesn't acknowledge the gravity of the issue I took it upon myself to fix it. In the process I managed to brick my phone and lose all sorts of data (most of which I backed up, luckily enough). Now I have it unlocked with a custom recovery and I managed to flash the old radio firmware.

So thanks again for the excellent customer service Google.

Next time: Samsung it is.

Same here, also Tele2 (NL) , since update to 4.3 often re-entering PIN (signal loss)--> disabled PIN-security :-(

And very weak battery! Last week on vacation with mobile data (and roaming) turned off, the battery last for 3 days easily....

I don't want to flash the radio to .48, because i dont want to wipe my phone!

Since there only appears to be predominately negative posts, I feel I should add a positive one.

I also experienced this issue and posted my issue (radio dying and battery consumption) on Virgin Mobile Canada a few weeks ago.  

Shortly after my post (an hour or two) I had a system update waiting for me on my Nexus 4 and Nexus 7.

I believe the issues have been fixed (I do not have a locked pin so I cannot comment on that).  My build is JWR66Y which I believe is unchanged from 4.3 release.

So was my post related to getting an update or is that coincidence?

I am again happy with my phone and I feel for all other users still experiencing this issue.  It definitely makes for a bad user experience of an android phone.  

I'm surprised this hasn't turned into a Iphone4 AntennaGate for Nexus4.  This fix needs to be rolled out before it does.

I myself though my issues had been fixed after I received an OTA (with build JWR66Y). Not the case unfortunately. Now that I've downgraded the radio I can make 60% at the end of the evening with my battery. Still not what it used to be unfortunately.

Any update?
I'm afraid as the Nexus 5 is coming, Nexus 4 will not be updated, and this issue will not be corrected...

Hello,

I got the problems twice with two different Nexus 4 (first phone bought on 31th January and the second I got for replacement early on September one after discussions with after-sale service).
My bug is that I lose GSM signals. The signal bar triangle is then empty. The only way to retrieve signals is to reboot the phone (I am doing this sometimes like more than 15 times a day).
I may be unlucky as possible to have twice the same "very minor" not listed bug (as say Google...) on two different phones, or the bug occurs when different factors are here together:
In my case:
- 2 Nexus 4 (Rev11)
- GSM operator: B&YOU (BOUYGUES TELECOM) FRANCE
- Problems after OTA update of Android 4.3 (with build JWR66Y)

Google, if you know about this bug, why are you waiting so long to send an update... I ask for my third replacement phone in 2 weeks because of this.

You are losing money and customer with this problem!

Regards,