The problem: All JB built AOSP/CM mms.apk files do not work with TW ROMS.
Observations: Most work fine, but crash on sending or receiving an MMS message. ICS built mms.apks do work, but since ICS doesn't have Quick Reply or MMS preview built in, it's a step behind.
Bounty requirements: Working JB (preferred 4.2 as it has Group Messaging built in) that doesn't crash on MMS sending or receiving. Also, Emoji support, Full timestamp support, soft keyboard type, and SMS to MMS converter. If you patch mms.apk directly via source, a changelog or link commit back to CM/Gerrit is required. An explanation of what was missing/changed if no direct code was patched.
Method of payment: All parties who join into the bounty will be solely responsible for payment, which are to be arranged between the two parties.
I will start by offering $5. If you would like to contribute to get this working, please post and I'll keep a running list and keep the thread updated with the current amount.
Update: Adrynalyne, of Team BAMF, was kind enough to lend a hand and provided a fix, which he details in this thread. Attached is the fix.
#Notes# The fix SOMETIMES hangs while sending an MMS issue. I've been able to reproduce, but never when I can capture a logcat of it. If you know how to enter/use logcat, and you want to help refine the fix even more, by all means, post in here or PM me. I actually don't think it has to do with the fix, but the mms.apk itself. But again, we need people who can post logcats to narrow it down.
This fix SHOULD work on ANY unmodified, deodexed framework.jar based on the VRBLK1 leak. If you don't know what this is, ASK your dev if they've modified the framework.jar. If your phone blows up, YOYO, you're on your own. As always, its a good idea to make a nandroid backup, just to be safe.
Update: Adrynalyne hammered out a working fix for BLK3, which I posted below. I tested it on Beans Build 8. Works like a charm
More importantly, please consider donating to adrynalyne here. He did this out of kindness, as a favor to me. He doesn't even own the phone, I had to test and send files and logcats to him. Any little bit helps, and I think it's awesome he helps out with a device his team does not directly support, and hope more devs in the future will help each other in this manner. Thanks.
I've never had a problem sending mms with AOSp roms, i've used AOKP, cm10 and now miui, no problems
CovXX said:
I've never had a problem sending mms with AOSp roms, i've used AOKP, cm10 and now miui, no problems
Click to expand...
Click to collapse
He isn't talking about aosp Roms.
CovXX said:
I've never had a problem sending mms with AOSp roms, i've used AOKP, cm10 and now miui, no problems
Click to expand...
Click to collapse
Read the first sentence. The problem is that the AOSP/CM mms.apks do not work on TOUCHWIZ BASED ROMs.
I'm using an Aosp messaging apk on clean rom. No problems sending mms or anything. Am I reading it wrong?
Sent from my SCH-I535 using xda premium
He is talking about getting the aosp/cm10 mms with quick reply to work on tw roms. The picture below is an example of what he is talking about.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The devs got the quick reply working so far but the app fc when viewing, sending or receiving a picture message.
also when you tap a thread with a MMS the app force closes
RCOVA said:
also when you tap a thread with a MMS the app force closes
Click to expand...
Click to collapse
We are almost there.
MMS force closes: fixed
MMS sending and receiving: mostly fixed. Possibly a signal issue as it sends OK at some times and not others. It receives fine.
adrynalyne said:
We are almost there.
MMS force closes: fixed
MMS sending and receiving: mostly fixed. Possibly a signal issue as it sends OK at some times and not others. It receives fine.
Click to expand...
Click to collapse
Damn...This is awesome. I cant wait!
You won't get the aosp group messaging because it requires framework tweaks
Sent from d2_vzw
con247 said:
You won't get the aosp group messaging because it requires framework tweaks
Sent from d2_vzw
Click to expand...
Click to collapse
That doesn't mean it can't be done. Can't never did nothin'. I'm starting with 4.1.x compatibility first.
As it stands, almost all my work so far to get AOSP MMS working has been framework code. I am going to post it here shortly so that I can get some more test results.
Edit: attached.
A couple things to note: Only send MMS through the app itself. In other words, don't try to send something from the gallery as MMS. Instead, open the MMS app and attach a file. I'll work on that limitation later.
This has worked for mexiken, both for receiving and sending, however sending becomes spotty. So let me know how it turns out. I do not know that this is the final fix and it may need some more work. I ran out of time due to Thanksgiving and family responsibilities. Once it fully works, I will be more than happy to share how I did it with everyone. Also, I modded the framework from his rom, so you might want to make a nandroid first, in case your JB TW rom isn't compatible. This is a test, and if your phone blows up, I hold no responsibility for it. I do not own this phone, so I cannot test it.
This package contains framework and a JB MMS app.
We've got it working on my phone, but I really don't know if it's my signal issues or what. I'm playing around with a few different combinations of files.
I will test further later tonight if I get out of the house. Worst case, I'll check tomorrow at work.
adrynalyne said:
That doesn't mean it can't be done. Can't never did nothin'. I'm starting with 4.1.x compatibility first.
As it stands, almost all my work so far to get AOSP MMS working has been framework code. I am going to post it here shortly so that I can get some more test results.
Edit: attached.
A couple things to note: Only send MMS through the app itself. In other words, don't try to send something from the gallery as MMS. Instead, open the MMS app and attach a file. I'll work on that limitation later.
This has worked for mexiken, both for receiving and sending, however sending becomes spotty. So let me know how it turns out. I do not know that this is the final fix and it may need some more work. I ran out of time due to Thanksgiving and family responsibilities. Once it fully works, I will be more than happy to share how I did it with everyone. Also, I modded the framework from his rom, so you might want to make a nandroid first, in case your JB TW rom isn't compatible. This is a test, and if your phone blows up, I hold no responsibility for it. I do not own this phone, so I cannot test it.
This package contains framework and a JB MMS app.
Click to expand...
Click to collapse
I'm not super familiar with how the framework works, so I figured I better ask before flashing this. I have a T-Mobile GS3 running a JB TW rom. Is the framework carrier or rom specific, meaning it would cause issues for me?
trickinit said:
I'm not super familiar with how the framework works, so I figured I better ask before flashing this. I have a T-Mobile GS3 running a JB TW rom. Is the framework carrier or rom specific, meaning it would cause issues for me?
Click to expand...
Click to collapse
I am going to assume so, yes. Once we verify it fully works, I can make versions for any version of phone...or post how it was done so others can (doesn't matter to me, I am doing this for free because mexiken is a good friend of mine).
Hello all!
Has anyone tried this on a VZW S3 yet? I'm running jelly beans stock rom with Nova launcher and I'm not feeling brave enough to try the fix just yet.
Sent from my SCH-I535 using xda app-developers app
Stre7ch said:
Hello all!
Has anyone tried this on a VZW S3 yet? I'm running jelly beans stock rom with Nova launcher and I'm not feeling brave enough to try the fix just yet.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I have the VZW S3 and can confirm it works in that it doesn't crash anymore, but it doesn't send reliably.
mexiken said:
I have the VZW S3 and can confirm it works in that it doesn't crash anymore, but it doesn't send reliably.
Click to expand...
Click to collapse
Good to hear, but what do you mean? Is it just MMS that won't send reliably or texts in general? What about receiving texts and MMS? Also, I know I'm a super noob, but how can I help with develop this?
Sent from my SCH-I535 using xda app-developers app
adrynalyne said:
That doesn't mean it can't be done. Can't never did nothin'. I'm starting with 4.1.x compatibility first.
As it stands, almost all my work so far to get AOSP MMS working has been framework code. I am going to post it here shortly so that I can get some more test results.
Edit: attached.
A couple things to note: Only send MMS through the app itself. In other words, don't try to send something from the gallery as MMS. Instead, open the MMS app and attach a file. I'll work on that limitation later.
This has worked for mexiken, both for receiving and sending, however sending becomes spotty. So let me know how it turns out. I do not know that this is the final fix and it may need some more work. I ran out of time due to Thanksgiving and family responsibilities. Once it fully works, I will be more than happy to share how I did it with everyone. Also, I modded the framework from his rom, so you might want to make a nandroid first, in case your JB TW rom isn't compatible. This is a test, and if your phone blows up, I hold no responsibility for it. I do not own this phone, so I cannot test it.
This package contains framework and a JB MMS app.
Click to expand...
Click to collapse
Thanks for your hard work! :victory:
Stre7ch said:
Good to hear, but what do you mean? Is it just MMS that won't send reliably or texts in general? What about receiving texts and MMS? Also, I know I'm a super noob, but how can I help with develop this?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Can you test it? Make a nandroid first. Verizon is having some MMS issues as well, which *may* attribute to this. I sent an MMS to my wife on a different phone today and it took a while for her to get it.
What I really need is a full logcat of when sending fails so I can figure out where its getting stuck. I believe mexiken told me he has about a 66% successful send rate.
Receiving always works AFAIK.
Try sending while on, and off WiFi.
Would love to help, unfortunately this does not seem to work on Synergy 118. tried with complete wipe as well as clearing Cache and Dalvik, still no dice. This looks like a great mod though.
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
MIUI 1.3.5
brought to you by ahmgsk, fusingblackrose, asdfghjkl, Mike_77, darkierawr,
and the latest by deano0714...
So now to get started:
MIUI 1.8.19
All Credit goes to Deano0714 for getting it to boot and working on it!!
Working:
-It boots...
-Wifi (only with static IP)
NOT working:
-Everything else...
-SD card (fix may be on the way)
MIUI 1.3.5
Things NOT working:
1. Bluetooth
2. Auto rotation
3. Screen wake lag receiving call
4. MMS (recompiling apk soon. aka maybe fixed)
5. front facing cam (who uses this?)
6. camcorder
7. EXTREME lag when using MIUI music...(fixed by downloading MIUI music)
Important things working:
1. SMS
2. 3G
3. Theme manager (important to me lol)
4. Everything else??
Chopped Up MIUI
It has the first kernel ahmgsk had in rom and was supposed to fix things.
Before flashing:
1. PLEASE remember to wipe everything...
2. If ext4 flash either MIUI or Chopped up.
3. If RFS flash MIUI only. Il upload separate dual kernel later.
I assume by now you all know how to convert to EXT4...if not then just root with CWM 3.0.0.6 and boot into recovery. It will then convert you and you HAVE to flash an EXT4 rom before reboot..
DOWNLOADS:
1.8.19 crespo4g port: http://db.tt/AdPyiM8*** CLICK HERE ***[/URL]
CREDIT goes to deano0714 for getting it to boot and fixing issues!!
MIUI.zip : *** CLICK HERE ***
Chopped Up MIUI.zip : *** CLICK HERE ***
Original EXT4 kernel : *** CLICK HERE ***
Working MIUI Music : *** CLICK HERE ***
This is not my fix..credit to micahrodriguez7 for posting this. And lightninbug and mad-murdock....
Well guys thats all for now.
PLEASE report any unknown bugs you find.
Huge thanks to all testers at MIUI-DEV and here at XDA !!!
And to ahmgsk for helping whenever he can!! He is a great DEV!
reserved...for what? who knows, but everyone does it. lol
Oh i know..il post some pics!
Yay first after poster for once
Sent from my SPH-D700 using XDA Premium App
Found an SMS bug. anytime i try and send a message even 1 character past the limit for one message, the person receives nothing but a bunch of symbols. so you'd have to send the message everytime you get to the limit of one message in order to send a long message
Edit: Sorry Running Chopped up Miui
big_slug06 said:
Found an SMS bug. anytime i try and send a message even 1 character past the limit for one message, the person receives nothing but a bunch of symbols. so you'd have to send the message everytime you get to the limit of one message in order to send a long message
Click to expand...
Click to collapse
Lol thats an AOSP thing if im not mistaken..i think the solution is download another text app that has "auto separate" in settings...i think handcent works...maybe go!sms lol
nixo31 said:
Lol thats an AOSP thing if im not mistaken..i think the solution is download another text app that has "auto separate" in settings...i think handcent works...maybe go!sms lol
Click to expand...
Click to collapse
ok, kool. i love go sms you have any idea how to fix the bluetooth in chopped up? thas all i need for everyday use. i need it for my workout music ...still running it now since i skipped my workout today tho lol
big_slug06 said:
ok, kool. i love go sms you have any idea how to fix the bluetooth in chopped up? thas all i need for everyday use. i need it for my workout music ...still running it now since i skipped my workout today tho lol
Click to expand...
Click to collapse
lmao i skipped it too...for about a month xD and i think the problem is in the initramfs..so its in the kernel and i dont know much about that yet :/ i wonder if the bonsai kernel or ACS kernel fixes it? im sure it probably breaks something else lol
nixo31 said:
lmao i skipped it too...for about a month xD and i think the problem is in the initramfs..so its in the kernel and i dont know much about that yet :/ i wonder if the bonsai kernel or ACS kernel fixes it? im sure it probably breaks something else lol
Click to expand...
Click to collapse
haha, probably. well, i'll probably run this one through tomorrow unless u post another one you want tested. i keep my eyes peeled for any more bugs, but its looking doubtful so tho. great work
Very nice, glad to see and updated thread for this. No offense to ahmgsk, I know he's real busy with other development.... oh and life lol.
Sent from my SPH-D700 using XDA Premium App
So happy to see continued MIUI development. I'll have to flash this over once it's a bit more fleshed out
nixo31 said:
Is the theme manager working?? It should flash theme and reboot into same theme not new one.
EDIT: NEW thread is open!! All updates will be posted here..
Click to expand...
Click to collapse
theme manager is working on the twilight kernel like the rest.
it works, but sometimes when im changing my lockscreen it'll (theme manager) will force close on me but it does that on other kernels too
3g is still a little iffy with this kernel (twilight)
okay upon further testing.....
it seems that ALOT of kernels are working with MIUI
some are EXTRA buttery my gawd how they are snappy it seems.
Imo, Twilight seems like one of the fastest however a few things are broken and are missing from the initramfs (i.e. bluetooth) However wifi modules and the like are obviously included in the initramfs because it tethers.....
3g just isnt so great
back with more
good news/bad news
[KERNEL][CM7] Phoenix v0.01 || Updated: 04/09/2011 - 11:45
^^flashes. Bluetooth turns on and all. However, virtually impossible to use. it needs some tightening up or reworking period. hella static!!!!!!
3g works
wifi tether is borked (missing things in the initramfs)
edit: this kernel borks wifi.... booooooooooooooo
twilight kernel fixes the lag when music player is running/on
however, 3g is hella inconsistant.... i flash this kernel before and 3g was working.....now it doesnt wanna work
HELLA iffy
Hello asdfghjkl.
I didn't know we had that many problems!
I guess fusingblackrose underplayed the whole deal
big_slug06 said:
Found an SMS bug. anytime i try and send a message even 1 character past the limit for one message, the person receives nothing but a bunch of symbols. so you'd have to send the message everytime you get to the limit of one message in order to send a long message
Edit: Sorry Running Chopped up Miui
Click to expand...
Click to collapse
nixo31 said:
Lol thats an AOSP thing if im not mistaken..i think the solution is download another text app that has "auto separate" in settings...i think handcent works...maybe go!sms lol
Click to expand...
Click to collapse
big_slug06 said:
ok, kool. i love go sms you have any idea how to fix the bluetooth in chopped up? thas all i need for everyday use. i need it for my workout music ...still running it now since i skipped my workout today tho lol
Click to expand...
Click to collapse
Yup, it is an AOSP thing. Use something like handcent to split the messages
isnt it also relative to our cdma networks as oppose to gsm networks?
DOHH got soo excited thought devs were being sneaky with this one and just release something stable, but this is progress! keep it up!
It has to do with both, combination of AOSP and CDMA network. Dunno why since CDMA support was added in Android 1.6 (shoehorned into 1.5 by HTC for the Hero and by Samsung for the Moment).
I would suggest the mods to keep the thread clean and allow only the testers and the other people related to the ROM post here.
PS: No offence meant to other members.
I'm not referring to the groupMe app, because they'd also have to install that.
I've tried Go SMS, pansi SMS, chomp SMS, and they don't seem to do it perfectly.
When I receive a group text from an iphone user, I want it to make a new thread with all members of the group text, where I can seamlessly respond to all users. Moreover, the stock app does this in a way that my response is not received as a group text on their end, but simply a message to them (as well as whoever else was in the group). Thus, the response goes into our 1v1 chat thread.
All I want is a plugin, rom, app, anything that solves this ridiculously frustrating issue.
I'd like to know as well. I have not been able to find an easy way to do it. I'm guessing it's Apple hating on us Android folks.
GoSMS does it very well, subject to a few limitations, not sure why it is not working for you. A couple of things to keep in mind.
1) The proper threading is not native but is run after the fact. This requires that the message be fully downloaded before it is properly threaded. This can take 10-15 seconds, if you open the message during that time it will not thread correctly.
2) Unfortunately the app will notify you twice, once the original message is received, and once it is recategorized. I handle this by shutting of sound and vibration in the app and using Tasker instead. If two notifications arrive within 15 secs Tasker just ignores the second one.
From what I have been told Handcent will do something similar
The GoSMS / Handcent implementations are ****. Sorry, but they are.
I've heard tell that Android finally put native group SMS / MMS into Android 4.2, which will likely never come to our phone officially but hopefully we'll get some of the benefit at least as things trickle down in the development community.
I'm also trying to find a solution to this too and I'm always hoping that every update of Go Sms and Handcent fixes this feature. Like one of the previous replies above stated, GO SMS will give you double notifications. It's annoying because it slows down your phone if you get too many all at once.
I've found that Handcent works better than GO SMS because it only notifies you after the message has been downloaded and you don't get double notifications. However, it's still flawed because sometimes your messages hang and dont download properly unless you physically click download. Also, sometimes when you're sending a text and try to hit send, it looks like it sends but just disappears. If you wrote a long message, you would have to re-type it all over again and hope it sends correctly the second time.
If you install CM 10.1 (android 4.2.2), this group messaging feature is baked into the rom. This is probably the best experience I've had to get the group messaging to work. It works like how an iphone user would see it. However, CM 10.1 still has some minor glitches that made me temporarily go back to sense roms. With every nightly, things seem to be getting better though. I will probably try it again in a couple weeks.
Currently I'm back on Viper using Handcent.
Have you tried side loading the MMS apk from 4.2?
Sent from my HTC One X using xda app-developers app
ChrisPBacon said:
Have you tried side loading the MMS apk from 4.2?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
+1 messaging from 4.2 works great
RollTribe said:
+1 messaging from 4.2 works great
Click to expand...
Click to collapse
Nice. Where did you guys get it from?
RollTribe said:
+1 messaging from 4.2 works great
Click to expand...
Click to collapse
Really? Doesn't seem to be working for me. I'm running aokp 4.2.2. Is there something else I must do? I see group messages are checked in the settings already
Sent from my One X using xda app-developers app
Yeah 4.2.x does this. Try it out
Sent from my One X using xda app-developers app
Guys, where can I find this APK?
can someone dropbox the newest apk?
So i tried installing this:
https://www.dropbox.com/s/oisv83ye8yv75lj/Mms.apk
I'm on ViperXL right now. I downloaded that MMS.apk to my phone and just tried running it, and the install process came up. Clicked yes through it but the app just force closes.
Am I doing something wrong here?
qozon said:
So i tried installing this:
https://www.dropbox.com/s/oisv83ye8yv75lj/Mms.apk
I'm on ViperXL right now. I downloaded that MMS.apk to my phone and just tried running it, and the install process came up. Clicked yes through it but the app just force closes.
Am I doing something wrong here?
Click to expand...
Click to collapse
I've been told before that SMS apps for stock Android won't work on Sense ROMs and vice-versa. No idea why or if that's really true.
qozon said:
So i tried installing this:
https://www.dropbox.com/s/oisv83ye8yv75lj/Mms.apk
I'm on ViperXL right now. I downloaded that MMS.apk to my phone and just tried running it, and the install process came up. Clicked yes through it but the app just force closes.
Am I doing something wrong here?
Click to expand...
Click to collapse
I've successfully run a CM10.1 mms.apk in CM10, but I've never tried this with Sense. Do you know what ROM that mms.apk file you have is actually from? I know CM10.1's mms.apk is compiled to require a minimum of JB 4.1, but versions from other JB 4.2 ROMs might have possibly been compiled to require JB 4.2
FWIW: mms.apk file is normally located in the /system/app folder, which requires root permissions to move a file to. File permissions might also need to be modified. Sense doesn't normally has a mms.apk in there since the stock messaging app is built around Sense and I believe the name starts with "htc", but I would assume a new mms.apk would at least run. I'm not sure whether this file location and permissions are actually part of your problem
update -
I've tried the entire process of putting the app in system, setting permissions, and installing, rebooting etc. No avail. App still force closes as soon as it opens.
I think the problem is in fact something to do with sense. I deleted the old messaging app as well first but that didn't do anything either.
Damn.
4.2.2 MMS force closes on viper 4.1
I uninstalled all the htc language packs, htc messaging. Install mms.apk.
I can get the app open, change settings, type a message... But as soon as I add a recipient it force closes.
Since I can do the things I can with the app open seems as though it should be able to work
If there is anyone that wants to work on this? I don't want to bug Turge with it.
Which mms.apk did you install?
Sent from my Evita
The one you uploaded in viperxl forum.
Sent from my HTC One XL using Tapatalk 4
rogcaw82 said:
The one you uploaded in viperxl forum.
Sent from my HTC One XL using Tapatalk 4
Click to expand...
Click to collapse
That is an mms.apk from an aosp ROM, I didn't mention that when I uploaded it. It won't work properly on a Sense ROM.
Sent from my Evita
EDIT: Download 8sms from Google Play or download from the website.
EDIT: 8sms now based on Android 4.4 KitKat / Cyanogenmod 10.2. See post #394.
EDIT: App renamed from 88sms to 8sms. See post #246.
Hi,
This is my first android app and my first app announcement on XDA so apologies in advance if I've broken any rules.
I've ported the stock messaging app and then added some enhancements and changes so it can (hopefully) work on any Jelly Bean phone. This app is downstream from the latest Android 4.3 and CyanogenMod 10.2 (not-yet-released as of writing).
(ICS compatibility is a possible future feature.)
Please have a look if interested and feel free to try it out.
The Play Store link is:
https://play.google.com/store/apps/details?id=com.thinkleft.eightyeightsms.mms
Excerpts from the app description follows ...
Notable features
Notification pop-ups
Quick reply
Gesture based templates
Emoji support
Optional dark theme
Install this app if you want to use features from the latest Android messaging app without having to wait for a full phone software update.
Usage
Whilst 88sms is a replacement for the messaging app that came with your phone, it is actually an add-on application only.
Please do not disable or remove the messaging app that came with your phone as that is still required to receive sms and mms messages.
88sms works best if you turn off notifications for the messaging app that came with your phone. Then you won't get two sets of notifications.
Phone compatibility
This app may not work (yet) on the Samsung Galaxy S3 and Galaxy Tab 2 7.0. If you install this app on one of these devices, please let us know if it works.
If you install this app on your phone and it does not work, please let us know. Please be sure to specify your phone model and software version number, and the version of 88sms you have installed.
Permissions
This app requires a wide range of permissions because it is a port of a system app. System apps use a lot of permissions. Full network access is required in order to send (or download) mms using your phone's cellular data (mms) connection.
Thank you.
Works great. Left my rating on the play store.
Sent from my HTC One
didn't work on LG LTE2
spitfire2425 said:
Works great. Left my rating on the play store.
Sent from my HTC One
Click to expand...
Click to collapse
it doesn't work on my LG LTE2,stock rom
Do you mind if I pm you to find out more and try to fix it?
thophan said:
it doesn't work on my LG LTE2,stock rom
Click to expand...
Click to collapse
@thophan: Hi, thanks for trying out the app. Do you mind if I pm you to find out more and try to fix it? (Although I might not get any free time until a week later.)
didn't work
bengtan said:
@thophan: Hi, thanks for trying out the app. Do you mind if I pm you to find out more and try to fix it? (Although I might not get any free time until a week later.)
Click to expand...
Click to collapse
Sure, really appreciate it. after install, i open it, but one dialog box appear (it said: sorry...._ i can't remember) then escape the program. i tried several time, same thing. so i uninstall your software.
Works great on note 1
mms isn't working it just keeps trying to send and never sends. The stock messaging app works fine. I am using a Note 2 on att with a rooted stock rom
Yea group messaging doesn't work since the MMS problem. It just stays sending and won't go through.
Sent from my SGH-M919 using xda premium
On Sprint GS4.... MMS doesn't send on this app :/ but when I go to my stock messaging app it sends and I receive it from both apps, just a little workaround to an otherwise amazing app. Love the look and feel like AOSP! Some custom theming options would be great!
Great app, I already love it...
A nice feature that I would like to see is the ability to set the number of line for tying SMS... Because 3 lines is not enough for long SMS typer like me ^^
Sent from my Evo 3D GSM using xda app-developers app
I will follow up and try to fix the bugs. Unfortunately, I've gone travelling ...
Hi,
Thanks to everyone of you for trying it out and thanks for the encouragement and feedback!
I acknowledge there may be a few problems on some devices ... it is my first app, after all, and it's not like I have a lot of different phones to test it on
I will follow up and try to fix the bugs. Unfortunately, I've gone travelling for a week so I might not be able to do much until a week later.
But I will follow up.
Thank you all!
bengtan said:
Hi,
Thanks to everyone of you for trying it out and thanks for the encouragement and feedback!
I acknowledge there may be a few problems on some devices ... it is my first app, after all, and it's not like I have a lot of different phones to test it on
I will follow up and try to fix the bugs. Unfortunately, I've gone travelling for a week so I might not be able to do much until a week later.
But I will follow up.
Thank you all!
Click to expand...
Click to collapse
Damn!! Well once you get back this app really has a lot of potential... just letting you know! don't give up man, this is gonna be awesome, I have a feeling!
Works great on my I9100 using LSS/AOKP Chameleon ROM.
Only thing I would change is the icon.
Does not work on HTC first running sense 4+ rom. Will revert back to stock rom tonight n give it a go.
Sent from my HTC first using Tapatalk 2
Working great on SGH-I337 Stock 4.2
FC on startup on i777 running JB 4.1.2
I can get to the conversation if I click on the incoming text notification; however trying to switch to the conversations list causes immediate FC.
Great job, this is the perfect SMS I've been looking for for years.
Sent from my GT-I9100 using Tapatalk 4
Beyond awesome!, just wish mms worked....sigh
Why is the right door always locked?
Spacemonkie4207 said:
Great job, this is the perfect SMS I've been looking for for years.
Sent from my GT-I9100 using Tapatalk 4
Click to expand...
Click to collapse
I couldn't agree more
It works perfectly on my galaxy s3 on 4.1.2 stock rom. Great piece of work my friend, well done
Sent from my GT-I9300 using Tapatalk 4
Any updates Dev?! Would loveeeee for this to be my daily driver messaging app, t is what I've been looking for, for a long time... an AOSP 9like messaging app, but I can use it on a TouchWiz ROM! Just wish MMS worked though
About Carbon
CarbonRom is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled roms, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best rom we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.
Please feel free to look at, build, and use our code on CarbonDev GitHub.
We would like to thank CyanogenMod for their device trees, framework/settings mods and their code that was incorporated into this project. We also extend our gratitude to the devs whose code that we have incorporated. Proper authorship has been maintained and can be viewed on our repository.
Special thanks also go to Slim Rom for some of their features, PA, AOKP, and anyone else we may have borrowed commits from that hasn't been mentioned here. If you feel you have been unfairly left out, please - let us know.
While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device, family, pets, or perception of reality. We ask that you do your part to know your device and know how to recover from problems before you flash! If you have questions, ask your fellow users or ask us in #teamcarbon on freenode IRC.
Screenshots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Carbon Updates
Join us on these Social Media Channels to keep yourself up-to-date on all the latest Carbon news, updates, contests, and more! Join our completely open Google+ community for insider conversation with devs and other users.
Download Carbon
All Carbon downloads and further information such as features, changelog, and FAQ can be found on our goo.im page.
CARBON-JB-UNOFFICIAL-20131009-2208-epicmtd.zip
Changelog
For a detailed changelog, check out the changes made each night here:
Change Log
Support
We spend an astonishing amount of time developing this software. We can't spend much time on XDA as a result, so if you need support, please try the following:
1) Search. Search, search, search. Yes, you. I don't care how unique or important your question is, it's very likely someone has adressed it already. Especially if you're even close to new at this.
2) Read our FAQ, which can be found on our goo.im page linked above. It's new, but expanding fast. Just like us!
3) Ask a question in your device forum. Someone will no doubt try to help you. Warning: this help may come in the form of telling you it's a dumb question that has been asked before. See step 1 - such are the perils of asking questions when you haven't done the research yourself. Android is about helping yourself.
4) Ask a question on our IRC channel. Connect to #teamcarbon on irc.freenode.net or click here. You'll find several other Carbon fans and usually one or more devs as well. Please be polite.
Who is Team Carbon?
Andros11
BigShotRob
Bionic Beast
dg4prez
Kejar31
mattmanwrx
morfic
nocoast
pixeldotz
slick_rick
winner00
Remember, every penny you send to us goes right back into the rom. It's used for hardware, server costs, etc - all the things that help us make Carbon better with every release. Your support means the world to us! If you've enjoyed Carbon, please consider a donation toward this goal. Thank you, and we hope you continue to enjoy Carbon!
This is obviously an unofficial build, but it runs great on my phone - and heck it's built on an official Carbon rig, so that's good enough right?
Enjoy folks, let me know if you have any issues.
Use standard gapps for 4.3...
gapps-jb-20130813-signed.zip Mirror #1 Mirror #2
First on the new thread
Sent from my SCH-I500 using xda app-developers app
let's see if this one can make me happy. thanks for the new toy.
Effsi said:
let's see if this one can make me happy. thanks for the new toy.
Click to expand...
Click to collapse
FYI I have noticed that mobile data bug from CM10.2 seems present here... I was on wifi, went out, data would not hook up until I rebooted the device...
Going to doublecheck that I have all the patches needed from 10.2, but I think I do :/
arrrghhh said:
FYI I have noticed that mobile data bug from CM10.2 seems present here... I was on wifi, went out, data would not hook up until I rebooted the device...
Going to doublecheck that I have all the patches needed from 10.2, but I think I do :/
Click to expand...
Click to collapse
The relevant patches that cured this on the CM builds were http://review.cyanogenmod.org/#/c/50036/ and http://review.cyanogenmod.org/#/c/50035/. They are still not merged so you might not have them. If you do have them, then well, I can make sure I'm not using any other random patches.
Sent from my SPH-D700 using xda app-developers app
bbelos said:
The relevant patches that cured this on the CM builds were http://review.cyanogenmod.org/#/c/50036/ and http://review.cyanogenmod.org/#/c/50035/. They are still not merged so you might not have them. If you do have them, then well, I can make sure I'm not using any other random patches.
Sent from my SPH-D700 using xda app-developers app
Click to expand...
Click to collapse
Ah, they are not merged...
Yea, I don't have these. Thanks!
Edit - built, just need to test if this fixed it...
Edit 2 - tested, seems to work. Uploading new build now
There isn't any special gapps package for this, right?
Sent from my SPH-D700 using Tapatalk 2
jeffreyjicha said:
There isn't any special gapps package for this, right?
Sent from my SPH-D700 using Tapatalk 2
Click to expand...
Click to collapse
4.3 gapps should be fine.
I'll add that to one of the posts I stole!
Edit - done
for some reason I can't seem to get my phone to get a radio signal outside of wifi. probably just something wrong with my flash... I'll post back eventually when I can reflash if no one else says it works/doesnt work.
Data, calling and texting work fine for me. I sometimes get the same text twice, or I'll be having a conversation and I'll randomly get the other person's previous responses, again. Also, I've noticed the front facing camera doesn't work for me and it hasn't for awhile.
I should add that I've had both of these issues on CM10.1.3.1
Sent from my SPH-D700 using Tapatalk 2
jeffreyjicha said:
Data, calling and texting work fine for me. I sometimes get the same text twice, or I'll be having a conversation and I'll randomly get the other person's previous responses, again. Also, I've noticed the front facing camera doesn't work for me and it hasn't for awhile.
I should add that I've had both of these issues on CM10.1.3.1
Sent from my SPH-D700 using Tapatalk 2
Click to expand...
Click to collapse
thanks for that! I was thinking it was on my end.
edit : confirmed data working. reflashed modem in odin and all is well.
jeffreyjicha said:
Data, calling and texting work fine for me. I sometimes get the same text twice, or I'll be having a conversation and I'll randomly get the other person's previous responses, again. Also, I've noticed the front facing camera doesn't work for me and it hasn't for awhile.
I should add that I've had both of these issues on CM10.1.3.1
Sent from my SPH-D700 using Tapatalk 2
Click to expand...
Click to collapse
Ah, thank you for confirming they are platform bugs.
I'll look into the front cam issue. Not sure about the multiple texts, but I use Google Voice, so I'm probably not the best use case.
I'm loving the active notifications tho!
Edit - so I just ran zDeviceTest, and the front cam worked as expected. Can you tell me where the front cam is failing for you?
arrrghhh said:
Ah, thank you for confirming they are platform bugs.
I'll look into the front cam issue. Not sure about the multiple texts, but I use Google Voice, so I'm probably not the best use case.
I'm loving the active notifications tho!
Edit - so I just ran zDeviceTest, and the front cam worked as expected. Can you tell me where the front cam is failing for you?
Click to expand...
Click to collapse
It just fails in general, like if I open the camera, and try to switch to the front camera, it FC's Gallery and then every time I open gallery or camera after that, it closes. The only thing I can do to use it again is to wipe data for gallery. Also I use Google Voice as well.So idk what the issue is there.
Sent from my SPH-D700 using Tapatalk 2
jeffreyjicha said:
It just fails in general, like if I open the camera, and try to switch to the front camera, it FC's Gallery and then every time I open gallery or camera after that, it closes. The only thing I can do to use it again is to wipe data for gallery. Also I use Google Voice as well.So idk what the issue is there.
Sent from my SPH-D700 using Tapatalk 2
Click to expand...
Click to collapse
For the text issue, did you enable Voice+, or are you using the GV app?
I also just tested this - open camera, switch to front camera - I see my ugly mug. Are you dirty flashing?
I did enable Voice+. Also I did a clean flash.
Sent from my SPH-D700 using Tapatalk 2
jeffreyjicha said:
I did enable Voice+. Also I did a clean flash.
Click to expand...
Click to collapse
This is the issue. Voice+ is known to cause problems like duplicate texts... I just use the GV app, I do not enable Voice+ personally and have never had this issue.
As for the front camera issue, perhaps clear cache on the gallery or camera app? That is strange, I can't seem to recreate it.
Well thanks for the info on Voice+. When I try to use the front camera, I usually clear data for it, idk if clearing cache will do anything different, but I'll check anyway.
Edit: Clearing cache does nothing.
Sent from my SPH-D700 using Tapatalk 2
jeffreyjicha said:
Well thanks for the info on Voice+. When I try to use the front camera, I usually clear data for it, idk if clearing cache will do anything different, but I'll check anyway.
Edit: Clearing cache does nothing.
Sent from my SPH-D700 using Tapatalk 2
Click to expand...
Click to collapse
Hm. Can you use that app I mentioned earlier? Z-Device Test. See if the front cam works there...
This is just the Sprint Visual Voicemail apps slightly modded so that the launcher icons better align with the new material design. I simply created the new icons in illustrator (one for each dpi), unpacked the apk and replaced the png's, repacked and signed. I'll try to keep this thread up to date with the latest version of the VVM app.
Confirmed working on s5 running 4.4.4 and s4 running 5.1.1 and with the newest update (vvmL). Keep in mind though, Sprint's VVM app is a finicky beast and it's performance/functioning heavily depends on the ROM that you're running.
Uninstall any existing Sprint VVM installation you have (to avoid mismatched signatures), then install the modded version as you would any other app. Enjoy!
Tip: Most ported ROMs contain information in build.prop from the device in which they were ported from, some unified builds may be slightly off. In order for this app to provision correctly, the following section in build.prop must be set to reflect your Sprint device before installing this app:
The following example is for the Sprint GS4:
Code:
ro.product.model=SPH-L720
ro.product.name=jfltespr
ro.product.device=jfltespr
(note this is not the tri-band L720T variant)
NOTE: The "9016" text messages are needed to wake the vvm client up to retrieve new voicemails as the come in. Blocking texts from 9016 in some sms apps (especially system sms apps) may cause the sprint visual voicemail app to not download new voicemail messaged. Muting the notifications for 9016 so your device doesn't ring/vibrate is ideal.
Don't have 9016 blocked or blacklisted, but still not receiving voicemails in the app?
Try reactivating VVM by opening the app, touching compose, recording a 5+ second message delivering it to [email protected].
Yes, the phantom voicemail notification is here on most kitkat ROMs. You can temporarily clear it by disabling then re-enabling notifications from vvm. I've personally had success by going into the app and selecting the voicemail message and touching "save" to move it into the archive folder. This has seemed to permanently fixed the phantom notification bug for me, IDK why.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Just pulled Sprint VVM T.7.0.0.16 (Sprint-vvm-m.apk) from the latest update-PB6 (Marshmallow) on GS6 edge . Haven't gotten a chance to test on any other phone/ROM so install at your own risk.
Thank you for this!
The newer APK didn't work for me and though the first APK worked, it doesnt rexieve any voicemails am I missing something?
jcoinster said:
The newer APK didn't work for me and though the first APK worked, it doesnt rexieve any voicemails am I missing something?
Click to expand...
Click to collapse
Are you by chance running a ported lollipop rom? Some people have reported issues with sprint vvm (even with the stock, unmodded version) myself included. I think this occurs because the build.prop's of some ported roms shows information from the device which they are ported from. To correct this, grab a build.prop editor from the play store or use es file manager to edit the build.prop. The sections ro.product.model, ro.product.name and ro.product.device should look like this for the Sprint GS4 L720 (not the L720T variant):
Code:
ro.product.model=SPH-L720
ro.product.name=jfltespr
ro.product.device=jfltespr
The GPE port I'm running had all the information from the international Google play edition GS4. I uninstalled Sprint VVM, edited the build.prop, and reinstalled and it provisioned flawlessly and the app functions as it should.
Thanks for the heads up on the new VVM, I wasn't able to test that one yet. I'll take it down and see whats going on and repost later. Did it give you any errors? or did it just say app not installed?
I downloaded the apk, but lookout says its riskware?
I get that same message when I download apks and Roms in chrome. Mobile lookout might be giving you this message because I had to sign the apk in order to make it installable so the my signature doesn't match the official Sprint signature in the apk. I can assure you though I didn't mess with the code within though (I wouldn't even know how) just swapped out .PNG image files
Hypochondria said:
I downloaded the apk, but lookout says its riskware?
Click to expand...
Click to collapse
Or if you want, grab a different copy of the official vvm apk and give it a try. That fix I pm'd to you about the with build.prop should fix the problem you were having with voicemail and the gpe ROM we're running
exeleon said:
Or if you want, grab a different copy of the official vvm apk and give it a try. That fix I pm'd to you about the with build.prop should fix the problem you were having with voicemail and the gpe ROM we're running
Click to expand...
Click to collapse
It worked, thanks so much
The newer zip just force closed on opening. I tried the build prop and it didnt work (I tried modifying it on an HTC M8 with the correct device info).
jcoinster said:
The newer zip just force closed on opening. I tried the build prop and it didnt work (I tried modifying it on an HTC M8 with the correct device info).
Click to expand...
Click to collapse
Yes, I removed the latest in the op, I wasn't able to test myself and when I did I had the same results as you. After the build.prop edits and reinstall the first version worked though correct?
I am too on the GPe 5.0 rom.
- So I change the build.prop and then just install the apk
- Recvd a text from 9016 stating Provisioning successful
- called myself from another phone and IT WORKED!!!!!
This worked for me on my Sprint Note 4 running Slim Rom 5.02 also. Thank you so much. Linking this is our thread if you don't mind.
e92dream said:
This worked for me on my Sprint Note 4 running Slim Rom 5.02 also. Thank you so much. Linking this is our thread if you don't mind.
Click to expand...
Click to collapse
Hey, no prob! Go right ahead and link this thread to yours!
e92dream said:
This worked for me on my Sprint Note 4 running Slim Rom 5.02 also. Thank you so much. Linking this is our thread if you don't mind.
Click to expand...
Click to collapse
Were you still getting the 9016 texts everytime you get a voice mail?
If so, how'd you go about stopping it? I don't want to block them in case that stops my voicemail alerts.
exeleon said:
Are you by chance running a ported lollipop rom? Some people have reported issues with sprint vvm (even with the stock, unmodded version) myself included. I think this occurs because the build.prop's of some ported roms shows information from the device which they are ported from. To correct this, grab a build.prop editor from the play store or use es file manager to edit the build.prop. The sections ro.product.model, ro.product.name and ro.product.device should look like this for the Sprint GS4 L720 (not the L720T variant):
Code:
ro.product.model=SPH-L720
ro.product.name=jfltespr
ro.product.device=jfltespr
The GPE port I'm running had all the information from the international Google play edition GS4. I uninstalled Sprint VVM, edited the build.prop, and reinstalled and it provisioned flawlessly and the app functions as it should.
Thanks for the heads up on the new VVM, I wasn't able to test that one yet. I'll take it down and see whats going on and repost later. Did it give you any errors? or did it just say app not installed?
Click to expand...
Click to collapse
Hey there. I am having the same problem as you. I downloaded an editor and
am comfortable using it, but am just not sure exactly what I should change.
I'm hoping you would be willing to help me out. I'm using a sprint note 3,
rooted of course, with the AICP Lollipop 5.0.2 rom. The device model under
settings shows it as an hltespr while the ro.product.model shows aicp_hltespr. I'd really appreciate any help you fouled offer of. Thanks!
jfogle01 said:
Hey there. I am having the same problem as you. I downloaded an editor and
am comfortable using it, but am just not sure exactly what I should change.
I'm hoping you would be willing to help me out. I'm using a sprint note 3,
rooted of course, with the AICP Lollipop 5.0.2 rom. The device model under
settings shows it as an hltespr while the ro.product.model shows aicp_hltespr. I'd really appreciate any help you fouled offer of. Thanks!
Click to expand...
Click to collapse
I believe the model number for the Sprint N3 to be SM-N900P while the name and device values should = hltespr. Keep in mind I have yet to test this on 5.0.2. Let us know how it goes.
exeleon said:
I believe the model number for the Sprint N3 to be SM-N900P while the name and device values should = hltespr. Keep in mind I have yet to test this on 5.0.2. Let us know how it goes.
Click to expand...
Click to collapse
You called it exeleon! Worked great!! Now, if I could just figure out how to stop those 9016 texts without it messing up what I just did!!! I'm considering texting 9999 and sending them the 9016 number....you think that will work?
Update:
I just tried texting 9999 with "block 9016" and this is what I received back:
"SprintFreeMsg: Sorry, the sender "9016" cannot be blocked because it is used for legal or account related notices."
Any other ideas would be greatly appreciated!! Thanks again!
Yet another update:
OK....I just found out that in my messenger app, after selecting a message to read and/or reply to, that while in the message if you click on the drop-in menu in the upper right-hand corner, you'll see an option to "add to blacklist". Well I clicked on it and added it but won't know if it works until I get another voicemail. When I do I'll let you all know!!
jfogle01 said:
You called it exeleon! Worked great!! Now, if I could just figure out how to stop those 9016 texts without it messing up what I just did!!! I'm considering texting 9999 and sending them the 9016 number....you think that will work?
Update:
I just tried texting 9999 with "block 9016" and this is what I received back:
"SprintFreeMsg: Sorry, the sender "9016" cannot be blocked because it is used for legal or account related notices."
Any other ideas would be greatly appreciated!! Thanks again!
Yet another update:
OK....I just found out that in my messenger app, after selecting a message to read and/or reply to, that while in the message if you click on the drop-in menu in the upper right-hand corner, you'll see an option to "add to blacklist". Well I clicked on it and added it but won't know if it works until I get another voicemail. When I do I'll let you all know!!
Click to expand...
Click to collapse
From what I've read, as long as your SMS app isn't installed as a system app you can block 9016 texts. Otherwise, if it is a system app, it gets blocked at the system level so the vvm app never knows when to retrieve messages. I use Google messenger as a system app and I muted the notifications so I still get the SMS, but my phone doesn't ring or vibrate when they come in.
exeleon said:
From what I've read, as long as your SMS app isn't installed as a system app you can block 9016 texts. Otherwise, if it is a system app, it gets blocked at the system level so the vvm app never knows when to retrieve messages. I use Google messenger as a system app and I muted the notifications so I still get the SMS, but my phone doesn't ring or vibrate when they come in.
Click to expand...
Click to collapse
Hey there.
I'm also having that issue with the Sprint Note 3. I did my build.prop edits, dialed *38 to make sure none of my calls were being forwarded. My phone is getting the voicemails, just not to the visual voicemail app. Just keep getting the messages from 9016.
Whenever I re-install it I get the "Verifying account..." message and shortly after the "Account Verification Failed". The first time I did it, 9016 sent me a message saying "Provisioning successful" but nothing.
Not too sure what I'm doing wrong here, would love any insight you may have.
***UPDATE****
& the noob in me is showing. I figured it out. I did the very first thing you advised we do "Compose 5+ second message and email to vvm..."
That did the trick. Don't know why I didn't see that at first. Thanks again for all your work.
Ravyn405th said:
Hey there.
I'm also having that issue with the Sprint Note 3. I did my build.prop edits, dialed *38 to make sure none of my calls were being forwarded. My phone is getting the voicemails, just not to the visual voicemail app. Just keep getting the messages from 9016.
Whenever I re-install it I get the "Verifying account..." message and shortly after the "Account Verification Failed". The first time I did it, 9016 sent me a message saying "Provisioning successful" but nothing.
Not too sure what I'm doing wrong here, would love any insight you may have.
***UPDATE****
& the noob in me is showing. I figured it out. I did the very first thing you advised we do "Compose 5+ second message and email to vvm..."
That did the trick. Don't know why I didn't see that at first. Thanks again for all your work.
Click to expand...
Click to collapse
Glad you got it working!