Related
I am seriously frustrated here:
I have an Ameo 16 GB (T-Mobile UK) and for the 1st couple of weeks remote desktop was working fine, then suddenly it stopped working.
I thought I broke the settings somewhere, so I double-checked everything. The T-Mobile Ameo comes with the default T-Mobile Internet connection pre-configured. It actually states "This connection is pre-configured. It cannot be modified."
The default settings are programs that auto connect to the Net should connect using the default T-Mobile Internet connection, and programs that auto-connect to a private network should use "My Work Network".
"My Work Network" has no values set anywhere.
Normal Internet access is fine in either IE or Opera (branded by T-Mobile as Web'n'Walk).
I have changed so programs that auto-connect to private network use T-Mobile Internet connection, same result as before.
I have set up a custom Internet connection for "My Work Network" using "general.t-mobile.uk" as access point, "user" as username, "pass" as password and domain left blank. I can connect to the Internet with these settings, but not via Remote Desktop.
Sometimes, normally after having re-booted the Amea and manually connected to "My Work Network" (as per settings above) I can connect, but it drops the connection while I'm still typing in username and password.
Normally I get either of these error messages when trying to connect via Remote Desktop:
"Cannot connect. Likely reasons are:
1) Specified computer name or ip does not exist.
2) A network error occurred while establishing the connection"
or
"Cannot connect with current connection settings. To change your connection settings, tap Settings".
I have cleared storage memory on the Ameo five times. I have phoned T-Mobile tech support who basically told me to sod off - apparently as long as the device can browse the Net they've done their job!
I have had T-Mobile replace the device and this morning I received a brand-spanking-new Ameo. I fired it up, let it go through the customisations, and reboot, then I tried Remote Desktop without changing anything or installing anything. And I got the same as above!!!!!
Please, guys, I'm desperate! Any help is very welcome here! I do network support for a living and I got the Ameo because I can fit a server's entire screen in and have a seperate keyboard. Except now I can't use it!
I used to have a Universal, which I sold to help finance the Ameo, so I'm truly stuck!
Oh how I wish I could unlock the damn thing and flash a better ROM to it!
Just as an update, yes, I've tried using "My ISP" as well, with the same results. And yes, everything's just peachy on the servers I need to connect to - I can connect to those servers using other devices.
And no, using Logmein is NOT an option and please don't even mention any form of VNC - you have to be seriously foolish to run VNC on a server, you might as well pay for some banner ads that say "Come hack me!"
Please don't give me advice on setting up routers, or Remote Desktop on 2000 Server, Server 2003 or Server 2008. I can do those quite well.
What I cannot do is get my damn Ameo to connect and stay connected and I'm absolutely desperate for help there!
the same
my ameo on t-mobile has done same thing, stopped working about 2 weeks ago, was working fine till then, only reason i bought the damn thing (anmd yes, i too ebayed my exec, i regretting it
so anyone out there got any ideas? i have same problem using ICS so i am guessing either a network etting on the phone, or some idiot at t has closed rdp traffic (tried chanmging a port number to 80 on a test box behind my router, still no go)
What is the operating system on the target pc first off. as i had that problem with a hack fix on vista home premium
all i had to do was to re-apply the fix.
as far as remote desktop the Ameo 8gb model ( x7500) didn't have rdp on it so i used one of the ones from this forum but under another section ( i think it was networking but do s earch to find them )
needless to say mine has never stopped working
a good test is try it from your local wireless home network if it's a home pc, and if ti works then look at the forwards on your router, make sure 3398 is still forwarding to YOUR pc and that your pc still has the same IP.
if you have a static ip and no router. always check your firewall settings.
as far as other possibles if your internet is working and all other data connections then there's no reason it SHOULDN'T work as t-mobile do not filter out 3389 port.
it has to be a problem at the target machine or network in that case.
but feel free to tell us more about the target pc and how it's connected to the internet and maybe we can find a solution
also what RDP client are you using on your Ameo
Cyberjak, the target machines vary: Server 2003 Enterprise Edition running ISA Server 2006, and Server 2008.
RRAS is installed on the non-ISA servers, while ISA of course takes over where RRAS left off. In all cases ports 3389 (TC{P & UDP) is open for inbound access, and on the ISA box it is open for in and outbound access.
Had you read what I wrote in my second post you would have seen I need no help in setting up RDP. I build, support and maintain networks for a living and trust me when I say the issue is NOT with the remote servers, but with the Ameo! I can use a collegue's O2 Touch Diamond and connect to any of the servers, but not the Ameo 16 GB.
I'm using a default T-Mobile Windows Mobile 6.1 setup as my Ameo has never been unlocked or flashed, and I'm using the stock standard Remote Desktop client that came pre-loaded and that used to work.
The issue is either with the Ameo, or with T-Mobile blocking RDP.
NanoRuler said:
Oh how I wish I could unlock the damn thing and flash a better ROM to it!
Click to expand...
Click to collapse
Why can't you do this? Is your phone owned by the company and they would frown if you modified it? AP4 includes Remote Desktop Mobile, so you might try that ROM if you do unlock.
My device is a 7510 and Olipro's unlocker doesn't work on it. I have been explicitly told that the unlocker might brick it
Hallelujah! The age of miracles is upon us!
I've put in a complaint to T-Mobile, and out of the blue Remote Desktop started working, while I also received an e-mail from T-Mobile's tech support.
Here's an extract from the e-mail:
"I have came across someone else with this problem and we are trying a temporary fix by adding a update to your account which is on now, so if you could retry the connection and let me know how you get on"
My translation of the message: We screwed up by choking RDP to save bandwidth across our network, you (and presumably others) caught us out, so now we'll pretend we're the good guys and that we've discovered something wrong and we'll fix it, but don't expect us to say sorry!
I will give T-Mobile a ring today and see, I guessed it would be t-mobile as I ave a whole range of different RDP servers I connect to and none worked!
lol, T-Mobile took all of about 2 minutes to enable my RDP again, told them I knew it was there prob as I read on XDA-Developers, got to love the internet nice one NanoRuler
NanoRuler said:
Hallelujah! The age of miracles is upon us!
I've put in a complaint to T-Mobile, and out of the blue Remote Desktop started working, while I also received an e-mail from T-Mobile's tech support.
Here's an extract from the e-mail:
"I have came across someone else with this problem and we are trying a temporary fix by adding a update to your account which is on now, so if you could retry the connection and let me know how you get on"
My translation of the message: We screwed up by choking RDP to save bandwidth across our network, you (and presumably others) caught us out, so now we'll pretend we're the good guys and that we've discovered something wrong and we'll fix it, but don't expect us to say sorry!
Click to expand...
Click to collapse
RDP Port filtering or NAT misconfigured !
bhermer said:
lol, T-Mobile took all of about 2 minutes to enable my RDP again, told them I knew it was there prob as I read on XDA-Developers, got to love the internet nice one NanoRuler
Click to expand...
Click to collapse
Just realised what T-Mobile said in their e-mail "I have came across someone else with this problem" - was that you? That WOULD be funny!
Way I look at it if we don't stick together we'll get shafted by big corporations!
Used to know a guy who had something printed on the reverse of some of his business cards. It read "Doing business with your firm is like having sex: it gives one a feeling of warm bliss.....while being screwed!"
Thanks to T-Mobile I know what that feels like! Having said that I'll also categorically state the last guy I dealt with at T-Mobile knows his stuff and was very helpful.
Curious, it does lead to believe something about the ports being like group policy's that they use as the voice over ip ports only are open for WnW Max customers usually unless you scream at them after being with them for a long time. heheh
Nano, no offence mate but i've been doing similar work for years as well but it's sometimes the simple things so you can understand me asking.
you would ask a client the same thing.
NanoRuler said:
Hallelujah! The age of miracles is upon us!
I've put in a complaint to T-Mobile, and out of the blue Remote Desktop started working, while I also received an e-mail from T-Mobile's tech support.
Here's an extract from the e-mail:
"I have came across someone else with this problem and we are trying a temporary fix by adding a update to your account which is on now, so if you could retry the connection and let me know how you get on"
My translation of the message: We screwed up by choking RDP to save bandwidth across our network, you (and presumably others) caught us out, so now we'll pretend we're the good guys and that we've discovered something wrong and we'll fix it, but don't expect us to say sorry!
Click to expand...
Click to collapse
A possible solution for those of us on T-Mobile's standard web n walk
Sorry to resurrect this thread, but I thought I'd post my experiences here in case anyone else (like me) searches for a solution to enabling RDP on T-Mobile (UK at least).
I was having the same problem with remote desktop, it saying that the server was not available. I phoned up T-Mobile's helpdesk as recommended here and after getting past first line support (who didn't know what remote desktop was, and tried sending new connection settings to my phone to resolve the issue) I got through to someone who knew what they were talking about. Turns out that I'm on T-Mobile's "basic" or "handset-only" web-n-walk package, and it's not possible to use RDP on this. I assume they block the relevant ports. They told me that I could pay an extra fiver a month to upgrade to a version of web-n-walk which can handle RDP.
Well I told them I would think about it, but instead tried to find a way around it as the one or two times I need to use RDP are certainly not worth a fiver a month. My solution is probably only suitable for the more techy of us, but without much work and with no prior experience I managed to set up a SSH tunnel using FreeSSHd as a server running on my windows server (although a normal windows box should work fine - http://www.freesshd.com/) and zaTunnel as a client on my phone (http://www.zatelnet.com/zatunnel/main.php). Both programs are free.
Basically my phone takes all RDP connections and tunnels them over SSH to my windows server, which then turns them back into RDP connections. T-Mobile have no idea I'm using RDP, and if they block the SSH port in the future I can always change FreeSSHd to run on port 80 (for web). This will also work for other protocols T-Mobile might be blocking (FTP springs to mind).
Just thought I'd post this in case anyone was in my situation of needing RDP on their standard web'n'walk.
Cool! Thanks for posting your rather excellent work-around! I will certainly be referring people back to your solution.
I think T-Mobile's out of order for not allowing RDP on all plans, without absolutely clearly stating that on some plans it isn't allowed.
You're the customer and you pay for some bandwidth. Short of illegal activities, what you use that bandwidth for is none of their business.
T-Mobile Grrrr
Many Thanks for this thread.
My Remote Desktop stopped working on my phone last month but co-incidently it was around the time I was re-intsalling my server and also flashing numerous roms to my phone so thought it maybe something with that.
But then realised I could remote desktop over my wireless at home and from other networks across the net so it wasn't anything to do with config on my side. Thought either phone or network.
Flashed a rom with remote desktop that i KNEW worked and still nothing...
Thought - this MUST be T-Mobile... glad I'm not the only one.
Have sent an email and hopefully they'll enable Remote Desktop on my line.
There is no way I'm gonna start paying an extra £5 a month for something I've been using for the last 20 months as part of my package and have removed wihtout any notice/warning.
i'll tell 'em where to shove their £5 extra a month
Hey all,
So I've got a small issue. I've got a Verizon XV6800 with the MR1 Rom WM6.1, Valhalla GPS server, 3.42.50 Radio.
Internet connection sharing is not working at this point. I've gone through the winmodem and internet connection sharing cab installs, registry edits, etc. None seem to help.
I previously had a ATT tilt 8925 and had no issues whatsoever tethering it to my mac by just pairing the phone, selecting to "Using a direct Higher speed connection to reach your ISP". Starting Internet Sharing on the phone, selecting Bluetooth PAN & the default data connection, then selecting connect. Then selecting "Connect to network" On the mac through the my phone listed in the bluetooth connections. That simple.
Having installed the "Internet Sharing" cab onto the phone. Internet sharing appears to work, but the phone does not advertise this service, like the ATT tilt did on ATT's network.
I've also tried a few registry edits, and used all variations of modem scripts, and got all the dialup info from verizon directly (so I know it was right ) but could not get dialup to work either. Usually not detecting a carrier, other times lockups.
I truely want to get the bluetooth-PAN working again as it did on my tilt. Anyone have this working on the MAc with a XV6800 on verizon?
i did have it working before. I'm wondering if you might be more successful with a custom rom. Verizon installs software (at least previous roms, I haven't tested the MR1 rom) that reverts reg edits and keeps it working like VzW wants it to. This could be causing problems. First check after a soft-reset to make sure your reg edits still exist.
Also I'm sure you've tried this be in Leopard's bluetooth setup delete the phone and try again. You need to select the type of device as any device in order for leopard to see it. Can you connect the device to your mac? Try that first. If you get a BT connection non-internet connection and you change your settings delete the phone and try again. I forget some of the setting I used. Also Engadget had a how to article for BT pan using the xv6700 and Tiger most of the information is still useful. It's a couple years old so you might have a hard time finding it.
Hope some of that helps.
Cycomachead said:
i did have it working before. I'm wondering if you might be more successful with a custom rom. Verizon installs software (at least previous roms, I haven't tested the MR1 rom) that reverts reg edits and keeps it working like VzW wants it to. This could be causing problems. First check after a soft-reset to make sure your reg edits still exist.
Also I'm sure you've tried this be in Leopard's bluetooth setup delete the phone and try again. You need to select the type of device as any device in order for leopard to see it. Can you connect the device to your mac? Try that first. If you get a BT connection non-internet connection and you change your settings delete the phone and try again. I forget some of the setting I used. Also Engadget had a how to article for BT pan using the xv6700 and Tiger most of the information is still useful. It's a couple years old so you might have a hard time finding it.
Hope some of that helps.
Click to expand...
Click to collapse
As mentioned, I have tried a ton of different methods to try and use the data connection, from using dialup settings, to trying to get the Bluetooth Pan working. I've removed and re-paired the device from my mac, flashed roms, hacked away at the registry a ton of times. Nothing seems to give so far.
I've got one more suggestion, found here: http://forum.xda-developers.com/showpost.php?p=1794133&postcount=29
I'm going to give this a shot tomorrow and will let you know how it goes.
Eponymous069 said:
Hey all,
So I've got a small issue. I've got a Verizon XV6800 with the MR1 Rom WM6.1, Valhalla GPS server, 3.42.50 Radio.
Internet connection sharing is not working at this point. I've gone through the winmodem and internet connection sharing cab installs, registry edits, etc. None seem to help.
I previously had a ATT tilt 8925 and had no issues whatsoever tethering it to my mac by just pairing the phone, selecting to "Using a direct Higher speed connection to reach your ISP". Starting Internet Sharing on the phone, selecting Bluetooth PAN & the default data connection, then selecting connect. Then selecting "Connect to network" On the mac through the my phone listed in the bluetooth connections. That simple.
Having installed the "Internet Sharing" cab onto the phone. Internet sharing appears to work, but the phone does not advertise this service, like the ATT tilt did on ATT's network.
Click to expand...
Click to collapse
I was wondering if you be gracious enough to share the Internet sharing CAB i only need to get it to work thought the USB cable and on a windows box, and from what im getting you got that far... JUST not working on a mac...
if thats the case, i would be ever so greatful..
Thanks
thetaz01 said:
I was wondering if you be gracious enough to share the Internet sharing CAB i only need to get it to work thought the USB cable and on a windows box, and from what im getting you got that far... JUST not working on a mac...
if thats the case, i would be ever so greatful..
Thanks
Click to expand...
Click to collapse
You can use the link from the previous post here, and just copy the dll's and exe to the Windows directory, and place teh shortcut into the Device\Windows\Start Menu\Programs\ directory.
Eponymous069 said:
You can use the link from the previous post here, and just copy the dll's and exe to the Windows directory, and place teh shortcut into the Device\Windows\Start Menu\Programs\ directory.
Click to expand...
Click to collapse
hey, ok great, i just downloaded the file, Just one question..
The file i downloaded has about a page of Reg Key changes, you didnt mention that in your "thngs to do"
Just want to see if i am to make all those changes or not.
thanks
So, your problem is in getting the internet connection to work and not connecting it to the mac, right? Does your mac recognize the phone as a modem?
If you're using MR1 I think you might need to hard reset and the soft reset right before the Verizon customizations run. You won't be able to run their apps but there won't be software to cripple the phone.
i have the same exact issue i have a new macbook pro and the bluetooth connects however the speed is slower then dial up it works perfectly however on bootcamp apple has to change the drivers
So more results.
I tried all the registry edits, (much easier with CD-Regedit so you can make the changes on your desktop) and now internet sharing does not even allow me to select a connection type, it had worked previously.
The only thing that was missing before I made the registry changes was that when I pair the phone, in the services listed, "Network Access Point" is not one of the listed services. My old phone has this service listed, and this is how I used it, where I started internet sharing on the phone, then selected the bluetooth device (phone) on the mac and selected: "Connect to Network) and it worked flawless.
Back to the drawing board. I'm going to try next to re-flash the MR1 rom and do as Cycomachead suggested and stop verizons customizations from happening.
bryanw17, what were the exact settings you used for dialup on the mac. The modem script used is probably the most important piece.
Number: #777
Username: Phonenumber (or [email protected]????)
Password: (We know this one, not sure if it's legal to post though)
Darn, I wish I could provide more help. It is indeed possible in Leopard, I had it going before I began flashing my phone - and I no longer have a data plan to test, otherwise I'd be using it a lot more!
aparently no one with a new macbook pro can get bluetooth pan to work. I have it connected however the drivers for the new macbook pro do not provide a good connection if you search the mac forums theyve been talking about it on there. I dont use a username n password however because i use the internet sharing app for the moment i am using wmwifirouter to connect online however my xv6800 doesnt charge at the same time for some reason so u can only use it till the battery dies
So some more results.
I installed ICS and all the registry edits. Then the internet Connection Sharing did not function at all. I verified the registry settings, all were fine. So no dice with me.
So back to the drawing board.
I installed a previous rom. DCD 3.2.6, and guess what? From initial flash of the phone and initial setup, no apps installed, no hacking, ICS runs and provides a network connection to my mac perfect. I also instantly notice when I pair it through bluetooth, it allows the option of "Access this device as a network port". And "Network Access point" is listed as an offered service.
I installed newer rom DCD 3.3.4, and the MR1 Rom. Neither have ICS installed initially. I can install the two files: intshare.dll and IntShrUI.exe into the windows directory without any reg edits, and then ICS works on the phone, but then pairing the phone to the Mac, and attempting to discover teh PAN service is unsuccessful. It only is discovered as a Dialup Access device, and not a "Network Access Point".
So, It appears I can get internet Sharing via Bluetooth PAN to function on the phone no matter which rom, but have not figure out how to tell the mac, or trick the mac, into thinking the "Network Access Point" service is available.
I have pulled completed registry dumps with CE-Regedit and compared the differences between the two, which there are quite a few, but not sure how to export these differences with the program so I can apply them to the other roms registry. I guess I might try a fukll backup and then restore to the new(er) rom and cross my fingers.
I'd stay with the 3.2.6 rom. and 3.42.50 Radio, with PRI 2.03, but I can only seem to make the GPS function successfully with the MR1 stock verizon rom.
Anybody want to take the two regs files compare, and see if they can find out where we can make the change to have the phone advertise the service "Network Access Point" when being paired to the mac or PC?
On one last note. I also tried the method of restoring the MR1 official rom, and then not allowing the customizations. ICS will function, but again, not advertising the service: "Network Access Point" when pairing, so it's not recognized as a valid networking method.
Where did you get those files (intshare.dll and IntShrUI.exe) to allow ICS via bluetooth?
Nevermind, I found it on PPCGeeks.
Don't know why DCD disabled the BT DUN on ICS.
I use Missing sync, and I turned on PAN then added my phone and it shoed it as a modem when I added it, but my BT connection is fairly Unrealible compared to the USB teather on Bootcamp
i was under the impression that bt pan has been whacked on macbook pro models starting from early 2008 on. anything earlier than that and it seems to work great. does anyone know why bt pan doesnt work on the newer machines and how to get it to work?
I know this is not allowed by att, but is this something that can be hacked, or is it a hardware issue? Or at least tethering?
Guess it should be solved as a voice call functionality block. S-OFF + simple property modification. Without custom ROM.
I'm sure a hack will be found for it, once the device is rooted and such. Much like the Sprint device ROMs come with the Wireless Tether application, there will likely be one for the Jetstream once we can get the device rooted.
Greetings... Believe it or not, I "accidently" found a way to activate it, without root. I installed super box from the market, and when I was in the power save menu, the hotspot line said off, but clicking it took me to the regular settings menu and the menu to the right allowed me to turn it on, give it a name and set security! The odd thing is that the list of menus on the left is not highlighted as to which one you are in, so you can't access it through "settings," only superbox. There may be another way, but this works!
HI,
I am new to Android with my first device being the Jetstream. I would love to have hotspot capabilities, would it be possible for you o provide a stepwise outline of how you gt this feature to work?
Thanks so much.
Ok, I downloaded the program and as you said, I was able to turn on the wi-fi hotspot capability; however, even when I changed the SSID name it showed up in other devices as "HTC Portable Hotspot" and even if the security was left open it kept asking for a password. I changed the security to require a password, but when I entered it it did not allow me to connect.
Did you do anything else?
I think you are on track.... The password is your choice, and is only an option if you pick one of the two security protocols. The password would be entered on the other device trying to connect to the jetstream. If the name is fixed, I'm at a loss, didn't have that issue...
any luck with this?
This morning I was confronted with something weird. My phone all of a sudden could not connect to a remote VPS server via POP3. It would just say No Connection.
The same phone however could connect to everything else, including other services on the same remote server. And, it could connect to other servers using POP3. If I switched to WiFi, it then connected just fine.
Drove me nuts trying to figure out what the issue.
Obvious things were checked, firewall, pop3 server etc... to no avail...
So finally, I figured that Verizon was having some weird 4G problem related to port 110.. I had the POP3 server, listen on a secondary port... Still nada...
While looking at the POP3 Server configs, I saw that they now had support for ipv6, but that by default it didn't listen to them. So I changed the configuration and bang.... the phone connected...
It was apparently trying to connect to ipv6 since the time I found it was failing.
Wonder if anyone has run into this.... Looking at the logs, my phone is the ONLY device connecting via ipv6, everything else is using ipv4.
Well this turned out to be pretty simple.
IF you publish an AAAA record for a host, and you are using Verizon 4G, it will use the AAAA entry for the host in liu of the AA record.
In my case, this had surprising results that once I figured it out made sense, but at the time caused a lot of confusion as to what was the trigger for the action that was taking place.
krelvinaz said:
Well this turned out to be pretty simple.
IF you publish an AAAA record for a host, and you are using Verizon 4G, it will use the AAAA entry for the host in liu of the AA record.
In my case, this had surprising results that once I figured it out made sense, but at the time caused a lot of confusion as to what was the trigger for the action that was taking place.
Click to expand...
Click to collapse
Yes.. you learned the hard way that LTE was rolled out with native IPv6 (and preferred stack too). Pretty smart to setup a new network using IPv6 and save us the headaches of upgrading later after the fact...
Hi. When someone trying to call me and i answer the call it immidietly disconnecting and it shows that i have missed call, the same happens when I'm trying to call someone. I'm almost 100% sure that this is happening because I deleted some important system app, but i have no idea which one. I tried to restore a few of them, rebooting phone in save mode, removing SIM card and insert it again. Nothing helped. I read somwhere that it could be potentially some spying app, but this is unlikely, because if that was the case then phone calls should work fine in safe mode, but they don't. I attached file with almost all the system apps i deleted.
Update: I reset network settings and figured that phone calls don't work when I have VoWi-Fi turned on, but they worked before without any problems, they work however with VoLTE turned on. I couldn't find any system app that could cause this and it's unlikely that my phone operator has changed something with this. Perhaps it is caused by some router update (Huawei AX3 Pro Quad-Core)?
I think this issue is from your phone operator's side.
Again, if this happens just try this, turn on Airplane mode for a few seconds then turn it off, hope it works.
rickysmith-tth said:
I think this issue is from your phone operator's side.
Again, if this happens just try this, turn on Airplane mode for a few seconds then turn it off, hope it works.
Click to expand...
Click to collapse
I already did that
Update: I spoke with Orange support and this is the informations i got:
,,Phones not on the list of terminals supporting VoLTE in Orange will have The VoLTE and Wi-Fi Calling services systematically disabled. Because the phones have not passed certification, Orange is not able to ensure the correct combination of calls and quality during the call. Connections from non-certified engines can have a negative impact on the service for other users on the network."
,,If the phone was purchased outside of Orange, the service is not supported by Orange"
So they created some magical certificate and only the phones bought from their shop will support this functions and the same phones from outside their shop will not. Nice job Orange! And of course they didn't share any information about this certificate even tho i asked, they just copy and paste the same massages over and over again.
Ps. This line ,,Connections from non-certified engines can have a negative impact on the service for other users on the network." is of course a total crap, because everyone in my house is using this functions and no one has ever complain about quality of phone calls and not a single phone was bought from the operator.
Certification just means the phone has been tested and proven to work. There is no actual certificate. You can use non-certified devices on a network but you run the risk of something not working correctly. Remember that this is their network and they can control who can use and what they can do on it. If they choose to block all non-certified devices then thats up to them. They can let it be a free-for-all but that just makes diagnosing issues alot more difficult for them and for you.
The bit about negative impacts you are misinterpretating. They only say that it CAN have a negative impact, not that it does. I've seen issues on networks where one misbehaving device interferes with all other devices on the network. Thats what the network operator is trying to avoid with certification.
As for the original issue, VoLTE and WiFi Calling are complex technologies. You're calling over a data connection which routes your call to the operators servers which then transfer the call to the standard telephone network. There are so many kinks in the chain here that its never a simple fix. For instance, if your Internet provider uses traffic shaping or you set QoS on your router, they can interfere with WiFi Calling.
I would suggest the biggest issue here though is that you have tinkered with your phone and broke it yourself. You cant blame anyone else but yourself for that. System apps can interlink with each other. Deleting an apparently useless app maybe provide something useful to a critical app. That will then break functionality. Your tinkering also widens all the possible issues that it could be so I dont even know where to start.
richhaynes said:
Certification just means the phone has been tested and proven to work. There is no actual certificate. You can use non-certified devices on a network but you run the risk of something not working correctly. Remember that this is their network and they can control who can use and what they can do on it. If they choose to block all non-certified devices then thats up to them. They can let it be a free-for-all but that just makes diagnosing issues alot more difficult for them and for you.
The bit about negative impacts you are misinterpretating. They only say that it CAN have a negative impact, not that it does. I've seen issues on networks where one misbehaving device interferes with all other devices on the network. Thats what the network operator is trying to avoid with certification.
As for the original issue, VoLTE and WiFi Calling are complex technologies. You're calling over a data connection which routes your call to the operators servers which then transfer the call to the standard telephone network. There are so many kinks in the chain here that its never a simple fix. For instance, if your Internet provider uses traffic shaping or you set QoS on your router, they can interfere with WiFi Calling.
I would suggest the biggest issue here though is that you have tinkered with your phone and broke it yourself. You cant blame anyone else but yourself for that. System apps can interlink with each other. Deleting an apparently useless app maybe provide something useful to a critical app. That will then break functionality. Your tinkering also widens all the possible issues that it could be so I dont even know where to start.
Click to expand...
Click to collapse
They said that they will be disabling systematically Wi-Fi Calling and VoLTE on non-certified phones (phones that were not bought directly from them), so that would mean that this is not my fault, but if it is then this is why i shared a list of system apps that i deleted so someone who knows more about them than me could tell me which one have any connection to Wi-Fi Calling. Also this phone I have is marked on their website as supported for this technlology, so tell me what is the diffrence between exactly the same phone bought directly from them and bought somewhere else (from official source of course), except additional bloatware, that would have any complication with those technologies?