Develop Bugs

MMS Profiles

OK, so for some reason our builds happen to be hardcoded with a UserAgent Profile pointing to http://www.google.com/oha/rdf/ua-profile-kila.xml. This is reported to the MMS server whenever our MMS client tries to download something, it's stuck in the x-wap-profile: header of the HTTP request.
If you read thru that file you'll see that it's the spec for a Samsung SGH-T429 with 320x480 screen. While looking into MMS receive issues on Sprint we discovered that the MMS server actually reads these profiles, and sizes the output that it sends you based on these profiles. So even if your buddy sends you a nice high-rez photo by MMS, when you receive it, it will be scaled down to 320x480.
[edit: that's not quite true. I think this only affects the size of the image as presented in the Messaging app. The actual attachment is whatever size was originally sent. Of course, most media is scaled down for sending anyway.]
We checked to see what profile the Sprint RHOD400 was sending under Winmo and found this http://device.sprintpcs.com/HTC/PPCTP7380SP/2046514.rdf which seems to have the correct screen dimensions. (I can't seem to download it now though.)
I also checked to see what my phone was using with T-Mobile, and got this
http://www.htcmms.com.tw/gen/RhodiumMR-1.0.xml which also has the right stuff, but a lot of winmo-specific details too. It seems to me that we're going to need to patch the framework to make this profile URL a settable property instead of hardcoding it like it's currently done, to get the most out of MMS.
We should probably start taking an inventory of profiles that are in use on all the MSM devices. In Winmo you can find them in the registry at HKLM\Software\Jataayu\MMS\SP - according to this thread: http://forum.xda-developers.com/showthread.php?t=795343
For example, here's the request for a Sprint RHOD400:
Code:
GET /?msgid=XXX&userId=YYY HTTP/1.1
Accept: */*, application/vnd.wap.mms-message, application/vnd.wap.sic
x-wap-profile: http://device.sprintpcs.com/HTC/PPCTP7380SP/2046514.rdf
Accept-Language: en-US
Host: mms.sprintpcs.com:80
Connection: Keep-Alive
User-Agent: T7380
Here's the request all of our phones are currently using to retrieve MMSs:
Code:
GET /?msgid=XXX&userId=YYY HTTP/1.1
Accept: */*, application/vnd.wap.mms-message, application/vnd.wap.sic
x-wap-profile: http://www.google.com/oha/rdf/ua-profile-kila.xml
Accept-Language: en-US
Host: mms.sprintpcs.com:80
Connection: Keep-Alive
User-Agent: Android-Mms/2.0

I've got this one in the registry:
http://www.htcmms.com.tw/gen/HTC_Touch_Pro2_T7373-1.0.xml
( Rhod100 / AUO )

Mine reads:
http://www.htcmms.com.tw/gen/HTC_Touch_Pro2_T7381-1.0.xml
Also worth noting it was in the registry key:
HKLM\Software\SIE\AutoVer\Opera\User Prefs
and HKLM\Software\Microsoft\Windows\CurrentVersion\Internet Settings

Raa_1 said:
Mine reads:
http://www.htcmms.com.tw/gen/HTC_Touch_Pro2_T7381-1.0.xml
Also worth noting it was in the registry key:
HKLM\Software\SIE\AutoVer\Opera\User Prefs
and HKLM\Software\Microsoft\Windows\CurrentVersion\Internet Settings
Click to expand...
Click to collapse
What model RHOD is that?

This was a setup.xml I made for people running custom roms on boost mobile. Everything should be the same for sprint except the "pcs-boost-mmsc" server address. Maybe helpful?
I changed it to .txt for posting. It seems to be the same that you have.

I know this is probably way to early to be asking this, but I have a Rhod400, where can I input this info (into what file or terminal emulator?) so that I can get MMS working on my phone so I can test it until the patch is ready for the public?

slickdaddy96 said:
I know this is probably way to early to be asking this, but I have a Rhod400, where can I input this info (into what file or terminal emulator?) so that I can get MMS working on my phone so I can test it until the patch is ready for the public?
Click to expand...
Click to collapse
Kinks are being worked out, to my knowledge nothing usable has surfaced yet. Sending works like a champ with the new RIL, and reception works - just gives a useless download link. Trying to make that link work, is what we're trying to do!

We checked to see what profile the Sprint RHOD400 was sending under Winmo and found this http://device.sprintpcs.com/HTC/PPCTP7380SP/2046514.rdf which seems to have the correct screen dimensions. (I can't seem to download it now though.)
Click to expand...
Click to collapse
I appreciate all the work that you've been doing, and especially for Sprint (even though you're on a GSM device ).
That site doesn't hit (I was hoping it was user-agent dependent, but it didn't work on my phone either).
Also, this thread (http://forum.ppcgeeks.com/htc-touch-pro-2/101286-native-htc-messaging-mms-fix-collaboration-31.html) says that there's no 1st P in the PPCT7380SP string, so it looks like http://device.sprintpcs.com/HTC/PPCT7380SP/%CDMA_ROM_VERSION%.rdf. Is anyone else able to download this .rdf file?
edit: and the 2046514 corresponds to the ROM version (found in Device Information/Software), which (for me at least) is 2.04.651.4

I don't get the download button on my RHOD500. Well it's there for a split second then downloads on it's own. Originally set the APN before all the ril changes so after setting the carrier ID it just worked with the new ril.

eww245 said:
I don't get the download button on my RHOD500. Well it's there for a split second then downloads on it's own. Originally set the APN before all the ril changes so after setting the carrier ID it just worked with the new ril.
Click to expand...
Click to collapse
Wait so Verizon CDMA MMS works?

rpierce99 said:
Wait so Verizon CDMA MMS works?
Click to expand...
Click to collapse
If I'm not mistaken, Verizon has been working ever since highlandsun's amazing work on the RIL originally.

manekineko said:
If I'm not mistaken, Verizon has been working ever since highlandsun's amazing work on the RIL originally.
Click to expand...
Click to collapse
If that's the case I really need a kind verizon user to provide me a download link for a MMS attachment. It's in mmssms.db, probably easiest for that person to hop on IRC so we can chat about it. Basically I need to figure out what is different about the Sprint payload than the Verizon payload to see why Sprint doesn't work.

rpierce99 said:
Wait so Verizon CDMA MMS works?
Click to expand...
Click to collapse
For me yes, no issues at all

rpierce99: you didn't get my note on IRC I guess. I'm pretty sure the attachment isn't the problem; pretty sure the problem is the original SMS PDU. You can grab that from the radio logcat when the MMS arrives. Decoding it is a bit more of a hassle; my code in the RIL only decodes the first 6 headers then passes the rest to Android to decode. Get me a sample PDU from your radio log...
I take that back. Now I see what the parser is doing...

Is this what you need?
The pdu table has some other info but connectbot isn't being nice
GSM_PDU=000002100402070295EA216506000601FC087600031257E0016703280010099199897B9B2B93B3632BA3997B6B6B99FB6B2B9B9B0B3B296B4B21E9820A19CA099989C9899A21C9818181821A19A1818181818981880448B401A9B981C1C1A9C9A189C17AA2CA8229EA82626A7004B233BB21D10233BB21D102A32B9BA34B7338000306110516223640
Click to expand...
Click to collapse

Sprint MMS receive is now working.
Yes, thanks. But I don't need it now, already got a copy.
We actually identified the problem several days ago, there's even a fix for it already in the Gingerbread source tree. But backporting the fix to Froyo was messy. I've now made a new fix that applies cleanly to Froyo and doesn't rely on the stupid compile-time settings that Google's fix uses. rpierce99 helped to verify that it works.
Basically the MMS server software that Sprint uses is mis-formatting what it sends out. The official specification for MMS/WAP says to do one thing, Sprint's MMS server does something completely different / wrong. The Android MMS parser would just die with an exception when trying to parse these things. The fix makes it ignore the improper header. There are other things that Sprint's server does that are also questionable. Even with this fix, if you want someone to send you an image or video in an MMS, make sure they don't type any text into the message body, otherwise it will still arrive messed up.

OK, the issues with displaying MMS image+text messages are resolved now too. And I've made the uaProfURL a settable property in case you want to override the compiled-in setting. set the ro.product.uaprofurl property to the URL you want to use.
Of course, you need to be running my patches to the Mms.apk for this to work. The source code is here https://gitorious.org/hycdroid/packages_apps_mms/commits/froyo
Full description of the Sprint bugs and the fixes: http://lists.xdandroid.com/pipermail/xdandroid-dev/2011-May/000288.html

So what was the initial problem here?
*scratches head*
MMS always physically worked fine for me. (your RIL)
Was it just an issue displaying the contents I never picked up on or...?

ryannathans said:
So what was the initial problem here?
*scratches head*
MMS always physically worked fine for me. (your RIL)
Was it just an issue displaying the contents I never picked up on or...?
Click to expand...
Click to collapse
Did you read his post? It's a Sprint-only issue. Always was (after his RIL).
Might want to look at this section of his post...
highlandsun said:
Full description of the Sprint bugs and the fixes: http://lists.xdandroid.com/pipermail...ay/000288.html
Click to expand...
Click to collapse

/facepalm...
Had a few late nights and unknowingly started reading from page 2.

Clicking a number to call in IE

Hey all,
Apologies if this has been asked before, I've scoured the search function but couldn't find it.
A feature I really miss from iOS and Android (I've had both) is where you look up a restaurant or something on your browser and it recognises the telephone number and underlines it.. so you just tap to call.
Right now I have to copy the number (or memorise it), go to the phone function and then create a new contact, paste the number and then call.
Is there an App or something that gives that functionality in WP (I have a HTC Titan with latest updates)?
Thanks,
K

Swisskom said:
Hey all,
Apologies if this has been asked before, I've scoured the search function but couldn't find it.
A feature I really miss from iOS and Android (I've had both) is where you look up a restaurant or something on your browser and it recognises the telephone number and underlines it.. so you just tap to call.
Right now I have to copy the number (or memorise it), go to the phone function and then create a new contact, paste the number and then call.
Is there an App or something that gives that functionality in WP (I have a HTC Titan with latest updates)?
Thanks,
K
Click to expand...
Click to collapse
something called 'send to my wp7' in marketplace.

drupad2drupad said:
something called 'send to my wp7' in marketplace.
Click to expand...
Click to collapse
I've just downloaded and set it up, and its useful (same as Chrome to phone on Android) but not what I meant. Essentially if I'm browsing the web on my phone, I want telephone numbers (on the web page) to automatically open up the phone program. All this is on the phone, not my PC.
Cheers

How are the numbers being formatted on the web page? IE9 I think looks for specific syntax.

ScottSUmmers said:
How are the numbers being formatted on the web page? IE9 I think looks for specific syntax.
Click to expand...
Click to collapse
Like (us of a numbers) 601-555-1234 just as you would dial them. The os pickes up a set of 7,10 or 11 numbers as phone numbers and dumps them to the dialer. Its the way it should have always been (nice)

I have Samsung Focus and running 7720 and I just tap the phone number on the web page and it take me to a screen asking if I want to call or store number.

Seed 2.0 said:
I have Samsung Focus and running 7720 and I just tap the phone number on the web page and it take me to a screen asking if I want to call or store number.
Click to expand...
Click to collapse
same here. Never had a single issue with this.

Same here... always works - is it do to the international settings? (Settings, swipe, phone, international assist)? i have mine on
Also in IE try changing from mobile to desktop version to see if it makes a difference.

ohgood said:
Like (us of a numbers) 601-555-1234 just as you would dial them. The os pickes up a set of 7,10 or 11 numbers as phone numbers and dumps them to the dialer. Its the way it should have always been (nice)
Click to expand...
Click to collapse
is the quoted phone number showing up as a link for anyone? Its not clickAble for me on 8107 with mobile or desktop setting. Also tried international assist setting and it had no effect as suspected.

One feature I miss from previous OSes is the lack of ability to paste a phone number in the dialer. It is not always the case that we are able to successfully dial a number by tapping on it.

bobzero said:
is the quoted phone number showing up as a link for anyone? Its not clickAble for me on 8107 with mobile or desktop setting. Also tried international assist setting and it had no effect as suspected.
Click to expand...
Click to collapse
Does not work for me, neither do national (Swiss) or other European numbers. I usually have the opposite problem with iOS etc.. i.e. any sequence of numbers (including serial numbers) being interpreted as a telephone number

419-685-5468
419.685.5468
(419) 685-5468
(419) 685 5468
(419)6855468
419 685 5468
4196855468
Do any of these show up as clickable? If so post your OS version
None are clickable on 8107 here.

bobzero said:
419-685-5468
419.685.5468
(419) 685-5468
(419) 685 5468
(419)6855468
419 685 5468
4196855468
Do any of these show up as clickable? If so post your OS version
None are clickable on 8107 here.
Click to expand...
Click to collapse
All but the last one were clickable for me (version 7720). I attached a screenshot of what I get with the first 6 numbers. Gives option to call, and edit number beforehand if necessary.

dtboos said:
All but the last one were clickable for me (version 7720). I attached a screenshot of what I get with the first 6 numbers. Gives option to call, and edit number beforehand if necessary.
Click to expand...
Click to collapse
Same results for me too. HTC Titan ATT 7720.

Interesting that it is working for you guys. I tried changing my region settings all to USA and now it is working was previously set to Canada.

Weird... report that one to MS... i would think it would urk a lot of people. I live in the US.

Not clickable to me. im using the dft v3 rom on my 7 Pro. How i have managed to pick up numbers from the browser is to copy the number, create a new contact and then call to the number. Leaving the name field empty makes that contact appear frist for easy calling and deletion after the call.
So bottom line here would be to get the paste option to the dialer. That is a WAY better solution to call numbers from the browser, than have the browser identify all numbers as phone numbers.

bobzero said:
is the quoted phone number showing up as a link for anyone? Its not clickAble for me on 8107 with mobile or desktop setting. Also tried international assist setting and it had no effect as suspected.
Click to expand...
Click to collapse
That phone number shows up as orange text that is clickable. I have my phone set to mobile view priority.
---------- Post added at 04:28 PM ---------- Previous post was at 04:26 PM ----------
dtboos said:
All but the last one were clickable for me (version 7720). I attached a screenshot of what I get with the first 6 numbers. Gives option to call, and edit number beforehand if necessary.
Click to expand...
Click to collapse
All but the last one work for me also. Plus the web page has to be 100% loaded before they are clickable.

I Did some more testing. The only value that seems to matter is your region format setting (second from the top) inside the region+location settings. Make sure it is set to united states. Everything else can be whatever.
Anyone have the ear of someone on the windows phone tem and could pass this bug on? There's no obvious reason why the Canadian region should not have the same clickable phone links as we generally use the same formats as our friends to the south. I would chalk this up as an oversight, Canada usually gets forgotten.
Also tested Australian, and it is not working for the above numbers, but then the Aussies use a different number format iirc.

adhoc125 said:
One feature I miss from previous OSes is the lack of ability to paste a phone number in the dialer. It is not always the case that we are able to successfully dial a number by tapping on it.
Click to expand...
Click to collapse
There are other dialers you can download that you can past phone numbers into. Give one of those a try.

[HOWTO][INFO]Editing the CSC file on your phone.

All samsung "touchwiz" based devices contain files in /system/csc that set variables dictating how certain parts of the phone act, what is pre-configured, etc. In the case of the AT&T variants, the contents of these files are often dictated by AT&T.
This post is an attempt to try and catalog some of the more useful values that can be changed (and the result of changing them.) Not all the variables seem to do much, and only by trial and error can we really know what will happen... So far, I've only played around with items I found interesting, but will continue to expand in this and if people reply to this post with actual experience changing other variables, I'll add the information to this thread.
PLEASE TEST THINGS AND CONTRIBUTE TO THIS THREAD.
Please don't reply with guesses as to what things may or may not do or with requests about specific variables. I'm hoping that eventually document every CSC variable available and "requests" won't make it go faster. If you want to know what a not-yet-documented variable does, try it out (and post your results.)
First, in order to play with the csc files, your phone should be rooted. This isn't optional, as you'll need the ability to overwrite files in the phone's /system partition (the firmware - sometimes improperly called the "ROM")
I'd strongly suggest making a nandroid (or backup via CWM Recovery or TWRP) before making changes. It's possible to mess things up badly enough that the phone won't boot properly.
It's possible to edit the CSC files directly on the phone, but I'd strongly suggest not doing that. Therefore, you should have a good text editor on your computer that's able to properly deal with unix/linux style line endings (notepad isn't good enough.) Notepad++ is a very good editor and freely available. Google "notepad++" For a linux box, plain "gedit" is fine.
In order to edit the files, you'll need to be able to mount the /system partition as read-write, and to move files from /system/csc to your PC or other location for editing. You have several options for this including root explorer, ES File Explorer, or just using adb. I prefer adb myself, but I'm a commandline type of person.
I won't be spending time describing how to get the CSC files off your phone to your PC, nor will I tell you how to overwrite the existing ones with your edits. This isn't because I'm elitist, an a**hole, or anything like that. (I _am_ some of those things, but that isn't my reason here.) My purpose for leaving out the information is to force inexperienced users to learn these things before editing system files. If I give you all the information, you become dependent on me for more information, and I don't want that (and trust me - neither do you.) As well, if I spoon-feed this, you won't have any idea what do to when something goes wrong.
Find this post helpful? If so, please make it MORE helpful by testing one of the other CSC features and replying to this thread telling us what result you had. ​
First up... feature.xml...

feature.xml
The CSC "feature.xml" file is in XML format. This means that everything "variable" has a start and end tag. Both contain the name of the variable,
but the end tag has a slash in it. The value of the variable is between the start and end tags. For example: <VariableName>value</VariableName>. So, if this message describes changing "CscFeature_SamsungSucks" from "false" to "true", you'd search in the xml file for "CscFeature_SamsungSucks" and might find this:
Code:
<CscFeature_SamsungSucks>false</CscFeature_SamsungSucks>
You'd change the "false" to "true" (no quotes!) and be done. In some cases, the entire line can be deleted (as noted.)
This file has a LOT of variables in it and this post will concentrate on that particular file. Almost all tinkering will occur in this file, and it's also the easiest to edit (as there aren't any complex xml structures.)
CscFeature_Common_DisableMenu4GalSearch: setting this to false didn't seem to bring up any new global address list options on my device (I'm connected to an exchange server) in the email app or contacts/dialer app.
CscFeature_Settings_DisableMenuFindMyMobile: (see next line)
CscFeature_Settings_FindMyMobile: setting "DisableMenuFindMyMobile" to false and this entry to true will enable the "find my mobile" entries in the Settings->Security menu. I'm unable to get these items to function properly, however. (They worked with my international note2, so it might be that there are other support files missing on the AT&T variant I'm using now.)
CscFeature_FMRadio*: editing these seem to have no effect (I don't think any of the LTE capable NoteII phones are capable of FM Radio.)
CscFeature_NFC_StatusBarIconType: If you delete this line, it will get rid of the "N" statusbar icon when NFC is turned on.
CscFeature_Message*: Be warned that editing some of these may break SMS/MMS messaging on your device. There appears to be many carrier specific settings in here that have dependencies on the specific carrier. For example, I don't think that AT&T's network supports proper SMS Delivery reports, so even setting the corresponding variable to "true" would be futile.
CscFeature_Email_UseFixedBgColorAsWhite: if changed from true to false, the email app will appear inverted (with a black background and white/gray text.)
CscFeature_Sip_DisableAutoCorrection: doesn't seem to have any impact on the samsung keyboard
CscFeature_Sip_DisableSpaceSuggestion: doesn't seem to have any impact on the samsung keyboard
CscFeature_Sip_DefaultOff4AutoSubstitution: doesn't seem to have any impact on the samsung keyboard
CscFeature_Launcher_*: all these seem to be for setting defaults for the touchwiz launcher, so no sense in changing them.

language.xml
(coming soon)
This appears to control what languages are available to the system. Canadian users might want to play with this file to see if adding en_US to the "Display" and/or "SupportList" tags will allow them to choose US English (and perhaps get google's TTS to talk to them in google now.)

others.xml
(coming soon)
This appears to set some carrier defaults, including the APN information and the carrier built-in dialer contacts (such as "AT&T Customer Care")

customer.xml
(coming soon)
I've only glanced at this file so far, but it appears to be carrier specified network information, some carrier specified settings defaults, and even some carrier specified browser bookmarks. There also appears to be some APN related information in here, but I'm not certain what it's in here for.

Nice how to guide man its very informative, im going to play around with this later when I get home...do you mind if I add it to my reference thread so it doesnt get lost when this thread begins to get bigger?
Sent from my SAMSUNG-SGH-I317 using xda premium

mjwhirly said:
Nice how to guide man its very informative, im going to play around with this later when I get home...do you mind if I add it to my reference thread so it doesnt get lost when this thread begins to get bigger?
Click to expand...
Click to collapse
This isn't mine to control. This "belongs" to the community, and I hope that the community contributes to it in a meaningful way. Please feel free to reference it elsewhere - perhaps with (contributions welcome) noted. My ONLY demand is that no one profits from effort I've given freely.
My secret motive is to nudge people out of the "MyRom" mentality and more into the "lets all work together to learn, develop and share" mentality often seen with kernels and open source projects.
Take care
Gary

Gary, have you seen the CSC feature web, set user agent?
Possibly an option to set "Desktop" as default user agent in browser, I for one despise mobile sites.

antiochasylum said:
Possibly an option to set "Desktop" as default user agent in browser, I for one despise mobile sites.
Click to expand...
Click to collapse
Not sure if this is what you are looking for or not: Start the browser, tap the "menu" button. Turn on the "desktop view" checkbox.
There are some UAgent related entries in the feature.xml file. Please play with them and post your results:
CscFeature_Web_SetUserAgent // currently empty
CscFeature_Web_SetUAProfile
CscFeature_Web_Bool_EnableUAProfile // currently false

Thanks so much for this. Sorry for the noob question but I haven't done much with xml files. What is the character to just comment out a line?
Sent from my SAMSUNG-SGH-I317 using xda premium

Romee74 said:
Thanks so much for this. Sorry for the noob question but I haven't done much with xml files. What is the character to just comment out a line?
Click to expand...
Click to collapse
In XML, in order to comment out a line (instead of completely deleting it), it has to be surrounded by special tags:
On the left of the commented out area, you need "<!--" (no quotes) and on the right, you need "-->"
See the below code block for an example.
Code:
<Is_This_Commented> false </Is_This_Commented>
<!-- <Is_This_Commented> true </Is_This_Commented> -->
Take care
Gary

On my Galaxy S III, the file /system/etc/feature_default.xml appears to contain default settings, and feature.xml can override those defaults. I'm not sure how comprehensive the list of settings in feature_default.xml are, but I would imagine that many of the available ones are covered there.

Thundersnuz said:
On my Galaxy S III, the file /system/etc/feature_default.xml appears to contain default settings, and feature.xml can override those defaults. I'm not sure how comprehensive the list of settings in feature_default.xml are, but I would imagine that many of the available ones are covered there.
Click to expand...
Click to collapse
That's interesting. Which variant of sgs3 do you have? Would you be willing to attach the two files to a reply in this thread (or point me to someplace I can find the firmware your using to investigate?)
Thank you
Gary

It would be amazing if we could somehow enable auto-replace on the samsung keyboard. I ended up switching to swiftkey because of how many mistakes I've been making with the stock keyboard, but now I don't get to take advantage of swipe, stylus writing, or the one-handed features...

UCLAKoolman said:
It would be amazing if we could somehow enable auto-replace on the samsung keyboard. I ended up switching to swiftkey because of how many mistakes I've been making with the stock keyboard, but now I don't get to take advantage of swipe, stylus writing, or the one-handed features...
Click to expand...
Click to collapse
I completely agree, but I wasn't able to get it working when tinkering with the CSC values (as noted in the corresponding post.) Perhaps there's some other combination of values that might get it going.
Please give it a try and let us know how it works out.
Take care
Gary

Removing the NFC icon from the staus bar is awesome but has anyone tried switching this line;
<CscFeature_NFC_DefaultCardModeConfig>DISABLE</CscFeature_NFC_DefaultCardModeConfig>
To enable? Im not sure why att would "block" this feature, especially with google wallet getting more support for non-nfc devices.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app

MonsterBandit said:
...but has anyone tried switching this line...
Click to expand...
Click to collapse
I'm not sure why people keep asking if other people have done this, that, or the other thing. TRY IT and let us know what happens.

garyd9 said:
I'm not sure why people keep asking if other people have done this, that, or the other thing. TRY IT and let us know what happens.
Click to expand...
Click to collapse
fair enough...thanks btw...im slowly growing the courage to make changes and explore deeper into these devices...changed the value to "ENABLE" (minus the quotes) and seemingly nothing changed. Google Wallet app still says Not supported. That might be on Google Wallet's end tho. I guess the better question might be has anyone with a Note 2 gotten Google Wallet to work?

When I first got my GN2 running stock, carrier billing worked. I then flashed Jedi 3.3, and it disappeared. I remember that on my HOXL, someone mentioned a fix on the build.prop. Is there anything I can do on the GN2's build.prop to get my carrier billing back?
I'm on AT&T by the way.

silentecho13 said:
When I first got my GN2 running stock, carrier billing worked. I then flashed Jedi 3.3, and it disappeared. I remember that on my HOXL, someone mentioned a fix on the build.prop. Is there anything I can do on the GN2's build.prop to get my carrier billing back?
I'm on AT&T by the way.
Click to expand...
Click to collapse
this is pretty much a how to thread ..
you seem to be having issues with a rom , you should post in there ..
here is how I fixed it in previous roms ..
compare your build.prop form your att rom to the one you are using ..
and add / replace with the att stuff .

Reverse Lookup?

Just got my new One today, came from a rooted and rom'd S3. One feature I miss, that I thought was just a KitKat feature is the reverse lookup when calling/getting called from businesses. Is there a way to enable that on here? Or is that a AOSP thing?

thegame3202 said:
Just got my new One today, came from a rooted and rom'd S3. One feature I miss, that I thought was just a KitKat feature is the reverse lookup when calling/getting called from businesses. Is there a way to enable that on here? Or is that a AOSP thing?
Click to expand...
Click to collapse
https://play.google.com/store/apps/details?id=com.esmobile.reverselookupfree
is this the sort of thing

jaythenut said:
https://play.google.com/store/apps/details?id=com.esmobile.reverselookupfree
is this the sort of thing
Click to expand...
Click to collapse
Kind of. It was actually built into the dialer. I was poking around, and it seems like that is a stock-Google feature built into the barebones google dialer. I might use this though! Thanks!

Reverse phone lookup is a service that allows anyone to trace a mobile or landline number or display information about the owner of the number. This includes name, address, and other contact details.This is a simple tool to find your caller information. Just you have to put his number and our system will give you the information about the number like owner name, address, email address and more.

Is there a way to replace TrueCaller?

I tried a number of things to get the Google dialer without success.
For now work with kk dialer, has anyone any idea how to get rid the TrueCaller?

Just don't use TrueCaller?

r25txe said:
Just don't use TrueCaller?
Click to expand...
Click to collapse
Thanks for nothing .
I have said that I have kk dialer, to install Google dialer am looking.

Open up the dialler and go to settings, the three dots, The top option is Truecaller you can turn it off

nikoslikos said:
Thanks for nothing .
I have said that I have kk dialer, to install Google dialer am looking.
Click to expand...
Click to collapse
I gave you the advice you wanted about Truecaller. As the previous poster stated, you can disable it, or, as I advised, simply not use it. Getting offended because someone took the time out to respond is terrible manners.
You may need to be rooted to remove it and we do not know if you are rooted. We don't know if you are running a Lollipop or Marshamallow ROM either. You have not helped us to help you by not giving us your platform information.
Have you tried to install the Google Dialer from the modular GApps thread?
Be warned that they are targeted to 32bit ROMs. Do a backup!
You could also try CM Next dialer from CM C-Apps package. This also includes Truecaller, but it is trivial to disable it.

I am rooted and am on stock TOS208G with trucaller uninstalled. I replaced with caller ID & call recorder app https://play.google.com/store/apps/details?id=com.callapp.contacts that I prefer.
I have found the phone does not display whose calling via contacts only by the true caller ap. Have I installed something in error or got a setting wrong please?

Trucaller help in many ways
r25txe said:
Just don't use TrueCaller?
Click to expand...
Click to collapse
It helps in many way to find out spam caller, customer care calls,
and know the number location carrier etc etc

thunderbolt9148 said:
It helps in many way to find out spam caller, customer care calls,
and know the number location carrier etc etc
Click to expand...
Click to collapse
Understood, but the poster doesn't want to use it.

r25txe said:
Understood, but the poster doesn't want to use it.
Click to expand...
Click to collapse
From what I have found, there is no caller id system on the phone without having one of the various true caller id apps installed.

image45 said:
From what I have found, there is no caller id system on the phone without having one of the various true caller id apps installed.
Click to expand...
Click to collapse
Caller ID is a stock feature of any basic dialer out there (Google/AOSP etc), it should not be dependent on True Caller.
I think True Caller is still on my Swift, so I will test this later.
Sent from my P00A using XDA Labs

r25txe said:
Caller ID is a stock feature of any basic dialer out there (Google/AOSP etc), it should not be dependent on True Caller.
I think True Caller is still on my Swift, so I will test this later.
Click to expand...
Click to collapse
Uninstall true caller id and see for yourself then, you don't have to trust the contents of members post if you so choose.

image45 said:
Uninstall true caller id and see for yourself then, you don't have to trust the contents of members post if you so choose.
Click to expand...
Click to collapse
I don't have TrueCaller on my device afterall. The dialer is the stock Android dialer and my caller ID works without issues.
What's the packagename for TrueCaller?
Sent from my P00A using XDA Labs

I wonder if I can restart this discussion here -- I want to turn off TrueCaller, but in Google Play it says it's a System App and it does not appear at all under any name in the Settings - Apps listing (no matter whether showing or hiding system apps). What other options do I have?
I'm on Android 7.1.2. My TrueCaller has no options to either turn it off or to turn off the notifications it brings up (which is my main reason for wanting to get rid of it: for something that's blocking spam, it spams me far too much with stuff that I don't want it to do).

r25txe said:
Caller ID is a stock feature of any basic dialer out there (Google/AOSP etc), it should not be dependent on True Caller.
Click to expand...
Click to collapse
This should indeed be the case. Unfortunately, for us Swift (1st gen) users at least, this is now broken.
When Wileyfox migrated from CyanogenMod to Android they broke a few things along the way as well as doing a deal with the Devil aka Truecaller.
Unless your device is Truecaller enabled then caller ID simply will not work. We've tested at least two dozen dialers and contact managers (all from Google Play) and not one of them works with the Swift in its current firmware state. We even installed the APK of the Google Phone dialer (provided by WF themselves and which according to Google Play is incompatible anyway) and even this does not work.
Besides, how many dialers does a mobile ecosystem need anyway? One has to ask themselves why there are so many and why they nearly always require OTA registration to do what they offer....
But that's another matter altogether.
There are other issues too such as SMS alerts going off at full volume in the earpiece during an active voicecall; or the persistence of 'charge mode' when connecting via USB, even though MTP has been set in the developer options or from the status pull-down.
One thing it tells us is that the Swift cannot be running stock Android - otherwise these problems just would not happen. If not that, then it is that WF don't have a proper working build process or test protocol.
Either way, the Swift is damaged goods now and it might seem WF are prepared to kick it into the kerb. Probably the best option now is to try Lineage, assuming owners are savvy and even want to.
On the other hand we could band together to oblige WF to get an update released. We have been trying for months to get their attention, both before and since their buyout by STK. For those who are minded to, perhaps you would like to add your support by liking the following Facebook post:-
https://www.facebook.com/officialwileyfox/posts/1872330073078309
If enough give it the thumbs up then WF may be moved to respond. Please support this initiative if you can.
Thanks.

gktscrk said:
I wonder if I can restart this discussion here -- I want to turn off TrueCaller, but in Google Play it says it's a System App and it does not appear at all under any name in the Settings - Apps listing (no matter whether showing or hiding system apps). What other options do I have?
I'm on Android 7.1.2. My TrueCaller has no options to either turn it off or to turn off the notifications it brings up (which is my main reason for wanting to get rid of it: for something that's blocking spam, it spams me far too much with stuff that I don't want it to do).
Click to expand...
Click to collapse
We think we have found a solution:-
It ought to be possible to disable Truecaller but not remove it entirely unless your phone is rooted and have other management tools. We have managed this is on our own device which is totally stock and never been tinkered with (7.1.2 Nougat, Build No: TOS257G – N2G48B).
Secondly, installing another dialler from Google Play or via APK will work but it's almost 100% likely that a further setting will need to be made: setting as the default phone app.
This can be done in two ways:-
i) Settings->Apps->Configure Apps (Gear icon in top bar).
ii) From the app drawer, drag the dialler app icon to the "App Info" drop zone at the top of the screen. Scroll down to the setting that says "Phone App" - it should be yes or no.
See attached screenshots for reference.
It seems to us that many owners think their Swift can't be used with any dialler other than Truecaller, when in fact they can; the mistake is on the part of the firmware which won't recognise another dialler by default and hence breaks the contact ID display when incoming calls are received (not to be confused with caller ID).
Hopefully this serves as a solution. :good: