yashsingh1/xdaforums huggingface dataset:
[Hero CDMA Android Development] BothGunzUP:
Ok, wow so I was testing my butt of trying to figure this thing out. I was taking all types of Mms.apk files from all different ROMs even Sense ROMs just to see what was going on here. Why can't the default messaging app split these into multiple messages, right? Well, I kept sending my bro, who is on Sprint with an Epic, a text message that will span two complete texts.

The funny thing is, the default messaging app from CM6.1 * IS * actually trying to split these messages up. It just fails to send them. I know this because every 2 message text that I send, I get back 2 failed messages notifications. So it split the message but the SPRINT NETWORK failed to send them.

So I was looking at APN XML file in the /system/etc folder and looking at settings, they were all right.

Then I went into settings > Wireless and Networks > Mobile Networks > System Select as this tells the phone what CDMA networks to use.

The settings are Home, Affiliated Networks, Auto. The default is Auto.

If I put this on Home (Sprint), the multi-spanning texts will fail. And I get 2 message notifications of said fail.

If I put this on Auto (In my case Sprint, others may default to Affiliated depending on where you are), the multi-spanning texts will fail. And I get 2 message notifications of said fail.

If I put this on Affiliated Networks, The multi-spanning texts will SEND correctly!

This is leading me to believe this is a Sprint Network issue of sorts. Or a radio issue, which is kind of the same thing in my eyes. I haven't tried different radio versions to see if this is the case with all of them, but one thing I do know, is that in my house, I get 1 bar on AUTO or HOME. I get 3 bars on AFFILIATED NETWORK. Which I think is Verizon, not positive.

Oh and I am using the latest Radio as I stated early in this thread.

So to those who claim not to have this issue, what System is selected, Auto, Home, or Affiliated?

For those who do have this issue, let me know as well, and try setting this to Affiliated and see what happens. Just send a large text and let me know what happens.

Sorry for rant. Trying to be detailed and informative. :)
[Hero CDMA Android Development] spanglmd:
I don't have the issue. I'm running CM 6.1 on baseband 2.42.01.04.27 using the default messaging app. Network is set to Automatic.
[Hero CDMA Android Development] BothGunzUP:
Interesting, I don't know where you reside, but it may just be that you are using Affiliated Networks by having it on Auto, simply because that is only service to you.

Maybe its just certain people in certain areas who have this issue to begin with. I am on the East Coast in NJ, about 3 miles from Philadelphia. Maybe its just in certain locations. Not sure.
[Hero CDMA Android Development] JustRuin:
I don't have "Affiliated Networks". I don't know if that has to do with the fact that I'm running on MIUI or not, though.

ALSO i have an EVO if THAT changes anything

lol...i forget where i am sometimes
[Hero CDMA Android Development] SirRipo:
I can recreate this. Latest radio, if I switch to affiliate network it will send but not under home network or auto.

Sprint said no Froyo for Hero, I said eff that.
[Hero CDMA Android Development] chinkster:
can someone confirm that the SMS character limit bug is fixed for CM6.1??
[Hero CDMA Android Development] SirRipo:
It's being worked on, but work on it might be slow the next few days, gaming is getting his wisdom teeth pulled so he might not be feeling up to working on it too much.

Though, from what we're seeing, it looks like this may be a network issue, not an issue with the messaging app as originally thought.

As a note, now that I think about it, it seems like what we need the app to do is split the message and send it as two separate messages, right? That seems like what the HTC messaging app did, would it be at all possible to use some of the code from that apk, modifying it for the AOSP/CM6 framework? Of course, I could just be retarded with this, I really don't know anything about coding or what needs to be done.
[Hero CDMA Android Development] Cipherblox:
Hey Ya'll. I'm feeling well enough today (Anesthesia finally stopped screwing with my stomach) that I'll get some coding done.

So what I have gathered so far from when I last posted, is that CM6.1 seems to have code that handles larger messages, but it is not working correctly on Sprint CDMA based towers - only on Verizon and others.

My compile was going well; however, apparently 10GB is not enough for CM6.1 to fit on - thus I need to create a new Virtual Disk and start it compiling again. Shouldn't take too too long.

As for your though SirRipo - that is actually what my code does. It detects how long the message is, from that finds how many messages it needs to be broken into, dynamically allocates a String array of sufficient size, and goes to work. In short, you were spot on with your assumption :)

I know I just said your reusing the APK doesn't apply since I have the source code and have implemented it in the manner you suggested; however, I did want to speak about reusing APK's. If you are at all familiar with the Java programming language, an APK is very similar to a .JAR file - a compiled Java file. Thus, in order to glean any code from it I have to disassemble the file and read the ARM9 Assembly Code from it and try and recreate Java code from it (Not easy to do in the slightest). In short, disassembling and manually reassembling is not a desirable way of operating if it can be avoided ;) )

I'll let ya'll know when CM6.1 is compiled and I'll take a look at the series of Java code that comprises their Messages.apk. Nobody has been able to get long messages working on AOSP on a Roaming tower yet, right?

-Kevin
[Hero CDMA Android Development] SirRipo:
Ah, I can see where that could be undesirable. It seemed...simpler to me for some reason lol. Well hopefully we can figure something out to get it working. If you need another tester, I'm free most of the time.
[Hero CDMA Android Development] Cipherblox:
Ok - I just ran a diff of the entire Mms/src subdirectory in CM6.1 and AOSP Master branch. The ONLY difference between the 2 was my changes.

I am still unable to see where this is splitting messages unless specific towers somehow notice they can't pass a message of large size and send only what it can at 1 time.

Additionally, I am unable to get CM6.1 to compile on my system. I keep getting errors regarding my processor not supporting `uxth r0,r0', `uxth r6,r6', `uxth r9,r9', `uxth r11,r11'

-Kevin
[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. System is set to Home. PRL 60671 if that makes any difference as well.

I'm also in the Twin Cities, MN area.
[Hero CDMA Android Development] Psycoboy15:
I have the phantom voicemail issue and have had it since CM6. I still have it in CM6.1 also... It's my only complaint about the rom. It is easy to reproduce on my phone. If I lose service or force it to lose service (like turning airplane mode on then back off) it will happen. As far as texting I never really ran into that issue since I use Handcent or ChompSMS
[Hero CDMA Android Development] Etrick:
Is the problem with sprint towers related to the fact that your sending multiple texts too quickly? As in the code detects a message over 160, determines how many msg's necc, splits into x amount of msg's and sends. Then sprints tower craps it out because of rapid firing out messages... like maybe something sprint built in to prevent spamming or etc. Could a delay between each msg going out after breaking up original msg get them to go?

I would assume you would have to sniff packets leaving a sprint stock ruu phone sending a msg and then a custom rom to look for a difference in header. Its plausible sprint is leary of someone modifying a device or a problem, virus, taco, etc manipulating data and its killing the msg because parameters are not right....

I'm not a genius on this stuff obviously... just curious...
[Hero CDMA Android Development] JustRuin:
If the messages are being split, wouldn't that technically mean that each message is being sent individually, and so each would be sent at the speed of an individual message? But maybe the stock rom does create some sort of delay?

But then none of what you said makes much sense for people who don't have the issue (unless every time they send a message, it sends it under Affiliated Network [which seems to work?])

I'm not saying you're wrong lol I'm just wondering too

Maybe I'm not understand correctly?
[Hero CDMA Android Development] SirRipo:
That doesn't seem very likely from my understanding. I mean, with my older phones (like my Blackberry, Instinct, and Rant) it sent them faster than my Hero ever did (even stock). And when you send the messages that way, they tend to arrive with the same timing. There have been times that my phone seems like it never stopped vibrating because it would receive long messages (a 4-piece example just the other day).
[Hero CDMA Android Development] SirRipo:
Any progress guys?
[Hero CDMA Android Development] Cipherblox:
Working on code that detects Voicemail notifications right now. I have a few ideas on some options once I find that particular piece of code.

As for the SMS issues, I am unable to compile CM6 and cannot for the life of me figure out what I have to do to specially compile an APK to get it to work with CM6.

If anyone is running CM6 and is unable to run the current Mms.apk that I posted, I'm going to compile a completely stock AOSP Mms.apk without making any changes myself and see if that makes any difference in whether the APK is accepted or not. I'll post it tomorrow, but would anyone mind testing an Mms.apk that shoulddo nothing but work the same as any other ROM?
[Hero CDMA Android Development] SirRipo:
I'll test it. I'm not doing anything major tomorrow, besides working in the morning. Perhaps tomorrow evening I'll be able to test it.
[Hero CDMA Android Development] BothGunzUP:
I'll test it too. I got a few ideas on how to test it as well. This could answer alot of questions.
[Hero CDMA Android Development] theimpaler747:
Cool, would be great to fix this good luck man :D
[Hero CDMA Android Development] Cipherblox:
Here is the stock Mms.apk

There is literally 0 difference between the code in this APK and the one included in AOSP and CM6.1.

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

Let me know how it goes...

-Kevin
[Hero CDMA Android Development] SirRipo:
Just waiting for my battery to get above 50% and then I'll give it a shot.

EDIT: Just gave it a shot, with my network set to both "home only" and "automatic". Neither one would send. Still works under "affiliated networks" though. Maybe it's got something to do with like the way the phone registers with the network? Like maybe there's some difference between CM6/AOSP and the Sense-based ROMs in the way they access the network to send the messages?
[Hero CDMA Android Development] 151jcolon:
last night i went to sense rom. sense rom sent sms good
[Hero CDMA Android Development] Cipherblox:
It didn't send a <160 character message at all?

The only point of that Mms.apk was to make sure that CM6.1 and AOSP could in fact recognize my compiled version instead of removing the Message icons and everything completely.

If it doesn't send anything at all, then there are unrelated problems.

Sense ROM's use a custom message program. While they all eventually come back to this Mms.apk and the code I modified to send things, they fix things prior to it getting there.

-Kevin
[Hero CDMA Android Development] 151jcolon:
im trying to install your apk but say problem parsing .....
[Hero CDMA Android Development] Cipherblox:
You do not install this .APK. This is a system apk. You simply push it to your /system/app directory on your phone to replace your current Mms.apk.
[Hero CDMA Android Development] 151jcolon:
i tried both, when i pushed the apk, the mms icon disappears
[Hero CDMA Android Development] Cipherblox:
Yea thats what I was checking for there.

That means that CM6 is not accepting modifications to system apks in some way shape or form. That is the same Mms.apk that is supplied with CM6.1, it was simply compiled by me and not the CM team.

There must be some sort of a flag that CM6 is expecting - unfortunately, not CM6 developers will get back to me and let me know what they want done for CM6 to read my APK's.

I'm not sure I can solve this problem - this seems like an issue with CM.

-Kevin
[Hero CDMA Android Development] tubazeppelin:
Is this native in AOSP's rom yet or will I still have to push it once I flash the ROM? I'd like to do give it a shot while I'm at work today but I don't have SDK installed on my work computer.

Running CM6 now...not splitting the sms's is pretty much my only problem with it and the only thing keeping me from being truly happy:rolleyes:
[Hero CDMA Android Development] Cipherblox:
AOSP was compiling and testing it with his code, so you would have to ask him.

As of right now CyanogenMod refuses to use anyone else's System APKs. I've been asking around on the CM forums but nobody will respond to my requests...
[Hero CDMA Android Development] tubazeppelin:
So weird. You'd think they'd be happy to have this fixed. Perhaps this is only an issue on the Hero? Or does no CDMA phone running CM6 split its messages?
[Hero CDMA Android Development] Cipherblox:
Yea, I'm not sure why nobody will respond. They may just not know, but it would be nice for someone to at least try and help....

No one who builds from the stock AOSP should be able to send messages >160. There have been reports about Roaming towers somehow handling it, but I think it is most probably a theme or mod that is sticking around and handling the case because, like I said, I looked over the entire Mms subdirectory, and there isn't anything that handles it....

-Kevin
[Hero CDMA Android Development] JusticeAA:
If this is the case then how are people theming CM6?
[Hero CDMA Android Development] theimpaler747:
Theming is us using CM apks, not CM using out apks ;)
[Touch Pro2, Tilt 2 Android Development] ztag100:
i installed the build of froyo reference from ... and all was going well until i met the problem of not being able to connect to my network.... it sees my network... and after i enter my wep key... it says connecting... then it says disconnected.:confused: can anyone help?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
We already talked about this, WEP isn't supported.

Although you said something interesting on IRC - that it worked on your RAPH...? Is that true, WEP works for the RAPH but not RHOD? I guess it's not a huge deal as anyone using WEP needs to change it anyways...
[Nexus One General] AbsoluteDesignz:
by the COMPLETE lack of info from Google itself regarding Gingerbread?
[Nexus One General] evilkorn:
No

10char
[Nexus One General] elmejor183:
yes, this time it seems they were very tight since nothing has leaked out. a couple of pictures here and there but thats all.
[Nexus One General] galaxys:
It's kinda secrative and exciting all at the same time! :D
[Nexus One General] gravufo:
Heh, seriously, who cares? They don't HAVE to....the less info leaks, the more of a surprise effect it will have, meaning more publicity, public enjoyment (if it was well done) and so on...

I honestly don't care since I enjoy my Nexus every minute I use it! It still would be nice to get Gingerbread this week since it will bring new things, new fun, new everything :D
[Nexus One General] AbsoluteDesignz:
you're luck you got 39 more posts than me or I'd rip you a new one for your short concise and detailed at the same time comment

lol
[Nexus One General] AbsoluteDesignz:
I purposely said slightly annoyed to differentiate from the idea that I'm frothing at the mouth smacking my computer screen.
[Nexus One General] crachel:
lets just say I'm pretty ticked off
[Nexus One General] evilkorn:
I thought your spam was concise and detailed enough so that it didn't warrant a concise and detailed response as to why Google is being tight lipped about their upcoming intellectual property release.
[Nexus One General] gibosn6594:
I think they were somewhat revealing at the I/O.
[Nexus One General] AndroidPerson:
Whenever I start longing for gingerbread I just thank God I don't have a Samsung vibrant, they're still waiting for froyo which was supposed to come like a month ago. I'm just happy to have a Samsung so I avoid Samsung's proverbial "jerk around". By the time they get froyo we will he knee deep in gingerbread. Poor bastards
[Nexus One General] AbsoluteDesignz:
imagine having the X10...
[Nexus One General] Quelltextfabrik:
Android is supposed to be

open

. At least that is what I heard.

Also, developers might find information regarding future releases and resulting API changes useful, ahead of time.
[Nexus One General] JHaste:
quick someone leave their n2 with 2.3 installed on their dinner table and walk off casually so some bloke can pick it up and hook the rest of us up! :P
[Nexus One General] Bronyr:
Google wants to know everything about everyone, but they hold their cards close to the chest.

www.google-watch.org

-------------------------------------

Sent via the XDA Tapatalk App
[Nexus One General] mrbkkt1:
I'm thinking the opposite. Maybe its real minor and unnoticable. This way we can't all ***** and moan before its released.
[Nexus One General] mrbkkt1:
I was thinking that the X10 is like having a beautiful brand new computer running windows 3.1.
[Nexus One General] AbsoluteDesignz:
lol, word..
[Nexus One General] cappysw10:
^^^this^^^

Swyping...please read slowly!
[Nexus One General] diversificationied:
Open doesn't mean spread eagle.
[Android Software/Hacking General [Developers Only]] Android Approved:
funny movie, makes fun of Apple and Steve Jobs

http://androidapproved.com/item/lg-optimus-one-the-mini-movie/

[YOUTUBE]http://www.youtube.com/v/5tV_faLS4uY[/YOUTUBE]
[Android Software/Hacking General [Developers Only]] dryhte:
Funny! I laughed.
[Android Software/Hacking General [Developers Only]] freakfingers12:
Haha, saw this couple days ago. Love that clip! Awesome advertising. :)
[Sony Ericsson XPERIA X10 Mini] bimasakti85:
Is there anyone know how to set up adhoc connection in 2.1?
[Sony Ericsson XPERIA X10 Mini] okristian1:
I use barnacle from market. Needs root.
[Sony Ericsson XPERIA X10 Mini] bimasakti85:
Barnacle si different with adhoc.
[Galaxy S I9000 Q&A, Help & Troubleshooting] source.rar:
Hi,

I just got my Samsung Galaxy S a few days back and installed Kies on my Windows Vista PC (32 bit) last night. It asked for an update as soon as I started it for the first time and I did so.

When I tried connecting my phone to the PC USB, it asked for the connection mode and I chose "Samsung Kies", right after this I see the Galaxy S flickering between the MTP application connection screen and the home screen. This goes on indefinitely and I need to pull out the cable to stop this.

This is really frustrating. Is this a problem with my phone (USB port damaged) or some other problem? If anyone else here is facing this and has resolved it please let me know how.

TIA
[Galaxy S I9000 Q&A, Help & Troubleshooting] Machtkampf:
Put your phone in mass storage mode, connect it to your PC so that you can browse the internal storage and delete any files that have extensions longer than 16 characters. This is the reason why MTP is crashing over and over. If you do a search for it, its a common problem. I think there is even an app that someone wrote to scan your internal SD and automatically remove these files.
[Galaxy S I9000 Q&A, Help & Troubleshooting] DaveJeep:
Know the name of the app?
[Galaxy S I9000 Q&A, Help & Troubleshooting] abhishek.vij:
Here is the app.
[Galaxy S I9000 Q&A, Help & Troubleshooting] cydiamante:
Had the same problem a while back and this fixed it :)
[Galaxy S I9000 Q&A, Help & Troubleshooting] source.rar:
Thanks for all the help.

Remvoed Dolphin HD (the one that had 16+ chars extensions) and was able to connect with Kies.
[Galaxy S I9000 Q&A, Help & Troubleshooting] _dsk_:
Ive had this problem when trying to install KIES last night, going to give this a go as i want to upgrade to some FroYo goodness! :)
[Windows Phone 7 General] DaveyBoy72:
After finally getting music onto my HD7 (long story), here are my thoughts on what is turning into a nightmare handset for me.

1. Set up - First of all, the Connector for Mac software will only access iTunes libraries on a local computer, so if like me you have your media stored on a NAS, you're in the sticky stuff. This also goes for USB sticks and external HDDs.

2. Zune - After finally getting some music on to the phone, I checked out the Zune player component. Coming from an i-device, it took a while to find my way around it, but on the whole, it's quite a nice interface. One thing I don't like is when browsing by artist, instead of giving you the albums to pick, it just jumps straight into playing all songs by the artist. Not a big deal, but slightly annoying.

*EDIT* Actually, scrap that last comment. Double tapping on the artist brings up the artist's albums. Excellent!

3. Sound quality - I use some high quality Denon 'buds and have to say, the sound quality is so much better than my iPhone. It's also very loud. Unfortunately, you do get some background hiss when you're flicking between the icons and have no music playing. There was also some feedback as mentioned below in point 4, but when NOT on a call.

4. Call quality - I found this to be pretty decent, UNLESS you're using headphones. You know that feedback ditt-ditty-ditt noise you get when you put a cellphone next to a radio? Well I got that constantly when on a call. Not sure if this is a fault with my phone itself or whether they're all like this. Either way, it's not a good advert for HTC.

5. The screen - After reading about the 'screen tearing' and wondering what it was all about, I now have first hand experience of it. The handset is only 1 day old, so I'm not exactly happy. Does anyone know if this is a hardware of software fault? Have the Mozart or Omnia 7 had the same problem?

6. No gapless playback - A big one for me is this. I've got 200 or so live/dj mix albums, so not having this feature has pretty much made this phone worthless to me. I just don't understand why MS haven't implemented it. If there are no plans to add this, then my HD7 will have to be returned.

Right, that's my take on the HD7. Admittedly, it's not exactly positive, but I have been honest and hope that it will give prospective buyers something to think about.

If I'd have known about some of these things in advance, I would have given the WP7 format a wide berth. This is a shame, as the UI is excellent and there are so many good things about it.