[Q] flash MIUI Messag app to CM7 - Desire Q&A, Help & Troubleshooting

Hi,
Is it possible to replace the CM7 messaging app with the MIUI one?

cardiak said:
Hi,
Is it possible to replace the CM7 messaging app with the MIUI one?
Click to expand...
Click to collapse
Nandroid and try.

cardiak said:
Hi,
Is it possible to replace the CM7 messaging app with the MIUI one?
Click to expand...
Click to collapse
I have tried file explorer from miui and it doesn't work, good luck anyway. report if you find a way

1. Download MIUI.
2. Download CM7.
3. Extract app from MIUI.
4. Replace app in CM7 with it.
5. Wipe Dalvik-cache.
6. Flash customized CM7.

cardiak said:
Hi,
Is it possible to replace the CM7 messaging app with the MIUI one?
Click to expand...
Click to collapse
Wont work!
try go sms instead! nice too!
-Toisan

It will not work.
Part of the reason is due to dependencies.
In other words, The messaging apk requires portions of code (and strings) located in other apks (such as contacts.apk and framework-res.apk). But even then, those apks require code from other apks, and so forth.
This cycle continues until pretty much all core APKs are MIUI APKs. And by that time, you are already using MIUI.
And this assumes that only APK dependencies are required - not specific system file changes.
Even if one string/piece of code is incorrectly declared, the entire APK may FC.

try Go SMS..
behave almost like MIUI msg, including the theme

does the latest gosms have the same slide down animations from MIUI instead of a popup?

Those are miui framework features.

fllash said:
It will not work.
Part of the reason is due to dependencies.
In other words, The messaging apk requires portions of code (and strings) located in other apks (such as contacts.apk and framework-res.apk). But even then, those apks require code from other apks, and so forth.
This cycle continues until pretty much all core APKs are MIUI APKs. And by that time, you are already using MIUI.
And this assumes that only APK dependencies are required - not specific system file changes.
Even if one string/piece of code is incorrectly declared, the entire APK may FC.
Click to expand...
Click to collapse
Basically this plus more.

Related

How to port sense ui?

How can i port sense ui to vanilla rom?
Which are interested files?
I already know about needing to edit init.rc, to put customize folder in system and to copy htc apps and libs but i can't get it working, how can i do?
Well, you'll definitely need the htc framework / res in /system/framework
along with Rosie, and the associated widgets in /system/app
adwinp said:
Well, you'll definitely need the htc framework / res in /system/framework
along with Rosie, and the associated widgets in /system/app
Click to expand...
Click to collapse
I have to edit framework-res too, right?
No, although you need com.htc.resources.apk.
Ok, i tried to do this but there are some problems
1. There aren't sense colors (for example highlight color is android's original orange)
2. There aren't sense images
3. Notify bar is white and not black
4. Rosie Home FC continuously
How can i fix?
1: copy over the framework from /system/framework from another rom
2: copy over the htc-specific apps from /system/app (you definitely need rosie.apk and htcaddprogramwidget.apk, amongst others)
adwinp said:
1: copy over the framework from /system/framework from another rom
2: copy over the htc-specific apps from /system/app (you definitely need rosie.apk and htcaddprogramwidget.apk, amongst others)
Click to expand...
Click to collapse
1. Already tried, stuck on bootscreen
2. Copied all htc apps
Ideas?
Just download Villain, and copy every apk starting with HTC from system/app.
You could try copying the framework too, but I've had a lot of problems porting it over 100% working vanilla builds. Try copying the framework over, but I can't guarantee it'll even boot. I think Villain is pushing it.. there are so many Sense apps and widgets that it seems sluggish.
Adwinp had it just right with his [email protected] roms. Perfect balance of Sense and no-sense. Very quick, but looked like sense.
nprussell said:
Just download Villain, and copy every apk starting with HTC from system/app.
You could try copying the framework too, but I've had a lot of problems porting it over 100% working vanilla builds. Try copying the framework over, but I can't guarantee it'll even boot. I think Villain is pushing it.. there are so many Sense apps and widgets that it seems sluggish.
Adwinp had it just right with his [email protected] roms. Perfect balance of Sense and no-sense. Very quick, but looked like sense.
Click to expand...
Click to collapse
I tried taking sense from villain and from hero/espresso hybrid:
- With villain if i copy the framework i can't get the phone to boot, if i don't copy the framework the rom starts but rosie give continuosly FC
- With espresso hybrid without copying the framework the rom doesn't recognize rosie as home, if i copy framework phone doesn't boot
Solutions?
Well
I can safely say it's being worked on . And Even more so that it is possible.
I currently have a working build based on Espresso Rosie with only a few problems in HTC widgets to iron out.
I can't promise when it'll get released (if at all) on my current schedule, but if I find the time to finish it for my personal needs. (I can't currently afford the time to keep flashing from my stock ROM to the Vanilla 2.1 I'm building it on).
I'm sure someone will beat me to a working build, but depending on how this next week goes with my real work, I may or may not have the time to finish it.
Just tried merging villain's framework-res with my rom's one, the phone remains on bootscreen
Exit93 said:
Just tried merging villain's framework-res with my rom's one, the phone remains on bootscreen
Click to expand...
Click to collapse
Out of interest - are you trying to re-sign the framework-res? Re-signing it with test keys will force it to hang on the boot screen.
I believe the launcher is the same... correct me if I'm wrong.
nprussell said:
Out of interest - are you trying to re-sign the framework-res? Re-signing it with test keys will force it to hang on the boot screen.
I believe the launcher is the same... correct me if I'm wrong.
Click to expand...
Click to collapse
Yeah...
I resigned it with stericson's method
So... we can't modify graphics in that res package? I wanted to customize it
Sorry for the little bit of thread hijacking here.
I too am interested in porting Sense, but to a Samsung device that's currently not supported in this forums - the Galaxy Spica (i5700).
I have tried to copy all HTC apps but the phone did not recognize them. For example, if I push all apps to /system/app and press the home button, the default home comes out and not sense (no prompt either).
Every other app FCs (for example com.htc.music or com.htc.browser).
Copying the HTC framework to the phone would result in eternal bootscreen.
Copying all the libs to the phone would result in hang

CM Apps on G2?

I really really want the CM messaging app on my G2. I know that I can't uninstall or replace the stock one, but is there a way to add in the one from CM and just use it instead?
Same here, I also wouldn't mind the CM browser as well.
It would appear that we can't remove or replace system apps, and we can't install it as an "update" either because the certs don't match. I think the only way to deal with this is to compile your own Browser.apk with a completely different package name so Android doesn't see a conflict.
along those lines would it be possible to somehow get the messaging.apk from MIUI to work on the G2?
rumitg2 said:
along those lines would it be possible to somehow get the messaging.apk from MIUI to work on the G2?
Click to expand...
Click to collapse
post it and I'll mess with it
here it is

[Q] [HELP] How to replace default dialer on CM 7.2?

Hi this must be a noob question, but i need to know how to replace the default dialer .apk file and also the contacts .apk file to something else (exDialer and exContacts) in the ROM itself.
Try extracting the apks from the stock ROM and replace it. Report back.
Sent from a Time Lord, using his TARDIS.
Nope it didn't seem to work!
It said installation failed.
Just follow these steps...there is a chance they might not work but you are free to try it
1.Install the dialer app(dont move it to sd card)
2.Use a file manager app with root permissions enabled(eg- ES File Explorer) and go to the "phone memory" then "data/app" copy the app's apk to the sd card
3.Now uninstall the app ....the install was for getting the apk file
4.Rename the backed up apk as "Phone.apk" (case-sensitive)
5.Backup your CM7 dialer by going into phone memory "system/app"....it will be named "Phone.apk".....back it up somewhere in the SD card
6.Now just take the apk of the dialer you wanted and copy it in phone memory "system/app"
7.Finally change the permissions of the apk as follows
--->In ES File Explorer,after moving your desired dialer's apk,long press for menu
--->Then select Properties
--->In the properties window there will be a button labelled "Change" just beside permissions
--->Then Select the 1st two check boxes in User,1st in group and 1st in other and press ok
8.Reboot the phone and pray to God it works
9.To revert back,just put the original "Phone.apk" in "system/app" and reboot
csoulr666 said:
8.Reboot the phone and pray to God it works
Click to expand...
Click to collapse
lol!
Sadly, no it didn't work. Damn this is tough!
Originally Posted by csoulr666
8.Reboot the phone and pray to God it works
Click to expand...
Click to collapse
lol!
Sadly, no it didn't work. Damn this is tough!
Click to expand...
Click to collapse
What happens?
Sent from my Wildfire S using XDA
You're not supposed to remove the default dialler app. It's a part of the system framework and the results when you do try to remove it will be severe. I believe that the phone aspect of Android is integrated into the default dialer apk (Both in sense and in AOSP).
In any case, there is no need to remove the dialler apk.You just install an alternate dialler and set that as default. It's works as if the original dialler was never there.
You cannot bring over the sense dialler though since that depends on the entire sense framework.
Just install exDialer and set it as default.
You can push it to /system/app if you would like. Leave the original one as it though.
vbhtt said:
What happens?
Sent from my Wildfire S using XDA
Click to expand...
Click to collapse
As soon as I replace the Phone.apk, it force closes to the homescreen. After I try restarting the device, it refuses to get past the Boot Screen Animation.
AceRoom said:
You're not supposed to remove the default dialler app. It's a part of the system framework and the results when you do try to remove it will be severe. I believe that the phone aspect of Android is integrated into the default dialer apk (Both in sense and in AOSP).
In any case, there is no need to remove the dialler apk.You just install an alternate dialler and set that as default. It's works as if the original dialler was never there.
You cannot bring over the sense dialler though since that depends on the entire sense framework.
Just install exDialer and set it as default.
You can push it to /system/app if you would like. Leave the original one as it though.
Click to expand...
Click to collapse
So you're saying there is no way I can natively replace the dialer to the exDialer in the Rom itself?
FYI: The Rom concerned here is HCMIUI 3.2 by Henry. Brilliant Rom otherwise!
Exactly, the default dialler cannot be replaced except perhaps by a full replacement say from the original cm7 rom or a themed version of your current dialler. You can only add a secondary dialler which will work in addition to the original one.
Check out the apk for the original Phone.apk
You'll find the components of the in-call screen.
cm7 themes for example retheme the framework which applies some modifications to the original in call screen.
AceRoom said:
Exactly, the default dialler cannot be replaced except perhaps by a full replacement say from the original cm7 rom
Click to expand...
Click to collapse
^ How do i do that? Actually this is exactly what i want to do, a full replacement!
You can probably take the Phone.apk and replace your current one with (Make sure you set the permissions to 644) but it really won't make much of a difference. Instead, just install the cm7 Theme Chooser and change your theme. HC MIUI is basically a themed cm7 rom with a MIUI flavor, MIUI apps and stellar animation effects!
Would love to get those on other ROMS!
There's actually a fuller MIUI (gb) but it's only on beta (There are some usability issues in which the colours in some apps are FUBAR) and the MIUI 4 (ics) is only on alpha... On my phone, the Phone crashed on making a calling the MIUI 4...
Well i guess this is not possible the way i thought i would!
maybe someone can make a patch or something that will do this( maybe for other default apps also) just a thought?!
How to set ExDialer as fault
AceRoom said:
You're not supposed to remove the default dialler app. It's a part of the system framework and the results when you do try to remove it will be severe. I believe that the phone aspect of Android is integrated into the default dialer apk (Both in sense and in AOSP).
In any case, there is no need to remove the dialler apk.You just install an alternate dialler and set that as default. It's works as if the original dialler was never there.
You cannot bring over the sense dialler though since that depends on the entire sense framework.
Just install exDialer and set it as default.
You can push it to /system/app if you would like. Leave the original one as it though.
Click to expand...
Click to collapse
How do i set exDialer as default dialer. I really want to set it as default one.
Thanks

[TEST] Android 5.0 deodexed system G900FXXU1BNL2

This is deodexed system part of G900FXXU1BNL2 ROM.
It's for chiefs and devs only and cannot be flashed directly.
Because i don't have S5 device, i cannot test it by myself. So, i'm asking qualified devs with S5 to try to make ROM based on this package and make a report if it can boot or even work.
Some important notes:
1) Because almost all APKs were originally odexed, all of them were required deodexing and then signing. So, original signatures are lost. I've used standard android development test certificate. Usually it's ok for system APK which never update from Play Store (only through ROM updates).
Thus, probably some APKs won't work correctly. You can delete such APK and replace it with one from Google Play store. Btw, Play Store is also resigned and may be won't work with Google servers (need to check).
Also, all resigned APKs won't be able to update in Play Store - so you need to replace such APKs with those from Play Store as well.
2) Following APKs i wasn't able to deodex without errors and not include in package:
Maps.apk
Music2.apk
DocumentService.apk
3) In Android 5.0 APKs having library, they are placed in lib folder of APK sub-folder. While deodexing, i've put these libs inside APKs. Probably, you need to extract these libs and put them all into /system/lib (same as all pre-5.0 ROMs).
4) I've placed APKs similar to pre-5.0 way (not every apk in its own folder). I hope it will work this way. If device won't be able to boot, then place them as in original system structure.
Those, who can build the ROM, please test it and tell me about result.
https://mega.co.nz/#!A4kynJpR!pobkpLuFBAUnhtnUwgJSa2KfT6S8apqWwYD5Asb83DU
Update 1:
- contains only modified parts of system, i.e.: only framework, app, priv-app dirs.
- app and priv-app dirs now have correct structure: each apk in its own dir and lib sub-dir.
- not re-signed, i.e. all apks contain original Samsung or Google certificate
- oops, i've forgot to delete Maps.apk, Music2.apk and DocumetService.apk - they were deodexed with errors and most likely won't work.
https://mega.co.nz/#!1l1BlSza!QN1fNyrU7qtwBu6xqkBRH85h3rL81Rvlc-JZv1OtMeE
Nice build
Sadly im just a normal rom builder with knowledge on v4.4 and below, idunno on v5.0 have to learn it to make good roms out of it
Procedures with 5.0 should be the same. The only difference i've found is placing apks in separate subfolder. I think, it required only for pre-odexed ROMs. So, just need to make an usual ROM, same as 4.4 and then check if it work.
sorg said:
Procedures with 5.0 should be the same. The only difference i've found is placing apks in separate subfolder. I think, it required only for pre-odexed ROMs. So, just need to make an usual ROM, same as 4.4 and then check if it work.
Click to expand...
Click to collapse
Very good than ill give it a try when home
But im not an advanced dev sadly dont expect much [emoji14]
I've tested it out, by putting all your deodexed apk's in their folders of my odexed XtreStoLite 2.0 TW Lollipop BETA ROM (and removed the 'arm' folders), also extracted out the lib files from your apk files, and put them in the 'lib' folder.
And replaced mine framework folder with your deodexed one...
But the phone doesn't boot up then.
So your deodexed files are probably not working.
edgarf28 said:
I've tested it out, by putting all your deodexed apk's in their folders of my odexed XtreStoLite 2.0 TW Lollipop BETA ROM (and removed the 'arm' folders), also extracted out the lib files from your apk files, and put them in the 'lib' folder.
And replaced mine framework folder with your deodexed one...
But the phone doesn't boot up then.
So your deodexed files are probably not working.
Click to expand...
Click to collapse
No log?
edgarf28 said:
I've tested it out, by putting all your deodexed apk's in their folders of my odexed XtreStoLite 2.0 TW Lollipop BETA ROM (and removed the 'arm' folders), also extracted out the lib files from your apk files, and put them in the 'lib' folder.
And replaced mine framework folder with your deodexed one...
But the phone doesn't boot up then.
So your deodexed files are probably not working.
Click to expand...
Click to collapse
logcat would be helpful.
Also you can try it step by step. At first, use odexed framework, and my deodexed APKs in subfolders (use my framework.apk and twframework.apk for certificate match).
Then try to put deodexed APKs into common folder (like 4.4 ROM).
If either of above will work, then try to replace the framework jar files.
It's not exactly because of wrong deodexing. May be you need to keep /arm/boot.* files in order to pass initial boot. And then may be OS will re-create new boot.
So, need to try different combination and look what you get in logcat. May be 5.0 requires some additional steps for deodexed ROMs.
Btw, after extracting libs, don't delete them from APKs.
Just checked CM12 ROM structure:
1) copy each APK in its separate folder (same as stock 5.0 ROM).
2) extract lib to separate lib folder (same as stock 5.0 ROM)
3) all arm folders should be deleted (including framework/arm)
http://www.xda-developers.com/android/deodex-lollipop-system-apps-with-ease/ ???
I've tried to replace some apps by deodexed singly (e.g. SamsungCamera3, SecMms_Candy, TeleService), of course with deleted corresponding arm folder
Unfortunately, none of them work (even completely unmodified), only FC ...
_alexndr said:
I've tried to replace some apps by deodexed singly (e.g. SamsungCamera3, SecMms_Candy, TeleService), of course with deleted corresponding arm folder
Unfortunately, none of them work (even completely unmodified), only FC ...
Click to expand...
Click to collapse
can you provide logcat? FC may be related to incompatible certificate.
sorg said:
can you provide logcat? FC may be related to incompatible certificate.
Click to expand...
Click to collapse
See attachment... logcat while I'm trying to run deodexed SamsungCamera3
_alexndr said:
See attachment... logcat while I'm trying to run deodexed SamsungCamera3
Click to expand...
Click to collapse
I don't see anything about SamsungCamera3 in logcat... If you get FC, then at least FC reason should be shown in logcat.
If it fc post the dumpstate_app_error.txt.gz from data/log rather than taking a log. Guaranteed to include all info
sorg said:
I don't see anything about SamsungCamera3 in logcat... If you get FC, then at least FC reason should be shown in logcat.
Click to expand...
Click to collapse
My mistake. I have not looked at sending and uploaded incomplete file. Now it should be ok
Goldie said:
If it fc post the dumpstate_app_error.txt.gz from data/log rather than taking a log. Guaranteed to include all info
Click to expand...
Click to collapse
This file is also attached
Assuming this permission is in manifest to start with it looks like some issue with actually reading the manifest?
12-12 09:09:30.688 6530 6530 E AndroidRuntime: Caused by: java.lang.SecurityException: Requires SET_ANIMATION_SCALE permission
Goldie said:
Assuming this permission is in manifest to start with it looks like some issue with actually reading the manifest?
12-12 09:09:30.688 6530 6530 E AndroidRuntime: Caused by: java.lang.SecurityException: Requires SET_ANIMATION_SCALE permission
Click to expand...
Click to collapse
While deodexing i didn't touch neither resources nor manifest, only injected dex then signed and then aligned. Probably, because re-signed apk uses different certificate (obviously, i don't have Samsung's private key), OS denies some system level access.
Usually, when i create custom ROM i resign all APKs which use Samsung certificate - thus all system APKs share the same signature and everything works.
Why do you resign all samsung apks? System apps do not require signing unless manifest is changed. Is this something you have always done?
Disabling signature checking may fix this then I guess or not resigning in the first place
Goldie said:
Why do you resign all samsung apks? System apps do not require signing unless manifest is changed. Is this something you have always done?
Disabling signature checking may fix this then I guess or not resigning in the first place
Click to expand...
Click to collapse
No problem, i will update pack with updated structure without resigning.
In my custom ROM i do many changes, sometimes including manifest change and adding additional system APKs imported from other devices or written by myself.
sorg said:
While deodexing i didn't touch neither resources nor manifest, only injected dex then signed and then aligned. Probably, because re-signed apk uses different certificate (obviously, i don't have Samsung's private key), OS denies some system level access.
Click to expand...
Click to collapse
Goldie said:
Why do you resign all samsung apks? System apps do not require signing unless manifest is changed. Is this something you have always done?
Disabling signature checking may fix this then I guess or not resigning in the first place
Click to expand...
Click to collapse
And... this was the cause :laugh:
I've put classes.dex from @sorg 's apk to original SamsungCamera3.apk and it works as deodexed !!!!!!
I will try to baksmali, then modify the code and smali again

C-apps

Download latest Cyanogen Apps Package for CM based rom
This flashable zip file includes:
1. Latest Audio-fx from Cyanogen
2. Theme chooser app
3. Dialer with Truecaller
4. Boxer email app
5. Latest Gallery from Cyanogen (it will replace your old Gallery)
6. Cyanogen account
7. Latest Cyanogen camera (much better than old camera and it will replace your old camera)
Download: https://drive.google.com/file/d/0B1cFIK50hEmZLVBHX2pBejBlRFk/view?usp=sharing
dibyenduroy said:
Download latest Cyanogen Apps Package for CM based rom
This flashable zip file includes:
1. Latest Audio-fx from Cyanogen
2. Theme chooser app
3. Dialer with Truecaller
4. Boxer email app
5. Latest Gallery from Cyanogen (it will replace your old Gallery)
6. Cyanogen account
7. Latest Cyanogen camera (much better than old camera and it will replace your old camera)
Download: https://drive.google.com/file/d/0B1cFIK50hEmZLVBHX2pBejBlRFk/view?usp=sharing
Click to expand...
Click to collapse
In the official package the Camera wasn't there
No.
dibyenduroy said:
No.
Click to expand...
Click to collapse
So? Did you add it?
Yes. Latest cyanogen camera is included in this zip file.
Do you know how to install only the app themer....i don't want any other apps @dibyenduroy or @ivan290
And will it work on CM13
cksup said:
Do you know how to install only the app themer....i don't want any other apps @dibyenduroy or @ivan290
And will it work on CM13
Click to expand...
Click to collapse
Find the attached file for Themer. Check it. CM13 I am not sure. It should work.
View attachment themer.zip
I like per app themer most
Argh!
dibyenduroy said:
Find the attached file for Themer. Check it. CM13 I am not sure. It should work.
View attachment 3540637
Click to expand...
Click to collapse
The 'themer.zip' file deleted my phone app! Per app themer was installed perfectly though (CM 12.1)
If it is possible then @dibyenduroy please made a individual flashable zip of all apps.
I want only gallery and camera app.
I've done some split apps.
All tested on AOSP 5.1.1 by Percy-G2 without gApps.
Camera crashes when using panorama mode; Gallery takes a long time after boot to notice the external storage but then is almost perfect!
Screen Recorder is perfect for the little it does (it reliably starts the up+power built-in video screenshot), and Boxer... uh, I can login to Gmail fine with it!
I haven't implemented backup.sh, frankly with most people jumping to TWRP with bulk install this is added complexity for little gain (and I have little free time in these 2 weeks, heh)
anilkashyap.tech said:
If it is possible then @dibyenduroy please made a individual flashable zip of all apps.
I want only gallery and camera app.
Click to expand...
Click to collapse
+1
Ryccardo said:
I've done some split apps.
All tested on AOSP 5.1.1 by Percy-G2 without gApps.
Camera crashes when using panorama mode; Gallery takes a long time after boot to notice the external storage but then is almost perfect!
Screen Recorder is perfect for the little it does (it reliably starts the up+power built-in video screenshot), and Boxer... uh, I can login to Gmail fine with it!
I haven't implemented backup.sh, frankly with most people jumping to TWRP with bulk install this is added complexity for little gain (and I have little free time in these 2 weeks, heh)
Click to expand...
Click to collapse
Great work man! Just wish all the apps were separated. Though i know I'm asking for too much
Maybe the OP can integrate Aroma Installer? That be much more convenient, no?
Guys it works for any cm ROM????plz reply
Sent from my Moto E using XDA Free mobile app
Great...The camera app is way better than the one i had

Categories

Resources