Related
Hello,
I am brand new to the forums. I have done some poking around but I want to have a threat dedicated to this as Im going to assume a lot of people are going to have this problem.
I just bought my gtablet about 2 hours ago. I havent been able to root it or install any roms yet because I bought it in chicago and I am on my way back home to michigan right now as I type this.
I am trying to see if anyone knows how to get wireless tether to work on the gtablet. I have a rooted incredible running cyanogen 6.0.2 w/ wireless tether. I am connected to my phone right now as I type this on my netbook. I cant get my gtab to see my wireless tether...any ideas or things to try. I cant be the only one thats run into issues.
Secondly, maybe this needs its own thread. I was going to try doing it via bluetooth with the bluetooth sync. Both devices see eachother.....both devices request a pair confirmation wiht the same key...but both are saying paired not connected. Any ideas why this is? I sync with other BT devices from my INC just fine.
So, wireless tether...wont work....works from other devices but not my gtab to my incredible...bluetooth wont connect.
I plan on rooting my gtab tonight when i get home and settled in. Any ideas would be awesome.
Thanks!
wheelerr said:
Hello,
I am brand new to the forums. I have done some poking around but I want to have a threat dedicated to this as Im going to assume a lot of people are going to have this problem.
I just bought my gtablet about 2 hours ago. I havent been able to root it or install any roms yet because I bought it in chicago and I am on my way back home to michigan right now as I type this.
I am trying to see if anyone knows how to get wireless tether to work on the gtablet. I have a rooted incredible running cyanogen 6.0.2 w/ wireless tether. I am connected to my phone right now as I type this on my netbook. I cant get my gtab to see my wireless tether...any ideas or things to try. I cant be the only one thats run into issues.
Secondly, maybe this needs its own thread. I was going to try doing it via bluetooth with the bluetooth sync. Both devices see eachother.....both devices request a pair confirmation wiht the same key...but both are saying paired not connected. Any ideas why this is? I sync with other BT devices from my INC just fine.
So, wireless tether...wont work....works from other devices but not my gtab to my incredible...bluetooth wont connect.
I plan on rooting my gtab tonight when i get home and settled in. Any ideas would be awesome.
Thanks!
Click to expand...
Click to collapse
i use wireless tether for my gtablet from my rooted incredible but i have heard others say they cannot get it to work. i am using the wireless tether that is installed on redemptive revolution 2.1.2
Your problem is what i ran into, ad-hoc networks vs infastructure. I am able to switch my gtablet back and forth using the information i found here: h ttp://www.slatedroid.com/pandigital-novel-android-tablet-discussion/4505-i-have-infrastructure-adhoc-working-same-time-do-you-want-look-here.html
Its not just layed out perfectly for you but the main idea is to edit wpa_supplicant.conf to look for ad-hoc. The link has a apk that lets you go from your current settings to a tethered setting then back again. The link is the only reason I figured it out and is the easiest way i found so far. Sorry I dont have time to lay out a straight forward guide for the gtablet right now but being I novice I was able to get it using the link.
hmm, mine works with no modifications.
Crimton said:
hmm, mine works with no modifications.
Click to expand...
Click to collapse
Not mine, but I will hold off with any more mods until a new TnT rom is released. Even with Titanium, getting the device back to par is getting old. Not even fooling with the openGL patch, since my luck will be boot loops and a forced reset of the rom.
Crimton said:
hmm, mine works with no modifications.
Click to expand...
Click to collapse
Some phones can tether using infrastructure setup but mine (droid1) and many others can only create ad-hoc networks to tether. From what I have read android can only connect to wireless infrastructure not ad-hoc without going through the steps in the link. I may be way off on this and would love to be wrong since the hack is kind of a pain to implement but its the only thing that has worked for me.
Wifi tether working for me now!
Apparently the version I had and the one in the market are not a fit for my device. A kind soul from a "rival" land pointed me to a version that does work.
Thanks!
I appreciate wifi tether (faster than expected), but we would save some serious battery power for both devices if USB tether was available
rushless said:
Wifi tether working for me now!
Apparently the version I had and the one in the market are not a fit for my device. A kind soul from a "rival" land pointed me to a version that does work.
Thanks!
I appreciate wifi tether (faster than expected), but we would save some serious battery power for both devices if USB tether was available
Click to expand...
Click to collapse
what phone and app do you have if you dont mind me asking, I have tried several tethering apps with my droid 1 and haven't had any luck.
wlawyer said:
what phone and app do you have if you dont mind me asking, I have tried several tethering apps with my droid 1 and haven't had any luck.
Click to expand...
Click to collapse
Sent a PM, since not sure I can link it here.
Phone is the Incredible.
UPDATE:
The wifitether app worked fine with TNT 1.03, but does not work with Tnt 2.0- device not seen, just like BEFORE I got this app. This issue is getting old quickly.
UPDATE 2:
Now it works... not understanding this at all. I need beer.
I have searched these forums and the net but can not find an easy solution to get the adhoc wifi of the Droid 1 to be seen by the Gtablet. In my searching I found where file wpa_supplicant.conf was to be edited and it fixed the problem (it was very involved). But I remember reading some place that had the file edited that you could just back up the original and copy the new over. Does anyone know where this updated file might be or a fix for someone like me that does not feel comfortable editing files?
I'll admit it... I'm looking for a noob way to fix this problem.
Hey there need help. I have a friend that just rooted his phone and is using wireless tether, but His computer won't recognise the phone as WiFi. What should he check for or fix?
Sent from my PC36100 using XDA App
mmracing said:
I have searched these forums and the net but can not find an easy solution to get the adhoc wifi of the Droid 1 to be seen by the Gtablet. In my searching I found where file wpa_supplicant.conf was to be edited and it fixed the problem (it was very involved).
Click to expand...
Click to collapse
I have tried everything I have read, and I still can not get my G Tablet to see my Droid 1. I have tried both Barnacle WiFi Tether and Wireless Tether. Both my G Tablet and my Droid 1 are rooted. My iPod Touch works with my Droid 1, so I don't think the Droid is the problem.
tnt2gamer said:
I have tried everything I have read, and I still can not get my G Tablet to see my Droid 1. I have tried both Barnacle WiFi Tether and Wireless Tether. Both my G Tablet and my Droid 1 are rooted. My iPod Touch works with my Droid 1, so I don't think the Droid is the problem.
Click to expand...
Click to collapse
There has to be a way to do it. I thought I read somewhere how to do it but I just can't find it. I have had my Gtablet from the day they went on sale at Sears and have looked at 1000's of post then I decided it was time to root both devices to use the wifi... only to find out the adhoc from the Droid 1 wouldn't work. BAH!
mmracing said:
There has to be a way to do it. I thought I read somewhere how to do it but I just can't find it. I have had my Gtablet from the day they went on sale at Sears and have looked at 1000's of post then I decided it was time to root both devices to use the wifi... only to find out the adhoc from the Droid 1 wouldn't work. BAH!
Click to expand...
Click to collapse
It does work, but not sure it does on all flavors of firmware as I had it set up just not sure which firmware I was testing on at the time... I did have problems with Original TNT stock firmware... same files I was trying worked on not sure whether early CM or Ztab... but on original TNT it looked like a wpa_supplicant bug as was definitiely seeing the conf file but wouldn't find anything with the scan... so came back with error like the original tablet I had to return did for any Infrastructure scan... I'm bouncing between both my Gtabs running diff firmware on each so easy to get confused at times... What version are you running and I'll try to give it a go tomorrow...
Stock GTab, rooted with market....
Flashed with clockworkmod from one of the threads here a file called wpa_adhoc-signed.zip and it worked.
Tethered to my Droid 1 to test...
I see my infrastructure AP and my adhoc "AP" but with a (*) in front of the name.
added the file I used..
Sent from my UPC300-2.2 using Tapatalk
jtbnet said:
What version are you running and I'll try to give it a go tomorrow...
Click to expand...
Click to collapse
I am also running the original G Tablet firmware, with the TNT 2967 update that was pushed to it on 22-Nov-2010.
UPDATE: I realized last night that my files were not being overwritten with the modified ones, even though I was telling Root Explorer to replace the existing ones. I will delete the old wpa_supplicant.conf file before copying the modified version next time, to see if it makes a difference. Right now I am restoring everything that I had on the GTab little by little after frying my wifi settings last night. I couldn't get it working, so I did a factory reset and lost everything.
ANOTHER UPDATE: Yep. That was my problem. My modified wpa_supplicant.conf file was not replacing the original one. Once I deleted the old one manually, and copied the modified one in its place, it worked. I can now tether to my original Motorola Droid. I am using a program called AdhocAble to switch easily between two different wpa_supplicant.conf files (one for adhoc, and another for infrastructure).
MORE INFO: The problem I am having now is that my wireless quits working after each reboot. I have to change the file permissions on wpa_supplicant.conf to allow read-write for Other. Once I do this, the wireless starts working again. I even tried changing onwership of the wpa_supplicant.conf file to system.wifi, but that stopped AdhocAble from being able to change between adhoc and normal modes. I will probably try that patched supplicant binary soon.
FINAL UPDATE: Wow. wpa_adhoc-signed.zip worked for me, too. My Droid 1 is showing up with an asterisk beside it in my wifi list. This is the best fix yet. Yahoo! Thanks tcrews for posting this one.
tcrews said:
Stock GTab, rooted with market....
Flashed with clockworkmod from one of the threads here a file called wpa_adhoc-signed.zip and it worked.
Tethered to my Droid 1 to test...
I see my infrastructure AP and my adhoc "AP" but with a (*) in front of the name.
Sent from my UPC300-2.2 using Tapatalk
Click to expand...
Click to collapse
THANX... I'll give this a try as after having gone through this on multiple tablets multiple times this smelled of a wpa_supplicant bug on TNT!
Rooted stock Gtablet firmware, with the TNT 2967 update that was pushed to it on 22-Nov-2010.
I have not tried any different ROMs.
mmracing said:
Rooted stock Gtablet firmware, with the TNT 2967 update that was pushed to it on 22-Nov-2010.
I have not tried any different ROMs.
Click to expand...
Click to collapse
Well basic TNT is what I originally had problems with... I'll try the supplicant patch hopefully tomorrow...
tcrews said:
Stock GTab, rooted with market....
Flashed with clockworkmod from one of the threads here a file called wpa_adhoc-signed.zip and it worked.
Tethered to my Droid 1 to test...
I see my infrastructure AP and my adhoc "AP" but with a (*) in front of the name.
added the file I used..
Sent from my UPC300-2.2 using Tapatalk
Click to expand...
Click to collapse
+1 for this post. major thanks to the poster. i was having problems with my gtab seeing my droid1 when running wireless tether, and this did the trick. for reference, currently using tnt 2.0.2 (supplemental applied to tnt 2.0.0). now ill be able to take this thing with me on the road this weekend and enjoy it. thanks again!
ps, the file flashed will not show in this quote, so scroll up to that post and grab it if you are in the same boat i was in.
as far as i can work out, all app i tried on x10 make it ad-hoc, and xoom doenst recognize ad-hoc.
so is there any other method that i can tether?
PS: i tried bluetooth tether on pdanet, and it doesnt work on x10
You simply need to download wifitether app.
http://code.google.com/p/android-wifi-tether/downloads/list
to the phone or to xoom?
i dled it on the phone, and it still only makes ad-hoc since kernel doenst support full function.
dl to the xoom? i dont see how it works but i will try........
dota-lina said:
to the phone or to xoom?
i dled it on the phone, and it still only makes ad-hoc since kernel doenst support full function.
dl to the xoom? i dont see how it works but i will try........
Click to expand...
Click to collapse
You need to download it to your phone, but if your phone doesn't support infrastucture mode then it probably won't work.
I think I did read somewhere that X10 will get an Android update soon, this should fix the problem.
I have been using my DHD (android 2.2.1 stock rom) with stock wifi hotspot app as an access point for my Xoom without any problems.
hope so, but i dont think SE will up the kernel with build. the kernel in my x10i was still .29
i have an x10 too and am sad to see bluetooth mode doesn't work
However, devs over in the x10 forum have cracked the bootloader and are working on custom kernel development!
Finally i did it.
Hi guys. Just a heads up for you, last night i was able to tether my x10 with my Xoom, i did not rooted my new Xoom because i just got it and i don´t want to loose my warranty just yet, so i tried to figure it out a way to make the x10 work on the Xoom, and last night i successfuly done this with bluetooth tethering. Works great, i just downloaded J's new CM7.0.3, after instalation i downloaded Wireless Tether from the Market and used Bluetooth functionality.
Since the new Kernel supports Iptables and Netfilter i was able to use it without problems. Any questions post here, i will try to help the best way i can.
If you root the xoom you can make it see ad-hoc networks by switching out the wpa_supplicant file.
Sent from my Xoom using Tapatalk
Yeah Mr_Wrong, i know that, but as i said in my previous post, i just got my Xoom and i don't want to loose my warranty already, that's why i started a battle with my X10 to make it support bluetooth PAN or Infrastructure tethering mode. So i did it without loosing my Xoom warranty.
But just for now anyways, soon or later my Xoom will be rooted, i just think it's too early for that right now.
Hi Guys,
In the last three days I've learned how to root my captivate, side-load apps, installed barnacle and wifi tether, all in the hopes of using my TF while on the road with my Captivate.
Unfortunately I cant get BT or Ad Hoc tethering to work.
I get the paired but not connected error when using BT
My TF is 8.2.3.13 so I can't root (without downgrading to 8.2.3.9 which I'm kind of afraid to do).
Does anyone know if I need to install a custom rom on my captivate in order to get the BT to tether?
I've probably read 100 threads in hopes of getting this to work, but at this point I might have to return the TF and get an ipad (yuck) just to get some connectivity for working on the road.
Any suggestions would be very very appreciated.
Regards,
wunshot
I'm assuming you want to use internet from your phone to tether to the tablet correct? Installing a custom rom is one way of achieving this. I use cognition rom which comes with the ability to tether through wifi. You need to activate that on the phone and have the tablet connect to the phone's wifi network.
I'm not sure if you were doing this but you cannot create an ad hoc network on the tablet and connect the phone to it to tether. The phone has to be the host and the tablet the client.
Sent from my SAMSUNG-SGH-I897 using XDA App
You don't want bluetooth. SirSid is on the right track suggesting the custom ROM although there are other ways that might not be as simple.
You want to turn on Mobile AP (Access Point) which turns your Cappy into a wifi hotspot and you're good to go. Go check the Captivate forums on how to achieve Mobile AP without much trouble. If you try to use it on a stock froyo cappy it will warn you about needing a tethering plan with ATT, you can easily remove the plan check using TiBu and it's all spelled out in the Cappy forums.
wunshot said:
Hi Guys,
In the last three days I've learned how to root my captivate, side-load apps, installed barnacle and wifi tether, all in the hopes of using my TF while on the road with my Captivate.
Unfortunately I cant get BT or Ad Hoc tethering to work.
I get the paired but not connected error when using BT
My TF is 8.2.3.13 so I can't root (without downgrading to 8.2.3.9 which I'm kind of afraid to do).
Does anyone know if I need to install a custom rom on my captivate in order to get the BT to tether?
I've probably read 100 threads in hopes of getting this to work, but at this point I might have to return the TF and get an ipad (yuck) just to get some connectivity for working on the road.
Any suggestions would be very very appreciated.
Regards,
wunshot
Click to expand...
Click to collapse
I use Captivate all the time and I can turn on the mobile hotspot and have my TF connect to it.
Atleast I'm not aware of being able to do BT tethering on a Captivate. I'm interested to know, if its even possible. Lets post a thread on the Captivate forum.
Thanks for the quick response. Yes, i plan on using my phone as the wifi host. I will give that cognition rom a shot. Im assuming the cognition rom creates the wifi network using infrastructure rather than ad hoc...is that the case?
Regards,
Wunshot
wunshot said:
Im assuming the cognition rom creates the wifi network using infrastructure rather than ad hoc...is that the case?
Click to expand...
Click to collapse
Have no idea, I know it just works, it's actually a part of Android since Froyo, it just needs to be enabled and/or not checked if you don't have a tether plan.
I think cognition just uses the defualt android AP app. It creates the network in infrastructure mode if I remember right.
In any case, it just works
(Its located in Settings >> Wireless and network >> Mobile AP)
It supports bluetooth tethering as well, but the tablet would need to recognize it as a bluetooth modem. I have not tried that yet. Using a usb tether would probably be best if it works however. Using wifi tether drains battery faster than than my car charger can charge my phone. I still manage to loose battery even when its plugged in.
Sweet...I'll install cognition when I get home and see where I stand. Thanks for the advice...I'll updater you in a few hours with my results
OP, I have a rooted cappy with firefly rom on it. Super easy to do and its stable and allows for wifi hot spot without stupid ATT finding out you are tethering.
http://www phoenix-hq com/firefly/
It is a legit stable rom. I am able to wifi tether easily with my TF, no problems.
I'm on a stock froyo captivate Mobile AP works fine for tethering, can't figure out bluetooth. I tried for a couple of hours but gave it up Mobile AP works great, although I hear bluetooth saves battery?
EDIT: sorry it's a rogers captivate, i believe US is still on 2.1 nvm!
wunshot said:
Thanks for the quick response. Yes, i plan on using my phone as the wifi host. I will give that cognition rom a shot. Im assuming the cognition rom creates the wifi network using infrastructure rather than ad hoc...is that the case?
Regards,
Wunshot
Click to expand...
Click to collapse
I don't understand why your getting into the Ad-hoc thing. Any rooted ROM you install on the Captivate, you can make your phone a Wifi hotspot via Mobile AP settings. That would create a Wifi network from the phone, and you can connect to that network in the TF.
wunshot said:
Hi Guys,
In the last three days I've learned how to root my captivate, side-load apps, installed barnacle and wifi tether, all in the hopes of using my TF while on the road with my Captivate.
Unfortunately I cant get BT or Ad Hoc tethering to work.
I get the paired but not connected error when using BT
My TF is 8.2.3.13 so I can't root (without downgrading to 8.2.3.9 which I'm kind of afraid to do).
Does anyone know if I need to install a custom rom on my captivate in order to get the BT to tether?
I've probably read 100 threads in hopes of getting this to work, but at this point I might have to return the TF and get an ipad (yuck) just to get some connectivity for working on the road.
Any suggestions would be very very appreciated.
Regards,
wunshot
Click to expand...
Click to collapse
I tested my Capativate with CyanogenMod 7 rom. It has "Tethering & portable hotspot" feature built-in. I tried it on my friend's TF yesterday and it actually works great!!!
I put cognition on my phone and it worked like a charm.....thanks!
for some reason my GT-P6210 doesnt pick my cell phones wi fi hot spot... my ipad picks up the cell wifi hot spot wit zero issue.... any suggestions?
I am sure you tried it already, but you may want to turn the wifi off and then back on, and/or reboot your device.
P_
Yea tried that that....
The 7+ can't connect to ad-hoc hotspots...
If you're phone is running an ad-hoc hotspot instead of infrastructure, you won't be able to tether to it.
AKA... Samsung/Atheros sucks.
thanx... I tried a different app and that solved the issue
I am having the same problem, so would really appreciate it if you let us know which app solved the problem. Thanks in advance
barleystubble said:
I am having the same problem, so would really appreciate it if you let us know which app solved the problem. Thanks in advance
Click to expand...
Click to collapse
https://market.android.com/details?id=com.wifi.hotspot
I'm using Wireless Tether 2.0.5-pre9 on my rooted Evo 4g. I'm using the pre9 version because there was talk on an evo root forum about other versions not working.
Sent from my GT-P6210 using Tapatalk
Needs a modified wpa_supplicant file
The GT 70+ needs a modified wpa_supplicant to allow it to see adhoc WiFi networks. The reason slyd0997 was able to get tethering to work was because they are using an EVO 4G phone and that phones WiFi hotspot is infastructure and not adhoc. Until a modified wpa_supplicant file is made available for this tab (I would do it myself but have no idea how too), tethering to a WiFi hotspot on a phone that is adhoc and not infastructure is out of the question. Modified wpa_supplicant files are available for other tablets (eg: Motorola Xoom) so we know it can be done. Is there anyone with the knowledge and access to a GT 7.0+ that would like to take this challenge on? I know that there would be a community of very gratefull GT 7.0+ users who would be forever in your debt and would name their first born child after you if you could do this. Okay, Okay...you might have to settle for just gratefull......
USCanthony said:
The GT 70+ needs a modified wpa_supplicant to allow it to see adhoc WiFi networks. The reason slyd0997 was able to get tethering to work was because they are using an EVO 4G phone and that phones WiFi hotspot is infastructure and not adhoc. Until a modified wpa_supplicant file is made available for this tab (I would do it myself but have no idea how too), tethering to a WiFi hotspot on a phone that is adhoc and not infastructure is out of the question. Modified wpa_supplicant files are available for other tablets (eg: Motorola Xoom) so we know it can be done. Is there anyone with the knowledge and access to a GT 7.0+ that would like to take this challenge on? I know that there would be a community of very gratefull GT 7.0+ users who would be forever in your debt and would name their first born child after you if you could do this. Okay, Okay...you might have to settle for just gratefull......
Click to expand...
Click to collapse
Not likely to happen - after chatting with garyd9, it sounds like Samsung put some Atheros-specific customizations into wpa_supplicant and is not releasing the source for these modifications (they're playing games with the dual-license nature of this item). So a standard wpa_supplicant likely won't work.
you can tether to your phone to your tab via bluetooth...it works using my mopho
I use this, it works great on my SII.
http://code.google.com/p/android-wifi-tether/downloads/list
Hello!
As my title states, I'm looking for a ROM that supports T-Mobile Wifi calling!
I do not enjoy the stock ROM and prefer ICS+
I flashed [ROM]CM 9.1 + bat drain fix + other tweaks Although I had working Wifi calling, my data reception was very SLOW. Slow enough for me to type that in all caps.
I flashed [ROM]MikXE-v0.4 and enjoyed the fast performance and working data, but Wifi calling wasn't present.
From what I have read, Wifi calling requires a few things in the Kernel in addition to the Wifi calling APK.
Anyone have recommendations for an ICS ROM (sense or no sense) that is stable, has no data issues and has working T-Mobile Wifi calling?
Cheers!
Give Virtuous Inquisition a try. You can find it on Rootz.
Hastily spouted for your befuddlement
Coug76 said:
Give Virtuous Inquisition a try. You can find it on Rootz.
Click to expand...
Click to collapse
Seeing people say good things about it after a quick google.
Downloading now!
Is TMobile wifi calling just some app APK that can be installed? (Already looked and didn't find it on Google Play.) If yes, is it available somewhere or can it be pulled from a ROM that has it?
Check weekendsR2short's mirror thread
wjcarpenter said:
Is TMobile wifi calling just some app APK that can be installed? (Already looked and didn't find it on Google Play.) If yes, is it available somewhere or can it be pulled from a ROM that has it?
Click to expand...
Click to collapse
I think its a bit more in depth than that. edkeys did some nice work on it for the g2/dz. not sure what needs to be done to the doubleshot to get it working right but this is what works for the vision:
http://forum.xda-developers.com/showthread.php?p=26336049
Sent from my HTC Vision using xda premium
demkantor said:
I think its a bit more in depth than that. edkeys did some nice work on it for the g2/dz. not sure what needs to be done to the doubleshot to get it working right but this is what works for the vision:
http://forum.xda-developers.com/showthread.php?p=26336049
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
WiFi calling already works for this device there is a flashable zip that has the apk for it + some RILs. Then you need the gan optimizer apk pushed to system/apps. WiFi calling works great!!!
While living in China I found that the Sidecar app actually worked better than the built-in WiFi Calling did on my phone. Better call quality, and all calls to US/Canada numbers are free for now. Sidecar now has the capability of using mobile data if you want and have it, but that can be turned off and make it WiFi only.
Fuzi0719 said:
While living in China I found that the Sidecar app actually worked better than the built-in WiFi Calling did on my phone. Better call quality, and all calls to US/Canada numbers are free for now. Sidecar now has the capability of using mobile data if you want and have it, but that can be turned off and make it WiFi only.
Click to expand...
Click to collapse
I definitely need to find time to look at this.
Stock wifi calling is a cancer slowly murdering the end-user perception of this devices capabilities.
One of the things I was working on for Bulletproof was a patch to remove wifi calling from an already installed copy of it. What a nightmare that was, for as far as I got anyway. Still lacking in sufficient diagnosis.
The difference in performance and responsiveness in my rom with stock wifi calling and with that removed as the only change to the install is - to put mildly - is observable just through using it, without a benchmarking app.
It's not something i'd ever use anyway - so I see all that extra load as needless waste instead of a sacrifice for something I want. Conversely that means i'll never find a replacement unless someone brings it to my attention.
Can't say when i'll get a chance to look at it, but it's infinitely more likely to happen sooner then later with a lead to go on.
Whenever I sit down with the time to go learn about something I know nothing about (directly) - such as wifi calling - it inevitably loses out to something like starting on the aosp site and reading every snippet on bluetooth before branching out to other sources for info on how it works in android.
Having a reference point places it in a different category entirely - thanks!
Blue6IX said:
I definitely need to find time to look at this.
Stock wifi calling is a cancer slowly murdering the end-user perception of this devices capabilities.
...
It's not something i'd ever use anyway - so I see all that extra load as needless waste instead of a sacrifice for something I want. Conversely that means i'll never find a replacement unless someone brings it to my attention.
...
Having a reference point places it in a different category entirely - thanks!
Click to expand...
Click to collapse
For me it's a bit of the opposite. I stick with T-mobile for two reasons.
GSM - BYOD portability and upgrades when I want.
WiFi Calling - I seem to work and live in low signal areas. WiFi calling is a Godsend, keeping me connected without switching to more restrictive carriers.
If the official app is such a system hog, I'm fine with it being left out as an option. But I either want it in a ROM, available to install, or a viable replacement must be available.
GoPadge said:
For me it's a bit of the opposite. I stick with T-mobile for two reasons.
GSM - BYOD portability and upgrades when I want.
WiFi Calling - I seem to work and live in low signal areas. WiFi calling is a Godsend, keeping me connected without switching to more restrictive carriers.
If the official app is such a system hog, I'm fine with it being left out as an option. But I either want it in a ROM, available to install, or a viable replacement must be available.
Click to expand...
Click to collapse
I was the same way, when I live in China I need the WiFi calling in order to stay in contact with friends and family back home. But, as I discovered, that Sidecar app that is freely available in the Play Store has better call quality than the built-in WiFi Calling on my stock-based ROM. I compared the two and ended up using Sidecar all the time. Now, the Sidecar app can only receive calls from other Sidecar users, that's the only drawback to it versus WiFi Calling.
WildChildIcE last nightly has it & it seems to work fine although I don't use it all the time. It may be worth checking out since everything else in the ROM seems to be just fine.
Another thing that I find pretty cool is grooVe IP from the market. It connects to Google Voice and uses your G Voice number for free incoming and outgoing voice calls to any number in the US and Canada, using mobile data or wifi. Works great, I've been using it on an Android that I have that has no service at all on it, except wifi. The only single drawback i've found so far is there is maybe a 2 second delay when I've used it, so I've had to wait for the person to hear what I said. All in all tho I find it great for a completely free service(well, there is a paid and free version of the app).
Sorry, I liked this app so I had to throw it in here. I might check out Sidecar as well
GoPadge said:
For me it's a bit of the opposite. I stick with T-mobile for two reasons.
GSM - BYOD portability and upgrades when I want.
WiFi Calling - I seem to work and live in low signal areas. WiFi calling is a Godsend, keeping me connected without switching to more restrictive carriers.
If the official app is such a system hog, I'm fine with it being left out as an option. But I either want it in a ROM, available to install, or a viable replacement must be available.
Click to expand...
Click to collapse
I agree wholeheartedly with number 2. I work in a building where nobody using any carrier gets cellphone signal for whatever reason. That is, nobody except for me because of wifi calling on T-Mobile. This device is first and foremost a phone and it needs to be able to make phone calls and if that means a little lag on some silly game being played on the phone or whatever then so be it.
Sent from my myTouch_4G_Slide using xda premium
IrefulSoul said:
Hello!
As my title states, I'm looking for a ROM that supports T-Mobile Wifi calling!
I do not enjoy the stock ROM and prefer ICS+
I flashed [ROM]CM 9.1 + bat drain fix + other tweaks Although I had working Wifi calling, my data reception was very SLOW. Slow enough for me to type that in all caps.
I flashed [ROM]MikXE-v0.4 and enjoyed the fast performance and working data, but Wifi calling wasn't present.
From what I have read, Wifi calling requires a few things in the Kernel in addition to the Wifi calling APK.
Anyone have recommendations for an ICS ROM (sense or no sense) that is stable, has no data issues and has working T-Mobile Wifi calling?
Cheers!
Click to expand...
Click to collapse
The CM 9.1 ROM you mentioned has the 2G data speed enabled by default to conserve battery. Did you uncheck this? I believe its the only ROM I've ever tried that came that way out of the box. Options > More > Mobile Networks > Use only 2g (uncheck).
Inquisition works well with the right T-Mobile wifi calling package applied (WifiCallingICSAOSP.zip), but it doesn't appear to have as much customization built in (I can't find how to edit the lock screen for example).
I have not had luck installing Infinity and pairing it with a working Wifi Calling package. Supposedly other have, but I can't get a straight answer for the last few weeks when I've tried to find out - even in their IRC channel. On my G2 however, Infinity worked great with WiFi calling, so my guess is that I've just not run across the right package to install.
I'd like to use a Virtuous ROM primarily, because I've been a long time user of Virtuous ROMs (third device now I've followed them). Inquisition seems the most complete, meaning it is the only ICS ROM I've tried where everything worked, including the little LED's for the caps and special keys. The development for this particular device just doesn't seem high on the radar though, and the community around Virtuous has nearly completely died out.
Beyond that, I've not tried any other ROM's for my MT4GS. I'm in a similar boat though apparently, I require WiFi calling, and I want ICS or Jelly Bean.
pyro9219 said:
The CM 9.1 ROM you mentioned has the 2G data speed enabled by default to conserve battery. Did you uncheck this? I believe its the only ROM I've ever tried that came that way out of the box. Options > More > Mobile Networks > Use only 2g (uncheck).
Inquisition works well with the right T-Mobile wifi calling package applied (WifiCallingICSAOSP.zip), but it doesn't appear to have as much customization built in (I can't find how to edit the lock screen for example).
I have not had luck installing Infinity and pairing it with a working Wifi Calling package. Supposedly other have, but I can't get a straight answer for the last few weeks when I've tried to find out - even in their IRC channel. On my G2 however, Infinity worked great with WiFi calling, so my guess is that I've just not run across the right package to install.
I'd like to use a Virtuous ROM primarily, because I've been a long time user of Virtuous ROMs (third device now I've followed them). Inquisition seems the most complete, meaning it is the only ICS ROM I've tried where everything worked, including the little LED's for the caps and special keys. The development for this particular device just doesn't seem high on the radar though, and the community around Virtuous has nearly completely died out.
Beyond that, I've not tried any other ROM's for my MT4GS. I'm in a similar boat though apparently, I require WiFi calling, and I want ICS or Jelly Bean.
Click to expand...
Click to collapse
use the same wifi calling zip you mentioned. go to the mirror thread download the gan optimizer.apk use root explorer to push to system/apps then set permissions and you are good to go. i have used on infinity for a while.
pyro9219 said:
The CM 9.1 ROM you mentioned has the 2G data speed enabled by default to conserve battery. Did you uncheck this? I believe its the only ROM I've ever tried that came that way out of the box. Options > More > Mobile Networks > Use only 2g (uncheck). .
Click to expand...
Click to collapse
You know, I remember seeing H indicators on my signal meter and trying unsuccessfully to look for new towers (Mobile Networks-=>Network operators).
I have flashed again and see "Use only 2G Networks" checked. Even though that was checked, my phone indicated H in my Downtown Area.
pyro9219 said:
Inquisition works well with the right T-Mobile wifi calling package applied (WifiCallingICSAOSP.zip), but it doesn't appear to have as much customization built in (I can't find how to edit the lock screen for example).
I have not had luck installing Infinity and pairing it with a working Wifi Calling package. Supposedly other have, but I can't get a straight answer for the last few weeks when I've tried to find out - even in their IRC channel. On my G2 however, Infinity worked great with WiFi calling, so my guess is that I've just not run across the right package to install.
I'd like to use a Virtuous ROM primarily, because I've been a long time user of Virtuous ROMs (third device now I've followed them). Inquisition seems the most complete, meaning it is the only ICS ROM I've tried where everything worked, including the little LED's for the caps and special keys. The development for this particular device just doesn't seem high on the radar though, and the community around Virtuous has nearly completely died out.
Beyond that, I've not tried any other ROM's for my MT4GS. I'm in a similar boat though apparently, I require WiFi calling, and I want ICS or Jelly Bean.
Click to expand...
Click to collapse
I just came from Virtuous Inquisition after reading the forum on Roots.
I ran the ROM for a bit, and Wifi calling kept dropping or staying quiet.
On 2-3 days with the ROM, I tried flashing WifiCallingICSAOSP.zip, and on reboot, Wifi calling would crash.
Was I supposed to do anything special to flash that WifiCallingAOSP package?
Now I'm on CM9.1 + Fixes with the WifiCallingAOSP package, and when I pick up the phone to answer, my phone defaults to speaker. It requires a double toggle of speakerphone mode during calls to get to handset.
IrefulSoul said:
Now I'm on CM9.1 + Fixes with the WifiCallingAOSP package, and when I pick up the phone to answer, my phone defaults to speaker. It requires a double toggle of speakerphone mode during calls to get to handset.
Click to expand...
Click to collapse
I have the same issue. I've kinda just grown used it.
---------- Post added at 06:16 PM ---------- Previous post was at 06:12 PM ----------
mattlowry said:
use the same wifi calling zip you mentioned. go to the mirror thread download the gan optimizer.apk use root explorer to push to system/apps then set permissions and you are good to go. i have used on infinity for a while.
Click to expand...
Click to collapse
The problem I have is that it keeps telling me "Reading SIM" in the wifi calling app, its not that typically "drops calls" problem I see most people with. When I try to toggle the mode on/off, it says "Calling Preferences can not be changed as the SIM is invalid" I even went into T-Mobile and swapped out my two year old SIM card for a new one.
EDIT: just tried Infinity 1.35 with the path and gan optimizer.. same thing..
IrefulSoul said:
I just came from Virtuous Inquisition after reading the forum on Roots.
I ran the ROM for a bit, and Wifi calling kept dropping or staying quiet.
On 2-3 days with the ROM, I tried flashing WifiCallingICSAOSP.zip, and on reboot, Wifi calling would crash.
Was I supposed to do anything special to flash that WifiCallingAOSP package?
Click to expand...
Click to collapse
I have not stayed on Inquisition for any grand length of time, but the few times I've had it on my phone it worked out well using WiFi calling.
I'm personally hoping that Jelly Bean re-inspires the developers for this phone to give us some great things. I'd imagine they kinda lost steam after so much fighting with ICS.
Wicked ROM supports WiFi Calling.