yashsingh1/xdaforums huggingface dataset:
[Epic 4G General] TNTRMSKD:
I noticed this back since the dk28 leak. I've only ever been able to reproduce it by using lvl 2 ram kill. I think some people here might be jumping the gun when they say it happens outside using ram clear. Sometimes whe your signal is weak it will stay on. 'Sending' for up to a few mins. I've actually monitored this in a weak signal area (my basement). However, once the signal strength returns the timestamp will pop up and the txt will send. I've had to wait as much as 2-3 mins in a weak/dead zone to see the timestamp. But when I use lvl 2 ram kill, I can be in a full signal area with max bars and wait until I'm blue in the face and the timestamp will never show up (ie. The msg never gets sent).
[Epic 4G General] Dvin211:
I wanted to report back with my results. I haven't used the lvl 2 ram clear in 2 days. So far all of my text messages have went through with no problem.

I'll let you guys know if I have the issue again. Thanks for the help.
[Epic 4G General] bertroid:
I've never had this problem ever on any Roms, custom or stock.... until yesterday. It just so happens that for the first time ever I cleared level 1 and 2 RAM. I never knew that functionality existed so when I found it, I thought "I'm going to clear my RAM". Sure enough a little while later I had several failed text messages that I could only fix with a reboot.

I then came to the forums today and found this thread. Sounds to me that the initial root cause of the problem is clearing the Level 2 RAM.
[Epic 4G General] bgaimur:
I had ISI just now and these instructions worked perfectly. I wasn't able to get the "stuck" messages to go, but I am now able to send them without rebooting the phone. Any way we could have this fixed, other than refraining from clearly level 2?
[Epic 4G General] Whosdaman:
So far I haven't been able to reproduce it at all. I'm sad now...
[Epic 4G General] The Root:
That clears your experience. Now you guys will never level up.
[Epic 4G General] Dameon87:
I've noticed this happen in random situations, but the circumstances are always the same.

The phone has no signal, or is switching from/to roaming.

My guess is that its related to samsungs hacky ass RIL.
[Epic 4G General] XtaC318:
I'm having an issue, where my phone will tell me the text message failed, but apparently it doesn't fail at all and sends anyways?

I can't have this thing crying wolf at me each time it thinks it fails, any ideas as to how to pinpoint the issue?
[Epic 4G General] CapsLockKey:
I've had this happen to me twice. The one time though I'm pretty positive it happened because I was sending the text at the same time I was getting an incoming call. I kept trying to resend several times. Then my wife calls a couple minutes later and said she was trying to call me but my phone never rang.
[Epic 4G General] mkasick:
If I could find a cause for the immediate problem (the race condition enabled by the task kill) I'd gladly patch it. Unfortunately I couldn't trace it to a "simple bug", and I'm not convinced that it's the result of one either. While a fix for that issue might be possible, it's likely to be quite involved and take some time.

I did identify a potential workaround that might alleviate the problem. But I'm not familar with the detailed behavior of the ServiceManager, and I can't say that the workaround would even work, or that it wouldn't introduce a subtle side-effect that would cause its own problems and be difficult to diagnose. So I'm hesitant to pursue it any further.

Since at this point, it seems that this particular cause of the SMS sending issue only happens as a result of a level 2 task kill, the simplest and for now, best solution is to refrain from doing them.

I believe that once dispatched, the radio has to acknowledge the success or failure to send an SMS. If the radio/ril drops the message, which I imagine could easily happen when switching modes, then the message will "send" forever until manually cleared.

If you can grab a logcat immediately after an SMS fails to send, post or PM it once you've confirmed it actually did send and we can take a look. The aLogcat app is probably useful here to grab it when it happens at a time when adb is inconvenient or impossible to use.
[Epic 4G General] Whosdaman:
You will have the best experience with their RIL due to working on CM7.
[Epic 4G General] theimpaler747:
Hmm, good to see I was correct.
[Epic 4G General] murso74:
this just started happening to me out of no where. i have no idea what's goign through and what's not. reboot and airplane toggle isnt helping
[Epic 4G General] XtaC318:
I'll do that for the next time it happens. :)
[Epic 4G General] The Root:
This actually plagued me on Eclair. My wife say to stop sending the same message multiple times after a fail. The only fails I've had on EC05 have been due to sending from elevators, stairwells and the basement of my apartment building from circa 1920. Though, they seem to make it through later without resend.
[Epic 4G General] fromchaos0646:
this has happened to me ever since i upgraded to 2.0. but when I odind eb13, the failed or continuous sending had ceased quite a bit. but lately I've noticed it a bit more. when it happens, I usually reboot the phone, kill all tasks (stage 2), then turn on airplane mode, kll tasks, turn off airplane mode, kill tasks, and then resend the message. if that doesn't work, I repeat but add in updating profile and prl. seems like a lot of work but it usually fixes he issue for me. although, its an uneeded hassle.
[Epic 4G General] murso74:
stopped happening after a few hours last night. wonder if it was a network error
[Epic 4G General] Whosdaman:
You cited the one of the many causes that cause the actual problem. Not the answer I was looking for at all. Like everyone has been saying, it happens completely random too.

Multiple things are causing the actual problem, just not the "RAM lvl 2 Clear" and it still doesn't cause the problem constantly, only 1 out of 10 people say it's been causing the ISI.

Still I think we have nailed the actual problem on the head, it is now how to fix it.
[Epic 4G General] treyxazn:
Gah I was convinced this was a signal issue then my friend told me he got th same picture message from me 8 times >.< lol
[Epic 4G General] Ryoma Echizen:
I had this issue also. I just updated prl and profile, and was good to go. You could also fix permissions, not sure what good that'd do, if any. You could also switch to handcent or something, I've found it really only affects you on the stock messaging app. You could remove the stock app with sdx app removal, its on xda, just google smthing like "sdx stock app removal xda" and you'll prob find the thread.
[Epic 4G General] flyers2114:
Incorrect from what I have read....most have reproduced or had the issue after a level 2 clear...others are posting issues that are definetly network issues...multiple sending, etc....there really is no reason to use the RAM clear at all...I have never nor will I ever need to...Android handles it all on its own with no issue....and also just becaue you cannot reproduce it using level 2 again does not mean it is not the cause....it obviuosly does not corrupt it each and every time...no suprise in that.....bottom line is your question has been asked and answered very early in thread by Impaler...so now its time to either take the advice or move along and continue to be in denial....

Sent from flyers Epic!
[Epic 4G General] intx:
I've read through some of the thread and the only thing I can add is this:

I've only had the ISI once, and that was after the L2 clear.

I've done the L2 clear before and it never caused it, but the only time I had ISI was due to the L2.

A reboot fixed and I haven't touched it since.
[Epic 4G General] zanderman112:
I think that people can keep throwing out their opinions all they want, but we won't know the reason this happens until real evidence is found as to what causes the problem.

Sent from my always stock, EC05 Epic 4G
[Epic 4G General] insanity213:
FWIW heres my experiences with texting issues with the 2 Epics on my account. This is by no means a comprehensive or controlled test, just some anecdotal data that could help people understand the issue.

Scenario 1:

Epic 1: DK28 (Viper) performing several level 2 ram clears per day

Epic 2: EB13 (multiple ROMs including stock) Never performed ram clears

Texts from E1 to E2 would be transmitted multiple times over the course of several hours or days on some occassions. E1 would show the message sent once. Sometimes would go into ISI.

Texts from E2 to E1 would sometimes work fine or would come into E1 hours after sent. Duplicates were never received by E1.

Texts from E1 to other phones on other networks would say they were sent, but never get there. ISI on occassion.

Texts from E2 going off net had no problems.

E2 never had ISI

Scenario 2:

Epic 1: Viper EB13 w/ EB13 modem performing multiple L2 RAM clears per day

Epic 2: Viper EB13 w/ EC05 modem performing multiple L2 RAM clears per day

E1 and E2 - constant ISI issues on network and off network. Duplicate sending issues have not resurfaced.

Scenario 3:

Epic 1: Viper EB13 w/ EB13 modem no L2 RAM clears

Epic 2: Multiple EB13 ROMs including stock w/ EC05 modem no L2 RAM clears

No problems sending or receiving on or off network.

My observations:

L2 Ram clear sucks bawls.

ISI never happened immediately following a L2 RAM clear, usually took an hour or more to occur.

DK28 modem + L2 ram clear causes single message to be sent multiple times.

Not ROM specific
[Epic 4G General] zanderman112:
Thank you! This is the kind of stuff that we need here more often. A nice detailed post. Whoulda thunk. I would hit the thanks, but im on the app.

Sent from my always stock, EC05 Epic 4G
[Epic 4G General] Whosdaman:
yes, but I want everyone to look at all the post in this thread again and think before you speak.
[Epic 4G General] zanderman112:
Makes sense to me.

Sent from my always stock, EC05 Epic 4G
[Epic 4G General] theimpaler747:
Agreed :) Seems like this should have be answered, but some are refusing to let it die.
[Epic 4G General] Whosdaman:
This is the issue. RAM Clearing Lvl 2 is not the issue lmao. There is one thing y'all don't understand, and it to how to comprehend what is exactly going on. RAM Clearing Lvl 2 may cause the problem, but it isn't the issue.

Un-der-stand?

I mean, it's already been confirmed that other things can cause the problem., some users get the issue and they don't even know what RAM clearing is...
[Epic 4G General] troyolson92:
I used to have this problem all the time. For me, using tasker solved it. I use tasker to put phone in airplane mode at work when signal is less than 1. Every half hour I come out of airplane mode to check signal. This is what fixed my problem. Coming out of airplane mode I first turn off airplane, then turn on mobile data. I believe it was the toggling of airplane mode then turning on mobile data that fixed my issues.

I also clear ram from a program called free memory. It is smarter in what it kills.

Anyway, no more issues for me. I think our phone just loose data connection once in awhile. Just my 2 cents hope it helps our goal of solving issues!
[Epic 4G General] murso74:
i;ve never cleared L2 ram and had the issue
[Epic 4G General] Whosdaman:
See the above post Zanderman? That's exactly what I mean
[Epic 4G General] zanderman112:
I dont expect anyone to remember who said everything in a thread, but I was one of the one's to agree with you. :) Lvl 2 *can* cause the problem, but lvl 2 isn't the problem itself. Lvl 2 is just one way that something is getting triggered.

Sent from my always stock, EC05 Epic 4G
[Epic 4G General] dito33:
I know one thing that Sprint is one of the problem.
[Epic 4G General] Whosdaman:
O sorry, it was flyer....not you :(
[Epic 4G General] zanderman112:
Like I said, all is forgiven. No one's perfect, an this thread is kinda big.

Sent from my always stock, EC05 Epic 4G
[Epic 4G General] gtuansdiamm:
i have just read 13 pages and haven't found the answer to the question i have been looking for

How do i fix it?:confused:

after i went from syndicate frozen to aosp 3.0.1 my epic got infected with isi

when i lvl 2 ram clear i get this problem

rebooting fixes it for me but that's a temporary fix

i tried 5 times just to make sure

not to be rude but all ive seen on this in this fourm was a war between whosdaman and theimpaler

is there any one working on a permanent fix
[Epic 4G General] Whosdaman:
There is only one fix and that is to rebooting it. The problem is a little more complex then the developers available can handle. It involves a lot of recoding because Samsung feels they have to rewrite everything themselves.
[Epic 4G General] gtuansdiamm:
thx for clarifying for me

i appreciate the reply

i still wonder why im still planning on buying another samsung phone after my epic
[Epic 4G General] charlie95113:
Havent read no pages but the first

like all you guys i once sufered from the infinite message crap and I was told someone on xda dont remember who to stop doing a LEVEL 2 ram kill process on the stock task killer ....... I had this issue on eb13 & ec05 and since ive stoped the level2 process kill it also stoped the ISI
[Epic 4G General] ungovernable1977:
So WDM, you don't think this is on Sprint's side, not even at all? Both myself and the GF have these issues, the ISI, the duplicates, the inconsistent MMS... shes got an intercept, so maybe it really is Sammy... Id like to find out, as this is getting pretty old... someone should have fixed something by now.
[Epic 4G General] Darkshneider:
Sometimes my txts dont go out and stay "sending" until "message not sent" comes up, thats when I call voicemail and it goes through. Mine is usually because of signal though, so a call to voicmail is kind of a manual push/pull for me.
[Epic 4G General] Anon9mouz:
I had to have sprint reset mine a few times
[Epic 4G General] ungovernable1977:
EDIT: reading way too many threads at once...

Anyways, it appears lvl 2 clearing is a known trigger, so best not to use it, there is a bigger underlying issue that requires logcats from those who run into this without LVL 2 clearing, as it seems that would help mkasick debug it... rebooting is the retroactive fix... if you get this issue, that SHOULD fix it... but best way to avoid it is to use the NO LVL2 condom approach... got it.

I do think signal drop/roam switching is a trigger as well, if I dont have roam control on at home I am constantly switching, and that is where I experience this issue most myself... will try that logcat app mentioned above if i can reproduce it.

Also, re fixing this issue, WDM, got any friends in credit debt that can make a judgement call and grant me another 'line' for an airrave?? Rep told me its noted in my acct to give me one for free, but credit no like me... is there anyone in sprint that can make a judgement call on this one??? you will be my hero forever, even if you can just point me towards who to call...
[General Questions and Answers] The_12oach:
Hello all,

Yes I have searched the forum. It might be me incapable of using the search system but I just can't find out how to get my twitter apps to work.

I am using this rom, which is working perfect except for twitter apps.

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

I did however try the auto timezone trick which seems to work for most people but not for me. I used a variety of timezones including my current one but everytime I get the error of me not being able to log in.

Apps I tried: Twicca, Twitdroid, Twitter for Android, Seesmic, Tweetdeck.
[Optimus One, P500, V General] rivered:
I download a file with name "themes cm7.zip" 17.67mb im using search to find that post again but with no luck. I need instractions how to install it. My english s**** sorry
[Optimus One, P500, V General] lekhwani:
Just unzip. You will find apk files. Install these apk files. Choose theme in theme chooser app.
[G Tablet Q&A, Help & Troubleshooting] njshkb:
I have been reading all the threads for several days. It may be a dumb question. But I am really curious if we can do everything only with stock 1.1 recovery since CWM .8 does not update bootloader and bring potential danger to soft-brick your gTab when future 3991 based builds include the new bootloader from VS. As far as I have found, flashing a ROM or kernel does not necessarily need CWM to do it. But with CWM we can do data wiping, which stock recovery is not able to. Calkulin posted a Format_All.zip file in his thread. It can do a wipe. I guess it works with CWM just like flashing any ROM or update. But I am not sure if I can use stock recovery to flash it to do a data wipe. Or does anyone know a good way to wipe/format data with only stock recovery?

Of course, one can use stock recovery to flash safely while use CWM to wipe the data. It is just because I am lazy and want to stick with stock recovery.:D
[G Tablet Q&A, Help & Troubleshooting] roebeet:
This came up in the Woot! forums as well, and it's my doing (I'll take the hit for it).

This is my suggestion: Use clockworkmod for all your day-to-day stuff (like backups and restores, SD partitioning and data wipes etc.). However, when you flash a firmware, you should look at that firmware, and the dev's post if that exists, to see if a bootloader update is required. In most cases here, that is NOT the case. However, if Viewsonic sticks to their guns and releases a new firmware with a new required bootloader, then the userbase needs to tread lightly as you might get a soft-brick if you're not careful.

I'm concerned about this because their UAT (build 3991) was like this, AND because the Notion Ink Adam (a sister device) is having these issues at this exact moment - their last update had a bootloader update and clockworkmod users were soft-bricking their devices because of it.

In TNT Lite 4.3.x and gADAM 1.3.x+. I added something called a "Recovery Pack". This allows the user to toggle between standard recovery and clockworkmod, as needed. I also create a standalone package if you wanted to add it to a 1.1-based rooted mod. This way, I (and everyone else) can use clockworkmod for day-to-day, but have the ability to toggle back to standard recovery as needed. I think this is a good balance, but users just need to be aware of the issues and when to use each.
[G Tablet Q&A, Help & Troubleshooting] njshkb:
Thanks a lot, Roebeet! for everything you have done for this community. I have saved your "recovery pack".
[G Tablet Q&A, Help & Troubleshooting] vegeetz:
Can Standard Recovery update kernels as well?
[G Tablet Q&A, Help & Troubleshooting] njshkb:
I think so,TMK. Just rename the whatever kernal.zip to "update.zip" and add recovery folder with command file in it and flash .....
[G Tablet Q&A, Help & Troubleshooting] vegeetz:
Seems standard recovery is my best bet if I want to mod a little and keep things as close to original as possible.

Looking to do TNT 4.3.2 with Clemsen v7 tomorrow.
[G Tablet Q&A, Help & Troubleshooting] roebeet:
Check with the developer - if they say "clockworkmod only" then you should follow their instructions, imo. My guess is that they only test with cwm, but that's only a guess.
[G Tablet Q&A, Help & Troubleshooting] njshkb:
I will probably go with Calkulin's 1.1 and clemsen v6. It looks Calkulin's one is the fastesd so far.
[G Tablet Q&A, Help & Troubleshooting] Rumbleweed:
Roebeet

Did a search and found everything but link to the "standalone Recovery Pack). Please provide again.
[G Tablet Q&A, Help & Troubleshooting] K J Rad:
http://xdaforums.com/showthread.php?t=1005080
[Thunderbolt General] sir2545:
Hi guys,

I was just wondering if anyone has had any issues with last.fm and pandora streaming on wifi. Last.fm just tries to play four or five songs and then I get an error. Pandora will stream one song and then stop....I thought maybe it was the network security not allowing it to pass through, but I tried it on my OG and it works fine.

Does this sound like an app issue or phone issue? Anyone have any suggestions?

Edit: I just connected to another wifi network and it works fine...must be the network at my job. Any way I could fix this?
[HD2 General] Erbsenkönig:
Hi,

I've got some major problems with my HD2. First of all, it was running well. Last Saturday, I wanted to update my NAND TyphooN_CM7_v2.5 to TyphooN_CM7_v2.8.1. I opened CWM and made a backup. Afterwards, I installed the 2.8.1 version and after the reboot, I restored the backup(I think that's my mistake).

After that, I checked the build-version - it was still 2.5..

A little confused, I went to buy a BD. I recognized in the car, that the wake up bug happened again and I resetted the phone. Then, it worked fine.

Back at home, I took my phone in order to reinstall the 2.8.1 version. Suddenly, the HD2 only showed a clear white screen. I didn't boot and MAGLDR didn't appear either. So I tried to reinstall MAGLDR - didn't work(sometimes it's the 270 error, then it's the 262..)

What I've done till today:

-Tried to reflash HSPL

-Hardreset

-Tried to flash a tmo original WM Rom via USB(262&270 error)

-Tried to flash a tmo original WM Rom via SD =>No Flash Screen appeared

I'm kinda stuck cause the damn phone won't flash...

The usb connection is functionnable(the HSPL installer recognizes the HSPL version on the phone)

Hope you can help me

Greets

Erbse
[HD2 General] T-Macgnolia:
Did you use s USB Micro SD card reader to copy tbd leoimg.nbh file to your SD card, and are you sure your SD card is formated Fat 32? Also go to your device manager in the control panel of hour computer while your BD2 is connected via USB and in bootloader. Make sure it says HTC USB Sync.
[HD2 General] Erbsenkönig:
Yep - I'm sure about everything you mentioned:)
[HD2 General] Erbsenkönig:
What to do next? The previous owner assured that the phone's got t-mobile de branding..

I guess then it is necessary to use a t-mobile Rom..

I'm quite confident, that it's not completely bricked - I can still enter the bootloader and the hard-reset mode:)

Give me some ideas:D
[HD2 General] T-Macgnolia:
Yes if you want to go back to stock and start over this is a very good idea. If you have the T-Mobile Leo with 1024MB RAM then yes only flash the T-Mobile official ROM to your HD2 as the any other official ROM will either brick your HD2 or the ROM will not function properly. Most of the time they brick a T-Mobile HD2 though as they have radios with x.xx.51.xx with them or a radio like these 2.04.50.xx or 2.05.50.xx. Any of those radio versions will brick a T-Mobile HD2

Also this may or may not help but I suggest it as it might help you out. Go to windowsmobile.com/getstarted and download the latest version of ActiveSync or Windows Mobile Device Center depending on what Windows your computer uses. The lateast releases have updated USB drivers and sometimes this is the problem when people are having issues flashing via USB.

You also had said you have tried the stock ROM already so you probably do not have HSPL anymore unless you got HSPL to reflash. So you will either have to flash a stock ROM or flash HSPL again so you can flash a custom ROM.
[HD2 General] Erbsenkönig:
As far as I know, it's the 512 MB Version - a friend of mine made me check it the first day I got it:D

Already done:)

The bootloader still says

PB81100 HX-BC

SPL-2.08.HSPL 8G XE

0x05

CotullaHSPL 0x30

:confused:
[HD2 General] T-Macgnolia:
Ok you still have HSPL 2.08 wich is good as this means you can flash a custom ROM if you want to. Bit be advised that seeing as you have the 512MB version if you use any 3.14 official ROM or 3.14 based custom ROM then you will have to have SPL 3.03.0000 or HSPL 3.03 or you will incounter memory problems, also you will need a Radio version with a 50 in it. bit yhis is only if you are going to use Windows Mobile, if you are going Android don't worry about this.

Now what all have you tried sense your first post, and have hou tried a task 29?