Develop Bugs

Random service drops? AOKP

Been running AOKP for quite some time now but I've been getting random blackouts lately where my phone will show zero bars of service with an X through it and it will come back within 30 seconds but it has been known to drop calls and it generally just ****s everything up. Happens a few times daily. Anyone else?

I've been running AOKP build 36 and Franco Kernel r166. I have experienced a couple data drops. It rarely ever happens for me.
What build and kernel are you running?

Syn Ack said:
Been running AOKP for quite some time now but I've been getting random blackouts lately where my phone will show zero bars of service with an X through it and it will come back within 30 seconds but it has been known to drop calls and it generally just ****s everything up. Happens a few times daily. Anyone else?
Click to expand...
Click to collapse
Maybe try wiping cache/dalvik?
i heard it's an issue with most if not all 4.0.4 builds out right now. some people suggest trying different kernels, others just say to do a clean install, etc. The only time it really happens to me is when connect to wifi, then disconnect. it doesn't go connect my data unless i reboot. can still get calls/texts though. this was on milestone5. I just upgraded to b38 and it may have cleared up, but i'll keep running tests.

soapbox23 said:
Maybe try wiping cache/dalvik?
i heard it's an issue with most if not all 4.0.4 builds out right now. some people suggest trying different kernels, others just say to do a clean install, etc. The only time it really happens to me is when connect to wifi, then disconnect. it doesn't go connect my data unless i reboot. can still get calls/texts though. this was on milestone5. I just upgraded to b38 and it may have cleared up, but i'll keep running tests.
Click to expand...
Click to collapse
Hmmm, I always wipe everything good when I install new builds. I also usually use Franco kernel, sometimes the AOKP kernel when I'm lazy or forget to install Franco.

This is a known issue with AOKP and also Franco's kernel.

Good to know thanks.

More like it is a known issue with AOSP in general from reading around as CM has it as well.
Sent from my Galaxy Nexus using xda premium

I was having the SAME EXACT issues, I fixed it 100% buy doing a full wipe (user + system data, plus dalvik) through recovery, and re-installing the most current CM9 Nightly (6/3/2012 for me) and now my phone hasn't dropped the signal ONCE in the 8+ hours I have been using it heavily.
I'm thinking the full wipe was all it needs and the ROM doesn't really matter, but I read somewhere (probably here) that if you underclock your CPU to anything below 400 Mhz then it will have issues connecting to the towers, I don't know how accurate that is, but I can confidently say that I have my Nexus back!
I'm using the most recent radios included in CM9 Toro 6/3/2012 which are the newest ones that Verizon pushed out with their 4.0.4 update.
My battery life is horrible now but I could care less at this point (4 months with a shoddy signal).

Liskrig said:
I was having the SAME EXACT issues, I fixed it 100% buy doing a full wipe (user + system data, plus dalvik) through recovery, and re-installing the most current CM9 Nightly (6/3/2012 for me) and now my phone hasn't dropped the signal ONCE in the 8+ hours I have been using it heavily.
I'm thinking the full wipe was all it needs and the ROM doesn't really matter, but I read somewhere (probably here) that if you underclock your CPU to anything below 400 Mhz then it will have issues connecting to the towers, I don't know how accurate that is, but I can confidently say that I have my Nexus back!
I'm using the most recent radios included in CM9 Toro 6/3/2012 which are the newest ones that Verizon pushed out with their 4.0.4 update.
My battery life is horrible now but I could care less at this point (4 months with a shoddy signal).
Click to expand...
Click to collapse
Well there ya go, Franco stock settings have a low end of 384Mhz I believe.

I was on AOKP b37 with the 4.0.4 radios on my old phone and had the same problems, but they happened from day 1 on stock software and were what caused me to root. If you always had the problem before rooting, then it is more than likely the phone. Full wipes didn't work, new radios didn't work, only getting a new phone worked.

It is a problem with AOSP..
Sent from my Galaxy Nexus using xda premium

joshnichols189 said:
It is a problem with AOSP..
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
So, should I wait for a fix, or wipe everything and install Gummy's rom?
Because it's having a phone without it's functionality www4.slikomat.com/11/0605/rew-DSC004.jpg

I have no issues on build 38 running ezekeels kernel 1.34
does gummy have the compass fixed all roms are backwards and that sucks

Chopders said:
So, should I wait for a fix, or wipe everything and install Gummy's rom?
Because it's having a phone without it's functionality www4.slikomat.com/11/0605/rew-DSC004.jpg
Click to expand...
Click to collapse
Gummy is made from AOSP..
Sent from my Galaxy Nexus using xda premium

Chopders said:
So, should I wait for a fix, or wipe everything and install Gummy's rom?
Because it's having a phone without it's functionality www4.slikomat.com/11/0605/rew-DSC004.jpg
Click to expand...
Click to collapse
No, return it to stock and have Verizon send you a new one.

Running AOKP B38 + Franco M3, and NEVER had this issue. Always clean install, and even in AOKP M5, up to every build leading to 38, never had data connection issues.
Sent from my Galaxy Nexus running AOKP+Franco

I was having the same issue with data drops happening on a regular basis even in strong LTE areas to the gray X. I tried flashing every radio out there and several roms and never fixed it. finally got VZ to send me a replacement and the new one works flawlessly, zero drops.
I'd just get it replaced.

I've been able to fix this problem by running the UGLC1 kernel. Also make sure your RIL matches your radio: https://play.google.com/store/apps/...t=W251bGwsMSwxLDMsImNvbS5zaWJib3IuZ2V0cmlsIl0.
After flashing UGLC1 and making sure my RIL matches I haven't dropped signal once.

Tynen said:
I've been able to fix this problem by running the UGLC1 kernel. Also make sure your RIL matches your radio: https://play.google.com/store/apps/...t=W251bGwsMSwxLDMsImNvbS5zaWJib3IuZ2V0cmlsIl0.
After flashing UGLC1 and making sure my RIL matches I haven't dropped signal once.
Click to expand...
Click to collapse
+1 to this
https://play.google.com/store/apps/details?id=com.sibbor.getril
Sent from my Galaxy Nexus using Tapatalk 2

android01 said:
+1 to this
https://play.google.com/store/apps/details?id=com.sibbor.getril
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I still agree
Sent from my Galaxy Nexus using xda premium

Little or no signal.

I had flashed to an AOKP rom a while back and had since had a very significant and noticeable drop in signal strength. So much so that I was unable to get a signal at all in places when I would normally have 2-3 bars. Other people still get signal in those places with the same service provider. I decided to try to flash different modems to try and fix the problem. I have since tried 3 different JB modems from rogerwilco's modem repository for the E4GT. Every single one I have not been able to get a data connection at all. At most I have been able to get 1-2 bars and no data connection. Even if my signal strength was low I could care less as long as I could get a data connection at all... can someone please assist me? Has anyone else been running across any other type of issue? I also wanted to know... when I update profile and PRL... is this stored in /data or does it burn it to the same area of memory as the modem image? Primarily... does it get wiped when you wipe data?

Goblinlord said:
I had flashed to an AOKP rom a while back and had since had a very significant and noticeable drop in signal strength. So much so that I was unable to get a signal at all in places when I would normally have 2-3 bars. Other people still get signal in those places with the same service provider. I decided to try to flash different modems to try and fix the problem. I have since tried 3 different JB modems from rogerwilco's modem repository for the E4GT. Every single one I have not been able to get a data connection at all. At most I have been able to get 1-2 bars and no data connection. Even if my signal strength was low I could care less as long as I could get a data connection at all... can someone please assist me? Has anyone else been running across any other type of issue? I also wanted to know... when I update profile and PRL... is this stored in /data or does it burn it to the same area of memory as the modem image? Primarily... does it get wiped when you wipe data?
Click to expand...
Click to collapse
JB modems don't work on the aokp roms..... I think... Not sure.
Sent from my SPH-D710 using xda app-developers app

E4GTUser94 said:
JB modems don't work on the aokp roms..... I think... Not sure.
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
Interesting... I have to say... it is rather difficult considering I can't find much as far as compatibility information for modem images... not with between versions anyways. Meaning... what is compatible and works with what. All I can seem to find out is what stock image they came out of.

JB modems only work with JB touchwiz based roms. All other modems work fine with all other roms. The FI27 modem worked just fine for me on various aosp roms.

The FL24 modem works great for me on AOSP. The leaked JB modems do not work on AOSP. I didn't have great luck with them on stock rooted roms either though (FK23 and FL04).

I would try a stock rooted build like FK23 and run it for a while and see if you get your signal strength back.
Them you can figure out whether it's your radio or Rom.
Pp.
sent from a jellybean filled epic touch.

PanchoPlanet said:
I would try a stock rooted build like FK23 and run it for a while and see if you get your signal strength back.
Them you can figure out whether it's your radio or Rom.
Pp.
sent from a jellybean filled epic touch.
Click to expand...
Click to collapse
Actually, flashed to an ICS radio and it started working.

"loosing" 3G on 4.3 Toro

So i was wondering if anyone else is having this issue.
for reference, I am on VZW, with the 4.1.1 radios (as the updated 4.2 radios had me locked into 3G no matter what, at work)
and i ALWAYS do a complete wipe (data/cache/dalvik/system) between ROM flashes.
4.3 bootloader as well.
anyway, this has been an issue since 4.3 hit my device...anything from pure AOSP to CM builds.
when I am on 3G, the bars will go gray and i cannot pull down data at all. (and yes i know the difference between blue and gray bars, I'm saying ANYTHING will say "network not available" not just google apps)
toggling data on/off fixes the problem. I ususally run into this problem 2-3 times a day and it is ALWAYS on 3G.
its not a huge deal, just more annoying than anything else. just wondering if I am alone here. going to be giving the 4.2.2 radios another chance and see if that fixes things.

Having this exact issue...it's driving me nuts as well. At this point I believe I've tried every radio with no luck. Going to try jumping back to 4.2 soon to see if it solves the issue.

Me too
+1
I love how much fast my GNex is on 4.3, but I don't think I can deal with this data bull**** much longer. Frankly, I'm really getting tired of getting a new version of Android, being happy at first, then finding the HUGE bug that makes my phone a horror to use. WHY HAVE YOU FORSAKEN THINE VZW GNEX, GOOGLE!?!?

Just an update, as I updated my radios right around the time I updated to 4.3. I just switched back to CM 10.1 and all my data connection issues went away. That means it definitely has to do with 4.3 builds and not the radio firmware.

ericbarch said:
Just an update, as I updated my radios right around the time I updated to 4.3. I just switched back to CM 10.1 and all my data connection issues went away. That means it definitely has to do with 4.3 builds and not the radio firmware.
Click to expand...
Click to collapse
That's right, 4.3 sucks.
Sent from my Galaxy Nexus using Tapatalk 4

Edit build.prop and include this line:
ro.telephony.default_cdma_sub=0
Data issues are being reported on nearly every rom for the gnex. My data reconnect /switch went from about 60 - 90 secs to a reasonable 5-10. (don't forget to reboot to apply changes)
Sent from my Galaxy Nexus using xda app-developers app

So happy I found this thread!
I'm having the SAME issue: GSM i9250 on Straight talk ATT sim (apn setting are updated and correct). Stock not rooted; been happening since 4.3 Update. From what I've read even folks on the N4 are having similar issues.
I've factory reset 3-4 times for testing purposes (back to "normal" for about an hour then those pesky gray bars and NO data on 3G/4G).
I have to do the airplane mode toggle every 1/2 hour if I'm really using the internet. Big pain in the ass!
I always rooted my devices in the past and haven't done the GNEX because I always felt stock was smooth enough for my purposes (quasi-work-phone and I need stability). If I have to deal with this bull-sh&% I'm probably gonna have to root and install a 4.2 ROM.
Any-whoo...thanks for letting me rant :^)
Hopefully "kit-kat" will help?

same issue its very annoying... did anyone find the fix ??

ffejy462 said:
Edit build.prop and include this line:
ro.telephony.default_cdma_sub=0
Data issues are being reported on nearly every rom for the gnex. My data reconnect /switch went from about 60 - 90 secs to a reasonable 5-10. (don't forget to reboot to apply changes)
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Is this a fix?
My issue seems to be on 4g as well. If the phone switches from wifi to 4g or if it goes from 4g to 3g and back to 4g it shows a connection with bars but never connects to data again.

[Q] Sprint GS3 Signal Reception

So this is my first flash to a different ROM on my GS3. I have been rooted for a while and decided I wanted to try a different rom on 4.2.2 coming from 4.1.2 with touchwiz. I am using the Dirty Unicorns 4.2.2 ROM and I noticed my signal reception is spotty at best. I am talking data and voice together. I flashed back to my 4.1.2 touchwiz stock rom and the reception went back to normal. I did some research on this issue and started looking into APNs. I noticed the file on the Dirty Unicorns rom is full of VZW, CREDO, Sprint... but the stock Sprint ROM only has Sprint stuff. The differences in the 2 files, only looking at the Sprint settings is slightly different still.
Is this my issue? If so should I use the stock APN file?
I am using the stock MD4 baseband and my PRL is 25015. Any thoughts or troubleshooting steps are appreciated.

I did some deeper research to find that the signal reception seems to be reporting incorrectly in the Dirty Unicorns ROM. I downloaded an app from the play store called network info II. This reported my cell reception to be the same it was on the stock MD4 touchwiz rom. I also think that the signal bar is reporting the faulty reception listed in the about section of settings. I made a few phone calls and ran Pandora on the cell network with no abnormal loss of quality.

Try a app in play store
Signal Check Lite
Gives a lot of info and signal strength for data too

I like that app better than the other one I was using... Thanks for the tip!
GSXeclipsePSI said:
Try a app in play store
Signal Check Lite
Gives a lot of info and signal strength for data too
Click to expand...
Click to collapse
Back to my issue, it looks as if the phone is reporting correct numbers in the signal information fields. What it looks like it is showing is the data connection it is using. I also, sometimes, find my phone on LTE even when I connected to wireless seems interesting. I am not sure however about the signal bars at the top of the phone. Rarely ever do I see them rise above 2 bars. Maybe somebody from an AOSP rom or CM rom could chime in with an answer.. even a DEV!!
FYI: Would have posted this in the development forum but I didn't have enough posts at the time. I am also sharing my info just in case it isn't around or it helps someone else.

[SOLVED] Same problems over here
edit 10/10/13 [SOLVED]: I found this thread about Team Sonic Modem Flasher Tool. There are five available radios in the super easy package. 1-4 came up with error messages, "No SIM card," or no signal with an Unknown Baseband in the phone settings. The fifth one, "LI3" radio solved my problems.
The Flasher Tool doesn't have a means of backing up your current radio. Seems like as soon as you start installing these other radios, your original one (mine was an MB1) was gone. BTW, my phone Baseband was a long string of letters and numbers. The type of radio that you've got is the last three characters.
I was also experiencing problems with other ROMs than the stock rom on my Sprint Galaxy S3. I was running Cyanogenmod 10 release candidate, and it seems to me that the signal was way worse than with the stock rom. I would also be in downtown Seattle, certainly with LTE service, and still I was stuck at 3G. 4G/LTE seems to be a thing of the past with the newer ROMs that I've been enjoying.
At the moment I'm back to a stock ROM, CleanBean v4.2 with Android 4.1.2. It seems to be happier. But I won't be back to an area with normal cell service for quite some time.
An interesting idea that the ROMs were reporting the incorrect signal strength. But reporting 3G vs 4G incorrectly too? That seems like something else was wrong.
I was thinking perhaps it was the radio or something, but CM doesn't really mention anything about flashing specific radios.

Are you judging from actual numbers or the signal bar? The latter is notoriously inaccurate many times (and can vary depending on what rom you're using

As for not jumping on 4g when I should have been, that was my oops. I had the settings in the phone to only do CDMA/3G rather than LTE/CDMA/3G. I would flash the radio to the newest version and leave it at that. I heard from someone else in another thread that the radios don't get changed.
dkerlee said:
I was also experiencing problems with other ROMs than the stock rom on my Sprint Galaxy S3. I was running Cyanogenmod 10 release candidate, and it seems to me that the signal was way worse than with the stock rom. I would also be in downtown Seattle, certainly with LTE service, and still I was stuck at 3G. 4G/LTE seems to be a thing of the past with the newer ROMs that I've been enjoying.
At the moment I'm back to a stock ROM, CleanBean v4.2 with Android 4.1.2. It seems to be happier. But I won't be back to an area with normal cell service for quite some time.
An interesting idea that the ROMs were reporting the incorrect signal strength. But reporting 3G vs 4G incorrectly too? That seems like something else was wrong.
I was thinking perhaps it was the radio or something, but CM doesn't really mention anything about flashing specific radios.
Click to expand...
Click to collapse
As for the feeling that the signal was reported incorrectly, I learned this. Dirty Unicorns, probably most other modded ROMs as well, are reporting the TRUE data signal strength in the signal bars. I downloaded Signal Check Lite. I compared the signal reported in the ROM to what this program says and they are identical. The bars are reporting the connected network types signal strength (ie. LTE,3G). It also says to be showing the RSSP which has been widely skeptical in most threads. If you're worried about your signal, check that program before switching away from a ROM or going back to stock. I actually kind of like them displaying the good info rather than just voice signal.

Does the kernel being used have any affect on signal reception? I'm just curious because I've switched between a few different 4.3 ROMs and the quality of signal is different between them.
When I was running Slim Bean 4.3, receiving a data signal at work wasnt a big issue. This morning I flashed Liquid Smooth 4.3 and even though the numbers being reported for signal strength are very similar, data on Liquid Smooth is almost unusable. Let me reiterate; Same phone (latest PRL), same location, same radio (MD4), same signal data numbers, using 2 different 4.3 ROMs and getting 2 extremely different usability results.
I'm not blaming either ROM, so I dont want to post in said threads, but is there a reason why this would be happening?

You are using data on the cell network and not the wifi network correct? There is a slight chance that it could but it would be mostly dependent on your modems I think. I am sure the modems and the kernel interact but that is about it. Testing for my issues, I am flashing the stock kernel back in, after doing a nandroid of course.
Disclaimer: I could be speaking rubbish. If I am please feel free to correct me, as I am still trying to learn.
uodii said:
Does the kernel being used have any affect on signal reception? I'm just curious because I've switched between a few different 4.3 ROMs and the quality of signal is different between them.
When I was running Slim Bean 4.3, receiving a data signal at work wasnt a big issue. This morning I flashed Liquid Smooth 4.3 and even though the numbers being reported for signal strength are very similar, data on Liquid Smooth is almost unusable. Let me reiterate; Same phone (latest PRL), same location, same radio (MD4), same signal data numbers, using 2 different 4.3 ROMs and getting 2 extremely different usability results.
I'm not blaming either ROM, so I dont want to post in said threads, but is there a reason why this would be happening?
Click to expand...
Click to collapse

Custom ROM and stock kernel don't seem to work, at least with me. Recovering from nandroid right now.

Skeeredfitless said:
Custom ROM and stock kernel don't seem to work, at least with me. Recovering from nandroid right now.
Click to expand...
Click to collapse
On custom ROMs you run, I think its best to run the kernel that the developer incorporated into the ROM for awhile. Then if you are sure your picking the correct kernel, you can try it out, but not before a nandroid of course. A touchwiz kernel is not going to function correctly on a AOSP ROM. Can cause alot of problems, TW & AOSP kernels are 2 totally different animals.

My battery life is sucking. I am trying to improve it so I thought I might try the stock one.
joeyhdownsouth said:
On custom ROMs you run, I think its best to run the kernel that the developer incorporated into the ROM for awhile. A touchwiz kernel is not going to function correctly on a AOSP ROM. Can cause alot of problems, TW & AOSP kernels are 2 totally different animals.
Click to expand...
Click to collapse

Skeeredfitless said:
My battery life is sucking. I am trying to improve it so I thought I might try the stock one.
Click to expand...
Click to collapse
Too many factors to list can cause this, try a different ROM with a clean wipe. Never use a TW kernel on a AOSP ROM.

Why does every KK rom have data issues?

I've tried Liquidsmooth, CM Remix, Omni, and now Carbon. Every KK rom shows me the orange no data connection icon. Airplane mode toggle and wifi toggle doesn't work. Reboots only work sometimes. And that's not really a solution, rebooting my phone every 5 minutes. Why is this happening?

I only home that you switched all these ROMs with clean installs. Did you?

Of course

yea same here got a gnex on eBay having trouble getting it going ..looks like I'm going to an old ROM that my other gnex runs and at least has data connection
4.2.2. lol....
what baseband are people using for KK on gnex Verizon ?
Sent from my Galaxy Nexus using XDA Premium 4 mobile app

rsswga said:
yea same here got a gnex on eBay having trouble getting it going ..looks like I'm going to an old ROM that my other gnex runs and at least has data connection
4.2.2. lol....
what baseband are people using for KK on gnex Verizon ?
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
Click to expand...
Click to collapse
yeah.. maybe your baseband version (radio.img) didnt suited you.
maybe broken driver ~ reflash kernel with wifi driver works for me. ( changing rom didnt change anything to radio/driver setting)

My old 4.2.2 JBSourcery gets signal just fine. And for some reason Omni gets better than the others but still cuts out.

Explodee said:
My old 4.2.2 JBSourcery gets signal just fine. And for some reason Omni gets better than the others but still cuts out.
Click to expand...
Click to collapse
your baseband??
sometimes when u using adblocker apps or network tweaks/mod its can easily mess your network setup. just double check if any.

Flashing roms doesnt change radios right?

the only way I can get data is if I put it right beside my network extender.
I've tried all the radios.. did I get a dud..?
sent from a violated gs3
---------- Post added at 02:13 PM ---------- Previous post was at 02:12 PM ----------
Explodee said:
Flashing roms doesnt change radios right?
Click to expand...
Click to collapse
nope
sent from a violated gs3

Explodee said:
Flashing roms doesnt change radios right?
Click to expand...
Click to collapse
rom can affects data coverage from the Rils files (in libs). usually continuously using 4.3 rils right now cause google doesn't update for gnex. gnex roms still on progress in this. CM & slim update the coverage issues so far. dont know wt others. sorry if im wrong..
http://www.slimroms.net/index.php/news/431-weekly-3-2

Explodee said:
I've tried Liquidsmooth, CM Remix, Omni, and now Carbon. Every KK rom shows me the orange no data connection icon. Airplane mode toggle and wifi toggle doesn't work. Reboots only work sometimes. And that's not really a solution, rebooting my phone every 5 minutes. Why is this happening?
Click to expand...
Click to collapse
I dont know what carrier you are on but when I was using my Verizon Galaxy Nexus, every ROM I flashed usually had no data on first boot. I got in the habit of rebooting the phone before I even went through the setup and after that, data had no issues. It was a known thing. Toggling airplane mode and 3g/LTE was also known to cause issues at one point. So if you clean flash, boot up and let it sit for a few seconds before going through the google setup. If data doesnt automatically connect, reboot right away. It should connect fine after that.

Yeah I'm on Verizon now. Hopefully making the switch to T-mo in about a month. The problem is not that data doesn't connect at all, the problem is that it will drop out and never come back. I live in Boston and in the subway I will lose the signal underground and it will never come back. Also my office is right in the main downtown area and I barely get a 3G signal no matter what. I know my signal strength isn't part of this problem. It's the data connection somehow becoming disconnected and staying idle that is stopping me from staying on KK.

Explodee said:
Yeah I'm on Verizon now. Hopefully making the switch to T-mo in about a month. The problem is not that data doesn't connect at all, the problem is that it will drop out and never come back. I live in Boston and in the subway I will lose the signal underground and it will never come back. Also my office is right in the main downtown area and I barely get a 3G signal no matter what. I know my signal strength isn't part of this problem. It's the data connection somehow becoming disconnected and staying idle that is stopping me from staying on KK.
Click to expand...
Click to collapse
Since you're on Verizon check shiny Rom. The guys there have done a lot of tweaking to improve data.
The reason data is problematic is partially since the gnex is no longer supported and the toro variant has had no officially android release since 4.2.2 and the ril and telephony stack have changed how they work with cdma in both 4.3 and 4.4. I believe the toro uses a bit of an older radio. Is this a problem when you disable 4g as well?
Sent from my HTC One using Tapatalk

I've gotta say that Shiny ROM is just about flawless. I've never had issues getting or keeping a data connection when there's signal. I'm using the FK01/FK02 radios from 4.2.2 and the 4.2 bootloader.
I'll give my little testimony here: a basic stock rom will get you farther than a fully-featured one. I've heard the expression "mo' features, mo' bugs" and that seems to fit quite well. I'm not aware of any features in any rom that you can't get from one xposed module or another, so that's what I've been doing. I'd say give it a try and see if your data issues are resolved for good.

Shiny has always worked fine for me. I run latest everything.. bootloader, radio. CM I think worked fine for me but was ugly. Paranoid Android seems to have some connectivity issues.. I wish someone could solve this data issues. Maybe it is time to leave my nexus behind Just been waiting for another verizon nexus
Explodee said:
I've tried Liquidsmooth, CM Remix, Omni, and now Carbon. Every KK rom shows me the orange no data connection icon. Airplane mode toggle and wifi toggle doesn't work. Reboots only work sometimes. And that's not really a solution, rebooting my phone every 5 minutes. Why is this happening?
Click to expand...
Click to collapse

I've got about 7 different Nandroids and have been switching between them to test. CM Remix which I believe is based on Slim seems to be working OK. I tried Slim this morning but still got a lot of data cut-outs

Explodee said:
I've got about 7 different Nandroids and have been switching between them to test. CM Remix which I believe is bases in Slim seems to be working OK. I tried Slim this morning but still got a lot of data cut-outs
Click to expand...
Click to collapse
wow.. lot of roms tested. that pretty brilliant idea for solving this. just use the best. data networks really different for each country.
* i found out a different in apn setting wt different rom. slim rom only captured 4g by my local provider (APN). when im tried asob its give choice in Apn setting ( 3g /4g). my country not fully h+ at several area. so changing to 3g got better network (better low than nothing)

memaro_maro said:
wow.. lot of roms tested. that pretty brilliant idea for solving this. just use the best. data networks really different for each country.
* i found out a different in apn setting wt different rom. slim rom only captured 4g by my local provider (APN). when im tried asob its give choice in Apn setting ( 3g /4g). my country not fully h+ at several area. so changing to 3g got better network (better low than nothing)
Click to expand...
Click to collapse
I don't think that applies to CDMA