Sorry if this is in a post already, I searched but didn't find anything the same.
I use the stock android messing setup, and on 1.6, when I sent a message with little service, I could leave it and it would keep trying till it sent. Now on 2.1, I find that if service is an issue, it will notify me right away that it didn't go through, and I'll need to hit resend. Any way to change this to the old way, so I don't have to keep bothering with it?
Thanks
Sent from my X10a using XDA App
No one else has this happening?
I've had this happen and had to manually resend the message. Not sure if there is a solution to it
I've had this happen too. Doesn't bother me too much, I just hard press the message and resend it again. My issue is the darned the new way to add recipients. I can't just type their names and the phone automatically recognizes them like with the old firmware. Annoying when I have to send multiple texts.
true say .
Im having this issue as well. And started a similar thread. Shouldnt have now that I found this one Lol...
But did not find solution thus far. But I noticed the phone always goes into H from 3G. I think this could have something to do with it because I know the phone sends them when in H mode rather than 3G.
That or I am just paranoid.
Hmm I have a different problem, whenever i come down to 20 characters left in the SMS, it starts lagging really bad, and sometimes it just closes :S
So I have run in to a bit of a snag, and though I doubt it is ROM specific, I thought I'd start by asking here to see if anyone else has run across this and might have a fix
I first noticed it when I was running ShiftAO5P 3.2, and though I didnt specifically think 3.2.1 would fix it, I tried that, and now the problem has come back.
The gist of the issue is that if I havent used my phone to talk to someone for some unspecified length of time, when I call someone, they cant hear me. I can hear them just fine, but they can't hear anything from my end. If I hang up, and call right back, then it all works fine. Also, it is fine if they call me - works right away without having to re-make the call.
Like I said, I did a complete reload to get to 3.2.1(full wipe, and even reformatted sd card), and since I suspected the tiamat kernel and the call recorder app I had been using under 3.2, I didnt reload those pieces and stuck with just the stock 3.2.1
Everything seemed OK for about the first week or so, but now it is doing the same thing again.
I am guessing it is some app, but I have no idea how to try to chase it down.
I have a logcat that I just dumped right after the problem happened, but dont really know what process to look for.
Any suggestions? TIA!!!
I have been rooting and installing custom roms for a while. I'm no expert, but now newb either. I recently rooted my S4. It's running on the stock verizon ME7 build.
The problem I have been having is that a few minutes after I reboot it all the sounds stop working. No music, notification or in call sounds. If I restart it goes away for a little while, but soon comes back. I tried factory defaulting it, which worked for a little while, but it recently started doing it again. The only thing I can think of is I installed avast Anti-theft with root access recently. Has anyone else had this problem & do you know of a solution? I can always try factory defaulting it again to see if that helps, but I would like to know if anyone else has any ideas.
Odined back
I tried everything I could thing of, then decided to Odin back to stock. Same problem started almost immediately . There are no system sounds and I can not hear anything when I call. Also it does not pick up sounds from my voice via voice commands & the person on the other end of my calls can not hear me. At this point I wonder if blocking is some how activated. Since Verizon was nice enough to prevent me from making changes to it I can't check.... Upwards on onward. I will keep this updated in-case someone else has this problem.
I have noticed that when I am in recovery, if I try to wipe the cache partition. I get a android on his back with a triangle exclamation point & then it reboots itself... Is this normal. I have never experienced this behavior before.
I installed the blocking mode MOD. It does not seem to be the problem. No sounds after using the phone for a few minutes. I guess its time to send it back. I really enjoyed the phone. But I seems like a received a bad one. Unless anyone has anythoughts.
When your sound stops have you tried to see if it is working with headphones or Bluetooth? If there is no sound using headphones or a Bluetooth device there's probably an issue with the phone itself. If you've done a stock Odin flash and its still doing it, I would have to guess the phone is bad. Send it back. The only problem you might have is if they check the flash count, you may end up paying for a new phone. I've never had to use Triangle Away to reset my flash counter, but I believe it needs to be flashed in a custom recovery (which you don't have).
Sent from my SCH-I545 using Tapatalk 4
The upgrade option came up late last night so I did it, I'm on Bell in Canada. After update was complete I can no longer text message. I only have the stock messaging software. If I try to start it all I get is a blank white screen with the messaging title at the top left. I tried downloading textra but it was stuck in setup forever so I uninstalled it.
I don't know or understand how to root, unlock, or flash, nor do I really have the time as I'm crazy busy at work. Does anyone have a solution? Texting is all I do on my phone, it's useless without this functionality. Please help!!!
Hi,
Did you solved the problem?
I had the same thing after the upgrade.
After installing some other SMS apps and few restarts, it started to work but all messages are lost.
I'm trying to find a way to recover them...
BE2026
The stock oxygen OS has a text message bug that apparently isnt fixed yet, so i thought id try a different rom.
I unlocked the bootloader, worked great.
Then i flashed TWRP and it worked great.
I then proceeded to try and flash DerpFest and when the ADB sideload (ACCORDING TO THE DIRECTIONS) was done, it is suppose to reboot into the new os. but I get nothing.
So Ive tried, a bunch of stuff. I tried using orangefox and it doesnt support SD cards and the sideload option just crashes. So then i try TWRP recovery instead of billies recovery and when i select the image to install in TWRP, and then 'swipe to flash' TWRP instantly resets. and nothing happens.
So then i tried the MSMdownloader tool and it will not recognize the phone at all. all adv and fastboot commands work great.
Can someone help me?
I tried switch A or B, and flashing both,
I tried to go back to stock and i cant even get that to work.
Help meh please, i just bought this phone and now i cant even use it
I also cannot get the MSMdownloader to work. it shows my phone on the list in EDL mode. but com port is empty. device id is empty. all the fields are empty and it just says waiting on device. nothing happens.
For MSM, did you get the driver properly installed?
[OPN105G][OOS 86AA/89BA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
arda99 said:
For MSM, did you get the driver properly installed?
[OPN105G][OOS 86AA/89BA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
Click to expand...
Click to collapse
everyone comes up as it should in the device manager. sad face....
Just to be sure, what do you actually SEE? IIRC it was tricky the first times I used it, until I figured everything out.
There is a separate driver from the MSM tool itself; that makes your phone show up as a Qualcomm something or other... but only for about 3 seconds! In that time, you have to start the upload. Thus, I'd have the tool RUNNING, mouse over the start button, THEN plug in phone.... when it shows up, click, and wait till it says something akin to "beginning firehose download"... then you can let go of buttons on phone, sit back, and watch the magic.
Given a proper setup, it's really odd that this fails, for anything other than a completely bricked phone (e.g. dropped it in the ocean)... if you can get into FB or recovery, you should be able to have MSM recover to stock 100%.
Hope that helps.
SomeRandomGuy said:
Just to be sure, what do you actually SEE? IIRC it was tricky the first times I used it, until I figured everything out.
There is a separate driver from the MSM tool itself; that makes your phone show up as a Qualcomm something or other... but only for about 3 seconds! In that time, you have to start the upload. Thus, I'd have the tool RUNNING, mouse over the start button, THEN plug in phone.... when it shows up, click, and wait till it says something akin to "beginning firehose download"... then you can let go of buttons on phone, sit back, and watch the magic.
Given a proper setup, it's really odd that this fails, for anything other than a completely bricked phone (e.g. dropped it in the ocean)... if you can get into FB or recovery, you should be able to have MSM recover to stock 100%.
Hope that helps.
Click to expand...
Click to collapse
OH wow it did. Thank you, the documentation for that side of MSMd is vague. So after trying like 3 different "qualcomm" drivers I finally got it to work! As in the stock android 10 is loaded and the phone is no longer bricked. However, when I try the same methods again to actually put a custom rom on this phone the same thing is still happening.
No matter what OS i try to flash, no matter what mode or slot, or what recovery 'program' i use like twrp or orange FOX, nothing seems to actually boot into an OS. it just loops into Fastbook.
Can anyone help me? I dont want to use oxygenOS
I had a somewhat similar experience in loading custom ROMs, and simply took to de-bloating the stock image (emphasis on de-google-services, de-OnePlusSpyware, and de-auto-OTA). Still not really happy, compiling AOSP source now to try to swap out some of the system APKs that annoy me for customized ones. If there are only a few things that sour you to OOS, maybe I (or others) can help cure those? Debloat and replace...
I wish I had more silver bullets for you on custom ROMs, but you aren't alone. At least know that you can now go back to stock no matter how bad a ROM is... a lot of other phones, not so much.
So the main reason for me not wanting to use Oxygen OS is because when initally setting up the phone, everything works great. for about 2 or 3 days. then for what ever reason i cannot receive text messages. If I factory reset the phone, or put my simcard into another telephone all of them come rushing in.
In the event of me factory reseting my phone, ill get text messages from 3 or 4 days ago.
and it always works. as soon as my friend is texting me and i dont recieve it, i just factory reset then boom its there.
I tried everything, different SMS apps, update this, android 11 that. it always did it to me, like clockwork. like the phone installs an update and breaks text messages. I tried contacting oneplus customer support but that shhit is a joke. they told me they are aware of multiple isolated incidents about this and that the only thing to do left is to send it in. I JUST BOUGHT THIS THINg, im not about to send my device away, right after paying for it. I paid you guys $400 just to NOT have a telephone for 8-16 weeks?
SomeRandomGuy said:
I wish I had more silver bullets for you on custom ROMs, but you aren't alone. At least know that you can now go back to stock no matter how bad a ROM is... a lot of other phones, not so much.
Click to expand...
Click to collapse
See thats the thing, Ive never gotten another room, to boot. at all. no splash screen, no bootlogo nothing. it always just goes back to fastboot. it never tries to boot an OS. i follow these billie instructions and nothing happens. its the same result. I have tried all the different versions in this forum. from pixel experience to derpfest. all work great, untill the very last step where they say side load rom/flash and then reboot. your new os should be booting! and it doesnt.
Wow, that's a new one for me. I wish I knew more about the internals (slowly learning) to help troubleshoot. I would GUESS that if you can change phones (e.g. you said you can put the sim in a new phone, and get a backup of messages delivered), that it isn't so much that the phone is dropping them as it is not getting them in the first place.
With no guarantees- this is a SWAG- have you checked your APN settings? Most definitely, these come through as part of a new registration (duh), and consequently can get messed up for $diety knows why later... but at least you may be able to get a known-good set of settings (post reset, post registration) to compare to after terrorists strike and you are no longer getting messages. It should be easy to add a new APN with the "right" settings and manually select it.
If it is something like that, odds are an alternative ROM would just do the same thing; I assume there's some kind of handshake standard for initialization of the carrier network. I'm on TMo and happy to share my settings, if it helps....?
Looks like RCS issue as 1+ switched to google phone/msg in OOS11.
Read here.
Turn Off RCS "Chat" When You Switch Phones or Else...
Now that Verizon has committed to RCS with Google, the three major US carriers are all onboard. RCS is here (unlike 5G) and will be a big part of your messaging experience going forward, assuming you have an Android phone. And while RCS is great and a big improvement on traditional text...
www.droid-life.com
How to turn off RCS chats
messages.google.com
arda99 said:
Looks like RCS issue as 1+ switched to google phone/msg in OOS11.
Read here.
Turn Off RCS "Chat" When You Switch Phones or Else...
Now that Verizon has committed to RCS with Google, the three major US carriers are all onboard. RCS is here (unlike 5G) and will be a big part of your messaging experience going forward, assuming you have an Android phone. And while RCS is great and a big improvement on traditional text...
www.droid-life.com
How to turn off RCS chats
messages.google.com
Click to expand...
Click to collapse
sadly this has nothing to do with my problem.
After much testing and another go round of fractory resets and then magicly i recieve texts again. There is nothing that can stop the factory oxygen OS from updating or downloading and installing some update that completely brtiks message functionality. Can someone help me maybe mod or edit the factory ROM image to prevent this?
I found out in the "google assisnt" of setting up your phone for the first time, if i set it to remind me tomorrow then im all good and i can keep using the phone. as soon as i go back to that "setup" and hit continue, the next screen says "installing updates" and then I can no longer receive texts. Does anyone know how to bypass/get rid of this auto matic update thats in the "first time run wizard for adroid" or whatever the FUCFKA its called.
Please, I really think this phone might just be a lost cause
agentruley said:
sadly this has nothing to do with my problem.
After much testing and another go round of fractory resets and then magicly i recieve texts again. There is nothing that can stop the factory oxygen OS from updating or downloading and installing some update that completely brtiks message functionality. Can someone help me maybe mod or edit the factory ROM image to prevent this?
I found out in the "google assisnt" of setting up your phone for the first time, if i set it to remind me tomorrow then im all good and i can keep using the phone. as soon as i go back to that "setup" and hit continue, the next screen says "installing updates" and then I can no longer receive texts. Does anyone know how to bypass/get rid of this auto matic update thats in the "first time run wizard for adroid" or whatever the FUCFKA its called.
Please, I really think this phone might just be a lost cause
Click to expand...
Click to collapse
"carrier services"? that's the only one I can think of. Try to uninstall the update, or if you don't have it in your phone, install it.
I had to go through the setup process again. First time the DF just didn't catch. I read ADB sideload can be broken as **** sometimes.
arda99 said:
"carrier services"? that's the only one I can think of. Try to uninstall the update, or if you don't have it in your phone, install it.
Click to expand...
Click to collapse
Sadly this has nothing to do with my problem. Installing newer/ using older versions do not change the behavior.
The phone breaks as soon as I go back to the "Google Assisnt" -Setting up your phone for the first time- wizard and instead of selecting "Remind me tomorrow" i select next, and then the following screen says "Installing updates" and then the telephone will no longer recieve text messages. Does anyone have any help?
Oneplus customer service is terrible and they told me to buy another device.
This is the last phone i will ever purchase from them