Database Users

Bugs still present in Froyo 3.21.605.1 / Radio 2.15.00.07.28

Like many others, after updating to the leaked radio 2.15.00.07.28 a few weeks ago, market installs began hanging, and 3G didn't always start after powering on. The fix for the market hang is to manually stop and restart the download/install, and the fix for 3G is to enter and exit airplane mode.
Surprisingly, after RUU'ing with "RUU_Incredible_C_Froyo_VERIZON_WWE_3.21.605.1_Radi o_2.15.00.07.28", and then later wiping and applying "Incredible Sense/Froyo v3.21.605.1 *Official Release* (100% stock, rooted)" via Clockworkmod, these bugs are still present!!
If you originally installed the leaked radio, then updated to the "official" OTA, do you have these bugs?
If you never installed the leaked radio, but have installed (or received) the official OTA, are you seeing these bugs?

I'm still running the 7/27 release with some of the fixes. Baseband is 2.05.00.06.11.
Sometimes my 3G doesn't turn on, so I empathize. Rarely will I have that market problem, but it will sometimes happen.
....makes me think it isn't neccessarily a problem with the official release or the newer radio.....

I never installed early leaks or anything until I did the RUU file the other day. I do not experience either of those bugs.

If you did the RUU, then its as if you started with a stock Incredible.
For the 3G issue, what is your wifi sleep policy set at? Is it never?
Sent from my ADR6300 using XDA App

oturn said:
Like many others, after updating to the leaked radio 2.15.00.07.28 a few weeks ago, market installs began hanging, and 3G didn't always start after powering on. The fix for the market hang is to manually stop and restart the download/install, and the fix for 3G is to enter and exit airplane mode.
Surprisingly, after RUU'ing with "RUU_Incredible_C_Froyo_VERIZON_WWE_3.21.605.1_Radi o_2.15.00.07.28", and then later wiping and applying "Incredible Sense/Froyo v3.21.605.1 *Official Release* (100% stock, rooted)" via Clockworkmod, these bugs are still present!!
If you originally installed the leaked radio, then updated to the "official" OTA, do you have these bugs?
If you never installed the leaked radio, but have installed (or received) the official OTA, are you seeing these bugs?
Click to expand...
Click to collapse
After you flash the RUU it is always good to do a factory reset. I always do that since WinMo days and never have the bugs.

When I was on the leaked 2.15x radio and 2.2 I never had the 3G problem, but ALL the time, my market would hang like that and it would take 2-3 stop and starts to finally get the download going.

It's definitely the 2.15 radio, and not the OS. These problems occur after a fresh RUU, with a completely clean OS, both stock, and rooted. Also, Wi-Fi is off.
As a test, I restored back to the stock radio/rom following "[GUIDES] Root, nand unlock, radio update, Froyo 2.2 update, Restore stock radio/rom". While back to stock 2.1, and the 1.x radio, every single time after powering on the phone, the 3G icon appears after less than a minute, and data works fine. Again, with the original radio, 3G starts every time.
Next, I ran "RUU_Incredible_C_Froyo_VERIZON_WWE_3.21.605.1_Rad i o_2.15.00.07.28" and repeated the test. At least 50% of the time after powering on, the 3G icon doesn't appear, and there is no data...until airplane mode is turned on, then off.
Could someone running the "official OTA" please run this test? Make sure your Wi-Fi is off, then power off your phone. Wait a few seconds, and power it back on. Don't do anything after boot until the screen times out. Next, check for the 3G icon, and check data by starting your browser. Repeat this at least 3 times, and let me know the results!
I'm obviously VERY interested if my phone has a problem, or if others are seeing this. Thanks!

I upgraded the radio (from 1.00 to 2.15) via Diacius's guide: http://forum.xda-developers.com/showthread.php?t=760651
Also installed RMK40's Official 2.2 ROM update: http://forum.xda-developers.com/showthread.php?t=765930
All of it was done this weekend. No problems yet.

No I am not running the Official OTA but I am running the RUU. I did have the 3G failure one time on the first day but not since.
I ran your test 3 times and the 3G icon comes up every time. Last by the way. And yes, the internet works.
I know this is not what you asked for but hope it helps

I installed leaked version. Works GREAT! However a fw of my apps when I wanted to load them again through the market "The requested item could not be found"
Is this because they wont work with 2.2 or is something else?
Thanks
[email protected]

Note a couple of things here.
1. You should always reprogram your phone after installing a radio or rom. This tends tohelp with some of the drop outs. of 3G.
2. The RUU includes a PRI update that NONE of us have been able to flash, and is likely the answer to these random drop outs.

I did the RUU update and I have to say I am disappointed.
I am having doubt about the RUU being the same as the OTA.
Rosie reloads after exit from astro file manager, not always but a few times so far.
Screen brightness has a mind of it own and it took upward of 25 seconds for the screen to brighten up after an interaction (not the backlight, but the brightness).
Overall slowness, it might have better benchmark but feel sluggish.
It might be something on my part during flash, but I doubt it.
Google action is the only improvement for 2.2. Don't see anything to write home about on the 720p.
And that's all folks! nothing else that I personally use or care about that's an improvement over 2.1.

Astro crashes Rosie and you blame the OS?
Interesting.

I still have problems with the lock screen not wanting to unlock. I'll drag it to the bottom and it'll just bounce back up.
In 2.1 I could hit menu and all will be well, in the RUU theres no hope, I eventually had to restart the phone just to clear the lock screen.

I thought the RUU had improved my phone, but then I tried installing a deodexed version and **** hit the fan. I even tried going back to the regular 2.2 before I had installed the deodexed one and still had issues.
My problems:
Battery drains ultra fast, when barely using phone.
Market doesn't download stuff right
hot battery
I noticed the biggest culprit after viewing battery info was
Android System
Phone Idle
Cell Standby
I think it might be the radio that is causing the issue.
I am about to go to the 2.05 radio. Seems it was a better radio and had less issues.

Marketplace: I have had the issue with the market download stalling, but that's only happened when downloading multiple installs. I've never had it happen on a single install. Hardware or Software? Don't know yet, but I'd assume software is missing a reply ACK back to the server on the multiple downloads. Who knows.
Radio Issues: NEVER had the 3G problem. 3G is always going strong, unless I'm in the tunnels beneath the buildings here, then I drop to 1x or lose all connectivity. When I return to the surface, I'm back at 3G with no problems.
I've rebooted my phone probably 10 times since installing the RUU, 3G has always come up fine.

TNS201 said:
I thought the RUU had improved my phone, but then I tried installing a deodexed version and **** hit the fan. I even tried going back to the regular 2.2 before I had installed the deodexed one and still had issues.
My problems:
Battery drains ultra fast, when barely using phone.
Market doesn't download stuff right
I noticed the biggest culprit after viewing battery info was
Android System
Phone Idle
Cell Standby
I think it might be the radio that is causing the issue.
I am about to go to the 2.05 radio. Seems it was a better radio and had less issues.
Click to expand...
Click to collapse
2.05x radio I think would just be worse.
how long have you been running 2.2??
You need to give it at least a week to settle down and everything.
It's like when you first got the phone my battery life sucked the first week until it settled it, it's the same way with going from 2.1 to 2.2.
I suggest charging to 100%. then wiping battery stats, and don't plug back in until phone dies, then use for a few days and see how that works. 2.15x radio is what comes with the official OTA 2.2 I don't understand why you would want 2.05 that's old news.
what makes you think your battery issues lie in the radio? just curious

ACD168 said:
2.05x radio I think would just be worse.
how long have you been running 2.2??
You need to give it at least a week to settle down and everything.
It's like when you first got the phone my battery life sucked the first week until it settled it, it's the same way with going from 2.1 to 2.2.
I suggest charging to 100%. then wiping battery stats, and don't plug back in until phone dies, then use for a few days and see how that works. 2.15x radio is what comes with the official OTA 2.2 I don't understand why you would want 2.05 that's old news.
what makes you think your battery issues lie in the radio? just curious
Click to expand...
Click to collapse
Just seems to be the culprit because I did S-OFF
Then I installed 2.15 radio and then problems started.
So far all seems good. Market downloads aren't getting stuck and my phone isnt getting hot as all hell and my battery isn't dying really fast.

nowandaway said:
I installed leaked version. Works GREAT! However a fw of my apps when I wanted to load them again through the market "The requested item could not be found"
Is this because they wont work with 2.2 or is something else?
Thanks
[email protected]
Click to expand...
Click to collapse
Some of the apps on the market won't work on 2.2 , most have been , or in the process being updated to 2.2.

I flashed the 8/26 leaked RUU to a stock 2.1 phone and my friends that did the same agree that we do not have the bugs named in this thread. They must only be in the the first leaked 2.15 radio. We never installed that radio.

HBOOT-0.35.0017 and 3g connectivity issues read here

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.

[Q] Nexus 4 Notification Delay

This topic has been discussed a lot of times on internet but I am really concerned about fixing my phone as no matter what, if i am on 2G, 3G or WIFI I stop having notification after 15-20 minutes. In fact I tried PINGING my device and PING stops really after 15 minutes. Anyways, currently I am desperately waiting for 4.3 and there is just no NEWS of the RELEASE DATE whatsoever. But also I am not much into CUSTOM ROM or KERNELS but was wondering if I can only update the KERNEL version (i.e., FRANCO if any one suggest) and solve this issue. I want to be remain on STOCK ANDROID but is it possible to only upgrade the kernel ?
Also I would need tutorial for the quickest root and the safest kernel to follow and keep upgrading it all the time. Thank you.

ibrahim52 said:
This topic has been discussed a lot of times on internet but I am really concerned about fixing my phone as no matter what, if i am on 2G, 3G or WIFI I stop having notification after 15-20 minutes. In fact I tried PINGING my device and PING stops really after 15 minutes. Anyways, currently I am desperately waiting for 4.3 and there is just no NEWS of the RELEASE DATE whatsoever. But also I am not much into CUSTOM ROM or KERNELS but was wondering if I can only update the KERNEL version (i.e., FRANCO if any one suggest) and solve this issue. I want to be remain on STOCK ANDROID but is it possible to only upgrade the kernel ?
Also I would need tutorial for the quickest root and the safest kernel to follow and keep upgrading it all the time. Thank you.
Click to expand...
Click to collapse
The choices and threads are out there for you if this is truly bothering you. You can stay stock and flash a couple of files to test out if your issue is fixed. Rooting is not the end of the world and you can always go back. As for tools there are multiple stickied root methods just choose one. Also no guarantee 4.3 fixes the issue. I flashed a couple files from Development in the Wifi/Fix thread and my problems went away. May for you it may be the prima drivers but you wont know until you do it

playya said:
The choices and threads are out there for you if this is truly bothering you. You can stay stock and flash a couple of files to test out if your issue is fixed. Rooting is not the end of the world and you can always go back. As for tools there are multiple stickied root methods just choose one. Also no guarantee 4.3 fixes the issue. I flashed a couple files from Development in the Wifi/Fix thread and my problems went away. May for you it may be the prima drivers but you wont know until you do it
Click to expand...
Click to collapse
I will be still waiting till 4.3 is released but just one thing I wanted to confirm when you said your problem was FIXED. Was it on both 3G / WiFi because this issue occurs on both interface.

Are there any other particular apps that still gets notification after everyone don't?
Sent from my Nexus 4 using xda app-developers app

QuackDuck said:
Are there any other particular apps that still gets notification after everyone don't?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
any APP has the same issue. I use the following and in everything it is the same frustrating issue.
whatsapp
Talk.to
Email (Even if the settings are on 1 hour INBOX CHECK, it never works until i manually do the sync)
These are the only apps I always expect to notify me INSTANTLY. Also it was the same in Google talk and any other IM apps.

ibrahim52 said:
I will be still waiting till 4.3 is released but just one thing I wanted to confirm when you said your problem was FIXED. Was it on both 3G / WiFi because this issue occurs on both interface.
Click to expand...
Click to collapse
for me I had mostly issues on wifi and now I can ping my phone after 30 minutes and it still going. I never honestly noticed it on 3g but either way you have options try them first

playya said:
for me I had mostly issues on wifi and now I can ping my phone after 30 minutes and it still going. I never honestly noticed it on 3g but either way you have options try them first
Click to expand...
Click to collapse
Thanks but it also happens in 2G because 3G I can't use due to my work environment where I can't keep charging my phone and in 3G this phone battery drains quickly. Well, two more weeks ill wait for 4.3 and if Google is still fooling then I will go ahead with ROOT and some KERNEL experiments. Thanks a load.

Flashing 03.61 radio on NRD90U

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.

Issues running CM13

So I got my S4 up and running on Ting and got CM13 running on it, was having the LTE issues and flashed the .zip for MVNO and got my lte working so that was fine. Everything was great but than I realized that when I'm at home (where I have very weak signal) that the network would drop out and it would just say no service and stay that way until I rebooted, than everything would be good again for a few minutes until it lost service again and it would not pick it back up. I flashed back to stock using odin and even though I would have very weak signal it would never fully drop the network and I could still receive calls. The phone is running on OK3, I tried the OCTOS CM13 rom and had the same problem. Haven't tried any AOSP or any other Touch wiz roms yet to see if the problem persists just because work hasn't afforded me the time to mess with it. I was curious if anyone else had these same issues though or if there was anything I could edit in the system files to get it to reconnect to the network after it drops it. I will note as well that when I'm at work where I have a strong cellular signal I don't have this problem at all, it's just when the network falls out it won't pick it back up again. I figure it has to be something simple that can be corrected but I don't have the experience or knowledge to even begin to know where to look and after almost a week of searching these forums and google I haven't been able to find an answer or a similar problem. Any help or guidance would be hugely appreciated.

Yes I feel your pain. I've been experiencing this issue also and have yet to find a fix. I did see that someone reported that they don't have the issue with the R1 build of OctOs. I have yet to test this but I hope it will fix the issue.

andyman2017 said:
Yes I feel your pain. I've been experiencing this issue also and have yet to find a fix. I did see that someone reported that they don't have the issue with the R1 build of OctOs. I have yet to test this but I hope it will fix the issue.
Click to expand...
Click to collapse
Well at least now I know I am not the only one! I'll keep searching for an answer and try a few other roms that aren't CM based and see if I can find some sort of solution that isn't running rooted stock firmware. Ideally something MM based. Also if you could link to the thread where someone else reported a similar problem that would be great. Let me know if you find a solution before I do, one has to exist I'm sure.

So I saw towards the end of the octos thread where other people have been reporting the same issue with CM13 and OCTOS, found the R1 version of octos, will give it a try and report back. Hopefully CM13 catches wind and can trace back to whatever it is that is causing this issue as well, I might try one of the newer CM13 nightlies and see if maybe the problem hasn't been remedied but I'm not holding my breath :-/ I just really want MM back.

So update, I installed the R1 version of octos and the "no network" issue has not reared its head again yet. I Flashed the buzzbeemvno fix as well afterwards and one thing I did notice, before the mvno flash I was getting 3g signal with the sprint profile, once I flashed over to the ting profile it was only pulling 1x as far as signal is concerned. I don't really mind though since I have a solid wifi signal at home and the main goal here was to just have reliable signal to receive calls and texts when I ought to.

Give this APN a shot. It's the one I'm using currently. I think I may need to make some adjustments still, but it seems to work well enough so far.
It's also usually a good idea to reboot into recovery and delete the telephony.db and telephony.db-journal files in /data/data/com.android.providers.telephony/databases/ after you have replaced the apns-conf.xml. The system will recreate those files on startup using the new data.

Blaises are you running that APN pack on the newer cm13 builds?

I'm running the APN I linked earlier rather than the MVNO fix., and I'm using it on OctOS R1 which is a CM13 build from March.
I'm using Ting on the Sprint network.

Can I get your opinion on oct-os? Is it a daily driver ROM? Did you guys stay on the ROM? Any advice for me or warnings?
Sent from my KIW-L24 using XDA-Developers mobile app

So I am on the older build of octos from the spring, it's been a great daily driver gives me almost no problems. There has been an occasional Bluetooth hiccup and camera hiccups. But maybe once a month, overall it's been a great ROM.