Develop Bugs

[Q] Wi-Fi Calling Removed... How to add back?

Newly rooted Tmo GS2 on 2.3.6. I used to use WiFi Calling quite a bit, but a few weeks back it disappeared. Calls with Tmo Customer Service says they don't know why it came off, but have put it back on, however the app remains missing from the Applications list.
Now that I have root, is there a way to force install this piece of software and regain this functionality?

fl4ian said:
Newly rooted Tmo GS2 on 2.3.6. I used to use WiFi Calling quite a bit, but a few weeks back it disappeared. Calls with Tmo Customer Service says they don't know why it came off, but have put it back on, however the app remains missing from the Applications list.
Now that I have root, is there a way to force install this piece of software and regain this functionality?
Click to expand...
Click to collapse
On the SGS2 , there is no app in the app drawer for wif-calling ... it is in settings under wireless .....

Thank you for that tidbit. I can't believe I missed it. Thank you thank you thank you!! It is now back in action.

So Im guessing that wifi-call isnt possible with Cyanogenmod yet? Im stuck with Juggernaut in that case. Which isnt a bad thing...but it would be nice if that feature was attained somehow.
Sent from my SGH-T989 using XDA App

alucardromero said:
So Im guessing that wifi-call isnt possible with Cyanogenmod yet? Im stuck with Juggernaut in that case. Which isnt a bad thing...but it would be nice if that feature was attained somehow.
Sent from my SGH-T989 using XDA App
Click to expand...
Click to collapse
No, not in the alpha CM builds yet...you need to use a stock-based ROM.

Desire Z on WIND Mobile (which radio version)

Has anyone figured out which radio version works best with WIND Mobile in Canada?
My phone seems to randomly lose data connection. To get data back, I turn mobile data off then on again. It happens so frequently, I have it in my Notification window as a toggle.
I have Automatcher v7 to match RIL with radio version. I also have wipe EFS.
Thanks,
Scott
Sent from my HTC Vision using XDA

skewty said:
Has anyone figured out which radio version works best with WIND Mobile in Canada?
My phone seems to randomly lose data connection. To get data back, I turn mobile data off then on again. It happens so frequently, I have it in my Notification window as a toggle.
I have Automatcher v7 to match RIL with radio version. I also have wipe EFS.
Thanks,
Scott
Sent from my HTC Vision using XDA
Click to expand...
Click to collapse
You could try to change your APN settings. Also i thought the DZ dosent work on wind because it has differrent frequencies?
Sent from my HTC Vision using xda premium

evilcuber said:
You need to change your APN settings. Also i thought the DZ dosent work on wind because it has differrent frequencies?
Click to expand...
Click to collapse
Oops! I meant G2 (T-Mobile). I have a G2.
If my APN settings were incorrect, why would my data work most of the time?

skewty said:
Oops! I meant G2 (T-Mobile). I have a G2.
If my APN settings were incorrect, why would my data work most of the time?
Click to expand...
Click to collapse
As someone who has friends on Wind... I'm thinking it may be your network. Also, you're not supposed to match the rils unless you're using sense. Which ROM are you running?
Sent from my Transformer TF101 using xda premium

skewty said:
Oops! I meant G2 (T-Mobile). I have a G2.
If my APN settings were incorrect, why would my data work most of the time?
Click to expand...
Click to collapse
Use latest Radio from T-Mobile 26.13.04.19_M, I'm on it, have never lost 3.5 G data connection

I am currently running ILWT but experienced the same running CM 7, ICS Audacity and ICS Quattro.
I have flashed the newest TMobile ROM a few times.. It must be the WIND network here.
Sent from my HTC Vision using XDA

Update
I don't think it is the network. My father's Amaze does not have this problem in the same places.
ILWT has been the most reliable ROM for me so far. I am currently running Andromadus b4 and am considering switching back because of the data drop-out issue. I have tried 5 different radio versions now.
It must be the ROM. Perhaps it encounters some data it can't make sense of and crashes. Perhaps it just needs to restart itself when this happens. A simple mobile data off, mobile data on fixes it almost every time.
I also find the bars reading incorrect. I be driving down the road with my screen on and the charger plugged in, and it will show me full bars. I can pull over and park for a few minutes, bars still full. Then suddenly half bars, no bars. This behavior is from a device that isn't being physically surrounded / shielded and is stationary.
Anyways, my G2 is getting old and it needs a another core to keep up with the way I now use it. I will wait for Jelly Bean but will likely switch to IOS.
Reasons If You Care
The menu button disaster is a big one for me. Also the lack of quick updates from Google for Nexus S and Nexus One. These devices should have had OS updates released on the same day the Galaxy Nexus was released.
ICS should have been backwards compatible for older devices as well. A few #ifdef in the code for fancy screen rendering and such. Big, huge fail!
Google, also, should have required no physical menu button for access to Google apps to enforce the new way. With only like 7% ICS market share no wonder app devs write for GB.
Google's handling of Android updates has opened my eyes.

skewty said:
I don't think it is the network. My father's Amaze does not have this problem in the same places.
ILWT has been the most reliable ROM for me so far. I am currently running Andromadus b4 and am considering switching back because of the data drop-out issue. I have tried 5 different radio versions now.
It must be the ROM. Perhaps it encounters some data it can't make sense of and crashes. Perhaps it just needs to restart itself when this happens. A simple mobile data off, mobile data on fixes it almost every time.
I also find the bars reading incorrect. I be driving down the road with my screen on and the charger plugged in, and it will show me full bars. I can pull over and park for a few minutes, bars still full. Then suddenly half bars, no bars. This behavior is from a device that isn't being physically surrounded / shielded and is stationary.
Anyways, my G2 is getting old and it needs a another core to keep up with the way I now use it. I will wait for Jelly Bean but will likely switch to IOS.
Reasons If You Care
The menu button disaster is a big one for me. Also the lack of quick updates from Google for Nexus S and Nexus One. These devices should have had OS updates released on the same day the Galaxy Nexus was released.
ICS should have been backwards compatible for older devices as well. A few #ifdef in the code for fancy screen rendering and such. Big, huge fail!
Google, also, should have required no physical menu button for access to Google apps to enforce the new way. With only like 7% ICS market share no wonder app devs write for GB.
Google's handling of Android updates has opened my eyes.
Click to expand...
Click to collapse
The issue isn't ICS. The issue is the vendors haven't released proper drivers for ICS. What we're dealing with is code we've hacked up to make things work. If the vendors released ICS source code for our devices things would be much more stable.
We're always working within our means. It's not Android/Google's fault and it's not an ICS issue, it's just circumstance.

Thanks
I realize where most of the issues lie. I am an EE grad so I can imagine how difficult hacking ROMs together without device drivers might be.
Writing ASM for a microproc with the datasheets is bad enough. Without knowing what each control register is for and what each bit controls, it is a guessing game at best. I get that.
I very much do appreciate your work. As you are aware, from reading my post, I run a ROM you contribute to. Thank you. You have prolonged the life / pleasure balance I require from my smartphone.
I would contribute more to the development, but my post count was less than 10. I was actually working towards my 10 posts today to post in the dev forums. (The Andromadus beta 4 thread to be more precise).

skewty said:
I realize where most of the issues lie. I am an EE grad so I can imagine how difficult hacking ROMs together without device drivers might be.
Writing ASM for a microproc with the datasheets is bad enough. Without knowing what each control register is for and what each bit controls, it is a guessing game at best. I get that.
I very much do appreciate your work. As you are aware, from reading my post, I run a ROM you contribute to. Thank you. You have prolonged the life / pleasure balance I require from my smartphone.
I would contribute more to the development, but my post count was less than 10. I was actually working towards my 10 posts today to post in the dev forums. (The Andromadus beta 4 thread to be more precise).
Click to expand...
Click to collapse
Drop by #g2ics on freenode if you're interested

I have the same issues, G2 on Wind as well. I've had some ROMs where it never occured, but then they had some kind of bug that left me unhappy. I'm currently on CM 7.2 RC1, and I keep a "data" toggle in my notification bar. When it drops I toggle it off and on and it connects again pretty quickly. Until about twelve months ago, MMS was unreliable, but I don't seem to have problems with that anymore.
In general I'm not happy with Android, but as the alternatives are all utterly closed systems I guess I'm stuck with it. It would be unbearable if it weren't for the hard work of all the developers around this forum. Thanks, developers

Agreed. Google has been a huge let down for me as well. Updates are slow or non existent in Canada (even on Nexus devices). Look at the percentage of devices that run ICS. JB is what ICS was supposed to be. I may get an iPhone for work. I am excited to compare it to my Samsung S3 on CM10.
Sent from my SGH-T999 using xda app-developers app

[Q] Nfc turn on Bluetooth when sharing?

well when i sharing a video or pic via nfc i see bluetooth icon appear and when check in notification bar is activate, in my mom phone galaxy s2 t989 appear too but turn off when sharing process finish...but in my s3 dont turn off automatically...so is normal bluetooth turn on when sharing via nfc?

Same happens with me
Sent from my SGH-T999 using xda premium

serio22 said:
Same happens with me
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I noticed this happens when two different versions of Android are connecting - AOSP to TouchWiz for example. I'll assume you're running a variation of AOSP and your mother is running factory TouchWiz? Go back to TouchWiz and try again, it won't turn on your bluetooth.
Now, no, I have no idea still why it turns on bluetooth instead of using NFC. It would be interesting to put the different version of Android together to see how each interacts with one another - AOSP, Sense, TouchWiz, Optimus, Experia, Motoblur, etc and see what happens.

Don_Perrignon said:
I noticed this happens when two different versions of Android are connecting - AOSP to TouchWiz for example. I'll assume you're running a variation of AOSP and your mother is running factory TouchWiz? Go back to TouchWiz and try again, it won't turn on your bluetooth.
Now, no, I have no idea still why it turns on bluetooth instead of using NFC. It would be interesting to put the different version of Android together to see how each interacts with one another - AOSP, Sense, TouchWiz, Optimus, Experia, Motoblur, etc and see what happens.
Click to expand...
Click to collapse
Never done it with aosp, only with touchwiz to touchwiz, and to a razr m.. its really not a big deal to me but I was just reporting
Sent from my SGH-T999 using xda premium

serio22 said:
Never done it with aosp, only with touchwiz to touchwiz, and to a razr m.. its really not a big deal to me but I was just reporting
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Hmm. I know when two S3s do it, Bluetooth doesn't turn on. So, then I guess the Note and Galaxy have slightly different versions of TouchWiz. I guess, I don't know.
Sent from my Galaxy Nexus using xda premium

Don_Perrignon said:
I noticed this happens when two different versions of Android are connecting - AOSP to TouchWiz for example. I'll assume you're running a variation of AOSP and your mother is running factory TouchWiz? Go back to TouchWiz and try again, it won't turn on your bluetooth.
Now, no, I have no idea still why it turns on bluetooth instead of using NFC. It would be interesting to put the different version of Android together to see how each interacts with one another - AOSP, Sense, TouchWiz, Optimus, Experia, Motoblur, etc and see what happens.
Click to expand...
Click to collapse
both run stocks rom...not root or custom recovery, my s3 run jelly 4.1.1 and the s2 run 4.1.2 official versions

santana_pr said:
both run stocks rom...not root or custom recovery, my s3 run jelly 4.1.1 and the s2 run 4.1.2 official versions
Click to expand...
Click to collapse
Then still, it must be there versions of TouchWiz. Two S3 will not turn on bluetooth.

Two s3's sharing will initiate the connection via nfc and will complete the transfer via WiFi direct (better transfer bandwidth and range so the devices don't have to remain touching). Dissimilar devices must use bluetooth when WiFi direct is unavailable.
Sent from my SGH-T999

yes i can confirn that...few moments ago do this with 2 galaxy S3 and dont activate bluetooth...test with other phones like S2 or Note 2 turn on bluetooth...so think this issue is resolved...thanks for your tips

Bluetooth switches ON during NFC transfer
I tried transferring media between Sony Xperia M and Sony Xperia L. The transfer takes place via bluetooth and not through NFC. The android versions are same on both the phones. Why does this still occur?

santana_pr said:
well when i sharing a video or pic via nfc i see bluetooth icon appear and when check in notification bar is activate, in my mom phone galaxy s2 t989 appear too but turn off when sharing process finish...but in my s3 dont turn off automatically...so is normal bluetooth turn on when sharing via nfc?
Click to expand...
Click to collapse
Do Note, given the same Antenna for NFC and Bloetooth, the same undelying APK controls both. So Android Beam may activate both. Perfectly normal.
ashrith.athreya said:
I tried transferring media between Sony Xperia M and Sony Xperia L. The transfer takes place via bluetooth and not through NFC. The android versions are same on both the phones. Why does this still occur?
Click to expand...
Click to collapse
Sony's implementation of NFC has been traditionally flaky. Plus see what I responded above.

that happens to both of my s3s. just checked.

m0nke10fdajung1e said:
that happens to both of my s3s. just checked.
Click to expand...
Click to collapse
Depends on Rom and Kernel. Possibly the code activated the icon. As I said earlier, the Antenna is the same.

Hmm. Same thing happens on my s3 but in a different situation. When I open bluetooth to transfer files and finished transferring, the nfc automatically turns on. I notice this prob after the update. Is there any software or hardware issue on my phone.. thanks

[Q] Fitbit Flex, BT4 & Custom Roms

Hi,
I've been running jelly bam lately because of the PA features (specifically per app DPI), but I recently purchased a Fitbit Flex and couldn't get it to work. I contacted their support and they just told me they don't support custom roms.. so I tried to restore my stock ATT/Samsung rom which is just version 4.1.1. The Fitbit Flex software installs and actually has the refresh button now but my phone doesn't seem to see my Flex when bluetooth is on. I think I need an update before I will be able to use the stock rom and I'm not sure how to do the updates with TWRP installed, I tried but it keeps rebooting into recovery. Anyway, I'd prefer not using the stock rom, specifically I would prefer a custom rom with PA features. I've just tried PAC-Man 4.3 nightly from last night (pac_t0lte-nightly-20130823.zip), and while my phone's bluetooth does see the device now, the Fitbit app doesn't give me the options like it did with my stock rom. Has anyone gotten the bluetooth and their Fitbit Flex to work with a custom rom with PA features?
Thanks!

If I recall, on a S3 and using a Fitbit One, you won't see the Fitbit except inside the app. There is a "devices" section in the app which lets you check the sync box. If you don't see that then the phone isn't seeing the Fitbit. Stock rom on the S3 works fine. Any custom rom will show you stats pulled from the web but not allow you to sync from the phone. I believe their app is the problem and not necessarily the phone or rom. Anyway, I've learned to live without syncing from the phone since stock firmware just isn't for me.

lensgrabber said:
If I recall, on a S3 and using a Fitbit One, you won't see the Fitbit except inside the app. There is a "devices" section in the app which lets you check the sync box. If you don't see that then the phone isn't seeing the Fitbit. Stock rom on the S3 works fine. Any custom rom will show you stats pulled from the web but not allow you to sync from the phone. I believe their app is the problem and not necessarily the phone or rom. Anyway, I've learned to live without syncing from the phone since stock firmware just isn't for me.
Click to expand...
Click to collapse
This is all exactly the same on my Note 2, but even my stock doesn't rom work. Like I said, possibly due to the old version 4.1.1. Under the stock rom the app shows all the additional options like you mention, but my phone's bluetooth never sees the Flex. I wonder what the Fitbit app uses to determine whether to show the additional options or not. I included screenshots to my "about device". I noticed that my model number was different with the new rom and thought maybe that might have something to do with it because clearly it's not (or not just) the android version.

Have you tried a stock 4.1.2 build ??
UCAMA4
It's a good option..and worth a try....g
Sent from my SAMSUNG-SGH-I317 using XDA Premium HD app

chellexor said:
Hi,
I've been running jelly bam lately because of the PA features (specifically per app DPI), but I recently purchased a Fitbit Flex and couldn't get it to work. I contacted their support and they just told me they don't support custom roms.. so I tried to restore my stock ATT/Samsung rom which is just version 4.1.1. The Fitbit Flex software installs and actually has the refresh button now but my phone doesn't seem to see my Flex when bluetooth is on. I think I need an update before I will be able to use the stock rom and I'm not sure how to do the updates with TWRP installed, I tried but it keeps rebooting into recovery. Anyway, I'd prefer not using the stock rom, specifically I would prefer a custom rom with PA features. I've just tried PAC-Man 4.3 nightly from last night (pac_t0lte-nightly-20130823.zip), and while my phone's bluetooth does see the device now, the Fitbit app doesn't give me the options like it did with my stock rom. Has anyone gotten the bluetooth and their Fitbit Flex to work with a custom rom with PA features?
Thanks!
Click to expand...
Click to collapse
lensgrabber said:
If I recall, on a S3 and using a Fitbit One, you won't see the Fitbit except inside the app. There is a "devices" section in the app which lets you check the sync box. If you don't see that then the phone isn't seeing the Fitbit. Stock rom on the S3 works fine. Any custom rom will show you stats pulled from the web but not allow you to sync from the phone. I believe their app is the problem and not necessarily the phone or rom. Anyway, I've learned to live without syncing from the phone since stock firmware just isn't for me.
Click to expand...
Click to collapse
chellexor said:
This is all exactly the same on my Note 2, but even my stock doesn't rom work. Like I said, possibly due to the old version 4.1.1. Under the stock rom the app shows all the additional options like you mention, but my phone's bluetooth never sees the Flex. I wonder what the Fitbit app uses to determine whether to show the additional options or not. I included screenshots to my "about device". I noticed that my model number was different with the new rom and thought maybe that might have something to do with it because clearly it's not (or not just) the android version.
Click to expand...
Click to collapse
gregsarg said:
Have you tried a stock 4.1.2 build ??
UCAMA4
It's a good option..and worth a try....g
Sent from my SAMSUNG-SGH-I317 using XDA Premium HD app
Click to expand...
Click to collapse
Can someone link a stock rom for me? I have the GPe of the GS4. i9505G, and I have AT&T. Started out with SGH-i337

Fitbit Sync
I got FitBit to Sync finally with my custom rom.
I used the Build Prop Editor from JRummy. play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor
change the ro.product.model=GT-I9505G
and ro.product.manufacturer=samsung
and save those settings, reboot, and now Fitbit will try to sync now. YAY! :victory:
chellexor said:
Hi,
I've been running jelly bam lately because of the PA features (specifically per app DPI), but I recently purchased a Fitbit Flex and couldn't get it to work. I contacted their support and they just told me they don't support custom roms.. so I tried to restore my stock ATT/Samsung rom which is just version 4.1.1. The Fitbit Flex software installs and actually has the refresh button now but my phone doesn't seem to see my Flex when bluetooth is on. I think I need an update before I will be able to use the stock rom and I'm not sure how to do the updates with TWRP installed, I tried but it keeps rebooting into recovery. Anyway, I'd prefer not using the stock rom, specifically I would prefer a custom rom with PA features. I've just tried PAC-Man 4.3 nightly from last night (pac_t0lte-nightly-20130823.zip), and while my phone's bluetooth does see the device now, the Fitbit app doesn't give me the options like it did with my stock rom. Has anyone gotten the bluetooth and their Fitbit Flex to work with a custom rom with PA features?
Thanks!
Click to expand...
Click to collapse

cklaus1 said:
I got FitBit to Sync finally with my custom rom.
I used the Build Prop Editor from JRummy. play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor
change the ro.product.model=GT-I9505G
and ro.product.manufacturer=samsung
and save those settings, reboot, and now Fitbit will try to sync now. YAY! :victory:
Click to expand...
Click to collapse
I followed those tips and got it working on my Galaxy S3 AT&T running Carbon ROM...
but now the Dilbert app is telling me that my device is not supported... which is weird because it's just an app to view the daily comic strip.

zadigre said:
I followed those tips and got it working on my Galaxy S3 AT&T running Carbon ROM...
but now the Dilbert app is telling me that my device is not supported... which is weird because it's just an app to view the daily comic strip.
Click to expand...
Click to collapse
Just one thing to try, my FitBit wouldn't initially synchronise with any of my devices (all custom ROM)...but I then tried removing the gel cover and plastic rear battery cover of the phone (an S3), held it very close to the FitBit and it then sync'ed fine!
It seems that this new low-power Bluetooth protocol is a little too low on the power element

Note 2 & Fitbit/Bluetooth Problems
I came here looking for answers/help with my bluetooth... but so far I haven't really been able to find anything that's actually helpful. I can share with everything what I've been able to find out, though.
I have a Galaxy Note 2 running stock on Android 4.4.2 and I have the Fitbit Flex. I used to sync without any problems but after my phone updated to 4.4.2 it no longer syncs. After researching for a few days... it seems the problem is with the Update itself... it reduces power or range of Bluetooth... that's why the Flex cannot sync to it. However, I have discovered an quick fix to that:
When syncing, just place your phone on top of your Flex band and it will sync up without any problems. This has become my temporary solution. Someone else suggest another quick fix would be to turn on Mobile Hotspot on your phone... that is suppose to increase the Bluetooth Power.
I also learned that Samsung won't update the Note 2 to 4.4.4, which would have fixed this problem.. but instead will Update the Note 2 to Lollipop... but that date is still unannounced.
If anyone has any ideas on how to really fix this problem... I'm all ears. The only solution I found was to open up the phone and do something to the bluetooth chip inside... but I forgot where I found that solution.

Oficial Update to KK 4.4

Hi, just to ask if somebody have information about note 2 update to KK 4.4, I read in this article and I think that Samsung is going to make an update to this version, what do you think???
http://bgr.com/2014/02/07/galaxy-s3-note-2-android-4-4-kitkat-update/
apologize if I broke any rules by the link, if so remove please.

potroveloz said:
Hi, just to ask if somebody have information about note 2 update to KK 4.4, I read in this article and I think that Samsung is going to make an update to this version, what do you think???
http://bgr.com/2014/02/07/galaxy-s3-note-2-android-4-4-kitkat-update/
apologize if I broke any rules by the link, if so remove please.
Click to expand...
Click to collapse
Per this article the updates are expected sometime in late March(end of Q1 2014).
Kitkat & touchwiz combination sounds good but again no idea how many new restrictions it will come with.
4.3 took too long but the wait was not worth it. I am happy with 4.3 on 4.1 bootloader.
I hope there isn't a requirement to update the bootloader.

ciphercodes said:
Per this article the updates are expected sometime in late March(end of Q1 2014).
Kitkat & touchwiz combination sounds good but again no idea how many new restrictions it will come with.
4.3 took too long but the wait was not worth it. I am happy with 4.3 on 4.1 bootloader.
I hope there isn't a requirement to update the bootloader.
Click to expand...
Click to collapse
Well, apparently it's official....
http://www.samsungmobileuspress.com...firms-KitKat-for-U.S.-Smartphones-and-Tablets

After two months after the S5 comes out lol
Sent from my SGH-T889 using XDA Premium 4 mobile app

Has anyone received this update yet? Just curious.

Ask T-mobile
Wink2tall2 said:
Has anyone received this update yet? Just curious.
Click to expand...
Click to collapse
Do not hold your breath. Before we get even close to thinking we will get this. You will first see Samsung update the note2 Unlocked and international Versions.Then Sprint or at&t Might then consider to update the phone (maybe). If that happens then MAYBE AND only if and a very doubtful maybe. Will T- Mobile decided to send us the update..
There are way more hands in the pot then just want samsung says. The press release says Carrier dependant...
Carrier is the word there . So ask T- Mobile on there plans

erica_renee said:
Do not hold your breath. Before we get even close to thinking we will get this. You will first see Samsung update the note2 Unlocked and international Versions.Then Sprint or at&t Might then consider to update the phone (maybe). If that happens then MAYBE AND only if and a very doubtful maybe. Will T- Mobile decided to send us the update..
There are way more hands in the pot then just want samsung says. The press release says Carrier dependant...
Carrier is the word there . So ask T- Mobile on there plans
Click to expand...
Click to collapse
DavidCDM said:
try to update if still not updated
Click to expand...
Click to collapse
I will try soon and post with result... although after some research I doubt I will be receiving any updates for at least a month or so.

Wink2tall2 said:
I will try soon and post with result... although after some research I doubt I will be receiving any updates for at least a month or so.
Click to expand...
Click to collapse
I have a Note 2 t-mobile as well.. Sorry i never disclosed this. and NO There is no update for it. my note 2 is on 4.3 factory

I've got the AT&T model (SGH-I317) of the Note II running 4.1.2. (I317UCALK7), but I'm on T-Mobile now.
I received 4.1.2 OTA after rooting.
I have been unable to get any updates past 4.1.2, even when manually checking.
A few days ago I checked again and instead of telling me there was an error when checking for updates, it told me there was an update (around 185.75 MB). It downloaded, but failed to install.
I'd really like to be able to get the official/TouchWiz 4.4 build installed.
When 4.4 does hit, should I be trying to get the T-Mobile version or the AT&T version? Or does it not matter?
It looks like I won't be able to get the update OTA since I can't get any updates OTA now and I'm stuck on 4.1.2, but surely there will be a dump I can grab online and load myself, right?

sexconker said:
I've got the AT&T model (SGH-I317) of the Note II running 4.1.2. (I317UCALK7), but I'm on T-Mobile now.
I received 4.1.2 OTA after rooting.
I have been unable to get any updates past 4.1.2, even when manually checking.
A few days ago I checked again and instead of telling me there was an error when checking for updates, it told me there was an update (around 185.75 MB). It downloaded, but failed to install.
I'd really like to be able to get the official/TouchWiz 4.4 build installed.
When 4.4 does hit, should I be trying to get the T-Mobile version or the AT&T version? Or does it not matter?
It looks like I won't be able to get the update OTA since I can't get any updates OTA now and I'm stuck on 4.1.2, but surely there will be a dump I can grab online and load myself, right?
Click to expand...
Click to collapse
Odin your stock un rooted Rom, then check for ota update. Don't forget to triangle away
Sent from my GT-N7105 using XDA Premium 4 mobile app

So any idea if a TouchWiz ROM with WiFi calling ONLY happen if T-Mobile releases an official ROM first, or is there a way for devs to make a 4.4.2 with WiFi calling based on the component present in the 4.3 build?
T-Mobile could win me for life by doing two things:
1) Improve rural reception (I know they're working on it with all that new 700Mhz spectrum)
2) Release WiFi calling as an app for T-Mobile customers so I could be free to run a non-TW ROM

spg900ny said:
So any idea if a TouchWiz ROM with WiFi calling ONLY happen if T-Mobile releases an official ROM first, or is there a way for devs to make a 4.4.2 with WiFi calling based on the component present in the 4.3 build?
T-Mobile could win me for life by doing two things:
1) Improve rural reception (I know they're working on it with all that new 700Mhz spectrum)
2) Release WiFi calling as an app for T-Mobile customers so I could be free to run a non-TW ROM
Click to expand...
Click to collapse
Why not use Google voice or an alternative app for WiFi calling?

OmegaBlaze said:
Why not use Google voice or an alternative app for WiFi calling?
Click to expand...
Click to collapse
Mostly because I'm not interested in changing my phone number (WiFi calling I only really need for incoming calls), and I want to get SMS texts to my current phone #.
Really wish T-Mobile would just release a WiFi calling app for its customers so that I could go AOSP. I am not liking TouchWiz at all after being on an original Droid w/Bugless Beast and then Nexus devices.

spg900ny said:
Mostly because I'm not interested in changing my phone number (WiFi calling I only really need for incoming calls), and I want to get SMS texts to my current phone #.
Really wish T-Mobile would just release a WiFi calling app for its customers so that I could go AOSP. I am not liking TouchWiz at all after being on an original Droid w/Bugless Beast and then Nexus devices.
Click to expand...
Click to collapse
You don't have to. You can choose to have all of your calls answered by Google Voice, or by your actual number.
I think you should give it a go..:good:

OmegaBlaze said:
You don't have to. You can choose to have all of your calls answered by Google Voice, or by your actual number.
I think you should give it a go..:good:
Click to expand...
Click to collapse
I have Google Voice for my voicemail, but obviously if I'm in the office where I have no signal, I'm not going to get the call because it goes right to Google Voice voicemail if I don't have a signal. Also, I need my regular number to accept SMS. Am I missing something?