Related
Hello,
I recently flashed the newest CM5.02 and it was fine. Then, yesterday in the middle of the day I noticed that my data had said E, which normally happens, but it never changed back to H (or 3g) no matter where I went, even to spots that I knew had full bars. Im in norcal, anyone else having this problem?
Yeah, mine does this all the time and I'm still stock. Are you on the newest radio as well as newest CM? This is my biggest radio issue.
Here at work where I don't get solid reception I see a lot of fluctuation HSPA to UTMS to EDGE and even down to GPRS sometimes which is fine, I am in a pretty solid bldg and my MT3G would slip as well. Issue is I can't get it back without doing what you did or switching between WCDMA Only then back to WCDMA Preferred basically anything to reset the radio. I notice this happens without fail if I take a call on it. I will lose all data connection until I hang up.
As well, when all this starts up real bad the phone will heat up quite a bit. When I leave my office things appear to be fine.
Didn't have this problem with the stock ROM
j2eubank said:
Yeah, mine does this all the time and I'm still stock. Are you on the newest radio as well as newest CM? This is my biggest radio issue.
Click to expand...
Click to collapse
I'm using CyanogenMod 5.0.2 and radio 4.04.00.03_2 (from Settings -> About phone -> Baseband version), but I did NOT have this problem with the stock radio after the OTA update (4.03.00.21_2).
I posted a poll about this at Stuck on EDGE with CyanogenMod 5.0.2 until reboot.
dandv said:
I'm using CyanogenMod 5.0.2 and radio 4.04.00.03_2 (from Settings -> About phone -> Baseband version), but I did NOT have this problem with the stock radio after the OTA update (4.03.00.21_2).
I posted a poll about this at Stuck on EDGE with CyanogenMod 5.0.2 until reboot.
Click to expand...
Click to collapse
my basband reads..
32.24.00.22U_4.03.00.21_2
How did you fix the issue in the first post?
badnewswrx said:
my basband reads..
32.24.00.22U_4.03.00.21_2
Click to expand...
Click to collapse
That means you have the old ROM. The new one can be found on the CM5.0.2 page.
Also, in your first post, can you mention how you fixed your issue?
FYI: Reverting back to the old radio did not fix the issue.
dandv said:
That means you have the old ROM. The new one can be found on the CM5.0.2 page.
Also, in your first post, can you mention how you fixed your issue?
Click to expand...
Click to collapse
I thought i fixed it by forcing it to search for networks then selecting t mobile, this was not a good solution as if it dropped it would not go back.
After upgrading to ROM 3.14.531.1 my wifi connection disconnects frequently.
Anyone have this problem or know of updated wireless drivers?
I am having the exact same problem.
I used to get connection to the router throughout my house and now it is spotty at best with the new update.
I also noticed that my range is cut by 1/4 and signal strength is very sporadic
tjensen said:
I also noticed that my range is cut by 1/4 and signal strength is very sporadic
Click to expand...
Click to collapse
Someone suggested flashing to the radio that you were using before. Anyone tried that?
I haven't (I have not even installed HPSL), but here is the rub...my phone signal seems better...my connection to the router is worse!
Not sure if that is an equal trade-off or not (also not sure if I am accurate on the phone signal though)...(what's my name again?_)
Camusa said:
I haven't (I have not even installed HPSL), but here is the rub...my phone signal seems better...my connection to the router is worse!
Not sure if that is an equal trade-off or not (also not sure if I am accurate on the phone signal though)...(what's my name again?_)
Click to expand...
Click to collapse
Or just try a completely different radio all together. Just make sure it's compatible... HSPL3 is easy as hell.
I observed the exact same problem with WIFI and reverted back to 2.13 ROM.... WIFI worked fine since!
shirreer said:
I observed the exact same problem with WIFI and reverted back to 2.13 ROM.... WIFI worked fine since!
Click to expand...
Click to collapse
I am seriously debating this.
The WIFI is ridiculous now.
The device does seem smoother though and battery life is greatly increased. Where I would usually be around 30% in the day I am at 50%!
Maybe I should just install an earlier radio, but I am nervous about doing that!
Battery life question
Fit those reporting implement in battery life, do you all keep all your radios on (bluetooth, wifi and 3g) all the time? I generally keep bluetooth off because it haas been giving me an additional half day of usage and, staying with this, I am not seeing any improvements in battery life. if anything, my battery life may actually be slightly worse with the new ROM.
I do have direct push email set to deliver instantaneously.
Also, with regards wifi, not seeing a signal issue but wifi drops after some period of inactivity. This was not the case with the previous radio. Like others, I am also very interested to see if anyone has rolled back to the previous radio with favorable results .
Camusa said:
I am seriously debating this.
The WIFI is ridiculous now.
The device does seem smoother though and battery life is greatly increased. Where I would usually be around 30% in the day I am at 50%!
Maybe I should just install an earlier radio, but I am nervous about doing that!
Click to expand...
Click to collapse
HardSPL3 and flashing the radio is so simple. I promise... Don't go back to 2.13, just HSPL and flash a radio. There is a thread in rom development that has all of the TMOUS radios... Just flash the radio back to 2.10.50.26. That's the stock radio from 2.13 Rom. If you want to private message me, I'd be glad to give you the step by step, but I learned what I know from reading threads on this site.
bugmenever said:
Fit those reporting implement in battery life, do you all keep all your radios on (bluetooth, wifi and 3g) all the time? I generally keep bluetooth off because it haas been giving me an additional half day of usage and, staying with this, I am not seeing any improvements in battery life. if anything, my battery life may actually be slightly worse with the new ROM.
I do have direct push email set to deliver instantaneously.
Also, with regards wifi, not seeing a signal issue but wifi drops after some period of inactivity. This was not the case with the previous radio. Like others, I am also very interested to see if anyone has rolled back to the previous radio with favorable results .
Click to expand...
Click to collapse
I do think the 2.15 radio is setup to disable your data if you are using wifi, and maybe as you suggested, turn off wifi if it's been idle for a while. Probably a way to save battery life... I had switched to the 2.10.50.26 radio that comes with the 2.13 ROM because the battery life wasn't great with the 2.15 Radio, but then I had also noticed before I flashed back to 2.10 Radio that I was getting full Edge at my buddy's house, where I normally have no signal at all. I decided to switch back to 2.15 radio and test the theory that the battery life gets better as the Rom "settles"... I'm not totally buying it because logically it doesn't make sense to me, but I'll try anything. That's how you learn stuff.
Thanks for the informative post, crisisinthecity! Keep its posted on erhart you find.
I have tried to adjust the power savings in advanced settings hoping that more power would keep the signal from disconnecting and give me better signal strength. Did not seem to have any effect
Hey guys.
I've got exactly same problem with the new ROM here in Holland. I am not T-mobile user.
I've posted my message on forum.xda-developers.com/showthread.php?p=8709630&posted=1#post8709630[/url] but apparently nobody had similar issue there.
I've also contacted HTC support. Of course they started from giving me instructions how to setup WiFi. Finally after several iterations they realized what problem is about. Just today I had long conversation with them and they said that this issue is happened with only me but "they really want to understand the issue and try to help".
They were suggesting me to install the new ROM again and try to test in on different WiFi network - apparently they reluctant to do it themselves properly. I said I don't wan't do it as I don't wan't to waste my time on that and I want them figure it out themselves iby having more complains about new ROM.
I've bought theory that the issue is in radio and tried to install new ROM on top of old ROM with SSPL_RUU. It worked but even with old radio+new ROM ("only flash Splashe and OS image") WiFi issue was not fixed.
I am not going to do any experiments with my device until I will be sure the issue is completely resolved. Very disappointed indeed. Very happy with old good ROM 1.66.
I was having this problem until a few minutes ago since I flashed the 3.14 rom. When I flashed the ROm from january 25 ... UK ... It's the 1.66 ... the issue with my HD2 stopped ... just finsihing the setup of my phone again ... and the wifi is working perfectly.
I was just about to adopt the first procedures to send my the goddam hd2 to
fix by htc, when i decided to do this test.
man, I can't wait to get rid of this phone
Juliette said:
Hey guys.
I've got exactly same problem with the new ROM here in Holland. I am not T-mobile user.
I've posted my message on forum.xda-developers.com/showthread.php?p=8709630&posted=1#post8709630[/url] but apparently nobody had similar issue there.
I've also contacted HTC support. Of course they started from giving me instructions how to setup WiFi. Finally after several iterations they realized what problem is about. Just today I had long conversation with them and they said that this issue is happened with only me but "they really want to understand the issue and try to help".
They were suggesting me to install the new ROM again and try to test in on different WiFi network - apparently they reluctant to do it themselves properly. I said I don't wan't do it as I don't wan't to waste my time on that and I want them figure it out themselves iby having more complains about new ROM.
I've bought theory that the issue is in radio and tried to install new ROM on top of old ROM with SSPL_RUU. It worked but even with old radio+new ROM ("only flash Splashe and OS image") WiFi issue was not fixed.
I am not going to do any experiments with my device until I will be sure the issue is completely resolved. Very disappointed indeed. Very happy with old good ROM 1.66.
Click to expand...
Click to collapse
Odd...I have been having the same issue and in contacting T-mo and HTC they both admit that this is a known issue and that they are working on it (no mention of whetehr or not they will release a new ROM to address and I doubt that they will).
yep, been having the same issue with 3.14 ROM, WiFi disconnects frequently.
this is not seen in previous versions of ROM. must be a botched job from HTC on the WiFi drivers.
this problem only happens with certain WiFi Access Points. So not everyone will experience this problem. that's why a lot of people can't relate to what we are experiencing.
Damn HTC.
I'm pretty sure this is not a problem of Radio, but rather the WiFi drivers in the ROM.
EDIT: The problem is still occurring. I thought it was fixed.
Myself and a couple other people experienced stange 3g connection problems while running the cm7 nightlies (among other ROMs) with the new HBOOT-0.35.0017. I know it's been said that HBOOT shouldn't have anything to do with your data connection but nonetheless it is causing problems.
Follow the instructions on this thread to downgrade (AMOLED NEXUS OWNERS ONLY!):
http://forum.xda-developers.com/showthread.php?t=726258
After downgrading back to HBOOT 0.33.0012 my connection problems vanished (still running the same CM7 nightly)
Credit goes to user Prgopala for noticing this and posting here:
http://forum.xda-developers.com/showpost.php?p=10902092&postcount=12533
Thanks!
I'm sorry to tell you, but hboot has NOTHING to do with the radio part of the phone: it controls the system partitions table and boots the system... nothing else, it doesn't even touch the RAM parts dedicated to the hardware, the kernel does it.
I almost made up my mind to downgrade until seen the edit part. 3g part of signal is very very frustrating experience on my side while call part rarely let it down. Also signal always in close to100 reading while my Acer liquid on T Mobile stays to perfect 75-80 reading.
I'm on HBOOT-0.35.0017 and sometimes I get x gray bars but after it picks up signal and gets connect to H it seem to work fine. Until I lose the signal or I switch to airplane, etc. Takes a while sometimes to get back signal or the H.
I did notice that when the screen goes off my download stops or sometimes when I download certain files it stops right away. I been updating roms so not sure if it related to them, but overall its been like that.
Tiberx said:
I'm on HBOOT-0.35.0017 and sometimes I get x gray bars but after it picks up signal and gets connect to H it seem to work fine. Until I lose the signal or I switch to airplane, etc. Takes a while sometimes to get back signal or the H.
I did notice that when the screen goes off my download stops or sometimes when I download certain files it stops right away. I been updating roms so not sure if it related to them, but overall its been like that.
Click to expand...
Click to collapse
yes screen off downloading stopping is quite annoying...
I dunno but since I upgraded my Hboot and used CM7... my data sucks. It will work then not work. I typically have to reset to get it back. Even switching in and out of airplane mode will not work.
And by 3G I mean my data connection. I'll have full bars and 3G coverage... but no data from the browser, no pings, no online apps, nothing. Seems like the only way to fix it is to reset the phone.
I also noticed my signal is noticeably less at home. Typically I have full bars but now I notice that it's been dropping out and bouncing.
Could be a carrier issue. But I haven't upgraded my radio since 5.08 first came out. I updated my HBoot for the early builds of GB. So I'm willing to test out this theory.
lol, hboot has nothing to do with the phone's radio. The radio version does.
If you're having a problem with the radio (voice/data) then you should look at the radio version you're running.
Again, hboot has nothing to do with your issue.
Ive had the data sticking problem since I got my n1. Remember reading somewhere that if you go into settings - wireless networks - mobile networks - network operators, when it finishes searching select "automatically select". I got T-Mobile & it works for me until the next time I flash a new rom.
FYI when I was on CM 6.1 I had your problems. I then switched to MicroMod777's Gingerbread and those problems disappeared. I've now flashed Enmother's TheOfficial Nexus1 and I'm testing. Absolutely a ROM problem.
elegos said:
FYI when I was on CM 6.1 I had your problems. I then switched to MicroMod777's Gingerbread and those problems disappeared. I've now flashed Enmother's TheOfficial Nexus1 and I'm testing. Absolutely a ROM problem.
Click to expand...
Click to collapse
Kinda the opposite for me. No data issues when i tried CM 6.1.1 but on MM Gingerbread i had no data connection at all!
"You pays your money and you takes your chances"
then it must the crap of our carriers
DirkGently1 said:
Kinda the opposite for me. No data issues when i tried CM 6.1.1 but on MM Gingerbread i had no data connection at all!
"You pays your money and you takes your chances"
Click to expand...
Click to collapse
Same here. I tried MM and nothing worked! lol. So I went back to the latest CM7 (#24). I'm not sure what the problem is. Now I'm on an older HBoot and an older Radio. I shoulda just left 5.12 and .35 on there.
Once I get my phone pieced back together, I may try one of the older CM6.1 roms to see if that fixes it. I think we are all using Gingerbread roms here, no? Perhaps that just is an issue that comes with it.
youareme7 said:
EDIT: The problem is still occurring. I thought it was fixed.
Myself and a couple other people experienced stange 3g connection problems while running the cm7 nightlies (among other ROMs) with the new HBOOT-0.35.0017. I know it's been said that HBOOT shouldn't have anything to do with your data connection but nonetheless it is causing problems.
Follow the instructions on this thread to downgrade (AMOLED NEXUS OWNERS ONLY!):
http://forum.xda-developers.com/showthread.php?t=726258
After downgrading back to HBOOT 0.33.0012 my connection problems vanished (still running the same CM7 nightly)
Credit goes to user Prgopala for noticing this and posting here:
http://forum.xda-developers.com/showpost.php?p=10902092&postcount=12533
Thanks!
Click to expand...
Click to collapse
Same issue here, wondering if this hboot is incompatible w/ my old radio.
just received my new nightly, will give this method a try as soon as i upgraded.
thanks!
-- just saw the updated post, thanks anyway
Perhaps the OP should change the title and original message to exclude the HBoot details as the problem is with Data connection.
This will let us continue discussion about the data connection problem that we are, I am at least, experiencing.
Using CM7 #24 from 1/30, it seems to be less of an issue. I notice that I'll have 3G and full bars, but no data will work until it changes to an "H". Seems like it might just be the rom. The latest nightly seems to correct the issue better then before. Now if I open a browser, after 30s-1minute, it will start chugging along.
I'm New to the forums here everyone.
Greetings!
I'm running NRD90U but I'm experiencing some issues with the recent radio update that came with nougat on Verizon. I've searched everywhere on the xda forums and found suggestions to others experiencing similar issues (simultaneous voice and data). With the 03.61 radio, everything worked just fine whereas with 03.72 I have to toggle airplane mode after every reboot in order to have simultaneous voice and data. I have performed all of the suggested things to no avail. HD voice is enabled on my line and I've tried taking it off and putting it back on. Enhanced LTE is set to on and I've toggled that. I've factory data reset. I've wiped cache. I've Tested SIM in another Verizon device and it works fine. I've Put another Verizon SIM in my device and still have the issue. I even gotten a new replacement device. I've sideloaded OTAs. I've flashed factory images. I've literally tried everything suggested here.
All said, I'm wondering if it's possible to flash the older 03.61 radio while keeping everything otherwise the same on my phone with stock Nougat-NRD90U.
I would appreciate input.
Thanks.
[email protected] said:
I'm New to the forums here everyone.
Greetings!
I'm running NRD90U but I'm experiencing some issues with the recent radio update that came with nougat on Verizon. I've searched everywhere on the xda forums and found suggestions to others experiencing similar issues (simultaneous voice and data). With the 03.61 radio, everything worked just fine whereas with 03.72 I have to toggle airplane mode after every reboot in order to have simultaneous voice and data. I have performed all of the suggested things to no avail. HD voice is enabled on my line and I've tried taking it off and putting it back on. Enhanced LTE is set to on and I've toggled that. I've factory data reset. I've wiped cache. I've Tested SIM in another Verizon device and it works fine. I've Put another Verizon SIM in my device and still have the issue. I even gotten a new replacement device. I've sideloaded OTAs. I've flashed factory images. I've literally tried everything suggested here.
All said, I'm wondering if it's possible to flash the older 03.61 radio while keeping everything otherwise the same on my phone with stock Nougat-NRD90U.
I would appreciate input.
Thanks.
Click to expand...
Click to collapse
If you are bootloader unlocked, you can fastboot flash any radio.img you want. If you are not bootloader unlocked, no you can't. The radio.img is universal btw, not specific to a carrier.
Edit: the guide below will help you unlock the bootloader and learn fastboot if you are unfamiliar.
http://forum.xda-developers.com/showthread.php?t=3206928
Sent from my Nexus 5X using Tapatalk
Thanks. I will do that. I appreciate the help.
Is this a problem for other Verizon users too? If so, I just won't upgrade the radio firmware on mine either.
I would highly suspect that the problem is for everybody on Verizon especially since I replaced my device and did all this SIM card changes and things. It is very unnoticeable in that the only time you experience it or see it is if you are making a call on the new nougat radio 03.72, you will see the LTE icon disappear as soon as you make your call, regardless of whether you are on an 'HD call' or not. If you are on the older radio 03.61 that is on marshmallow, then you never experience that problem, ever, ever. Everything is perfect with that "radio." I've done a lot of testing on it, as I said, up to replacing my device, all to no avail. unless using 03.61 which is again, perfect. I wouldn't change if you can avoid it. If you do get the nougat radio though (03.72), it's a nuisance because after the majority of reboots overall, you will come up with everything normal-'looking' with the LTE icon there but when trying to make a call it will disappear and you'll have an exclamation point there until you hang up from the call and LTE comes right back. (unless you're on wifi off course in which case none of this apples). The solution if you find yourself with the 03.72 nougat radio with this happening, is to toggle airplane mode and then you're good to go until the next time you have to reboot. I always check afterwards by calling voicemail to make sure the LTE icon stays while on the call. It will disappear immediately.
I'm going to assume there is some sort of an "initial-boot-handshake" that's not taking place correctly, but DOES communicate correctly coming out of airplane mode when the device is already booted.
Regards
Edit: This may be a regional VZW issue and not a phone or baseband issue.
Verizon has had issues where I live for more than a week.
I live in Northern Ca and they just sorted things out.
Funny, I flashed the Nougat radio on top of 6.x to see if my issue was fixed.
It's not the radio. Mine is finally stable. Not sure what VZW did.
tech_head
Everything was working fine on mine with the marshmallow radio. I didn't have an issue until I updated to nougat.
Hearing what happened with yours makes me think that it's a regional Verizon thing. Hopefully they will fix soon. I'm not holding my breath because it's been about a month here in Central Kentucky
I'm glad yours is working now man.
Cheers!
I'm having a similar problem for the last couple days after flashing the latest update. I may try stepping back to the older radio to see if that fixes my problem. I just hope it doesn't affect my bluetooth, as that's finally working fine again.
heffe2001 said:
I'm having a similar problem for the last couple days after flashing the latest update. I may try stepping back to the older radio to see if that fixes my problem. I just hope it doesn't affect my bluetooth, as that's finally working fine again.
Click to expand...
Click to collapse
Best of luck. Let us know how it goes if you get the chance. Thanks!
Holy crap, I thought it was just me! I did the exact same things (minus an RMA) as the OP to fix the issue with no luck, even downgrading to MTC20F and upgrading to MTC20L and finally Nougat, just to make sure something wasn't getting jacked in the flashing process. I spent an hour on the phone last night w/ a tier 2 tech guys from Verizon and the only issue he could see was that my PRL had an update for my SIM which should happen automatically. He pushed it through from their end but it didn't fix the issue. Normally I don't care about browsing/downloading when I'm on the phone since I hate talking on the phone and get off as soon as possible but it causes another problem which is not acceptable: if I am browsing chrome or doing anything with data, incoming calls go straight to voicemail. Tried switching the phone from "global" to "LTE/CDMA" with no luck-a reboot always kills simultaneous voice and data. I can rule out this being a Verizon issue on my end as when I flashed the MM images to update via OTA this morning, all worked perfectly fine.
Edit: I have called multiple people in my area that are on VZW after having them reboot their phones and all of them maintained simultaneous voice and data. I think it is safe to state that this issue is software/device specific.
bjoostema said:
Holy crap, I thought it was just me! I did the exact same things (minus an RMA) as the OP to fix the issue with no luck, even downgrading to MTC20F and upgrading to MTC20L and finally Nougat, just to make sure something wasn't getting jacked in the flashing process. I spent an hour on the phone last night w/ a tier 2 tech guys from Verizon and the only issue he could see was that my PRL had an update for my SIM which should happen automatically. He pushed it through from their end but it didn't fix the issue. Normally I don't care about browsing/downloading when I'm on the phone since I hate talking on the phone and get off as soon as possible but it causes another problem which is not acceptable: if I am browsing chrome or doing anything with data, incoming calls go straight to voicemail. Tried switching the phone from "global" to "LTE/CDMA" with no luck-a reboot always kills simultaneous voice and data. I can rule out this being a Verizon issue on my end as when I flashed the MM images to update via OTA this morning, all worked perfectly fine.
Edit: I have called multiple people in my area that are on VZW after having them reboot their phones and all of them maintained simultaneous voice and data. I think it is safe to state that this issue is software/device specific.
Click to expand...
Click to collapse
I have done and agree with what you said - other devices(non NEXUS 6p) work fine and 6p works fine on marshmallow. However, tech_head posted above that his I'd all good now and that it was a Verizon issue. I'm not sure where you live but based on tech_head's post, I can't rule out VZW as the problem. One thing is for sure it is an issue here in Central Kentucky on the two NEXUS 6ps that I have had and tried EVERYTHING, like you, on both of them to no avail without marshmallow radio. I haven't tried flashing marshmallow radio on top of nougat. I may just wait and see if VZW or Google work something out to fix it soon with a possible update. Not holding my breath but I believe it will eventually get fixed in the future, OFFICIALLY.
Thanks man.
I appreciate your input.
**
As mentioned earlier in the thread, the radio is independent of the OS version, so why not take 1 or 2 minutes and flash an earlier radio? There is a radio / modem repository thread on XDA with all versions you can just grab and try out. Literally takes less than a minute and if you don't like the results, then just flash it right back. I use Fastboot, but TWRP, FF, NRT, etc. all work equally well. You may also post what you find under "Phone Settings" when typing " *#*#4636#*#* " into the dialer. Report back on your findings.
Here are the screenshot links for my phone settings.
Thanks
OP
http://forum.xda-developers.com/attachment.php?attachmentid=3882483&stc=1&d=1474502181
http://forum.xda-developers.com/attachment.php?attachmentid=3882482&stc=1&d=1474502181
tech_head said:
Verizon has had issues where I live for more than a week.
I live in Northern Ca and they just sorted things out.
Funny, I flashed the Nougat radio on top of 6.x to see if my issue was fixed.
It's not the radio. Mine is finally stable. Not sure what VZW did.
Click to expand...
Click to collapse
Are You running stock nougat now. If so, what is your simultaneous voice and data status with respect to my post.
Thanks
OP
[email protected] said:
I have done and agree with what you said - other devices(non NEXUS 6p) work fine and 6p works fine on marshmallow. However, tech_head posted above that his I'd all good now and that it was a Verizon issue. I'm not sure where you live but based on tech_head's post, I can't rule out VZW as the problem. One thing is for sure it is an issue here in Central Kentucky on the two NEXUS 6ps that I have had and tried EVERYTHING, like you, on both of them to no avail without marshmallow radio. I haven't tried flashing marshmallow radio on top of nougat. I may just wait and see if VZW or Google work something out to fix it soon with a possible update. Not holding my breath but I believe it will eventually get fixed in the future, OFFICIALLY.
Thanks man.
I appreciate your input.
Click to expand...
Click to collapse
No problem bud! I haven't flashed another radio yet either. I will report back after I test a few more things.
Has anyone determined the cause of the problem? Was it the radio firmware after all? There seem to be conflicting answers here.
chaoticyeshua said:
Has anyone determined the cause of the problem? Was it the radio firmware after all? There seem to be conflicting answers here.
Click to expand...
Click to collapse
It is still kind of up in the air. What I do know is that there is a software incompatibility somewhere within nougat here in Lexington, KY, at least. I assume it's the radio software but I'm not certain. I'm not bootloader unlocked at this point so I haven't yet tried to flash marshmallow radio on to stock nougat. I will probably try this in a few days when I have the time to deal with the factory reset it involves. Please refer back to the original post for questions about my reasoning.
It's quite interesting, the problem, as everything with stock nougat - voice and data-wise, works just like marshmallow after I toggle airplane mode after reboot. With marshmallow, it just worked. Very weird. But given I can just toggle airplane mode 1 time for every time I boot, it's just a slight nuisance. Once I toggle airplane mode, everything is good just like marshmallow, as if nothing was ever wrong. It could be something about the boot sequence. It's very interesting. I'm open to ideas at this point.
Thanks.
My 2¢
When i was on 6.0.1 didn't have and issue with radio. i flashed the 7.0 radio while still on 6.0.1, still no issues.
Then i flashed 7.0 OS and that's when the issue started and it was only affecting upload speed download was great. Then i flashed the last radio from 6.0.1 and the issue went away.
P.S.
the data going off during a call is VZW. i had to call to have them fix this even before 7.0 they dont like the fact that we are using a non vzw branded cell.
I'm back on 6.0.1, never signed on to be a beta tester for 7.0?. These days its about profit and quantity and the hell with quality
Sent from my Nexus 6P using XDA-Developers mobile app
spjetrovic said:
My 2¢
When i was on 6.0.1 didn't have and issue with radio. i flashed the 7.0 radio while still on 6.0.1, still no issues.
Then i flashed 7.0 OS and that's when the issue started and it was only affecting upload speed download was great. Then i flashed the last radio from 6.0.1 and the issue went away.
P.S.
the data going off during a call is VZW. i had to call to have them fix this even before 7.0 they dont like the fact that we are using a non vzw branded cell.
I'm back on 6.0.1, never signed on to be a beta tester for 7.0?. These days its about profit and quantity and the hell with quality
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
I appreciate your input. It doesn't sound like our issues are quite the same. I'm not sure though.
What is it that Verizon did for you. That may be the answer to my problems.
Thanks. Best Regsrds.
Hi,
Since I updated my nexus 6p to 7.1.1 I experiencing a lot of network drops and call issues.
Does anyone have the same problem?
Not at all. What baseband version is showing in settings? angler-03.78 is the current baseband. Other than that, confirm your APN profile is the same as it was before you had issues.
3.78 here, and same APN.
The problem still persist after reflashing the stock firmware (trough flashfire)
asafba said:
Hi,
Since I updated my nexus 6p to 7.1.1 I experiencing a lot of network drops and call issues.
Does anyone have the same problem?
Click to expand...
Click to collapse
Yes, I've had several connectivity issues regarding LTE. Multiple instances of getting the "LTE" logo showing pretty good signal strength but with the little "x" next to it showing there is no actual connection.
I've also had some calling weirdness where I try to take an in coming call but other person can't hear me. When I try to call them back it goes straight from "dialing" to hangup right away.
I sideloaded the 7.1.1 update and I'm on Verizon so I'm not terribly surprised there are some issues. I don't have any fixes or suggestions, just letting you know you're not alone
Haha thanks, I'm in Israeli carrier so if it a carrier related issues, it's a big problem for me.
Can we use an older modem?
asafba said:
Haha thanks, I'm in Israeli carrier so if it a carrier related issues, it's a big problem for me.
Can we use an older modem?
Click to expand...
Click to collapse
Nope that might cause bootloops
I have the same problem.. After a fresh reboot first few minutes the phone just drops and connects to signal all the time. Can't even make a 10 second call (sometimes it manages to get call started and then just cuts off as it drops signal). Then after a few minutes phone shows full signal all the time but it cant make/recieve a call(it says number not available)... tried everything that I could on software level so I guess its something wrong with the antenna in my phone. I'm taking it back to the shop where I bought it from for a repair.
Vref said:
Yes, I've had several connectivity issues regarding LTE. Multiple instances of getting the "LTE" logo showing pretty good signal strength but with the little "x" next to it showing there is no actual connection.
I've also had some calling weirdness where I try to take an in coming call but other person can't hear me. When I try to call them back it goes straight from "dialing" to hangup right away.
I sideloaded the 7.1.1 update and I'm on Verizon so I'm not terribly surprised there are some issues. I don't have any fixes or suggestions, just letting you know you're not alone
Click to expand...
Click to collapse
Some people on Verizon in the Cortex ROM thread reported that flashing radio 3.75 fixed their connectivity issues. I didn't have this issue and am using the latest radio so I have no personal experience with this fix.
---------- Post added at 12:16 AM ---------- Previous post was at 12:09 AM ----------
asafba said:
Haha thanks, I'm in Israeli carrier so if it a carrier related issues, it's a big problem for me.
Can we use an older modem?
Click to expand...
Click to collapse
Some people in Cortex Rom thread had similar issues and reported that flashing radio 3.75 fixed the problem. Cortex ROM is stock based so if it didn't cause a boot loop for them it probably won't cause one for you--but that might depend on the ROM you are running and whether or not your bootloader is locked. I'm running the latest radio so I can't personally vouch for this as a fix.
jhs39 said:
Some people on Verizon in the Cortex ROM thread reported that flashing radio 3.75 fixed their connectivity issues. I didn't have this issue and am using the latest radio so I have no personal experience with this fix.
---------- Post added at 12:16 AM ---------- Previous post was at 12:09 AM ----------
Some people in Cortex Rom thread had similar issues and reported that flashing radio 3.75 fixed the problem. Cortex ROM is stock based so if it didn't cause a boot loop for them it probably won't cause one for you--but that might depend on the ROM you are running and whether or not your bootloader is locked. I'm running the latest radio so I can't personally vouch for this as a fix.
Click to expand...
Click to collapse
Appreciate it. Unless you can flash just the radio with the bootloader locked it's gonna be a no go for me. Had to unroot, relock, and go back to straight outta the box stock when I got hired at my new company.
Sent from my Nexus 6P using XDA-Developers mobile app