yashsingh1/xdaforums huggingface dataset:
[Droid Incredible Q&A, Help & Troubleshooting] GrimeSyndicate:
the actual problem defined...

Well that is interesting. Now that you mention it, it makes perfect sense and I am unable, in hindsight, to see how this didn't dawn on me initially. Obviously, in CM10.1, the splitting of the texts happens automatically w/out the presence of a checkbox-able option. At least, that's what happens in theory. I think that there's a small chance that because the meter in the new messaging app wasn't showing up until later I wasn't noticing it's presence as it neared the end of the 145 limit. But I have messed with it pretty extensively, so I think that it IS behaving erratically but it's chosen not to act up right now. Either way though, there is something amiss. As I say, the meter seems to be showing up just fine around the ten characters left mark right now, but I see that even when it's showing the denominator numeral /2 or /3 etc, it never splits the text message. The messaging app disregards the meter completely and sends a single block of text, always. So I guess that's the meat of the issue: how to get the messaging app to heed the meter's instruction? (or whatever goes on behind the scenes to have that perceived effect.) And/or, get the meter to show up reliably. But if it split the text automatically, I could care less about the meter.

I hope that now that we've gotten down to the crux of the problem that there are some troubleshooting steps to take n whatnot. I can say with confidence that it's never split a text on it's own, without my intervention and manual splitting. And I've been on this Rom for two updates now, the first that I flashed was the 03/09 Rom. Each time until the last, I'd done the full data wipe/factory restore, cache wipe and Dalvik wipe, then freshly flashed the Rom, gapps, the flashable keyboard and offline vc files. (though I've yet to see the voice control function work without an internet connection of one kind or another) This last 3-22 update though, I just flashed the Rom over everything else, and there seems to have been no bad effects from not wiping everything first. But throughout, messaging has has never changed a bit.
[Droid Incredible Q&A, Help & Troubleshooting] kramer56:
do you get charged differently either way. I have sent the wife a few page text to check this issue out and it does indeed come in as sms not mms. Mine says its split but in her receipt of it it shows up as one just like as it does on my phone after I hit send. Does not at all affect me and my texts tho.
[Droid Incredible Q&A, Help & Troubleshooting] GrimeSyndicate:
Charges aren't the concern, the text will not go through after a certain character count (i thought w/cricket it was 160, but maybe it varies handset to handset?) and kicks back an "unable to send" notification after hanging for 20 seconds. Consistently.
[Droid Incredible Q&A, Help & Troubleshooting] tiny4579:
I think you helped here. It seems the issue is that Cricket doesn't split messages over 160. The reason people have not reported an issue is that I believe Verizon does the splitting on the network end.

Here is the thread about it in CM7 though the change referenced was abandoned, the code should still work:

http://xdaforums.com/showthread.php?t=962405

Below is the merged change to CM7:

http://review.cyanogenmod.org/#/c/3316/

The interesting thing is when checking this out to implement, it seems redundant as it's already implemented. The only thing I'd be able to do is determine if it's toggled. Let me see what can be done.
[Droid Incredible Q&A, Help & Troubleshooting] tiny4579:
Hmm, leads to a non-buildable ROM. I'm not sure how much time is needing to add this feature in. It also seems you're the first to comment on this splitting issue. I don't think it's an issue on the VZW network or most people don't split. Either way, I'm unable to grant your request at the moment. I will investigate a bit more still. Either way, CM definitely should have MMS splitting but I wonder if the detection is different as the code is definitely there to split. It used to be checkbox related but it seems that they have changed it. It defaults to being disabled.

Ok, good news, I think I can have this enabled for you. It shouldn't be too hard. I just hope it doesn't break splitting for anyone else. It shouldn't cause any issues but for now I'm going to post the Mms.apk once I build it.
[Droid Incredible Q&A, Help & Troubleshooting] tiny4579:
Here is an updated Mms.apk. Just push it to /system/app either in recovery or ROM and then set permissions (644 or rw-r--r-- or otherwise read-write for user and read for group and others). Then reboot into the ROM.

Mms.apk - 2.91 MB
[Droid Incredible Q&A, Help & Troubleshooting] GrimeSyndicate:
hmm

I tried using astro file manager es file explorer to copy that apk file to /system/app, but it gives me a copy error and an offer to rename (but I'm not sure, is it having me rename the file that's already in system/app? or the one I'm trying to move there?) If it's just renaming the existing one, awesome, cuz I'd name it .bak and keep it in case this doesn't work, but I don't wanna proceed w/out some direction. And I don't see r/w mount options, nor do I see permissions settings. So, what to do gentlemen? And which prog is best to use. Just pick one and instruct w/ file manager of preference between those i have or can get (preferably) for free.

Got it copied, dunno what the deal was the first couple tries. But Astro isn't giving me any obvious place to mess w/ permissions. And now I figured out I just needed a different explorer, got root browser lite and I should be good, thanks for abiding my newbness

---------- Post added at 03:48 PM ---------- Previous post was at 02:59 PM ----------

K, i did everything as asked, rebooted, and had the same exact issue occur. I've resorted to "Handcent" at the moment, but it's an option I'm taking ever-so-begrudgingly. As I feared, it's a bit more laggy than the stock messaging app, and I'm not a fan of it's bubble-based layout. It has an android mimicking option, but looks only marginally like the stock sms/mms messaging app. The original is the bee's, I hope you can find a workaround. I've got faith you'll work it out though...
[Droid Incredible Q&A, Help & Troubleshooting] tiny4579:
Seems like the mms.apk is configured correctly. Not sure what to tell you. Will try one more thing. Was it trying to send an SMS or MMS?
[Droid Incredible Q&A, Help & Troubleshooting] GrimeSyndicate:
Well, I tapped out a text that left the meter saying 112/2, hit send any it goes up to the conversation section as a single message, hangs at the "sending..." dialog, then eventually I get a "message not sent" notification and a little exclamation in an upside down triangle appears below the message where it'd usually say sent and the time-stamp
[Droid Incredible Q&A, Help & Troubleshooting] tiny4579:
Let me know how this one goes. As far as tweaking the mms config, this is about all that I can think of at the moment. I had originally thought that feature was missing and that CM just changed it. I hate to divert from CM's too much so if this fails, maybe there's one other thing but it wouldn't be mainstream unless it doesn't affect other users.

Mms.apk - 2.91 MB
[Droid Incredible Q&A, Help & Troubleshooting] kramer56:
Tap that message and resend it does it go then? Mine does that when I send when another one is incoming at the same time. I just resend it.
[Droid Incredible Q&A, Help & Troubleshooting] tiny4579:
His issue is specific to any messages that are too large to send as one message. I don't think his network splits them automatically like Verizon. Default feature is to let the network split up the sms messages which I don't think Cricket does.

@GrimeSyndicate, You can try pulling mms.apk from CM7 but I'd do a nandroid backup before pushing it to your phone in case something funky happens as they are for different android versions.
[Droid Incredible Q&A, Help & Troubleshooting] GrimeSyndicate:
It worked! The second MMS.apk did the trick. However, it may have worked with the first 1 if I had installed it after placing it in the system/app folder like i had to do with this one. Anyways, after installing from system/app, I fixed permissions and all was well. My confidence in your skills was well placed!

King among men!
[Droid Incredible Q&A, Help & Troubleshooting] tiny4579:
Great ! Can you do me a favor and try with the first one again making sure the apk is installed in system/app?
[Droid Incredible Q&A, Help & Troubleshooting] GrimeSyndicate:
Yeeeeeee

I don't know if I was, in fact, supposed to actually select the mms.apk and install it after moving it to the system/app folder, but I tried it on a whim. I didn't see it in any of the directions I looked up on this forum and around the web, they all merely said to move it to the folder, fix permissions and reboot. Can anyone tell me if installing is the way to go? I mean, it worked, but am I doing something that's dangerous in any way? Also, do you need me to go back and check whether the first mms app you presented works as well? Or is that unnecessary since you're not including it in the builds globally going forward anyways?

Anyways, I'm stoked, thanks for handling that untidy affair.

---------- Post added at 02:13 AM ---------- Previous post was at 02:08 AM ----------

Ohhhh, ha! I started typing this up, then passed out on my keyboard, woke up and finished it. Only to discover that in the meantime you'd asked me to do just that!
[Droid Incredible Q&A, Help & Troubleshooting] tiny4579:
Test it as is. No need to install to system/app. Just copy and fix permissions. I'd like the original fixed apk tested. I may include it in builds. Can a vzw user test it and make sure split SMS works fine?
[Droid Incredible Q&A, Help & Troubleshooting] GrimeSyndicate:
Alright, tested MMS.apk build #1, and we're in business. Build 1 appears to be functional as well, so you can have Verizon users check it for issues and pat yourself on the back, cuz you've made my week.

---------- Post added at 01:02 PM ---------- Previous post was at 12:43 PM ----------

I forgot to ask, do you know why offline voice dictation isn't working? It never has, and I've flashed it every time I've updated your rom. Ideas?
[Droid Incredible Q&A, Help & Troubleshooting] tiny4579:
All shall be revealed in my mystical OPs. Im sneaky in that I have two of them. Check them out. Also, can a verizon user test the MMS.apk and ensure SMS and split functionality still work for them. I need to have the first MMS and not.the second one.
[Droid Incredible Q&A, Help & Troubleshooting] omniatic:
Just replaced the original MMS with the first one you posted. No problems with it, splits the message fine. Sent it to my Google Voice number, came through as two.

From my Incredible
[Droid Incredible Q&A, Help & Troubleshooting] Kaepernick:
Is it possible for a theme to consume more ram than other themes and stock? Was using PCB Blue and I generally had around 110 to 120mb of free ram left (including the 33 or so MB Settings takes up when I look at it). Using CyanOrangen Cobalt and I usually have around 80 to 90 left. Just want to know if it's the theme or something else.
[Droid Incredible Q&A, Help & Troubleshooting] musical_chairs:
No lag, that's why I use it. I prefer the layout of the stock keyboard, but I can type (or swipe) a lot faster with touchpal. Its text prediction drives me crazy sometimes though.

It doesn't work because you run out of space while flashing the offline files. Make room first, and it works. But be warned: offline voice dictation on this phone is very slow, (not exactly a quad-core processor here if you know what I mean). You may also need to install Google Search (aka Google Now) from the Play Store to get voice typing, I don't remember if that's currently included by default with the ROM and gapps or not.
[Droid Incredible Q&A, Help & Troubleshooting] Kaepernick:
Pretty sure voice typing is included with the rom. Haven't tried offline voice but online voice works pretty well.
[Droid Incredible Q&A, Help & Troubleshooting] DT@china:
On March 22 for the system version, I do not feel very good, and sometimes a sudden it does not take in the status bar. Seems to be caused by three new files in the bin directory, but are not sure.

The availability of the new version the setting.apk, but not integrated rights management.
[Droid Incredible Q&A, Help & Troubleshooting] musical_chairs:
I believe you're right, it's part of QuickSearchBox.apk, which I deleted and replaced with Google Search from the Play Store to make more room for the offline files.

I found that clearing data for SystemUI.apk (I used Titanium Backup to do this) fixed the problem with the status bar freezing.
[Droid Incredible Q&A, Help & Troubleshooting] DT@china:
The problem may be the three files in the 22nd version of the system \ bin directory mdnsd, debuggerd, recovery
[Droid Incredible Q&A, Help & Troubleshooting] tiny4579:
I disagree. Do you have any evidence they changed? This issue which I've never seen has occurred in several builds but just for a few users.
[Droid Incredible Q&A, Help & Troubleshooting] DT@china:
Beyond Compare software, you can find the March 22 version of the system \ bin directory recovery changed.
[Droid Incredible Q&A, Help & Troubleshooting] tiny4579:
Fair enough. Do you have any evidence these files are related to the issue.

I don't believe they are as the issue was reported prior to the 3/22 build. It could be a lack of system resources though.
[Droid Incredible Q&A, Help & Troubleshooting] DT@china:
I used 3/09 and their modified rom, replace some of the new file. Same status bar appears to be frozen.

I restore the files in the bin directory that does not currently a problem, I do not have enough time to prove. So I said it might be in this place
[Droid Incredible Q&A, Help & Troubleshooting] Zero_FeniX:
Whenever I leave wi-fi on, after maybe 5 minutes or so of inactivity, my data transfer is non-existant. What I mean by this is that the wifi symbol shows upload arrows but the color is grey, as if it's lost connection to google, but any app that requires some sort of data transfer never appears to receive anything. I can alleviate it by turning wifi off or switching in and out of airplane mode but I haven't found anything to prevent it. Any suggestions?

I'm using 20130315 version of 10.1. This also occurred with the most recent build of CM10.0 that you did.

Apologies if this is already noted, but I couldn't find anything in this thread or on this forum.
[Droid Incredible Q&A, Help & Troubleshooting] tiny4579:
I have had this issue before on my Galaxy Nexus. I think it's related to the broadcom wifi drivers we are using here but nothing to prove it and it may not be the case. Anyway as far as preventing it, try changing the screen off policy from always to never and back (it just needs a toggle to a different screen off policy and back) then reboot. I heard this on a different thread so I'm not making up this solution. If you do this, you should be good until the next time you toggle wifi off and on again then the bug may settle in. Sorry I don't have any better suggestions.
[Droid Incredible Q&A, Help & Troubleshooting] Zero_FeniX:
I did what you suggested and it appears to be working. Thank you very much, I finally get to have Wi-Fi on again XD

It appears that when it would sleep, wi-fi wouldn't get fully suspended and data would take over. Instead wi-fi would mostly shut down but still remain the effective method of data transfer, thereby blocking all data transmissions since it was actually shut off. But I could also be completely wrong.

Thanks for your work with CM10.1 it breathes new life into my 3 year old incredible since I can't find anything worth upgrading to on big red.
[Droid Incredible Q&A, Help & Troubleshooting] tiny4579:
For upgrades? Not the Galaxy Nexus or DNA or the HTC One if they get it. All of them are pretty substantial upgrades.

I may try integrating the 3.4 drivers into this kernel. It seems to be pretty popular on my Galaxy Nexus kernel but does break WEP.
[Droid Incredible Q&A, Help & Troubleshooting] tydiamond11:
The newer kernel would be so cool!
[Droid Incredible Q&A, Help & Troubleshooting] tiny4579:
I'm done Androiding for the night (Yes, new word). Either way, the way it works in my Galaxy Nexus breaks wifi on the Droid Incredible. So as it is now I can't use the new wifi drivers. I'm pushing a new build with the status bar fixes and the AOSP keyboard with gesture typing. Recommended when it's built and uploaded is to wipe system and then flash the latest build and the 3/28 gapps which I'll link after the ROM is up. This is to ensure that the old latinime files don't get copied over. It should work to flash the new gapps before the ROM so it will back up with the correct backup script.
[Droid Incredible Q&A, Help & Troubleshooting] tydiamond11:
For me the newer kernel bracking wep WiFi that would be OK if people need it then they could download an older build just saying thank u for all this!
[Droid Incredible Q&A, Help & Troubleshooting] tiny4579:
I'm not sure you fully understood. The kernel with the new drivers breaks wifi completely as in no wifi at all. It should only break WEP but as it is now wifi won't even start up. New build coming shortly. I'll annouce it on the dev page.
[Droid Incredible Q&A, Help & Troubleshooting] dag1337:
Just wondering if anyone knows how to turn off the lights on the capacitive keys? I can't figure out how to do this...
[Droid Incredible Q&A, Help & Troubleshooting] GrimeSyndicate:
I was just wondering if you know of an easy way to enter diag mode on this ROM. So far, I've tried everything I could find scouring this and other forums msg boards including the gscripts fix, another script-based fix, messing with drivers, etc.... I don't know what to do. Short of flashing some stock ROM, which I don't want to have to do and don't really know which one to flash to ensure it'd work, I'm up the proverbial creek. ##3234# is what I'm going for here, with no luck at all. Somebody save me, yeah?
[Droid Incredible Q&A, Help & Troubleshooting] tiny4579:
Aside from a framework edit, there isn't a way.

No, I'm quite certain the only way is to use a stock or stock based ROM.
[Droid Incredible Q&A, Help & Troubleshooting] Kaepernick:
You need the stock rom. And not just the stock rom. You may need the stock recovery too so you can do a factory reset within that recovery for it to work (I had to).
[Droid Incredible Q&A, Help & Troubleshooting] tiny4579:
That is not true about recovery. When I used epst a couple hears ago I was on a custom sense ROM with clockworkmod. If that's the diag mode he means, it just needs the sense framework with an epst.apk.
[Droid Incredible Q&A, Help & Troubleshooting] Kaepernick:
Was true for me. I tried the stock rom that cmlusco posted and it simply wouldn't work. Tried the ##778# method. It was only when I switched to stock recovery and did a factory reset within that recovery, did it work.

http://xdaforums.com/showthread.php?t=2141642&page=4
[Droid Incredible Q&A, Help & Troubleshooting] GrimeSyndicate:
I ended up flashing the "A touch of Blue 3.0" rom and went from there. It worked like a charm, and I was able to pull the MIN and the .prl file off the phone that I was hoping for. Great success, High five!
[Droid Incredible Q&A, Help & Troubleshooting] elmedex:
Does anyone know what happened with the welcome menu? I like to use the first time i boot since it restore my backups setting in my google account
[Droid Incredible Q&A, Help & Troubleshooting] tiny4579:
It only shows up on a clean install.
[Droid Incredible Q&A, Help & Troubleshooting] elmedex:
I full wipe before installing didn't show up I even did a factory reset, this is with 3/22 and 3/30 before that i used to get the welcome screen every new rom flash i returned to 3/9
[Droid Incredible Q&A, Help & Troubleshooting] tiny4579:
If you wiped system before the ROM did you remember to flash gapps?
[Droid Incredible Q&A, Help & Troubleshooting] elmedex:
I did the following:

Wipe data

Wipe cache

Wipe dalvic

(All this twice)

Install 3/30

Flash gapps 3/01

When first boot nothing appeared so factory reset from the backup nothing either so did the same process to flash 3/09

Welcome menu appeared
[Droid Incredible Q&A, Help & Troubleshooting] tiny4579:
You need to use the gapps I specifically linked in my development thread. The gapps may not full install if you're using the official ones. And as stated in my op you can dirty flash cm builds. No need to wipe each time.
[Droid Incredible Q&A, Help & Troubleshooting] Pons:
Well, don't see a mention of...

If you're doing a clean install, all the extra steps is probably messing you up. Try just factory reset (once), wipe system (once), then flash the ROM, flash gapps. As simple as that.
[Droid Incredible Q&A, Help & Troubleshooting] elmedex:
im pretty sure I did, gapps-jb-20130301-signed.zip for 3/22 and gapps-jb42-20130328-TINY-signed.zip for 3/30

Gonna try again doing a clean install as pons mention

As i mentioned originally before 3/09 i had never had this issue
[Droid Incredible Q&A, Help & Troubleshooting] elmedex:
I just try a new clean install to doublecheck I wasn;t doing anything wrong

I tried with 3/30 and gapps-jb42-20130328-TINY-signed.zip

new downloads both, and I didn;t receive the Welcome Screen at the firs boot.

So I'm back again on 3/09, I know in the end I could just stay with 3/30 add my gogle account and download apps one by one

but I like my google backup because it not only downloads all my app but also recover my wifi password which are a lot.

Here in my country for google play paid apps I need a credit card which I don;t have so I cannot have titanium pro to restore all that stuff, so I just stick to the google backup.

If you guys do a clean install on 3/30 actually receive the Welcome Menu?
[Droid Incredible Q&A, Help & Troubleshooting] Zero_FeniX:
I was wondering if USB tethering is working for anyone?

Whenever I try to enable it, either through settings or the notifications widget menus, I get a message saying "Unfortunately, System UI has stopped." or "Unfortunately, Settings has stopped." I don't use the tethering much so when I've needed it I just turn on Wi-Fi but it would be nice to have USB since it doesn't drain the battery as fast.

I've seen other posts suggesting it doesn't work but haven't found any that present a solution to the problem.
[Droid Incredible Q&A, Help & Troubleshooting] tiny4579:
Try Bluetooth tethering. It's lighter on battery than Wi-Fi. I don't think USB tethering works on this ROM or any JB inc ROM. It may be something that can be fixed on the kernel side. A logcat would help as I can't test just yet.
[Droid Incredible Q&A, Help & Troubleshooting] omniatic:
Here's one of those "If a tree falls in the woods..." questions.

During a call, when the screen times out, does the phone sleep?

While doing something on the phone, a call comes in. After a bit, the screen goes off. Shortly after that, the call goes dead, and I get a soft reboot. Only happens when I'm on WiFi, which is set to turn off when sleeping. Also, only when I have the screen on when the call comes in. I've seen the lag time between WiFi going off and 3g coming on, but should it affect the phone signal, too?

For now, I'll set the WiFi so it's always on, and see if it makes any difference. Hope that isn't too tough on battery life.

Any thoughts?

From my Incredible
[Droid Incredible Q&A, Help & Troubleshooting] tiny4579:
No the phone doesn't sleep during a call. The call would keep the phone awake. Not sure why you're getting a soft boot. Logcat would help. Try to get one after the reboot. Hopefully it won't die from a soft boot.

WiFi shouldn't hurt battery. It actually may help a tad as it should use less battery to background sync than data and data isn't used with WiFi on.
[Droid Incredible Q&A, Help & Troubleshooting] omniatic:
I'll see if I can get it to happen again when I'm home. And get a logcat.

Going to check out a Gnex at Verizon...maybe time for an upgrade.

Thanks,

From my Incredible