Always make a backup before changing / on your device!
Q. What is this?
A. A way to change your region. More manufacturers in QRemote, Russian/Greek/etc T9 in dialer, working 4G, no wifi frequency restrictions and more.
Q. Will it get me OTA's of the region i changed to?
A. No.
Q. Is there any easier method, one that does not require root, perhaps?
A. I don't know one.
Boring technical details:
Latest firmwares do not "belong" to region. Instead, they adapt to phone's own region. The check is done at each boot, settings are applied after build.prop.
The detection uses combination of operator code and country code (2 bytes, numbering convention unknown. In LG's documents it's referred to as "BUYER").
LG determines phone's region by looking into the "misc" partition, at addresses 0000A000-0000A020.
Information at them looks like this:
Code:
"1","FFF,FFF,FFFFFFFF,FFFFFFFF,12"
, where "12" is country code.
We can change it ourselves by using hex editor on a dumped image.
The regional parameters reside in /cust/ folder. The file "/cust/cust_path_mapping.cfg" maps "{operator_code},{country_code}" to a folder where it's parameters reside.
Note: some countries (FRA, for example) or some operators don't have their own folder in /cust/. They use 11 (OPEN_EU) as NT code, and identify themselves based on some other info I've yet to find.
Example of cust_path_mapping.cfg content:
Code:
20810,FF=/cust/VDF_COM/FR
20810,01=/cust/VDF_COM/LPM
Explanation: Vodafone in any country but 01 will use "/cust/VDF_COM/FR", while Vodafone in "01" country will use "/cust/VDF_COM/LPM". Notice theirs relative positions. This means that only the most exact match is used, and creating "FFFFFF,FF=/cust/XDA" key won't point the phone towards XDA folder.
By changing this file - or changing the contents of the folder your "operator,country" combo is pointing to - you can change your phone's region to anything you want.
There is also a "/cust/cust.prop" file. It contains fallback to defaults, if phone was unable to determine needed folder, or it didn't exist, it uses "/cust/SUPERSET/".
! In 5.0 firmwares, annoying message stating that "current version not avaliable for user" shows up if the above happens.
The folders in /cust/ hold operator/country settings. LG named them this way: "OPERATOR_COUNTRY". There are 2 special values - OPEN for operator - which means any operator, COM for country - which means any country.
OPEN_XXX hold parameters for specific country. These folders may contain subfolders with parameters for smaller operators which operate only inside this country.
Example: OPEN_ZA, which contains folders for MTN and VDC operators.
XXX_COM contain parameters for specific operator. These folders may contain subfolders with parameters for specific countries.
Example: /VDF_COM is intended for Vodafone. It contains folders FR and LPM, which are intended for France and LPM (?).
{OPERATOR_COUNTRY} folders are intended for 1 combination of operator and country, they should not contain subfolders with settings for other operators/countries.
Example: PCL_IL, contains settings for one of Israel operators.
The method itself:
1) Install Busybox.
1) Look at /cust/cust_path_mapping.cfg and choose some region's code. The folder names are usually self-explanatory, and you can always look into /cust/{folder}/cust.prop to see to what ro.build.target_operator, ro.build.target_country and ro.build.target_region variables are set.
2) Execute the below code, replacing "\x31\x32" in "echo -n '\x31\x32'" with your chosen code. Examples: "\x35\x36" is 56 region, "\x37\x33" is 73 region and so on.
First line backs up your "misc" partition to /sdcard/misc.bin, you should copy this file to safe storage.
Code:
dd if=/dev/block/platform/msm_sdcc.1/by-name/misc of=/sdcard/misc.bin
echo -n '\x31\x32' | /system/xbin/dd of=/dev/block/platform/msm_sdcc.1/by-name/misc bs=1 seek=40991 count=2 conv=notrunc
reboot
Why did i use busybox's dd? Because in LG's 5.0 default dd was compiled without conv option...
Enjoy your new region!
Other methods:
Method 1: substitution.
Step 1: Find out which country your phone was meant to use ("Settings->About Phone-> Software" ). Find your current operator code. Using these, find currently used folder in /cust/. You can get to know folder's region by looking on it's name, or opening the {folder}/cust.prop file and looking at these keys:
Code:
ro.build.target_operator
ro.build.target_country
ro.build.target_region
They are pretty self-explanatory.
Step 2: Replace the folder's content with content from the region you want to change to.
Step 3: Reboot and be happy!
Method 2: via editing "misc" partition.
Be extra careful with "misc". This partition is unique for every phone. If it's damaged or wiped, things may get ugly.
I do not know a way of regenerating "misc", since it contains your bluetooth/wifi mac's and IMEI. AFAIK, It is only used for displaying that info in Android and for LG's updates - so you won't lose bluetooth/wifi/mobile data, but still...
Since it's also used for updates, PC suite and "ota updater" won't be able to update your phone anymore if this partition is damaged.
It may also have uses which we don't know about. Make a backup, save it to several clouds and 2-3 offline storages.
Do not proceed if you don't know what "hex editor", "backup" and "partition dump" are.
1) Grab misc with "dd if=/dev/block/platform/msm_sdcc.1/by-name/misc of=/sdcard/misc.bin".
2) Open misc.bin in any hex editor, go to address "0000A000" and look for this:
Code:
"1","FFF,FFF,FFFFFFFF,FFFFFFFF,12"
Change "12" or whatever number you have there to the one that you need. You can look into cust_path_mapping.cfg to determine it. Save the result to a new file, name it "misc_edited.bin".
3) Replace your misc with edited one: "dd if=/sdcard/misc_edited.bin of=/dev/block/platform/msm_sdcc.1/by-name/misc".
4) Reboot.
I have no idea about how PC suite and others will react to IMEI and country code mismatch. They probably won't care, but we don't know it for sure.
Method 3:
Warning, in 5.0 this will cause the annoying "Current version not avaliable for user!" message to show up at each boot.
1) Backup your rom and /cust/ folder.
2) In /cust/cust_path_mapping.cfg delete all lines except
Code:
999999,99=/cust/SUPERSET
.
3) Copy everything from /cust/{Your_desired_region} to /cust/SUPERSET.
4) Reboot.
Big thanks to my Russian comrades rxu, KestL and Beerukoff for pointing out important details!
Reserved.
Hi, thanks very much for this write up. I'm still a bit confused as to how to actually do this - and I'm thinking others might be as well since there haven't been any responses. Would you mind walking me through how to change the region for a phone purchased in HK? I would like to change it to the EUR region.
Would I open the cust.prop file within the HK folder and change the values for the three variables above to match the ones found in the cust.prop file within the EU folder?
Thanks.
Japultra said:
Hi, thanks very much for this write up. I'm still a bit confused as to how to actually do this - and I'm thinking others might be as well since there haven't been any responses. Would you mind walking me through how to change the region for a phone purchased in HK? I would like to change it to the EUR region.
Would I open the cust.prop file within the HK folder and change the values for the three variables above to match the ones found in the cust.prop file within the EU folder?
Thanks.
Click to expand...
Click to collapse
It would be better to change /cust/cust_path_mapping.cfg file. Open it, find the line "FFFFFF,54=/cust/OPEN_HK", change it to "FFFFFF,54=/cust/OPEN_EU" and reboot.
I'm using a custom based off a version that doesn't have my cust (SEA) so mine reverts to the default. I'm in the uk.
Other than having to delete the ltesettings apk I haven't noticed any problems. Do you think I would notice anything if I change the mapping to point at EU it would improve anything?
Nice write-up, very detailed. This seems very specific, do you know why you would want to do this? A scenario maybe?
YaDr said:
It would be better to change /cust/cust_path_mapping.cfg file. Open it, find the line "FFFFFF,54=/cust/OPEN_HK", change it to "FFFFFF,54=/cust/OPEN_EU" and reboot.
Click to expand...
Click to collapse
Thanks! That worked.
oracleoftruth said:
I'm using a custom based off a version that doesn't have my cust (SEA) so mine reverts to the default. I'm in the uk.
Other than having to delete the ltesettings apk I haven't noticed any problems. Do you think I would notice anything if I change the mapping to point at EU it would improve anything?
Click to expand...
Click to collapse
No, i don't think that you'll notice anything. You'll get more manufacturers in qremote and other very minor features.
sprremix said:
Nice write-up, very detailed. This seems very specific, do you know why you would want to do this? A scenario maybe?
Click to expand...
Click to collapse
Thanks!
Why you may want to change region:
1) QRemote contains a lot more manufacturers if ro.build.target_region is set to ESA. Since /cust/ is applied after build.prop, you'll have to edit it.
For example, in CIS region Western Digital is absent. It is officially sold here in Russia, there is no embargo or whatever. LG just decided that Russians doesn't have the right to control "WD TV live" using QRemote. Nice.
2) Dialer - there are special dialer overlays with letters used in specific regions. For CIS it contains cyrillic letters, for Greece it contains Greek letters, and so on.
3) Featureset.xml also depends on region. It contains miscellaneous settings, like the ability to send empty sms.
4) There are a lot more overlays for other apps. Voicemate, etc. Nothing major, but this can change in future.
P.S. I updated first post with info about misc partition.
Thanks @YaDr
Just changed the V10M Hong kong to EUR-XX.
One question: do i need to manually change/fix all the new files permissions?
robalm said:
Thanks @YaDr
Just changed the V10M Hong kong to EUR-XX.
One question: do i need to manually change/fix all the new files permissions?
Click to expand...
Click to collapse
No, until files have been exposed to non-posix filesystem and lost their permissions, or you've changed them manually.
Default permissions for /cust/ are 755 with root/root as owner/group.
YaDr said:
No, until files have been exposed to non-posix filesystem and lost their permissions, or you've changed them manually.
Default permissions for /cust/ are 755 with root/root as owner/group.
Click to expand...
Click to collapse
Ok.
In /cust/SUPERSET There is already a "cust.prop" file should i replace that one with the cust.prop from my OPEN_XX folder?
Is there a risk to loose/get blocked IMEI in this way we change region?
robalm said:
Ok.
In /cust/SUPERSET There is already a "cust.prop" file should i replace that one with the cust.prop from my OPEN_XX folder?
Is there a risk to loose/get blocked IMEI in this way we change region?
Click to expand...
Click to collapse
Yes, you should replace it.
It is highly unlikely that you will lose IMEI. However, i ask everyone to make a full nandroid backup, efs included, before you do anything to your phone.
As for the blocking... Why would your service provider care enough to blacklist your IMEI? Unless it is forbidden by local laws or service contract, manipulating files on your phone is perfectly legal.
YaDr said:
Yes, you should replace it.
It is highly unlikely that you will lose IMEI. However, i ask everyone to make a full nandroid backup, efs included, before you do anything to your phone.
As for the blocking... Why would your service provider care enough to blacklist your IMEI? Unless it is forbidden by local laws or service contract, manipulating files on your phone is perfectly legal.
Click to expand...
Click to collapse
Thanks bud.
I have a efs backup, but no nandroid backup.
YaDr said:
It would be better to change /cust/cust_path_mapping.cfg file. Open it, find the line "FFFFFF,54=/cust/OPEN_HK", change it to "FFFFFF,54=/cust/OPEN_EU" and reboot.
Click to expand...
Click to collapse
Hi
Need to erase all the rest lines or only change those 2?
Thank you
alexa74 said:
Hi
Need to erase all the rest lines or only change those 2?
Thank you
Click to expand...
Click to collapse
You only need to change 1 line. Nothing has to be deleted.
Did anybody tried if this works on the Korean models (F400S/L/K)?
YaDr said:
You only need to change 1 line. Nothing has to be deleted.
Click to expand...
Click to collapse
Hi
Thanks, it was helpfully,but may be you can help me to change the region to Israel?
alexa74 said:
Hi
Thanks, it was helpfully,but may be you can help me to change the region to Israel?
Click to expand...
Click to collapse
What's your current region?
YaDr said:
What's your current region?
Click to expand...
Click to collapse
Was HKG and now is EU
alexa74 said:
Was HKG and now is EU
Click to expand...
Click to collapse
in /cust/cust_path_mapping.cfg find a line ending with "OPEN_EU", and change folder name from "OPEN_EU" to "PCL_IL" or "ORI_IL". If you don't have these folders, i can zip them and send them to you.
Related
[REF] Manually change "sales code" (CSC selection) when multi-CSC won't allow you to
I've recently been getting annoyed with how, whenever I updated a firmware, on first boot the phone would still look for an invalid CSC code, which I had "removed" from the phone.
For example, none of the XEU CSCs currently available will allow you to change to / from XEU as those CSCs don't include other options. ... so if you've manually set your CSC to XEE using the *#272*IMEI# trick; there's no way to get back to XEU.
The solution is as follows: (yes, you need root)
1) Ensure the product code in your nvram.bin file is set how you want it, in this case XEU. (it's in the file twice, once on it's own and once at the end of the "I9100LKA" string. Both those should be at the end of line 215 of the file)
2) (and this is the new bit) - there's another file on the phone which stores the "Sales Code" - its the file that tells the phone what CSC to look for on first boot after flashing a firmware. This file doesn't change unless you can successfully use the *#272*IMEI# trick!
2a) Using a file browser that has root privileges, navigate to /efs/imei/ then look for the file "mps_code.dat"
2b) Open this file as a text document (making sure you're mounted R/W) and edit the string to whatever you want (in this case XEU). Note, you should only put in the 3 letter code, not the rest of the product code.
2c) Save the file and reboot the phone. Hey presto you're on a different CSC!
(and I *think* this trick works to change CSC (without actually installing one, obviously), without wiping the /data partition.
wow great work
ok maybe it's just me but I cannot locate the nvram.bin file anywhere????
I'm on ke7 cf rooted and using script manager to browse system, could u direct me pls as I am running around in circles here.
I found efs/imei and that is xeu but i'm stuck on abr somewhere and it's causing me a few probs.
what and where is this "nvram.bin" file ? thanks
c19932 said:
what and where is this "nvram.bin" file ? thanks
Click to expand...
Click to collapse
Anyone can point to where is this nvram.bin file is located please? i am searching for it using root explorer till my eyes are blurry now...still cant find it
Thanks
^^
You cannot see the contents of efs unless you are rooted!
reb73 said:
^^
You cannot see the contents of efs unless you are rooted!
Click to expand...
Click to collapse
With all due respect sir..yes I have root..but still can't locate the nvram.bin file. I found the rest but as per my understanding is...I need to change the value in the nvram.bin file aswell to make all this work.
Thanks again for all the help.
Sent from my GT-I9100 using Tapatalk
My method on SGS1 was to use custom rom from rom kitchen open that and just change the required CSC folder and files with new folder and files zip back up and install .
Does not work yet on SGS 2 due to being unable to rezip and install custom roms .
Work around has just been to copy the relevant \CSC folder and two CSC files + SW conf file to phone deleting originals . Files have been ripped from original firmware nandroid backup .
Factory reset and all changed .
jje
Ok dokie...thanks for the explanation.
Sent from my GT-I9100 using Tapatalk
iznee said:
Anyone can point to where is this nvram.bin file is located please? i am searching for it using root explorer till my eyes are blurry now...still cant find it
Thanks
Click to expand...
Click to collapse
No, because there is no "nvram.bin" inside the latest (-> KE2, KE7, KF1) stock firmwares!
And changing only "mps_code.dat" won't do the trick as this will only create a new "nv_data.bin" after next reboot.
And if you would delete this new "nv_data.bin" (hoping that the files will be recreated/replaced at next reboot, this worked with SGS like this) you will end up with NO ProductCode and an fake IMEI too! So you should be VERY careful modding anything inside of /efs!
I edited the nv data.bin as well from KOR to BTU is this not a wise thing to do on GS3?
Sent from my GT-I9300 using Tapatalk 2
Solution to Change sales code
How to change CSC sales code on Samsung Galaxy S2?
1.Just type *#272*Device IMEI# at Phone dial pad.
2.Select the CSC that you want.
3.Click Install.
4.Phone will be rebooted by itself.
5.That’s all.
goodie said:
I edited the nv data.bin as well from KOR to BTU is this not a wise thing to do on GS3?
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
I need to change my CSC on GS3 too, that has been locked using *#272*Device IMEI# method.
Did you have any success? If so are you able to please share instructions?
Carrier is just showing numbers on a AOSP rom I installed. I understand this is completely stripped but I was wondering how to setup the carrier name properly instead. I read that spn-conf.xml in /system/etc/ is what I should edit but there was no file so I created one and pushed it to the device with adb rebooted the device but no luck. Anyone know how to set this up? Thanks
maybe you lost the imei?
No phone works fine.. I know there is suppose to be a file that will read the numbers then display the carrier name. Before it use to be spn-conf.xml and you would setup the file as follows;
<spnOverride
numeric="302320" spn="Mobilicity"/>
</spnOverrides>
then push it to /system/etc and it would overwrite the file however in the new 2.3.5 this file is not present and was wondering if anyone with knowledge knows this. I would post in development but that is for projects and not for troubleshooting or chatting.
Thanks
Did you find a fix for this? I just installed CyanogenMOD 7.1 and am seeing these numbers as well (using Mobilicity on my Vibrant).
Just wanted to share a few CSC features that are tested to work on the S6/S6 edge.
This is not my work, just sharing.
To enable these you will need root, a root explorer and text editor.
Simply navigate to system/csc/Features.xml and add the corresponding line to the end of the file but before the very last few lines that say </feature> and </Samsung>
(if this file does not exist, create the csc folder in system and a txt file within it then change the name to features.xml and add the correct lines and save) if this does not work you can try the same method with Others.XML in the same folder
*Make sure you make backups of the stock files in case there are issues.*
Enable WiFi calling in phone settings:
Code:
<CscFeature_Setting_SupportWifiCall>TRUE</CscFeature_Setting_SupportWifiCall>
Enable native voice call recording(maybe illegal is some countries):
Code:
<CscFeature_VoiceCall_ConfigRecording>RecordingAllowed</CscFeature_VoiceCall_ConfigRecording>
Enable shutter sound switch in camera settings(maybe illegal is some countries):
Code:
<CscFeature_Camera_ShutterSoundMenu>true</CscFeature_Camera_ShutterSoundMenu>
Enable camera during call:
Code:
<CscFeature_Camera_EnableCameraDuringCall></CscFeature_Camera_EnableCameraDuringCall>
Enable manual rotation option in gallery:
Code:
<CscFeature_Gallery_AddAutoRotationIcon>true</CscFeature_Gallery_AddAutoRotationIcon>
Continuous music while using camera:
Code:
<CscFeature_Camera_CamcorderDoNotPauseMusic></CscFeature_Camera_CamcorderDoNotPauseMusic>
Enable scheduled messaging option in messaging app:
Code:
<CscFeature_Message_EnableScheduledMessage>true</CscFeature_Message_EnableScheduledMessage>
<CscFeature_Message_EnableScheduledMsgBox>true</CscFeature_Message_EnableScheduledMsgBox>
Enable exit buttons in default browser:
Code:
<CscFeature_Web_AddOptionToTerminate>true</CscFeature_Web_AddOptionToTerminate>
Enable 2nd symbol keys on stock keyboard:
Code:
<CscFeature_Sip_UseSymbolInCMKey>true</CscFeature_Sip_UseSymbolInCMKey>
<CscFeature_Sip_EnableSymbolInSecondary>de;en_US;en_GB</CscFeature_Sip_EnableSymbolInSecondary>
Enable VoLTE Support: Thanks to IakobosJ
Code:
<CscFeature_RIL_SupportVolte>true</CscFeature_RIL_SupportVolte>
<CscFeature_IMS_EnableVoLTE>true</CscFeature_IMS_EnableVoLTE>
Remove NFC enabled icon in the status bar: Thanks to evonc
Code:
[COLOR="Red"]Delete line[/COLOR] : <CscFeature_NFC_StatusBarIconType>DEFAULT</CscFeature_NFC_StatusBarIconType>
ADDED 21/04/15
Sort app draw alphabetically:
Code:
<CscFeature_Launcher_EnableViewByAlphabetAsDefault>true</CscFeature_Launcher_EnableViewByAlphabetAsDefault>
I Hope this helps someone out,
Big Thanks to this post for the info, there are many more in the original post but these are the only ones I've tried and have worked so far,
and IakobosJ for his help in the wifi calling thread
if anything needs adding let us know and it can be added to this post,
This is dedicated to the hard working XDA community
Thank You All
Theres also some nice tools in the play store -:- Be careful when using these!
Samsung CSC Master
CSC Feature Expert
(I own google so get a big cut of the profit made on these )
I've tried CSC Feature Expert now -and it seems to work well,
Quick tut:
I would backup original CSC folder first
Just search for the option you want to enable,
Select the value ( see pic 1)
in the popup - Input the correct value (see pic 2 - label 1)
(a few examples of values)
' RecordingAllowed ' to enable call recording,
' true ' for shutter sound menu,
' true ' for launcher by alphabet,
' true ' for rotation icon in gallery,
' true ' for support wifi call,
then click save (see pic 2 - label 2)
restart you device
Hope this helps
If only we could root, without tripping Knox.
I don't want to root my phone in fear that Samsung Pay won't work with a tripped Knox.
Nice to see you've put all of this information together
For those on EE you may also want to enable VoLTE. I know it's unlikely to be in anyones area yet, but they are rolling it out across the UK (Very slowly)
Enable VoLTE Support
<CscFeature_RIL_SupportVolte>TRUE</CscFeature_RIL_SupportVolte>
Enable VoLTE
<CscFeature_IMS_EnableVoLTE>true</CscFeature_IMS_EnableVoLTE>
Just a quick note that the commands have to be added before the
</FeatureSet>
</SamsungMobileFeauture> tags at the end of the file.
Tested the Call recording and Shutter sound edits. Worked great.
Lastly if you want to remove that ugly NFC enabled icon in the status bar, delete line
<CscFeature_NFC_StatusBarIconType>DEFAULT</CscFeature_NFC_StatusBarIconType>
from the file and it will hide the icon.
evonc said:
Just a quick note that the commands have to be added before the
</FeatureSet>
</SamsungMobileFeauture> tags at the end of the file.
Tested the Call recording and Shutter sound edits. Worked great.
Lastly if you want to remove that ugly NFC enabled icon in the status bar, delete line
<CscFeature_NFC_StatusBarIconType>DEFAULT</CscFeature_NFC_StatusBarIconType>
from the file and it will hide the icon.
Click to expand...
Click to collapse
Thats strange as I've added mine after the samsung tags and all is working fine fine on my device.
Have you had problems in the past with doing that?
No. I saw the file header and noticed they're inserting commands between those tags. The original guide also has that listed but I guess it may or may not work.
Also I believe the file may get reset when you enter stock recovery so I'm assuming this should work as a fix.
1. Open the sales_code.dat to find your csc code.
2. Open the folder above with the same code.
3. Navigate to <code>/system/csc and you'll see another others.xml
4. This is most likely the file that gets applied after a factory reset/activation.
5. Make changes to this file as well.
*Make sure you make backups of the stock files in case there are issues.*
evonc said:
No. I saw the file header and noticed they're inserting commands between those tags. The original guide also has that listed but I guess it may or may not work.
Also I believe the file may get reset when you enter stock recovery so I'm assuming this should work as a fix.
1. Open the sales_code.dat to find your csc code.
2. Open the folder above with the same code.
3. Navigate to <code>/system/csc and you'll see another others.xml
4. This is most likely the file that gets applied after a factory reset/activation.
5. Make changes to this file as well.
*Make sure you make backups of the stock files in case there are issues.*
Click to expand...
Click to collapse
I would have thought it would have had to be within those tags too. Only found it didn't when i wasn't paying attention while modding it. LoL
Nice tip. Thanks. hoping there's more cool things that can enabled with this, maybe some S6 exclusives finds .
I'm on the Sprint Edge and don't have that folder. I guess I'll create and see what happens
SantinoInc said:
I'm on the Sprint Edge and don't have that folder. I guess I'll create and see what happens
Click to expand...
Click to collapse
I didnt have it either . Just create the csc folder and make a txt file and change the name to others.xml. as the op states. infact ill post a copy with basic changes i the first post.
It works fine for me. hopfully you wont have any issues
I actually did have the folder. I was looking at the folder ". System" However, after adding those lines and saving it had no effect. Can you take a look at this to see if it's right?
Edit: can't upload the xml file.
SantinoInc said:
I actually did have the folder. I was looking at the folder ". System" However, after adding those lines and saving it had no effect. Can you take a look at this to see if it's right?
Edit: can't upload the xml file.
Click to expand...
Click to collapse
You'll have to zip it before you can upload it... or rename others.xml to others.txt
I've attached a basic others.xml with all functions listed in the OP
and an original copy of the EE csc folder that IakobosJ uploaded in the WIFI calling thread
(it would be good if everybody could upload their original csc folders for reference and backups in case someone messes up theirs by accident.)
You can just copy and paste my others.xml into the bottom of your own others.xml(backup yours first)
I've had to do this as XDA's forum system seems to have changed at least one of the lines I've posted, and I've even tried going back and editing and it keeps putting a space in the middle of one of them, so use the upload if your having trouble,
I've deleted all but this file in my csc folder and tested it to make sure there nothing else it depends on - everything is working fine on my device.
But feel free to upload your for us to have a look at
im confused?
i can already do wifi calling and most of these things already without root
im on tmobile
tiboric said:
You'll have to zip it before you can upload it... or rename others.xml to others.txt
I've attached a basic others.xml with all functions listed in the OP
and an original copy of the EE csc folder that IakobosJ uploaded in the WIFI calling thread
(it would be good if everybody could upload their original csc folders for reference and backups in case someone messes up theirs by accident.)
You can just copy and paste my others.xml into the bottom of your own others.xml(backup yours first)
I've had to do this as XDA's forum system seems to have changed at least one of the lines I've posted, and I've even tried going back and editing and it keeps putting a space in the middle of one of them, so use the upload if your having trouble,
I've deleted all but this file in my csc folder and tested it to make sure there nothing else it depends on - everything is working fine on my device.
But feel free to upload your for us to have a look at
Click to expand...
Click to collapse
Ok, I'm finally on a PC so I had a chance to zip that file and have uploaded it. IDK where I screwed up. I'm rooted, I found the System/CSC/Others file and made the proper edits and then saved it. The original file was automatically backed up. The permissions were the same as the original file. IDK what I did wrong.
SantinoInc said:
Ok, I'm finally on a PC so I had a chance to zip that file and have uploaded it. IDK where I screwed up. I'm rooted, I found the System/CSC/Others file and made the proper edits and then saved it. The original file was automatically backed up. The permissions were the same as the original file. IDK what I did wrong.
Click to expand...
Click to collapse
is it just call recording and shutter sound toggle you want to add?
I want to add the NO NFC notification, CALL RECORDING, WI-FI CALLING and NO SOUND for snapping pics.
SantinoInc said:
I want to add the NO NFC notification, CALL RECORDING, WI-FI CALLING and NO SOUND for snapping pics.
Click to expand...
Click to collapse
I've uploaded two versions, one with the feature you've asked for and a full featured one, both based on your original other.xml and tested on my device to be working
just copy one to your csc folder
let me know if you have any problems
tiboric said:
I've uploaded two versions, one with the feature you've asked for and a full featured one, both based on your original other.xml and tested on my device to be working
just copy one to your csc folder
let me know if you have any problems
Click to expand...
Click to collapse
I really appreciate the effort but that didn't work either. I used the file you uploaded for me and made sure the permissions were the same and rebooted. None of the mods worked. It's really weird. I'm going to inquire in the Sprint thread to see if anyone can get these to work.
Unrelated do you know which folder I can find the boot sounds and camera sounds? I'm just going to delete them and that will solve part of my problem.
SantinoInc said:
I really appreciate the effort but that didn't work either. I used the file you uploaded for me and made sure the permissions were the same and rebooted. None of the mods worked. It's really weird. I'm going to inquire in the Sprint thread to see if anyone can get these to work.
Unrelated do you know which folder I can find the boot sounds and camera sounds? I'm just going to delete them and that will solve part of my problem.
Click to expand...
Click to collapse
Thats a shame maybe sprint have changed something.
Sure its
/system/media/audio/ui/PowerOn.ogg
Hope this helps
Killed boot sound but I must have not found the right OGG file for the camera. Do you know the name of the file?
SantinoInc said:
Killed boot sound but I must have not found the right OGG file for the camera. Do you know the name of the file?
Click to expand...
Click to collapse
I believe its
/system/media/audio/ui/camera_click.ogg
P.s did you try any of the apps posted in the second post. I dont know how well the work but ghey seem to have good reviews
*edit* deleted thread. Unfortunately this doesn't fix it. QFIL then flashing EUI ROM 14s and then upgrading to a newer EUI ROM or device firmware update then custom ROM is the only true fix.
Sadly, it doesn´t work for mine, maybe you can help me?
Greetings.
Iceee44 said:
Sadly, it doesn´t work for mine, maybe you can help me?
Greetings.
Click to expand...
Click to collapse
Heyyo, hmm darn that's unfortunate... Well, I have a test build of LineageOS 15.1 for the Le Max 2 with the calibration fixes in place and same with the upcoming official weekly build of LineageOS 14.1 for the X2 this Saturday. It's up to you which you would want to try. Hopefully one of them will work for you.
If not? I'm unsure what else could be causing the issue then hmm...
Hey thanks for reply!
I don't why, but something worked!
I got the splitscreen bug, then I flashed the recovery to the newest twrp (the blue one, don't know which version, but I will look it up). Then I wiped everything and install your fix. Result = bricked. Another try with one flash 2.0 and no error from flash. Fastboot recovery flash and everything was perfect.
I think it was luck, but my leeco le max 2 is repaired :victory:
Wow that's lucky! Congrats on fixing it!
May I please ask what happened to cause the brick? I've heard of device bricking but haven't seen an exact answer as to what unfortunately caused it.
It was totally my fault... I Format my data...and no image on storage... And one flash did the screen problem, maybe the program doesn't decompress a file finally... I decompressed the qfil data two times... The first time I got an error, after full decompressed everything...
Ah if you format data without any ROM on the device you can always use a PC and USB cable to do this...
adb push NameOfROM.zip /sdcard
Which will copy the zip file to the root of your data storage. Same can be repeated for Gapps or Magisk, etc.
I tried to push a 1,8GB file...
But after 2 hours it wasn't transferred, so I found the software and this is much easier.
Could you explain what exactly the "Unbricked devices split screen" bug is?
So from understanding the changes, does this mean that the 4 profiles in the Display -> Colour mode menu won't actually activate for people with the issue? (So if they do change then you don't have the bug?)
I'm guessing that editing those xml files could help with this problem? https://forum.xda-developers.com/le-max-2/how-to/le-max-2-black-crush-survey-t3744594
Or are there other places where those parameters are set?
ThE_MarD said:
Heyyo, this is a TWRP flashable zip file to replace the broken formatting on the qdcm calibration xml files for the display panels used in the LeEco Le Max 2
Click to expand...
Click to collapse
Which bug your fix is intended to fix? Do you mean this: https://youtu.be/3yXnrkfsJMI - I have never seen it on my device.
Or you mean color calibration, which is currently terrible by default (too much yellowish)
oneNight1 said:
Could you explain what exactly the "Unbricked devices split screen" bug is?
So from understanding the changes, does this mean that the 4 profiles in the Display -> Colour mode menu won't actually activate for people with the issue? (So if they do change then you don't have the bug?)
I'm guessing that editing those xml files could help with this problem? https://forum.xda-developers.com/le-max-2/how-to/le-max-2-black-crush-survey-t3744594
Or are there other places where those parameters are set?
Click to expand...
Click to collapse
For both of these questions the hopes is that the main issue with most people who unbrick their devices having screen issues is due to calibration settings being lost which this in theory should restore as it would have XML files with proper formatting unlike before where stock EUI ROM for the Le Max 2 had broken calibration XML files.
In theory if the black crush issue is also a calibration issue there's a chance this could also fix it... But still, I haven't really looked into that as I was mainly looking for a better solution for those unfortunate people suffering from unbrick device woes. If it fixes it? Cool... If not? Then I'm not too sure. Calibration files could potentially be modified to fix black crush if the issue is in there that LeEco never addressed.
giaur said:
Which bug your fix is intended to fix? Do you mean this:
- I have never seen it on my device.
Or you mean color calibration, which is currently terrible by default (too much yellowish)
Click to expand...
Click to collapse
How do i view the config files and transfer them to my computer to compare them to yours? I enabled usb debugging, thinking that would let me see everything but when i connect to my computer with MTP mode i can only see standard files, not all the linux config files etc.
(edit: I tried using adb shell and i could view the root directory but it wouldn't let me access the config folder - permission denied. Do i need root access? If so, how do i get it temporarily and then remove it once i have transferred the files? I can't just run adb as root because you need root on the phone apparently).
Also i did a search of the available EUI x829 source (http://opensource.le.com/ or http://opensource.le.com/ or https://forum.xda-developers.com/le-max-2/how-to/source-code-available-t3482334 )and i couldn't find those xml files. Are they generated by the OS or something?
To me it seems like the files are probably already formatted correctly on my particular phone as changing the colour mode does appear to function. However they obviously seem to be not calibrated properly (or intentionally calibrated very badly).
I wonder if it only reads these files on boot? Otherwise i guess an application could be made to interactively adjust them.
I wonder if KCAL uses these files.
However from looking at how large the data is and also the mention of LUTs (lookup tables), it would seem that this is actually more advanced than kcal? And could potentially give proper screen calibration if using a colourimeter etc?
Of course, more than one profile would be necessary for different brightness levels though.
But anything is better than nothing.
It is definitely to do with the eui colour mode settings because if you go to google translate and translate the names in for each profile, they match up with colour mode options.
These are part of EUI ROM as I did mention the XML formatting is broken on all the EUI ROM versions I looked at.
You can use an Android ROM extractor like this to open up EUI ROM and see the files yourself if you'd like.
https://forum.xda-developers.com/android/help/extract-dat-marshmallow-lollipop-easily-t3334117
I found this https://usermanual.wiki/Pdf/KBA160907024936QDCMPCToolDebugGuide.968066270 which implies that the xml file is used directly.
Have you considered that <Calib_Data /> just means that the Calib_Data section is empty deliberately and that the colour profile and LUT sections were never intended to be within the calibration data tag?
We do not have the specification of the QDCM xml file that the tool generates.
It would be beneficial if the QDCM tool could be somehow leaked or obtained, then the end user could calibrate their phones. Or at least a specification of the file format of the QDCM xml files so correct data could be generated.
I suggest this should be brought up to the wider android community as it applies to all recent qualcomm phones.
Then we can compare with the QDCM xml files distributed with their handsets. Maybe some handsets even contain the same panels and therefore maybe we could attempt to use their profile / calibration settings. Of course it won't give perfect results because screens should be calibrated on an individual basis but it might be a lot better than the awfullness i currently have.
I wonder, do Le Eco calibrate each handset individually because if they do and then CFW overwrites the calibration with a "random" one then i can understand how that would cause issues. However my display has been bad before i loaded CFW... (unless the seller tampered with the FW but i don't know how you are meant to tell that).
I am not saying you are wrong but you have not given sources for your findings and to me, the individual colour profiles are working it's just that the overall calibration (or all of the profiles themselves) is extremely awful with huge black crush.
That tools seems to be for looking at backup images? But i want to view what is on my phone currently. Do you have to root your phone to do so? If so how can i root and then unroot it after i'm done?
Thanks
oneNight1 said:
I found this https://usermanual.wiki/Pdf/KBA160907024936QDCMPCToolDebugGuide.968066270 which implies that the xml file is used directly.
Have you considered that <Calib_Data /> just means that the Calib_Data section is empty deliberately and that the colour profile and LUT sections were never intended to be within the calibration data tag?
We do not have the specification of the QDCM xml file that the tool generates.
The way the XML formatting is? Calib_Data is supposed to house the entire XML file to let QDCM know where the calibration data starts and ends... So on the broken EUI ROM XML files it only has an end and never loads the calibration data.
It would be beneficial if the QDCM tool could be somehow leaked or obtained, then the end user could calibrate their phones. Or at least a specification of the file format of the QDCM xml files so correct data could be generated.
I suggest this should be brought up to the wider android community as it applies to all recent qualcomm phones.
Then we can compare with the QDCM xml files distributed with their handsets. Maybe some handsets even contain the same panels and therefore maybe we could attempt to use their profile / calibration settings. Of course it won't give perfect results because screens should be calibrated on an individual basis but it might be a lot better than the awfullness i currently have.
I wonder, do Le Eco calibrate each handset individually because if they do and then CFW overwrites the calibration with a "random" one then i can understand how that would cause issues. However my display has been bad before i loaded CFW... (unless the seller tampered with the FW but i don't know how you are meant to tell that).
I am not saying you are wrong but you have not given sources for your findings and to me, the individual colour profiles are working it's just that the overall calibration (or all of the profiles themselves) is extremely awful with huge black crush.
That tools seems to be for looking at backup images? But i want to view what is on my phone currently. Do you have to root your phone to do so? If so how can i root and then unroot it after i'm done?
Thanks
Click to expand...
Click to collapse
Heyyo, it's definitely a formatting error. XML standard has open and close brackets.
For example, the OnePlus 5T
https://github.com/TheMuppets/propr...b_data_samsung_s6e3fc1_cmd_mode_dsi_panel.xml
Or the Xiaomi Mi5 (Gemini)
https://github.com/TheMuppets/propr...calib_data_sharp_fhd_cmd_incell_dsi_panel.xml
As for viewing the files on your phone? Yes you would need root and a root file explorer.
Magisk, SuperSU, KingRoot or such all work for root but some versions of EUI ROM have issues.
For root enabled file browser? Amaze works... Amazing. Just get it from the Play store and then in settings enable root explorer.
For uninstalling root please Google the uninstall method to whichever root method you use as they are all different.
That's not true, XML tags can close themselves. If you don't believe me look here: https://www.w3schools.com/xml/xml_elements.asp (scroll down to empty xml elements)
How they had formatted their tags was valid xml.
Code:
<Calib_Data />
is just an element with nothing in it, the same thing as:
Code:
<Calib_Data> </Calib_Data>
However what you showed me from the other xml files for other phones make it look like it should be the way you have changed it
Okay i will have a look and let you know. I have small eui installed atm. So if you just flash an su to your system and then once you uninstall the app root is completely gone? I never would have thought it would be that simple.
It seems when you have root you can use an adb shell as root so i might try that rather than bothering to install anything on the phone.
Is there a way also to view what it was in the backup of my original fw without restoring it? (i used this guide for backup https://forum.xda-developers.com/le-max-2/how-to/protocol-backup-stock-rom-flash-stock-t3517151 ).
How can i find out which of the 3 display types my device is using? (Preferrably via adb).
I will be really surprised if it's wrong in mine because the colour modes work which will be very weird if that xml file isn't being used - they must do it another way too if that's the case :S
It's also weird how those xml files have been hand tampered with!
Thanks!
oneNight1 said:
That's not true, XML tags can close themselves. If you don't believe me look here: https://www.w3schools.com/xml/xml_elements.asp (scroll down to empty xml elements)
How they had formatted their tags was valid xml.
Code:
<Calib_Data />
is just an element with nothing in it, the same thing as:
Code:
<Calib_Data> </Calib_Data>
However what you showed me from the other xml files for other phones make it look like it should be the way you have changed it
Okay i will have a look and let you know. I have small eui installed atm. So if you just flash an su to your system and then once you uninstall the app root is completely gone? I never would have thought it would be that simple.
It seems when you have root you can use an adb shell as root so i might try that rather than bothering to install anything on the phone.
Is there a way also to view what it was in the backup of my original fw without restoring it? (i used this guide for backup https://forum.xda-developers.com/le-max-2/how-to/protocol-backup-stock-rom-flash-stock-t3517151 ).
How can i find out which of the 3 display types my device is using? (Preferrably via adb).
I will be really surprised if it's wrong in mine because the colour modes work which will be very weird if that xml file isn't being used - they must do it another way too if that's the case :S
It's also weird how those xml files have been hand tampered with!
Thanks!
Click to expand...
Click to collapse
Write this in the terminal.
Code:
cat /sys/devices/virtual/graphics/fb0/msm_fb_panel_info | grep panel_name
Thanks Sergio, so my device is running:
Code:
le_x2_mdss_dsi_truly_qhd_dualdsi_cmd_pvt
Hmm it seems that SmallEUI ( https://forum.xda-developers.com/le-max-2/development/rom-small-eui-5-9-aurel-battery-t3524531 ) wiped the configs folder. It looks the same through both ADB --> shell ---> su ---> cd config as it does through the Amaze app on the phone itself - empty.
I am pretty sure that I have root properly, supersu seems to be installed.
For some reason though, if i try and get ADB to get root, it says:
Code:
adbd cannot run as root in production builds
I don't have a folder named configs, only one called "config" and it is completely empty.
Is there any way to view the files that were in my TWRP backup of my stock X829 FW without reflashing it?
I have lots of data.ext4.win000 files etc. Which archive would it be in? System? Data? EFS? Boot? And how do i browse the archives?
Thanks
oneNight1 said:
Thanks Sergio, so my device is running:
Code:
le_x2_mdss_dsi_truly_qhd_dualdsi_cmd_pvt
Hmm it seems that SmallEUI ( https://forum.xda-developers.com/le-max-2/development/rom-small-eui-5-9-aurel-battery-t3524531 ) wiped the configs folder. It looks the same through both ADB --> shell ---> su ---> cd config as it does through the Amaze app on the phone itself - empty.
I am pretty sure that I have root properly, supersu seems to be installed.
For some reason though, if i try and get ADB to get root, it says:
Code:
adbd cannot run as root in production builds
I don't have a folder named configs, only one called "config" and it is completely empty.
Is there any way to view the files that were in my TWRP backup of my stock X829 FW without reflashing it?
I have lots of data.ext4.win000 files etc. Which archive would it be in? System? Data? EFS? Boot? And how do i browse the archives?
Thanks
Click to expand...
Click to collapse
You should notice this does not work, garbage screen is there even with this fix applied. I have it all the time on latest Lineage 15.1.
Okay I checked in
Code:
system/etc
and I do have the files. They are formatted as
Code:
<Calib_Data />
too.
Why does your github page say that they should be in
Code:
config/qcdm
???
Anyway, I flashed your zip to see if it would make a difference but it didn't help with the black crush sadly.
Although maybe modifying the calibration data would - but of course we would need to understand the format.
I checked my TWRP backup image (you can just browse them with 7zip) and they have the same empty tag too.
First of all credit to pomeroythomas for his post which I am basically just relaying here.
This is for anyone who wishes to use the native call recorder but it is currently disabled for them. For example in the USA federal laws state that call recording is legal and it is legal in most states but because some states require two party consent Lineage OS has decided to disabled it by default so this "HOW TO" is needed to enable it. You are ultimately the one responsible to follow any laws where you live.
This requires you to have root access. You may be able to accomplish the same with adb without root though.
You will need APK Easy Tool. For more information on APK Easy Tool visit the original thread here. I personally just used the portable version.
You will also need to know your carriers MCC code which you can find here.
1. There are many different ways to get the Dialer.apk from your device. Personally I use Root Explorer. Copy your Dialer.apk located on your device at "/system/priv-app/Dialer" to your sdcard and then connect your device to your PC and copy the Dialer.apk to it.
2. Now open "apkeasytool.exe and click "Sel.APK/JAR" and open your Dialer.apk and select "Decompile".
3. Once it has finished decompiling open the folder "1-Decompiled APKs" located in the APK Easy Tool folder.
4. The file we are looking for is in "Dialer/res/" this is where you need your MCC code. Personally I am on T-Mobile so the folder I need is "values-mcc310" most US carriers also use this same MCC code ie. Sprint, Verizon, AT&T
5. Once inside your carriers MCC folder you want to open "Bools.xml" in notepad and change
Code:
<bool name="call_recording_enabled">false</bool>
to
Code:
<bool name="call_recording_enabled">true</bool>
and then save it.
6. Now go back to APK Easy Tool and click "Compile"
7. Once it has finished your new Dialer.apk will be located in "2-Recomiled APKs". Copy that back over to your device
8. Navigate to "/system/priv-app/Dialer" and rename your current Dialer.apk to "Dialer.apk.bak" and replace it with your modified one and change the permissions to "rw-r-r" or "0644". and then reboot.
Thats it. Now to test make a phone call and you should now have the record button available, the first time you press it you will be greeted with a message telling you that you are responsible for compliance with any laws, then you can hit "RECORD CALL" and then give Dialer the permissions it needs. Your recording will be saved to a folder named "CallRecordings".
This will not survive an update but you can keep the modified Dialer.apk on your SDcard and just repeat step 8 after an update.
Joe333x said:
4. The file we are looking for is in "Dialer/res/" this is where you need your MCC code. Personally I am on T-Mobile so the folder I need is "values-mcc310" most US carriers also use this same MCC code ie. Sprint, Verizon, AT&T
5. Once inside your carriers MCC folder you want to open "Bools.xml" in notepad and change
Code:
<bool name="call_recording_enabled">false</bool>
to
Code:
<bool name="call_recording_enabled">true</bool>
and then save it.
Click to expand...
Click to collapse
I'm in kccat6, official LineageOS - Samsung Galaxy S5 Plus (G901F).
This procedure seems simple, but I have my carrier in Spain, where recording is allowed, and there is no MCC folder with its number.
I've found related settings (and I changed them) in
Dialer/res/values/bools.xml (changed false to true)
Code:
<bool name="call_recording_enabled">true</bool>
and
Dialer/res/values/integers.xml (changed 1 to 4)
Code:
integer name="call_recording_audio_source">4</integer>
Compiled (signed), copied, checked permissions, wiped cache & dalvik, rebooted and there isn't a record button when calling.
Also there's a "Dialer/res/values-es" folder, but there isn't a "Dialer/res/values-mcc214-mnc4" folder. I created that folder and copied the files bools.xml and integers.xml, with only the above contents inside them. Compiled, copied, etc... and there isn't a record button.
Am I missing something?
Ochoceros, its worked for me. I am using Lowi, MCC 214. The only stick, that its needed to press "record" button with every call, its doesnt records automaticali. I have created the folder with MMC code in his name and only the bools.xml file, without integers.
LOS made changes to native call recording, the phone checks what country your in instead of the MCC code. Has anyone figured out how to enable call recording again?
I found the new file, where you can edit the call recording states.
Follow the instruction from the first post, except don't follow step 4 and 5.
Go to "Dialer/res/xml/call_record_states.xml" and set everything to true (easiest way).
Now continue on step 6.
Now how about auto recording
Nice work Vanta-Chan!
eric93se said:
Now how about auto recording
Nice work Vanta-Chan!
Click to expand...
Click to collapse
I wish I could program, but we either have to wait for the official developers of LOS, or hope for a kind soul who does that with a tutorial :angel:
Interestingly the version of dialer.apk from the first post (around early november 2019) had auto dialing. I'm pretty sure that dialer version doesn't work with the latest LOS roms (I could be wrong).
I have a screenshot of it since I was trying to sell my LG G3.
eric93se said:
Interestingly the version of dialer.apk from the first post (around early november 2019) had auto dialing. I'm pretty sure that dialer version doesn't work with the latest LOS roms (I could be wrong).
I have a screenshot of it since I was trying to sell my LG G3.
Click to expand...
Click to collapse
If you somehow could retrieve that Dialer.apk, which has the auto-record function, I could try to reimplement it to the newer versions.
can anyone upload the apk, i try recompiling but always get an exit code = 1 error.
n950 said:
can anyone upload the apk, i try recompiling but always get an exit code = 1 error.
Click to expand...
Click to collapse
Can't upload it directly to XDA, file is too big (~33Mb), but here's a link:
https://workupload.com/file/URfFtrAU
Mirror: https://anonfile.com/zd6eO0b4oa/Dialer_apk
Vanta-Chan said:
Can't upload it directly to XDA, file is too big (~33Mb), but here's a link:
https://workupload.com/file/URfFtrAU
Mirror: https://anonfile.com/zd6eO0b4oa/Dialer_apk
Click to expand...
Click to collapse
Thank u )
I can recommend the EdXposed Module XCallRecordingSettings.
https://github.com/iptux/XCallRecording-xposed
https://repo.xposed.info/module/net.iptux.xposed.callrecording
Version 1.0.14 supports LOS 16
Works great for me and easy to setup!
I know, it's not the native way to setup, but I guess this Module justs enables the call recording the natural way in LOS
textmarker007 said:
I can recommend the EdXposed Module XCallRecordingSettings.
https://github.com/iptux/XCallRecording-xposed
https://repo.xposed.info/module/net.iptux.xposed.callrecording
Version 1.0.14 supports LOS 16
Works great for me and easy to setup!
I know, it's not the native way to setup, but I guess this Module justs enables the call recording the natural way in LOS
Click to expand...
Click to collapse
This would mean not only have to install your mentioned app, but also edxposed etc.
Which, IMHO slows down the s5
andreoide said:
This would mean not only have to install your mentioned app, but also edxposed etc.
Which, IMHO slows down the s5
Click to expand...
Click to collapse
Add:
On my g900f sound is great, on g910f sound is very weak, uninstalled all exposed from g901f because like I said, sound is bad and edxposed slows down performance very much.
Add: (march 1)
Anyone know why sound is no good on g901f?
What might cause it, and how to fix (if any exists)?
I have tried all of these steps and it didn't work i still can't get record button i have also tried the solutions in the replies and nothing worked how can i enable the recording in lineage os 16
The phone is GT-I9505
the country i live in is Egypt so can anyone help me please
I'm using lineage 17.1 which uses Google dialer, this method doesn't work.
Can you please describe how to make it work on Google dialer.
Sent from my MI 9 using Tapatalk
Vanta-Chan said:
If you somehow could retrieve that Dialer.apk, which has the auto-record function, I could try to reimplement it to the newer versions.
Click to expand...
Click to collapse
Shouldn't it be on GitHub history?
You bet!
Thanks for the credit, man. Hope this helps y'all.
Joe333x said:
First of all credit to pomeroythomas for his post which I am basically just relaying here.
This is for anyone who wishes to use the native call recorder but it is currently disabled for them. For example in the USA federal laws state that call recording is legal and it is legal in most states but because some states require two party consent Lineage OS has decided to disabled it by default so this "HOW TO" is needed to enable it. You are ultimately the one responsible to follow any laws where you live.
This requires you to have root access. You may be able to accomplish the same with adb without root though.
You will need APK Easy Tool. For more information on APK Easy Tool visit the original thread here. I personally just used the portable version.
You will also need to know your carriers MCC code which you can find here.
1. There are many different ways to get the Dialer.apk from your device. Personally I use Root Explorer. Copy your Dialer.apk located on your device at "/system/priv-app/Dialer" to your sdcard and then connect your device to your PC and copy the Dialer.apk to it.
2. Now open "apkeasytool.exe and click "Sel.APK/JAR" and open your Dialer.apk and select "Decompile".
3. Once it has finished decompiling open the folder "1-Decompiled APKs" located in the APK Easy Tool folder.
4. The file we are looking for is in "Dialer/res/" this is where you need your MCC code. Personally I am on T-Mobile so the folder I need is "values-mcc310" most US carriers also use this same MCC code ie. Sprint, Verizon, AT&T
5. Once inside your carriers MCC folder you want to open "Bools.xml" in notepad and change
Code:
<bool name="call_recording_enabled">false</bool>
to
Code:
<bool name="call_recording_enabled">true</bool>
and then save it.
6. Now go back to APK Easy Tool and click "Compile"
7. Once it has finished your new Dialer.apk will be located in "2-Recomiled APKs". Copy that back over to your device
8. Navigate to "/system/priv-app/Dialer" and rename your current Dialer.apk to "Dialer.apk.bak" and replace it with your modified one and change the permissions to "rw-r-r" or "0644". and then reboot.
Thats it. Now to test make a phone call and you should now have the record button available, the first time you press it you will be greeted with a message telling you that you are responsible for compliance with any laws, then you can hit "RECORD CALL" and then give Dialer the permissions it needs. Your recording will be saved to a folder named "CallRecordings".
This will not survive an update but you can keep the modified Dialer.apk on your SDcard and just repeat step 8 after an update.
Click to expand...
Click to collapse
pomeroythomas said:
Thanks for the credit, man. Hope this helps y'all.
.
5. Once inside your carriers MCC folder you want to open "Bools.xml" in notepad and change to
Click to expand...
Click to collapse
The last code is given twice, but my guess is change that only once?
(Just to be sure...)
Thanks, I'll go try one of these days, and report back here later....
( phone: Samsung galaxy S5 plus, SM- G901F )
The dialer.apk, I don't think I have the original from lineage, I installed the dialer from google play a while ago. How to obtain the original? Or does it work withe google dialer also?