yashsingh1/xdaforums huggingface dataset:
[HTC Sensation] Darnell_Chat_TN:
This flashable patch has the following in its build.prop in that section.

rild.libpath=/system/lib/libhtc_ril.so
# RilLibPath for Ganlite by Godel_Chen
rild.libpath.ganlite=/system/lib/librilswitch.so
rilswitch.vendorlibpath=/system/lib/libhtc_ril.so
rilswitch.ganlibpath=/system/lib/libganril.so

I'm using EnergyROM which has the following in its build.prop and people who use this patch having removed the build.prop, so they keep EnergyROM's customized build.prop say WiFi calling won't work.

rild.libpath=/system/lib/libhtc_ril.so
# RilLibPath for Ganlite by Godel_Chen
rild.libpath.ganlite=/system/lib/librilswitch.so
rilswitch.vendorlibpath=/system/lib/libhtc_ril.so
rilswitch.ganlibpath=/system/lib/libganril.so

Same thing, but neither has the value as you mentioned, each has it slightly different.

But people using EnergyROM say this patch works if they use all of its included build.prop values. So I can't figure out what could be causing the issue. I do know that EnergyROM's build.prop makes no mention of "tmobile" anywhere in it. While the build.prop in the patch has a lot of mentions of "tmobile" in various places. Could the issue be mentions of "tmobile" in some areas of the file?
[HTC Sensation] jahmezis45:
How can I raise volume on wifi calling outgoing volume too low!
[HTC Sensation] xboarder56:
so can people confirm does this work on android revolution hd 3.0.4 or not
[HTC Sensation] xboarder56:
patch updated to v1.0.1 :D fixed a bunch of issues

Version - 1.0.1

- Fixed low mic (please report)

- Updated build.prop (mike1986.)

- Updated t-mobile wifi calling app

- T-mobile wifi calling app pushed to /data/app for easy uninstall

- Updated install script to fix some install issues

tested version 1.0.1 on both android revolution hd 3.0.4 and energy september 5 and both work :D so enjoy
[HTC Sensation] Darnell_Chat_TN:
Thank you for testing with EnergyROM.

Since you use a different build.prop from EnergyROM and have many tweaks in build.prop for Android Revolution HD. Is is possible/likely that some EnergyROM tweaks are lost when this patch is used with EnergyROM?
[HTC Sensation] xboarder56:
I dont think so but only really tested to see if wifi calling works and that anything didnt force close... But it shouldnt mess up anything in Energy Rom except maybe screenshot if he emplanted that feature in his new update
[HTC Sensation] Darnell_Chat_TN:
Yes, I think he did, because the EnergyROM build.prop includes:

ro.htc.framework.screencapture = true

Yours has that value set to false.

So setting it to "true" in yours would yeild the same effect right?

I don't know much about this, but just figuring that's the case from the differences I saw in the files.
[HTC Sensation] xboarder56:
ya just change to true and you have screenshot back :D enjoy
[HTC Sensation] Darnell_Chat_TN:
Great!

I had another question about build.prop if you could enlighten me :D .

If a build.prop file happend to have

ro.htc.framework.screencapture = true

and later in that same build.prop file it had:

ro.htc.framework.screencapture = false

Would Android recognize the last mention of it and set the feature to false or would it only recognize the first mention and set it to true?

Thank you again :) .
[HTC Sensation] xboarder56:
not sure havnt tested that one yet but i think it would reconize the flase most likly
[HTC Sensation] Darnell_Chat_TN:
OK. Just wondering. I figured maybe the last value too.

Some EnergyROM users were copy/pasting all of EnergyROM's build.prop into yours and it all worked. So I guess they got the EnergyROM values plus any new stuff yours had.

Did you know your build.prop has this in it:

(Lines 180-181)

ro.setupwizard.mode=DISABLED
ro.setupwizard.mode=OPTIONAL

Like first it's disabled and then optional :) .
[HTC Sensation] xboarder56:
ya its not my build.prop is arhd's 3.0.4 build.prop but i use mike1986 while i work on aosp so thats manliy why i made it but works on all roms
[HTC Sensation] Darnell_Chat_TN:
A build.prop with some more EnergyROM friendly values

Based on our discussions and what I've found in the EnergyROM build.prop versus the one for this patch. Along with some researching into the purpose and use of the values for ones I could find details about. I've constructed a build.prop that is my effort to retain the benefits of the build.prop provided with the patch and also include some additions that are usually found in EnergyROM.

I've attached it as a zip file, BUT THIS IS NOT A FILE YOU SHOULD ATTEMPT TO FLASH ON VIA RECOVERY! I have not tried flashing it and don't know enough about making flashable zip files to even make one with any kind of certainty. What I did is took the build.prop that is in the attached zip file and placed it in the zip file provided with this patch in its "system" folder. Basically, I replaced the build.prop provided in the patch with the one I've attached and then flashed that modified patch zip file.

(***Use at your own risk***)

I'm using it and things are just fine. But I'm not buying anybody a Sensation if you use this and claim it broke yours. You assume all liability if you use this.

Below is a detailed list of changes I made to the WiFi Calling Patch build.prop to make it even more EnergyROM friendly.

[B]Changed:[/B]
From: dalvik.vm.heapsize=32m
TO: dalvik.vm.heapsize=36m

From: wifi.supplicant_scan_interval=120
To: wifi.supplicant_scan_interval=150
[I](saves battery life by looking less often for WiFi connections)[/I]

From: ro.htc.framework.screencapture = false
To: ro.htc.framework.screencapture = true
[I](enables the screen capture feature)[/I]

From: windowsmgr.max_events_per_sec=150
To: windowsmgr.max_events_per_sec=178
[I](Increases scrolling speed through lists)[/I]

[I](The next 3 below are just some ringtone adjustments.)[/I]
From: ro.config.ringtone=QuietlyBrilliant.mp3
To: ro.config.ringtone=Glass.mp3

From: ro.config.notification_sound=Zeta.mp3
To: ro.config.notification_sound=Alpha.mp3

From: ro.config.msg_notification=Gamma.mp3
To: ro.config.msg_notification=Alpha.mp3

[B]Added:[/B]
persist.service.adb.enable=1

ro.telephony.call_ring.delay=10
[I](speeds up ring when dialing out)[/I]

[B]Removed:[/B]
ro.setupwizard.mode=OPTIONAL

[B]Not changed:[/B]
[I](*Really nothing else is changed, but I just wanted to point out these two, for anyone who may desire different values for these. So you know about them and you can edit them yourself as you desire.*)[/I]
Wifi Patch has: net.bt.name=Android
EnergyROM has: net.bt.name=Energy

Wifi Patch has: 1.45.401.2
EnergyROM has: 09.05.2011
[HTC Sensation] zdentist:
---------- Post added at 03:19 PM ---------- Previous post was at 03:17 PM ----------

[/COLOR]

Thanks for the great job.
[HTC Sensation] nabzilla1990:
is this working on sense 3.5
[HTC Sensation] gururise:
Any way to update this patch for the new 2.3.5 based ROMS? It seems most of the devs are using the 2.3.4 based wifi calling libs and its causing problems on the newer 2.3.5 based sense 3.5 roms.

Specifically random crashes of the KINETO library/wifi calling app in the middle of a call.
[HTC Sensation] xboarder56:
ill look into it man :D
[HTC Sensation] alucardunit1:
Hey i am using insert coin and i have the crashing issue and i tried patching it and now just crashes
[HTC Sensation] jahmezis45:
can we get this to work on 2.3.5 because my wifi calling keeps dropping or people complaining about volume or clarity
[HTC Sensation] gururise:
Thanks! Looking forward to being able to use WiFi calling on 2.3.5 ROMS w/o Force Closing! :)
[HTC Sensation] MESALLEM:
any update on the sense 3.5 patch??
[HTC Sensation] bahurd:
+1 on the question.
[HTC Sensation] raul602:
worked great for me on insertcoin, thanks man!
[HTC Sensation] bahurd:
Wifi Calling fix for Sense 3.5 roms?

Well, I can't seem to find the file link again but... the name of the file is:

WIFICALLING_CdT v1.7.0.zip

I'm on InsertCoin 3.4.0 and have been on wifi calling pretty much all morning without any FC or dropped calls.

If search doesn't work try to PM me.
[HTC Sensation] gururise:
Did you get this file off XDA? A google search turns up nothing. Is it really a working wifi calling patch for 2.3.5 based roms?
[HTC Sensation] psychedelicx:
Looks like there is another version by dwsmith here as well:

http://xdaforums.com/showpost.php?p=18452432&postcount=3472
[HTC Sensation] tibere86:
Will v1.0.1 work with AOSP ROMs (Cyanogen Mod)? I'm using the stock WIFI Calling app (v1.0) and I suffer from the low mic volume issue.

Edit: Does not work with AOSP ROMs. Caused stuck at boot animation
[HTC Sensation] gururise:
Did either of those patches work for you on a 2.3.5 based ROM?
[HTC Sensation] psychedelicx:
Same issue with the 8.0 version so unfortunately no :(
[HTC Sensation] BACARDILIMON:
http://xdaforums.com/showthread.php?t=1280358&page=83

THIS IS WHAT I HAVE USED IN THE PAST. HAS WORKED GREAT FOR ME. I AM ON CTDROID 2.3.5
[HTC Sensation] bahurd:
Yes, this is the file. I since upgraded to InsertCoin 3.4.1 and reapplied things. Unfortunately, the problem returned today but not sure if it's due to the 3.4.1 or applying the "T-Mobile patch" over things.

May just move back to 3.4.0 for now with only this patch as it worked for me.

UPDATE: Wiped and reflashed InsertCoin 3.4.0 + applied the WIFICALLING_CdT v1.7.0.zip patch in the link above (only, no further patches applied). Have been on 3 WiFi calls this morning without any FC issues. Will try and see how this setup works over the next few days and report back.

Anyone else??
[HTC Sensation] gururise:
So I tried the v1.7 of the posted patch on InsertCoin 3.4.1. I was on a 15 min wifi call yesterday with no FC issues.

I did; however, have to delete wifi calling data (from setting) after first applying the patch.

So far v1.7 seems to have cleared the FC issues. I will keep testing and report back.

EDIT: v1.7 seems to have FC issues in InsertCoin 2.4.3 and above. I'm not sure why. I also tried a newer version v2.1 and still experiencing FC.
[HTC Sensation] bahurd:
Well... I just got dumped off a call after 5 minutes. This Wifi issue on Sense 3.5 is a huge problem for me so I guess I'm heading back to 3.0 for now.

I'll keep checking back (I hadn't cleared after applying the patch though, what made you do that?).
[HTC Sensation] BACARDILIMON:
I have been on the 1.7 and have had calls last up to 2 hours and no dropped call. Well the one flaw i do have is when phone is on standy by it loses wifi then recovers.i doubt that has anything to do with wifi calling patch.
[HTC Sensation] bahurd:
I'm curious, what widget(s) are you using on the home screen? My memory tells me each time I have had FC erros with WiFi calling it is when I have had the 'quick launch' widget for Sense 3.5 on my home screen.

The case where it was stable was when I was using a 'stock' screen with the weather widget (as normal rom the factory). Maybe nothing to it....

WiFi was never an issue in my home when on stock or any other sense 3.0 ROM.

Also, I have 3 routers setup and have had this setup for 2 years (Blackberry UMA prior to HTC).
[HTC Sensation] BACARDILIMON:
i am actually not running any widgets at all. using go launcher and it is not a force close it more of a loss of wifi then it finds the signal and wifi comes back.
[HTC Sensation] knotrkr:
Every ROM I USE It on sense or nonsense it does the same thing. IT SAYS READING SIMS CARD, AND STICKS THERE. ANY FIXES, SORRY ABOUT THE CAPS.. MY KEYBOARD is gunked to all hell..
[HTC Sensation] bahurd:
Huh........?
[HTC Sensation] piimp:
I THINK what he means is that his wificalling won't connect, as it.has to check ur simcard to make sure its active blah blah....so even with this fix its just stuck there...

Sent by my feau gee
[HTC Sensation] bahurd:
Oh. :D

I never had a problem where it just hung forever. Once in a while, when just moving to a new ROM I've had the App sit there for a while trying to initialize then tell me I wasn't 'registered' but a reboot takes care of it.

I'm back to a 3.0 ROM and redid the radio/RIL to stock TMOUS 169RIL/9035.01 Radio and have not had any issues for days now.

Guess I'll need to see a TMOUS phone using sense 3.5 before the ROMS get updated for the US iFi calling?
[HTC Sensation] dadozi:
How to remove patch 1.0.1 on CM7 Hyper Sensation

hi

how to remove patch or get back to working rom again ?? :confused:

Hyper Sensation v1.0
[HTC Sensation] knotrkr:
Works for me... thanks Garrett... Just wondering, any plans to try an AOSP Sensation ICS rom?
[HTC Sensation] Tungst5n:
recently did a full wipe, flashed HyperSensation on and then flashed this patch on in recovery. phone was in bootloop for about an hour and then when I did a battery pull and tried reflashing HyperSensation, I now get errors on the SD card (even after I connected to my laptop to remove the tmo wifi-calling patch) this happened to anyone else??
[HTC Sensation] KAsp3rd:
updated patch is here --> updated patch
[HTC Sensation] joogle:
Hi - I bought an International version of HTC Sensation and installed Android Revolution 3.6.11 as per instructions on this forum, I am T-mobile US customer, my question is how do I get Wifi calling enabled.

I have the UMA feature on my account, I enabled Wifi Calling under Settings > Call, but I don't see minutes go through UMA, how do I setup it so I can use Wifi Calling on T-mobile?

Or do I need to apply this patch, I would appreciate the help, want to get the steps straight before I mess anything up on the phone.

Thank you!
[HTC Sensation] craven667:
wont work in Android Revolution HD™ 6.0.2 but it was on .1 ???
[HTC Sensation] joogle:
Just in case this helps anyone, I applied mike's patch in post 4 on this thread to get wifi calling to work on my t-mobile.

http://xdaforums.com/showthread.php?t=1435743
[HTC Sensation] emanon:
try the patch from casper seems to be working on most rom.
[HTC Sensation] OhioDroid80:
What rom are you on?
[HTC Sensation] danperde:
The trick is that, yes you have wifi calling enabled on your account, BUT you have to go on T-Mobile website and under your account you need to add the "free wifi calling" feature to your account. I know, it doesn't make sense, but if you do not do that, all the minutes used on your wifi calling counts towards your plan minutes. Once you do that, the minutes are free. Or call T-Mobile and tell them that you want the "free wifi calling" on your account.

---------- Post added at 03:12 PM ---------- Previous post was at 03:08 PM ----------

If you are on a ICS rom, then you get that error. I have it once in a while too. The thing is that Wifi Calling is not optimized for ICS, it's just a port from GB. And you'll be experiencing some dropped calls or no sound too. It sucks, I'm relying on the feature too, because T-Mobile coverage has a LOOOOT of holes in it.
[HTC Sensation] PePiTo.:
thank you is working fine with no problems on HTC Sensation 4G :D
[HTC Sensation] kingston73:
In the linked post it says "follow directions", do I just flash this in recovery? And does this new patch work for 2.3.5 roms?

EDIT: answered that myself, its a resounding NO. I'm currently on energy 2.3.5 and this patch froze it on the bootup screen. Maybe I'll try the ctdroid patch next...
[Sony Ericsson XPERIA X10 Mini] jatin007:
Hi anyone help me, m install minicm7 rom nd now m useing anothor rom but my m give wifi mac address in college so wifi work only that mac address and now mac address change. can m change wifi mac address ?
[Sony Ericsson XPERIA X10 Mini] jatin007:
Nobody here to solve problem
[Sony Ericsson XPERIA X10 Mini] dr.norton:
http://xdaforums.com/showthread.php?t=917684

http://blog.thecodecracker.com/hacks/spoof-mac-address-in-android/

if you need more, try to search it with the term "spoof".
[Sony Ericsson XPERIA X10 Mini] dr.norton:
double post, sorry.
[Sony Ericsson XPERIA X10 Mini] jatin007:
Tnx friend
[G2 and Desire Z General] BTTRDYZ:
Just read the U.S is trying to block AT&T from purchasing T-Mo...

http://www.msnbc.msn.com/id/44341803/ns/business-us_business/

lets hope for the best!!!:D
[G2 and Desire Z General] fluxgfx:
For the best... Well let's hope that they can't buy T-Mo... and then let's hope for a judged ordered break down of AT&T.... now that would be awesome! Worst case scenarios... AT&T wins and merges T-Mo... and well look at that everyone PRICES go up to par :)
[G2 and Desire Z General] martonikaj:
Yep we'll see. This doesn't mean the merger is completely stopped, but its a big step in the right direction!
[G2 and Desire Z General] Nospin:
Problem is, DT still doesn't want T-Mobile USA, what will they do?

Hey Google...got a little extra cash?
[G2 and Desire Z General] wesmagyar:
I kinda feel sorry for all those people who jumped ship at the first announcment and are now stuck with verizon...
[G2 and Desire Z General] martonikaj:
Haha good luck. If Google tried to buy T-mo there's no way that would ever go through. We can hope though right?

Well that's their problem. They're pretty stupid to have jumped to Verizon. Especially considering that at that point if the merger did go through, they were looking at at least 18 months before they saw anything real happen to T-Mobile as we know them now.
[G2 and Desire Z General] blanthony:
thank god. I got At&T for 24 hours to get the new iPhone after being with T-Mobile for 8 years or so and thought their service sucked at least in Tampa. T-Mo was much faster and hella cheaper. The iPhone sucks, it's is all hype. Android all the way!
[G2 and Desire Z General] tronmech:
Personally, I would like to see one of the providers that use T-Mobile network buy T-Mobile. Tsimple Mobile? Walmart?

Or maybe US Cellular or other regional player can get bigger?
[G2 and Desire Z General] kaijura:
I can understand the sentiments between the services of T-mo and AT&T, but I'm simply looking at this from a bigger picture.

If passed, this means the USA is going more in the direction most people never wanted it to go. Government intervention between our personal, and business lives when, sometimes, there isn't anything to intervene about -- AT&T and T-mobile are big boys, they might not make the best decisions that all their customers approve of, but for the most part they should be able to settle it themselves amicably.

Next thing you know, this situation paves the road for the government managing industries like a nagging granny.

All in all, this looks good in the immediate focus, but not in the prospective future. Who wants things being held at a stop point?
[G2 and Desire Z General] martonikaj:
I think most people agree that monopolies are generally not a good thing, no matter which end of the political spectrum you're on.
[G2 and Desire Z General] mputtr:
I was originally all for the merger, but after the "changes" and "streamlining" that AT&T has done so far, I think the government is doing the right thing.

As soon as the merger was approved, AT&T goes ahead and "streamlines" their text plan by giving the customers even LESS options. so now you have to either pay 20c per text and 30c per mms OR pay 20 bucks for unlimited.... They claim that the merger would provide better service for the customers and country but they're showing that the merger would make the customers pay more.

I dont know how true this is, but it technically costs AT&T 1 penny to send 5,000 text messages yet, they charge us 20 cent for 1 text message. So after actions like this, I now am completely opposed to the merger and I hope that it will not go through, so I can switch over to Tmobile when my DZ dies.
[G2 and Desire Z General] kaijura:
if it passes, att would have as much of a monopoly over the US cellular market as android has over the smartphone market right now. It's a decent half, but nowhere near close to the legit term.

I just don't feel it is a good thing for government to intervene, that's my gripe over the issue. It denounces the true meaning for consumer/business capitalism we once hoped to live in.

On a side note, I'm not exactly excited about AT&T fees either. It's a mixed feeling, but I don't let my personal anecdotes get into politics.
[G2 and Desire Z General] martonikaj:
It would be a GSM monopoly, and effectively a cell carrier duopoly between AT&T and Verizon. Sprint wouldn't stand a chance if AT&T consumed T-mobile, and they'd either be bought out or disappear as well. Its just not a good thing for consumers in any way. I'm very anti-government intervention, but I really think they did the right thing here.
[G2 and Desire Z General] Nospin:
If it passed than you are looking at a wide variety of possibilities. The death of Sprint and other small carriers, loss of thousands of jobs...

I hate government intervention as well (i'm not a Pastafarian for nothing), but things like this do need to be investigated. Big corporations almost never care about what's in the best interest of the consumer, and mergers that radically change the landscape like this need to be examined.

AT&T didn't try to do this for the greater good, they did it to line their pockets and have more customers to screw over. They would have had too much influence in the wireless market.
[G2 and Desire Z General] tep065:
on NPR, they said AT&T promised that it would move 5000 call center jobs back to the US, and NO T-Mobile call center people would loose their jobs. I'm not a fan of AT&T and would prolly switch to Sprint once the merger happens. BUT, wouldn't AT&T have to honor all the current contracts at those rates and services and grandfather them for renewal? So if your T-Mo now, you would be able to stay at your current plan indefinitely? It would just effect new customers..no? Plus i've an upgrade available and have been eyeballing the Ruby :) So would rather not have to switch carriers.
[G2 and Desire Z General] G2toVibrant2.2:
Lol I live I'm Tampa but my service is great
[G2 and Desire Z General] mputtr:
technically yes.

but here's how they usually change it on you. You are welcome to continue with your plan, but if you ever upgrade with AT&T into a 2 year contract for a new phone, you MUST go by their plan, in which case considering that AT&T will probably not change their infrastructure anyways, you would NEED a new phone because tmo uses a completley different set of spectrums and methods than AT&T (1 spectrum for uploads, 1 for downloads as opposed to AT&T's 1 spectrum for up and down).

Your current tmobile phone will not get 3g at all.

so essentially you'll be forced to their new plan and you have no say with what you can pretty much get since you know you have to get their $25, 2gb data plan + voice + $20 unlimited text message for sure. the only choice in this matter is whether you're going to downgrade to 200mb (i think not) and which voice plan will you be using.

so yes, they will honor the old contract, but only if you keep your old phone or buy phones at full price from at&t or somewhere else that works with at&t's bands.
[G2 and Desire Z General] biohazrd51:
I'm sure they would honor it, but having technologies that don't work together would require a lot of people to "upgrade" and sign a new contract with different rates.

As for the jobs, yes they may have the call center jobs, but what about techs, or duplication of retail stores within a certain area. How many of those would be shut down and people lose their jobs? If they really cared about bringing the jobs home and not just cash, they would've done it already.

To me it just looks like AT&T trying to prevent themselves from sinking in the long run. T-Mobile brought out 4G first, Verizon got the iPhone. Other than having the iPhone first, I don't really see much coming out of them. If this doesn't go through, it wouldn't surprise me to see Spring getting a much larger market share in the next 3-7 years.
[G2 and Desire Z General] kaijura:
On a side note, saw this on bloomberg this morning:

http://www.bloomberg.com/news/2011-...h-new-t-mobile-buyer-real-m-a.html?cmpid=yhoo

T-mobile to lose $12billion if merger is or isn't done, already lost 600,000+ subscribers and income down 55% since 2011.. holy hell!
[G2 and Desire Z General] martonikaj:
I think it was pretty well known that T-mobile (and Sprint) is in a really tough spot right now. Neither company has been making money or increasing subscribers in a long long time.