Related
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
Is there any way we can get the new swype update incorporated into some of the ROMs? Or do we have to download it separately?
shahud said:
Is there any way we can get the new swype update incorporated into some of the ROMs? Or do we have to download it separately?
Click to expand...
Click to collapse
I would imagine it will get incorporated into future ROMs or included in an update to a current ROM. But if you want it now you will have to download it separately. Before you can download 3.0 you will have to switch your default keyboard to another keyboard then using a file explorer app such as root explorer go in and delete these four files: /system/app/swype.apk, /data/data/com.swype.android.inputmethod, /dbdata/databases/com.swype.android.inputmethod, and /system/lib/libswypecore.so
swype 3.0 beta has drm/licensing stuff in it..so it will expire at some point if we incorporate as is into the roms (comrom/etc)
im hopeful we can get that stuff removed as was done for 2.29 that we were using in tsm roms
Okay cool. Thanks for the replies
Spent some time trying to get swype 3b installed.
The installer apparently requires the old version to be removed. So I did (Titanium). The installer went all the way through the download process, but actually installing gave me "was not installed." Gee, what a helpful error.
So I tried downloading an apk from the web and got the same error. So I tried using root explorer to install the apk manually (including setting permissions and changing owner). It FC'd repeatedly after reboot. So I removed it.
Then I tried adb install. That didn't work either. Then, realizing that Titanium didn't have a backup for my original Swype, I tried installing the v2 apk via adb, but that doesn't work either.
Ugh. Now I don't have Swype at all! Any ideas? Can someone tell me if there's a unique version for this phone or something?
idheitmann said:
Spent some time trying to get swype 3b installed.
The installer apparently requires the old version to be removed. So I did (Titanium). The installer went all the way through the download process, but actually installing gave me "was not installed." Gee, what a helpful error.
So I tried downloading an apk from the web and got the same error. So I tried using root explorer to install the apk manually (including setting permissions and changing owner). It FC'd repeatedly after reboot. So I removed it.
Then I tried adb install. That didn't work either. Then, realizing that Titanium didn't have a backup for my original Swype, I tried installing the v2 apk via adb, but that doesn't work either.
Ugh. Now I don't have Swype at all! Any ideas? Can someone tell me if there's a unique version for this phone or something?
Click to expand...
Click to collapse
Me too on the Swype problem. I had 3.0 working on the CM7 Alpha that jt built but that was a little to buggy so I switched to CommROM 2.0. Because of the way Swype is integrated into CommROM, it can't be easily replaced. Would love for someone to point me in the right direction on this.
I'm pretty sure I read somewhere that you're not supposed to download swype beta if you have a phone that comes with swype installed. I'm not sure why but I read that it won't work.
Choose a different keyboard. Uninstall old swype. Reboot, then install new beta.
Worked for me.
Yeah, I struggled with that issue last night (getting "was not installed" with 3.0 after removing 2)... but don't fret, it turns out the solution (which I discovered by mistake) is to literally just reboot your phone before installing 3.0. Hurr.
Keep in mind you still do have to manually delete /system/lib/libswypecore.so using Root Explorer or the like after uninstalling Swpye 2 via TB -- otherwise you will have problems.
Is there an echo in here?
And I did not have to manually delete any files and everything is working fine.
I used Titanium to delete the original, then used the installer without problems. That said, I don't like 3.0 and went back to the old version.
Working!
After seeing your replies, I deleted the lib file. I also ran
adb shell pm list packages
and found com.swype.android.inputmethod was still installed:
adb uninstall com.swype.android.inputmethod
then reboot.
then used swype little installer package.
and now it works!
Easy Peasy Lemon Squeezy
Delete using Titanium, reboot, install using the standard Swype installer seems to work.
Keeps getting better with every release!!!
I had been having some issues with the latest Swype beta's auto-correction, in that when I was touch-typing for non-dictionary words (like acronyms, etc.), the auto-correction was doing its job and was 'auto-correcting'; but of course, I didn't want these words corrected! (I guess I was still operating under Swype's old rules which were when you touch-typed, it always assumed you were entering the correct spelling of whatever you had typed). So I turned off automatic auto-correct, and now I just have the word suggestion bar. This process seems to be working much better for me now.
black alien trial period issues
nitsuj17 said:
swype 3.0 beta has drm/licensing stuff in it..so it will expire at some point if we incorporate as is into the roms (comrom/etc)
im hopeful we can get that stuff removed as was done for 2.29 that we were using in tsm roms
Click to expand...
Click to collapse
is gunnermike aware of this? i am using his black alien theme, which is awesome, and i was getting a trial period ended error last night and swype will not swype it just works like a regular keyboard.
gonna try the solution above after work
Thanks for the great ROM
wscaddie56 said:
is gunnermike aware of this? i am using his black alien theme, which is awesome, and i was getting a trial period ended error last night and swype will not swype it just works like a regular keyboard.
gonna try the solution above after work
Thanks for the great ROM
Click to expand...
Click to collapse
Yeah 2.29 very much expired, once a recalled how to uninstall the old and reinstall the new I'm running 3.6 now myself and even if it expires in awhile its a five minute process to go one from to the latest
idheitmann said:
Spent some time trying to get swype 3b installed.
The installer apparently requires the old version to be removed. So I did (Titanium). The installer went all the way through the download process, but actually installing gave me "was not installed." Gee, what a helpful error.
So I tried downloading an apk from the web and got the same error. So I tried using root explorer to install the apk manually (including setting permissions and changing owner). It FC'd repeatedly after reboot. So I removed it.
Then I tried adb install. That didn't work either. Then, realizing that Titanium didn't have a backup for my original Swype, I tried installing the v2 apk via adb, but that doesn't work either.
Ugh. Now I don't have Swype at all! Any ideas? Can someone tell me if there's a unique version for this phone or something?
Click to expand...
Click to collapse
looks like you forgot to reboot!
Sent from E.T.
Are there any other file managers besides root explorer that take advantage of root access?
I'm sure root explorer is good and all, I just don't feel like forking over 3 or 4 bucks or whatever for it - I don't like paying for apps, it's just one more thing that isn't a free download if you have to reflash your ROM or do a factory reset or something. Learned that lesson a few years ago with an 2nd gen iPod Touch.
That being said, there's plenty of free file managers out there, will any of them perform root operations such as deleting Swype.apk manually?
Once you purchase an app it is linked to your gmail acct. If you wipe or reflash it's still your's. Save yourself the headache and just buy root explorer.
Sent from my SCH-I500 using XDA App
This isn't what I would call a troublesome thing, but I found it odd. I'm trying to learn all I can about Android's inner workings, so perhaps someone around here could clue me in on this behavior.
I decided earlier to tweak my SystemUI.apk. I pulled it, tweaked it, pushed it back, and it started into an FC loop. In retaliation, I deleted it, rebooted, and restored the TB copy. I tried my tweak again, pushed it back, and noticed no reaction from Android whatsoever. I took a peek at my /system/app directory, and saw that my SystemUI.apk was now neighbored by a com.android.systemui.apk that TB dropped in there.
This is where it gets a bit odd. For yucks, I deleted both apks, cleaned the DC, booted recovery, and dropped in a brand new SystemUI.apk extracted from the ROM I'm currently using. After rebooting, I had no status bar, TB reported it as not installed, and logcat complained about it missing.
So, I deleted my SystemUI.apk, cleaned the DC - it found one file - rebooted, restored the TB backup, rebooted, and all was fine. I renamed com.android.systemui.apk to SystemUI.apk, cleaned the DC, rebooted, and still no problems. I deleted SystemUI.apk, pushed a fresh copy from the ROM again, and still no problems.
That brings me to my question. Could anybody provide insight as to why Android was ignoring SystemUI.apk after having removed com.android.systemui.apk and rebooting?
i am currently building a rom for the samsung captivate built off 2.3.5.
The base im using is stock - deodexed/ ziped / minorly changed
this base flashes and works just fine!
what i am doing to it:
remove bloat.
- at&t apps,
- protips.apk
- remove broken swype
- remove stock email (not gmail)
- removed stock launcher
change to hacked camera.apk
remove bootsound
remove shutdown sound
change bootanimation
added user apps in data/apps
added widget picker in system/app
changed default wallpaper in framework_res.apk
changed install script
changed CSC
custom twwallpaperchooser
everything works fine through the install.
but durring the "setup" on first boot " phone setup wizard " will force close right at the step where you setup your google sign in.
BUT THATS NOT THE PROBLEM, (just the first sign of it)
the real problem is any apps installed after flashing do not show up in data/apps
any apps installed through the flash are there, but any installed after ARENT.
and no they arent on the SD card.
the apps will slowly disappear after installing one by one.
when i reboot THEY ALL DISAPPEAR!!!
it seems that the apps install to cache or memory.
as the memory gets cleared or you reboot, they get wiped away!
i have tried various things to fix this
i have rebuilt my rom MANY times.
with and without my framework res changed file
with and without my custom install script
with and without removing stock launcher
with and without changed CSC files.
with and without twwallpaperchooser
if i flash the base i was working from again, all is good.
this only seems to be an issue when i flash data/apps from the zip file. however i have used a script from a rom that successfully flashed data/apps before without this issue, so i do not think it is a permission problem....
im stuck and lost.
more specific, rewritten description i emailed to a few friends
holy hell i bet youve been busy...
me too, i finally have my rom built. for KH2 KJ1 and KJ2 !!
have it down to an easy process now. install script working!
but im having one final issue and cant find any useful info on it anywhere and its very specific
**I know KJ1 and KJ2 install any app to the SD if possible by default. any app on SD will not be affected by this issue ***until it is moved to phone
if I build my rom to install apps to data/app (through cwm flash )- any app that gets installed after (through market or sideload) will slowly disappear after some use or immediately after reboot. they also will not show up in data/app or system/app when installed ** once again not including apps on SD. and if apps on SD are moved to data/app they do not end up there. they disappear.
this leads me to beleive that they are installing to cache or memory, as the memory gets cleared or the phone reboots. they are gone!
if i build my rom without user /data/apps (and without that part of the script).
everything is fine. any app installed after shows up in data/app and is still there after reboot.
i have also used unmodified scripts with and without the package_extract ("data", "/data")
that have been known to work with the original rom they were taken from. without the issue i am seeing.
so i do not think it is a script / permission issue not allowing the system to write new data to that location. but i could be wrong.
my rom is ready for release once i can get this last part figured out. otherwise ill have to release with no user apps... any input would be greatly appreciated.
thanks again!
Click to expand...
Click to collapse
one search i came across mentioned something about possibly not being converted to rfs, but I have flashed to stock with re-partitioning ( rfs for sure ) and the rom and kernel i am building does not support it so that shouldn't be an issue.
from what other rom builders have told me this is an issue with gingerbread roms.
have apps copied to SD card and ask users to install manually.
Dude just found this post....sorry i was busy with KJ2
glad you got a tempory fix
ya you gave me the fix in the PM! LOL
TRusselo said:
ya you gave me the fix in the PM! LOL
Click to expand...
Click to collapse
you just got spanked!!
I found that gg.jpg picture of Alessandra Ambrosio inside the Leedroid APK under res/drawable-hdps. I tried to replace it with a black 540x960 "gg.jpg" file but then I couldn't figure out how to reinstall Leedroid with the resulting APK. I had also tried updating Leedroid Tweaks but none of the versions I downloaded seemed to install successfully. Is the latest build of Eternity 3.0 running the latest version of Leedroid Tweaks? Is there a flashable or installable Leedroid Tweaks with a black background instead in case someone wants that as an option?
I also had a problem with Leedroid Tweaks in r193 where when I tried to change the overscroll color, the phone would crash and bootloop and I had to start all over again. Is that fixed in r218?
What's the deal with alternative kernels for r218? People are talking about chad's kernel having better battery life and being faster. Is it included in r218 or do I need to download and flash it separately? Is "InfectedROM_Eternity-SynergyforCHAD-b1.zip" the same as r218 except with chad's kernel and the Eternity blue theme? I'd like the "stock" theme rather than the blue theme. If I need to flash chad's kernel separately, from where can I download it? Is it already overclocked? Or is the overclocking something you have to do with "System Panel" or "SetCPU"?
So I was able to open up the zip file for the latest Eternity 3.0 ROM and I extracted "system/app/TweaksCDMA.apk" to my desktop and then I opened that file with IZArc, removed res/drawable-hdpi/gg.jpg, and then saved the file. Then I opened the apk again and put a new black gg.jpg file in res/drawable-hdpi and then saved it again. Then I deleted "system/app/TweaksCDMA.apk" from the Eternity ROM zip and replaced it with my modified version. After flashing the updated ROM file I have found that Leedroid Tweaks no longer has the image of Alessandra Ambrosio as the background so it's SFW
As an aside, I'm still unable to change the overscroll color with Leedroid Tweaks without having to wipe/reflash the ROM. For some reason that setting with this version of Leedroid Tweaks makes the phone immediately bootloop. Lesson learned. Stay away until someone updates Leedroid in this ROM. This is still true as of the r218 of Eternity.
If anyone knows a solution, please let me know.
Thanks.
I'm getting frustrated with Virus's latest Eternity 3.0 ROM: "InfectedROM_Eternity-SynergyforCHAD-b1.zip"
First issue:
WiFi is often disconnecting and failing to reconnect. I try switching Airplane mode on and off and WiFi off and on and rebooting. Eventually it will reconnect but it's definitely not connecting as reliably as it did with r193.
Second issue:
Titanium Backup Pro 4.8.4 keeps locking up during batch restores. I've been trying to get all my apps restored last night and all day today and I keep having to FC Titanium and start again. I have also had the phone crash and reboot during a TB batch restore several times today.
Third issue:
Even when I'm connected to WiFi (at home and at work), I'm getting a lot of network timeouts. For example, I open "Google Play" and get the spinner for a while and then get "Connection timed out" [Retry]
Fourth issue (already mentioned):
Changing the overscroll color in Leedroid Tweaks cause the phone to crash and bootloop.
Also, the phone definitely "seems" less responsive and more laggy than it did on r193.
I do really like the blue themeing, however.
I did all the wiping I could with TWRP before flashing this ROM. I could try starting over again. Any other suggestions?
Fifth issue:
Power+Home native screenshots produce 0 B (empty) jpg files in /sdcard/DCIM. This was also the case with r193.
I was able to download a different root screenshot app from "Play Store" and got that to work instead. Still, it's annoying that the native screenshot functionality is broken.
What Hboot are you running? Sounds like a kernal issue to me. :/
djscience500 said:
What Hboot are you running? Sounds like a kernal issue to me. :/
Click to expand...
Click to collapse
HBOOT 1.40.1100
Which issue sounds like a kernel issue?