Just received the qe1 update on my 920t a few days ago and now I'm losing 4g constantly. The only way to reconnect is to turn airplane mode on and off. I have seen this is a problem with the nougat update. Is anyone else having this problem and does anyone have a solution? I've tried everything I can think of to help and nothing works.
I have not noticed any change after the update...
4G stable as ever!
Nightcatfisher said:
Just received the qe1 update on my 920t a few days ago and now I'm losing 4g constantly. The only way to reconnect is to turn airplane mode on and off. I have seen this is a problem with the nougat update. Is anyone else having this problem and does anyone have a solution? I've tried everything I can think of to help and nothing works.
Click to expand...
Click to collapse
How did you flash? Did you update over the last update? Did you use smart switch?
When ever I hear of people (or myself) runs into problems after an update I usually suggest a full wipe with TWRP. (this includes the system partition)
Starting fresh and Odining the latest firmware is the best way to go.
Not sure how this could have happened. If anything the QE1 update was supposed to have fixed some call issues. You can always try reflashing the QE1 modem from HERE though and see if that fixes it. If not you can try reflashing the firmware with Odin from the "Sammobile" site. If that doesn't fix the issue either then you always can always try goung back to QC6 either from Sammobile or, if you happen to be rooted, then simply by flashing my QC6 Lite Rom.
Related
I updated my stock Rogers Nexus 9020A via the manual update to 2.3.4 update went fine but now my search button randomly flashes and executes on it's own...is this a bug in stock 2.3.4? Also did a factory reset still problem exists.
Anyone else experience the same?
Im on Rogers as well. Had no problems at all...certainly not like this. Then i ended up switching to custom ROM's and what not just to add some enhancements. Try re-flashing? Did you create a backup first?
I had this problem prior to updating to 2.3.4. It has been 12 hours and I have not seen it occur. I am crossing my fingers on this one. Google claims they are investigating the issue. There were a lot of complaints on the Google Mobile forum. It seems random and occurs maybe once or twice a day, sometimes it skips a day.
So I was able to figure out the cause for the search button bug was the Baseband switching to KD1....I reverted back to 2.3.3 with baseband KD1 but problem still occured...once I switched the radio back to KB2 problem was gone....so any ideas on what I should do to get the Stock 2.3.4 update to function on my rogers device without the search button bug? I have not received any OTA notice on my phone yet. Anyone on Rogers receive the OTA?
So after trying to flash 2.3.4 many ways it is evident the baseband of KD1 is causing my Nexus S this search button bug. So now I am using 2.3.4 with the KB2 radio and it is rock solid. Anyone have an idea why only a select few nexus s 9020A phones are doing this after the 2.3.4 update?
Looks like a lot of people with the Canadian version Nexus S 9020A are experiencing the same problem once they upgrade OTA to 2.3.4 .....google is trying to narrow down the problem.
http://www.google.la/support/forum/p/Google+Mobile/thread?hl=en&tid=49e8ca84071d51a4&start=80
I cleared Dalvik cache, did not resolve the issue.
I know downgrading to kb2 would solve a lot of the issues, but then i still have issues with the search bug during navigation.
Let's see if we can figure this out.
Matridom said:
I cleared Dalvik cache, did not resolve the issue.
I know downgrading to kb2 would solve a lot of the issues, but then i still have issues with the search bug during navigation.
Let's see if we can figure this out.
Click to expand...
Click to collapse
Looks to be a confirmed bug in KD1 baseband:
http://mobilesyrup.com/2011/05/23/canadian-nexus-s-experiencing-voice-search-bug/
So your saying since you bought your nexus s with the stock 2.3.3 you have had this issue?....and is the issue worse once you update to 2.3.4 like I have?
Rob
richerob said:
Looks to be a confirmed bug in KD1 baseband:
http://mobilesyrup.com/2011/05/23/canadian-nexus-s-experiencing-voice-search-bug/
So your saying since you bought your nexus s with the stock 2.3.3 you have had this issue?....and is the issue worse once you update to 2.3.4 like I have?
Rob
Click to expand...
Click to collapse
Yup. I need to do more testing but with kb2 I would only get it in gps mode.
Sent from my Nexus S
Hello,
I recently flashed the uckj2 modem with red cwm but was dissatisfied with my phone dropping to 3g signals when it was idle. i didn't make a backup of my original baseband file (unless a cwm backup counts) so when i decided to flash back to the ucke3 modem, i downloaded it from the modem file in the dev forum. my problem is that the network time keeps setting itself to 7 hours ahead of pacific time--the auto update on/off trick works for a few minutes but it goes back after that. also, the data dropping to 3g problem has persisted.
flashing to uckj1 fixes the time problem but the not the 3g problem. reflashing the ucke3 modem doesn't work either. does anyone have other suggestions?
thanks from a n00b
From what I understand, numerous people have been having the same problem with the e3 modem. If you read through the modem forum, I believe some people have toggled the auto update of time on and off NUMEROUS times in a row and it fixed the problem but was temporary. That being said, I don't have a solution, just wanted to let u know you're not alone... I haven't skimmed through that forum recently, but if you do, u might find something new that helps. Sorry I couldn't help more...
Hi all -
I recently updated to the 4.4.3 VzW firmware and upgraded from Viper 1.8.0 to Viper 2.5.0. Since upgrading, I have been having troubles with my hotspot. After being on and other devices have been using it for a bit, my M8 begins to rapidly turn on/off the Data Connection. This doesn't stop and the only way to fix the problem is go into airplane mode and back out again. I figured that I may have had a bad flash, so i tried reflashing clean downloads of both the firmware and a full wipe and reinstall of ViperOne, but still seeing the exact same issue. I seem to be also experiencing a problem where my phone is reporting a 4G connection, but data is disconnected and i cannot get anything over the data channel. Voice works fine. Again, to fix it's a cycle through airplane mode.
I tried applying the changes recommended by for the 4G handoff fix, even though the problem described does not seem to be exactly the same as mine. It did not seem to help, and mae it even harder to get a reliable 4G connection.
http://forum.xda-developers.com/verizon-htc-one-m8/general/verizon-4g-handoff-fix-t2868778
Has anyone else seen anything like this and have any recommendations for a fix?
Just realized this would be better in the troubleshooting forum. Is there a way for me to move it there or does that require a moderator?
Check http://forum.xda-developers.com/verizon-htc-one-m8/help/loss-lte-data-using-ap-t2900047
I have had the same thing, going back to 1.55.605.2 FW does seem to be the fix, I think its something with 4.4.3 FW.
One of the so called improvements is Mobile hotspot connectivity, but maybe that's only with phones that don't use the patched default.xml,
the ones that really pay for the mobile hotspot.
kc6wke said:
I have had the same thing, going back to 1.55.605.2 FW does seem to be the fix, I think its something with 4.4.3 FW.
One of the so called improvements is Mobile hotspot connectivity, but maybe that's only with phones that don't use the patched default.xml,
the ones that really pay for the mobile hotspot.
Click to expand...
Click to collapse
Thanks for the reply - do you have a link for the old firmware, so i can flash and revert back to that?
Also - are you still running Viper 2.x or did you roll back to a prior ROM as well?
After some more searching, i found this link for stock 4.4.2 on VzW, but was wondering if anyone has the firmware only, so don't have to restore recovery, and rom afterwards.
http://forum.xda-developers.com/showthread.php?t=2727831
I certainly can and will do it, if necessary, just would prefer to have the firmware only, if someone has it available. Anyone?
Thanks in advance for the help!
Dave
deh2k7 said:
Thanks for the reply - do you have a link for the old firmware, so i can flash and revert back to that?
Click to expand...
Click to collapse
https://www.androidfilehost.com/?w=files&flid=13966
Dl the one without boot img
Thanks, downloaded and reverted. Long boot times, but things working. Now to give the hotspot a few tests. I'll update with my results.
deh2k7 said:
Thanks, downloaded and reverted. Long boot times, but things working. Now to give the hotspot a few tests. I'll update with my results.
Click to expand...
Click to collapse
initial tests are very promising. hotspot seems to be stable and hasn't dumped the data connection yet. Looks like good old VzW managed to screw up the firmware update as usual. Would be nice if they didn't always to be different. Thank god for these forums and the hardworking devs here!
I spoke too soon. Still seeing the same issue after reverting the FW back to 1.55.605.2. Anyone seeing this? Any thoughts on if reverting back to Viper 1.8 would help?
deh2k7 said:
I spoke too soon. Still seeing the same issue after reverting the FW back to 1.55.605.2. Anyone seeing this? Any thoughts on if reverting back to Viper 1.8 would help?
Click to expand...
Click to collapse
I don't think it is the firmware that is the issue, I think it is the kernel. You should be good going back to Viper 1.8 as it uses an older kernel. I would think you would also be fine using the newer firmware and an older ROM version.
jsaxon2 said:
I don't think it is the firmware that is the issue, I think it is the kernel. You should be good going back to Viper 1.8 as it uses an older kernel. I would think you would also be fine using the newer firmware and an older ROM version.
Click to expand...
Click to collapse
I'm starting to believe this as well, that there's something flaky in the 2.x Viper ROMS for VzW and hotspots, and likely in the kernel. I've already reverted back to the old firmware, and I'm going to go back to a clean 1.7.x full install, then OTA to 1.8. Will update with the results.
deh2k7 said:
I'm starting to believe this as well, that there's something flaky in the 2.x Viper ROMS for VzW and hotspots, and likely in the kernel. I've already reverted back to the old firmware, and I'm going to go back to a clean 1.7.x full install, then OTA to 1.8. Will update with the results.
Click to expand...
Click to collapse
Any luck fixing this issue?
My Nexus 5 which I upgraded from a 5.01 to the 5.1 (stock Google rom, without wipe) has a very big battery problem: the device never reaches deep sleep.
I have some years experience in identifying wakelocks, but this wakelock is new. And the strange thing is: I can't even find a thing on Google. Nothing!
The wakelock is a kernelwakelock (PowerManagerService.Wakelocks). I investigated at partial wakelocks which wakelock it is. It's a wakelock called 'ProxyController'. It's related to the phone process/app.
I wiped cache, tried different Kernel (elementalx). Changed CPU gov, wiped dalvik, changed network, refreshed some settings. Disabled unused apps. I even reinstalled the image and other files through recovery. But nothing helps.
Also I noticed, it might be related, that sometimes my phone reboots or it looses sim and signal. (Which worked perfect in 5.01!). All problems started after 5.1 upgrade.
Ofcourse I can do a full wipe, or revert back or try a custom rom. But I hope it is possible to fix, because besides these weird problems it was / is perfect!
Edit: Important, I couldn't be called either. Also calling someone was difficult and the phone process kept freezing. My phone (and then the phone part) was totally broken! Radio of 5.01 did fix. Read comments below!
Have you tried flashing an older radio.img version and/or a clean flash?
Elluel said:
Have you tried flashing an older radio.img version and/or a clean flash?
Click to expand...
Click to collapse
I tried a clean flash now. I didn't only have a wakelock but nobody could call me either.
Also sometimes the phone process did get frozen.
Now I tried a wipe and totally clean install with other installer (The Google original images and installer!). I did not install any other new unneeded apps. And I still have the problem.
I think I will try an older radio now. Very strange... My phone became unusable after the upgrade from 5.01 to 5.1. This looks to be some major bug.
cognosco said:
I tried a clean flash now. I didn't only have a wakelock but nobody could call me either.
Also sometimes the phone process did get frozen.
Now I tried a wipe and totally clean install with other installer (The Google original images and installer!). I did not install any other new unneeded apps. And I still have the problem.
I think I will try an older radio now. Very strange... My phone became unusable after the upgrade from 5.01 to 5.1. This looks to be some major bug.
Click to expand...
Click to collapse
If it happens with a completely clean flash with nothing installed, and with every radio version, then it could be a hardware problem.
But yeah, try an older radio version.
Elluel said:
If it happens with a completely clean flash with nothing installed, and with every radio version, then it could be a hardware problem.
But yeah, try an older radio version.
Click to expand...
Click to collapse
Yes I fear that too.
However, it started immediately after the 5.1 upgrade, before all was good...
It also seems there might be a link with screenoff/standby. When it's in standby and I switch the device on I see it has no connection or is reconnecting. As if something goes wrong with the connection then. Maybe important information.
I will investigate further. Ofcourse all new tips, ideas and infos are welcome. I will also keep you updated.
Update:
Flashed 5.01 radio into my 5.1. Now it SEEMS to be fixed. Phone goes to deep sleep, I can call people without crashing and I can be called. For now. But don't cheer to early, I have only tested for 10 minutes.
So it seems to be something completely wrong in this radio in combination with my device or simcard or provider. I am using Vodafone NL.
Update: a few days later. Running 5.1 rom with 5.01 radio and all seems ok and fixed!
cognosco said:
Update:
Flashed 5.01 radio into my 5.1. Now it SEEMS to be fixed. Phone goes to deep sleep, I can call people without crashing and I can be called. For now. But don't cheer to early, I have only tested for 10 minutes.
So it seems to be something completely wrong in this radio in combination with my device or simcard or provider. I am using Vodafone NL.
Click to expand...
Click to collapse
Hi,
I'm having exactly the same problem. Did the "new" radio fix it? Which radio did you flash?
Thanks,
Regards,
DarkSorcerer said:
Hi,
I'm having exactly the same problem. Did the "new" radio fix it? Which radio did you flash?
Thanks,
Regards,
Click to expand...
Click to collapse
Hello. I am running this Radio (2.0.50.2.22) since my last post, A couple of days. I am experiencing no problems as far as I can tell. It seems to work well and the big problems seem to be gone.
I can advise you to flash this Radio from the 5.01 packages. Big chance your problems will be fixed.
Strange that there is only one other person for now. I am thinking what we could have in common. What is your provider?
cognosco said:
Hello. I am running this Radio (2.0.50.2.22) since my last post, A couple of days. I am experiencing no problems as far as I can tell. It seems to work well and the big problems seem to be gone.
I can advise you to flash this Radio from the 5.01 packages. Big chance your problems will be fixed.
Strange that there is only one other person for now. I am thinking what we could have in common. What is your provider?
Click to expand...
Click to collapse
Hi,
Thank you for your quick answer. I'll try it first thing in the morning.
It is weird indeed.. My provider is the equivalent of Orange. As with you, it only started to happen after the update to 5.1.
I'll report back. Thanks!
So ever since yesterday I've been able to use WiFi. I was chromecasting something and while it was casting my phone went through a reboot, thought nothing of it since its happened lately. Well i think it did it a few times. Well I check my phone after my show is over and my WiFi is off., and I can't turn it on. I rooted my phone last night since it was unlocked already from when I had it rooted before. It's on Android 6.0 right now. I was just wondering if anyone had any ideas of how to fix it. I was getting a logcat error in reference to the wifistatemachine.
Did you try flashing an older stock rom?
I have a phone with the same problem and it believe it is a hardware problem because stock and custom kk, lp, and M ROMs do not solve the problem. After swapping out the motherboard, everything was fine.
I have not yet. I was trying to create a nandroid backup first, but NRT doesn't seem to want to let me do that because i don't have a modified boot image.