SMS's not sending - Have to reboot to send. - One (M8) Q&A, Help & Troubleshooting

I'm having an issue with my SMS where after a while they will sit in my inbox trying to send but not actually send or fail. I physically have to reboot the phone for them then to send. S-off, rooted running ARHD 10.2. I'm not sure if it's more network related or handset related as I can receive and everything else works solidly.
Anyone else experienced this?

I am running a similar set up like you, im on ATT, I can't say I've had that problem enough to say its a problem..
Obviously your service is good in that particular area?

xavier2k3 said:
I'm having an issue with my SMS where after a while they will sit in my inbox trying to send but not actually send or fail. I physically have to reboot the phone for them then to send. S-off, rooted running ARHD 10.2. I'm not sure if it's more network related or handset related as I can receive and everything else works solidly.
Anyone else experienced this?
Click to expand...
Click to collapse
Have you upgrade the firmware? Check this link http://forum.xda-developers.com/showpost.php?p=54408500&postcount=9592
US users may wish to try the 2.22.1540.3 fw

jmoneste said:
Have you upgrade the firmware? Check this link http://forum.xda-developers.com/showpost.php?p=54408500&postcount=9592
US users may wish to try the 2.22.1540.3 fw
Click to expand...
Click to collapse
Yeh I have upgraded my firmware before flashing 10.2. It's an intermittent problem which is the most annoying thing. In the ARHD post there seem to be at least 2 others with this same issue as well which is strange...

xavier2k3 said:
Yeh I have upgraded my firmware before flashing 10.2. It's an intermittent problem which is the most annoying thing. In the ARHD post there seem to be at least 2 others with this same issue as well which is strange...
Click to expand...
Click to collapse
I had an issue with sms notifications after I installed a custom rom. Then learned that my problem comes from the hearbeat interval settings. I think my carrier uses a custom value (5min is default) and since I changed the rom, their settings have not been pushed to my phone.
Testing several things I came across this app. It will not hurt to try it:
Install an app called "pnf push notification fixer". Is free from store.
Set the heartbeat mobile interval to 3 minutes.
Reboot.
Make sure the value did not change itself
Monitor and see if the problem stays the same.
This maintains the connection alive for me.
Have you checked when you experience the issue if the sms carrier center number removes or changes?
On the dialer press *#*#4636#*#*
Select phone info
Scroll down to smsc and hit refresh. Note the number when working. When it stops, repeat the process and check if the number is diff or was removed. You can also hardcode one there.

jmoneste said:
I had an issue with sms notifications after I installed a custom rom. Then learned that my problem comes from the hearbeat interval settings. I think my carrier uses a custom value (5min is default) and since I changed the rom, their settings have not been pushed to my phone.
Testing several things I came across this app. It will not hurt to try it:
Install an app called "pnf push notification fixer". Is free from store.
Set the heartbeat mobile interval to 3 minutes.
Reboot.
Make sure the value did not change itself
Monitor and see if the problem stays the same.
This maintains the connection alive for me.
Have you checked when you experience the issue if the sms carrier center number removes or changes?
On the dialer press *#*#4636#*#*
Select phone info
Scroll down to smsc and hit refresh. Note the number when working. When it stops, repeat the process and check if the number is diff or was removed. You can also hardcode one there.
Click to expand...
Click to collapse
Was your problem with notifications or actually having the messages send?

xavier2k3 said:
Was your problem with notifications or actually having the messages send?
Click to expand...
Click to collapse
I had a bit of both. The cellphone was not maitaining the network alive fast enough.

I have the same issue.
I've tried what jmoneste wrote, but the problem still persist. SMS keep failing. Everytime I want a message to be sent I have to activate airplane mode and then desactivate en resend the SMS. It's so annoying.
This problems comes from stock rom and now I'm using the Viper One ROM but it still fails.
Has anyone found the solution?

KamixD said:
I have the same issue.
I've tried what jmoneste wrote, but the problem still persist. SMS keep failing. Everytime I want a message to be sent I have to activate airplane mode and then desactivate en resend the SMS. It's so annoying.
This problems comes from stock rom and now I'm using the Viper One ROM but it still fails.
Has anyone found the solution?
Click to expand...
Click to collapse
I too have the sms not sending until put in flight mode and then off it again occasionally. Cant believe that its so common, but theres no fix. My phones completely stock too!

Related

Issues with my Tilt 2-Phone Doesn't work & other problems

I've had my Tilt 2 for about a month now. I've tried 4 or 5 different ROMs now, but i've come across a problem all of a sudden that wasn't fixed by a hard reset or flashing the stock ROM back. The phone all of a sudden doesn't work! I can still send and recieve text messages just fine, but the phone doesn't work. It says "Dialing...," sits there silent for a few seconds, then beeps 3 times and goes back to my recent calls list.
Beyond this, I have also not been able to get the text message announcements to work on any ROM except for the stock AT&T ROM. I get the same result with all of them, having tried combonations of several different ROMs and three different copies of MSVC. Now matter how I try MSVC will announce my emails, but not my text messages, which happens to be the exact opposite of what I want. Anyone know how to fix this? A registry edit, maybe?
Also, I have tried several different copies of HTC QuichGPS on these cooked ROMs and they all give me an error when I try to run the program. It says something to the effect of "certificate not being signed...one or more missing components..." Is there a particular version that I need to install, or is Advanced Config not really turning off the certificate security?
Any help with any of these problems would be greatly appreciated, the phone in particular being a higher priority of course. Thanks in advance for any help provided.
Chris
The call error should be fixed by calling your provider on a different line and tell them you lost the ability to call after upgrading to a new ROM.
Not sure about MSVC. Do you have high priority messages only checked?
SDK Certs should get rid of any certification errors.
*edit*
Now that I think about it your GPS problem might also be linked to the first one. Have them reset all your connections when you call.
burtonsnow8 said:
The call error should be fixed by calling your provider on a different line and tell them you lost the ability to call after upgrading to a new ROM.
Not sure about MSVC. Do you have high priority messages only checked?
SDK Certs should get rid of any certification errors.
*edit*
Now that I think about it your GPS problem might also be linked to the first one. Have them reset all your connections when you call.
Click to expand...
Click to collapse
I'm going to try to flash a new radio first and see if that fixes it. i don't really have my hope up though because i've tried several ROMs over the past month, and it just suddenly did this around lunch today. and i know one or two of the custom ROMs had radios flashed with them, as did the stock one i just reverted back to. but it a radio flash doesn't work, then i'll try calling my provider. i just hate to have to sit on hold waiting on AT&T. thanks for the advice.

[Q] Text Messaging Problems, native Email, etc. (HTC Incredible)

Hello there,
I'm relatively new to XDA but I've heard that pretty much any problem can be solved through you guys. So here we go. I have an original HTC Incredible (hence the title) which is rooted and has the Android Business Gingersense 2.3.5 ROM installed. My problem is hard to explain, yet may be very simple. I simply cannot send or receive text messages to my knowledge.
So here are the details. Whenever I compose a text message in the native "Messages" app, I click send and the "Loading..." little window with the spinny circle pops up for a split second, disappears and nothing happens. It doesn't show me that the message was sent, nor does it give me an error message saying that it didn't send. Nothing. I have heard, however, from the people I sent the messages to that some of them did in fact go through, but I just didn't know they did cause it didn't show up on my screen. They also said they texted me back multiple times trying to get a hold of me to no avail, which is the other problem. I also cannot receive any messages. It may be that these issues are connected in some way but I am not sure.
Another problem. My native email app has the same sort of issue, only when I compose a message and hit send, it force closes the app saying, "an unexpected problem has occurred." Therefore I cannot send or receive emails as well. Quite inconvenient as many of you probably know.
One last issue involving the texting problem. May not have anything to do with the native sms app, but I believe there is still a possibility. I mainly text with Pinger's TextFree application, which not surprisingly has the same problem as the native app. Every time I try to send a message, NOTHING happens, yet I get reports from the people I "sent" the message to that they actually got the message and tried to get back up with me multiple times. Still, I didn't receive anything. But I did go on the web based version of the app and saw both of our messages between each other and the web app worked fine.
Any help at all is greatly appreciated and I hope I can get this resolved.
Thanks alot!
Almost sounds like a data/mms config problem. Are you able to receive any messages or emails at all?
Sent from my ADR6300 using xda premium
Well, the weird part is, it goes on and off... like one minute I could receive SMS and email another minute I'm back to where I've been
Sent from my Droid using xda premium
I just flashed the new cynagenmod 9 to my Dinc, and can't received texts either. I can send them with no problem, but neither the native text program or the GOSms app are able to receive texts.
Any help?
ousuxndallas said:
I just flashed the new cynagenmod 9 to my Dinc, and can't received texts either. I can send them with no problem, but neither the native text program or the GOSms app are able to receive texts.
Any help?
Click to expand...
Click to collapse
Have you tried a complete wipe and reflash?
Shano56 said:
Have you tried a complete wipe and reflash?
Click to expand...
Click to collapse
Yes, did a complete wipe again, and reflashed 9.
Is it a radio problem?
ousuxndallas said:
Yes, did a complete wipe again, and reflashed 9.
Is it a radio problem?
Click to expand...
Click to collapse
Maybe. Or maybe a block on your plan? What radio do u have
Sent from my HTC Incredible using Tapatalk 2
Open the stock messaging app then hit menu - settings - connection settings, there will be 5 settings greyed out in there. What are the current settings for those 5?
Edit: Nevermind i forgot were talking about cm9, might not the same settings as sense. Better yet go to the market and download "apn backup and restore", do a backup and then go to the sdcard then the apn backup folder and then open the xml backup with a text editor and copy and paste its contents to here. You are on verizon correct?
Shano56 said:
Maybe. Or maybe a block on your plan? What radio do u have
Sent from my HTC Incredible using Tapatalk 2
Click to expand...
Click to collapse
Radio: baseband version 2.15.00.07.28
ousuxndallas said:
Radio: baseband version 2.15.00.07.28
Click to expand...
Click to collapse
I have the same radio also CM9 a5.. I dont think kernel would effect messaging..perhaps try a reflash ?
Shano56 said:
I have the same radio also CM9 a5.. I dont think kernel would effect messaging..perhaps try a reflash ?
Click to expand...
Click to collapse
Okay, I think I have figured it out. Before I reflashed, I deleted my Google account. Then, reflashed C9 and when prompted on reboot to sign into Google, I clicked "later".
So, now I received several test text messages I had sent the past 2 days.
So far, so good.
Also, when I restore from Titanium, I am only going to restore Apps, but not the System Data.
I think Google is somehow interfering with things. Maybe something funky with how my Google Voice is interacting with my phone. Who knows. Anyway, I will be sure to report back here to help others that may have similar problems.
Well, so far so good. When I re-installed Apps I de-selected Data.
Texting is fine now.
Perhaps it was the System Data from prior ROMs interfering with the current ROM?
ousuxndallas said:
Well, so far so good. When I re-installed Apps I de-selected Data.
Texting is fine now.
Perhaps it was the System Data from prior ROMs interfering with the current ROM?
Click to expand...
Click to collapse
haha yes. its never a good idea to restore system data
Hester topeico
One more follow-up. I now Restored all data for the apps separately through Titanium.
Texting still works.
I think when I flashed the new C9 ROM, when I restored Apps+Data in Titanium, something got screwed up and thus the texting function got screwed up.
Now able to send SMS texts but NOT receive them
I'm reviving this thread.
I have checked out a few other threads, and this comes the closest to describing my issues with my rooted unlocked (SEC OFF) HTC Droid Incredible (version 1).
I did NOT change ROMs -- right after getting the DINC, I installed a rooted stock deodexed GB 2.3.4 ROM from DINC.DOES-IT.NET, and I have not touched the ROM since.
BTW, the ROM build is 4.06.605.3 CL 140944 release-keys
Ditto baseband radios, no change. Version: 2.15.10.07.07
I did recently update the kernel to a version of gingertiny that allows apps to record phone conversations without the speakerphone being turned on.
Old version: 2.6.35.14-gingertiny-v2+ Feb 2012
New Version: 2.6.35.14-gingertiny-v2 Nov 6 2012
It is POSSIBLE that the problems started with the change of kernel, because I don't use texting very much at all, but that was still a few weeks ago.
Based on what I have read on XDA, I went into Clockwork Mod 5.x Recovery, deleted and reformatted the data cache, and rebooted.
After that, I could SEND but NOT RECEIVE text SMS.
I had some doubts about whether all my calls were ringing through properly. I am still not entirely sure, but test calls from a landline and mobile phone did ring the phone, so maybe that is no longer (or maybe was not ever?) a problem.
I have seen suggestions to do everything from reinstalling ROM (being sure to restore only apps+data, NOT system data) to flashing a new radio to running *228 over-the-air update to manually upgrading the PRL list.
And then there is the question I have about the kernel change somehow being the culprit...
EDIT: One other thing I did right before changing the kernel was run Convert2Ext4 v2.0 using the "no data limit normal dalvik" version. My reason for running this was to get rid of the low memory/no memory warnings, lockups and crashes I was expriencing despite having over 300MB left out of 775MB on internal memory.
How should I go about trying to restore the ability to receive SMS without totally bricking or otherwise disrupting my DINC and causing more harm than good?
The SMS issue is not a kernel-related issue. I'm reading and re-reading the thread and I'm not 100% positive on what caused the issue for you. Also the convert mod would have no impact on phone related features (data/SMS/calls). Also on the convert mod, the 750MB internal memory (/data) partition is not what was causing the low storage, it's the 150MB /data/data partition that HTC uses for app data/libs/cache.
Process of elimination says go back to the previous kernel from February and see if you have the texting issue. Go back to the same exact build and see if that fixes it. I'd be surprised if the kernel change caused it as a lot of people are using gingertiny without issue.
Also a couple of other thoughts. Are you using the stock SMS app or a third party? Try uninstalling any third party SMS apps temporarily if you have them. Last suggestion is to call Verizon and see if they have a block on receiving SMS. I don't think they would since you can send them and it has to be customer initiated.
Also, no where in your post did it say you tested SMS, just that you couldn't receive them so I'm guessing your conclusion is from the fact that someone said they sent it and you didn't receive them.
Some more details
tiny4579 said:
The SMS issue is not a kernel-related issue. I'm reading and re-reading the thread and I'm not 100% positive on what caused the issue for you. Also the convert mod would have no impact on phone related features (data/SMS/calls). Also on the convert mod, the 750MB internal memory (/data) partition is not what was causing the low storage, it's the 150MB /data/data partition that HTC uses for app data/libs/cache.
Process of elimination says go back to the previous kernel from February and see if you have the texting issue. Go back to the same exact build and see if that fixes it. I'd be surprised if the kernel change caused it as a lot of people are using gingertiny without issue.
Also a couple of other thoughts. Are you using the stock SMS app or a third party? Try uninstalling any third party SMS apps temporarily if you have them. Last suggestion is to call Verizon and see if they have a block on receiving SMS. I don't think they would since you can send them and it has to be customer initiated.
Also, no where in your post did it say you tested SMS, just that you couldn't receive them so I'm guessing your conclusion is from the fact that someone said they sent it and you didn't receive them.
Click to expand...
Click to collapse
Thanks for having a look in, Tiny.
I use PagePlus running off VZW towers. PagePlus service rep sent me an SMS while I was in contact with her by phone, she said it got deducted from by cash balance. The only thing is, it did not actually reach my phone!
I have only used the stock SMS app until just yesterday, when I installed Handcent SMS. That did not help. Will uninstall, but I doubt that will make a difference.
Will go back to the old gingertiny kernel and see what that does, and report back here.
If that doesn't do it, maybe it's time for a Touch of Blue ROM, with which many seem to be doing so wiell...

Jellybean SMS problem

Hi there.
When I go into messages app and make a new message I select contact but then the program drops the area code.
However if I go into the people app then select a contact, press the message button then the sms message will go through because it doesn't drop the area code..
So it is sort of annoying that I have to start messages that way. Anyone else have this?
I am running 4.1.1
Thanks
Seth_nexus said:
Hi there.
When I go into messages app and make a new message I select contact but then the program drops the area code.
However if I go into the people app then select a contact, press the message button then the sms message will go through because it doesn't drop the area code..
So it is sort of annoying that I have to start messages that way. Anyone else have this?
I am running 4.1.1
Thanks
Click to expand...
Click to collapse
are you on maguro, toro, or toroplus?
and what ROM and Kernel are you running?
Wolfbeef123 said:
are you on maguro, toro, or toroplus?
and what ROM and Kernel are you running?
Click to expand...
Click to collapse
I am running this in the odexed version.
http://forum.xda-developers.com/showthread.php?t=1737849
My phone said maguro.
Seth_nexus said:
I am running this in the odexed version.
http://forum.xda-developers.com/showthread.php?t=1737849
My phone said maguro.
Click to expand...
Click to collapse
maybe you got a bad flash.
nandroid and rewipe nad reflash. see if it fixes it.
Wolfbeef123 said:
maybe you got a bad flash.
nandroid and rewipe nad reflash. see if it fixes it.
Click to expand...
Click to collapse
I just went back to 4.04 and downloaded the official ota file. Setting it up now.
Seth_nexus said:
I just went back to 4.04 and downloaded the official ota file. Setting it up now.
Click to expand...
Click to collapse
Turns out that did not fix the issue either.
I guess I am just stuck with starting sms from my people app.
i've noticed this too after the ota, seems like the Parentheses around the code confuse it(###)
Grey Ghost said:
i've noticed this too after the ota, seems like the Parentheses around the code confuse it(###)
Click to expand...
Click to collapse
Glad I am not the only one.
I also have this problem. All my contacts have parentheses () as well.
Bill
I'm also experiencing this issue with the ota update on my i9029a
Anyone solve this issue. This is happening for me too
Seth_nexus said:
Hi there.
When I go into messages app and make a new message I select contact but then the program drops the area code.
However if I go into the people app then select a contact, press the message button then the sms message will go through because it doesn't drop the area code..
So it is sort of annoying that I have to start messages that way. Anyone else have this?
I am running 4.1.1
Thanks
Click to expand...
Click to collapse
I have had the same problem for a while now as well. The most convenient solution in my opinion is to edit the contacts by deleting the parenthesis from the number. I realize this can be tedious but at least its a one time fix instead of starting a conversation through the people app every time. I have been editing the contacts on my Gmail on my computer for convenience and then syncing to my phone. Or just keep using your phone like normal and whenever you run into a problem, just go to the contact page real quick and fix it.
I haven't tried the previously proposed solution of performing a factory reset and re-downloading contacts from the google account. I prefer my method since performing a factory reset would be very inconvenient for me.
Does anyone came up with the solution. Been experiencing the same problem also.

[Bug List]KitKat 4.4.2 Upgrade Bugs

Here's a list of reported bugs since the 4.4.2 kitkat upgrade (bugs may not affect everyone)
1. Horizontal lines during video playback - happens randomly - Rebooting the tablet fixes it / enabling "Disable overlay" in developer settings seems to work -elzeus
2. Audio quality degradation - happens randomly - Rebooting the tablet fixes it / going to test after a clean stock install -elzeus
3. Battery life issues - inaccurate battery level reporting (5% turns 25% after reboot) - alexandruene
4.Chromecast systemui crash is pretty serious. - GldRush98
5.Lockscreen widgets are broken. - GldRush98
6. Emails not showing up in sent folder - jaytee23
7. long press the "period" the "?" doesn't work - RTbar
Battery life
The big issue i have is the battery life. today i couldn't get more then 2 hours on the internet. Did a factory reset and the same thing.
Once it reaches 5 percent if i restart it goes up to 25 but it drops back down to 5 percent in like 5 minutes. Tried with no sd card, no other app's but the same thing. Anyone with a tip on how to get this fixed?? Before the update it was working fine.....
I've added your issues. I have not come across that battery issue on my tablet. Have you tried wiping your cache and user data from recovery before setting up the tablet?
Update for my issues I did a Odin restore with the stock 4.4.2 image and so far no video or sound issues but they took some time to show up before so I'll be keeping a close eye on it.
elzeus said:
So far I've come across 2 major bugs and I'll be updating the list with other bugs when found.
1. Horizontal lines during video playback - happens randomly - Rebooting the tablet fixes it / going to test after a clean stock install -elzeus
2. Audio quality degradation - happens randomly - Rebooting the tablet fixes it / going to test after a clean stock install -elzeus
3. Battery life issues - inaccurate battery level reporting (5% turns 25% after reboot) - alexandruene
Click to expand...
Click to collapse
I can verify random audio quality issue. Happened to me four times since the KK update.
It seems to happen either after you quit an app/game or waking the Note from sleep. I haven't been able to trace the trigger to an exact action or app yet, if there is one.
You don't have to reboot to fix. You can fix by locking and unlocking... maybe once, maybe a few times. But it comes back to normal after one or a few tries for me. Reminds me of the audio bug we had on the HP Touchpad after its final firmware update. Damn! I thought I wasn't going to have to deal with that anymore!
I'll try to be more specific on the lock/unlock fix as I gather more info when it happens again.
And by the way, the fix on the Touchpad was also very similar - lock, wait ten seconds, unlock... lol... maybe Samsung is using the Touchpad audio driver!
jaytee23 said:
I can verify random audio quality issue. Happened to me four times since the KK update.
It seems to happen either after you quit an app/game or waking the Note from sleep. I haven't been able to trace the trigger to an exact action or app yet, if there is one.
You don't have to reboot to fix. You can fix by locking and unlocking... maybe once, maybe a few times. But it comes back to normal after one or a few tries for me. Reminds me of the audio bug we had on the HP Touchpad after its final firmware update. Damn! I thought I wasn't going to have to deal with that anymore!
I'll try to be more specific on the lock/unlock fix as I gather more info when it happens again.
And by the way, the fix on the Touchpad was also very similar - lock, wait ten seconds, unlock... lol... maybe Samsung is using the Touchpad audio driver!
Click to expand...
Click to collapse
Got lines again on video tried to lock a bunch of times didn't work (ill try for audio). Don't they test these updates? This is a pretty nasty bug that didnt happen pre kitkat, I think im going to downgrade until its fixed.
Update after reading this youtube thread https://www.youtube.com/watch?v=NEasAq2ik_A
I'm trying out forced gpu rendering to see if it fixes it. It seems like it is a software issue as it affects the pro 12.2 model as well.
elzeus said:
I've added your issues. I have not come across that battery issue on my tablet. Have you tried wiping your cache and user data from recovery before setting up the tablet?
Did everything but didn't help, last night i left in recovery mode so i can make sure the battery dies completely and to day i saw a big improvement.
I hope it will stay that way.. I will keep you updated
Click to expand...
Click to collapse
Mh, as developer I am always careful to call something a bug.
And for these "bugs" my question is: Why not everyone have it? Why only a small group? Therefore I don't think that these are bugs but have to do with your installation.
Did anyone of your try a factory reset? Try out on a clean installation, which means without any settings changed, any app installed, any sd-card inserted?
Elim said:
Mh, as developer I am always careful to call something a bug.
And for these "bugs" my question is: Why not everyone have it? Why only a small group? Therefore I don't think that these are bugs but have to do with your installation.
Did anyone of your try a factory reset? Try out on a clean installation, which means without any settings changed, any app installed, any sd-card inserted?
Click to expand...
Click to collapse
I've done a factory reset & clean installation. I haven't rooted but did add my normal apps after getting it setup with sd card. The next time it happens I'll try unmounting the sd card.
If you check out this video https://www.youtube.com/watch?v=NEasAq2ik_A they also had the issue on their Pro 12.2 but that tablet received a stability update in early April that may have fixed it. It may be that our version was trailing there's or there is some other variable (no magazine UI etc) that is causing it http://forum.xda-developers.com/showpost.php?p=50527314&postcount=20 that person also had the lines in late Feb. I'll pm him and ask him if the issue went away after their update.
Forcing GPU 2d rendering from the developer options didn't seem to work as the corruption came back, but I did enable the "Disable UI overlay" and it did end up going away "crossing fingers" as this is the only thing I've tried that has gotten rid of the lines while the tablet is powered on (usually it only goes away after rebooting).
Another bug I found so far is with the included Email app. I'm using it with my gmail account. The new version included with KK has an issue with sent mail. Specifically, it doesn't update the sent mail folder - at least for me. It used to work perfectly. Now when you send an email from the app, the email doesn't show up in your sent mail folder within the app. I have tried deleting all the email data on the tablet, and the cache, and set it up four times since KK and it it just won't show email you send from the tablet in the sent mail folder. Note, I'm not talking about email that is already in your sent email folder in your gmail account. I'm saying, send a new email from the tablet, and that email should immediately appear in your sent mail folder, but it doesn't. It doesn't ever show up there. Kind of a problem. Can anyone else confirm this? Send an email from the Email app and see if it shows up in your sent mail folder within the email app. Thanks.
---------- Post added at 10:40 PM ---------- Previous post was at 10:19 PM ----------
Elim said:
Mh, as developer I am always careful to call something a bug.
And for these "bugs" my question is: Why not everyone have it? Why only a small group? Therefore I don't think that these are bugs but have to do with your installation.
Did anyone of your try a factory reset? Try out on a clean installation, which means without any settings changed, any app installed, any sd-card inserted?
Click to expand...
Click to collapse
You're a developer and you say that? Are you serious? I'm an expert user. Every platform I've ever owned for the past 30 years from the Commodore 64 to this Note 10.1 has had bugs, some minor, some major. Just like the 24-second touchsceen timeout bug I found and reported in the last firmware version. The new KK update is so new its still rolling out to users. I've already encountered two bugs for sure - the audio quality bug and the email bug I just described in the previous post. The audio bug has been confirmed and I believe the email bug I just reported will also be confirmed. The fact is that certain people are more adept at finding and reporting issues. It also depends on how you use the device and with what regularity. Are you suggesting that we sit on our hands and not report the problems we find? Please.
jaytee23 said:
Another bug I found so far is with the included Email app. I'm using it with my gmail account. The new version included with KK has an issue with sent mail. Specifically, it doesn't update the sent mail folder - at least for me. It used to work perfectly. Now when you send an email from the app, the email doesn't show up in your sent mail folder within the app. I have tried deleting all the email data on the tablet, and the cache, and set it up four times since KK and it it just won't show email you send from the tablet in the sent mail folder. Note, I'm not talking about email that is already in your sent email folder in your gmail account. I'm saying, send a new email from the tablet, and that email should immediately appear in your sent mail folder, but it doesn't. It doesn't ever show up there. Kind of a problem. Can anyone else confirm this? Send an email from the Email app and see if it shows up in your sent mail folder within the email app. Thanks.
Click to expand...
Click to collapse
I normally just use gmail but I setup the stock email app to test it for you. I set it up as a push account and sent a test email. It was briefly in the "Outbox" folder then it was sent out leaving the outbox folder empty. I then checked the Sent folder right underneath the outbox folder and it wasn't updated yet so I hit the refresh button in the top right corner and my test email showed up.
jaytee23 said:
Every platform I've ever owned for the past 30 years from the Commodore 64 to this Note 10.1 has had bugs, some minor, some major.
Click to expand...
Click to collapse
I never said that there are no bugs. I am only saying that not every issue is a bug. I mean when your are playing with the developer options (which normally hidden with a reason) then you should understand what yiu are doing and not call then probelms because of it a bug.
jaytee23 said:
I've already encountered two bugs for sure
Click to expand...
Click to collapse
No, I am not sure and that is what I am saying.
jaytee23 said:
Are you suggesting that we sit on our hands and not report the problems we find? Please.
Click to expand...
Click to collapse
I never did that. I only mentioned not to call issues a bug. This didn't help anyone. People who didn't have this problem begin to fear it and people who have will stop searching the real reason because it is a bug.
I mean what I see are already hundreds of downloads of KK and only 3 persons complaint the video "bug". Did you think that only 3 "power" users are watching videos?
---------- Post added at 08:36 AM ---------- Previous post was at 08:16 AM ----------
elzeus said:
and my test email showed up.
Click to expand...
Click to collapse
Same here and I checked it also with other KK devices and there it is the same, which is for me also normal. But maybe I didn't understand your problem?
elzeus said:
I normally just use gmail but I setup the stock email app to test it for you. I set it up as a push account and sent a test email. It was briefly in the "Outbox" folder then it was sent out leaving the outbox folder empty. I then checked the Sent folder right underneath the outbox folder and it wasn't updated yet so I hit the refresh button in the top right corner and my test email showed up.
Click to expand...
Click to collapse
Do you have an SD card inserted?
I just tried something where:
1) I deleted my email account from the client again
2) deleted the data/cache from the Email app
3) ejected my SD card
4) set up the account again in the Email client
5) sent a test email
6) sent email now shows up in sent email folder but only after a manual refresh
7) reinserted SD card
8) sent another test email
9) sent email still showing up in sent email folder, but only after a manual refresh (shouldn't have to do that) and it takes awhile.... hmmm....
I tried this because I was reading a thread in the 12.2 forum (http://forum.xda-developers.com/showthread.php?t=2670065) where a guy mentioned a similar issue. I thought I would try dismounting the SD card and setting up the account again... still not happy... still uncertain about this... something wonky here.
I'll try more tomorrow... must sleep now.
Chromecast systemui crash is pretty serious.
Lockscreen widgets are broken.
jaytee23 said:
Do you have an SD card inserted?
Click to expand...
Click to collapse
Yes SD card inserted 24/7 never removed it after the initial 4.4.2 recovery setup.
GldRush98 said:
Chromecast systemui crash is pretty serious.
Lockscreen widgets are broken.
Click to expand...
Click to collapse
Adding to the list, I could have sworn before I reinstalled 4.4.2 that my lockscreen widgets were working after upgrading from 4.3 but now I have no option to enable them in 4.4.2.
Elim said:
Same here and I checked it also with other KK devices and there it is the same, which is for me also normal. But maybe I didn't understand your problem?
Click to expand...
Click to collapse
I didn't have any problem with email I was tracing my steps for jaytee in case I did anything different from him in the way his email is setup. As for the list if they aren't bugs then what are they? People make bug lists so they can get fixed or so people can post workarounds. The only reason I enabled the developer options was to find a solution for the video lines...so far the disable overlay checkbox has worked.
elzeus said:
As for the list if they aren't bugs then what are they?
Click to expand...
Click to collapse
Maybe it is personal but I would call them problems and not bugs. The difference for me is that a problem is my problem and I have to find a solution or work-around (or someone else for me) and a bug came from Samsung and normally can only be solved by Samsung. A problem didn't have anybody, can be constructive be solved and create a positive atmosphere here in xda. A bug have anybody, can be solved only by experts and is something negative because the product didn't work like it should be.
Therefore I find good that you start such a list but I would more mentioned what you did before (how you get the update), which update, if rooted or not, what happens and what was expected and then if a solution or work-around exists.
Elim said:
Mh, as developer I am always careful to call something a bug.
And for these "bugs" my question is: Why not everyone have it? Why only a small group? Therefore I don't think that these are bugs but have to do with your installation.
Did anyone of your try a factory reset? Try out on a clean installation, which means without any settings changed, any app installed, any sd-card inserted?
Click to expand...
Click to collapse
jaytee23 said:
You're a developer and you say that? Are you serious? I'm an expert user. Every platform I've ever owned for the past 30 years from the Commodore 64 to this Note 10.1 has had bugs, some minor, some major. Just like the 24-second touchsceen timeout bug I found and reported in the last firmware version. The new KK update is so new its still rolling out to users. I've already encountered two bugs for sure - the audio quality bug and the email bug I just described in the previous post. The audio bug has been confirmed and I believe the email bug I just reported will also be confirmed. The fact is that certain people are more adept at finding and reporting issues. It also depends on how you use the device and with what regularity. Are you suggesting that we sit on our hands and not report the problems we find? Please.
Click to expand...
Click to collapse
You're both sort-of correct. There are pervasive "bugs" and situational bugs. @Elim is right, it's pretty clear that some of the issues being reported are situational bugs caused by some combination of elements that affect a subset of users. Add to that no two Android devices are configured the same way and it's easy to see how things that affect one user (or set of users) don't affect another. Some people rooted, some use tons of system/memory managers and battery boosters, some flashed over 4.3, and some are using a ROM from a different CSC than assigned to their h/w. All those things can cause issues of varying degrees.
Not everyone's having the battery life, Chromecast, and video lines issues so you can pretty much assume it's not the 4.4 s/w alone causing some folks to have problems. Like Elim said, if it were in the core ROM s/w everyone would be experiencing the issues equally. His advice was solid; do a restore through recovery and before loading any personal apps or settings see if the problem(s) still there. If it's not, it's something related to an individual configuration.
I don't have a problem with Chromecast or lockscreen widgets.
Sent from my SM-P605V using Tapatalk
KwestJones said:
I don't have a problem with Chromecast or lockscreen widgets.
Click to expand...
Click to collapse
Are you on official 4.4.2?
elzeus said:
Are you on official 4.4.2?
Click to expand...
Click to collapse
Yes... Got an official OTA update
Sent from my SM-N900P using Tapatalk

HTC U12+ Known Issues

Sooo I got the phone last Thursday and am using it on Verizon. I've had a few issues that I figured I'd throw a thread together incase anyone else has the same...
Known Issues that I have:
"GroupMe" application will not update unless I am in the application and clicking on a specific chat. - Worked on every other phone I have and cant even find anything on this subject on google. If someone sends a message in a chat it will not update or notify me. I have to click on the specific chat for it to update. I've reinstalled the app 3 times and cleared the cache. un-optimized it with battery settings, nothing is working.
Fixed Issues that I have:
Phantom vibration. - Almost like a notification is happening but nothing is showing on the screen. Cant figure out this one for the life of me. I even have a notification log downloaded and it just vibrates away with nothing being logged.
Found out it was Verizon Caller ID app. Apparently it keeps crashing and "starting" over and over again. I disabled notifications on it and the vibration went away!​
MMS Cannot be received only sent. - I've gone through this extensively with Verizon support. Tried everything on another thread, switched out sim blah blah blah, finally they have opened a ticket with the engineers and will get back to me in 48 hours.
Works now in default app just not android messages.​.....................................
Anyone else having any other issues?
That's disappointing that there are mms issues. MMS on the U11 using anything but the stock messaging app was a complete ****show. I hope you can get more bands than just 13 as well.
Sent from my Pixel 2 XL using Tapatalk
MMS works fine on my European un-locked (and rooted) U12+. Got one as late as yesterday... Using stock SMS app.
Pr3dict said:
Sooo I got the phone last Thursday and am using it on Verizon. I've had a few issues that I figured I'd throw a thread together incase anyone else has the same...
Known Issues that I have:
MMS Cannot be received only sent. - I've gone through this extensively with Verizon support. Tried everything on another thread, switched out sim blah blah blah, finally they have opened a ticket with the engineers and will get back to me in 48 hours.
Phantom vibration. - Almost like a notification is happening but nothing is showing on the screen. Cant figure out this one for the life of me. I even have a notification log downloaded and it just vibrates away with nothing being logged.
"GroupMe" application will not update unless I am in the application and clicking on a specific chat. - Worked on every other phone I have and cant even find anything on this subject on google. If someone sends a message in a chat it will not update or notify me. I have to click on the specific chat for it to update. I've reinstalled the app 3 times and cleared the cache. un-optimized it with battery settings, nothing is working.
.....................................
Anyone else having any other issues?
Click to expand...
Click to collapse
Someone on Android Central had Verizon block messaging and then re-add it for everything to work. Maybe worth a shot?
Same here... Unlocked US model. Send but not receive texts...
I've done the same, reset, new SIM, swapped Sims etc.
I'll take a look on AC and see if they have something there for a solution... Thanks for the heads-up. Glad I'm not alone.
CJ
I have found that Android messages app doesn't work as you can't select the preferred sim for messages. Having to use stock at the moment.
Somewhere in another thread, there was an adb command I think that set and enforced the default sim slot. Wonder if that would help with your issue, Nestacres? Sorry, I would search myself and link but just checking in on a quick break at work.
Nestacres said:
I have found that Android messages app doesn't work as you can't select the preferred sim for messages. Having to use stock at the moment.
Click to expand...
Click to collapse
Android Messages isn't comiled for usage with Dual-SIM, as Google Nexus/Pixel phones are all Single-SIM devices. If you know how to use adb you cand do the following:
From adb shell run the following command
Code:
adb shell settings put global multi_sim_sms 1
This did the trick on the U11 DUGL as well, and Android Messages could be used and worked just fine. Thanks to @Electronic Punk for pointing that one out to me!
Soooo Got MMS to work on the default app and with Verizon Message +.... Android messages still does not work and that is something many others have said as well....
Very sad.
Pr3dict said:
Soooo Got MMS to work on the default app and with Verizon Message +.... Android messages still does not work and that is something many others have said as well....
Very sad.
Click to expand...
Click to collapse
Pr3dict: did you do anything different other than what you originally posted? I've been on vacation since i got the U12 and haven't called Verizon. I can send everything, but not receive. I can pop the SIM and put it in my iPhone x and the texts just role in immediately...I really want to love this phone! Lol
5m4r7ph0n36uru said:
Android Messages isn't comiled for usage with Dual-SIM, as Google Nexus/Pixel phones are all Single-SIM devices. If you know how to use adb you cand do the following:
From adb shell run the following command
Code:
adb shell settings put global multi_sim_sms 1
This did the trick on the U11 DUGL as well, and Android Messages could be used and worked just fine. Thanks to @Electronic Punk for pointing that one out to me!
Click to expand...
Click to collapse
It actually works great with dual sim, for some reason HTC left out the default SMS sim option out on Oreo (simply doesn't exist in settings.apk anymore) and only left the data one. Fortunately that fix is basically a fire and forget, once it sees a default it has no issue picking between them.
HTC handle it differently on phone and SMS as they have a button for each sim.
Electronic Punk said:
It actually works great with dual sim, for some reason HTC left out the default SMS sim option out on Oreo (simply doesn't exist in settings.apk anymore) and only left the data one. Fortunately that fix is basically a fire and forget, once it sees a default it has no issue picking between them.
HTC handle it differently on phone and SMS as they have a button for each sim.
Click to expand...
Click to collapse
Yeah they handle it quite different. But let's see. Maybe we'll get an overhaul with Android P.
Sent from my HTC U12+ using XDA Labs
cramjammer said:
Pr3dict: did you do anything different other than what you originally posted? I've been on vacation since i got the U12 and haven't called Verizon. I can send everything, but not receive. I can pop the SIM and put it in my iPhone x and the texts just role in immediately...I really want to love this phone! Lol
Click to expand...
Click to collapse
I did everything possible. Even got a new SIM... What seemed to do the trick (and was the last thing I did) was having Verizon block my messages and then unblock them.
Then I could send + receive. Beforehand I could only Send... But beware it does not work with Android Messages.
cramjammer said:
Pr3dict: did you do anything different other than what you originally posted? I've been on vacation since i got the U12 and haven't called Verizon. I can send everything, but not receive. I can pop the SIM and put it in my iPhone x and the texts just role in immediately...I really want to love this phone! Lol
Click to expand...
Click to collapse
How did you first activate your phone? If it's not activated properly on Verizon it can fry your SIM card or cause things to not work.
I first swapped my SIM from my U11 and could not make calls but was able to use internet and send and receive text and mms. But just like the U11, I can only receive MMS on the stock apps like HTC messaging and Verizon message+. Cannot receive MMS on third party apps.
But the proper way to activate the U11 and U12+ is to first register your imei with Verizon then you have to transfer your SIM from a Verizon device that has advanced calling/VoLTE in the settings.
The U12+ does not have any Verizon advanced calling or VoLTE setting so if you just pop a new SIM in without first having it activated on a Verizon advanced calling device, it could cause problems and fry your SIM card.
It sucks but that is the best way to activate it.
Manually attached IMEI to SIM, and toggled messages/on/off on my account.
All is well and working for receiving SMS/MMS on stock messages! It worked immediately...
Thanks for the feedback and discussion everyone.
CJ
In my case, after updating (purely, after RUU) to v1.21.401.3 I have noticed a few times that after picking up the device and "squeezing" I should wake up, scan my face and unlock my smartphone (I have my preferences set) .
But just the few times after "squeezing" the device does not react at all, there is no vibration.
After the traditional unlocking (applying the finger to the fingerpront or pressing the POWER button) the smartphone wakes up properly.
This happens when the smartphone is not used for a long time (deep sleep?).
But this is not the rule.
I also had ONE total reboot.
On the other hand, the update did not improve in the first few months the best inflections of the volume up button (Vol +). Very often you have to press many times "to surprise", and pressing and holding it to turn up in series - is very difficult to achieve
regards
q.
Is anyone else having issues with the youtube app? Im finding it buggy. To be precise: if I start a video and then turn the phone landscape to go into fullscreen, if I then turn back the phone vertical and come out of fullscreen and then try minimise the still playing video it goes a bit haywire, parts of the screen goes grey and I can't minimise the video. Can any replicate?!
Sent from my HTC U12+ using Tapatalk
New issue thats bothering THE CRAP OUT OF ME!!!!
The phone isnt vibrating on incoming calls. I thought I just kept not feeling it or hearing it but nope, the phone literally turns the screen on and it just doesnt vibrate. I don't have battery saver on, and I don't have "Do not disturb" on. Its weird.
sentient85 said:
Is anyone else having issues with the youtube app? Im finding it buggy. To be precise: if I start a video and then turn the phone landscape to go into fullscreen, if I then turn back the phone vertical and come out of fullscreen and then try minimise the still playing video it goes a bit haywire, parts of the screen goes grey and I can't minimise the video. Can any replicate?!
Click to expand...
Click to collapse
I have the same problem. It also happens when I press back on the navigation bar
tdwpkidd said:
I have the same problem. It also happens when I press back on the navigation bar
Click to expand...
Click to collapse
Discovered a slight work around since. It doesn't happen if you go in and out of fullscreen using little button in the bottom right. So it only happens with auto rotation.
Sent from my HTC U12+ using Tapatalk

Categories

Resources