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.

"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] AOSP Known Issues?

I'm just trying to keep these straight, since I've seen bits and pieces of various problems on the various dev threads. Would someone be so kind as to check my logic here? Thanks in advance!
Problem: Can't get a GPS lock after flashing any AOSP-based 4.3 rom
Solution: Flash back to stock (RUU?), open up Maps or otherwise get a good GPS lock, flash back to your rom of choice
Burning Question: Why does this happen and why does stock flashing work?
(Idiot Newbie Question: RUU is basically a stock image? I need an encrypted version? Do I need to worry about breaking my rumrunner s-off/root?)
Problem: When on a phone call, and the other party hangs up, you get "call lost" instead of the standard graceful disconnect.
Solution: Isn't one yet. Gotta wait for a fix to be made.
Problem: Signal strength meter shows impossibly low values, despite data, voice, LTE all working as expected.
Solution: No idea. Of the 3 roms I've tried, (CM10, Liquid, Carbon), all do this. Minor problem, but anyways.
Problem: Purplish tint on the camera in dark scenes.
Solution: Phone's defective, send it in. / Or: Wait for a software patch.
Which is it?

@Karunamon
Problem 1. Not really figured out yet. All you need to do is flash any Sense rom.
Problem 2. Is fixed! For a couple of days now for any ROM built after 11th of this month.
Problem 3. I get the same dBm on Sense and AOSP. Sure a lot of other people do also. But people panic when looking at the network bars.
Problem 4. I get no purple/pink tint when on Sense but after flashing AOSP I get the purple/pink tint on my FFC. So I would wait til 4.3.

Is the issue with AOSP roms killing the radios on certain phones fixed as of the 11th?

adrenalinemotion said:
Is the issue with AOSP roms killing the radios on certain phones fixed as of the 11th?
Click to expand...
Click to collapse
That isn't AOSP fault. Something was happening after the s-off procedures that people need to do a factory reset from HBOOT before flashing anything to reset their radio
Sent from my One using Tapatalk now Free

Flyhalf205 said:
That isn't AOSP fault. Something was happening after the s-off procedures that people need to do a factory reset from HBOOT before flashing anything to reset their radio
Sent from my One using Tapatalk now Free
Click to expand...
Click to collapse
I s-off'd, unlocked my bootloader and rooted with no issues. I was stock rooted and everything functioned. As soon as I flashed an AOSP rom, the radio broke. I had data, but no voice. (You posted in a thread I started and helped me fix my radio)
I'm not trying to argue or anything, just trying to understand.
Are you saying that I should now be able to flash an AOSP rom and have no radio issues now since I reflashed the stock recovery to fix the radio, then flashed back to TWRP?

adrenalinemotion said:
I s-off'd, unlocked my bootloader and rooted with no issues. I was stock rooted and everything functioned. As soon as I flashed an AOSP rom, the radio broke. I had data, but no voice. (You posted in a thread I started and helped me fix my radio)
I'm not trying to argue or anything, just trying to understand.
Are you saying that I should now be able to flash an AOSP rom and have no radio issues now since I reflashed the stock recovery to fix the radio, then flashed back to TWRP?
Click to expand...
Click to collapse
I really think you can go back to an AOSP rom. I have no problems and tons of other people with no problems. I noticed that the guys who s-off with sonic didn't have these issues. That is just why I think it is something with the whole current s-off process.
But if you do decide to give AOSP another try. I would flash when you have about a hour of free time with a computer just to make sure it doesn't crap out again.

Does one need to have the stock recovery to reset from Hboot?
Sent from my HTC6500LVW using Tapatalk now Free

Flyhalf205 said:
@Karunamon
Problem 1. Not really figured out yet. All you need to do is flash any Sense rom.
Problem 2. Is fixed! For a couple of days now for any ROM built after 11th of this month.
Problem 3. I get the same dBm on Sense and AOSP. Sure a lot of other people do also. But people panic when looking at the network bars.
Problem 4. I get no purple/pink tint when on Sense but after flashing AOSP I get the purple/pink tint on my FFC. So I would wait til 4.3.
Click to expand...
Click to collapse
Excellent, seems I just need to dig up a sense rom and then reflash something new and i'll be good on 1 and 2.
Any idea what could be causing 3, though? For comparison, when I was on stock, the meter was completely full for LTE in my home. Now, it's one bar. Coverage is still good though and data still works at breakneck speeds, so I don't think it's an actual signal issue.

Karunamon said:
Excellent, seems I just need to dig up a sense rom and then reflash something new and i'll be good on 1 and 2.
Any idea what could be causing 3, though? For comparison, when I was on stock, the meter was completely full for LTE in my home. Now, it's one bar. Coverage is still good though and data still works at breakneck speeds, so I don't think it's an actual signal issue.
Click to expand...
Click to collapse
check DBM isntead of looking at your bars to see if you even have an issue.

The signal issue sounds the same as AOSP on the Rezound. The signal strength would be same, but the signal icon would be different. Basically, HTC has set the icons to show more than AOSP.
I didn't factory reset after using rumrunner and the only thing I have noticed was I would not connect to 4g as much or as fast as before. It seems to be getting better though. I am running bonestock.
Sent from my phone using an app

Like it was explained to me the bars are kinda like the idiot lights on a cars dash. They really don't do much. Aosp shows your true signal and sense and so on shows a false truth just so people doesn't complain about poor signal. As long as my data works I don't care if I have zero bars.
Sent from my M7 using Tapatalk

Are there any bluetooth issue's ?

nujackk said:
Are there any bluetooth issue's ?
Click to expand...
Click to collapse
No issues using a Bluetooth headset here.
Can't say anything about Bluetooth audio streaming, haven't tried that yet.

sawedust said:
No issues using a Bluetooth headset here.
Can't say anything about Bluetooth audio streaming, haven't tried that yet.
Click to expand...
Click to collapse
IR work yet?

exzacklyright said:
IR work yet?
Click to expand...
Click to collapse
IR is working on VanirAOSP.
I'm using Smart IR Remote to control my devices; great interface and works well with the majority of the stuff that I have.
Not sure what the progress is re: IR with the other AOSP ROMs.

With smart ir remote it should work on any Rom.
Sent from my HTC6500LVW using XDA Premium 4 mobile app

sawedust said:
No issues using a Bluetooth headset here.
Can't say anything about Bluetooth audio streaming, haven't tried that yet.
Click to expand...
Click to collapse
The streaming is my main concern, Use is inmy truck and main reason I will try to keep my unlimited data FOREVER

adrenalinemotion said:
I s-off'd, unlocked my bootloader and rooted with no issues. I was stock rooted and everything functioned. As soon as I flashed an AOSP rom, the radio broke. I had data, but no voice. (You posted in a thread I started and helped me fix my radio)
I'm not trying to argue or anything, just trying to understand.
Are you saying that I should now be able to flash an AOSP rom and have no radio issues now since I reflashed the stock recovery to fix the radio, then flashed back to TWRP?
Click to expand...
Click to collapse
Did this happen using twrp or cwm? Some folks are thinking its cwm causing this.
Sent from my HTC6500LVW using Tapatalk
---------- Post added at 08:29 AM ---------- Previous post was at 08:28 AM ----------
Flyhalf205 said:
I really think you can go back to an AOSP rom. I have no problems and tons of other people with no problems. I noticed that the guys who s-off with sonic didn't have these issues. That is just why I think it is something with the whole current s-off process.
But if you do decide to give AOSP another try. I would flash when you have about a hour of free time with a computer just to make sure it doesn't crap out again.
Click to expand...
Click to collapse
This happened to people who hardware s-off'd and flashed the gpe rom too. Don't think it has anything to do with it.
Sent from my HTC6500LVW using Tapatalk

NF9 tmobile firmware update discussion

THIS THREAD IS FOR GENERAL DISCUSSION OF THE TMOBILE NF9 FIRMWARE UPDATE
Everyone have their phones right where they want them after the last two firmware updates? ...
Tough, NF9 is available for download at Sammobile and it looks like there's some nice features, seamless switching between wifi calling and regular calls, Volte switching and more.
Break out Odin, chainfire root and everything all over again.
(If you have s5, or s4, i noticed they have updates as well)
ANNOUNCEMENT
If you need the individual files for upgrade, @toastido has worked hard to get everything together for you HERE
If you're looking for the easiest way to upgrade your firmware and have a deodexed, zipaligned stock ROM for the new firmware with all the bells and whistles, and debloated, @effortless has you taken care of... HERE you will find the effortless guide to upgrade the firmware to NF9, and HERE you will find the Effortless ROM updated to NF9.
Lets upgrade our Note 3's again...for the third time... in just a couple months.
I see this question come up every time theres an upgrade, so...
YES! You can use the previous methods of root and recovery with this firmware.
If you need it:
I odin over TWRP from HERE
and then drop into recovery and flash the latest SuperSU by @Chainfire from HERE
But, if you need to know how root NF9, @effortless has you taken care of HERE, and it is also discussed later in this thread. Thanks to @Vegasden for the link to effortless root for NF9.

I'm working on it now. Going to open a new thread with the firmware extracted into its parts as I have done for the past 3.

I only updated to NF4 three days ago and I will wait a week or two to do the same with NF9 especially if there isn't much in it

Just finished the update, baseband and firmware are now nf9 but pda and csc are nf4 because i restored my bobcat nandroid. Hopefully bobcat updates soon. I know @effortless is working on it.

sacky73 said:
I only updated to NF4 three days ago and I will wait a week or two to do the same with NF9 especially if there isn't much in it
Click to expand...
Click to collapse
The ability to smoothly transition between wifi and 4G calls without drops was enough for me. The whole reason I never used wifi calls is because I would be in the house or the office talking to a customer, walk out the door and get down the road on a wifi call and lose it.

Megaflop666 said:
The ability to smoothly transition between wifi and 4G calls without drops was enough for me. The whole reason I never used wifi calls is because I would be in the house or the office talking to a customer, walk out the door and get down the road on a wifi call and lose it.
Click to expand...
Click to collapse
Is this confirmed...? It looks like T-Mobile wouldn't say anything more than "Wifi calling enhancement", and I don't see other sources posting this as a change.

kgptzac said:
Is this confirmed...? It looks like T-Mobile wouldn't say anything more than "Wifi calling enhancement", and I don't see other sources posting this as a change.
Click to expand...
Click to collapse
I have been playing with it and it's a little touchy but i switched between Wifi and lte earlier on a call. You have to set up smart network switch and some other details. S4 seems to have gotten the most noticeable changes in its UI for this round of firmware updates.

The S4 got updated to 4.4.4 with NH7.
Is NF9 still 4.4.2?
NM... just saw a screenshot in Effortless' post.
Still 4.4.2

rjohnstone said:
The S4 got updated to 4.4.4 with NH7.
Is NF9 still 4.4.2?
NM... just saw a screenshot in Effortless' post.
Still 4.4.2
Click to expand...
Click to collapse
Yes still 4.4.2, and my s5 is still 4.4.2. I'm a little ticked about that. The phone i gave my daughter gets the latest rom. Lol

Update. The wifi switching i saw was a fluke. I was on a call, switched wifi on and got the wifi call signal in my status bar. Turned off wifi and everything stayed connected. Tried a call initiated from wifi calling and turned wifi off and got a message asking if i wanted to find another network to keep the call, and it showed my call was gone. BUT, the call didn't hang up on the other phone, it showed connected. Any thoughts anyone?

Megaflop666 said:
Update. The wifi switching i saw was a fluke. I was on a call, switched wifi on and got the wifi call signal in my status bar. Turned off wifi and everything stayed connected. Tried a call initiated from wifi calling and turned wifi off and got a message asking if i wanted to find another network to keep the call, and it showed my call was gone. BUT, the call didn't hang up on the other phone, it showed connected. Any thoughts anyone?
Click to expand...
Click to collapse
Well i don't think it was designed to have people flipping wifi on and off to see if it keeps a call.
Try turning wifi calling on and leave it on and see if it drops a call when you are in and out of range of your router.
No i haven't tried it out yet but i do want to try out the personal cellspot....

rolling56 said:
Well i don't think it was designed to have people flipping wifi on and off to see if it keeps a call.
Try turning wifi calling on and leave it on and see if it drops a call when you are in and out of range of your router.
No i haven't tried it out yet but i do want to try out the personal cellspot....
Click to expand...
Click to collapse
Tried that too. Walked out of range of my router, five houses away, and it asked again. I will play with it some more this evening when i get home. Right now I'm not in a wifi area, plus I need to switch back to NF9 rom as I'm currently on nf4 bobcat rom.

Were you on LTE at the time? According to the Q&A they did at the event, you have to be on VoLTE for the seemless wifi handoff to work properly. I also wonder if their router is needed, but I wouldn't think so as it's mostly QoS changes on a normal WiFi router.

Megaflop666 said:
Tried that too. Walked out of range of my router, five houses away, and it asked again. I will play with it some more this evening when i get home. Right now I'm not in a wifi area, plus I need to switch back to NF9 rom as I'm currently on nf4 bobcat rom.
Click to expand...
Click to collapse
Pretty sure you have to be on NF9 stock for this stuff to work properly. The WiFi calling features and VoLTE features are baked into the stock rom, and when updated to NF9 they likely got updated. If you're running an NF4 base, it's highly likely it doesn't include the NF9 updates.

I agree with toastido, you have to have the NF9 stock for it to work. Also, I wonder, if it's not all going to work everywhere at this point. September 17/18 was mentioned a lot in their press release. So it might not be an immediate rollout. And, no, you don't have to use their router.

toastido said:
Pretty sure you have to be on NF9 stock for this stuff to work properly. The WiFi calling features and VoLTE features are baked into the stock rom, and when updated to NF9 they likely got updated. If you're running an NF4 base, it's highly likely it doesn't include the NF9 updates.
Click to expand...
Click to collapse
Oh no, misunderstanding. I'm on nf9 base. Have full nf9 on my phone. Just switch back to my nf4 rom for use during the day because i can't stand stock rom. All my testing and experimenting is on full nf9 base and stock rooted rom. Just switch back and forth between backups.
Later this evening in taking my other note 3 and stripping it down and doing nf9 on it and it will be my experimental nf9 toy and keep my daily on nf9/nf4.

I called my wife and walked away from my home wifi and lost the call when transferring from wifi to network. Walking back using network it was seamless to wifi and the call didn't drop so i don't know if that will happen all the time or not.

Sounds like my experience. I switched my phone back to full nf9 again and I'll be on it for experimenting purposes and such.... damn I forgot how ugly stock can be

can i upgrade my basebamd to nf9 without using a pc?

sevenslugs said:
can i upgrade my basebamd to nf9 without using a pc?
Click to expand...
Click to collapse
No
Sent from my SM-N900T using Tapatalk

LG G3 back to JellyBean

This may have been posted, If so, sorry, I could not find it.
Now that that I have installed the T-mo Lollipoop update, my phone is a paperweight. As I don't suppose T-mo will replace it....
Is there anyway to roll the LG-G3 back to KitKat or whatever version it was on WHEN IT WORKED PERFECTLY?
Any help would be appreciated, it is useless as it is.

Gdraft1 said:
This may have been posted, If so, sorry, I could not find it.
Now that that I have installed the T-mo Lollipoop update, my phone is a paperweight. As I don't suppose T-mo will replace it....
Is there anyway to roll the LG-G3 back to KitKat or whatever version it was on WHEN IT WORKED PERFECTLY?
Any help would be appreciated, it is useless as it is.
Click to expand...
Click to collapse
I ask this when fixing computers, why is it a paper weight lol.. whats wrong with the phone ? we need moar nfo ...

Paperweight
No or Spotty Wi/Fi
Cell signal has almost vanished (it I stand next to a T-mo tower I can get 5 bars for a minute)
Cell signal keeps dropping so the phone is constantly searching for a signal
Due to constantly searching for signals, the battery drain is actually watchable on the notification screen, about 1% a minute.
Phone will not stay connected long enough to complete a call.
All of these Issues happened after Lollipoop.
Hence, is there a way do "Upgrade" it back to Kit Kat.
I could not find anything on her about it. I did find a video on Youtube, but it was for a Verizon unit, not sure if it would be the same or not
I have two phones, same issue on both phones.

Gdraft1 said:
No or Spotty Wi/Fi
Cell signal has almost vanished (it I stand next to a T-mo tower I can get 5 bars for a minute)
Cell signal keeps dropping so the phone is constantly searching for a signal
Due to constantly searching for signals, the battery drain is actually watchable on the notification screen, about 1% a minute.
Phone will not stay connected long enough to complete a call.
All of these Issues happened after Lollipoop.
Hence, is there a way do "Upgrade" it back to Kit Kat.
I could not find anything on her about it. I did find a video on Youtube, but it was for a Verizon unit, not sure if it would be the same or not
I have two phones, same issue on both phones.
Click to expand...
Click to collapse
Unfortunately from my experiences and other people's experiences downgrading to Kitkat after Lollipop with data issues, you will still have those data issues when you go back to Kitkat. It seems going back to Kitkat via KDZ or TOT does not restore the modem or it does but the modem still does not function correctly. The only way to fix LTE and data issues was to flash Blisspop 2.3 and determining that data sticks on that rom. If it does, your data and modem issues should be resolved and you can use stock lollipop again. If you want to try this route here is my thread on how to fix it. Make sure you are rooted with twrp
http://forum.xda-developers.com/tmobile-lg-g3/help/lte-lollipop-issue-fix-t3075637

vel0city said:
Unfortunately from my experiences and other people's experiences downgrading to Kitkat after Lollipop with data issues, you will still have those data issues when you go back to Kitkat. It seems going back to Kitkat via KDZ or TOT does not restore the modem or it does but the modem still does not function correctly. The only way to fix LTE and data issues was to flash Blisspop 2.3 and determining that data sticks on that rom. If it does, your data and modem issues should be resolved and you can use stock lollipop again. If you want to try this route here is my thread on how to fix it. Make sure you are rooted with twrp
http://forum.xda-developers.com/tmobile-lg-g3/help/lte-lollipop-issue-fix-t3075637
Click to expand...
Click to collapse
Once I do that I will lose WiFi calling won't I?
It is my understanding once you over write T-mo's Rom you lose that.

Gdraft1 said:
Once I do that I will lose WiFi calling won't I?
It is my understanding once you over write T-mo's Rom you lose that.
Click to expand...
Click to collapse
Yes and No flashing blisspop rom will just fixed your data and LTE issues, I'm not telling you to keep the rom, that is entirely up to you. Yes keeping custom roms that are not stock will lose wifi calling and all the tmobile stuff. After you can confirm that LTE and data works you can then flash back to stock or restore to stock. That way you can still have Wifi calling and have a stock rom.