Related
T-Mobile offers a service of using Wifi to send/receive calls rather than the cellular service. It costs minutes for Pay-as-you-go folks, but is free if you have a plan (at least in the US). The feature shows up as 'Wifi Calling' and automatically updates if you have a Wifi connection. It is really handy if yo have poor cellular reception.
There have been various P509-specific roms here with Wifi-Calling, but they were either based on T-Mobile's 2.2.2 whose performance sucked, or they didn't work for me.
Here is a flashable zip (signed) which should work in amonra and CWM, to add the relevant files and properties to any 2.2 based rom for a P500.
I've been using it on devoid with no issues.
It probably won't work on a gingerbread rom
It definitely won't work if your provider isn't T-Mobile
You should be able to install the zip and be good to go.
For reference these are the manual steps I used to get it working:
install:
system/apps/Kineto.apk
system/lib/libganril.so
system/lib/libkineto.so
system/lib/librilswitch.so
Add this to the end of build.prop
Code:
rild.libpath=/system/lib/librilswitch.so
rilswitch.vendorlibpath=/system/lib/libril-qc-1.so
rilswitch.ganlibpath=/system/lib/libganril.so
None of this is difficult, but finding all the bits and pieces took some time, and the error messages from logcat are next to worthless as far as debugging goes.
The zip does a crude hack to modify build.prop, so you should only install this once per ROM (i.e. install after reflashing a ROM, not if flashing a kernel or another mod).
I originally started this as a question in the general forum, but now that we have a solution, I was advised it probably belongs here. If them mods disagree, please feel free to delete this or that thread:
http://forum.xda-developers.com/showthread.php?t=1100681
Thanks again it works!!!!
Works. Woohoo. Finally. ;-) thank you much.
Sent from my LG-P500 using Tapatalk
Thank you...
This works, thanks!!!
Will we need to wait until T-Mobile releases 2.3 for this to work on gb?
nchall said:
Will we need to wait until T-Mobile releases 2.3 for this to work on gb?
Click to expand...
Click to collapse
I haven't tried it yet, so I don't know for sure, but my guess is that we will need different shared-libraries to deal with the updated 2.3 baseband. So my expectation is that we either need to wait for a 2.3update from T-Mobile, or to maybe find anothe LG phone with the same baseband that we could grab the shared-libs from.
Works perfect on devoid froyo final
Sent from my LG-P500 using XDA Premium App
I've been trying to get TMO wifi calling working all day for my HTC HD2. I'm running a completely stock Desire HD ROM port = Android 2.2.1 w/ Sense 2.1 (CMYLXGO's). Is this ONLY going to work on a P500 or will this work on any 2.2.1 Froyo build?
OK - so I went ahead and flashed it from CWM and it all appeared to go smoothly. It installed and the app is there, but it just sits on "Enabling" once I turn the app on. I've verified that:
1. The three "*.so" files are in the "system/lib" folder
2. The build.prop file was appended and the appropriate code was added to the very end of the build.prop file
But still no love. Any thoughts/help??
For reference, I've tried a newer Gingerbread ROM and the associated TMO Wifi Calling app that's been documented to work and I have WiFi Calling working in that scenario. So I know I have correct setup (right SIM, etc...). The problem is I'm not a huge fan of that ROM and I'd really like to get it working w/ Froyo 2.2.1... Any help would be GREATLY appreciated.
thnx
mgreig said:
I've been trying to get TMO wifi calling working all day for my HTC HD2. I'm running a completely stock Desire HD ROM port = Android 2.2.1 w/ Sense 2.1 (CMYLXGO's). Is this ONLY going to work on a P500 or will this work on any 2.2.1 Froyo build?
Click to expand...
Click to collapse
This Wifi-Calling Build is for Optimus T (P509).
Swyped from my LG-P509 using XDA App.
will it work on Phoenix ROM 2.3.4......?
please tell me...
suyashc said:
will it work on Phoenix ROM 2.3.4......?
please tell me...
Click to expand...
Click to collapse
no. you need to find a gingerbread version. I know there was one in the development section, but it's been taken down.
If anyone has one, please post!
I am looking for this as well for CM7 for my girlfriend when she leaves to study abroad.
I just read this thread....
Can someone help clarify if the .zip file in this thread is the standalone Wifi Calling app or it's a ROM that I need to reflash to my phone in order to use the hacked Wifi Calling app?
I rather not reflash, prefer to stay with the official Android 2.2.2 from T-mobile, so any advice for installing the hacked Wifi Calling app alone is most appreciated.
Thanks! My phone's the Optimus T (P509).
me4tux said:
I just read this thread....
Can someone help clarify if the .zip file in this thread is the standalone Wifi Calling app or it's a ROM that I need to reflash to my phone in order to use the hacked Wifi Calling app?
I rather not reflash, prefer to stay with the official Android 2.2.2 from T-mobile, so any advice for installing the hacked Wifi Calling app alone is most appreciated.
Thanks! My phone's the Optimus T (P509).
Click to expand...
Click to collapse
It is just the standalone kineto wifi calling.
Sent from my LG-P509 using XDA App
Is this app working?
Ok. I downloaded this hacked Wifi Calling app to my phone (T-mo Optimus T P509 - Android 2.2.2 official / stock)
It unzipped, and presumably placed the files where they needed to go. Rebooted the phone.
I then checked my prepaid balance, and noted it.
Next I made sure Wifi is on and connected. Wifi Calling "blue logo" is also lit up. I used the browser to make sure internet is working on Wifi. All good.
One extra thing I did manually:
I noticed the "Use only 2G networks" setting under "Mobile network settings" is set for 2G and I "UNCHECKED" it. Not sure if causes any anomalies to the Wifi Calling hacked app.
My prepaid balance got reduced after my test call. What's going on?
me4tux said:
Ok. I downloaded this hacked Wifi Calling app to my phone (T-mo Optimus T P509 - Android 2.2.2 official / stock)
It unzipped, and presumably placed the files where they needed to go. Rebooted the phone.
I then checked my prepaid balance, and noted it.
Next I made sure Wifi is on and connected. Wifi Calling "blue logo" is also lit up. I used the browser to make sure internet is working on Wifi. All good.
One extra thing I did manually:
I noticed the "Use only 2G networks" setting under "Mobile network settings" is set for 2G and I "UNCHECKED" it. Not sure if causes any anomalies to the Wifi Calling hacked app.
My prepaid balance got reduced after my test call. What's going on?
Click to expand...
Click to collapse
As I recall wifi calling also uses your minutes.
Sent from my LG-P509 using XDA App
InfiniteRisen said:
As I recall wifi calling also uses your minutes.
Sent from my LG-P509 using XDA App
Click to expand...
Click to collapse
Alright then. It was my mis-understanding.
I originally thought this modified Wifi Calling app would allow Prepaid users the benefit of free calls when Wifi is present.
me4tux said:
Alright then. It was my mis-understanding.
I originally thought this modified Wifi Calling app would allow Prepaid users the benefit of free calls when Wifi is present.
Click to expand...
Click to collapse
I believe this used to be true for those who were on monthly subscription plans, but from what I've heard, it uses minutes for prepaid users.
There are still benefits though, with the main one being better signal coverage. I have also heard that if you are overseas and you use Wi-fi calling to a US number, you will still be charged at the normal domestic rate instead of paying international roaming.
Do we know if there is a version of this out for Android 2.3 yet?
Jawadali said:
Do we know if there is a version of this out for Android 2.3 yet?
Click to expand...
Click to collapse
Same question, different day.
tl;dr:
A SU660 BB (824, 1120, 0420) will fix the weird static noise and bad call quality issue on "made in Korea" devices!
You'll find more information on this issue in this post and more information (including known issues and fixes) on BB 824/1120/0420 in the second one.
Original Post:
-------------------
I just want to share this with all of you who might have missed it within the CM7 Nightlies and Baseband discussion threads - and want to gather all information about this into one thread.
This was found out originally by vadonka here.
I found many others who confirmed that people on the other end of your call complain about static noise (like the noise when you're holding 2 phones together or standing next to a speaker).
We were not able to track down why some p990 users suffered from it and others don't. Some could fix it with the 502BB - some with 725BB and the Gingerbread leaked ROM - but not with CM7.
It appears that there are different (hardware?) versions out there.
If your device is "Made in Korea" (you'll find that info on a sticker under your battery) you might suffer from this noise issue - but not all Korea-made devices do.
For "Made in Korea" ones this noise is almost gone with SU660 BB and a matching RIL (824, 1120, 0420)!
These basebands are for the SU660 (the korean version of the P990), but work for us, too.
I'd almost given up on this issue - was using the leaked ROM (which sucks if you wanna use CM7) and intended to sell it soon. I tried nearly every possible combination of BB/RILs with CM7 some time ago - and never got rid of this problem. My poor girlfriend had to answer maaaaaaany test calls hehe.
This weekend I thought to give CM7 one more try, lurked into the CM7 nightly thread and found this Baseband which seems to fix my issue.
It's confirmed to work for the "Made in Korea" 2x's of vadonka, Sckank, TrymHansen, pastime1971 and temasek.
You'll find more infos on known issues in the 2nd thread.
So - why are Basebands which are made for the SU660 working best with our "Made in Korea" P990's? This could explain many of the "hard to track down" issues some people have - because their phones differ even if it's the same model.
You can get 824/1120/0420 BB and RIL here: P990 Complete Baseband Overview Thread
There you'll find BB and RIL install instructions, too.
positive comments
pretty similar to 725BB - if you don't have problems with 725 BB stick to it, as it might have less issues!
good call quality on both ends
good battery life (neither better nor worse than e.g. 218 or 725 BB)
good network speed & connectivity
no wifi problems
known issues with SU660 BBs (824, 1120, 0420)
automatic time is not working
Click to expand...
Click to collapse
Fix:
There is a fix from pastime1971 if you're using CM7, you need a CM version with the following fix cherry picked though: "Change Iaaf7f1c4: LGEStarRIL: Apply DST regardless of Infineon fix (PATCH #3)"
In temasek's or owains KANGs this fix is already included.
Head to their threads to download a ROM and get instructions how to enable automatic time.
grognaz said:
every reboot i have to set 2G only again (...)
Click to expand...
Click to collapse
Fixes:
- Installing Toggle 2G/3G will fix this with the "Turn on 3G manually" setting! (confirmed by rugglez, thx!)
- Set 2G manually (duh!)
When you're on 2G and you'll disable data and reenable it, data might not turn on for some users
Click to expand...
Click to collapse
This can happen with other basebands as well, it seems to be a BB/ROM combination issue
Fixes:
- activate and deactivate airplane mode
- use 3G
You could loose your IMEI while flashing
Click to expand...
Click to collapse
Fix:
- please refer to this post to restore your IMEI.
Some people won't get signal
Click to expand...
Click to collapse
Fixes:
Well your phone isn't compatible to 824BB - you should install 725 or 218 instead.
As it's not compatible you shouldn't suffer from the "Made in Korea"-Noise issue anyway.
So this is the dial-up-esque noise that pre-warns of any impending text messages/phone calls?
plz tonydl i wana try 824 BB and RIL , i'm on cm7 7.2 the latest kang , but can you tell how to change it ?? (a mini guide plz)
Mungulz said:
So this is the dial-up-esque noise that pre-warns of any impending text messages/phone calls?
Click to expand...
Click to collapse
No - it's a quite disturbing noise on the other end which won't stop. If you're not suffering (better: the people whom you're calling) I wouldn't advise this baseband.
stpsp said:
plz tonydl i wana try 824 BB and RIL , i'm on cm7 7.2 the latest kang , but can you tell how to change it ?? (a mini guide plz)
Click to expand...
Click to collapse
Sure - just follow Pauls guide to change the baseband here.
For getting the matching RIL I use sibbors "GetRIL" app: https://market.android.com/details?id=com.sibbor.getril
i flashed 824 yesterday and i have a couple of problems with it.
every reboot i have to set 2G only again, seems to reset/ignore the GSM only option and the timezone is 1hour behind...
so far i have not noticed any noise like i had with 725 but havent used it a lot so i will continue to listen and ask if its better than before
grognaz said:
i flashed 824 yesterday and i have a couple of problems with it.
every reboot i have to set 2G only again, seems to reset/ignore the GSM only option and the timezone is 1hour behind...
so far i have not noticed any noise like i had with 725 but havent used it a lot so i will continue to listen and ask if its better than before
Click to expand...
Click to collapse
Yep, it's not perfect. As I said before, you need to disable automatic time for the moment - which is probably due to the "fix" I mentioned above.
I can confirm that 2G makes some trouble - maybe Toggle 2G/3G will help you?
tonydl said:
Yep, it's not perfect. As I said before, you need to disable automatic time for the moment - which is probably due to the "fix" I mentioned above.
I can confirm that 2G makes some trouble - maybe Toggle 2G/3G will help you?
Click to expand...
Click to collapse
well it no serious problem once its set manually and since i never use 3g i just have to think about enabling the 2g option when i reboot. maybe i could try if green power can handle the 2g only option... lets see
edit: nope doesnt look like it since green power works with the device settings which are messed up. however, as far as i experienced it might be a problem with cm7, i think i have some strange behavior with every bb except 208 if i remember correctly.
Sent from my Optimus 2X using XDA App
Beware of imei getting hosed when you install Korean baseband. There is a way to recover and keep it handy. I used putty on windows to fix it when I messed up a while ago.
This also explains why I my phone keeps rebooting and showing BSODS when installing Spica's HP kernel. I always thought that it was strange that there where different versions of the phone.
FYI, I tried different BB and also the 824 with MIUI but the battery drain was awful. LG just released V20M for the Netherlands so i got stuck with the 725 BB.
I don't complain about the quality and I didn't try the 824 with this version. Maybe later when i'm sick of this one .
I have a "made in korea" device with 725 BB (from v20c I think) and 218 RIL. My rom is CM7 204. I have asked a lot of my friends and family and no complains for the quality.
afpapa said:
I have a "made in korea" device with 725 BB (from v20c I think) and 218 RIL. My rom is CM7 204. I have asked a lot of my friends and family and no complains for the quality.
Click to expand...
Click to collapse
That's interesting.
Then there're even some more differences than "made in korea".
LG has somehow managed to fix the static sound for their v20x builds with 725 BB, but CM7 hasn't.
Does anyone have an idea how to track this down to help the devs to build a workaround? I am pretty happy with 824 BB right now, but I would prefer to have a choice.
I have a P990 assembled in Korea and it had awful call quality with every BaseBand except 0502 and 0824.
i have tried 502 and it was also pretty good but the battery drain was a lot higher:O
so im back to 824. anyone know if there is a fix for the automatic time beeing off by an hour? i remember that this was present in earlier nigjtlies and got fixed somehow, so maybe the same fix can be used on this case.
Sent from my Optimus 2X using XDA App
grognaz said:
i have tried 502 and it was also pretty good but the battery drain was a lot higher:O
so im back to 824. anyone know if there is a fix for the automatic time beeing off by an hour? i remember that this was present in earlier nigjtlies and got fixed somehow, so maybe the same fix can be used on this case.
Click to expand...
Click to collapse
There is a fix from pastime1971 if you're using CM7.
You need a CM version with the following fix cherry picked though:
"Change Iaaf7f1c4: LGEStarRIL: Apply DST regardless of Infineon fix (PATCH #3)"
Head over to this post for a KANG which included it and gives a description: http://forum.xda-developers.com/showpost.php?p=20595849&postcount=12065
This is the latest KANG build P204-16
http://forum.xda-developers.com/showpost.php?p=20610135&postcount=12098
Another small issue: the call initiation is a bit longer - if I'm too quick with saying "hello" then the other end won't get it (and vice versa).
Can anyone confirm?
hmm now that you mention this i remember that i was talking over the headset with a friend and when i unplugged it he couldnt hear me anymore. i had to enable the speaker so he couos hear me again, after switching it off again everything was fine.
its like the mic didnt switch from headset to phone when i unplugged it:/
Sent from my Optimus 2X using XDA App
grognaz said:
hmm now that you mention this i remember that i was talking over the headset with a friend and when i unplugged it he couldnt hear me anymore. i had to enable the speaker so he couos hear me again, after switching it off again everything was fine.
its like the mic didnt switch from headset to phone when i unplugged it:/
Click to expand...
Click to collapse
I cannot reproduce that. Which ROM are you using and which BB/RIL?
Hello!
Mine is also made in Korea.
I tested 0622, 0725 and 0823 - 0824 didn't work.
Voice quality was always acceptable didn't notice any problems there.
But overall signal reception(especially indoors) is by far better using 0823 - but this might be a special because my provider is known for bad reception indoors…
This is my first post, so first of all, hi everyone. I'm having a strange issue with CM9 by Owain94, as many others as I have seen in multiple threads (even with ICS Nova), but no solution is provided nowhere until now.
After certain time connected to WiFi, at the moment of disable it, 3G is not available (signal bars stay greyed, browser and mail apps fails to connect, and so on). Only toggle between airplane mode and normal mode, or reset the device, solves the problem. I tried multiple solutions (GSM Auto PRL vs WCDMA prefered, disable automatic time and date, multiple combinations of BB/RIL) but none is working for me.
Has anyone been able to solve this problem?
If helps, this is my actual configuration:
CM9 Unofficial by Owain94 build 33
Baseband 313
RIL 405 V10c Spain
Coming from Ultra Wipe (term is mine): back to Stock Froyo, root, update to CM7, update to CM9
Thanks in advance.
davidmarco said:
This is my first post, so first of all, hi everyone. I'm having a strange issue with CM9 by Owain94, as many others as I have seen in multiple threads (even with ICS Nova), but no solution is provided nowhere until now.
After certain time connected to WiFi, at the moment of disable it, the 3G is unable to startup. Only toggle between airplane mode and normal mode, or reset the device, solves the problem. I tried multiple solutions (GSM Auto PRL vs WCDMA prefered, disable automatic time and date, multiple combinations of BB/RIL) but none is working for me.
Has anyone been able to solve this problem?
If helps, this is my actual configuration:
CM9 Unofficial by Owain94 build 33
Baseband 313
RIL 405 V10c Spain
Coming from Ultra Wipe (term is mine): back to Stock Froyo, root, update to CM7, update to CM9
Thanks in advance.
Click to expand...
Click to collapse
bad answer sorry
sorry for the bad english
I have the same problem. With stockrom it's equal.
Is your provider vodafone?
Gesendet von meinem Optimus 2X mit Tapatalk
-SONNY- said:
I have the same problem. With stockrom it's equal.
Is your provider vodafone?
Gesendet von meinem Optimus 2X mit Tapatalk
Click to expand...
Click to collapse
My provider is Orange (through national data roaming). On CM7 I never had this problem.
davidmarco said:
My provider is Orange (through national data roaming). On CM7 I never had this problem.
Click to expand...
Click to collapse
Yep i only get this problem with stock, cm9 and miui. On cm7 i don't have that issue.
Gesendet von meinem Optimus 2X mit Tapatalk
Same problem here. I have to turn on 2g and then back to 3G to make it work. But after a while you get used to it.
Sent from my LG-P990 using Tapatalk 2 Beta-5
No solution, but a workaround:
Try Toggle2G app.
Well, I'm on CM7.2 RC1, but I suppose there is a Power control widget too. If you try to add it, there are some actions you can change - like "WiFi enables 3G" (3G when WiFi is disabled), but there are more.
I'm thinking if that can be a workaround (or even a source of problem, but if it does even on the stock rom..).
Thronesmasher said:
No solution, but a workaround:
Try Toggle2G app.
Click to expand...
Click to collapse
Thanks, I'll try until a solution will be provided.
This afternoon I'm discovered some interesting things. A few days ago, I tried through the service menu (aka *#*#4636#*#*) the GSM Auto PRL solution given by others, but it didn't work for me, probably because I was restarting the phone just after select the cited network mode. But todat, thinking about (arrjj) I'm discovered that after restart, the phone backs automatically to the previouos WCDMA Preferred mode (I remember that behavior from old days with CM7).
So I changed the network mode, wait for the phone to reconnect prior left the service menu, and voila!! 3g connectivity did not drop after connect to a wifi network for a while.
Because CM9 does not have an option in Network Settings to set the preferred network mode (as had CM7), neither the service menu appears to save this information in a persistent way, I tried to find out where such information was stored. Multiple locations appear to do it. First is /system/build.prop:
#ro.telephony.default_network=0
This value stands for the network modes supported by Android:
0 - WCDMA Perferred
1 - GSM Only
2 - WCDMA Only
3 - GSM/WCDMA (auto PRL)
4 - CDMA / EVDO Perfered
After uncomment the line, change the value and reset the phone, 3g drop still occurs (service menu stay stuck on WCDMA Preferred)
Next site to looking for is the database /data/data/com.android.providers.settings/databases/settings.db. Whitin it, there is a table named secure in which you can found a data row like the following (column headers are drawed for clarity):
id | name | value
-------------------------------------
84 | preferred_network_mode | 0
So next step was change it. From a shell console, I ran the following commands:
$ su
# cd /data/data/com.android.providers.settings/databases
# sqlite3 settings.db
sqlite> update secure set value="3" where name="preferred_network_mode";
After reset the phone, 3g drop still occurs (same symptom as earlier).
So none of these solutions are working for me, neiter individually nor in conjunction. What is clear, at least for me, is that the data connectivity drop occurs due the default network mode (WCDMA Preferred) in my rom (CM9 by Owain94 - build 35), and the impossibility of change it persistently.
Devs are tracking the bug, it seems to be an issue with routing network process, when wifi is disabled, there should be a route modification to enable gsm network, and that fails for an unknown reason yet (a daemon isn't properly launched, or dies too early).
This process wasn't used in GB, that's why you don't have this bug with 2.3 roms.
Striatum_bdr said:
Devs are tracking the bug, it seems to be an issue with routing network process, when wifi is disabled, there should be a route modification to enable gsm network, and that fails for an unknown reason yet (a daemon isn't properly launched, or dies too early).
This process wasn't used in GB, that's why you don't have this bug with 2.3 roms.
Click to expand...
Click to collapse
But i have the same problem with all roms even Stock except CM7 since V20q BB...
Gesendet von meinem Optimus 2X mit Tapatalk
i get it in every rom, thats why i tried something else than cm7 and now sent my device in for repair or replacement.
Sent from my HTC Wildfire using XDA
+1
i also have this problem with all others rom on except CM7.
i think devs are on the right way, lets wait patiently and dont stay asking about same thing.
until there, all that still in trouble stay on CM7 and be happy
*does someone have positive experience using toogle2G or using power control with "wifi turn off 3g"?
I experienced the issue on stock v20m and Modaco Gr6. Last week I switched to CM7, the has not yet returned. Anyone experience with the 'new' v20r ROM?
Sent from my Optimus 2X using Tapatalk 2
rafaelsartori said:
i think devs are on the right way, lets wait patiently and dont stay asking about same thing.
Click to expand...
Click to collapse
I think nobody is giving the importance it have, 3g drop is a very old issue. I'm actually investigating the source code to determine why it happens and try to solve myself.
rafaelsartori said:
*does someone have positive experience using toogle2G or using power control with "wifi turn off 3g"?
Click to expand...
Click to collapse
Toggle2g isn't working very fine for me, after install it About phone > Status get freezed, and sometimes Phone app gets a FC. Others say it work properly, so I encourage you to try.
Switching off WiFi works fine for me on RC's CM9SK3 and ironkrnL. It takes like 5 seconds till im fully connected to H. 0725 BB + 0725 V10d RIL. Vodafone Germany is my carrier.
langhaardack said:
Switching off WiFi works fine for me on RC's CM9SK3 and ironkrnL. It takes like 5 seconds till im fully connected to H. 0725 BB + 0725 V10d RIL. Vodafone Germany is my carrier.
Click to expand...
Click to collapse
Yes!! After flash a V10 RIL the problem is m-a-g-i-c-a-l-l-y gone
I now know the really mean of "ONLY V10 RILS ON CM9"...
My current ROM-BB-RIL combination is as follows:
CM9 Unofficial by XXMrHyde build RC0-8
BB 725 V20Q
RIL V10d Europe
Hey,
i had and have exactly the same problem. The combination
BB 725 V20Q
RIL V10d Europe
didn't solve it for me.
I have to use cm7 i guess.
dickeplatte said:
Hey,
i had and have exactly the same problem. The combination
BB 725 V20Q
RIL V10d Europe
didn't solve it for me.
I have to use cm7 i guess.
Click to expand...
Click to collapse
Curious, because I'd never had the problem on CM7.
After a few months uninstalled (those kept on CM9), I've also discovered that the problem emerges when JuiceDefender joins into the equation. After stop it, data comes back again successfully.
Cheers.
Hi guys,
I've been digging a lot since I got my unlocked VZW Droid4 on eBay last month to get it working on european (french) networks, and finally yesterday I got it working.
I'l try to explain in details sometime but basically (after rooting, updating to 619 build and applied the latest SELFKANG nightly) I first applied the trick found by fragulina on the "Bionic on tmobile" (http://forum.xda-developers.com/showpost.php?p=25219819&postcount=12), then I applied the GSM patch used by RAZR users (http://forum.xda-developers.com/showthread.php?t=1495884) and modified the build.prop for our XT894 device.
And it works (voice and data, not sure about 3G as I have a very poor signal here but it *did* showed up sooner today).
I still have to *#*#4636#*#* after a fresh install to switch to "WCDMA Prefered" before the phone accepts my french "Free Mobile" APNs, but that's it.
THANKS! It works! And I didn't even use the Selfkang rom. I flashed my d4 with Stock motoblur and Applied the GSM patch and applied the Radiocomm adjustment. I didn't even have to wait. It switched to 3g right away!
Call (voice) quality is very bad though, so I'll be playing with my D4 some more this weekend, but... IT WORKS! Woohoo!
Just to be clear: Are you guys using safestrap first, before applying this patch?
highlandsun said:
Just to be clear: Are you guys using safestrap first, before applying this patch?
Click to expand...
Click to collapse
Yes.
Yes, Safestrap, and apply the GSM patch as if you install gapps.
Cool. I've done the Radiocomm thing (using VirtualBox, glad that worked) and applied the GSM patch on top of the stock 215 ROM. Still using my Verizon SIM at the moment, waiting for the micro-SIM cutter I bought off eBay so I can swap my Irish SIM in and test.
The RAZR-GSM patch changes a lot in /system/build.prop that we probably don't want to change. Has anyone got just the relevant diffs we can look at? I'm going to try to pare down to just the bare minimal diff later. Right now I've only got CDMA working, no LTE, using the RAZR-GSM build.prop as-is.
I am doing a similar analysis of the build.prop in the RAZR GSM patch so we have a proper version for the D4. There are definitely things in there that should not be for the D4. I will have more time tonight to work on it.
highlandsun said:
Cool. I've done the Radiocomm thing (using VirtualBox, glad that worked) and applied the GSM patch on top of the stock 215 ROM. Still using my Verizon SIM at the moment, waiting for the micro-SIM cutter I bought off eBay so I can swap my Irish SIM in and test.
The RAZR-GSM patch changes a lot in /system/build.prop that we probably don't want to change. Has anyone got just the relevant diffs we can look at? I'm going to try to pare down to just the bare minimal diff later. Right now I've only got CDMA working, no LTE, using the RAZR-GSM build.prop as-is.
Click to expand...
Click to collapse
Well, voice quality is bad to nonexistent (Sometimes people can't hear me and the other way around), the keyboard doesn't light up and the brightness adjustments won't work anymore. That's all I could find for now.
can you send text messages?
Still tinkering with this. Here are the system/lib files that the "GSM patch" archives update:
Code:
643696 Defl:N 318513 51% 2012-03-02 16:16 ea29f77b system/lib/lib-mot-lte-ril.so
13692 Defl:N 5635 59% 2012-03-02 16:16 5d586a83 system/lib/libmoto_nwif_ril.so
30368 Defl:N 12974 57% 2012-03-02 16:16 c41e8c74 system/lib/libmoto_qmi_ril.so
343424 Defl:N 176091 49% 2012-03-02 16:16 a86cca0f system/lib/libmoto_ril.so
5448 Defl:N 2010 63% 2012-03-02 16:16 f6df272b system/lib/libpppd_plugin-ril.so
22168 Defl:N 11992 46% 2012-03-02 16:16 18b182ce system/lib/libreference-ril.so
123664 Defl:N 57493 54% 2012-03-02 16:16 5f39940e system/lib/moto-ril-multimode.so
The libmoto_nwif_ril.so is identical to stock 215/219, so there's no need to update it. Same with libpppd_plugin-ril.so and libreference-ril.so. That leaves just 4 files that are different: lib-mot-lte-ril.so, libmoto_qmi_ril.so, libmoto_ril.so, and moto-ril-multimode.so. Of these 4, libmoto_ril.so and libmoto_qmi_ril.so are updated by the 219 patch. I kept the 219 version on my phone, and found that LTE wasn't working. So I copied over the 215 versions of lib-mot-lte-ril.so and moto-ril-multimode.so as well, and LTE is back again.
I still haven't actually tried GSM yet, still waiting for my micro-sim cutter to arrive in the mail. But after comparing build.prop files, this is what I've changed so far.
Code:
--- bprop.219 2012-04-28 12:18:46.060572850 -0700
+++ bprop2.219 2012-04-28 12:28:33.499485790 -0700
@@ -39,7 +39,8 @@
ro.sf.lcd_density=240
ro.default_usb_mode=2
ro.mot.ril.danlist=611,*611,#611
-persist.ril.ecclist=911,*911,#911
+persist.ril.ecclist=911,*911,#911,112
+# Use 2 for UMTS
persist.ril.modem.mode =1
# This defines the max event window manager can
# handle in 1 s. We may adjust this # for performance
@@ -67,7 +68,7 @@
# Time between scans in seconds. Keep it high to minimize battery drain.
# This only affects the case in which there are remembered access points,
# but none are in range.
-wifi.supplicant_scan_interval = 45
+wifi.supplicant_scan_interval = 90
# Indicate carrier OTA SP number schema
# refer to frameworks/base/telephony/java/com/android/
@@ -82,7 +83,7 @@
ro.opengles.version = 131072
# This is a high density device with more memory, so larger vm heaps for it.
-dalvik.vm.heapsize=42m
+dalvik.vm.heapsize=76m
# our HTML browser (not WAP browser ) does not need to specify UAProf URL
ro.mot.hw.uaprof=http://uaprof.vtext.com/mot/xt894/xt894.xml
@@ -140,7 +141,7 @@
#1 this is verizon wireless globle phone
#0 this is not verizon wireless globle phone
# NOTE: The definition moved to cdma_maserati.mk to support diff config for factory.
-ro.mot.phonemode.vzwglobalphone=0
+ro.mot.phonemode.vzwglobalphone=1
# END Motorola, nfjb73, 21-jun-2010, IKMAIN-732
# BEGIN Motorola, nfjb73 23-jun-2010, IKMAIN-624
@@ -153,7 +154,7 @@
# This is part of the VZW World-phone Feature. SMS are always sent to a US SMSC and then injected
# into that network. This allows for billing and give the user the impression that the device is
# still in the US.
-ro.telephony.gsm-routes-us-smsc = 1
+ro.telephony.gsm-routes-us-smsc = 0
# END Motorola, qmfd78, 14-Jul-2010, IKMAIN-884
# BEGIN Motorola, a22600 qmfd78, 16-Jul-2010, IKDROIDPRO-423
@@ -331,3 +332,12 @@
ro.build.version.full=Blur_Version.6.13.219.XT894.Verizon.en.US
ro.mot.hidden_keyboards=evfwd
+ro.ril.hsxpa=3
+ro.ril.gprsclass=12
+ro.ril.hep=1
+ro.ril.enable.dtm=1
+ro.ril.hsdpa.category=28
+ro.ril.enable.a53=1
+ro.ril.enable.3g.prefix=1
+ro.ril.hsupa.category=7
+
highlandsun said:
Still tinkering with this. Here are the system/lib files that the "GSM patch" archives update:
I still haven't actually tried GSM yet, still waiting for my micro-sim cutter to arrive in the mail. But after comparing build.prop files, this is what I've changed so far.
[/code]
Click to expand...
Click to collapse
Oh yes I was too excited when I talked about build.prop yesterday and I'm having some friends at home today so I could'nt answer your questions, but I hacked a lot my build.prop since my first tries last month (when I was trying to only change RIL libraries and check the radio log to see what happened and was missing the radiocomm hack).
Did'nt checked voice quality, will try later today, but yes the thing is very sensible to different values in here. If you don't get it right you won't be able to set up your APN's, or you'll return to the VZW "setup data" thing, and so on (but I'm sure you already know).
I did'nt verify everything as you do, never had the patience, but here is mine (I use a 200 dpi in this).
directions for stock rom + gsm
Can someone post a tutorial for me?
I've got stock rom and trying to get GSM working. I don't wan to mess up my phone.
Does this mean if i follow your instructions above i can take this phone to europe and shove a vodafone sim in it? Would like to figure this out before i go on vacation.
Sent from my DROID4 using Tapatalk 2
Not working
For some reason the Droid won't accept my simcard. I cut to Micro size using scissors . But I keep getting SIM is from unknown source. The SIM works in my Milestone so that's not it. Too bad I don't know any Micro-SIM users. Now I have to order one and see if that will help. Funny thins is when I tried to take it out it showed KPN-NL for a moment. Well I only saw it when I turned the phone around back to front.
So bummer, still no GSM for me. I just hope its as simple as replacing the SIM with an brand new Micro-SIM.
@zeroktal: I posted it somewhere else on the forum I'll paste it here, mods, don't hate me for cross posting
Still working on it. It's quick and dirty but it does the job for now, more or less
Before you continue I need to say this: Do this at your own risk! I'm am not responsible for your actions, bricking/destroying your phone.
First: Download Radiocomm, install it on your pc and connect your Droid 4.
Download Radiocomm here: http://www.mediafire.com/?du2dimtzztj
1. Ensure USB is connected as PC Tools mode (not Mass Storage)
2. In Radiocomm go to MA->COMMON->MDM 6x00
3. After it comes up, switch to FTM Common1 tab and wait for the phone to enumerate purple or green.
4. On the upper right side in the NVAccess, scroll to NV item 1877 NV_RF_BC_CONFIG_I
5. Read the value from the device
6. Replace the first 8 bytes (16 digits) with: 8703E80400000200
7. Write the data to the device and powercycle.
This will enable GSM/UMTS bands... thanks to Fragulina
If you flashed your D4 You might need to reflash it. And install the GSM patch. These are my test restults so far:
Moto stock: GSM works! No data, just Extremely bad to nonexistent voice
Moto stock with RAZR GSM PATCH: GSM works, Data works. Voice is very bad, but it works.
Chinese ICS modded CM9 rom without GSM patch: GSM doesn't work out of the box but if you type *#*#4636#*#* Select "phone information", scroll down, and select one of the GSM options, it'll work. Its unstable though.
Chinese ICS modded CM9 rom with GSM patch: GSM works! No data, just Extremely bad to nonexistent voice
Gummy: To be tested
SelfKang: To be tested
Applying the GSM patch can be done by installing the zip after flashing your rom (same way as installing gapps)
Download the GSM patch here -> RAZR_AOKP_CM9_GSM_RIL_PATCH.zip (Thanks to shahulvm, Adlx.xda and Spryte)
If the first patch doesn't work, try this patch: -> Eclipse GSM Patch Frasertag.zip (Thanks to Frasertag)
That's it for now. This howto is far from finished. There's a lot to be tested but it's a start. I'll try to update this howto as often as possible.
Special thanks to: Poursinet, Fragulina, (XDA) Disablewong (ANGEEKS/XDA) And many more!
And Especially for die bruine (HOLLAND/SURINAME WOOHO)
@Calebu2: Yes. That's what I did and it works (Not perfect yet though, but it's a start)
@Die Bruine: It's not necessary to order a micro sim. Your cutted sim should work perfectly. Heck, my simcard is also cut with a scissor. The "This sim is from an unknown source" error message appears every time and is easy to bypass. When you turn on the phone, you see the android logo with the text to touch it to start. Don't touch the logo but instead, touch the four corners of your screen. Start with upper left, then upper right, lower right and finally lower left. The activation procedure will be skipped. It will search for the motorola servers though. Don't cancel that for it will take you back to the activation screen. Let it time out and continue from there with the following steps.
Good luck!
@Nickoloz: Yes, Texting works and data works.
Die Bruine said:
For some reason the Droid won't accept my simcard. I cut to Micro size using scissors . But I keep getting SIM is from unknown source. The SIM works in my Milestone so that's not it. Too bad I don't know any Micro-SIM users. Now I have to order one and see if that will help. Funny thins is when I tried to take it out it showed KPN-NL for a moment. Well I only saw it when I turned the phone around back to front.
So bummer, still no GSM for me. I just hope its as simple as replacing the SIM with an brand new Micro-SIM.
Click to expand...
Click to collapse
One of my phone works with a scissored tunisian micro-sim (when I asked the store for a micro-sim, they just cut it in front of me). No problem at all.
On the Bionic thread, users say they have the "unknown source" message but the phone catch signal despite that. I had it under motoblur too, but CM9 never complained.
@Poursinet, how is your voice quality?
So I haven't been able to get passed the Unknown error. I just re-reflased 215 and applied the RAZR patch. Now the phone does recognize my SIM card (in Safemode). I made two calls from Simyo to Vodafone. No voice issues there. However, no data for me yet. I can't choose nor edit APN's. So I'll have to look for my settings. I'm sure I can find them somewhere in/on my Milestone.
First I'm gonna eat something . I'll be back in 30 minutes or so with an update.
@ Die Bruine You won't have data without the gsm patch. You need to apply the patch directly after flashing your rom. If you apply the patch after your boot, the system will be unstable (been there, done that)
Good luck and "Eet Smakelijk"
vmu said:
@Poursinet, how is your voice quality?
Click to expand...
Click to collapse
Not an easy thing to say when you're home alone, friends have gone early before I had a chance to ask them to try out with me.
When I call from the Droid4 on my right to my Droid3 with speaker enabled on my left, voice seems loud and clear but it echoes from one phone to another juste like double-mirrored images. Texting works fine too.
But remember I'm using CM9 latest nightly, I did not try it under Motoblur.
I have the 4G version, is this specific model have a working CM10 ROM? I know the Wi-Fi model does, just want to make sure this won't brick mine or anything.
I'm new to this, just got this today!
It does not. Our version (i957) uses a different chipset then the Wi-Fi version. Best to not flash.
Sent from my Galaxy Nexus using Tapatalk 2
CM10 will eventually support this device -- In fact, the device tree was just created by cyanogen yesterday @ https://github.com/CyanogenMod/android_device_samsung_p5att -- However, work still remains to get this code to even boot, let alone be functional as a daily driver. It will get there, eventually.
The ICS (4.0.4) ROM from Samsung for this device is currently in test with the carriers. The Korean variant (SHV-140) just received the ICS update a few weeks ago, and some of that code might help speed along the Cyanogen update.
The CM10 code currently on github does build, but the kernel does not seem to fully boot -- Locks up just after displaying the initlogo, with adb unavailable, so I have no idea how to get the dmesg. I suspect there are some needle-in-a-haystack sort of details that need to get ironed out, the kind of which probably will require some hardware hacking (ie: serial and/or jtag access) to get at... or for the official i957 kernel to get released.
The shv rom has to be out there somewhere
Sent from my SGH-I727 using xda premium
In for the first screenshot of a p5att (SGH-I957) running jellybean, in case you need some encouragement you won't be stuck on honeycomb forever...
No, it's not even close to stable.
Yes, pretty much everything is broken. IE no LTE, audio, and probably everything else I didn't try.
works: wifi, touchscreen.
No, I won't be maintaining a release for this, the people way smarter than me on the cyanogen team did all the real work on this.. I just built and kludged until I got it to boot with graphics If things go well you'll see a real release from the CM team sometime. For all I know they'll run into a horrible problem and give up, but you know how those guys are.. totally badass.
basic idea:
- breakfast cm_p5att-userdebug
- replace msm-8660-common kernel with code from jb-full branch
- *** edit to update: it seems there is no longer a jb-full branch, there is now just jellybean and jb-old. I'm guessing the out of date msm8660-common kernel from what was jellybean is now jb-old, and jb-full has become jellybean.. hmm.. working on seeing if this is the case (need to clone/build/boot it)
- hack p5att boardconfig
- pick your combination of samsung proprietary files, good luck, the note and/or skyrocket CM10 releases are your best starting point
- brunch p5att, consume more coffee and stuffs
- hack resulting .zip to remove assert for 957 (TWRP has wrong product ID lulz)
- hack ramdisk to enable adb on boot so you can debug why it doesnt come up
- hack proprietary files until you get working graphics
** (not for the faint of heart)
nrvate said:
In for the first screenshot of a p5att (SGH-I957) running jellybean, in case you need some encouragement you won't be stuck on honeycomb forever...
No, it's not even close to stable.
Yes, pretty much everything is broken. IE no LTE, audio, and probably everything else I didn't try.
works: wifi, touchscreen.
No, I won't be maintaining a release for this, the people way smarter than me on the cyanogen team did all the real work on this.. I just built and kludged until I got it to boot with graphics If things go well you'll see a real release from the CM team sometime. For all I know they'll run into a horrible problem and give up, but you know how those guys are.. totally badass.
basic idea:
lunch cm_p5att-userdebug
replace msm-8660-common kernel with code from jb-full tree
hack p5att boardconfig
pick your combination of samsung proprietary files, good luck, the note and/or skyrocket CM10 releases are your best starting point
brunch p5att, consume more coffee and stuffs
hack resulting .zip to remove assert for 957 (TWRP has wrong product ID lulz)
hack ramdisk to enable adb on boot so you can debug why it doesnt come up
hack proprietary files until you get working graphics
(not for the faint of heart)
Click to expand...
Click to collapse
nice job man!
EDIT: I created a separate thread for doing the CM10 build: http://forum.xda-developers.com/showthread.php?t=1867579
Cheers!
Still hacking stuff.. lol.. using the file list from the msm-8660 common proprietary file list, i grabbed that set of files from the CM10 i717 ROM and dropped them onto the i957. Working audio! Don't know about the mic, but it plays sound now. Also, it almost got LTE working... logcat -b radio shows the LTE radio finding the LTE cell and reporting signal strength, but the data session doesn't actually establish, even with the proper APN config. GPS looks like it might even eventually lock on, it found 2 sats after a while, but didn't get a lock. I suspect when full 4G comes up, it'll be able to use SUPL to get it's initial location then actually get a fix.
Downloading the gigantic i717 stock image, going to see if 4G plays nicer with the note radios, since I'm using the note RIL now.. Dan had mentioned he had successfully got the note radios running on the tab 8.9 LTE in an attempt to get voice calls up... the honeycomb RIL stuff just results in lots of errors, so thats straight fail.
I didn't realize how many software pieces go into the cellular data connectivity, yikes!
The more I delve into code and binary packages... the more it appears the 957 is very close to a supersized note! sweet.
Also, bluetooth finds my neighbors macbook, so it probably works, but my headset is at work and I haven't been there in a while (hence having time to do this fun stuff).
If anyone has any suggestions on getting LTE up, I'm all ears. If I can get LTE working, I might be tempted to try to package this beast up.
More fun...
Good grief, it looks like the userdebug variant compiles with all the radio debug flags on, thousands and thousands of lines of everything from verbose text to hex dumps!
i957 honeycomb radio: baseband shows unknown, isn't worth anything
i717 ICS radios, both UCLF5 and 6: entire tablet slows to a crawl once rild starts, fail! Nothing useful in the logs as to why, nothing hogging CPU time... no idea, abort
i727 skyrocket ICS radio I727UCALC4 (no idea how current or valid this radio really is): gets HSPA+ on old 3G "wap.cingular" SIM, no luck with tablet only LTE "Broadband" APN SIM. ~2-2.5mbit download speed.
i727 skyrocket ICS radio UCLD2: Obtained HSPA+ with Broadband APN data-only SIM. ~4.0-5 mbit download speeds. After ~10 minutes, found an LTE cell and pulled 30-35mbit down. After each radio reset (reboot, airplane mode, etc) it takes the 3-10 minute period to get LTE again, and it's also slow (10-50 seconds) to get on HSPA. All around sluggish to jump on a cell, but returns nice speeds once it does so.
i727 skyrocket ICS radio UCLF6 (latest I could find): Pretty much the same as UCLD2 above, similar speeds, but seemed to jump on LTE quicker after a reboot, but still takes a while when coming back from airplane mode. It's the latest, i think, and it works, so it's probably the way to go.
Pending investigation: RIL files -- going to try the skyrocket UCLF6 RIL and see how it works out. Currently still using the note RIL files. Tried UCALC4 skyrocket RIL and it didn't work at all, will try UCLF6 from stock skyrocket ICS release...
Looks like it doesn't like the Broadband APN on a tablet (data-plan-only) SIM. I tossed in a "old school phone SIM" from the 3G days, which is set up on an unlimited phone/data plan (as you could get ages ago) and gave it wap.cingular, and whamo, HSPA+ connectivity. Looks more like a configuration issue and/or the phone RIL/radio combination refuse to play nice with data-only SIM.
I've never tried to debug getting onto 3G/4G service at the RIL radio log level, so not totally sure what to look for, but... guessing it's trying to set up a voice bearer and the UMTS system says F you. need foods, sleep, etc... haha.
And more fun... Skyrocket UCLD2 radio returns HSPA+ connectivity on data-only SIM with Broadband APN, but no LTE. Set APN type to "supl" to enable SUPL, got the first GPS fix in about 2 minutes, after 5 more minutes found 12 sats and obtained 12m accuracy.. sweet!
Update: UCLD2 radio, after sitting around idling for 10 minutes while I made some munchies, decided it would pick up an LTE cell. No idea why it took so long, I'm really close to an LTE cell and both my other LTE devices have never (and don't presently) exhibit this behavior at my location. I suspect this is probably normal behavior of UCLD2 or UCLD2 plays less than optimally with the i957 radio... which should be the same as a skyrocket radio, considering both identify as an M8260 when inquired with "ati" via ttyACM0. Whatever the case, 50ms ping and 30 mbit down works for me...
I really should go to bed sometime...... and make a backup of this device before I bust something!
Adding a little more info: I modified device/samsung/p5att/BoardConfig.mk a little before building... Other devices with no SD card slot had BOARD_HAS_SD_CARD_INTERNAL defined, so i tossed that in. The BOARD_SDCARD_DEVICE_PRIMARY, BOARD_SDCARD_DEVICE_SECONDARY and BOARD_SDEXT_DEVICE_SDEXT values seemed bogus, and I knew the init scripts would set up /sdcard as a fuse device on the /data partition anyways, so I just commented them out.
I don't know if anything uses the 3 values I commented out, but since there's no actual mmcblk device for the fuse (filesystem in user space) emulated sdcard, it doesn't seem a valid value could be found, so, why set one.... Seems to work!
BOARD_HAS_SDCARD_INTERNAL := true
#BOARD_SDCARD_DEVICE_PRIMARY := /dev/block/mmcblk1p1
#BOARD_SDCARD_DEVICE_SECONDARY := /dev/block/mmcblk0p28
#BOARD_SDEXT_DEVICE := /dev/block/mmcblk1p2
Click to expand...
Click to collapse
But, this is my first attempt at hacking cyanogenmod onto a half-baked device, so... don't take my word for it
And before anyone asks, yes, I plan on releasing a flashable update for this, but first... figuring out enough to start from a fresh source tree and build from scratch so I can document how I did this... Let's beat the carriers to jellybean and forget ICS
(yes, I'm editing this post a bazillion times as try stuff, I'll put together something a little more coherent soon)