First off, all credit on figuring out this mod goes to untermensch, thanks a ton!
Please see his post here: http://forum.xda-developers.com/showpost.php?p=8542257&postcount=6114
So, this is the Mms.apk from Cyanogen Mod 5.0.8 (taken from the nexus 1 build) and modified to support the samsung puzzle-lock messaging notifications!
UPDATE 10/12/2010: added a smaller, faster version, with all images optimized, cut the file-size almost in half. New version is "Optimized_CM_5_0_8_with_puzzle_Mms.apk" though I'm leaving the original file attached to the post for anyone that wants to test both files.
For anyone that's never used an AOSP/CM android rom, you can see screenshots of the app here:
http://picasaweb.google.com/113127051130934911253/AndroidCM508MMS?feat=directlink
If you already use an AOSP/CM mms.apk, this can be pushed right on top of your existing apk.
To install if you still use the touchwiz mms apk, either use adb/terminal/root explorer to delete your existing mms.apk from /system/app then reboot, and uninstall "com.android.mms" then reboot into recovery, and clear cache and dalvik-cache.
Reboot one last time, rename this apk Mms.apk, and adb push to /system/app
Cheers everyone, and thanks again to untermensch for making this possible!
Awesome thanks for sharing your findings! Just pushed it to Bionix 1.7 and MMS seems to still work and have the puzzle piece. After getting so used to that puzzle piece I go nuts without it haha.
Thanks! Works great
Very cool thanks Man.
Updated the OP with a smaller, faster version with all images optimized, cuts the file-size almost in half.
Cheers everyone, =)
has this been tested with a stock 2.2 Mms.apk?
tyty! just pushed it to frankin-twiz. made it the perfect ROM.
I've never actually used Stock Android. Can I get some screenshots to see what it looks like? Don't want to change it if I don't end up liking it
kuhan said:
I've never actually used Stock Android. Can I get some screenshots to see what it looks like? Don't want to change it if I don't end up liking it
Click to expand...
Click to collapse
Hi,
I posted a link in the OP to some screenshots. The biggest thing for me, is that instead of making delivery reports a notification that has to be cleared after every sms/mms, it shows an icon, in-line with the message text, that changes based on status (pending, delivered, error, etc.)
Also, this does not use the "chat bubbles" like the touchwiz mms app. Personally, I don't really care for them in the touchwiz mms, since it truncates long messages, forcing you to click each message to view the full text.
Anyway, hope this helps, cheers, =)
I followed you installation instructions but did not see the app named com.android.mms after deleting mms.apk and rebooting i didnt see it in titanium or the stock app manager...now i pushed the file but it wont show up after restarting 3 times? Did i do something wrong? And yes i wiped cache and dalvik cache twice
Vibrant - Bionix 1.9.1 - JAC's Xmod kernel v1 - ext2 lag fix
kennyp987 said:
I followed you installation instructions but did not see the app named com.android.mms after deleting mms.apk and rebooting i didnt see it in titanium or the stock app manager...now i pushed the file but it wont show up after restarting 3 times? Did i do something wrong? And yes i wiped cache and dalvik cache twice
Vibrant - Bionix 1.9.1 - JAC's Xmod kernel v1 - ext2 lag fix
Click to expand...
Click to collapse
Hi,
I've never run into that before, everytime you remove/delete an apk from /system/app it should leave residual data. Granted, this is from a terminal/shell approach, I don't personally use titanium, root explorer, etc. but do almost everything from an adb shell.
The only thing I can suggest is try deleting the mms.apk again manually, from a shell, and reboot and then go to /settings/applications/manage applications and hit menu, change filter to all, and then search for anything that looks like com.android.mms
Sorry about that, not sure why its not working for you, do you run a custom rom?
cheers, =)
s0niqu3 said:
Hi,
I've never run into that before, everytime you remove/delete an apk from /system/app it should leave residual data. Granted, this is from a terminal/shell approach, I don't personally use titanium, root explorer, etc. but do almost everything from an adb shell.
The only thing I can suggest is try deleting the mms.apk again manually, from a shell, and reboot and then go to /settings/applications/manage applications and hit menu, change filter to all, and then search for anything that looks like com.android.mms
Sorry about that, not sure why its not working for you, do you run a custom rom?
cheers, =)
Click to expand...
Click to collapse
Yes bionix 1.9.1
Vibrant - Bionix 1.9.1 - JAC's Xmod kernel v1 - ext2 lag fix
Thank you!
This phone is looking more and more like android and less like an iphone everyday thanks!
coming from touchwiz make sure to remove Mms.odex as well
Confirmed working in Bionix Fusion 1.0.
s0niqu3:.
I know I posted this to Viral when he made the mods to the Mms.apk back in Bionix 1.7ish to get it black, but it never got fixed. The background color of MMS content (easily seen when adding audio) is still a light blue. Think you can change it to black to match?
Thanks for this. I tried following the instructions but it didn't cooperate. My mms.apk was still there after reboot. So I just replaced it with the new one using root explorer. Seems to work without a problem. Running Fusion 1.0
sent from my Vibrant - Bionix Fusion 1.0
kennyp987 said:
Yes bionix 1.9.1
Vibrant - Bionix 1.9.1 - JAC's Xmod kernel v1 - ext2 lag fix
Click to expand...
Click to collapse
Fix permissions fixed it
Vibrant - Hybrid R4 - JAC's Xmod kernel v1 - ext2 lag fix
Works great for me. I had to use adb to push it though, root explorer wouldn't install it.
So nice to get rid of that cartoon like Samsung app!
Works great for me; Bionix 1.9 OC/UV/Voodoo.
I want the TW MMS icon though... the AOSP icon looks stupid.
Edit: Switched them with the pretty TW icons (used larger/higher res icons from each apk, picking the best ones). Works perfectly!
dude i love u no homo
I've done lots of reading and still can't find a thread for this one.
I'm running Win7 Home Premium x64 and the latest version of the FlashTool (v0.2.4).
Everything works like a charm, except for the xRecovery Installation. That part freezes up.
And speaking of the xRecovery, the Install Fix only works for me sometimes on my X10.
On my X10 I'm running v2.1 Build v2.0.A.0.504. Basically when the install doesn't work, I end up uninstalling the SuperUser App (after giving ROOT permissions to xRecovery Installer), and then it installs just fine.
Only once was I able to get the xRecovery installer to work once (without uninstalling SuperUser App). And xRecovery wasn't even given ROOT permissions yet. It all happened on the fly, I'm guessing ... the way it was supposed to. Haven't found a way to reduplicate this yet.
So, anyone else find a fix for these issues?
P.S. I can accomplish what I want with my own methods, but I really like the easy X10FlashTool method the best :-D SOOOOO much faster.
install superuser & busybox from market.
and install xRecovery like a normal .apk with one of the file manager apps.
xRecovery
Ok, yah I was going with the version of BusyBox that came with either the 2.1 image or came with the FlashTool.
Just to be clear, I haven't actually had any problems installing the APK for xRecovery... which turns out was version 1.15 and the latest is 1.17 (hah oops, silly me). So much for being lazy and not re-downloading the BusyBox App. My bad for that. (Good thing I finally figured out how to get to my apps and back them up via Root Explorer!)
Just to be clear, I never had a problem actually installing the xRecovery APK. That works fine, it's just opening the xRecovery installer (after installing the APK) and then running it, i get the 3 red circles with a slash, instead of 3 green checks. Did you get that from my first post? Or did it sound like something else?
TheArkive said:
Ok, yah I was going with the version of BusyBox that came with either the 2.1 image or came with the FlashTool.
Just to be clear, I haven't actually had any problems installing the APK for xRecovery... which turns out was version 1.15 and the latest is 1.17 (hah oops, silly me). So much for being lazy and not re-downloading the BusyBox App. My bad for that. (Good thing I finally figured out how to get to my apps and back them up via Root Explorer!)
Just to be clear, I never had a problem actually installing the xRecovery APK. That works fine, it's just opening the xRecovery installer (after installing the APK) and then running it, i get the 3 red circles with a slash, instead of 3 green checks. Did you get that from my first post? Or did it sound like something else?
Click to expand...
Click to collapse
Just use busybox from market and problem solved
if you're installed busybox from somewhere else, that's the problem.
install updated busybox from market.
and problem solved.
you should get green arows.
reboot, tap back button few times and you're good to go.
Alright
Thanks guys! That definitely makes sense.
im currently running the cyanogen 6.1.3 gingerbread v01. I tried to install the Pendo Trans Blue Market 2.2.11. I put it on my sd card and supposedly successfully installed via xrecovery. When i go to load the same old green market appears, any insight? (It's already running the 2.2.11 version, just not the blue theme)
hi all,
i installed cyanogenmod 7 and this theme http://forum.xda-developers.com/showthread.php?t=896943
then device booted it can not open my phone please help me what can i do ?
At the top of the screen it says:
~ [UPDATED!] Xtreme X10 Mini/Pro theme! ~
(And 2.1 [For Build 2.0.A.0.504 without zip file and 2.0.2.A.0.24 with the zip file])
The writing in blue is telling you which firmware the theme is compatible with. In order for you to have installed CM7 you would have build 2.1.1.A.0.6 loaded on your device. the theme you tried installing isn't compatible with you 2.1 firmware and neither is it with CM7.
To fix this, do a SEUS repair and reinstall CM7 and search the market for CM7 themes (search "CM7") and in future read the firmware requirements before installing anything. In the case of installing CM7 themes, if it doesn't say "CM7 theme" DON'T INSTALL!!!
Good luck
Originally Posted by raj_k_r
Download any CM7 theme from xda or from the market (search for cm7 in the market), install it (only apk files) and then goto theme chooser application (already present in the current minicm7 ROM), select a theme, apply and restart. Thats it!!!!!!!!!. You will get a warning and you can say continue anyway. I tried almost 20 themes and all worked. And good thing about CM7 is, you will have all the themes installed and you can change any time you want by just selecting a theme and restarting. Not like CM6 wherein you need to flash the theme everytime. This is one of the thing I liked most about CM7.
Also if you want to change only the font, download fontchanger from market (free app), download any font you like (.ttf file) and copy under .fontchanger folder in sdcard, open fontchanger application, select the font and apply it. You need to restart your device (sometimes twice) and thats it!!!!!!!. It is working in my device atleast (I changed almost 15 to 20 times both the themes and font without any problem) and I am really enjoying this ROM. SO much flexibility.
^a little more explanation from raj_k_r on installing themes on CM7
ops to late...
howto take away posts?
christophermaisch said:
At the top of the screen it says:
~ [UPDATED!] Xtreme X10 Mini/Pro theme! ~
(And 2.1 [For Build 2.0.A.0.504 without zip file and 2.0.2.A.0.24 with the zip file])
The writing in blue is telling you which firmware the theme is compatible with. In order for you to have installed CM7 you would have build 2.1.1.A.0.6 loaded on your device. the theme you tried installing isn't compatible with you 2.1 firmware and neither is it with CM7.
To fix this, do a SEUS repair and reinstall CM7 and search the market for CM7 themes (search "CM7") and in future read the firmware requirements before installing anything. In the case of installing CM7 themes, if it doesn't say "CM7 theme" DON'T INSTALL!!!
Good luck
Click to expand...
Click to collapse
thanks,
but device can not open/close i can't use update service but it says "close the phone and push back button"..
just try to do a new flash in xrecovery (if not working try to format system)
urqun said:
thanks,
but device can not open/close i can't use update service but it says "close the phone and push back button"..
Click to expand...
Click to collapse
What you must do is switch the phone off, hold in the back button and insert the USB when SEUS is searching for the phone. If its still looping, insert the USB, hold down the power, home (the middle button) and back button together until the phone resets (it with vibrate) then ONLY RELEASE THE POWER AND HOME BUTTON and KEEP the back button pressed until SEUS tells you to release it the it should work.
thanks christophermaisch i tried it and flashing with seus manager thanks again
Hi,
In my brief run-in with the TW update before going back to stock, the only thing I was really impressed with was the Video Player (not the red icon Google one, the white icon one).
I've tried ADB'ing the VideoPlayer.apk into /system/app following an unsuccessful attempt to install it normally and the icon is there but it FC's.
Has anyone been successful in installing this app on the Stock 3.1 ROM and if so, how?
I'm not sure how to check what possible dependencies it has.
Thanks,
Neil.
I don't think there's much hope for me. Using ADB logging it seems to raise an exception calling a maethod com.andoid.widget.SearchView.SetSearchViewAnimation, which as far I can see isn't listed in the Android SDK...