So I need to install a rom on the HD2 where I know wifi calling will work reliably. Its super important because this HD2 will be used where there is very spotty T-Mobile service. Wifi with a UMA Blackberry is the only thing that works currently.
I know there has been discussion as to how reliable the wifi calling feature can be in general, but I have a MyTouch4G and it works perfectly.
So is it a froyo only thing, or maybe only a froyo sense only thing?
I have friends that have it on their G2 and it works perfect for them as well.
So can anyone list a few roms where the wifi calling works reliably?
Thanks.
EyeAndroid said:
So I need to install a rom on the HD2 where I know wifi calling will work reliably. Its super important because this HD2 will be used where there is very spotty T-Mobile service. Wifi with a UMA Blackberry is the only thing that works currently.
I know there has been discussion as to how reliable the wifi calling feature can be in general, but I have a MyTouch4G and it works perfectly.
So is it a froyo only thing, or maybe only a froyo sense only thing?
I have friends that have it on their G2 and it works perfect for them as well.
So can anyone list a few roms where the wifi calling works reliably?
Thanks.
Click to expand...
Click to collapse
The common belief is that wifi calling can't work on the hd2 due to it not having some hardware required for it
Really? I thought that it was just an app? Just like the vibrant doesn't come with it but someone was able to figure it out.
Here..I found the post. Its not entirely hardware related, but has something to do with the radio..
The UMA client is embedded into the baseband processor of a dual-mode handset. The client executes the UMA protocol and is also responsible for monitoring Wi-Fi threshold levels, establishing the IPSec tunnel, and handling VoIP aspects of a UMA circuit voice session. Consequently a UMA client consists of four logical elements.
The UMA Protocol Interface
The core UMA protocol resides within the baseband stack. This is the set of core messages responsible for managing and maintaining an active UMA session. The core protocol module is integrated into the platform's radio resource (RR) layer and tunnels all messages between the handset's Non Access Stratum (NAS) layers and the mobile core network. GSM has standardized a large number of supplementary services. The UMA architecture is transparent to the NAS layers (MM and above) in the handset and the network. Because the supplementary services logically reside in the NAS, they are inherently supported in UMA access mode.
so it seems i was wrong about the hardware specific part to some degree, it seems that the radio software in the device has to have the uma feature (client) written in and then flashed to the device to add that functionality to the hd2, but thats the big issue... who knows enough to dismantle a radio nbh and modify and insert it with the code needed..? i guess in that matter it might as well be entirely hardware based..
so it may be possible but not likely at the moment...
Click to expand...
Click to collapse
EyeAndroid said:
Really? I thought that it was just an app? Just like the vibrant doesn't come with it but someone was able to figure it out.
Click to expand...
Click to collapse
Yes, you have that correct. I use the Nettalk app for WiFi calling on the Cmylxgo NAND Stock Desire HD(2) ROM without a problem.
any news on the ROM?
There's a kernel in the nand section being tested for wifi calling, I think there's a rom in the thread too but I don't know if its working
Edit:
Here's the link, http://forum.xda-developers.com/showthread.php?t=1038784
It doesn't appear to be working yet, but tyweens working on it and he's got an awesome kernel and rom
Related
Just saw this over at msmobile.com http://msmobiles.com/news.php/4853.html Is it true???
It doesnt work in my jasjar
didnt think it would......
Its ROM dependent if i am not mistaken.
UD.
Dont tempt the devol on that one: 802.11G on the Universal
universaldoc said:
Its ROM dependent if i am not mistaken.
UD.
Click to expand...
Click to collapse
Hello everybody; For your information, i tried everything discussed in the forums to unlock 802.11G on the Universal (V1640 flashed to qtek 9000 french release), from altering manually the registry and clicking on the avaiable cabs whithout any success.
But i almost lost connection between my UNIVERSAL with my 108Mb netgear router in the process and could'nt revert back WITHOUT hardresetting the universal and reinstalling it from scratch.
So my advice would be to await lore precise info on that "may be embedded" feature without attempting anything in the meantime as your bound to loose some of the features of the universal.
Brgds, Arnaud
It worked on my JasJar, although at first it didn't want to reconnect. I'm not that it's any faster, but I think I'll leave it set this way.
**Can't get it to work after setting my wifi back to mixed and then back to G only, so maybe I was hallucinating previously. Sorry**
It doesn't work. I even tried it myself! I was sitting here switching my router from B&G to G-only and it would only connect when in B&G mode...
Why would they design hardware that could cope with 802.11b and g and then cripple the faster speed through software?
Surely this must be a hardware limitation that we'll never overcome? :?:
Unless maybe it's to preserve battery life. Would the g protocol require more battery than the b protocol?
If you check the chipset datasheet for the wlan you see that there isn't support for G. This is just a hoax.
End of hoax
ncruz said:
If you check the chipset datasheet for the wlan you see that there isn't support for G. This is just a hoax.
Click to expand...
Click to collapse
Hum, this certainly makes sense and seems a final and reliable statement;
Adhoc (Arnaud)
Didn't work for me.
Didn't work also on my Dopod 900.
Re: End of hoax
adhoc said:
ncruz said:
If you check the chipset datasheet for the wlan you see that there isn't support for G. This is just a hoax.
Click to expand...
Click to collapse
Hum, this certainly makes sense and seems a final and reliable statement;
Adhoc (Arnaud)
Click to expand...
Click to collapse
The link is on the wiki, on the hardware part...
May have worked
I could not find the device under the same registry string as documented.
Found my wireless under tiacxwln1, suggesting the listed fix may relate to newer models may have a newer wlan card. My unit is a T-mobile MDA pro given to me around November.
Amended the registy settings and connected to a 54g router.
Did seem faster and have discovered more networks at my office today.
Still to establish if it is 54G or not.
On another note looks like T-mobile uk may be readying a rom upgrade, lots of activity on their ftp site last week. Half of the URL's I use to have to official upgrades and firmware for T-mobile uk devices dont work anymore.
It's got me thinking about this whole thing.
WHAT IF you could "rewrite" the radio stack, much like Linksys has provided the source code so that avid developers and Linux lovers could mess around with it?
Could we possibly enable EDGE capability? Could we retune to get 850 instead of 900 MHz?
Since the radio stack can obviously be changed regardless of the CE ROM, it may not be tied too directly to jump points in memory (unless the developers are following a fixed structure on how to build the stack).
I'm thinking back in the days when latter 33.6k modems were flash-upgradable to 56k with that K56Flex/X2 fiasco back then...
If the hardware is there and is primarily software-controlled, it just takes the right reprogramming to get it right.
Anyone on the same page as me?
BeyondtheTech said:
Since the radio stack can obviously be changed regardless of the CE ROM, it may not be tied too directly to jump points in memory (unless the developers are following a fixed structure on how to build the stack).
Click to expand...
Click to collapse
What you call a "radio stack" is usually a realtime unix
operating system, running on a separate computer with its own CPU/RAM/ROM/IO/etc.
It is relatively easy to replace wince with Linux on the "general purpose" part of the phone.
Dealing with the GSM part is much more difficult for various reasons.
ratcom said:
Just saw this over at msmobile.com http://msmobiles.com/news.php/4853.html Is it true???
Click to expand...
Click to collapse
Universal uses the same TI ACX100 wlan chipset as the Blueangel, ipaq hx4700, and many others.
It supports only the 11Mb speed.
cr2 said:
ratcom said:
Just saw this over at msmobile.com http://msmobiles.com/news.php/4853.html Is it true???
Click to expand...
Click to collapse
Universal uses the same TI ACX100 wlan chipset as the Blueangel, ipaq hx4700, and many others.
It supports only the 11Mb speed.
Click to expand...
Click to collapse
Then Universal chipset is different from Wizard chipset...:?:
I tried DJVW WLAN 302.11g Activator, suggested in Wizard forum, with my 9000 but i get CapNotify error on startup :?
cr2 said:
ratcom said:
Just saw this over at msmobile.com http://msmobiles.com/news.php/4853.html Is it true???
Click to expand...
Click to collapse
Universal uses the same TI ACX100 wlan chipset as the Blueangel, ipaq hx4700, and many others.
It supports only the 11Mb speed.
Click to expand...
Click to collapse
Is there a pin compatible 802.11G chip out there? If upgrading surface mount RAM in these things is possible, why not radio chips?
Tryed it, been there.
DOES NOT WORK FOR ME
(testing was done by setting my Router to G only mode the MDA PRO would not connect)
Anybody get VOIP working on the WM6 Herald yet? I've read the entire thread over on the Hermes forum and installed both WM6VoiP.CAB and SipConfig on my Wing. I've gotten the internet connection on Today and have been able to try and dial out but no ring just 15 seconds of silence. I uninstalled and installed VM VI Black VOIP & Config.Cab with the same outcome.
I got it to work, but it worked like Crap. Never messed with it much since . . .
haven't you heard?
http://www.newsfactor.com/story.xhtml?story_id=53378 [\url]
T-Mobile Marries Wi-Fi to Cell Phones
Yep, heard about that. I've only got it working with Fring which blew. Hopefully the "legal" version from t-mobile will be good. Since I pay for their service anyway.
Woops.. Looks like [email protected] may not work. Only for UMA phones which Herald isn't or so they so.
Isn't UMA (the actual handling of switching calls from WiFi to GSM) all in the software. So shouldn't they be able to come out with an update that will allow the wing to work on [email protected]? Is this possible or is there some hardware required that I don't know about to run UMA?
It's software, but not in the "just install and go" sense. The switching is handled at a low level in the radio to keep it seamless. Unless you have access to the sources it's not going to be easy to hack the GSM stack to support UMA.
gamescan said:
It's software, but not in the "just install and go" sense. The switching is handled at a low level in the radio to keep it seamless. Unless you have access to the sources it's not going to be easy to hack the GSM stack to support UMA.
Click to expand...
Click to collapse
That's what i was thinking, it would likely be a full update to the phone, sorta like when I updated my Dash from WM5 to WM6
Check out http://forum.xda-developers.com/showthread.php?t=315654 for a FULL review of Fring.
This possibly needs to be in the dev section but I will start here.
First off this is not a complaint. What I initially want to do is get an understanding (Technical) of the issues around the PPP dropouts and locks ups.
From where I sit this is the only outstanding issue around the current android builds. Simply the phone rocks on SD card and is ultra stable and fun.
I have noticed various wiki'sstate that internet access is complete however obviously not.
There are a number of issues such as
1: Network dropout. Data connectivity will stop responding. Restart of the radio or mobile data needed
2: Network freeze. Android restart as the radio will not turnoff.
3: console level networking not avail. Eg ping etc simply does not work. DNS does not resolve and ping cannot find a route. Std Android this works fine.
4: Related issues. GPS-A data not downloadable. Only via application layer tool.
Is PPP the default connection type on factory android builds?
What is the difference between the HD2 in dev and a std android with the implementation of the data connection.
How can I help. I have over 20 years in IT and have a thorough understanding of TCP IP layers and routing. I have reasonable understanding of Linux and the kernel IP stack but zero understanding of the android kernel or application layer.
I also have dollars to contribute.
Update:
Currently I am trying all four with isome improvements
1: Updated the Ril WRapper with no luck.
http://forum.xda-developers.com/showthread.php?t=794309
2: Change the phones default connection to GSM PL.
Change the setting found in the menu phone info when you "call" *#*#4636#*#*. There is a option to choose your preferred network. Set to GSM auto (PRL)
3: Update DNS settings.
http://forum.xda-developers.com/showthread.php?t=812930
4: Ensure the correct APN's are being used.
This is no internet versus unstable Internet.
Note. Currently trying all four and things are improving. Had my first dropout after 36 hours versus 2 per day. It happened whilst using the GPS and making a call which always tend to be a stresser anyway. Will try to keep this thread updated.
This thread also has a number of updates http://forum.xda-developers.com/showthread.php?t=813148
I am running a stock WinMo Rom (Latest European release 3.14 I believe). 2.15 radio on a Telstra Network in Australia. My phone is a T8585. Also running [19.10.10]|<<Mdeejay FroYo Sense Series>>|2.25.771.1| cos I like the transparent titlebars
Now I have been running all 4 of the above for around a week now and have to say there is a def improvement. Where it was common to get multiple disconnects per day I have only had 3 in the last week. Mainly when I use the GPS.
I am still searching and have yet to find a 100% fix the stability is now at a point of reasonable reliable. Also noted that the Devs are still hard at work on this.
Update 31-10-2010
A good test is to open google maps while driving. Its about the only time I get a drop out now.
The GPS kicking in always stresses the radio and that combined with the handover of cell sites is a great deal breaker.
This also seems to be consist with my suspicions around the poor handling of corrupt connections.
Eg the system on fresh boot only has a table for handling 50 connections line. This ensures it can handle multiple simultaneous connections as well as background coms.
Now when a connection is damaged or locked normally it should timeout and/or then be deleted from the table. My suspicions is that this is not happening and all the avail connection handling are slowly filling up until there are now free. Frozen this is why it seems to be very unlikely for a freeze to occur straight after a restart but more likely after a day. Also dependent on stress environments. Homes with lots of RF noise, Long way from cell towers, driving, lots of gps use, Wifi cut over.
http://forum.xda-developers.com/showthread.php?t=812930&page=7
http://forum.xda-developers.com/showthread.php?t=794309
Thanks for the response.
I was not looking for work around but more technical information to try and identify where the issue lies. curious to see if ppp is the default and if the ppp implementation should work or is it still a hack/work around.
The steps I have tried are
1: Updated the Ril WRapper with no luck. No improvement
2: Change the phones default connection to GSM PL. No improvement
3: Update DNS settings. Still testing however does not resolve console level network issues and unlikely related to ppp freeze. No logic?
4: Ensure the correct APN's are being used. No improvement
Note. Currently trying all three
This is also separate to a lot of people issues around APN's. From the application layer internet works fine except for the freeze.
I believe rmnet is android's default connection and ppp is winmo's. I think dft reengineered ppp for Android. Remember seeing it some where when ppp first started to appear. Of course this is how I remember it and my life is hectic so it might be the opposite.
Sent from my Mytouch HD2
So I understand that one of the issues with RMNET was dropped packets. Was this due to it not being correctly engineered/implemented or just a nature of the beast?
Also with the issues everyone is having why are we not continuing to investigate RMNET as at least this was initially more stable and more of a native option.
dusty_nz said:
So I understand that one of the issues with RMNET was dropped packets. Was this due to it not being correctly engineered/implemented or just a nature of the beast?
Click to expand...
Click to collapse
That is because it isn't implemented correctly. The radio receiver in our phones was made for PPP, not for RMNET. Latter is standard in native android devices. And there it works very fast and stable. So the devs had to implement PPP in android, which isn't proper working. But they're working on it to improve the stability, I'm pretty sure 'bout that. At least it does work and I had never problems with loosing my connection and bad speeds.
Edit: Those are the known steps to get it at least halfways stable working.
Cheers
Okay.
Did some more playing.
Both RMNET and PPP allow pinging from the console. Just had to enable SU first.
Thanks everyone for your info. Will try my best to be patient.
dusty_nz said:
Okay.
Did some more playing.
Both RMNET and PPP allow pinging from the console. Just had to enable SU first.
Thanks everyone for your info. Will try my best to be patient.
Click to expand...
Click to collapse
But did you also have a delay till it worked? It took me about 20 seconds before any reply came up. And does your ping test work if you try it in the hidden menu when you "call" *#*#4636#*#*?
Aye.
There was a delay and the hidden menu ping does not work either.
Still needs work.
dusty_nz said:
Aye.
There was a delay and the hidden menu ping does not work either.
Still needs work.
Click to expand...
Click to collapse
Right.
Have you seen this thread? It might be a possible solution.
Some people have reported that it works. But I had no time to test it. Had to move servers
That is fix number 3. Update DNS. Testing now. Only been 24 hours however no drops.
Seems strange thou. Hard to imagine it is a DNS issue.
On a side note. Does anyone know what changes to the Rom are needed when installing an RMNET kernel?
Eg If I took the latest MDeejay rom and changed the kernel?
Update
Update on first post.
Def improvements to be found. DNS seems to be the biggest improvement for me but also running all 4 at once.
dusty_nz said:
On a side note. Does anyone know what changes to the Rom are needed when installing an RMNET kernel?
Eg If I took the latest MDeejay rom and changed the kernel?
Click to expand...
Click to collapse
No one who knows cares enough to answer.
As far as I can tell, no 'modern' build uses an rmnet kernel anymore, because apparently the chefs either don't care about data reception, or don't think that there is a problem because they don't leave a build on long enough for it to start developing problems.
enneract said:
No one who knows cares enough to answer.
As far as I can tell, no 'modern' build uses an rmnet kernel anymore, because apparently the chefs either don't care about data reception, or don't think that there is a problem because they don't leave a build on long enough for it to start developing problems.
Click to expand...
Click to collapse
any build that says it uses michyprima r11 is still rmnet based. I don't think the nexus one-based kernels worked with ppp at all.
on another note, I was getting loads of Network Freezes (where flicking airplane mode wouldn't reset the data connection) since last week despite not fundamentally changing anything in my Android setup (see sig). However been doing some research around xda yesterday and may have found something else that's improved my ppp connection stability (so far) and resolved my constant network freeze issue... will update when I've tested this for a few more days.
Some improvment?
APNs are correct, Did the RIL_WRAPPER with no significant improvment. This morning I changed to GSM PRL and noticed an improvment.
Before the GSM PRL, I had many PPP drops, especially when streaming large amounts of data. After the GSM PRL update, I did try streaming youtube, Last.FM, slingpalyer together and NetTest, concurrently, everything is working with no PPP drop.
This is not enough to reach a conclusion, but nevertheless, I never could have done it before
Have a look here.
Stock rom 1.48 WWE, radio 2.15.50 and Froyostone 3.2
Thanks for the support!
BTW: How can I obtain the DNS information for my mobile carrier?
Just report.
I didn't believe change dns will work.
But after I change dns, the data suddenly work ( no need to restart!).
So I think it have something relate to dns.
Same thing. Updating the DNS in the build.pro file seems to have the greatest benefit.
I have a suspicion that the issues are caused with the network driver not flushing dead connections. Eg outgoing requests that to not get a reply. Ideally they should be flushed other wise the connection cache will fill until it can no longer take more connections. Symptom dead/frozen internet
All the symptoms seem to relate to this sort of issue
Things like ppp drop out more likely when on the move (More dropped packets). GPS and wifi but back. etc.
@Dusty_Nz,
Thanks for your help, this is a great thread and its certainly appreciated (the devs are busy enough as it is, xda member contributions are a great help).
As it was asked a few posts up, how do I obtain the DNS settings for my carrier? I am using TMobile US and I'd like to test your observations.
Thanks!
Sent from my HTC HD2 using XDA App
tgtoys said:
@Dusty_Nz,
Thanks for your help, this is a great thread and its certainly appreciated (the devs are busy enough as it is, xda member contributions are a great help).
As it was asked a few posts up, how do I obtain the DNS settings for my carrier? I am using TMobile US and I'd like to test your observations.
Thanks!
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
Follow the link on post 3
will then lead you here.
http://www.opengear.com/faq383-Confi...-APNs.html#USA
I've been looking at the T-Mobile official support forum on their website, and seeing quite a few people with problems running WiFi (or not being able to get it going again) and WiFi tethering after updating to the new 3.14 ROM.
Is it a coincidence that T-Mobile is announcing a new Tethering Plan just after this update? Or did T-Mobile deliberately "kill" WiFi tethering to force users to buy the new Tethering plan?
Asquared said:
I've been looking at the T-Mobile official support forum on their website, and seeing quite a few people with problems running WiFi (or not being able to get it going again) and WiFi tethering after updating to the new 3.14 ROM.
Is it a coincidence that T-Mobile is announcing a new Tethering Plan just after this update? Or did T-Mobile deliberately "kill" WiFi tethering to force users to buy the new Tethering plan?
Click to expand...
Click to collapse
Wifi tether was never on the HD2 to begin with, so nobody will know if it was a coincidence or not.
Indeed, WiFi tethering is something that has to be added by the end user, so it was never officially sanctioned by T-Mobile to begin with...but as far as intentionally screwing it up, I do not think T-Mobile would do such a thing. I mean comeon, they aren't Apple afterall. I personally chalk it up to a poor WiFi driver stack provided in the new ROM. Installing a new radio MAY help, but it's unlikely.
Here's my theory:
It seems to me that the 3.14 ROM has a feature to turn off or put your data connection in standby mode, (same deal with the wifi), when the device is idle... Which makes sense. It also turns off your data connection if you are connected to wifi. Still makes sense. SO if you are using your phone as a wifi router, that means you are probably on your other device and not on your HD2 and it's idle, so it shuts it down.
Most likely it was implemented to save battery life as well as save wasted network data.
You can't really call it sabotage when this device didn't come with a wifi router program in the first place. Not even an oversight by the developers. Although I admittedly did feel a little cheated when I realized that the US HD2 didn't come with the wifi hot spot. It was one of the features that was highlighted by HTC's marketing team for the HD2. It was also one of the main reasons that I wanted the phone, besides the fact that the screen was huge and it looked awesome. Of course once I started nerding out on it I quickly found that I could just install a cab.
If my theory is correct, maybe someone will come up with a work around. If not, then those of you who depend on the wifi tethering and want a stock ROM, should install Shehrams stock 2.13 ROM with the 2.10 touch drivers. It's pretty much flawless with the exception of a few minor known 2.13 issues. There aren't many. The biggest one for me was the touch sensitivity, which this ROM fixes. With the 2.10 touch drivers 2.13 is pretty great.
Obviously you do need to have HSPL to flash the ROM, but you can always go back to stock by flashing a stock ROM from a microSD card.
I just got around to testing this and i've been connected to my HD2 Wifi Router for over an hour on the web and it hasn't disconnected once... Which program are you using? Also my Wifi signal is great.
ditto on the wrong program, tom codon still works for me.
mr8820 said:
ditto on the wrong program, tom codon still works for me.
Click to expand...
Click to collapse
Yep. Tom Codon for pres.
I really don't see the need for wi-fi tethering. What is its advantage over Bluetooth or USB tethering?
me said:
I really don't see the need for wi-fi tethering. What is its advantage over Bluetooth or USB tethering?
Click to expand...
Click to collapse
BT is sssssssssslllllllloooooooowwwww compared to wifi tethering and USB tethering
the main advantage over USB tethering is no cable required. The disadvantage is sucking the life right out of your phone's battery
anhyeuemmaimai said:
BT is sssssssssslllllllloooooooowwwww compared to wifi tethering and USB tethering
the main advantage over USB tethering is no cable required. The disadvantage is sucking the life right out of your phone's battery
Click to expand...
Click to collapse
Has anyone compared WiFi VS USB tether speeds? I would think USB would be faster.
Yesterday I flashed GINGERBREAD-DS-Beta-20110716 on my 32B to experiment with inbuilt Sip stack and would like to say to would be users that this application in a rooted rom works wonderful. Both over WiFi and 3G. However it does have some limitations like not being able to choose any ports under 1000. ie I would prefer port 443 TCP. Having said that, most users will use port 5060!
All in all, it is very functional and usable. The battery will be consumed more if you tick for receiving calls but consumption is sip server dependent.
I am using it with VoXaLoT with 5 registration.
Note that new HTC android handsets like Desire and Incredible have this feature but limited to making calls over WiFi only.