Develop Bugs

[Q] New Glide owner, could use some advice.

Howdy Folks!​
I recently got a SGH-I927 that is locked to AT&T.
I have read what I believe is all the relevant data about how to do the things I want, and I think I have it down, but I want to make sure I have everything exactly correct. I still have 6 days left with Virgin Mobile before I have to have all this done.
What I want to do...
Root
Back up my EFS
Update from 2.3.6 to 4.0.4
Carrier Unlock from AT&T so I can use a T-Mobile MVNO.
So my question is- is this the best order to do things in? I know I have to root before I can Unlock the phone or Backup my EFS, but I notice that there are two different methods for Rooting. I can root before I update to ICS or after. Does it make a difference? Which method is easier, which one is more reliable/safer? I also noticed that Unlocking the phone after updating to ICS requires an extra step, so that would be another factor.
Kies seems to be working, and when I plugged my phone in, it offered to update me from 2.3.6 (Baseband Ver I927UCKL1) to 4.04 (Baseband Ver I927UCLJ3), so it doesn't seem like updating will be a problem.
Are there any major issues with version two of the ICS update? I have read a lot of people that had issues with the first version of ICS that got released, and I know AT&T pulled it as an OTR update, but haven't heard a lot about version two. The people who have it are you satisfied with it? Did anyone prefer Gingerbread?
Thanks in advance for any help, and sorry if these questions have been answered already, I really did read through a LOT of information before posting here, and haven't seen these answered.

You don't need to root to unlock the phone. You just need to insert a code you buy from a seller on the internet.
I'm running the ULCHJ version of ICS and it works fine. I experienced the same GPS issue i had in GB, but the same fix worked it out and it I'm totally happy with it.
I can say, hope i won't regret, that there's nothing i should fix so far. Some minor issues were fixed as soon as i went through, I'm quite satisfied with this ROM now.

DarkBlaidd said:
Howdy Folks!​
I recently got a SGH-I927 that is locked to AT&T.
I have read what I believe is all the relevant data about how to do the things I want, and I think I have it down, but I want to make sure I have everything exactly correct. I still have 6 days left with Virgin Mobile before I have to have all this done.
What I want to do...
Root
Back up my EFS
Update from 2.3.6 to 4.0.4
Carrier Unlock from AT&T so I can use a T-Mobile MVNO.
So my question is- is this the best order to do things in? I know I have to root before I can Unlock the phone or Backup my EFS, but I notice that there are two different methods for Rooting. I can root before I update to ICS or after. Does it make a difference? Which method is easier, which one is more reliable/safer? I also noticed that Unlocking the phone after updating to ICS requires an extra step, so that would be another factor.
Kies seems to be working, and when I plugged my phone in, it offered to update me from 2.3.6 (Baseband Ver I927UCKL1) to 4.04 (Baseband Ver I927UCLJ3), so it doesn't seem like updating will be a problem.
Are there any major issues with version two of the ICS update? I have read a lot of people that had issues with the first version of ICS that got released, and I know AT&T pulled it as an OTR update, but haven't heard a lot about version two. The people who have it are you satisfied with it? Did anyone prefer Gingerbread?
Thanks in advance for any help, and sorry if these questions have been answered already, I really did read through a LOT of information before posting here, and haven't seen these answered.
Click to expand...
Click to collapse
hi dark blaidd, welcome to glide!
if i were to do it over again i would backup my efs via adb on my computer before rooting or anything.
i used fastgsm to unlock my phone which is a codeless way to unlock and i suspect its how i lost my imei
certainly get a code and use dmans uclj3 deodexed rooted as the stable rom.. then you can use es explorer to modify sirgps.conf and gps.conf to get your gps working. before i switched to cm10.1 JB I was running it with no issues and instant GPS lock in all apps.
I will likely switch back as I have a new hands free stereo for my car that I would like to legally take advantage of
let us know if you run into issues you will need to do a few searches.

sbiricuda said:
You don't need to root to unlock the phone. You just need to insert a code you buy from a seller on the internet.
Click to expand...
Click to collapse
I'm a poor boy, so I am probably going to try and save a few bucks by using this method, which requires root.
I'm running the ULCHJ version of ICS and it works fine. I experienced the same GPS issue i had in GB, but the same fix worked it out and it I'm totally happy with it.
Click to expand...
Click to collapse
What was the GPS issue? Can you link to the fix please?
I can say, hope i won't regret, that there's nothing i should fix so far. Some minor issues were fixed as soon as i went through, I'm quite satisfied with this ROM now.
Click to expand...
Click to collapse
Cool, thanks for giving your opinion. How good is your battery life?

yohan4ws said:
hi dark blaidd, welcome to glide!
if i were to do it over again i would backup my efs via adb on my computer before rooting or anything.
Click to expand...
Click to collapse
Sounds like a good idea, I will do that.
i used fastgsm to unlock my phone which is a codeless way to unlock and i suspect its how i lost my imei
Click to expand...
Click to collapse
Noted, I will stay away from fastgsm. I think I am going to do this or GalaxSim Unlock.
certainly get a code and use dmans uclj3 deodexed rooted as the stable rom.. then you can use es explorer to modify sirgps.conf and gps.conf to get your gps working. before i switched to cm10.1 JB I was running it with no issues and instant GPS lock in all apps.
Click to expand...
Click to collapse
I can't believe I am about to say this, I have spent the last two years on custom ROMs, but I think I am fine with stock for now. The ROMs for the Glide look promising, but I MUST have Camera and Bluetooth, so I will probably wait until those issues get ironed out. There is also a chance that Samsung will update us to Jellybean, they just released an update for the Galaxy S2, so it's possible.
let us know if you run into issues you will need to do a few searches.
Click to expand...
Click to collapse
Thanks! I believe I have done enough research to do what I want, so hopefully I won't make any dumb mistakes.

DarkBlaidd said:
Update from 2.3.6 to 4.0.4
Click to expand...
Click to collapse
Don't bother with ICS, the official ROM has issues and we never did much dev at that level. Go to CM10.1 once you have the ICS bootloader.
Carrier Unlock from AT&T so I can use a T-Mobile MVNO.
Click to expand...
Click to collapse
About that... AT&T phones, even once unlocked, cannot use UMTS or HSPA+ on T-Mobile's network. It's a physical limitation of the radio. ONLY do this if you already KNOW you will be happy with EDGE.

DarkBlaidd said:
I can't believe I am about to say this, I have spent the last two years on custom ROMs, but I think I am fine with stock for now. The ROMs for the Glide look promising, but I MUST have Camera and Bluetooth, so I will probably wait until those issues get ironed out.
Click to expand...
Click to collapse
I'm in same boat here I guess. Just ordered a Glide, looking forward to having a physical keyboard again since my TP2 days. I was checking out the ROM options, found the link for "Stock UCLJ3 Rom" and it looks like that is the way go, other than maybe just staying stock... I need Bluetooth, Camera, GPS, and Tethering to work, so I guess I won't be messing around with anything fancy.
So don't do any OTA upgrade at all when I first get it out of the box? Just back it up, then root, and install UCLJ3 via CWM? Is this the best choice?
roothorick said:
Don't bother with ICS, the official ROM has issues and we never did much dev at that level. Go to CM10.1 once you have the ICS bootloader.
Click to expand...
Click to collapse
Doesn't CM10.1 still have issues, like with bluetooth, GPS, and camera?

idenlover said:
Doesn't CM10.1 still have issues, like with bluetooth, GPS, and camera?
Click to expand...
Click to collapse
There is not and never has been GPS problems that actually affect normal use. I don't know where people are getting that from. There's some anomalies in the data returned, but nothing that's actually used by the location API.
Bluetooth itself works, but there are some audio layer problems that interfere with headsets/earpieces and the like. (TBH our whole audio layer is a mess right now.) Stuff like OBEX and tethering should work fine.
Speaking of audio layer issues... there's still a longstanding bug where if userspace (i.e. an app; normal cell network phonecalls are fine) opens the microphone, audio output is corrupted. The biggest problem caused by this is the other person is basically unintelligible when calling in Skype. That and Bluetooth audio routing are really the only big problems we still have.
The camera was fixed months and months and months ago. I discovered the original fix even. There was a problem with audio in the video recorder that has now been solved recently.

roothorick said:
There is not and never has been GPS problems that actually affect normal use. I don't know where people are getting that from. There's some anomalies in the data returned, but nothing that's actually used by the location API.
Bluetooth itself works, but there are some audio layer problems that interfere with headsets/earpieces and the like. (TBH our whole audio layer is a mess right now.) Stuff like OBEX and tethering should work fine.
Speaking of audio layer issues... there's still a longstanding bug where if userspace (i.e. an app; normal cell network phonecalls are fine) opens the microphone, audio output is corrupted. The biggest problem caused by this is the other person is basically unintelligible when calling in Skype. That and Bluetooth audio routing are really the only big problems we still have.
The camera was fixed months and months and months ago. I discovered the original fix even. There was a problem with audio in the video recorder that has now been solved recently.
Click to expand...
Click to collapse
OK, so then just the random app microphone and bluetooth issues still remain... So you still say it's worth it? I'm leaning towards the debloated rooted stock as I'm just lazy and want everything to work.

idenlover said:
OK, so then just the random app microphone and bluetooth issues still remain... So you still say it's worth it? I'm leaning towards the debloated rooted stock as I'm just lazy and want everything to work.
Click to expand...
Click to collapse
Official ICS was something of a ****storm, as Samsung never did get it to work quite right. There was a myriad of weird keyboard issues, intermittent radio problems, and come to think of it, I think I know where the GPS thing came from... official ROMs have lethargic GPS if you're not on AT&T. I'd say 99% of power users with a Glide are on one build/variant or the other of CM10.1 because it's the most problem-free ROM that's not, ugh, Gingerbread.
The primary value of official ICS to us was the kernel sources and RIL blobs -- the last few critical bits and pieces we needed to make our own ROMs and properly connect them to all the phone hardware.
I'd say, once you have everything backed up:
Flash official ICS UCLJ3 (for the bootloader and baseband)
Flash CWM over the top of it
Use CWM to flash the current CM10.1 build and gapps. Call it good.

roothorick said:
Official ICS was something of a ****storm, as Samsung never did get it to work quite right. There was a myriad of weird keyboard issues, intermittent radio problems, and come to think of it, I think I know where the GPS thing came from... official ROMs have lethargic GPS if you're not on AT&T. I'd say 99% of power users with a Glide are on one build/variant or the other of CM10.1 because it's the most problem-free ROM that's not, ugh, Gingerbread.
The primary value of official ICS to us was the kernel sources and RIL blobs -- the last few critical bits and pieces we needed to make our own ROMs and properly connect them to all the phone hardware.
I'd say, once you have everything backed up:
Flash official ICS UCLJ3 (for the bootloader and baseband)
Flash CWM over the top of it
Use CWM to flash the current CM10.1 build and gapps. Call it good.
Click to expand...
Click to collapse
Ok great, thanks for the explanation/breakdown So if there is an OTA update that pops up right out of the box, do I do it or skip it? And I'll have to root before flashing the UCLJ3, right?

idenlover said:
Ok great, thanks for the explanation/breakdown So if there is an OTA update that pops up right out of the box, do I do it or skip it? And I'll have to root before flashing the UCLJ3, right?
Click to expand...
Click to collapse
Might as well, as if it happens to be UCLJ3, well, it just did Step 1 for you, and if not, well, it doesn't matter either way.
You don't really need root for any of this since our bootloader is unlocked OOB.

roothorick said:
Might as well, as if it happens to be UCLJ3, well, it just did Step 1 for you, and if not, well, it doesn't matter either way.
You don't really need root for any of this since our bootloader is unlocked OOB.
Click to expand...
Click to collapse
Awesome, thanks for the help!:good:

roothorick said:
About that... AT&T phones, even once unlocked, cannot use UMTS or HSPA+ on T-Mobile's network. It's a physical limitation of the radio. ONLY do this if you already KNOW you will be happy with EDGE.
Click to expand...
Click to collapse
Damn it, that really sucks. Thank you so much for letting me know that, you saved me some headaches.
Edit: I did some digging around to get a technical explanation of this issue and stumbled across some unexpectedly good news, I can use HSPA+ on T-MO, well halfway at least, I'm going to make a new post as a public service.

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

Can't Send SMS; Can Receive SMS/MMS & Send MMS

Hey guys,
I think I've reached the point where it's time to call in the cavalry and see if anyone around here is having the same issue; there appears to be a plague going around on the Verizon network, specifically in the Pennsylvania area, preventing people from sending SMS, but still receiving fine (and 4G works fine too, for the record). MMS still sends / receives fine, but I'm unable to send SMS. There are tricks to allowing a single SMS message to go through which involves toggling Airplane mode on / off every. Single. Time. People have also had success with turning 4G off completely, using the CDMA band after a reboot at which point they can send *several*, but still end up with the same issue.
The only solution I've read about that FIXED it is by reverting back to complete stock from VZW. Performing factory resets, using other ROMs, etc etc...doesn't work. I'd REALLY rather not do this and, frankly, would rather use 3G / toggle Airplane mode for texts than use Sense and get off of my ROM (http://forum.xda-developers.com/showthread.php?t=2560831).
People from other device forums on XDA are having the same problem; the ones I've seen that are active discussions are the Samsung Galaxy S III & IV. They're mostly CM ROMs *as well as* AOSP ROMs in general.
http://forum.xda-developers.com/showthread.php?t=2532414
http://forum.xda-developers.com/showthread.php?t=2658572
SIM card replacements are a no-go, and the recorded instances seem to be in the 717 / 570 area codes, mostly. Now I DO know that VZW released an OTA update for the One recently, and I'm relatively confident that would fix the issue, but I've no idea why. I'm thinking perhaps they dispatched new radios? I looked around a bit and couldn't find any flashable zips of radios extracted from the latest OTA, that's the next step I'll be trying once that download finishes.
So is anyone else having this issue? Any word on fixes?

The newest firmware from the latest OTA can be found in the 2nd post in this thread: http://forum.xda-developers.com/showthread.php?t=2485319
If you've already flashed the latest firmware then I'm not sure what to tell you... maybe ask your favorite rom developer to take a look at the latest OTA in regards to this issue?

If it has the stock rom and OTA update why not take it to the store and let them look at it. Something might be wrong with your account.

movieman999 said:
Hey guys,
I think I've reached the point where it's time to call in the cavalry and see if anyone around here is having the same issue; there appears to be a plague going around on the Verizon network, specifically in the Pennsylvania area, preventing people from sending SMS, but still receiving fine (and 4G works fine too, for the record). MMS still sends / receives fine, but I'm unable to send SMS. There are tricks to allowing a single SMS message to go through which involves toggling Airplane mode on / off every. Single. Time. People have also had success with turning 4G off completely, using the CDMA band after a reboot at which point they can send *several*, but still end up with the same issue.
The only solution I've read about that FIXED it is by reverting back to complete stock from VZW. Performing factory resets, using other ROMs, etc etc...doesn't work. I'd REALLY rather not do this and, frankly, would rather use 3G / toggle Airplane mode for texts than use Sense and get off of my ROM (http://forum.xda-developers.com/showthread.php?t=2560831).
People from other device forums on XDA are having the same problem; the ones I've seen that are active discussions are the Samsung Galaxy S III & IV. They're mostly CM ROMs *as well as* AOSP ROMs in general.
http://forum.xda-developers.com/showthread.php?t=2532414
http://forum.xda-developers.com/showthread.php?t=2658572
SIM card replacements are a no-go, and the recorded instances seem to be in the 717 / 570 area codes, mostly. Now I DO know that VZW released an OTA update for the One recently, and I'm relatively confident that would fix the issue, but I've no idea why. I'm thinking perhaps they dispatched new radios? I looked around a bit and couldn't find any flashable zips of radios extracted from the latest OTA, that's the next step I'll be trying once that download finishes.
So is anyone else having this issue? Any word on fixes?
Click to expand...
Click to collapse
Those area codes for all phones on aosp roms are not working right now. Since 2/20/14. Has nothing to do with HTC or their firmware. I'ts a bizarre Verizon 4G issue. I am in the 717 area code with a Note 2 with the issue. I have seen others with S4 and S3. Verizon is aware of the issue and is working with another XDA member to fix it. To date it's not resolved.

DreamFX said:
Those area codes for all phones on aosp roms are not working right now. Since 2/20/14. Has nothing to do with HTC or their firmware. I'ts a bizarre Verizon 4G issue. I am in the 717 area code with a Note 2 with the issue. I have seen others with S4 and S3. Verizon is aware of the issue and is working with another XDA member to fix it. To date it's not resolved.
Click to expand...
Click to collapse
Thanks DreamFX; I've been following this thread (http://forum.xda-developers.com/showthread.php?t=2658572&page=6) lately as they seem to be the most on top of it. I can't believe Verizon has let this issue go on for so long, but given that it seems to only be relevant to those of us with AOSP ROM's, I guess it makes sense. At least I'm still able to send texts, if not only through a silly process of toggling airplane mode on / off. Hopefully it gets resolved soon...

DreamFX said:
Those area codes for all phones on aosp roms are not working right now. Since 2/20/14. Has nothing to do with HTC or their firmware. I'ts a bizarre Verizon 4G issue. I am in the 717 area code with a Note 2 with the issue. I have seen others with S4 and S3. Verizon is aware of the issue and is working with another XDA member to fix it. To date it's not resolved.
Click to expand...
Click to collapse
movieman999 said:
Thanks DreamFX; I've been following this thread (http://forum.xda-developers.com/showthread.php?t=2658572&page=6) lately as they seem to be the most on top of it. I can't believe Verizon has let this issue go on for so long, but given that it seems to only be relevant to those of us with AOSP ROM's, I guess it makes sense. At least I'm still able to send texts, if not only through a silly process of toggling airplane mode on / off. Hopefully it gets resolved soon...
Click to expand...
Click to collapse
I'm getting this too, just started for me today from what I can tell. Driving me bonkers but, Airplane mode toggle totally works for me. :cyclops:
VZW SGS4 running AOSPA with 804 area code operating in Oregon.

dickenam said:
I'm getting this too, just started for me today from what I can tell. Driving me bonkers but, Airplane mode toggle totally works for me. :cyclops:
VZW SGS4 running AOSPA with 804 area code operating in Oregon.
Click to expand...
Click to collapse
Whoa, that's weird. I really thought it was isolated to the 717 area code. It's getting pretty crazy...I've been dealing with this for a few weeks now and my patience is running thin. Unfortunately it's not like we can just report this to VZW because all anyone would tell us to do is "restore to factory", which simply isn't a solution.

movieman999 said:
Whoa, that's weird. I really thought it was isolated to the 717 area code. It's getting pretty crazy...I've been dealing with this for a few weeks now and my patience is running thin. Unfortunately it's not like we can just report this to VZW because all anyone would tell us to do is "restore to factory", which simply isn't a solution.
Click to expand...
Click to collapse
Yup, I thought so too. Just cropped up between 10a and 11a PDT. Like you said MMS is fine, simply affects SMS. And yes, restoring stock is simply not an option. Going to TMobile, however, is totally an option that I'm considering more and more often......
EDIT: AND SMS began sending properly (without workaround) for me around 8p PDT last night, just tested and still ok. RESOLVED!
EDIT EDIT: Issue now persists....sadface =[
Sent from my SCH-I545 using Tapatalk

dickenam said:
Yup, I thought so too. Just cropped up between 10a and 11a PDT. Like you said MMS is fine, simply affects SMS. And yes, restoring stock is simply not an option. Going to TMobile, however, is totally an option that I'm considering more and more often......
EDIT: AND SMS began sending properly (without workaround) for me around 8p PDT last night, just tested and still ok. RESOLVED!
EDIT EDIT: Issue now persists....sadface =[
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
IM getting it now. but not exactly the same. phone freezes without warning and I have to toggle airplane mode and restart to get it to unfreeze. this happened after the last OTA update. I am going to a custom ROM until I don't read anything about this for a while

Issue with Madhi-ROM 4.4.2 and data

Hello,
I have flashed Madhi-ROM 4.4.2 yesterday night and it had LTE working properly. Today, I ran into an issue where it would no longer connect to data at all. I have reflashed the stock rom and updated profile and prl then reflashed Madhi-rom 4.4.2 and at the screen "Activate mobile data service", it just keeps running and occasionally make a call to activate mobile data which ends up failing. I don't know if this is a common issue, but I'd like my mobile data to work. Other than this issue, I think its a very nice rom. Any help would be greatly appreciated.

staro0989 said:
Hello,
I have flashed Madhi-ROM 4.4.2 yesterday night and it had LTE working properly. Today, I ran into an issue where it would no longer connect to data at all. I have reflashed the stock rom and updated profile and prl then reflashed Madhi-rom 4.4.2 and at the screen "Activate mobile data service", it just keeps running and occasionally make a call to activate mobile data which ends up failing. I don't know if this is a common issue, but I'd like my mobile data to work. Other than this issue, I think its a very nice rom. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Have you requested help in the appropriate thread?
Any issues that I have had is best directed to the appropriate thread.

mesacarvin said:
Have you requested help in the appropriate thread?
Any issues that I have had is best directed to the appropriate thread.
Click to expand...
Click to collapse
I would love too, but I don't have my required 10 posts.

staro0989 said:
I would love too, but I don't have my required 10 posts.
Click to expand...
Click to collapse
oh okay
Seems like some people have been having 4G connection issues not only with Mahdi but other Roms as well.
Here are some of the suggestions:
Toggle Airplane mode for 10 seconds then turn off
Dirty flash ROM again
Return to stock and update PRL then reflash custom ROM
Keep data connection at 3G and live with it
You can also try flashing and comparing the Gee version vs. the ls970 version
It's hit or miss with this phone. No rhyme or reason for no consistency for such a basic requirement
I'm sure more experienced members will offer more suggestions
Hope this helps

Yeah, LTE is extremely sketchy on AOSP ROMs, Gee or LS970. Since the connection is just so inconsistent, I've found that the best thing to do is, as listed above, toggle airplane mode on/off, reflashing, or just sticking with 3G. 4G works flawlessly on stock LG ROMs though.
Sent from my LG-gee using Tapatalk

mesacarvin said:
oh okay
Seems like some people have been having 4G connection issues not only with Mahdi but other Roms as well.
Here are some of the suggestions:
Toggle Airplane mode for 10 seconds then turn off
Dirty flash ROM again
Return to stock and update PRL then reflash custom ROM
Keep data connection at 3G and live with it
You can also try flashing and comparing the Gee version vs. the ls970 version
It's hit or miss with this phone. No rhyme or reason for no consistency for such a basic requirement
I'm sure more experienced members will offer more suggestions
Hope this helps
Click to expand...
Click to collapse
iamterence said:
Yeah, LTE is extremely sketchy on AOSP ROMs, Gee or LS970. Since the connection is just so inconsistent, I've found that the best thing to do is, as listed above, toggle airplane mode on/off, reflashing, or just sticking with 3G. 4G works flawlessly on stock LG ROMs though.
Sent from my LG-gee using Tapatalk
Click to expand...
Click to collapse
Thank you guys for the help. I tried all the fixes above with no luck. I have reverted back to the stock rom since I rather have my mobile data working than run an AOSP rom.

staro0989 said:
Thank you guys for the help. I tried all the fixes above with no luck. I have reverted back to the stock rom since I rather have my mobile data working than run an AOSP rom.
Click to expand...
Click to collapse
I believe I've struck gold with the latest Dirty Unicorn ROM!
Everything works: 4G, GPS, yes and even google calendar.
At first, I could only get 3G then one of options was just to simply display 4G instead of LTE in status bar then viola, 4G!
Probably just coincidence but I am one happy dude!
Might want to give DU a try

mesacarvin said:
I believe I've struck gold with the latest Dirty Unicorn ROM!
Everything works: 4G, GPS, yes and even google calendar.
At first, I could only get 3G then one of options was just to simply display 4G instead of LTE in status bar then viola, 4G!
Probably just coincidence but I am one happy dude!
Might want to give DU a try
Click to expand...
Click to collapse
I may give it a try sometime later. My phone works perfectly with the stock rom at the moment.

staro0989 said:
Thank you guys for the help. I tried all the fixes above with no luck. I have reverted back to the stock rom since I rather have my mobile data working than run an AOSP rom.
Click to expand...
Click to collapse
Have you tried SuperNexus? Honestly heard nothing but good things about this rom as long as the installation instructions are followed exactly. LTE, GPS, Bluetooth, and battery life are all working from what i've heard, you might wanna give it a try.
http://forum.xda-developers.com/showthread.php?t=2370804

grivera1296 said:
Have you tried SuperNexus? Honestly heard nothing but good things about this rom as long as the installation instructions are followed exactly. LTE, GPS, Bluetooth, and battery life are all working from what i've heard, you might wanna give it a try.
http://forum.xda-developers.com/showthread.php?t=2370804
Click to expand...
Click to collapse
I will definitely give this one a try.

How to Enable Wi-Fi Calling on the LG G3 on Candy5 Android 5.1.1 ROM

Hello, I would like to preface this post by saying I'm a complete noob to XDA Forums and custom ROMs as well. I've know about XDA Developers for years, just never been much of a tinkerer when it comes to Android, I just prefer stock.
Well recently, I bought a used LG G3 because the deal was just to good to pass up. It was my first time using a ROM other than stock and it was utterly disgusting in comparison. I hated it so much I installed my first ROM ever, and it was Candy5 for I heard CynogenMod stopped supporting the LG G3 is some capacity. Well, I've been using it for a while now and made it look as close as I could to stock, there's just one problem.
I recently enabled Wi-Fi calling on Ting. The device was a Verizon model, but I purchased it unlocked, and activated it on the MNVO Ting. Well, it wasn't working so I was wondering what's up. I read that you had to enable it within the devices settings, but all guides were not specific to the custom ROM I had installed, and even following along as closely as I could, the option for Wi-Fi calling wasn't there. I've read that if Wi-Fi calling doesn't appear, your device doesn't support it. But, everywhere I've read, has been consistent that Wi-Fi calling is supported on the LG G3.
So, I ask you long time tinkerers, do you know how to enable Wi-Fi calling within the Candy5 ROM? Does it just not support it? I even used the neat search feature within the settings app and couldn't find a switch for it. Please help!

NeatAndClean said:
Hello, I would like to preface this post by saying I'm a complete noob to XDA Forums and custom ROMs as well. I've know about XDA Developers for years, just never been much of a tinkerer when it comes to Android, I just prefer stock.
Well recently, I bought a used LG G3 because the deal was just to good to pass up. It was my first time using a ROM other than stock and it was utterly disgusting in comparison. I hated it so much I installed my first ROM ever, and it was Candy5 for I heard CynogenMod stopped supporting the LG G3 is some capacity. Well, I've been using it for a while now and made it look as close as I could to stock, there's just one problem.
I recently enabled Wi-Fi calling on Ting. The device was a Verizon model, but I purchased it unlocked, and activated it on the MNVO Ting. Well, it wasn't working so I was wondering what's up. I read that you had to enable it within the devices settings, but all guides were not specific to the custom ROM I had installed, and even following along as closely as I could, the option for Wi-Fi calling wasn't there. I've read that if Wi-Fi calling doesn't appear, your device doesn't support it. But, everywhere I've read, has been consistent that Wi-Fi calling is supported on the LG G3.
So, I ask you long time tinkerers, do you know how to enable Wi-Fi calling within the Candy5 ROM? Does it just not support it? I even used the neat search feature within the settings app and couldn't find a switch for it. Please help!
Click to expand...
Click to collapse
Yeah WiFi calling won't be an option on AOSP ROMs... Its cooked into the stock software (for at least t mobile) and only works on stock based ROMs. There was a developer that tried to use the code from I BELIEVE the nexus 6 and adopt it to our devices but it never got pushed through. If you want WiFi calling/VolTE, stick with stock ROMs.

yanowman said:
Yeah WiFi calling won't be an option on AOSP ROMs... Its cooked into the stock software (for at least t mobile) and only works on stock based ROMs. There was a developer that tried to use the code from I BELIEVE the nexus 6 and adopt it to our devices but it never got pushed through. If you want WiFi calling/VolTE, stick with stock ROMs.
Click to expand...
Click to collapse
Ah, I see. Hopefully some day it would be available on custom ROMs. Using the stock ROM is not even worth the gloriousness of Wi-Fi calling, and that's really saying something, because my room is a complete dead zone for reception. I have to walk out on my porch every time I want to place / receive phones calls or SMS texts.

NeatAndClean said:
Ah, I see. Hopefully some day it would be available on custom ROMs. Using the stock ROM is not even worth the gloriousness of Wi-Fi calling, and that's really saying something, because my room is a complete dead zone for reception. I have to walk out on my porch every time I want to place / receive phones calls or SMS texts.
Click to expand...
Click to collapse
Yeah I completely feel your problem. Over at my house (which is in the maybe 10 minutes from the main bay area) there is NO reception, only when you walk down the street is there reception. When I was on Verizon I got their WiFi booster thing... Now that I'm on T mob, I use WiFi calling bakdd info their ROMS