• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [Boost Mobile] Changing phone and contact APKs

BLVCKHVLO

Android Enthusiast
I want to change out these two apk, and I know it's not as simple as simply pasting them in... in other phones you can usually flash them with phonesettings apk or similar, but I'm not sure what the dependencies are. Anybody who has or is deving a rom done this with the warp and can you tell me how???
 
I've seen themed dialers on the warp but that's it. I'm pretty sure you are breaking new ground on this

It's not so much that I want to put *new dialers or contacts, but rather ones from another rom. The one in the rom I'm working on has groups, which I don't want and I have seen them without this in a few other warped roms. How do I pull the phone apk and contacts apk from another rom and put it in mine? Mine just FC's I know it's because I'm missing something.

From what I understand these apks are universal and independent of the rom. I've even seen people using dialers from different phones (assuming they were both GB or JB or ICS). I've tried including contact and telephony provider etc, but to no avail.

I've even tried using the stock phone and contact apk but get the same problems.
 
Really? Nobody knows how to switch out apk's for phone and contacts?

I've researched it, but everything points to needing to add another apk which is a dependency to properly install, which is not present in any of our roms for some reason.
 
Have you tried decompiling with a specified dependency file (e.g. framework-res.apk or whatever) from the source ROM, then recompiling under the proper API level for GB?
 
Have you tried decompiling with a specified dependency file (e.g. framework-res.apk or whatever) from the source ROM, then recompiling under the proper API level for GB?

Here- maybe I am being unclear: I want to use a dialer from say Noob or AOEM.

How? I don't know what the dependency would be? There seems to be none. Messenger works without a hitch. I know I need contacts as a dependency for phone because one themes the other, but I don't know what else is missing.

But: I think I may try to do what you just mentioned as well if I can just get this working and I decide to try and get a little fancy (I have seen ICS phone ported over to GB on other phones and so on.
 
Here- maybe I am being unclear: I want to use a dialer from say Noob or AOEM.

How? I don't know what the dependency would be? There seems to be none. Messenger works without a hitch. I know I need contacts as a dependency for phone because one themes the other, but I don't know what else is missing.
...

Ah, ok. Then I see no reason (unless I'm missing something here) why you can't just swap them out. They're both sourced from the stock Warp image, so you should be able to remove the one Cyanoid has and replace it with the one from n00b or what-have-you. I know for a fact there is no dependency for MMS.APK, however there are a couple things you'll most likely have to edit to get it to compile properly once again. I have a post about it in the WOEM thread.

Edit: Those posts about MMS de/re-compiling can be found here:

http://androidforums.com/5570020-post182.html

http://androidforums.com/5570049-post183.html
 
Ah, ok. Then I see no reason (unless I'm missing something here) why you can't just swap them out. They're both sourced from the stock Warp image, so you should be able to remove the one Cyanoid has and replace it with the one from n00b or what-have-you. I know for a fact there is no dependency for MMS.APK, however there are a couple things you'll most likely have to edit to get it to compile properly once again. I have a post about it in the WOEM thread.

Edit: Those posts about MMS de/re-compiling can be found here:

http://androidforums.com/5570020-post182.html

http://androidforums.com/5570049-post183.html

Really?? I haven't had any issues decompiling your mms apk. I already went in and changed a couple of things in XML and swapped some images out?? It runs great... I will read this though, as i didn't decompile or recompile in a computer, but from my phone.

Also on my computer, I was having the same issues you were but with systemui.apk in vst (remember that message I sent you with the link?)... I just switched over to apk changer from vst and everything compiled fine. I would have probably taken the time to fix the stuff if I had it like you had done... alas I don't fix what is not broken to me. If it works, it works lol.
 
Really?? I haven't had any issues decompiling your mms apk. I already went in and changed a couple of things in XML and swapped some images out?? It runs great... I will read this though, as i didn't decompile or recompile in a computer, but from my phone.

Also on my computer, I was having the same issues you were but with systemui.apk in vst (remember that message I sent you with the link?)... I just switched over to apk changer from vst and everything compiled fine. I would have probably taken the time to fix the stuff if I had it like you had done... alas I don't fix what is not broken to me. If it works, it works lol.

Oh, OK if you're using the MMS from Warp OEM then that stuff is already fixed, so you won't have to worry about it. That only applies to stock :-)
 
  • Like
Reactions: Doc
Ah, ok. Then I see no reason (unless I'm missing something here) why you can't just swap them out. They're both sourced from the stock Warp image, so you should be able to remove the one Cyanoid has and replace it with the one from n00b or what-have-you. I know for a fact there is no dependency for MMS.APK, however there are a couple things you'll most likely have to edit to get it to compile properly once again. I have a post about it in the WOEM thread.

Edit: Those posts about MMS de/re-compiling can be found here:

http://androidforums.com/5570020-post182.html

http://androidforums.com/5570049-post183.html


Going back through old threads and I find this... there's no dependency for MMS.apk? Meaning I could flash one from CTmod into noob and no hitches correct?
 
You should be able to assuming that the data folder comes from the same base and often times framework res ie they often need to be from b10g or b08c. Otherwise the manifest files will need to be switched when you resign just to get the apk to show up in app tray if they are from different bases. When you do this you lose a lot of the theming you are after as well as other functionality. Trust me I've been doing the same thing making a franken Rom with cyanoid and ct. You are going to run into issues when you actually zip it and update or install. The libraries overlap so it looks good in a nandroid but when you wipe and do a legitimately installation you are going to have a lot off issues that are hard to distinguish and single out to fix. You put one fire out and make another. I'll post a working nandroid of my project and then the actual Rom if you want to see what you are in for. I had to ditch the cyanoid base and start over.
 
Also when I use the mms from oem in my Rom it works fine in b08c but jot in b10g even though oem 2 is b10. It took me a minute to figure out that his wasn't b10g based but integrated. So he must have kept old dependencies from the old base. So whatever Rom you are working with you need to make sure if they are based on the new update in full or just integrated. I think both of the Rom you are working with are.
 
Also when I use the mms from oem in my Rom it works fine in b08c but jot in b10g even though oem 2 is b10. It took me a minute to figure out that his wasn't b10g based but integrated. So he must have kept old dependencies from the old base. So whatever Rom you are working with you need to make sure if they are based on the new update in full or just integrated. I think both of the Rom you are working with are.

I had that same issue when decompiling APKs from various ROMs for learning. However, Warp OEM is a complete implementation of B10G - e.g. I started with a full B08C install, let the B10G update do its work, then began whittling that into Warp OEM, porting all the in-depth mods (extended power menu, theming, etc.) over to the new firmware myself.

That said, I have no idea why WOEM's MMS.APK wouldn't work in a B10G environment :confused:
 
I had that same issue when decompiling APKs from various ROMs for learning. However, Warp OEM is a complete implementation of B10G - e.g. I started with a full B08C install, let the B10G update do its work, then began whittling that into Warp OEM, porting all the in-depth mods (extended power menu, theming, etc.) over to the new firmware myself.

That said, I have no idea why WOEM's MMS.APK wouldn't work in a B10G environment :confused:

I have no idea. I've tried it on multiple B10 based roms, the only pattern I have established is that it works in B08c without a hitch. I've resigned it to the same signatures as the MMS being replaced, left it alone, resigned complete roms with it included in sys/app... nothing unless it's bo8c or on your rom. I even put it in stock deodex b10.

Also whenever I try to update any rom with the b10 update zip, it just hangs on splash indefinitely. I even tried this on stock deodexed b10. I can get baseband to work alone but that's it.

Man I think I'm done fooling with roms after I get this project done. I just don't have the time, and the progress is so slow. Unless you have the time, foresight etc. before hand, it gets pretty frustrating. I have a completed rom done, and it boots, but for some reason after the first boot, and then a reboot, it just bootloops the second time and every time after. Aside from that it is super fast and all that. My other issue is that my dialer works and calls, but I get no option to sync contacts- even though it lets me sync my google account for everything else?? Have no idea why. Everything works great from what I've built back and forth into my phone, but when I pull system.img and make a build in kitchen the results are as mentioned after flashing.

It sucks because I really don't want to abandon this rom- I highly dislike not finishing what I start. It works great on my phone, but I don't have the time or knowledge (moreso the time to aquire needed knowledge- babies don't care care about my phone unless it's making cool sounds) to complete this or figure out the bugs and fix them so as to make a working flashable build. LAME. I should have just made one from scratch. At least I learned a bunch of stuff (which is absolutely useless to me in the real world- it would be nice if this was more than just a hobby or time kill).
 
I have no idea. I've tried it on multiple B10 based roms, the only pattern I have established is that it works in B08c without a hitch. I've resigned it to the same signatures as the MMS being replaced, left it alone, resigned complete roms with it included in sys/app... nothing unless it's bo8c or on your rom. I even put it in stock deodex b10.

Also whenever I try to update any rom with the b10 update zip, it just hangs on splash indefinitely. I even tried this on stock deodexed b10. I can get baseband to work alone but that's it.

Man I think I'm done fooling with roms after I get this project done. I just don't have the time, and the progress is so slow. Unless you have the time, foresight etc. before hand, it gets pretty frustrating. I have a completed rom done, and it boots, but for some reason after the first boot, and then a reboot, it just bootloops the second time and every time after. Aside from that it is super fast and all that. My other issue is that my dialer works and calls, but I get no option to sync contacts- even though it lets me sync my google account for everything else?? Have no idea why. Everything works great from what I've built back and forth into my phone, but when I pull system.img and make a build in kitchen the results are as mentioned after flashing.

It sucks because I really don't want to abandon this rom- I highly dislike not finishing what I start. It works great on my phone, but I don't have the time or knowledge (moreso the time to aquire needed knowledge- babies don't care care about my phone unless it's making cool sounds) to complete this or figure out the bugs and fix them so as to make a working flashable build. LAME. I should have just made one from scratch. At least I learned a bunch of stuff (which is absolutely useless to me in the real world- it would be nice if this was more than just a hobby or time kill).

I hear you... the going is always slow it seems, and I sometimes have a tendancy to overlook small details that I often don't think about until my ROM is building. Then I remember and kick myself lol

Also, did you include the ContactsProvider.apk? If not, maybe that's why you're having the sync issue. Just a guess on my part.
 
Back
Top Bottom