Ok this is a quick little guide. Decided not to put this in the notification text thread as that needs to be cleaned up anyway.
This is for modifying .xml's in say /values or wherever you want. This particular example is going to use /values/styles.xml
First up, decode your framework using apktool
** Make a backup! **
Code:
: adb pull /system/framework/framework-res.apk /sdcard/mytheme/backup.apk
: adb pull /system/framework/framework-res.apk C:\themes\mytheme.apk
: apktool d -f C:\themes\mytheme.apk C:\themes\mytheme\decoded\
Then open up the /res/values/styles.xml.
Find "<style name="Widget.Button" parent="@style/Widget">
Change the textcolor to #FFFF0000
This will make all buttons have a RED text color.
Click to expand...
Click to collapse
Now re-encode the file
Code:
:apktool b C:\themes\mytheme\decoded C:\themes\mytheme\encoded\mytheme-new.apk
Now, the simplest thing to do is to do the following:
- Open the original C:\themes\mytheme.apk with 7-zip
- Drag and drop the META-INF and AndroidManifest.xml File into a folder, like C:\themes\mytheme\signed
* Now you have a copy you can always use, and skip the above steps after doing it once *
- Open the new encoded mytheme-new.apk with 7-zip
- Drag and drop the META-INF and AndroidManifest.xml from the \signed directory
Click to expand...
Click to collapse
Code:
: adb push C:\themes\mytheme\encoded\mytheme-new.apk /sdcard/mytheme/framework-res.apk
: adb remount (if available for you!)
: adb shell
**Only if remount doesn't work.**
: mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
: cp /sdcard/mytheme/framework-res.apk /system/framework/framework-res.apk
**Wait for the theme to apply, no need to reboot**
**If you Bootloop and stay in shell (which you should if you don't reboot)**
Click to expand...
Click to collapse
Code:
: cp /sdcard/mytheme/backup.apk /system/framework/framework-res.apk
**After this the bootloops should stop as your last stable framework is loaded**
Click to expand...
Click to collapse
That's it!
Questions? Comments? Leave em!
So, for instance, in the Vanilla Froyo theme for 2.1, where all of the text elements that should be a dark grey or black are white, this would allow me to change them?
Yep. Just a matter of figuring out which style controls what...that's next on my list to document lol. It's a LOT easier than trying to Hex Edit everything.
I'm really surprised this thread isn't exploding with questions, but I have to say great work, man!
I'm gonna wait it out until I know my way around the SDK a little more, but I really wanna dig through this and finish the Vanilla theme I'm using.
Thanks! I should make one big guide get it stickied and be fine with it lol. You can check out my vanilla theme fire an idea of what I've done.
Sent from my DROIDX using XDA App
Great tutorial man. I especially appreciate the part about not having to reboot. I wonder why everyone always says to do that for installing themes.
If you use apkmanager (which is a frontend for apktool) -- it automates some of the steps mentioned here. Its in the G1 development section as well as apktool.
Not work...
Very sad
After complete all steps, device not boot after LG lable longer.
Any ideas?
log cmd in process:
Code:
D:\Android\SDKTools\tools>apktool d -f C:\themes\mytheme.apk C:\themes\mytheme\decoded\
I: Loading resource table...
I: Decoding resources...
I: Copying assets and libs...
D:\Android\SDKTools\tools>apktool b C:\themes\mytheme\decoded C:\themes\mytheme\encoded\mytheme-new.apk
[B][COLOR="Red"]W: Could not find sources[/COLOR][/B]
I: Checking whether resources has changed...
I: Building resources...
I: Building apk file...
phimuskapsi said:
Thanks! I should make one big guide get it stickied and be fine with it lol. You can check out my vanilla theme fire an idea of what I've done.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Phim, you're the best! I have been searching for a simple guide like this, as I found one a while ago when theming, but lost the link. Thanks for all your contributions on here, they are greatly appreciated! If I have some questions on editing some xml files, can I shoot you a PM or two?
Sent from my DROIDX using XDA App
I am trying to edit the color of the text in the drop down notification bar for the text such as USB Connection.
Can someone please tell me which xml file and which portion needs to be edited?
The font color would most likely be in the styles.xml file (in the values folder). I don't know which line exactly but you can take too different color versions and compare the decompiled xml files with word or online and look for differences.
yawdapaah said:
The font color would most likely be in the styles.xml file (in the values folder). I don't know which line exactly but you can take too different color versions and compare the decompiled xml files with word or online and look for differences.
Click to expand...
Click to collapse
Yae, thanks for the info. I found it shortly after posting through trial and error. I think it was in one of the status_bar_latest*.xml
For some reason when I made the esit and recompiled my famework-res.apk I lost adb capabilities and usb-mode and had to revert to a nandroid.
Any ideas on what may have caused this? Only edited an xml file...
Sent from my DROIDX using XDA App
.apk on desktop (adp pull C: [??])
phimuskapsi said:
Ok this is a quick little guide. Decided not to put this in the notification text thread as that needs to be cleaned up anyway.
This is for modifying .xml's in say /values or wherever you want. This particular example is going to use /values/styles.xml
First up, decode your framework using apktool
** Make a backup! **
Code:
: adb pull /system/framework/framework-res.apk /sdcard/mytheme/backup.apk
: adb pull /system/framework/framework-res.apk C:\themes\mytheme.apk
: apktool d -f C:\themes\mytheme.apk C:\themes\mytheme\decoded\
Click to expand...
Click to collapse
Hi there, newbie here (but I've managed to decode all the java and xml, which is fully readable). Only thing I have left is this pesky "resources.arsc" file. I tried using both the xml way and java way, but neither worked, that's when I found your posting. Thanks so much for sharing btw!!
I haven't tried this yet because I'm confused about why you did not put a "C:" in the beginning of the file address to route the command to the folder on your sdcard which contains your .apk.
My .apk will be on my desktop, so, how should my command line look???
Thanks again, hope to here from you.
Ok, I managed to decode everything except resources.arsc. I imported package successfully into eclipse but I have errors. I looked through all XML, which is in English and good, except for the resources.arsc, which is not decoding by methods I'm familiar with. Your method will probably work but I need command prompt spelled out for me (sorry about that).
So, resources.arsc is located: desktop/space/resources.arsc. I'll play around with it an see what happens...
Hello wazzup!
Ive try this but still dont acomplish this:
Ive got a APK which i want to edit the manifest(like package, label name, such stuff)
if i open the APK with WINRAR the manifest is decoded so ive moved on:
Ive downloaded the APKTool to reverse the application to smali or what it is called and get the real AndroidManifest.XML
I open the reversed Manifest.XML with notepad and have edit the things i want.
Now i am not sure how to decode the manifest. Because it wont work if i put the manifest.XML and use the AUTOSign tool because it expect the manifest to be decoded.
So what do i do? or is there another way to edit the manifest?
Thank you!
Your Mate!
Idon't think it's that simple, I tried and it doesn't work, you need something like apktool to do this for you
http://code.google.com/p/android-apktool/ (with or without the easier to use shell apkmanager)
@wixi909
You have to build XML file back to binary format using apktool or similar tool.
Brut.all said:
@wixi909
You have to build XML file back to binary format using apktool or similar tool.
Click to expand...
Click to collapse
hmm...ihave apktool. but could you explain more please
wixi909 said:
hmm...ihave apktool. but could you explain more please
Click to expand...
Click to collapse
I don't understand: you know, how to decode apk using apktool, but you don't know, how to build it back? This is almost the same, but "apktool b" instead of "apktool d". Everything is in apktool's usage help.
Brut.all said:
I don't understand: you know, how to decode apk using apktool, but you don't know, how to build it back? This is almost the same, but "apktool b" instead of "apktool d". Everything is in apktool's usage help.
Click to expand...
Click to collapse
I know but how do i edit the manifest. im just able do edit the drawables.
Do you understand now?
wixi909 said:
Do you understand now?
Click to expand...
Click to collapse
No, I don't.
wixi909 said:
I open the reversed Manifest.XML with notepad and have edit the things i want.
Click to expand...
Click to collapse
wixi909 said:
I know but how do i edit the manifest. im just able do edit the drawables.
Click to expand...
Click to collapse
You have written in your first post that you have edited manifest, but don't know, how to put it back to apk file. Now you say you can't edit manifest.
Whole process is:
Decode apk using apktool.
Edit AndroidManifest.xml using any text editor.
Build apk using apktool.
Nothing less, nothing more.
I'm having a related issue..
I'm using apktool to decode my apk. I then edit my AndroidManifest.xml, and repack it using
apktool b name_of_folder
For some reason though, the Manifest isn't being saved with my edits. I'm using Text Editor on Windows to edit the Manifest.
I know that it is saved before running "apktool b" so it seems to be reverting to the original during the repacking script.
Any ideas?
phiredrop said:
I'm having a related issue..
I'm using apktool to decode my apk. I then edit my AndroidManifest.xml, and repack it using
apktool b name_of_folder
For some reason though, the Manifest isn't being saved with my edits. I'm using Text Editor on Windows to edit the Manifest.
I know that it is saved before running "apktool b" so it seems to be reverting to the original during the repacking script.
Any ideas?
Click to expand...
Click to collapse
How do you know your modifications aren't saved to manifest? Did you tried to decode new apk back and see whether your changes are really there? Or you just don't see changes on a device? What did you changed?
Brut.all said:
How do you know your modifications aren't saved to manifest? Did you tried to decode new apk back and see whether your changes are really there? Or you just don't see changes on a device? What did you changed?
Click to expand...
Click to collapse
Yes, I decode the modified apk and can see my changes aren't there.
Its worked for me before, so it's strange that it's not working now. Primarily I'm adding version:Code and version:Name so I can upload to the market. Would changing the package name and/or label cause this issue?
Sent from my SGH-T959 using XDA App
UPDATED 8/15 !!!
Original Post:
The method explained here: http://forum.xda-developers.com/showthread.php?t=1109962
works for SGS II but not the III. I have copied the xml sip permissions file to /system/etc/permissions, and I have decompiled framework-res.apk, where the res/values/bools.xml file already reads
Code:
<bool name="config_sip_wifi_only">false</bool>
<bool name="config_built_in_sip_phone">true</bool>
I've looked over the rest of framework-res.apk and can't find anything. Verizon must be blocking this somewhere else.. any ideas??
Click to expand...
Click to collapse
---------------------------
My own research/efforts:
I have added /etc/permissions/android.software.sip.voip.xml from a sprint Galaxy S III (its the same on all versions, its only like 4 lines) and set permissions to rw-r--r--
I have replaced my deodexed SecPhone.apk and SecContacts.apk with deodexed Sprint ones. These run fantastically (no FCs anywhere). I've also double checked the boolean values in framework-res.apk which allow SIP (as previously stated)
PROGRESS
By installing the xml SIP permissions file and then editing build.prob to imitate the sprint model:
Code:
ro.product.model=LPH-L710
ro.product.name=d2spr
ro.product.device=d2spr
or the Galaxy Nexus:
Code:
ro.product.model=Galaxy Nexus
ro.product.name=yakju
ro.product.device=maguro
it opens up the "internet call options" submenu within the dialer options. You now have sip calling... Over wifi only though, as this wipes out your data connection.
In order to keep data working, you must set set the model, name, and device to be something from verizon, which in turn disables SIP calling. It is a vicious cycle.
Therefore, in order to use SIP calling on the Verizon Galaxy S III we must either use an AOSP ROM or find where this check is occuring in smali and remove it or make it constantly return true. However, I have no clue where it could be...
preusstang said:
The method explained here: http://forum.xda-developers.com/showthread.php?t=1109962
works for SGS II but not the III. I have copied the xml sip permissions file to /system/etc/permissions, and I have decompiled framework-res.apk, where the res/values/bools.xml file already reads
Code:
<bool name="config_sip_wifi_only">false</bool>
<bool name="config_built_in_sip_phone">true</bool>
I've looked over the rest of framework-res.apk and can't find anything. Verizon must be blocking this somewhere else.. any ideas??
Click to expand...
Click to collapse
just looking at it rather quickly, the way sip stack works in ICS is different than gingerbread. The guide you have is for gingerbread. You will need to find a guide that supports ICS. I would help you with this, but I already have to many projects on my table.
nosympathy said:
just looking at it rather quickly, the way sip stack works in ICS is different than gingerbread. The guide you have is for gingerbread. You will need to find a guide that supports ICS. I would help you with this, but I already have to many projects on my table.
Click to expand...
Click to collapse
That's the thing. There are none. The menu shows up fine on the i9300. I have a copy of their SecPhone.apk that I'm looking at now.
I'm having some trouble with apktool and apk manager tho, whenever I extract, I'm not seeing the "res/values/" folder or the smali folder.
preusstang said:
That's the thing. There are none. The menu shows up fine on the i9300. I have a copy of their SecPhone.apk that I'm looking at now.
I'm having some trouble with apktool and apk manager tho, whenever I extract, I'm not seeing the "res/values/" folder or the smali folder.
Click to expand...
Click to collapse
What version of apktools are you using?
Sent from my SCH-I535 using xda app-developers app
nosympathy said:
What version of apktools are you using?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
ok so I now have apktool 1.4.3, with the windows helper files - apktool.bat and aapt.exe.
Code:
C:\apktool-1.4.3>apktool d originals/framework-res.apk
I: Loading resource table...
I: Loaded.
I: Decoding file-resources...
I: Decoding values*/* XMLs...
I: Done.
I: Copying assets and libs...
C:\apktool-1.4.3>
decompiles everything fine. including the values/ xml files. I still see no smali folder though. how do you get access to that?
also, im not able to recompile the apk. its decompiled to framework-res/, but trying to build it results in epic failure:
Code:
C:\apktool-1.4.3>apktool b framework-res
W: Could not find sources
I: Checking whether resources has changed...
I: Building resources...
invalid resource directory name: C:\apktool-1.4.3\framework-res\res/drawable-sw3
20dp-hdpi
invalid resource directory name: C:\apktool-1.4.3\framework-res\res/drawable-sw3
20dp-w533dp-hdpi
invalid resource directory name: C:\apktool-1.4.3\framework-res\res/drawable-sw3
60dp-hdpi
invalid resource directory name: C:\apktool-1.4.3\framework-res\res/drawable-sw3
60dp-w640dp-hdpi
invalid resource directory name: C:\apktool-1.4.3\framework-res\res/drawable-sw3
60dp-w640dp-xhdpi
invalid resource directory name: C:\apktool-1.4.3\framework-res\res/drawable-sw3
60dp-xhdpi
invalid resource directory name: C:\apktool-1.4.3\framework-res\res/drawable-sw6
00dp-xhdpi
invalid resource directory name: C:\apktool-1.4.3\framework-res\res/layout-sw320
dp
invalid resource directory name: C:\apktool-1.4.3\framework-res\res/layout-sw320
dp-hdpi
invalid resource directory name: C:\apktool-1.4.3\framework-res\res/layout-sw320
dp-w533dp-hdpi
invalid resource directory name: C:\apktool-1.4.3\framework-res\res/layout-sw360
dp
invalid resource directory name: C:\apktool-1.4.3\framework-res\res/layout-sw360
dp-hdpi
invalid resource directory name: C:\apktool-1.4.3\framework-res\res/layout-sw360
dp-w640dp-hdpi
invalid resource directory name: C:\apktool-1.4.3\framework-res\res/layout-sw360
dp-xhdpi
invalid resource directory name: C:\apktool-1.4.3\framework-res\res/layout-sw600
dp
invalid resource directory name: C:\apktool-1.4.3\framework-res\res/layout-w600d
p
invalid resource directory name: C:\apktool-1.4.3\framework-res\res/values-h720d
p
invalid resource directory name: C:\apktool-1.4.3\framework-res\res/values-sw320
dp
invalid resource directory name: C:\apktool-1.4.3\framework-res\res/values-sw320
dp-hdpi
invalid resource directory name: C:\apktool-1.4.3\framework-res\res/values-sw360
dp
invalid resource directory name: C:\apktool-1.4.3\framework-res\res/values-sw360
dp-hdpi
invalid resource directory name: C:\apktool-1.4.3\framework-res\res/values-sw360
dp-xhdpi
invalid resource directory name: C:\apktool-1.4.3\framework-res\res/values-sw600
dp
invalid resource directory name: C:\apktool-1.4.3\framework-res\res/values-sw600
dp-land
invalid resource directory name: C:\apktool-1.4.3\framework-res\res/values-sw600
dp-w1024dp
invalid resource directory name: C:\apktool-1.4.3\framework-res\res/values-sw600
dp-w1280dp
invalid resource directory name: C:\apktool-1.4.3\framework-res\res/values-w360d
p
invalid resource directory name: C:\apktool-1.4.3\framework-res\res/values-w480d
p
invalid resource directory name: C:\apktool-1.4.3\framework-res\res/values-w500d
p
invalid resource directory name: C:\apktool-1.4.3\framework-res\res/values-w600d
p
invalid resource directory name: C:\apktool-1.4.3\framework-res\res/values-w720d
p
Exception in thread "main" brut.androlib.AndrolibException: brut.common.BrutExce
ption: could not exec command: [aapt, p, -F, C:\Users\Kyle\AppData\Local\Temp\AP
KTOOL3864608409932162932.tmp, -x, -S, C:\apktool-1.4.3\framework-res\res, -M, C:
\apktool-1.4.3\framework-res\AndroidManifest.xml]
at brut.androlib.res.AndrolibResources.aaptPackage(AndrolibResources.jav
a:193)
at brut.androlib.Androlib.buildResourcesFull(Androlib.java:301)
at brut.androlib.Androlib.buildResources(Androlib.java:248)
at brut.androlib.Androlib.build(Androlib.java:171)
at brut.androlib.Androlib.build(Androlib.java:154)
at brut.apktool.Main.cmdBuild(Main.java:182)
at brut.apktool.Main.main(Main.java:67)
Caused by: brut.common.BrutException: could not exec command: [aapt, p, -F, C:\U
sers\Kyle\AppData\Local\Temp\APKTOOL3864608409932162932.tmp, -x, -S, C:\apktool-
1.4.3\framework-res\res, -M, C:\apktool-1.4.3\framework-res\AndroidManifest.xml]
at brut.util.OS.exec(OS.java:83)
at brut.androlib.res.AndrolibResources.aaptPackage(AndrolibResources.jav
a:191)
... 6 more
C:\apktool-1.4.3>
for some reason the program is changing directory backslashes to slashes midway, but those directories it mentions do not exist. more importantly, I don't know what is causing the error with exec'ing aapt - aapt.exe runs fine and is in my PATH.
any ideas? thanks for your help.
EDIT: if i run the failed exec command manually:
Code:
aapt p -F C:\Users\Kyle\AppData\Local\Temp\APKTOOL7789083448626722688.tmp -x -S C:\apktool-1.4.3\framework-res\res -M C:\apktool-1.4.3\framework-res\AndroidManifest.xml
I get more directory errors, but these directories really do exist.
Can someone tell me what sip is?
Sent from my SCH-I535 using xda premium
SIP = Session Initiation Protocol.
The short of it - VoIP (GTalk/Voice, Vonage, etc).
Stock Android supports it natively since 2.3.x.
I'm not sure if this would help but I found that there's an option in AnyCut:
Activity
Sip settings
I'd create a shortcut on the home screen to this and try setting up your sip account credentials
My phone gives me the option, I just have no sip account to my knowledge
Afterwards, I've read you should go to the Dialer settings to enable ask each call.
Sent from my SCH-I535
Josolanes said:
I'm not sure if this would help but I found that there's an option in AnyCut:
Activity
Sip settings
I'd create a shortcut on the home screen to this and try setting up your sip account credentials
My phone gives me the option, I just have no sip account to my knowledge
Afterwards, I've read you should go to the Dialer settings to enable ask each call.
Sent from my SCH-I535
Click to expand...
Click to collapse
the sip settings dialog that shows when you use the anycut widget is a big part of the sip calling. it allows you to set up accounts and register them, it then says its receiving calls but it doesn't.. Here's what the menu(s) look like:
{
"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"
}
However, the actual call settings menu still lacks the buttons required to set up/allow dialing out with SIP.
because that internet calling section is missing, this dialog is never presented:
I have tried decompiling the SecPhone.apk from nosympathys stock OTA VRALG (deodexed) rom and get errors:
Code:
C:\apktool>apktool d SecPhone.apk
I: Baksmaling...
Exception in thread "main" java.lang.RuntimeException: bad magic value: 64 65 78
0a 30 33 36 00
at org.jf.dexlib.DexFile.(DexFile.java:377)
at org.jf.dexlib.DexFile.(DexFile.java:274)
at brut.androlib.src.SmaliDecoder.decode(SmaliDecoder.java:48)
at brut.androlib.src.SmaliDecoder.decode(SmaliDecoder.java:33)
at brut.androlib.Androlib.decodeSourcesSmali(Androlib.java:68)
at brut.androlib.ApkDecoder.decode(ApkDecoder.java:85)
at brut.apktool.Main.cmdDecode(Main.java:128)
at brut.apktool.Main.main(Main.java:65)
C:\apktool>
I've also tried replacing our SecPhone.apk with one from the i9300, obtained here:
http://forum.xda-developers.com/showthread.php?t=1706310
(in the posted zip file)
but it results in mad FC's. I'm not sure what else to do here..
EDIT: all screens were stolen from http://blog.brightpointuk.co.uk/setting-sip-voip-account-samsung-galaxy-s-iii
Any further progress on this. I am really interested to try this out. However, my knowledge of modding things is somewhat limited.
joebob296 said:
Any further progress on this. I am really interested to try this out. However, my knowledge of modding things is somewhat limited.
Click to expand...
Click to collapse
Unfortunately, no. It seems the community here [is used to getting bent over backwards by verizon and/or doesn't know about the awesome benefits of SIP(!) and] is not interested in making/receiving FREE calls nationwide with their Google voice # or another outward trunk to the PSTN (public switched telephone network)
Instead of actually modifying our touchwiz dialer (or installing other carriers' GS III touchwiz dialer) I think we have a better chance of some dev around here building an ASOP dialer from source. But I think that also necessitates an ASOP build of the contacts app.
Could we use the dialer from cm9/10 giant that aosp? I don't know if we could use that apk or have to modify it to use on a stock touchwiz ROM.
Edit: Or maybe the sprint app if they have that feature still open to them.
Sent from my SCH-I535 using xda app-developers app
joebob296 said:
Could we use the dialer from cm9/10 giant that aosp? I don't know if we could use that apk or have to modify it to use on a stock touchwiz ROM.
Edit: Or maybe the sprint app if they have that feature still open to them.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Good thinking. I'm not sure why I didn't see that.. I'll extract them from one of the CM builds tonight. I'm still unsure though of exactly what apks need copied out.
update:
I made a zip which removed SecPhone, SecTelephonyProvider, SecContacts, and SecContactsProvider and installed:
Phone.apk
TelephonyProvider.apk
Contacts.apk
ContactsProvider.apk
all from invisiblek's cm9 build. this caused mad FC's with the gallery, messaging, sync service, and google.process.gapps.
fail somewhat of a learning experience though.
I'm now gonna try installing the "Sec" apks from a sprint ROM. *crosses fingers*
if you have google voice here is an awesome app for talking for free. its well setup.. its called groove ip and you can get it here..
https://play.google.com/store/apps/details?id=com.gvoip&hl=en
i have been using it for a long time now, never fails
mrbracht said:
if you have google voice here is an awesome app for talking for free. its well setup.. its called groove ip and you can get it here..
https://play.google.com/store/apps/details?id=com.gvoip&hl=en
i have been using it for a long time now, never fails
Click to expand...
Click to collapse
It is a good app and works very well. its just disappointing that you need to download a 3rd party app for something that the android OS already provides for. And verizon is the only carrier to do this. isn't surprising tho..
preusstang said:
It is a good app and works very well. its just disappointing that you need to download a 3rd party app for something that the android OS already provides for. And verizon is the only carrier to do this. isn't surprising tho..
Click to expand...
Click to collapse
Verizon is pretty much a joke. I still can't believe they get away with all the **** they do
Sent from my SCH-I535 using Tapatalk 2
preusstang said:
update:
I made a zip which removed SecPhone, SecTelephonyProvider, SecContacts, and SecContactsProvider and installed:
Phone.apk
TelephonyProvider.apk
Contacts.apk
ContactsProvider.apk
all from invisiblek's cm9 build. this caused mad FC's with the gallery, messaging, sync service, and google.process.gapps.
fail somewhat of a learning experience though.
I'm now gonna try installing the "Sec" apks from a sprint ROM. *crosses fingers*
Click to expand...
Click to collapse
Yea I'm learning to. I read today that the dialer app relies on more then just the app itself if I recall correctly we have to change some framework files. So we would have to modify more then just the app. But I think that an app with that already allows sip calling would be a good place to start. I think that we would have a better chance using sprints stock dialer if they have it enabled, because that should be based on touchwiz.
Sent from my Galaxy Nexus using xda app-developers app
---------- Post added at 02:30 AM ---------- Previous post was at 02:20 AM ----------
mrbracht said:
if you have google voice here is an awesome app for talking for free. its well setup.. its called groove ip and you can get it here..
https://play.google.com/store/apps/details?id=com.gvoip&hl=en
i have been using it for a long time now, never fails
Click to expand...
Click to collapse
How is the voice quality over 3g/4g? Any complaints about the app?
Sent from verizons soon to be unlocked galaxy s3
joebob296 said:
Yea I'm learning to. I read today that the dialer app relies on more then just the app itself if I recall correctly we have to change some framework files. So we would have to modify more then just the app. But I think that an app with that already allows sip calling would be a good place to start. I think that we would have a better chance using sprints stock dialer if they have it enabled, because that should be based on touchwiz.
Sent from my Galaxy Nexus using xda app-developers app
---------- Post added at 02:30 AM ---------- Previous post was at 02:20 AM ----------
How is the voice quality over 3g/4g? Any complaints about the app?
Sent from verizons soon to be unlocked galaxy s3
Click to expand...
Click to collapse
None what so ever. Loving it to be honest, been using it for a while now
Sent from my SCH-I535 using Tapatalk 2
I've been debating whether or not to try it. Right now I use talkatone which was free for 3g/4g calling but I've had issues with it recently.
Sent from Verizon's soon to be unlocked Galaxy S3.