Related
Hi I am currently a T - Mobile customer and when I originally bought my Samsung Galaxy S2 with the company, I thought I could take advantage of using both the T - Mobile network and 2G services of the T - Mobile Orange Network.
However after successfully using it for the first 2 weeks, after my KE7 firmware update, I have an unbranded phone, it did not connect to the network anymore, stating, even if I manually select T - Mobile Orange in GSM mode only, Cannot registor with network, Unable to connect, then it states it is registered and yet I have emergency calls only stated and not either T - Mobile or even T - Mobile Orange. Then it will not connect to either network manually until I restart the phone.
I have since flashed my phone with various other firmwares, am currently on cognition s2 1.13, it's a great Rom, and still the same thing occurs.
I have contacted T - Mobile, they can't fix it, I have took the phone to a Samsung Repairer and they couldn't see anything wrong, stating it was a fault with Orange, as the guy in the shop's T - Mobile branded Galaxy s2 did the same.
Anyone solved the mystery, or is able to explain the issue to me?
It's doing my nut in, I have had phones like these for years, flashed them and enjoyed them, and usually work things out for myself, my last phone was an Samsung I8910, which was great with custom firmware support and I must say the Galaxy s2 is by far my favourite ever phone, but even my Samsung Omnia I8910 works properly on T - Mobile and Orange, and the latest and greatest phone won't!!
Have you tried flashing a different modem? Seeing as the cognition rom is based on I9100XXKG1, I know of a couple of forum members that have had trouble with the KG1 modem, and had to revert to the KF2 modem.
Worth a try? It won't wipe you phone of anything daft either.
List of official modems: http://forum.xda-developers.com/showthread.php?t=1131950
Before you do anything, can you dial*#1234# and just check what phone software is installed?
Thanks for the option Unfortunately I have tried the KE2, KE7, KF2 and KG1 Modems now, none of them have worked. It is really bizaar as the bloody thing works really well on T - Mobile, when there is coverage, plus the 3 and H is great speeds when they are in coverage, it just won't switch to Orange
mattisfaction said:
Thanks for the option Unfortunately I have tried the KE2, KE7, KF2 and KG1 Modems now, none of them have worked. It is really bizaar as the bloody thing works really well on T - Mobile, when there is coverage, plus the 3 and H is great speeds when they are in coverage, it just won't switch to Orange
Click to expand...
Click to collapse
one moment, I'm on t-mobile aswell.
text YES to 2121.
Homer moment: Doh, you cant text can you?
Just for reference, I'm with Orange and in my network list I have both "Orange" and "Orange and T-Mobile". I can connect to the Orange one fine, but not to the other one. It does switch to T-Mobile sometimes though. I've seen it do it.
Hi again, I have text yes to 2121, and it was working on my phone before. So yours has no issues then?
mattisfaction said:
Hi again, I have text yes to 2121, and it was working on my phone before. So yours has no issues then?
Click to expand...
Click to collapse
No, but I remember I used to have an everythingeverywhere app in data/private, which is no longer there.
I just texted yes to 2121 and now it lets me register on orange aswell as t-mobile.
stoney73 said:
No, but I remember I used to have an everythingeverywhere app in data/private, which is no longer there.
I just texted yes to 2121 and now it lets me register on orange aswell as t-mobile.
Click to expand...
Click to collapse
I just looked in data/private and do not have an everythingeverywhere app, plus I have just again text 2121 and still cannot use the orange network
Cheers for your advice though mate
johncmolyneux said:
Just for reference, I'm with Orange and in my network list I have both "Orange" and "Orange and T-Mobile". I can connect to the Orange one fine, but not to the other one. It does switch to T-Mobile sometimes though. I've seen it do it.
Click to expand...
Click to collapse
Cheers for the information
Unfortunately if I let mine automatically switch network, it switches to emergency calls only if I am out of a t mobile network range, not orange, and it used to switch to orange no problem
Then when it is in emergency calls only, I have to turn it on and off to get it to work at all, as it will not register back to T mobile
My last attempt......when you go into wireless/mobile network settings, is data roaming ticked?
stoney73 said:
My last attempt......when you go into wireless/mobile network settings, is data roaming ticked?
Click to expand...
Click to collapse
Yes it is, cheers for all your help. It's very frustrating and I can't fathom it out, so cheers for trying yourself
You don't need data roaming ticked in order to use Orange. T-mobile and Orange are both considered 'home' networks.
I'm on T-Mobile without data roaming ticked and it switches automatically to Orange without any issues. Might be worth phoning t-mobile up and seeing if there's some sort of issue with your account.
I installed Lite'ning Rom and found that I couldn't connect to Orange on my unlocked tmobile sim. Turned out that I had the "com.orange.authentication.simcard.permission" apk missing.
Downloaded it here:- http://www.contentsd.nl/apk/SimServicePermission.apk
and installed it with titanium and registered ok on orange.
Hope this helps.
dirobeshploppy said:
I installed Lite'ning Rom and found that I couldn't connect to Orange on my unlocked tmobile sim. Turned out that I had the "com.orange.authentication.simcard.permission" apk missing.
Downloaded it here:- http://www.contentsd.nl/apk/SimServicePermission.apk
and installed it with titanium and registered ok on orange.
Hope this helps.
Click to expand...
Click to collapse
I've just checked my simfree phone and it has the above apk installed. How on earth did you figure out you were missing this apk??
Joey2o11 said:
I've just checked my simfree phone and it has the above apk installed. How on earth did you figure out you were missing this apk??
Click to expand...
Click to collapse
Was browsing the list of stock apk's here:-
https://spreadsheets.google.com/spreadsheet/pub?hl=en_US&hl=en_US&key=0Ag43oj7rLQP4dENZcmhGN0ZUa3pHSENVeXlqUm5vV0E&single=true&gid=0&output=html
and noticed the "com.orange.authentication.simcard.permission" reference and when I checked via titanium it wasn't installed so I tried it and it sorted out my problem.
Hiya guys. Sorry to jump on this thread but I am having the same issue as OP. I'd just like to give you an update on what I know so far. It is a nightmare trying to speak to someone at T-Mobile who actually knows whats going on, but I was persistent and got through to an engineer who said that they are having transmitter problems in east anglia and surrounding areas...not sure if you are in that area or not. Unfortunately all the engineer said is that they are working hard to a. figure out what the problem is ang b. fix it! He also could not give me an ETA and said that the only way to get back onto the network is to reboot the phone a couple of times. Not ideal, but I though it was something to do with the VillainRom that I flashed...so here's stupid me flashing stock, bricking/unbricking the phone etc etc only to find out later that its not the phone...on the plus side I have amazing battery life now haha who would have thought ey!
Anyways, hope this information is useful to you all.
Steph
It is not a ROM issue - it is a T-Mobile/Orange fault
stephan.pieri said:
... I was persistent and got through to an engineer who said that they are having transmitter problems in east anglia and surrounding areas...not sure if you are in that area or not. Unfortunately all the engineer said is that they are working hard to a. figure out what the problem is ang b. fix it! He also could not give me an ETA and said that the only way to get back onto the network is to reboot the phone a couple of times. Not ideal, but I though it was something to do with the VillainRom that I flashed...so here's stupid me flashing stock, bricking/unbricking the phone etc etc only to find out later that its not the phone...on the plus side I have amazing battery life now haha who would have thought ey!
Anyways, hope this information is useful to you all.
Steph
Click to expand...
Click to collapse
Absolutely right Steph, it is not ROM related.
T-Mobile have acknowledged that there is a problem with registering T-Mobile customers on T'Orange cell towers.
I've been having this issue for a couple of weeks now (also in East Anglia), and after a lot of perseverance I got transferred to Level 2 support (Technical Support - not Customer Support) last Monday. They said there was a 'rectifier problem' on a mast in Henny Street, near Sudbury, Suffolk at the end of June and it has had a knock-on effect on other masts in the area. It was/is a level 2 priority for fix.
I wasn't happy with that explanation as it happens all over Suffolk!
Still with the issue on Thursday, I called them again and got straight through to Level 2 as they had marked my account as an on-going problem which Customer Support (in the Philippines) couldn't handle.
While explaining in detail the 'Your SIM does not allow you to connect to this network' problem the Guy I was talking to received an internal notification that they were aware of issues registering on T'Orange cells, that they'd known about it for 72 hours, have no idea what is causing it, and no eta to fix.
I've been using a forced connection to T'Orange for the last couple of days (poor T-Mo signal in house which always caused it to hunt for T'Orange anyway). Downside of course is that it won't get a 3G signal when forced into T'Orange mode.
Still happening today so need to give them another prod...
Oh, and I found this thread searching for answers - I don't have a Galaxy S, I have a Desire. Further proof that it isn't ROM related.
I'll update when I find out more from them.
Aaron
Just spoken to them again, problem is still on-going, they are still investigating and looking for more samples of the problem to try and isolate the issue. In light of that I would suggest anyone else having this to phone them and ask for Technical Support and register the fault - the more samples they have, the better chance of getting it resolved.
In other words, they still don't know what's causing it or when they'll fix it.
Alright so ill start this of by saying, Picked up my note today and loving it so far. Got it rooted thanks to Da G and getting ready to get into roms.
Anyway im making this thread to see if anyone else has tried anything out on the non-AT&T notes(i.e I717M and what not). So far from what i have read people are developing mostly for the AT&T model and saying its not for bell rogers or telus. Now I have been in the samsung world for a while and when it comes to my galaxy there was always ways around this.
For instance most of my ROMs were made for the international version not my bell version. But as long as I kept a copy of the bell modem on my phone i could just flash that and the ROM worked great. So does anyone have a copy of the bell telus or rogers modem for the note? or know if there all the same?
Another example in the galaxy s world was the captivate(Same soft keys as our phones). A person with a captivate could flash an international ROM as long they made a soft key fix when they developed the ROM.
One of the main reasons I ask all of this is because i see so many N7000 ROMs up and running and am wondering what will and wont work.
Look forward to hearing from you all
adamtrace said:
For instance most of my ROMs were made for the international version not my bell version. But as long as I kept a copy of the bell modem on my phone i could just flash that and the ROM worked great. So does anyone have a copy of the bell telus or rogers modem for the note? or know if there all the same?
Click to expand...
Click to collapse
you can get all the carrier radio/modem, and even the kernel from carrier here:
http://forum.xda-developers.com/showthread.php?t=1506212
---------- Post added at 02:08 AM ---------- Previous post was at 02:05 AM ----------
and here: http://forum.xda-developers.com/showthread.php?t=1630843
---------- Post added at 02:10 AM ---------- Previous post was at 02:08 AM ----------
sorry, I also forgot this kernel: http://forum.xda-developers.com/showthread.php?t=1589389
Bell note here. Been. The at & t roms with no problem.
The only issue that I have is the Yellow Pages crap that appears in my contact list as well as at& t bloat depending on the rom. Easy enough to deal with though.
Aside from that, it's been perfect.
Currently on Team Perfection 4.0.4.
Sent from my SAMSUNG-SGH-I717 using xda premium
I forgot to add that I haven't had any issues with data speeds at all.
Also, Don't venture into the N7000 roms because they will not work.
Sent from my SAMSUNG-SGH-I717 using xda premium
The N7000 ROMs can hard brick your phone since the hardware if the two models are completely different. AS Far as ROMs go, most are based off the AT&T software simply because that's the only ICS leak we have available. But you can use any ROM for the i717 on your Bell Note. I have a Bell Note and flashed almost every ROM and never ran into any problems. Also, Ruth the help ofa lot of people on this sure, I've made stock images of the Bell, Telus, and Rogers Notes so we can always go back. Best if luck and don't hesitate to ask anything.
Thanks for the info, I get mine today and was wondering the same thing.
Yesterday I flashed my Rogers Branded Galaxy i717 with Bell Rom and Kernel and have not 1 issue. I chose to flash the rogers i717 with Bell because I use bell mobiletv and this was the only way to get this particular app to work. Again not 1 issue with data or anything else.
No Rooted device either. Just flashed using ODIN.
I'm currently running the UCLE2 Rom on my Rogers i717. I've noticed that I am not getting LTE where I should be. And GPS connectivity is shoddy at best.
I have a second i717 which is stock that is with me to compare (family member).
I am going to flash the Rogers modem to hopefully correct atleast the LTE issue. Anyone know if this would improve my GPS connectivity as well?
For a number of years I have been buying Canadian phones to use on ATT. Canadain ROMs have less restrictions than ATT. For instance tethering and NFC are not locked. Also after rooting my Roger's Note it took under a minute to remove the Rogers branding. (all except splash screen) I was left with a fully optioned unbranded ROM.
I did want to try the stock UCLE2 ROM out of curiosity but I thought it would not install because my phone was not an ATT I717. How did you install it eugenekim618? Personally I would rather wait for the Rogers ICS version. Keep checking everyday to see if it is available.
I have tried quite of a few of the ROMS on here with my Bell i717M, no problems at all so far, other than the "android.phone has stopped working" at startup, I don't know the cause but it only happens at boot.
DO NOT use N7000 roms! But all of the AT&T stuff has worked great for me.
Agoattamer said:
For a number of years I have been buying Canadian phones to use on ATT. Canadain ROMs have less restrictions than ATT. For instance tethering and NFC are not locked. Also after rooting my Roger's Note it took under a minute to remove the Rogers branding. (all except splash screen) I was left with a fully optioned unbranded ROM.
I did want to try the stock UCLE2 ROM out of curiosity but I thought it would not install because my phone was not an ATT I717. How did you install it eugenekim618? Personally I would rather wait for the Rogers ICS version. Keep checking everyday to see if it is available.
Click to expand...
Click to collapse
I followed the posts in the Dev section to Root the phone.
Then installed CWM.
The picked a ROM I thought was good and followed the instructions in it's respective post to install.
I've done a lot of ROM installs for the Dell Streak I used to have and for a Sony Xperia X10.
So I am not totally unfamiliar with the process. Just a matter of getting used to the delivery method for each manufacturer. And then, dealing with the quirks of a ROM that is not 100% for your carrier. Goes with the territory, right?
I tried to read all the posts in a given thread as much as I can.
So you are saying you didn't install the one click odin stock UCLE2 ROM?
Agoattamer said:
So you are saying you didn't install the one click odin stock UCLE2 ROM?
Click to expand...
Click to collapse
No, that doesn't work for non AT&T phones I believe. I tried it, and ODIN recognized the COM, but failed to install. From my readings, can't do the one click install on Rogers since it's not a Rogers ROM.
all custom roms should work no problem, ive flashed tons on my unlocked bell note.
its the stock odin files when you want to make sure you get the proper device.
Hey guys Ive flashed pretty much all the roms I can and some I cant lol. So far my experiances have encountered a few setbacks but nothing substantial and allot if not most of the bugs and glitchs occurring in the first & second gen of roms have been fixed or patched.
As far as roms go as was already mentioned as long as you stay away from n7000 model roms and stick to i727 youll be ok. With at&t roms I always seem to have signal and gps issues. Generally tho I find my signal problem will clear itself up on its own and I believe is actually just just caused by the fresh software 'settling in', even though my signal appears low or fluctuating speed testing always shows Im getting peak d/l & u/l speeds. If the signal doesnt seem to improve flashing the Bell stock modem via cwm always does the trick. Gps usually works great, very fast & accurate, when Im having location issues I use the 'faster fix' app from the market, I dont know about anyone elses experiance but allot of the times theres a problem the gps server isnt set to the normal 'north america pool' but servers Ive never seen before or set to an 'international pool'.
All in all besides signal headaches the only other recurring problems are the inherent and unpredictable random force closing of system apps. It can be pretty random but I find a few constant trouble makers to be at&t software update, android phone. At&t update can be disabled easily under applications in the main settings or I was able to actually remove it using 'rom toolbox's app manager but strangely not with root toolboxs remove system apps. For pretty much all other f/c problems the remedy is a running of 'fix permissions', there are a bunch of ways/apps to do it and Ive found using 'rom manager' works the best meanwhile rebooting into recovery and fixing permissions from there will actually cause more problems.
Ok so those are the most recurring and annoying issues Ive had to name a few but the list is too big to write merely because Ive tried just about every rom right from the sketchiest unstable first releases and everything in between lol so feel free to drop me line if your stuck on a problem cause I might be able to help.
But before I end this novel here lol I just flashed the new 'OnlyOne Beta2' rom from the development section and it runs great. The rom is super stable, very fast and features both fully functional S Voice app and fully functional S Notes app. If you havnt tried S Notes yet its awesome the new functions and abilities totally blew me away so I highly recommend you give this rom a try!
eugenekim618 said:
I'm currently running the UCLE2 Rom on my Rogers i717. I've noticed that I am not getting LTE where I should be. And GPS connectivity is shoddy at best.
I have a second i717 which is stock that is with me to compare (family member).
I am going to flash the Rogers modem to hopefully correct atleast the LTE issue. Anyone know if this would improve my GPS connectivity as well?
Click to expand...
Click to collapse
If you had LTE before and lost it through flashing a custom ROM or whatever then try changing your APN to your Carrier LTE network. If you never had LTE when you bought your phone, probably the seller gave you a wrong sim. tell her to give you a 403 LTE capable sim, the 401 is only 4G.
andronikal659 said:
If you had LTE before and lost it through flashing a custom ROM or whatever then try changing your APN to your Carrier LTE network. If you never had LTE when you bought your phone, probably the seller gave you a wrong sim. tell her to give you a 403 LTE capable sim, the 401 is only 4G.
Click to expand...
Click to collapse
Thanks for the tip. But I got everything running again. I did have LTE to start, and have a LTE sim card. The *#2263* certainly helped. And Flapjaxxx's GPS tools in his ROM helped me get the GPS back up to par.
eugenekim618 said:
Thanks for the tip. But I got everything running again. I did have LTE to start, and have a LTE sim card. The *#2263* certainly helped. And Flapjaxxx's GPS tools in his ROM helped me get the GPS back up to par.
Click to expand...
Click to collapse
ok now I just lost my LTE after flashing new ROM from Seraphim Stratosphere. How did you get it back. I factory wipe everything and flash Rogers modem and it doesn't work. How did you manage to get LTE back? btw I have a Canadian Note with Rogers. the Saurom ROM was canadian and I had LTE too.
andronikal659 said:
ok now I just lost my LTE after flashing new ROM from Seraphim Stratosphere. How did you get it back. I factory wipe everything and flash Rogers modem and it doesn't work. How did you manage to get LTE back? btw I have a Canadian Note with Rogers. the Saurom ROM was canadian and I had LTE too.
Click to expand...
Click to collapse
Try *#2263#
Then force select LTE, and select ALL. That should force the LTE connection. So watch the connection bars. You should see a loss of connection, then reconnect on LTE. Once that is established, do the code again, and just select automatic.
eugenekim618 said:
Try *#2263#
Then force select LTE, and select ALL. That should force the LTE connection. So watch the connection bars. You should see a loss of connection, then reconnect on LTE. Once that is established, do the code again, and just select automatic.
Click to expand...
Click to collapse
When I try dialing it, it says error can't find USSP or something like that... What does this mean?
Just to be clear that im doing the right thing. I go to the dialer and punch the code *#2263#. How do I "force select LTE"? will something popup for me to select it or should I go to settings/ wireless and networks... I don't have those options in "wireless settings", I only have APN settings...
Hello All,
I have been looking around and seeing if anyone else is experiencing the same issue I have. But I have not had much luck. I have seen similar cases, but for whatever reason, some of the workarounds found that worked for others have not been successful for myself, or are temporary.
For the past three months, I have been experiencing an off and on issue where I am unable to receive texts, but I am able to send out text. And it is something that I would not realize until people actually notify me, or it is awkwardly silent on the "texting front", which makes me second guess myself. Almost every other week or two weeks this has occurred. At the time, I am running Darky's 8.8 [4.1.2] ROM for the i9300. I have tried rebooting, taking out the SIM, re-flashing Darky and re-flashing Stock (full wipe, etc), and replacing my old SIM with a new one. None have been successful thus far. The only success I have found is that inserting my SIM in a different phones allows the text to flow through almost immediately. I would then place the SIM back in the i9300 and any new texts sent I would receive immediately. After a week or two, it randomly just stops receiving text again, and the cycle continues.
I was wondering if whether this may be a bug with the Android OS itself? I have seen a few posts in regards to SMS being handled by Jelly Bean, but I am not 100% sure if my issue would fall in the same boat. Or if it is possibly faulty hardware? Or some kind of network issue. My network is AT&T, but I'm ruling out a network issue since I am able to receive text almost instantaneously on other phones.
Any information, advice, or help would be greatly appreciated.
Its not a bug .
Usual reason is wrong MMS message centre settings or network settings .
jje
JJEgan said:
Its not a bug .
Usual reason is wrong MMS message centre settings or network settings .
jje
Click to expand...
Click to collapse
I've verified that the MMS APNs and SMS settings are correctly configured to AT&Ts network. If it were incorrect from the beginning, I would not get text messages (or MMS) at all. But in this case, it is intermittent and only resolved when I get to "unload" the text messages on to another device.
Same thing happens to me (why I had to use my upgrade to buy a phone from them -_-) I'm using a S2 for now... it sucks when you have been on the S3. Their excuse for not being able to help me was "Its an international phone, therefore may not work with our network." That's freaking BS. It worked for 6 months before this issue came up. New micro SIM card is the only temporary solution for now. When I have time. I'm going up there or calling help line. Gonna file a complaint and mention I might be leaving service with them or I can say legal action will be taken since they are denying me a service I'm paying for. They should start helping by them. I don't abuse their services. I don't tether. I don't cheat them in any way. Its retaarded.
b-eock said:
Same thing happens to me (why I had to use my upgrade to buy a phone from them -_-) I'm using a S2 for now... it sucks when you have been on the S3. Their excuse for not being able to help me was "Its an international phone, therefore may not work with our network." That's freaking BS. It worked for 6 months before this issue came up. New micro SIM card is the only temporary solution for now. When I have time. I'm going up there or calling help line. Gonna file a complaint and mention I might be leaving service with them or I can say legal action will be taken since they are denying me a service I'm paying for. They should start helping by them. I don't abuse their services. I don't tether. I don't cheat them in any way. Its retaarded.
Click to expand...
Click to collapse
Ahh! Thank you b-eock! I don't mean this in the wrong way, but I'm glad that I'm not the only who has experienced this. When this occurred to you, were you on some version of 4.1.2? From what I can remember, this issue never came up until I upgraded from 4.1.1 to 4.1.2. Just trying to find some kind of trend here...
I have had to call up AT&T a number of times regarding this issue. And each time they were of no help. Although they were able to confirm that everything on their end of setup correctly, I got the same BS that you got. And they even gave me the whole baloney that I should upgrade so that they can help assist me better and that since it is not their branded phone, it may not be fully compatible.
I really do not want to give up on this. And I definitely want to find a solution. So I am hoping there is a lucky one out there that has tried different ways of getting fixed. Whether that be trying a new ROM, or downgrading from Jelly Bean to ICS, etc.
Came up a few weeks after I upgraded to 4.1.2 but there isn't really a connection between that. It worked before. Its just random crap. And them telling us everything is good on their end, that's complete BS. They don't know what's going on behind their computer screen.
Same exact thing happens to me. It's ROM dependent i'm thinking. Samsung roms from other countries do it the most for me. Has done it on AT&T and AT&T with StraightTalk. Experiencing it on Purelok HD v3.1 right now. I love this rom but im probably going to go AOSP/AOKP as I don't experience it on those kind of roms.
Camera just isn't the same without the Samsung software to me.
Hey guys,
So I have a bit of a tricky question that I can't seem to find an answer for. My wife and I just move to Europe for work for 2 years. We had AT&T in the states, so my wife has an AT&T HTC One X+. We got our phones SIM unlocked before we left, and purchased French SIM cards that run on the Bouygues Telecom network. My phone (Lumia 925) can do wifi tethering no problem... My wife's on the other hand has issues. I keep getting the following error:
" There is a temporary network problem that prevents the enablement of the Mobile Hotspot function. Please retry later."
I have tried the following steps:
1. Rooting the phone.
2. Installing other hotspot apps (Both root and non-root)
3. Installed custom ROMs with hotfixes to remove AT&T data requirements.
I don't know if it's relevant, but when I do a reset on the phone, it doesn't automatically connect to Bouygues network for data. I have to manually add the APN every time. Once I do that, her mobile data works just fine, so I don't THINK that the APN is causing the problem...
Anyways, if anyone has an suggestions on how to fix this issue, I would be indebted to you... I've just never encountered this problem on any of my other Android devices and I have to believe that there is a simple solution to fix the problem that I've just not encountered. Thanks!!
I loved my international HOX, so when got dropped in water i said lets go for the ATT HOX+ that has LTE.
Big mistake! I have OP's same issue, im in spain and my provider is Movistar.
I bought it on e-Bay, configured all the APNs, I used settings from their webpage and also tried telephony.db values from an international rom, stock rom didn't tether.
Rooted stock (4.1.2 i think it was) still nothing.
Elegancia (4.2.2) ROM, still nothing.
Changed some stuff on the telephony.db, still nothing
Swapped the wifirouter.apk with the international wifirouter.apk, still nothing.
Nuked TetherGuard.apk, still nothing.
Installed Moto-X tether Xposed module, still nothing (probably cause it's for android 4.4).
I read that AOSP or Cyanogen ROMs don’t have this issue.
I also read that if you swap telephone.db from international version to USA version the phone goes into a reboot loop, [More Info].
I guess the solution lays in something similar to the Moto-X tether patch, but i don't really have the time to fork the project, and try to get my tethering working.
Hope someone can give us a hand, im sure there are at least 5 more people in this same situation.
Hello,
My Elderly grandad has just moved rural in the UK and needs to use wifi calling as there is no mobile signal, he has an old Samsung S6 which he uses which my brother bought off ebay.
The issues is the S6 is an AT&T version and for whatever reason the wifi calling setting will not turn on, on contacting Samsung they say this is likely due to the fact its an AT&T version of the phone and there is compatability issue. His carrier 3 ( the phone is unlocked) allows wifi calling so it's definitely a phone issue.
I wondered if I could flash a different firmware or such as it's a software issue and get it working?
Any help would be awesome, otherwise the phone is now useless.
Thanks!
Jonathan
jrid said:
Hello,
My Elderly grandad has just moved rural in the UK and needs to use wifi calling as there is no mobile signal, he has an old Samsung S6 which he uses which my brother bought off ebay.
The issues is the S6 is an AT&T version and for whatever reason the wifi calling setting will not turn on, on contacting Samsung they say this is likely due to the fact its an AT&T version of the phone and there is compatability issue. His carrier 3 ( the phone is unlocked) allows wifi calling so it's definitely a phone issue.
I wondered if I could flash a different firmware or such as it's a software issue and get it working?
Any help would be awesome, otherwise the phone is now useless.
Thanks!
Jonathan
Click to expand...
Click to collapse
U've the only option to flash an other firmware to test. I don't know