Example of ADB pull command Question - Nexus One General

Hi everyone,
I'm trying to pull the htcime fill from my nexus so as to do what is described on this website
http://ostebaronen.dk/changing-htc_ime-language-to-danish/comment-page-1/#comment-8407
I want to make it so I can change the input languages at will without having to go to settings and change the local.
My adb attempts have been successful, ie ./adb devices gives me the serial number so I know I'm connected, but when i try the following command:
./adb pull /data/data/com.htc.android.htcime/shared_prefs/com.htc.android.htcime_preferences.xml .
all i get is the menu that tells me what all the commands mean.
I'm on a mac, using terminal. I cd into the tools folder in the android sdk on my desktop and would like to pull the above file from my phone to my desktop.
Could you please tell me what it is that I'm doing wrong?
Thanks in advance...I've searched high and low, on this site and others, that's how I discovered to add the ./ on mac
Also, what is the correct adb push line as well....thanks again
Lou

For one, cause that file doesnt exist.
Nexus doesn't have HTCime installed

I know, but I added it.
I kept trying and managed to do it by putting a space before the last . so i was able to pull the file, change it, and push it back into the phone.
The only problem now is that it doesn't do exactly what I want it to do.
I want to have the option of changing back and forth between french and english dictionary, but the changes I made make it so that I can keep the system in English, but use a french dictionary. here is the xml
<?xml version='1.0' encoding='utf-8' standalone='yes' ?>
<map>
<string name="keyboard_types">1</string>
<boolean name="predict_qwerty" value="true" />
<int name="MODIFIED" value="0" />
<boolean name="keyboard_ime_settings_pcqwerty_wc" value="true" />
<boolean name="keyboard_ime_settings_fqwerty_prediction" value="true" />
<boolean name="customized_kb_type" value="true" />
<string name="keyboard_language">0</string>
<boolean name="keyboard_ime_settings_others_vibration" value="false" />
<boolean name="predict_1220" value="true" />
<boolean name="keyboard_ime_settings_pcqwerty_sc" value="true" />
</map>
by changing the 0 to 1 here
<string name="keyboard_language">0</string>
I can have the french dictionary.
Is there a string I can add to give me the option between 0(english) and 1(french)
I tried copying the exact same string with the values changed under it, but it only takes the top one.
Lou

Related

view flipper

i have some doubts related to view flipper in android
1>when to use setAnimation and setInAnimation/setOutAnimation? or what the difference between them?
2>can u decipher push_left_in.xml in animation folder(available in sample folder in sdk) as i have to make push_right_in.xml ?
HTML:
<set xmlns:android="http://schemas.android.com/apk/res/android">
<translate android:fromXDelta="100%p" android:toXDelta="0" android:duration="300"/>
<alpha android:fromAlpha="0.0" android:toAlpha="1.0" android:duration="300" />
</set>

[GUIDE] How to change the number of stock launcher screens of JB ROM [Launcher2.apk]

Hello guys,
I received quite some messages / requests to write a guide on how to change the number of screens of JB ROM for team EOS by modifying the launcher2.apk;
So, I decided to share with you what I did with thanks go first to runandhide05 for his valuable help...
This guide is not only applicable to EOS ROM, but also to any JB ROM for XOOM and other devices with /system/app/launcher2.apk.
Tools Required:
APKTOOL: http://dl.dropbox.com/u/65414192/apktoo_8.15.12.zip
7zip
Notepad++: for file editing
GUIDE:
1) grap /system/app/launcher2.apk: To be modded.
2) grap /system/framework/framework-res.apk: Needed for apktool environment
3) download apktool and extract it. Say: C:/
4) open command line, cmd, and navigate to where you extracted apktool
5) place framework-res.apk in the apktool folder where it was extracted.
6) install the framework-res.apk by typing: apktool if framework-res.apk
7) place the launcher2.apk in the apktool folder where it was extracted.
7) decompile launcher2.apk by typing: apktool d Launcher2.apk
8) after successful decompilation, the output folder will be :\were\extracted\zip\is\Launcher2\
9) Make the below changes:
Here are the files you need to modifiy:
res/layout-port/launcher.xml
res/layout-land/launcher.xml
res/layout-sw720dp/workspace.xml
res/values/public.xml
res/values/ids.xml
To decrease the number of screens; example from 5 to 3:
- change launcher:defaultScreen="2" to launcher:defaultScreen="1" where 1 is the middle screen of the 3 screens. numbers convension are 0,1,2.
- From:
<include android:id="@id/cell1" layout="@layout/workspace_screen" />
<include android:id="@id/cell2" layout="@layout/workspace_screen" />
<include android:id="@id/cell3" layout="@layout/workspace_screen" />
<include android:id="@id/cell4" layout="@layout/workspace_screen" />
<include android:id="@id/cell5" layout="@layout/workspace_screen" />
- To:
<include android:id="@id/cell1" layout="@layout/workspace_screen" />
<include android:id="@id/cell2" layout="@layout/workspace_screen" />
<include android:id="@id/cell3" layout="@layout/workspace_screen" />
- And public.xml in res/values in which I had to delete
<public type="id" name="cell4" id="hex val xxxxx" />
<public type="id" name="cell5" id="hex val xxxxx" />
To increase the number of screens; example from 5 to 7
- change launcher:defaultScreen="2" to launcher:defaultScreen="2" where 3 is the middle screen of the 7 screens. numbers convension are 0,1,2,3,4,5,6
- From:
<include android:id="@id/cell1" layout="@layout/workspace_screen" />
<include android:id="@id/cell2" layout="@layout/workspace_screen" />
<include android:id="@id/cell3" layout="@layout/workspace_screen" />
<include android:id="@id/cell4" layout="@layout/workspace_screen" />
<include android:id="@id/cell5" layout="@layout/workspace_screen" />
- To:
<include android:id="@id/cell1" layout="@layout/workspace_screen" />
<include android:id="@id/cell2" layout="@layout/workspace_screen" />
<include android:id="@id/cell3" layout="@layout/workspace_screen" />
<include android:id="@id/cell4" layout="@layout/workspace_screen" />
<include android:id="@id/cell5" layout="@layout/workspace_screen" />
<include android:id="@id/cell6" layout="@layout/workspace_screen" />
<include android:id="@id/cell7" layout="@layout/workspace_screen" />
- And public.xml in res/values in which I had to add
<public type="id" name="cell6" id="hex val xxxxx" />
<public type="id" name="cell7" id="hex val xxxxx" />
xxx is the hex code for the vale id. You have to make sure that this code is unique and it is not present anywhere. You cannot use an existing value. So, to make it easy,
you open the pulic.xml file and check the last code used; increment by 1 for each added configuration; example: if the last hex code used in the file is 0x7f0d0017, you use 0x7f0d0018 and 0x7f0d0019
Hex codes are from 0 -- F [0,1,2,3,4,5,6,7,8,9,a,b,c,d,e,f] if the last digit of the code is 9 and you want to increase, then 9 + 1 = a;
- Note: ids.xml
if you are adding more screens, then in ids.xml you have to add instances.
<item type="id" name="cell6">false</item>
<item type="id" name="cell7">false</item>
if you are decreasing the number of screens, no need to add, just keep them 5, they are false anyway.
10) compile the apk: in cmd type
apktool b Launcher2
11) now navigate to :\were\extracted\zip\is\Launcher2\build\apk\
12) copy the original Launcher2.apk from :\were\extracted\zip\is\ to :\were\extracted\zip\is\Launcher2\build\apk\
13) OPEN not extract the apk with 7zip
14) and now click and highlight from the :\were\extracted\zip\is\Launcher2\build\apk\ the res folder the classes.dex file and the resouces.arsc and drag them into the root of the Launcher2.apk that is open in 7zip
15) close 7zip and the file is now ready to be pushed / flashed in device.
Attached is a ready flashable script that can be used to flash your modded file through recovery.
Installation:
1) download the sample flashable zip
2) extract it and put your modded launcher2.apk in \system\app\
3) rezip
4) put your flashable zip in SD CARD.
5) boot into recovery and flash it.
6) reboot.
I have made stock launcher screens ready (1,3,5,7,9 screens) ready in here:
http://forum.xda-developers.com/showthread.php?t=1836783
ENJOY

Bypass Security in WP8.1 Gain access in the WPSystem sub files & folders.

I’ve successfully bypassed the security of DRM Encryption Technology. The bug that I have found can access the WPSystem folder installed on the SD Card Memory. I have successfully bypassed all the security which is embedded by OS DRM Encryption Technology and now I can handle DRM Decrypted Files & Folders.
I also had it tested on NOKIA LUMIA 630 which is running latest Windows Phone8.1 (officially released firmware version for user device)& it works perfectly.
It is not a need Interop Unlock, or no Need Developer Unlock too.
It is free from any unlocking method. (I don’t do illegal things.) Just doors are opened, just go ahead.
It’s a very Tricky Method.
METHOD OF BYPASS:
P.S. :
To Whomsoever it may concern:
In order to avoid any sort of confusion in understanding and interpretation of my method of bypass I have tried to put all the steps in utmost detail and and the simplest language possible which can be understood even by a layman in the field.
Thank you.
First of all you have to install two file managers from the marketplace on any Windows Phone. Install both File Mangers on Phone Memory (C:\ Drive).
1. WINDOWS EXPLORER. (Version 1.0.0.5) (.Xap File Attached)
Description: - This gives better access on DRM Encrypted Files of system files. It can read copy and share operations on DRM Encrypted Files.
(It’s is paid version, but you can try it. No need to buy).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2. POCKET FILE MANAGER. (Version 4.2.3.0)
Description: -This app is best file manager. It shows HIDDEN FILE SUPPORT such as WPSystem,read and write operations.
We will take an example.Let’s try using Metrotube Application to view the installed files of it. Once you get the full access then you can do all operations such as read/write.
i. MetroTube (Version 4.1.4.0)
Store link:-http://www.windowsphone.com/en-in/store/app/metrotube/8d93224f-2808-e011-9264-00237de2db9e
Description: - MetroTube is YouTube client application & it is paid app. You can try it for the demo.
__________________________________________________________________________________
STEP 1 –
Open the windows explorer application. You can view there two drives C: / (Phone memory) and D: / (SD card).
STEP 2 -
Open the D: / drive. You can view several folders and files but WPSystem folder is not visible here.
STEP 3 -
To get the WPSystem folder visible you have to go to the above cmd bar. Then Manually type the path as “D:\WPSystem\Apps” and tap on go.
STEP 4 -
Now you can view System Files which are under this folder. Those all are the installed system files, such as Application installed programs.
STEP 5 -
You can access all folders and files, but as we have considering Metrotube application as an example, we shall open its directory. {8D93224F-2808-E011-9264-00237DE2DB9E}
You will see the folders such as Install, NI, XBF...etc.
STEP 6-
Now open the “Install” folder, now you will see only those applications program files which are supported by the ”Windows Explorer” having the extensions such as *.JPG, *.PNG, *.XML etc. They all are DRM Decrypted and accessible and you can read them.
But you can’t read the other program files because they are invisible due to the lack of application support. such as *.dll, *.XAML and other such extensions.
To get the visibility of the above listed files follow the further steps.
STEP 7-
Open the Pocket File Manager Application.
(Please note that only old version of Pocket file manager can support WPSystem folder and its sub folders and files. If you can’t get the old version then you can try the alternate method which is listed in below-
1. Remove memory card from the mobile device.
2. Insert that card in the computer using memory card reader.)
Then go to the WPSystem directory and rename the Apps folder to any name (xyz, abc, pqr) I have used “Appszzz” to get the access of its internal folder and files.
STEP 8 -
Then go to the “WPSystem\Appszzz\{8D93224F-2808-E011-9264-00237DE2DB9E}\install\“directory. Now all folders and files are visible such as *.dll but those are DRM Encrypted so you can’t read those files.
Just add the extension “.txt”(which is supported by Windows Explorer app) to view the file in Windows Explorer app. i.e. - (LazyTube.dll.txt, AppManifest.xml.txt)
STEP 9-
Again rename the “WPSystem\appsz” folder to its original name “WPSystem\Apps”.
STEP 10 -
Go to the “Metrotube”Application Install directory through Windows Explorer.
Now all the program files of the Metrotube application are visible to you.All these files are DRM Decrypted. So now you can do various operations on these files. (Read, Copy, Share)
STEP 11-
Copy the whole install folder on to the public directory (D:/).
So you have copied all DRM Decrypted files from the WPSystem folder.
So nowon is free to use or misuse the DRM Decrypted Files in any which way possible.
I did all worked without a computer and that’s my pleasure.
If you liked this one.
Please donate me, support me. For buying a computer so that i can do more research and development.
I don’t have a computer at my home. I’ve found this bug without a computer.
Thank you
Regards
Amol Baikar.
Good
---------- Post added at 10:12 PM ---------- Previous post was at 10:10 PM ----------
It works.good job
I have no SD card on my Lumia 1020 what now
phoy18 said:
Good
---------- Post added at 10:12 PM ---------- Previous post was at 10:10 PM ----------
It works.good job
Click to expand...
Click to collapse
Thanks man
I'm sure there are other methods to do this faster and this is no security issue for me with this you can't interop unlock your device or do access the phones system. But it is goodto see people trying to get full access to the system.
sisqo88 said:
I'm sure there are other methods to do this faster and this is no security issue for me with this you can't interop unlock your device or do access the phones system. But it is goodto see people trying to get full access to the system.
Click to expand...
Click to collapse
Do i mis something?
Whats the point of renaming the app folder.
sisqo88 said:
I have no SD card on my Lumia 1020 what now
Click to expand...
Click to collapse
920 here
Guess we can't do anything since the actual phone's storage isn't as easy to get to. Baby steps I guess.
Nice work OP!
Good find, but you made a lot of fuss for something that I don't think it's so useful for devs.
Offtopic: How can you be an "electronic music producer", as your twitter account state, without a personal computer?
I have an idea. Is that method lets us write something into the hidden folders of the apps that stored into Internal Memory? If yes, maybe we can add/modify something to high privileges (interop or more) apps from Nokia or Microsoft to make some app that might able to write needed registry key/value? Just guessing...
See no help in that method to unblock regular Skype account (not Microsoft one) logging in into latest versions of Skype (see that thread for more). The only reason I wish my Lumia 620 interop-unlocked is to might been able to install an old Skype version that supports it. I did found some unlocked/openable XAPs but all they have ID_CAP_INTEROPSERVICES manifest string, can't be sideloaded with it and doesn`t work (starts then crashes) after sideloading when string is removed.
Probably riff box+jtag method is applicable for me but that hardware costs more than my phone and it`s hard to get it in Russia.
I like to thx the OP
Finaly i can change some app ( not all ) tiles, so they blend in in my homescreen.
Never thougt of that.
Useful or not; let the devs decide but give credit where it's due for time, work, and ingenuity. At least it shows that there are chinks in WP8's armor. As someone posted earlier...babysteps. Congrats @djamol

			
				
Nice! Go ahead, thx for sharing.
Okay,
Just used this methode to change some tiles.
Bey bey red anoying pinterest
And the green Tweakers......
Also reedited #1 Toolkit and flashlight
Hmm.. Kinda newbie topic, with a lot of pics & bull****... What kind of "hack" are you talking about?..

			
				
spavlin said:
View attachment 2812894
View attachment 2812895
Click to expand...
Click to collapse
How can you browse those folders ?
contable said:
How can you browse those folders ?
Click to expand...
Click to collapse
Add ID_CAP from IO Explorer
spavlin said:
Add ID_CAP from IO Explorer
Click to expand...
Click to collapse
I´m a bit confused. Which ID_Cap do you mean ?
Code:
<?xml version="1.0" encoding="utf-8"?>
<Deployment xmlns="[URL]http://schemas.microsoft.com/windowsphone/2014/deployment[/URL]" AppPlatformVersion="8.1">
<DefaultLanguage xmlns="" code="en-US" />
<App xmlns="" Title="Windows Explorer" RuntimeType="Silverlight" Version="1.0.0.0" Description="Sample description" ProductID="{abfe6f86-ea26-4433-ac3a-d6e53f9af89b}" Genre="apps.normal" IsBeta="false" Author="Annan Zubair" Publisher="Annan Zubair" PublisherID="{60a650d5-7e0c-450d-b3e1-5dd734547b02}">
<IconPath IsRelative="true" IsResource="false">Assets\ApplicationIcon.png</IconPath>
<Capabilities>
<Capability Name="ID_CAP_MAP" />
<Capability Name="ID_CAP_NETWORKING" />
<Capability Name="ID_CAP_MEDIALIB_AUDIO" />
<Capability Name="ID_CAP_MEDIALIB_PLAYBACK" />
<Capability Name="ID_CAP_MEDIALIB_PHOTO" />
<Capability Name="ID_CAP_MEDIALIB_PHOTO_FULL" />
<Capability Name="ID_CAP_SENSORS" />
<Capability Name="ID_CAP_WEBBROWSERCOMPONENT" />
<Capability Name="ID_CAP_INTEROPSERVICES" />
<Capability Name="ID_CAP_DEVICE_MANAGEMENT_SECURITY_POLICIES" />
<Capability Name="ID_CAP_DEVICE_MANAGEMENT_ADMIN" />
<Capability Name="ID_CAP_OEM_DEPLOYMENT" />
<Capability Name="ID_CAP_CSP_FOUNDATION" />
<Capability Name="ID_CAP_CSP_OEM" />
<Capability Name="ID_CAP_CSP_W4_APPLICATION" />
<Capability Name="ID_CAP_INTERNET_EXPLORER_SEARCH_PROVIDER_KEYS_HKCU" />
<Capability Name="ID_CAP_REMOVABLE_STORAGE" />
<Capability Name="ID_CAP_PUSH_NOTIFICATION" />
<Capability Name="ID_CAP_OEMPUBLICDIRECTORY" />
<Capability Name="ID_CAP_PUBLIC_FOLDER_FULL" />
<Capability Name="ID_CAP_OFFICE_LAUNCH_URL" />
<Capability Name="ID_CAP_STORAGE_MANAGEMENT" />
<Capability Name="ID_CAP_CHAMBER_PROFILE_DATA_RW" />
<Capability Name="ID_CAP_CHAMBER_PROFILE_CODE_RW" />
<!--<Capability Name="ID_CAP_INTERNET_EXPLORER_HKCU_WRITE" />
<Capability Name="ID_CAP_PM_INSTALL" />
<Capability Name="ID_CAP_PM_BSS" />
<Capability Name="ID_CAP_PM_1ST_PARTY" />-->
<Capability Name="ID_CAP_MAP" />
<!-- Available for non-interop-unlocked apps; may give a little more access -->
<Capability Name="ID_CAP_APPOINTMENTS" />
<Capability Name="ID_CAP_CONTACTS" />
<Capability Name="ID_CAP_GAMERSERVICES" />
<Capability Name="ID_CAP_IDENTITY_DEVICE" />
<Capability Name="ID_CAP_IDENTITY_USER" />
<Capability Name="ID_CAP_ISV_CAMERA" />
<Capability Name="ID_CAP_LOCATION" />
<Capability Name="ID_CAP_MEDIALIB_AUDIO" />
<Capability Name="ID_CAP_MEDIALIB_PHOTO" />
<Capability Name="ID_CAP_MEDIALIB_PLAYBACK" />
<Capability Name="ID_CAP_MICROPHONE" />
<Capability Name="ID_CAP_PHONEDIALER" />
<Capability Name="ID_CAP_PUSH_NOTIFICATION" />
<Capability Name="ID_CAP_PROXIMITY" />
<Capability Name="ID_CAP_REMOVABLE_STORAGE" />
<Capability Name="ID_CAP_RINGTONE_ADD" />
<Capability Name="ID_CAP_SENSORS" />
<Capability Name="ID_CAP_SPEECH_RECOGNITION" />
<Capability Name="ID_CAP_VOIP" />
<Capability Name="ID_CAP_WALLET" />
<Capability Name="ID_CAP_WALLET_PAYMENTINSTRUMENTS" />
<Capability Name="ID_CAP_WEBBROWSERCOMPONENT" />
<!-- The following require interop-unlock and capability-unlock -->
<Capability Name="ID_CAP_ACCESS_FAMILY_NOTES_API" />
<Capability Name="ID_CAP_APPPREINSTALL_DIRECTORY" />
<Capability Name="ID_CAP_BINGCLIENT_OSS" />
<Capability Name="ID_CAP_CHAMBER_PROFILE_CODE_RW" />
<Capability Name="ID_CAP_COMMS_SERVICES" />
<Capability Name="ID_CAP_COMMS_APPLICATIONS" />
<Capability Name="ID_CAP_COMMS_COMMON" />
<Capability Name="ID_CAP_COMMANDCHANNEL" />
<Capability Name="ID_CAP_CSP_FOUNDATION" />
<Capability Name="ID_CAP_CSP_OEM" />
<Capability Name="ID_CAP_CSP_WIFI_HOTSPOT" />
<Capability Name="ID_CAP_DU_SHARED_DATA" />
<Capability Name="ID_CAP_DUASVC" />
<Capability Name="ID_CAP_EDM_CACHE_WRITE" />
<Capability Name="ID_CAP_ENDPOINTDISCOVERY" />
<Capability Name="ID_CAP_ENTERPRISE_SERVICE" />
<Capability Name="ID_CAP_INPUT_CORE" />
<Capability Name="ID_CAP_INPUT_SERVICE" />
<Capability Name="ID_CAP_INTERNET_EXPLORER_FAVORITES" />
<Capability Name="ID_CAP_INTERNET_EXPLORER_SEARCH_PROVIDER_KEYS_HKCU" />
<Capability Name="ID_CAP_LEXICONUPDATE" />
<Capability Name="ID_CAP_MAP_ADMIN" />
<Capability Name="ID_CAP_MEDIALIB_INT" />
<Capability Name="ID_CAP_MEDIALIB_PHOTO_FULL" />
<Capability Name="ID_CAP_OEM_ADC" />
<Capability Name="ID_CAP_OEMPUBLICDIRECTORY" />
<Capability Name="ID_CAP_OFFICE_LAUNCH_URL" />
<Capability Name="ID_CAP_PLAYREADY_ADMIN" />
<Capability Name="ID_CAP_PUBLIC_FOLDER_FULL" />
<Capability Name="ID_CAP_RETAILDEMO_CLIENT" />
<Capability Name="ID_CAP_RUNTIME_CONFIG" />
<Capability Name="ID_CAP_SEARCHMAPS_SHAREDCONFIG" />
<Capability Name="ID_CAP_SEND_TO_ONENOTE" />
<Capability Name="ID_CAP_SOUND_CONTROL" />
<Capability Name="ID_CAP_SPEECH_GRAMMARS" />
<Capability Name="ID_CAP_SPEECH_RECOGNITION_SYSTEM" />
<Capability Name="ID_CAP_TELEMETRY_ADMIN" />
<Capability Name="ID_CAP_WIFI_ADMIN" />
<Capability Name="ID_CAP_WPTOOLS_INSTALL_FOLDER" />
<!-- -->
</Capabilities>
<Tasks>
<DefaultTask Name="_default" NavigationPage="MainPage.xaml" />
</Tasks>
<Tokens>
<PrimaryToken TokenID="File_ExplorerToken" TaskName="_default">
<TemplateFlip>
<SmallImageURI IsRelative="true" IsResource="false">Assets\SquareTile71x71.png</SmallImageURI>
<Count>0</Count>
<BackgroundImageURI IsRelative="true" IsResource="false">Assets\SquareTile150x150.png</BackgroundImageURI>
<Title>Windows Explorer</Title>
<BackContent></BackContent>
<BackBackgroundImageURI></BackBackgroundImageURI>
<BackTitle></BackTitle>
<DeviceLockImageURI></DeviceLockImageURI>
<HasLarge></HasLarge>
</TemplateFlip>
</PrimaryToken>
</Tokens>
<ScreenResolutions>
<ScreenResolution Name="ID_RESOLUTION_WVGA" />
<ScreenResolution Name="ID_RESOLUTION_WXGA" />
<ScreenResolution Name="ID_RESOLUTION_HD720P" />
</ScreenResolutions>
</App>
</Deployment>

[SHARE][TUTORIAL][HOWTO]disabling/Enabling option for system APP

hi,
in different customization of the same device for region or operator , we find some option in system configuration enabled in some and other no then we can do it by changing variable value in application files in system by decompiling and recompiling after modifying ( bools or arrays...etc ) it take a lot of time
so customization Sony has choose to make a little files for a region customization or enabling or disabling option in system app without modifying the original app file by using {real_application_name}-res.apk what will be adding in /system/vendor/overlay
in 4.0.4 and before sony ericsson used /system/etc/customization/ folder for enabling and parameterizing apps, so in JB 4.2 and 4.3or 4.4 these files are incompatible only 4.3 and 4.4 are compatible (attached files)
for JB 4.2
4.3 and 4.4
How to use ??
example :
for enabling data traffic notification and status icon in status bar we must change in or semcphone.apk phone.apk this line after decompiling Phone.apk or SemcPhone.apk in res/value/bools/xml we find a default value of application :
Code:
<bool name="data_connection_except_mms_can_clear_icon">true</bool>
<bool name="data_connection_except_mms_show_icon_when_disabled">true</bool>
<bool name="data_connection_except_mms_show_icon_when_enabled">false</bool>
Click to expand...
Click to collapse
they must be change to :
Code:
<bool name="data_connection_except_mms_can_clear_icon">false</bool> ----->[COLOR="red"] icon always visible can't be removed[/COLOR]
<bool name="data_connection_except_mms_show_icon_when_disabled">true</bool>
<bool name="data_connection_except_mms_show_icon_when_enabled">true</bool>
Click to expand...
Click to collapse
then it can be inserted in com.phone-res.apk and injected in system/vendor/overlay and rebooting after that the options are activated.
just know what value to want be activated in the main application apk
Another exemple :
in this post http://forum.xda-developers.com/showthread.php?t=2703113 to have mod for activating low cost in conversations.apk but with decompiling main apk conversations.apk but the simple one is using -res.apk
default value are :
Code:
<bool name="character_conversion">false</bool>
<bool name="character_conversion_visibility">false</bool>
Click to expand...
Click to collapse
and must be changed to
Code:
<bool name="character_conversion">true</bool>
<bool name="character_conversion_visibility">true</bool>
Click to expand...
Click to collapse
then modifing com.sonyericsson.conversations-res.apk
after decomiling
we have
Code:
[CODE]
[/CODE]
res
|-------> bools.xml -------------> to be modified
|-------> public.xml ---------------important contains all variable defined
bools.xml
Code:
<?xml version="1.0" encoding="utf-8"?>
<resources>
<bool name="three_digit_number_linkify">true</bool>
<bool name="delivery_report">true</bool>
<bool name="mms_retrieval_during_roaming_visibility">true</bool>
[COLOR="Red"]<bool name="character_conversion">true</bool>
<bool name="character_conversion_visibility">true</bool>[/COLOR]
</resources>
public.xml
Code:
<?xml version="1.0" encoding="utf-8"?>
<resources>
<public type="bool" name="three_digit_number_linkify" id="0x7f020000" />
<public type="bool" name="delivery_report" id="0x7f020001" />
<public type="bool" name="mms_retrieval_during_roaming_visibility" id="0x7f020002" />
[COLOR="red"]<public type="bool" name="character_conversion" id="0x7f020003" />
<public type="bool" name="character_conversion_visibility" id="0x7f020004" />[/COLOR]
<public type="bool" name="enable_send_empty_message" id="0x7f020005" />
<public type="integer" name="max_recipients" id="0x7f030000" />
<public type="integer" name="mms_max_size" id="0x7f030001" />
<public type="integer" name="sms_max_segments" id="0x7f030002" />
<public type="integer" name="mms_trigger_sms_segments" id="0x7f030003" />
</resources>
and recompile , push it in system/vendor/overlay and done.

CarrierConfig VoLTE / VoWiFi

Hi all
I'm running a Nexus 6P on a carrier which does not support volte / vowifi officially. But I managed to get all the specific values for this carrier. But the big question is, how to implement those values into the phone?
I did some research and found out that some parameters are specified in the carrierconfig app. An example:
HTML:
<?xml version='1.0' encoding='utf-8' standalone='yes' ?>
<carrier_config_list>
<carrier_config>
<int name="vvm_port_number_int" value="1808" />
<string name="vvm_destination_number_string">122</string>
<string name="carrier_vvm_package_name_string">com.tmobile.vvm.application</string>
<boolean name="carrier_volte_available_bool" value="true" />
<string name="vvm_type_string">vvm_type_cvvm</string>
<boolean name="carrier_volte_tty_supported_bool" value="false" />
<boolean name="carrier_wfc_ims_available_bool" value="true" />
<boolean name="carrier_ims_gba_required_bool" value="true" />
<int name="maxMessageSize" value="1048576" />
<int name="maxImageWidth" value="2592" />
<int name="maxImageHeight" value="1944" />
<int name="volte_replacement_rat_int" value="3" />
</carrier_config>
</carrier_config_list>
Search for platform/packages/apps/CarrierConfig to find it
So I tried to decompile the carrierconfig app and add my carrier aswell, but unfortunately I can not install the app again (parsing error, defect package). But where is the rest of the data stored (P-CSCF address, used algorithms, ePDG address and so on) ?? How was VoLTE / VoWiFi Calling brought to AOSP roms for EE and T-Mobile USA??
Thanks for your help!

Categories

Resources