yashsingh1/xdaforums huggingface dataset:
[Hero CDMA Android Development] BothGunzUP:
I did the same thing you did, I just pushed the Mms.apk right overtop of the last one. It did push it right over, I checked inside the /system/app folder on my phone and your APK was in there. The icon for it was simply a white icon that had the text APK with an orange cog in the bottom right corner. All the other APKs in that directory had their app icon or the green android guy icon. This kinda let me believe the system wasn't recognizing the file or it was corrupt somehow.

After placing the new Mms.apk file on my phone, it was like there was no messaging app at all. Not in Apps list, on my home page, and if I long pressed the search button, the only option was to voice search when it usually asks you to choose messaging or voice search. So somehow it didn't take.

I may just retry it again and see what happens. It has worked for others.
[Hero CDMA Android Development] Cipherblox:
This fix should not interfere at all with any themes. It merely adds code to the WorkingMessage.java to handle the case where a message contains too much text for the network.

I looked at the CM source code and there is literally no difference between this WorkingMessage.java and the other WorkingMessage.java. The difference is in the modifications that CM does on other files.

That would mean that in the make process to generate the .apk file, CM6 links to additional libraries thatare no longer there. I'm trying to get a fix up for CM6 users as fast as possible; however pulling down the entire branch again and compiling will take hours - so I'm trying to pull down a particular package in the CM branch.

-Kevin
[Hero CDMA Android Development] theimpaler747:
No, we were wondering if themes interfered with this ;)
[Hero CDMA Android Development] 151jcolon:
nevermind about it.
[Hero CDMA Android Development] BothGunzUP:
So this won't work for CM6 as it is now? So there is no point in me retrying this? I know you use a different MOD than I so I was just curious if that is why it wasn't working.
[Hero CDMA Android Development] Cipherblox:
Yea - it shouldn't interfere, but I am unfamiliar with how you theme the ROMs so if it is calling methods or objects or linking things in some other way than just affecting the look of the .apk, there could be a problem. I am running AOSP 0.9.7 - perhaps someone could try using this on AOSP instead of CM6.1.

-Kevin
[Hero CDMA Android Development] theimpaler747:
I agree, it shouldn't, and it'd be good for testing to have some aospMOD users try this.
[Hero CDMA Android Development] Cipherblox:
I mean you can TRY- but it is unlikely that you did anything wrong. I think CM is expecting certain objects to be linked that aren't there. If you give me a few minutes though, I think I can pull down the CM6 source code and regenerate an Mms.apk for you.

Shouldn't be more than 5-10 minutes.

-Kevin
[Hero CDMA Android Development] aosp:
bring it over to the thread:D
[Hero CDMA Android Development] BothGunzUP:
OMG thank you! I am waiting anxiously, and I'll test this out and let everyone know if it works. :D
[Hero CDMA Android Development] Cipherblox:
Im compiling the changes with CM's files right now and just in that I'm blown away at the amount of changes this causes as an incremental make is updating the .dex and the .apks for Calculator, Browser, etc...

I'll post in a few minutes as soon as it finishes making the changes.

-Kevin
[Hero CDMA Android Development] BothGunzUP:
Huh. So is this new Mms.apk your compiling somehow linked to all these other apps your referring to (Calc, Browser, etc.)? What does it mean when it updates the .dex and .apks for these other apps? Will I have to update them as well, so they are all on the same page, so to speak?

Obviously, I don't know how this all works or how CM6 implements it but I am just curious, I like to know how things work on a deep down level.
[Hero CDMA Android Development] Cipherblox:
Here it is:

Try this Mms.apk which was compiled with CM6's MMS package code.

http://www.mediafire.com/?o59c369b5ndvb20

Let me know if this makes a difference. If it doesn't, I can pull down the entire CM6 repo and try again (Though this will take a long time to recompile.

-Kevin
[Hero CDMA Android Development] Cipherblox:
The fact that it updates those files I think simply means that the Makefile (The file that calls all the gcc compile commands) noticed enough changes to update all packages.

However, the MMS directory, while containing the same WorkingMessage.java as AOSP, probably contains other files that weren't there and, thus, should be significantly different now.

-Kevin
[Hero CDMA Android Development] BothGunzUP:
Ok, I just pushed the CM6 Mms.apk you just posted and now I don't have the default messaging app on my phone. The new Mms.apk is in the /system/app directory, Estrongs File Explorer shows that and it has the same file size as what I just downloaded with dates to match.

But for some reason, CM6 isn't verifying it as the messaging app. When I first boot the phone after reboot, I get a weird icon in my status bar up top which looks like the phone is trying to do something. I have never seem this in my statusbar up top before. Im going to try and reboot and see what is going on with that. But here is a screen shot of my /system/app folder so you can see the icon for Mms.apk, its the only file in this directory with an icon like that. It's gotta mean something.

Does CM6 somehow only want their Mms.apk? Is there some kind of check for only their version. The way it is now, its like I have no default messaging app on my phone at all.
[Hero CDMA Android Development] Cipherblox:
Hmm.... that is weird. I honestly don't know. Perhaps CM requires an update.zip or requires me to build with their makefile.

It will take a while, but let me pull down the entire source for CM6.1, apply the patch and then build from there. This will take a few hours unfortunately.

A push SHOULD do this already, but, in the mean time, if you wouldn't mind trying to flat out delete the Mms.apk and then repush it - if not, I'll work as fast as I can to get the CM6 source code compiled.

-Kevin
[Hero CDMA Android Development] BothGunzUP:
Delete and repushed and still nothing. I wonder what it could be? The system seems to be picky about this for some reason. Since Mms.apk is there should it just use that as the messaging app? Is the system no liking that it was modified at all?
[Hero CDMA Android Development] Cipherblox:
That *IS* what should happen.

This is so weird. I downloaded estrongs and looked at my /system/app folder and I had the proper icon there.

CM6 must be doing something weird to verify .apks. Part of me wonders if I need to sign the apk for CM6 to work with it.

I'm real sorry about this by the way - I honestly had no idea CM6 would be this different than AOSP.

Does anyone else know what needs to be done in order to load custom apks on CM6? I'm going to post in the CM6 thread as well and see if I can't get someone over there to help as well.

-Kevin
[Hero CDMA Android Development] theimpaler747:
Should just install right over :confused:
[Hero CDMA Android Development] BothGunzUP:
No need to be sorry. I appreciate all the work done to get this working. Maybe someone could ask cyanogen what's going on as he would know best I think. Maybe he needs to roll it into the next update?

Maybe it has to be signed and flashed via recovery? Is there a way to do that? Maybe setup the signed zip file to put the apk in /system/app from recovery.

I'm just spitballing here but I'm confident you got it working we just need cm6.1 to recognize it.
[Hero CDMA Android Development] someonenewhere:
the 1st mms.apk attachment is for AOSP? if that's the case....I'm pushing it to my phone tonight to fix the 160 chars problem..
[Hero CDMA Android Development] Cipherblox:
Yes - the first one is for AOSP. The second one isn't working yet, but it is ideally for CM6.
[Hero CDMA Android Development] theimpaler747:
Yes that's correct :)
[Hero CDMA Android Development] someonenewhere:
Thanks you guys!.....Now i can send big text messages in one text...
[Hero CDMA Android Development] theimpaler747:
Don't thank me, it was all Gamingphreek on this one :)
[Hero CDMA Android Development] BothGunzUP:
Someonenewhere have you tried it and is out working for you?
[Hero CDMA Android Development] someonenewhere:
Just pushed the Mms.apk for AOSP....rebooting as I type..

I will test it out and let you all know if it's working or not.. ;)
[Hero CDMA Android Development] theimpaler747:
It should, it's been working well for aosp users so far, just not CM
[Hero CDMA Android Development] someonenewhere:
hmmm sent a big message and it hanged on me...tried it with the stock mms app....

then on handcent removed the send settings and it didn't work..

but with the settings set on handcent to Auto-convert to MMS and 160 set to simple split..it worked.....
[Hero CDMA Android Development] Cipherblox:
Are you running AOSP or CM6?

That is really weird that you are running into those kinds of problems though. It certainly shouldn't hang...
[Hero CDMA Android Development] someonenewhere:
newest AOSP version ...but yes, I didn't get sent out....
[Hero CDMA Android Development] Cipherblox:
When you say it didn't get sent out and it hanged on you what all do you mean?

Did the message you typed appear in your list of messages to the particular recipient? Did a message fail to send? What all happened?

-Kevin
[Hero CDMA Android Development] someonenewhere:
it hanged...then it failed to send....
[Hero CDMA Android Development] Cipherblox:
Hmm - you just used the standard Messaging app? I wonder if Handcent was interfering with the sending process in some way.

-Kevin
[Hero CDMA Android Development] someonenewhere:
Maybe...i'll remove it and give you feedback when I do..

Sent from my AOSP 2.2 ... Eat a fat one Sprint!
[Hero CDMA Android Development] BothGunzUP:
Yea let us know if handcet is interfering in any way. I'm curious as well. For CM6 users we gotta see why the apk isn't registering with the OS like it does with AOSPMod.
[Hero CDMA Android Development] SirRipo:
Really hoping this gets resolved on CM6, it would be SO nice.
[Hero CDMA Android Development] JustRuin:
I tried this out on the latest MIUI ROM, and no dice :\

I don't know if there's any big difference.

After it rebooted, the messaging app was gone (though it was still in /system/app)

I'm sure there's some kind of difference because the file sizes are different to begin with.

If someone could let me know what's up?

Thanks!
[Hero CDMA Android Development] gmoney41685:
Hows the progress on the phantom vm notification? I will gladly donate to whoever fixes that.

Sent from my Hero CM6.1 Rc1
[Hero CDMA Android Development] Cipherblox:
I looked briefly at the VM Notification code, but am largely devoting my efforts towards fixing the SMS Text Message issues right now.

I cannot for the life of me understand why the Messaging.apk is not working properly with builds outside of AOSP.

I'm at work right now, but I will pull down both the CM code, the AOSP code, and the FroYo branch (instead of the Master branch), patch, and build all of them. I'll try to post all 3 .apks later tonight.

-Kevin
[Hero CDMA Android Development] aosp:
please link a .diff of your patch so i can try to compile it thanks;)
[Hero CDMA Android Development] Cipherblox:
I'm at work for another 4 or so hours, but I'll link a .diff as soon as I get home.
[Hero CDMA Android Development] theimpaler747:
Is this still not 100% correct yet?
[Hero CDMA Android Development] Cipherblox:
Just uploaded now :)

http://www.mediafire.com/?337z11km63g2e84

Here is the link to the udiff patch. Let me know if you need anything else AOSP.

-Kevin
[Hero CDMA Android Development] 151jcolon:
I'm testing nightly 127 and so far there is not issues.
[Hero CDMA Android Development] theimpaler747:
Great! PM me when it's 100% Gamingphreek and I'll include it in all my themes :)
[Hero CDMA Android Development] Cipherblox:
Awesome! Thats a CM ROM that is working which is terrific. I wonder what is going on with everyone elses ROM's. Did you do anything special or did you just do a push?

Will do theImpaler! Thanks for the encouragement and troubleshooting :)

-Kevin
[Hero CDMA Android Development] theimpaler747:
No problem, let me know if you need anything or any testing :)
[Hero CDMA Android Development] 151jcolon:
Sorry I'm still testing. 127 is failing now. Arrrgg :(
[Hero CDMA Android Development] theimpaler747:
Is it failing to send?
[Hero CDMA Android Development] 151jcolon:
yesss... man.. i cant send 4 row message

4 row is like 80 letter I think so.
[Hero CDMA Android Development] Cipherblox:
You can't judge a message like that. If, after typing, you hit the back button and a number isn't present in the bottom right corner, you haven't gone over or come close to going over 1 message yet.

-Kevin
[Hero CDMA Android Development] Cipherblox:
I'm asking this to anyone who knows:

When should you clear the Dalvik cache? I'm wondering whether a Dalvik Cache wipe might fix problems some users are having.

-Kevin
[Hero CDMA Android Development] BothGunzUP:
Is there an updated CM6 version yet? I would like to test it out if there is. I'll wipe dalvik if need be.
[Hero CDMA Android Development] Cipherblox:
Outside of the nightlies, CM6.1 should be the latest version.

I really appreciate all the testing BothGunz! Like I said earlier, I'm real sorry that you are having to debug this and am really trying everything to get this fix working for you!

Hopefully AOSP will come back and notice something when trying to compile it in his own code.

-Kevin
[Hero CDMA Android Development] BothGunzUP:
Anyway I can contribute is fine by me. I just wish I could figure out why CyanogenMOD isnt recognizing the Mms.apk that you built. Does anyone know if CM6 is "rejecting" (loose term) the Mms.apk because it isn't theirs?

For all we know your new APK is fine, but maybe CM6 knows its not default so it won't use it.

Oh, btw, you said earlier that you would pull down CM6 trunk and see about recompiling APK specific for this. Did you create an updated Mms.apk yet or no? Let me know and I'll gladly test it for you.

Oh, and I pushed the one you created yesterday on my phone and wiped dalvik just to see if that would help and it was a no go. Oh, well couldn't hurt to try. Let me know if you need me to test out a new one.
[Hero CDMA Android Development] Cipherblox:
I'm pulling down the source code as we speak. I would have it done faster, but Apple, in its infinite wisdom, uses a Filesystem that is Case-Insensitive - thus I have to create a virtual partition for all Android work.

I'll let you know as soon as I get it built though :)

-Kevin
[Hero CDMA Android Development] BothGunzUP:
Sweet, can't wait! :)
[Hero CDMA Android Development] theimpaler747:
You can wipe dalvik at any point, just needs to be done via recovery
[Hero CDMA Android Development] dpeeps74:
Here is a screenshot just to show I'm not crazy. Sent it to my gv # and it was fine too. I made a logcat, and can add it and my mms.apk if you like. Again, my setup is pretty standard. had to just attach photo, it didn't like my flickr link.

And yes, you all have my number now cuz I'm too lazy to edit, that's how unaltered this cap is.

*EDIT* ok, now that i'm on a computer it's altered without my phone #. Also attached are the logcat while running mms (may not be super useful, but shows the compose message calls, and if i read part of it right, appears to properly recognize as 3 messages. Also attached is the mms.apk from my cm6.1. as noted, only changes, other than apps are CFS kernel and a theme made from UOT, however i was able to text with just 6.1 prior to those changes..but you're correct, there could be all sorts of code changes going on i would n't see, so figured i could do something to give you helpful information vs just being an ass today :)

View attachment Mms.apk

View attachment sms-logcat.zip
[Hero CDMA Android Development] theimpaler747:
Looks like it works to me! And I'd edit that if I were you please ;)
[Hero CDMA Android Development] Jim_Bob:
Phantom VM or Update

I've read the entire thread...and I know you are working on the texting issue...but I'm trying to figure out if you mean a voicemail notification of a call or a notification of a "Mandatory Update" I have update notification and can't make it go away.
[Hero CDMA Android Development] Infinity03:
What 160 bug? I am using the stable release of CM6 with the stock messenger and don't have a problem sending texts longer than 160 characters - it splits and successfully sends just fine.
[Hero CDMA Android Development] mulhiny:
Look in the theme/app section. The updated voicemail has been posted.:D
[Hero CDMA Android Development] junkshow:
Which build? I'm running nightly 117, and it always fails. Has on every nightly I've ever tried.
[Hero CDMA Android Development] Cipherblox:
I certainly never thought you were lying - just to clear that up ;)

I do think that CM6.1 must have recently made a change that facilitates the sending on long SMS as in the Master branch of the AOSP code from google, nothing is present.

I'm not familiar with ARM Assembly Code (I stick to x86 Assembly when I need to), but I'm going to run a diff of a Disassembled version of your APK and the stock android APK and figure out what is different. I suppose it may be easier for me to just look at the recent CM code itself instead of the disassembly lol.

I know there is a method call to check whether or not MMS is required, so it may be converting the message to MMS without alerting you. Perhaps this method is broken in the AOSP source and that instead of merely fixing it, I rewrote it.

I'll look into it.

Gunz - the CM code is downloaded on my system. I'm having my wisdom teeth yoinked tomorrow so I've been kinda busy and neglected to start it compiling while I am at work. I promise I'll have an attempted fix posted tonight though!

As for the voicemail notification: It is a notification to call a specific number that is set regardless of whether you disable call in Voicemails or whether you have a Voicemail. It simply triggers a notification when you switch towers and gives you a notification to call number 'x'.

-Kevin
[Hero CDMA Android Development] yadnom:
I haven't had this problem either. I'm running CM6.1 and my messages split and send without issue.
[Hero CDMA Android Development] Infinity03:
[ROM] CyanogenMod-6 for Hero CDMA - V6.0.0 (09/18/2010)

I tried to post the link, but since I am a new user it wont let me.
[Hero CDMA Android Development] JustRuin:
The issue is a network tower issue as far as I know. At least that's what multiple people have claimed.

Depending on your location, sending long messages may or may not work.

Gamingphreek simply seeks to remedy the problem for those (including himself) who are having it.

What I gather from this is that it is *not* a "so-so rom build so-so" issue (yet?).

I say this because I notice enough people asking why this is going on, given that they cannot reproduce the issue.

If you're skeptical, then take a look at Handcent/ChompSMS. They both have this feature already, because the issue must exist (Why would they add it for no reason?)

Another thing to point out is that a lot of Sprint users specifically, have this issue. There is even a way to change your PRL to Verizon's so that you gain the ability to send the long messages (since Sprint's, apparently, is the faulty one)

I'm in no way an expert though, so I could be absolutely wrong :p
[Hero CDMA Android Development] yadnom:
Thanks for the explanation JustRuin. That does make sense to me as I have not had any issues.

Regardless, I just wanted to say thanks to the devs like Gamingphreek who put in their own time to work on fixes for everyone.
[Hero CDMA Android Development] 151jcolon:
i have the issue... my baseband version is 2.41.01.04.27
[Hero CDMA Android Development] theimpaler747:
Yeah, it's always failed on CM really :confused:
[Hero CDMA Android Development] dpeeps74:
Gaming, to note what you mentioned about the mms conversion, that does happen but I've only hit that limit once that I can recall and it was at 4 or 5 message length. It surprised me when I saw it because it actually said it was converting to mms or something. Definitely though, if you are able to resolve this for the many that seem to have the problem I would love to not see all the posts on it anymore! Hopefully the log or apk I posted will help.
[Hero CDMA Android Development] Cipherblox:
Yea - I think the code here that I have has it set to 8 messages before it switches.

Also, I cannot get the Cyanogen Source to compile. For whatever reason their Makefile requires OSX 10.4 SDK's - something that is no long available (And hasn't been for quite some time). I'm going to try and edit the Makefile, but if anyone has any ideas on how to compile it on 10.6.5 I'm all ears...

-Kevin
[Hero CDMA Android Development] BlaqkAudio:
This is for the Nexus One, but I reckon it should be the same process overall:

http://wiki.cyanogenmod.com/index.php?title=Compile_CyanogenMod_for_Passion_(Mac)
[Hero CDMA Android Development] Cipherblox:
Excellent catch! I never thought of using a symbolic link to make the Makefile think that 10.4u.sdk actually does exist.

Compiling now!

Unless this compiles in the next few minutes (Doubtful) it may be a day until I am able to do anything. I'm getting my Wisdom teeth out tomorrow so I'm not sure developing will be high on my priority list ;) (I'll try though)

-Kevin
[Hero CDMA Android Development] BothGunzUP:
I too use the same radio and have the split message issue. Those of you who have no problems with split messages, are you using the default messaging app and what radio are you using?
[Hero CDMA Android Development] BothGunzUP:
Gamingphreek, no worries. Take care of yourself and I'll test your hard work when you finish. :)
[Hero CDMA Android Development] vinnypel2ella:
it keeps giving me the error "[INSTALL_FAILED_OLDER_SDK]"...what does this mean?
[Hero CDMA Android Development] yadnom:
I don't have the issue. I'm running CM 6.1 on baseband 2.42.01.04.27 using the default messaging app.
[Hero CDMA Android Development] texas83:
I don't have an issue with the text messages, but I do have the ghost VM notification.

I'm going to try and document whats going on now. I've already uninstalled sprint VVM until I figure this out. I went in to Titanium backup and scrolled through the apps. Theres no app under voicemail anymore. There is however, an app/process called "[VOICEMAIL] Dialer 2.1-update1". When I click on this, I have the option to "Wipe Data". Wiping the data causes the notification to go away!... But only for 10-15 seconds, then it reappears. Now the VM notification says "Dial *86". I used titaniums freeze function and froze the app. Then I wiped data, notification disappeared, then reappeared again, even with the app frozen. While the app is frozen, if I try to access the call settings function in the menu, it gives me an error force close that the com.android.settings has stopped working unexpectedly.

After I unfreeze the app, voila, the settings function works again, but the notification remains =(

Even with the Sprint VVM uninstalled, and the cache and data cleared, the notification stays there!
[Hero CDMA Android Development] JusticeAA:
This problem needs to be fixed within the system code of the ROMS. Unless you know how to do that, save your time because it is next on the list after the SMS issue gets resolved.
[Hero CDMA Android Development] SirRipo:
wait...how does one update their baseband? Is it just the radio version? Mine's at 1.04.01.09.21! How does one update the radio?
[Hero CDMA Android Development] aosp:
flash this 2.42.01.04.27 from recovery;)
[Hero CDMA Android Development] SirRipo:
That's definitely the right one, right? don't wanna brick my phone.
[Hero CDMA Android Development] theimpaler747:
Yes it is, or see my sig if you're not sure :)