Strange bug after modifying Settings.apk - AT&T, Rogers, Bell, Telus Samsung Galaxy S III

So I installed Mokee Rom (KitKat) and as I usually do on new ROM, I edited Settings.apk. I decompiled it with apktool and I added the lacking translated strings in values-fr, so that the app can be entirely translated in french. Then I recompiled it, I took the resources.arsc from the recompiled settings.apk and I copied it on desktop. I then used the file to overwrite the resources.arsc from the original Settings.apk. It did work and I now have a fully translated app. There's only one small bug, when I click on the option to limit sms message under Security section, the Settings app crash. It did not happen before I did my modification. What could cause this?

Related

HELP editing Phone.apk from Galaxy S CM9 to have full picture on the incoming calls

I want to modify the Phone.apk from teamhacksung CM9 B17 for Galaxy S.
What I want to do is to modify it that when I have an incoming call, to see the full picture of the caller. more precisely I want that the black rectangle where you have icon to answer or t reject, to be transparent.
It can be done. I got from the xda forum a moded Phone.apk for B16 where that rectangle is transparent.
I have attached a picture so that you understand what I'm talking about. i also have attached that transparent mod for B16.
Using Beyond Compare 3, I guess that I have to modify in the following file:
Phone.apk\res\layout\incall_touch_ui.xml and replace:
<com.android.internal.widget.multiwaveview.MultiWaveView android:id="@id/incomingCallWidget" android:background="@android:color/black" android:visibility="gone" android:layout_width="fill_parent" .......
with:
<com.android.internal.widget.multiwaveview.MultiWaveView android:id="@id/incomingCallWidget" android:background="@android:color/transparent" android:visibility="gone" android:layout_width="fill_parent" .......
Here comes the problem:
I decompile Phone.apk with Apk_Manager_5.0.2, change that word, save the file and the recompile.
After i install the phone.apk using a zip container from recovery, when I try to make a call or receive a call, I get the: "Voice calls not suported" error.
I tryed all the combinations for compiling: system app, signed/unnsigned; nonsystem app signed/unsigned. Same error.
What am I doin wrong? Any ideas?
Thanks.
similar problem here, but my Phone.apk just crashs
I've had similar issues on Samsung's GB ROMs. I had no problems with Contacts.apk, MMS.apk and DialerTabActivity.apk. I could easily recompile them and moded versions would work. But recompiled Phone.apk kept FC-ing so I eventually gave up.
I don't know what tools themers use to make it work.
After recompiling the Phone.apk open it with 7zip, extract the file that you have modified and put it in the original phone.apk.
Inviato dal mio GT-I9000 usando Tapatalk 2 Final
copying the file did work, thanks for that tip. However the mod did not work, the lower area is still black :-(
You need to change some files from the apk manager to compile android 4.0 files. I can upload my apk manager whitch works as soon as I get home.
those apk manager changes (it's actually not a single change in apk manager but just using apktools 1.4.1) are only related to the smali/dex files. layout/*.xml aren't influenced by that.
These are the changes that I was talking about:
"No problem I used Apk Manager 5.x(dont know exactly). But I've done this two things with the APK-Manager:
-deleted the original aapt.exe in /others and copied the one from the platform tools folder in from the sdk(has to be done if you work with ics apps)
-(de)compiled with Apk-tool 1.4.1 instead of 1.4.3 as the newer version sometimes causes some errors. Just delete the Apkttool.jar in /others and download 1.4.1 from the apk tool webite and paste it in /other
afterwards everything should work fine.."
i know those changes (see above), they don't solve the problem though.
apktool 1.4.1 + copy unchanged files (everything but ressources.arsc and incall_touch_ui.xml): FC
apktool 1.4.1 + don't copy: FC
apktool 1.4.3 + copy unchanged files: no FC but contact pic is still the old size
apktool 1.4.3 + don't copy: FC
same proble here with GS2.
this incoming call screen filled with black is very anoying...
any news on how to fiw that?
phone transparent incoming call
That app does wgat it is supposed, ask mr goodle, for i don't kjnow where i have found it
i made it AOKP build 37
Thats great, but can you explain how to do that?
Cause i' use GS2, and not GS, adn with different rom, we have to use differents phone.apk.
So instead of asking you every time, i'd like to learn how to do it.
Thanks!
Decompiled
Edited
Compiled
Signed
Hi. That's how I was able to do it:
First, copy your Phone.apk from the system folder inside your phone to your computer. Do not use any other Phone.apk, because it may be another version and it will not work. Or extract the Phone.apk from the rom that you flashed to your phone and use it.
You must make some changes to the apk manager to complie/decomplile Phone.apk.
Here is the list with the changes. If you follow it exactly, it should work:
-delete the original aapt.exe in /others and copy the one from the platform tools folder from the sdk(has to be done if you work with ics apps) - you must install android 4.0 sdk. Google it and you will find it easy.
-(de)compile with Apk-tool 1.4.1 instead of 1.4.3 as the newer version sometimes causes some errors. Just delete the Apkttool.jar in /others and download 1.4.1 from the apk tool webite and paste it in /other
afterwards everything should work fine...
Then, when you get the unsignedPhone.apk, rename it to Phone.apk, and put it in a zip file and flash via recovery. Do not copy it with inside the phone because it will not work. If you don't know how to make a zip file, just download any mod (perka, reloaded ...) and open the zip with 7zip, delete any apk's you find in it, and drag Phone.apk inside the System folder from the zip, and then flash it via recovery.
Good luck.
If it does't work, send me an email: [email protected], and I will send you my apk manager that is allready modified and works to compile/decompile.

I modified framework-res.apk to modify apn.xml and now random reboots...ideas?

After I modified my framework-res.apk I now get random reboots on my stock, rooted, deodexed 4.67 rom.
Here is what I did with APK Manager 5.0.2
-Option 22 to set project.
-Option 10 decompile apk, added com.htc.resources.apk for dependencies
-Modified the apns.xml and changed the mms.sprintpcs.com to mm.myboostmobile.com
-Option 11 to compile and I selected it was a system apk and deleted apns.xml and resourcse.aspc from the keep folder.
-Added it to my roms zip and resigned the rom.
Now I get random reboots. Did I do something wrong?

[Q] Theme improperly compiled

I decompile the OutlineCyanogenModTheme.apk and edit somethings [apktool metod] signed the apk and compiled again, but when I apply the theme, this happen - This theme was improperly compiled and cannot be applied.Please report this incident to the theme author.
Am i doing some thing wrong?
I want modify MMS background.
(files and pictures are attached)
Sorry for my english.

SOLVED: [Q] apktool compile error: need HELP

Hoping an "apktool" wizard can help me resolve a compile error driving me up a wall. I've been using apktool for past 6 months successfully making various system and data apk changes, but this one has me stumped. Experimenting with making a few simple color changes in my active Gmail v4.5.2 (inverted theme) apk. It successfully decompiles, but cannot recompile. To eliminate any of my changes, I started over and decompiled the Gmail apk... then immediately recompiled, but get the "No resource identifier found for attribute..." error (attached). I updated my JAVA and re-installed apktool... same issue. Anyone have guidance on what the issue might be? attaching screenshot of my CMD window commands in both WORD and PDF formats. Thx
EDIT: SOLVED I got it solved thanks to recognized themer "Ticklefish" in the UK. Turns out, the apk I was editing included 4.2 code (WidgetCategory)... and apktools could not handle this during recompile with my 4.1.2 framework. I just edited the 4 xml files which had the 4.2 code and removed those lines... made my theming edits... and it recompiled flawlessly. Then signed the apk and pushed to /system/app. If anyone else runs into similar apktool compile errors, this is why and how to resolve.

[NST/NSTG] Multilanguage and modified Settings.apk for 1.2 firmware

For NST/NSTG with 1.2 firmware​
Hi, new NTSG owener here
After reading this thread I've decided to make similar mod for 1.2 firmware.
NOTE: this was tested on rooted 1.2 firmware on NSTG but should work fine also on NST
Modifications in framework-res.apk:
-added languages: the same as in original mod
-replaced some images: by default not-localized ones had ugly "X" painted on top, now they look as for English locale
Modifications in Settings.apk:
-all languages are now visible in language picker ( <extra android:name="hideDevLanguages" android:value="false" /> in xml/settings_locale.xml) removed due to SetupWizard incompatibility (com.bn.oobe doesn't like this)
-added Development Options in main menu (changes in xml/settings_root.xml and xml/settings_root_gossamer.xml- first file is for NSTG, second for NST)
-locale picker is present in Development Options
-added Sync & Settings submenu
If you wish to play further with Settings.apk I can recommend this tutorial (it's for ICS but workflow is the same for Eclair).
Downloads:
All files are CWM flashable zips
NSTG-MULTI-1.2.x-flash.zip -modified framework-res.apk
NSTG-settings-accounts-1.2.x.zip -modified Settings.apk
RESTORE_FRAMEWORK.zip -restore stock framework-res.apk
stock-settings.zip -restore stock Settings.apk
Remember to make a full backup before flashing anything​
Updated Settings.apk- now Accounts & Sync is available
NST owners- please post feedback, I can't test modifications on your hardware.
EDIT:
Removed modded settings.apk due to SetupWizard incompatibility, testing alternate solutions
EDIT EDIT:
Modded Settings.apk back online.
BIG FAT WARNING
Settings.apk is deeply tied to other B&N system apps, Setup Wizard will fail with a modded one.
So if you want to use it keep original one around in case of data wipe
PERFECT! just what I wanted.. hey this DOES have Japanese on it right?
as in.. the list that said..
languages with better support by android:
Click to expand...
Click to collapse
EDIT: nope no Japanese... lemme see if I can add it in myself
MadHatterRyu said:
nope no Japanese... lemme see if I can add it in myself
Click to expand...
Click to collapse
Languages were taken from 2.1 Samsung EU rom.
I've used Android Multitool
If you want to add language:
1.Grab a 2.1 rom which has your language onboard, decompile framework-res.apk,
-copy /res/values-[desired language code]/ folder which includes arrays.xml, plurals.xml and strings.xml
-copy /res/raw-[desired language code] folder
2. Decompile Nook's framework-res.apk
-put both previously extracted folders to /res
-copy any of existing /res/raw-XX to /res/raw-[desired language code] -this folder holds localized images
-compile apk
-there will be warning about missing strings in translation- dont' worry, system will use english ones
-copy AndroidManifest.xml file and /META-INF from original framework-res.apk to newly compiled one (apk is a zip)
3. Replace framework-res.apk in a flashable zip and flash it
I'd advise to wipe dalvik-cache after flashing (just in case)
And better don't use modded Settings.apk, language picker can be accessed in Nook Color Tools.
Sorry, I didn't find a way to make modded Settings work in SetupWizard (oobe.apk in reality)
EDIT:
And better check if fonts support japanese
ahead of that.. I just wanted it to recognize Japanese characters.. only had to add ttf files into the fonts folder.
(oddly the stock reader doesn't do that.. meh, I didn't like it to begin with.. I'm using AIreader) but thanks though : )
This looks great! Thanks, @gen_scheisskopf. Due to this mod's being created, I'm now working on my own modified Settings.apk.
ИΘΘK¡€ said:
Due to this mod's being created, I'm now working on my own modified Settings.apk.
Click to expand...
Click to collapse
I'd suggest to take a look at dependencies, AFAIR settings.apk depends on B&N apks (this is most likely why my modified apk only FC-ed when booting system after a wipe)
gen_scheisskopf said:
I'd suggest to take a look at dependencies, AFAIR settings.apk depends on B&N apks (this is most likely why my modified apk only FC-ed when booting system after a wipe)
Click to expand...
Click to collapse
Check. I've got the beta version of my Settings.apk working famously on my NTG - here's the project thread.

Categories

Resources