yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] Iskateforfree:
Hey everyone. I'm having a weird issue here. For some reason, whenever I have MULTIPLE texts, the pull down notification only displays the one LATEST text I got, instead of displaying the multiple texts. In order for me to view the multiple text, I have to go into the messaging app instead of seeing all text previews in the notification drop down panel...any suggestions?
[Verizon Samsung Galaxy S 4] JBeXX:
That is the normal behavior for aosp MMS. However if you choose the pop-up option you can scroll side to side to see multiple messages.
[Verizon Samsung Galaxy S 4] JBeXX:
[MENTION=2508408]jskala[/MENTION] you up for a test zip?? If so, what ROM are you running?
[Verizon Samsung Galaxy S 4] 2012crazymexican:
soo its this for vzw samsung s4?

just wanna really know if this its for samung s4 thanks n.n
[Verizon Samsung Galaxy S 4] Iskateforfree:
I can do a test for you if you'd like. I'm running Beans Build 6 with Faux 007u kernel.

---------- Post added at 11:36 PM ---------- Previous post was at 11:35 PM ----------

I can do a test for you if you want. I'm running Beans Build 6 with Faux 007u kernel.
[Verizon Samsung Galaxy S 4] JBeXX:
Nice, thanks. PM incoming in 5 minutes. Might wanna do a nandroid just in case.
[Verizon Samsung Galaxy S 4] Iskateforfree:
Perfect. Let me know when the PM is sent. I'll do a nandroid as soon as I download the zip. Do you have a change log?
[Verizon Samsung Galaxy S 4] JBeXX:
PM sent.

No change log, this is just a hopeful working dark version. I'm currently running an aosp rom so hoping testers like yourself can give me feedback
[Verizon Samsung Galaxy S 4] Iskateforfree:
Sounds good. Will this run on ME7 Beans Build 6? How long would you like me to test it out for? Full day?
[Verizon Samsung Galaxy S 4] JBeXX:
You should be able to send yourself a few test messages to know if it is working. The biggest thing I'll need to know is if when you send a picture message if the app forcecloses. If it does, you should still be fine to use this you'll just need to click "view" before sending the picture and then it will send properly when you back to the message.
[Verizon Samsung Galaxy S 4] Iskateforfree:
Okay sounds good. I'll make a nandroid and flash the zip. I'll give you an update in about 30 minutes.
[Verizon Samsung Galaxy S 4] JBeXX:
[MENTION=5303167]Iskateforfree[/MENTION] just PM'd you a restore zip in case you want to go back.
[Verizon Samsung Galaxy S 4] Iskateforfree:
Update: When using anything in the actual messaging app, there are force closes. This means selecting search, selecting a new message or selecting a previous conversation to view...all leads to force closes. Also, I was unable to receive any texts whatsoever.
[Verizon Samsung Galaxy S 4] JBeXX:
Damn, ok. Are you up for another one? Gonna PM another with hopefully better luck.
[Verizon Samsung Galaxy S 4] Iskateforfree:
Send it over my friend.

---------- Post added at 01:37 AM ---------- Previous post was at 01:12 AM ----------

So far so good. Only known issues right now is the MMS sending in which you have to press view before sending it and clicking your own contact picture within the message causes a force close...other than that it seems relatively stable. I will report back in the morning after using it for a couple of hours.
[Verizon Samsung Galaxy S 4] JBeXX:
Excellent! Thanks for the help!

I've reached out to CPA Poke who solved the mms issue on the mdk build to see if he can help us out with this as well. In the meantime, the workaround is pretty minor to get the sexy aosp mms back ;)
[Verizon Samsung Galaxy S 4] Iskateforfree:
No problem man. Thank YOU for the hard work and providing us with this new AOSP interface for messaging. Feel free to PM me anything you'd like tested that you're working on. I'm happy to help.
[Verizon Samsung Galaxy S 4] Iskateforfree:
Found another weird thing after I flashed the second zip file...after receiving a text, my lock screen shifts away from my default widget and adds a new lock screen for some reason. Heres what it looks like after receiving one text and answering the text (it stays like this until I reboot)

Here's what its supposed to look like no matter what.
[Verizon Samsung Galaxy S 4] JBeXX:
Yes, sorry forgot to tell you this step. Use a root explorer and go into system/app folder and rename the keyguardwidget.apk with.bak at the end or just delete it if you dont use the TW lockscreen clock
[Verizon Samsung Galaxy S 4] 2012crazymexican:
watha....

man this thing didnt work in my rom [hyperdrive rls 8]
[Verizon Samsung Galaxy S 4] JBeXX:
hyderdrive rls 8 is ME7 base. OP sates very clearly this will not work on ME7 and is for MDK
[Verizon Samsung Galaxy S 4] 2012crazymexican:
ooooooooooooooooooooo i see wasup thanks man so much thanks for ur answer love u !!! no gay mode lol no one really answers this days thanks
[Verizon Samsung Galaxy S 4] JBeXX:
Lol, no worries man! I am working on getting a working version for ME7. If you are interested I can PM you a zip to flash. If you flashed the zip in the OP you may need to reflash your rom before using the test zip tho. I got 4 hours left in my shift so let me know if you're up for it.
[Verizon Samsung Galaxy S 4] 2012crazymexican:
sure i jsut send u a message thanks !
[Verizon Samsung Galaxy S 4] Iskateforfree:
I just tried but it wouldn't let me delete the apk. And when I tried to rename is to keyguardwidget.apk.bak it would let me enter the .bak and hit okay but the name change wouldn't stick. I'm using ES File Explorer.
[Verizon Samsung Galaxy S 4] JBeXX:
before renaming or deleting, make sure ES has root permission and you mount the system first
[Verizon Samsung Galaxy S 4] JBeXX:
I'll try and get one posted up this weekend. If you don't want to wait you could probably snag an MMS.apk from a cm nightly and follow the steps in the op but instead of flashing, stick it in the system/app folder and set permissions to rw-r-r and reboot. Should get you the same results if you rename those files from my directions first.
[Verizon Samsung Galaxy S 4] revolt1:
I've tried that before and It didn't work it would force close
[Verizon Samsung Galaxy S 4] JBeXX:
OK, I'll find you one that works and let ya know. Weekend at the latest as I have a packed next few days but possibly sooner if I can.

And if anyone else has come across a working non-inverted version please feel free to use this thread to share your findings.
[Verizon Samsung Galaxy S 4] KillVolume:
Force closes every time for me whenever I touch my own contact picture in any conversation.
[Verizon Samsung Galaxy S 4] maddog00:
Will this work on stock rooted? Figured I'd ask before I take the plunge.
[Verizon Samsung Galaxy S 4] JBeXX:
Yes :)
[Verizon Samsung Galaxy S 4] JBeXX:
Yes, forgot to add that in the OP but that's a known bug for Aosp messaging on touchwiz. You checking yourself out lol?
[Verizon Samsung Galaxy S 4] suptt14:
Unchecked group messaging and was able to respond without a force close, just haven't got a response yet to determine whether or not they got it lol. But before whenever I even clicked to open a group message I would get a FC, so that's progress...

---------- Post added at 09:19 AM ---------- Previous post was at 09:15 AM ----------

So I am able to respond, and they get the message however it obviously created separate messages because they responded individually. Thats better than a FC thought for sure.
[Verizon Samsung Galaxy S 4] JBeXX:
[MENTION=4792286]suptt14[/MENTION] great! Thanks for the feedback! That might be the only workaround until someone who knows more than me is able to get it working right. On 4.1.2 it was possible so I'm sure we'll see that and proper mms hopefully sooner than later.

Thanks again!
[Verizon Samsung Galaxy S 4] maddog00:
Excellent! Second question. Do we need to flash the zip file? Or can we manually replace the files using root explorer (giving it appropriate permissions) then reboot?
[Verizon Samsung Galaxy S 4] JBeXX:
I can't say for sure but that method should work just fine as well. Just make sure to rename those 2 files first and set permissions for MMS.apk to rw-r-r. If you go that route please go ahead and post to let us know it is all good.
[Verizon Samsung Galaxy S 4] snagg641:
I would also really like to see a non inverted aosp mms app! Thanks for the hard work
[Verizon Samsung Galaxy S 4] JBeXX:
Alright [MENTION=2123571]revolt1[/MENTION] and [MENTION=2555524]snagg641[/MENTION]. Attached is a working and tested non-inverted version from a cm build. Use the exact same instructions as the OP but when you hit step 4, rename this file to just Mms.apk and stick it in system/app then change permissions to rw-r-r and reboot.
[Verizon Samsung Galaxy S 4] alixyz:
This is great thanks! Any chance you can do one with non blue reply text?
[Verizon Samsung Galaxy S 4] JBeXX:
I'll poke around and post if I find one
[Verizon Samsung Galaxy S 4] Badger50:
Nice job again buddy. Working like a charm :)

Sent fom my Mobile Beast Device :)
[Verizon Samsung Galaxy S 4] peppersu812:
I'm having issues sending mms over wifi now. Has this been an issue before and is there a fix?

Sent from far out galaxy!
[Verizon Samsung Galaxy S 4] JBeXX:
Odd. I just tested one over wifi and it worked fine. Did you select view before sending?
[Verizon Samsung Galaxy S 4] peppersu812:
Yea I did.
[Verizon Samsung Galaxy S 4] JBeXX:
Are you using the inverted or non-inverted version? It is working great for me with the original inverted version in the OP as long as I select to view before sending. I don't have the non-inverted loaded up at the moment to test but I had sent at least 2 pics earlier while running it and also sent fine(from home over wifi)

Anyone else having issues?
[Verizon Samsung Galaxy S 4] Iskateforfree:
I don't mean to sound like an idiot but can you explain to me how to do that? I believe it has root permission but it didn't ask me for root permission when I opened it. I also have no idea how to mount the system.
[Verizon Samsung Galaxy S 4] JBeXX:
No worries man. I'm not familiar with ES and I'm not sure where you grant root if it can also be used as a root explorer. Try using this app https://play.google.com/store/apps/details?id=com.jrummy.root.browserfree&hl=en . It's free and will mount automatically for you when you go to rename.
[Verizon Samsung Galaxy S 4] Iskateforfree:
Sweet deal man. I'll install and rename the apk and update you soon. Thanks for the help so far.

---------- Post added at 08:56 AM ---------- Previous post was at 08:42 AM ----------

UPDATE: The renaming of KeyguardWidget.apk to KeyguardWidget.apk.bak worked for the lockscreen issue. Everything seems to be stable. Only two known issues is the contact picture force close and the picture MMS in which you have to click view before sending. Other than those two small concerns, the AOSP Messaging is running great!
[Verizon Samsung Galaxy S 4] sbcrumb:
I am running hyper 8.1 and I can test pm me I will give you my email easier to get me.
[Verizon Samsung Galaxy S 4] JBeXX:
PM sent :)
[Verizon Samsung Galaxy S 4] JBeXX:
If anyone is around tonight who is on an ME7 based rom and can do some testing, I have a test zip ready to go with a themeable version that will hopefully be fully functional on ME7.

This will definitely require you to backup before flashing and will also delete you current messages when flashing so please back those up as well.

Any takers??
[Verizon Samsung Galaxy S 4] dachef3184:
I'll test
[Verizon Samsung Galaxy S 4] JBeXX:
PM sent :)

Thanks!
[Verizon Samsung Galaxy S 4] dachef3184:
Anytime thanks

Running beans 6. Just flashed and wiped caches. When I go to messages it force closes. It still shows the tw MMS icon in the top corner before it does force close though
[Verizon Samsung Galaxy S 4] JBeXX:
Hmmmm ok. Do me a favor if you can and look in the system/app folder and see if you have both mms.apk and secmms.apk. If you have both, try deleting secmms and make sure the permissions on mms.apk are rw-r-r. Then try rebooting and see if if works.
[Verizon Samsung Galaxy S 4] dachef3184:
Had both delete s secmms rebooted wiped caches now the new MMS shows but then closes right away

just flashed bone stock 1.4 it works besides the mms issue as before you have to hit view for it to send mms....

I think it didnt work before is I had flashed the black it out mod a few days ago and forgot that is using the old apks..
[Verizon Samsung Galaxy S 4] JBeXX:
OK thanks. I'm packaging a new zip to try shortly that CPApoke helped edit who is the one that fixed the MDK version. Up for another try? :)
[Verizon Samsung Galaxy S 4] dachef3184:
Definitely Ill be up for a while
[Verizon Samsung Galaxy S 4] JBeXX:
Alright [MENTION=2975244]dachef3184[/MENTION]

and anyone else willing to test from ME7 base ROM. Please give this a try and let me know some feedback. Please make sure you backup sms/mms before flashing and not a bad idea to do a nandroid. This hopefully fixes the MMS workaround,it is also the original themeable version from the OP.

EDIT

Removed for now
[Verizon Samsung Galaxy S 4] dachef3184:
Test 4 caused phone to constantly foreclose
[Verizon Samsung Galaxy S 4] JBeXX:
Damn, sorry!

Back to work. Thanks again for testing.
[Verizon Samsung Galaxy S 4] dachef3184:
No worries back ups are great Lol. Anytime
[Verizon Samsung Galaxy S 4] dnlgthr:
Willing to beta test

If you're looking for more testers I'm on a VZW Galaxy S4 running Hyperdrive RLS8.1. I really appreciate the work you put into this. When I had it running on a pre-ME7 ROM it was flawless. Looking forward to an updated apk!
[Verizon Samsung Galaxy S 4] JBeXX:
I will be needing some testers tonight. If you're up I'll PM you. It won't be until after 8 mountain time.

Thanks!
[Verizon Samsung Galaxy S 4] JBeXX:
Alrighty. Anyone up for a new test zip of themeable me7?
[Verizon Samsung Galaxy S 4] roboots21:
What would we need to do to try this? Just replace/rename some apks? Last time I tried a themed SMS my phone wouldn't boot lol.
[Verizon Samsung Galaxy S 4] JBeXX:
It's a flashable zip file. Just backup your current rom and sms/mms if you want to test. Let me know and I'll send you a link.
[Verizon Samsung Galaxy S 4] roboots21:
I'm on stock ME7, so no backing up current ROM haha. I can backup SMS/MMS .. I am debating on trying this as there is things I like about touchwiz MMS but things I don't .. and the 88sms in the OP wouldnt do MMS.
[Verizon Samsung Galaxy S 4] JBeXX:
Gotcha. Unfortunately this may not do you any good while you are stuck on stock. This is still in testing so without being able to backup I wouldn't recommend testing.

When did you last try 88sms out? I think they may have fixed MMS
[Verizon Samsung Galaxy S 4] roboots21:
A couple of days ago. Prolly Saturday? I couldn't send or receive MMS but SMS worked just fine. The other thing is stock MMS still vibrates in blocking mode whereas 88sms does not .. Those were my only two gripes. .
[Verizon Samsung Galaxy S 4] JBeXX:
Sweet thanks! Give me about 15 minutes or so. I'm testing one now and if it doesn't work out I won't bother sending it over.
[Verizon Samsung Galaxy S 4] dachef3184:
No prob. Sounds good
[Verizon Samsung Galaxy S 4] JBeXX:
VICTORY!!(I think)

Anyone else that wants to test. I have a themeable(same version as OP MDK) working on Beans 6 with no MMS workaround needed.

Here is the link. I'm holding off updating the OP until a get a couple other successful testers. Who's with me???

edit
[Verizon Samsung Galaxy S 4] justda:
Im on it. DL not will report asap

---------- Post added at 08:39 PM ---------- Previous post was at 08:24 PM ----------

Opens, stalls, closea back to main screen.

I deleted secmms.apk restarted after cache wipe no change.
[Verizon Samsung Galaxy S 4] JBeXX:
Hmmm. What ROM are you on? Did you have any other sms mods or 3rd party apps installed?

I have it working flawless, but flashed during a fresh install of Beans 6.

And this zip will replace the SecMms.apk so you'll want to keep that intact.
[Verizon Samsung Galaxy S 4] justda:
Hyperdrive 8.1 fresh install, xposed mods, and aosp browser
[Verizon Samsung Galaxy S 4] JBeXX:
OK, thanks. I'm gonna try and round up a few more Hyper testers and see if they get the same results. Hyper and Beans are both similar ME7 deodex bases so I'm not sure why it would work with Beans and not Hyper. But I also don't know alot of things lol ;)

Thanks again for testing
[Verizon Samsung Galaxy S 4] JBeXX:
PM sent
[Verizon Samsung Galaxy S 4] justda:
Could it be the Xposed framework, or the mods attached to it?

I haven't tried it without the framework installed.
[Verizon Samsung Galaxy S 4] JBeXX:
It could yes. Xposed might buttheads with the framework edits. I know it's a lot to ask but if you have time to try a clean install of hyper and flash this right after the ROM install.
[Verizon Samsung Galaxy S 4] JBeXX:
That is for MDK bases roms only. Most roms are now updated to the ME7 base. The one from the OP will not work with ME7.
[Verizon Samsung Galaxy S 4] JBeXX:
Are you running xposed framework by any chance?
[Verizon Samsung Galaxy S 4] JBeXX:
OK thanks for the test. I have it flashed and working fine on Beans right now so I'm trying to find the culprit for the FCs.

Did you happen to do a nandroid? If so, would you be willing to try flashing this after a clean install of Beans? I understand if now as I know that is more time consuming.

Also, you did flash the test7me7mms.zip correct? Not the zip from the OP?
[Verizon Samsung Galaxy S 4] JBeXX:
as long as it was the zip named tes7me7mms.zip. I posted it a page or so back and is also the one I sent you in PM.

LOL, and thanks. Love those nandroids ;)
[Verizon Samsung Galaxy S 4] JBeXX:
Boom. Think I got it. This should finally fix ya up and be fully functional on Beans.
[MENTION=4713243]justda[/MENTION] this should work for you as well.

https://www.dropbox.com/s/hth9ksapaw1iqzg/test9me7mms.zip
[Verizon Samsung Galaxy S 4] justda:
3x wiped Fresh flash, no mods, no add ons through aroma, stock kernel. Same deal it opens, hangs, black screen, back to previous screen.

Tell me what to do. Any type of loggin program that might give a little more detail as to it failing?

Can anyone confirm this working on HD 8.0+? I have seen it work in Eclipse, and JBexx says it works with Beans...
[Verizon Samsung Galaxy S 4] JBeXX:
Flash the test9 zip I just linked. You should be good to go after that.
[Verizon Samsung Galaxy S 4] JBeXX:
Excellent. Thanks for testing! This should be fully functional aside from the cross the board issues such as click on your own contact and getting FC and funky behavior from iphone group messages.
[Verizon Samsung Galaxy S 4] justda:
messages sent, received, changed backgrounds, changed bubbles and colors.. so far so good!

I will update tomorrow after my friends are actually awake and not just telling me to f*ck off for texting them so late.

Thanks JBeXX, I hated using the stock TW MMS, and the 88 one had its own issues. I have never had an issue with this MMS, so again thank you for putting in the time to get this working for us HD 8.1 guys.
[Verizon Samsung Galaxy S 4] JBeXX:
Glad you are up and running!

Thanks again for being a guinea pig :)
[Verizon Samsung Galaxy S 4] JBeXX:
OP Updated with working ME7 zip

Thanks to all testers for helping work out the kinks on getting this going for ME7 bases!!!

Also, thanks again to [MENTION=4913579]CPA Poke[/MENTION] for providing the edits to framework.jar to get this going on ME7.

OP is updated with a working zip file for ME7 deodex bases.
[Verizon Samsung Galaxy S 4] roboots21:
Do you think this may be worth a shot trying out on stock ME7? I'd be willing to try it even though the possibility of a soft brick (thank god for Odin). What are your thoughts?
[Verizon Samsung Galaxy S 4] JBeXX:
Because you're stuck on odex, this would require the MMS workaround either way. So if you are prepared for that.

Take the Mms.apk from the zip, stick it in system/app folder, set permissions to rw-r-r.

Then rename the SecMms.apk file from the same folder and rename to SecMms.apk.bak.

Then rename the keyguardwidget.apk also with .bak at the end.

Reboot and see where you're at.

If it works and doesn't FC. Just make sure you select "view" on a picture before sending.

I'm off to bed after an a night work shift but it doesn't work. Just remove the Mms.apk and rename the other 2 without bak and reboot to get back to stock.
[Verizon Samsung Galaxy S 4] alphanu22:
anyone running ME7 on Hyperdrive RLS8.1?
[Verizon Samsung Galaxy S 4] jettadieselguy:
I'm in Hyperdrive 8.1
[Verizon Samsung Galaxy S 4] dachef3184:
Works great thanks
[Verizon Samsung Galaxy S 4] alphanu22:
any MMS probs?
[Verizon Samsung Galaxy S 4] jettadieselguy:
Just flashed. I'll test it for a bit and let you know.

---------- Post added at 01:03 PM ---------- Previous post was at 12:55 PM ----------

Sent messages and mms with no issues so far. Appears to be working great at this point. So much better that stock messaging for me.
[Verizon Samsung Galaxy S 4] roboots21:
Going to try this in a few. So I do not need to push either the SecTelephonyProvider nor the framework2.jar to my system?
[Verizon Samsung Galaxy S 4] dnlgthr:
No issues on ME7 so far

Thanks for the ME7 version! Flashed it earlier this afternoon. So far so good.
[Verizon Samsung Galaxy S 4] JBeXX:
No, I'd stay away from those. Even if they swapped out with issue you'd almost definitely still need to do the MMS workaround. You should get those same results and a safe way back trying just Mms.apk
[Verizon Samsung Galaxy S 4] JBeXX:
Nope. Just the issues mentioned in the OP with wonky results from iPhone group messaging.
[Verizon Samsung Galaxy S 4] alphanu22:
Flashed via CWR Touch

-ME7

-Hyperdrive

-3minit

everything running like normal-
[Verizon Samsung Galaxy S 4] Badger50:
Well done JbeXX. Working like a charm on Beans 6. Thanks buddy :D

Sent fom my Mobile Beast Device :)
[Verizon Samsung Galaxy S 4] JBeXX:
Thanks Badger! Haven't run into you in a while. Hope a is well my friend!
[Verizon Samsung Galaxy S 4] Badger50:
You know how life is bro...been busy as all get out. Glad to finally see you and Polk got this baby working on me7. She's Saweeeeeeeeet to say the least :D

Sent fom my Mobile Beast Device :)
[Verizon Samsung Galaxy S 4] justda:
Running since midnight last night.

40+ text sent and received, sent out mass text, and sent and received pictures. All working flawlessly

Well done good sir, well done!
[Verizon Samsung Galaxy S 4] roboots21:
So pushed this to system on stock rooted ME7, and it worked! I have to do the MMS workaround, but everything else worked like a charm! Thanks!
[Verizon Samsung Galaxy S 4] wesley404:
Thanks for the hard work getting this up and running on all the ROMs. I have been reading back through the pages of the thread and just wanted to make sure that I didn't miss something, the FC's when trying to look at contacts is a known issue on the ME7, but is it due to the KeyGuardWidget.apk or something else I haven't done?

I'm running Beans 6, I've removed KeyGuard from the system folder and I do have Xposed installed and running.
[Verizon Samsung Galaxy S 4] JBeXX:
Nice! And it really is only a 2 second workaround so not too shabby.

Also, if your lockscreen defaults to the small clock. Go into system/app folder and renam keyguardwidget.apk with .bak and that will fix you up.
[Verizon Samsung Galaxy S 4] JBeXX:
You should only get FCs when clicking on your own contact pic from within the app. And that is a known issue pretty much 4.1 and up with aosp mms for some reason. Clicking others with the newest version should be all good.
[Verizon Samsung Galaxy S 4] wesley404:
Okay, I will delete the one I have now and re-download the ME7 and try again. Thanks.
[Verizon Samsung Galaxy S 4] JBeXX:
No problem.

All good now?