Hi everyone,
I accidentally removed phone.apk from /system/app, thinking I could replace the stock blur dialer application. Unfortunately, the blur dialer which is still being used in the jellybean update does not work well for blind people like myself who use talkback, and I can't find a way to remove it..
Regardless, I did do an adb pull /system/phone.apk prior to doing this but somehow the file cannot be found anywhere. I don't want to reflash as that would require sighted help, something I don't have at the moment.
I'm wondering if anyone has a dump of the d4 4.1.2 image, or can give me the original phone.apk file. Either works for now.
Thanks,
Tomi
http://db.tt/NuVZara3
Phone.apk
http://db.tt/YnAIhe3c
Phone.odex
Could someone get me the apks and odexs for the camera, messaging, and contacts?
Please and thank you
Related
i know some themes change it, but i like the theme i have already. i just want to change the keyboard to a more pleasant look. is there somewhere i can find different ones to download or flash onto my rom? i don't want to use betterkeyboard app, etc.
Here You Go Buddy.
Well i skinned the stock keyboard pretty easily with a few easy techniques.
First check out my theme Ivory http://forum.xda-developers.com/showthread.php?t=612315 To see if that's what you want. I hope your familiar with themeing or this might be confsing.
-I took the latinIME.apk from cyanogens last rom
-Opened it as a zip and navigated to the res drawable folders
-downloaded the better keyboard skins i wanted (simple black and green)
-pulled the different drawable files from the betterkeyboard apps and replaced the stock cyanogen ones
-resigned apk and flashed inside my theme
sassyness77 said:
Well i skinned the stock keyboard pretty easily with a few easy techniques.
First check out my theme Ivory http://forum.xda-developers.com/showthread.php?t=612315 To see if that's what you want. I hope your familiar with themeing or this might be confsing.
-I took the latinIME.apk from cyanogens last rom
-Opened it as a zip and navigated to the res drawable folders
-downloaded the better keyboard skins i wanted (simple black and green)
-pulled the different drawable files from the betterkeyboard apps and replaced the stock cyanogen ones
-resigned apk and flashed inside my theme
Click to expand...
Click to collapse
haha thats EXACTLY what i tried to do yesterday night! except i got the acore force close thing, & im sure it's because i didn't sign it first. i had an easy auto-sign program but i deleted it a few days ago :| & now i can't find it on here anymore!
jonesyruless said:
haha thats EXACTLY what i tried to do yesterday night! except i got the acore force close thing, & im sure it's because i didn't sign it first. i had an easy auto-sign program but i deleted it a few days ago :| & now i can't find it on here anymore!
Click to expand...
Click to collapse
haha what are the odds well at least your on the right track!
I would go for editing HTC_IME.apk, just a personal preference i guess, but i think its better, and have played around with editing it a bit myself, and its pretty easy, but you need to be able to do *.9.png files.
sassyness77 said:
haha what are the odds well at least your on the right track!
Click to expand...
Click to collapse
okay i found it. but im still geting te acore force close): what could i be doing wrong?
hmmmm.
jonesyruless said:
okay i found it. but im still geting te acore force close): what could i be doing wrong?
Click to expand...
Click to collapse
Im not sure, are you using stricstons signing tool? how are you flashing it?
What ROM are you trying it on? The new CM ROMs the keyboard is now in the LatinIME.apk instead of the framework-res.apk, but if you are using one of the other ROMs, that may not be the case.
sassyness77 said:
Im not sure, are you using stricstons signing tool? how are you flashing it?
Click to expand...
Click to collapse
i dont think so, im using a modded apk signing tool i found on here, i lost the link.
and im doing
cp /sdcard/LatinIME.apk(the one i made) /system/app
in terminal emulator.
then after that the keyboard just dissappears. if i restart after that, the keyboard never shows up. if i just try to go back, i get acore force close repeatedly.
jairomeo said:
What ROM are you trying it on? The new CM ROMs the keyboard is now in the LatinIME.apk instead of the framework-res.apk, but if you are using one of the other ROMs, that may not be the case.
Click to expand...
Click to collapse
yea i know, im on cyanogen's latest.
You may want to try getting Stericson's signing tool. If it is disappearing signing could be the main issue. Since you edit it on your PC, why don't you just push it through adb after signing instead of copying it to your sd and then having to use the terminal?
jairomeo said:
You may want to try getting Stericson's signing tool. If it is disappearing signing could be the main issue. Since you edit it on your PC, why don't you just push it through adb after signing instead of copying it to your sd and then having to use the terminal?
Click to expand...
Click to collapse
the thing is though that i used the same signing tool to edit a graphic on a different app & it worked just fine.
i don't have/really know what adb OR sdk is & terminal is the easiest way i know how to do it. i mean does it really make a difference?
its been confirmed that it's not my signing tool because i used the same tool to edit a different app, a battery widget i downloaded from the market. & it worked fine. anyone else can help me?
lets get this working buddy,
Alrighty maybe try flashing the keyboard in an update.zip, just put the latinIME.apk into a folder named app. Then copy a meta inf folder from another theme download, you can use mine. Then send that to a compressed folder, resign and try to flash it. I would try that, I have never had good luck pushing with adb and pulling stuff, I stick with the easy way
yesssss i finally got it to work! it turns out i didnt need the signing tool at all. i took the latinime.apk file from a theme with a skinned keyboard, then i ONLY replaced the keyboard png's, and kept the meta-inf how it was. thanks guys for trying to help
There is not much that i miss about the stock apps on the Fascinate. However, I must say that I do miss the awesome music widget that you can pull down the CD (with album art on it) from the top of the screen. Do you think it's possible to port this over to use?
I have tried taking the apk and odex files from the stock rom and placing them into /system/app but it does not work. I'm not sure if voodoo's new ext4 file format is causing permission issues or what, but either way i haven't been able to get it working. Anyone have any ideas on this? If not, anyone up for porting over the app
emplox said:
There is not much that i miss about the stock apps on the Fascinate. However, I must say that I do miss the awesome music widget that you can pull down the CD (with album art on it) from the top of the screen. Do you think it's possible to port this over to use?
I have tried taking the apk and odex files from the stock rom and placing them into /system/app but it does not work. I'm not sure if voodoo's new ext4 file format is causing permission issues or what, but either way i haven't been able to get it working. Anyone have any ideas on this? If not, anyone up for porting over the app
Click to expand...
Click to collapse
Are you on JT's rom? if so don't use an apk with an odex, his system is deodex'ed.
Try the following apk, it should work.
I get "application not installed" when I try to install it. Could it be because there is already a Music app called "Music" on Jt's rom?
emplox said:
I get "application not installed" when I try to install it. Could it be because there is already a Music app called "Music" on Jt's rom?
Click to expand...
Click to collapse
That is a system file. You can't just install it. You need to replace the original file with that one with adb or root explorer (or something similar).
blazingwolf said:
That is a system file. You can't just install it. You need to replace the original file with that one with adb or root explorer (or something similar).
Click to expand...
Click to collapse
adb pull /system/apps/musicplayer.apk
backup that version, copy new version into its place.
adb push musicplayer.apk /system/apps/
?? is that how you would do it? or is that even where it is?
I think it's /system/app
regardless, i have tried this and every time i do it my phone goes to black screen after the VZW screen. It will just sit there. Then when I go back and put the original .apk back in place...it boots right up and works. I have a friend trying to go back to the touchwiz calendar who has the exact same problem. Neither of us can figure it out.
emplox said:
I think it's /system/app
regardless, i have tried this and every time i do it my phone goes to black screen after the VZW screen. It will just sit there. Then when I go back and put the original .apk back in place...it boots right up and works. I have a friend trying to go back to the touchwiz calendar who has the exact same problem. Neither of us can figure it out.
Click to expand...
Click to collapse
Here flash this through CW and see if it still gives you a black screen.
that worked can you make one for the touchwiz calendar apk too? I'd love to know what you did to make it and what the difference is so i can do it myself.
The one part that stinks is that the widget on the lockscreen is a feature of TouchWiz lockscreen, as it's not work on stock. Once I flashed the puzzle lock it worked.
I was wondering if it would be possible to take the Messaging .apk from a 2.1 ROM, and push it onto a 2.2 ROM, replacing the 2.2 Messaging app. I don't really like the 2.2 one, as it lags for me, and I can't really change the font sizes or anything.
Also, is it possible to take a 2.1 LatinIME.apk and do the same thing? These are the only two things that I don't really like about Froyo ROMs, because they are both slow on my phone.
Thanks!
I'm no dev or anything so I'm not 100% sure but I think it can be done. I just don't know if it would run I read somewhere where people tried to push apps from a different build and it FC's when the app starts. Also, I was looking into getting the froyo messager on a donut rom to see how it would run and i found this http://forum.xda-developers.com/showthread.php?t=752604. I opened it up to see what files we're flashed to get this and it's just the mms.apk. So I'm guessing what you said can be done by getting the mms.apk from a Eclair rom and push it into your system/app/ folder, The question is will it run though?
Ianlikescake said:
I'm no dev or anything so I'm not 100% sure but I think it can be done. I just don't know if it would run I read somewhere where people tried to push apps from a different build and it FC's when the app starts. Also, I was looking into getting the froyo messager on a donut rom to see how it would run and i found this http://forum.xda-developers.com/showthread.php?t=752604. I opened it up to see what files we're flashed to get this and it's just the mms.apk. So I'm guessing what you said can be done by getting the mms.apk from a Eclair rom and push it into your system/app/ folder, The question is will it run though?
Click to expand...
Click to collapse
I think I'm just gonna try it. I'll adb pull the original MMS.apk first, and if the pushed one doesn't work, I'll just push the original back in.
EDIT: Nope, doesn't work.
skate4lyph said:
I think I'm just gonna try it. I'll adb pull the original MMS.apk first, and if the pushed one doesn't work, I'll just push the original back in.
EDIT: Nope, doesn't work.
Click to expand...
Click to collapse
It was worth a shot.
I'd like to remove SMS messages from my phone log. I've retrieved the logsprovider.apk file from Cognition 4.3 that I think has been modified to do this.
My question is basically can I just drop that file into the system/apps directory and have it do its thing? I notice there is a .odex file counterpart on my device that is not present in the Cognition rom and was wondering what effect that would have.
Just trying to do small things... Any advice would be appreciated. I'm on this path because I've done too much reading!
Running 2.2 with existz KB1 kernel. Just doing some things before I go Gingerbread.
Your firmware needs deodexed in order to drop that apk in.
Thanks. I wondered about that and since I'm still running essentially stock 2.2 it has not been, right?
Which is why all the custom ROM's say that they are... well shucks. Anyway, thanks for the reply.
Super easy way to get your texts to not show up in the log:
use handcent sms
That's what i use personally and the texts don't show up, even though i didn't modify the logsprovider.apk in my ROM.
This is a repost from the Moto X Pure section. LINK
Follow the instructions to backup and then flash the AOSP dialer and contacts in TWRP. This worked perfectly for me on my Turbo.
Works great. Thanks!
I'm considering flashing this. Then I got to looking at these apps in the play store. Of course it shows that they're incompatible with all my devices, but my question is to ask if after flashing this, has anyone tried updating to the updated apps that are in the Play Store? Of course if I don't get a response in the next few minutes, I'll probably give it a shot anyway. After a nandroid, naturally.
I was able to get the contacts to install and initiated, and the dialer installed, according to Aroma, but for some reason, it wouldn't initiate. I suspect it's something to do with it being CM. I recall that CM somehow broke the dialer compatibility, back in either 10 or 11...
Sent from my DROID Turbo via Tapatalk. Now with that cyanogenmod goodness.
The original write up didn't pan out for me. I renamed the stock dialer and contacts, extracted the ones from the .zip and put them in the folder where dialer and contacts were. System>priv-apps>Dialer/Contacts. I then rebooted and they seem to be working, time will tell. There doesn't appear to be the oft desired Call Blocking. I think that's only on the newer versions, Marshmallow only. The newest versions of these apps that are on the Play Store won't work either, as they're MM only.
Wynnded said:
The original write up didn't pan out for me. I renamed the stock dialer and contacts, extracted the ones from the .zip and put them in the folder where dialer and contacts were. System>priv-apps>Dialer/Contacts. I then rebooted and they seem to be working, time will tell. There doesn't appear to be the oft desired Call Blocking. I think that's only on the newer versions, Marshmallow only. The newest versions of these apps that are on the Play Store won't work either, as they're MM only.
Click to expand...
Click to collapse
I did the same thing. On CF's 1.2.5 odex ROM, renamed the existing dialer.apk and contacts.apk, flashed the zip, and it worked.
GeoFX said:
I did the same thing. On CF's 1.2.5 odex ROM, renamed the existing dialer.apk and contacts.apk, flashed the zip, and it worked.
Click to expand...
Click to collapse
Flashing the .zip wasn't panning out for me. When I did it that way, I didn't have a dialing app. I could go to contacts and initiate a call from there, and it would ring through, but there wasn't an interface for the ongoing call. I couldn't close the line. I removed the .apks from the .zip and placed them in the appropriate folders then rebooted. Really only had one incoming call, yesterday, and it was fine. I don't think that we have video call though, not that I've ever used it, but I didn't notice the icon for it.
Can somebody help me out? I'm trying to figure out the difference between the 5.1 stock contacts and the Google contacts zipped with the Google dialer in the OP. I'm comparing the 2 side by side on my phone and I swear I cant find a difference. I know the Google dialer has differences I am specifically asking about the contacts app. Thanks.
koftheworld said:
This is a repost from the Moto X Pure section. LINK
Follow the instructions to backup and then flash the AOSP dialer and contacts in TWRP. This worked perfectly for me on my Turbo.
Click to expand...
Click to collapse
couldn't get this to work on my droid. i tried the OP way by deleting the folders and letting the flash repopulate them, but the problem is that the zip's folders aren't 'contacts' and 'dialer', but rather 'googlecontacts' and 'googledialer'. i tried to flash and then to rename the contacts and dialer apks, and replace them with the new ones, but i still didn't have a dialer to speak of on my phone after reboot.
anyone find another way that works? i would really love to have this dialer...
I renamed the .apks inside of the Contact and Dialer folders to .bak, then flashed this file.
By the way, I believe that these Google .apks have been updated, but I don't have a clue how to make a flashable .zip. Anyone want to have a go at it?
Wynnded said:
I renamed the .apks inside of the Contact and Dialer folders to .bak, then flashed this file.
Click to expand...
Click to collapse
this is where my hangup is. the folder structure in my system is priv-apps>dialer>dialer.apk; in the flashable zip it's priv-apps>googledialer>dialer.apk
whether or not i rename the original file or delete it entirely, the new dialer apk just isn't routing to the same directory. guess i'll have to be patient and keep on with what i have...
midnitemass said:
this is where my hangup is. the folder structure in my system is priv-apps>dialer>dialer.apk; in the flashable zip it's priv-apps>googledialer>dialer.apk
whether or not i rename the original file or delete it entirely, the new dialer apk just isn't routing to the same directory. guess i'll have to be patient and keep on with what i have...
Click to expand...
Click to collapse
Odd, in the flashable .zip, and as installed, mine drills down as: priv-app>GoogleDialer>GoogleDialer.apk. The structure is the same when I drill down into the .zip file that I keep because I have to rename and flash it again after ROM updates. I can't help you beyond that. Beyond my abilities.
If you are running CM 13, download the latest version of gapps stock from open gapps project. You will have Google Dialer. They have white listed our device"quark" as compatible.
Once flashed make sure that you set the app as default in your app settings.
Sent from my DROID Turbo using XDA-Developers mobile app