The problem is when I receive text messages from any network, the time stamp is messed up and shows up two minutes in the future (see picture below). I have done a complete hard reset about five times, tried all different software updates, went completely back to stock (unrooted), tried AOSP roms, tried Gingerbread roms, tried Sense roms with AOSP mms.apk, and whatever I try I cannot get rid of this bug. It causes all my text messages to be scrambled and not in order. I use this phone 90% of the time for texting. It's how I handle most of my business. I called Sprint and ended up getting up to their advanced tech support where they simply did a provisioning reset (completely unactivated and activated again) and after that they said there is nothing they can do. So I took it into the remedial Sprint tech in my local Sprint store (don't have enough time to travel 2 hours to get to a corporate store), and they did another master hard reset where they completely reloaded the software (I guess). Still not fixed. I am outside of my 30 days so i cannot do a swap. I cannot send my phone in to HTC because I simply cannot live without a phone for 2 weeks, and I don't have a backup. I've done all types of searching on google and the only thing I could find was about 6 months ago people were having this problem but the times were delayed by an hour or two. The texts are not delayed they show up on time, they just have the wrong time stamp. It has to be something with the network and not the software. My immediate suspicion is that is has something to do with my MMS provisioning to the network but I really don't know how to look into this.
This is probably one of the weirdest problems you will ever see. The picture at the bottom shows the right time in the corner but look at the time on my last incoming text. Off by two minutes in the future. Can anybody offer my some advice I am up for anything. I can also post or send anybody anything. I need this fixed but I just can't deal with Sprint anymore. I realized they are a business but if they support a faulty product, they should fix it without taking anything away from their customers. I always feel like Sprint is trying to take something away from their customers. Oh also one of the Sprint techs said the EVo would not get an official gingerbread update because Sprint wants to push other phones.........most likely a fib but who knows....sounds like Sprint and HTC. Anyways
Just a thought, what if those texts really are coming from the future? I mean for all you know you are caught in some sort of weird time vortex thing that distorts your perception of time, making it seem like you are in the present when actually you are two minutes behind everybody else. That would make any text coming in to you be from 2 minutes in the future. I know this sounds far fetched but I wouldn't discount it as a possibility.
This is a bug in android. Search the market for sms time fix and see if that helps.
Usually it's off by hours and not minutes though. There is also a setting somewhere that will let you use the local time instead of network time but I don't remember where it is at. You could also try disabling roaming, I keep mine locked to Sprint's network and never lose a signal.
Never heard of this fix, but I got the same bug. I just installed chomp sms, works perfect now.
Sent from my PC36100 using Tapatalk
Try CM7. Perhaps the bug was fixed in Gingerbread (2.3.1)
I tired gingerbread....and the funny thing is this only happens to some phones because my roomate has an evo right now and it does not do any of this....so it is not a problem with android......it has to be the Sprint servers or something. I'm on fully stock right now (no root). I tired gingerbread (CM7) and it didn't help anything. I'm taking my phone back into Sprint today but this time I'm going to give them hell. I payed 350 dollars for this phone I will not settle for "Oh, well we can't do anything about it." You shouldn't have to install anything extra on your phone. I tried that SMS fix but the funny thing is, it messes everything up because my Sprint texts are fine but my verizon and att are all futuristic. And no I am not in some weird wormhole or time continuum the phone is just messed up. It happens with electronics but there is usually this thing called a warranty that allows for direct replacement and for some reason cell phone companies have avoided this whole customer based process. I'll get back in about an hour.
Alright went to my local Sprint Repair Center and they could do absolutely nothing. However I did have the manager push through a priority claim ticket to the network engineers and hopefully, and I do mean hopefully, they call me back. Apparently the last few times I've called they told me they started a ticket, and actually didn't. I think they think I was telling them a lie or something. The manager there was actually extremely helpful and told me he would make sure I get a new phone if this doesn't work. If anybody has any other suggestions please let me know.
I'm curious if this would fix it...
Go to your time options. Settings-Date/Time If automatic is ticked, untick it. If its not, tick it. I would think the bug is caused when a text is sent with a timestamp via the network, at lets say 6:00 but your phone is registered as 5:58. Your timestamp would get all different kinds of backwards in your text app. I'm not sure if time on a phone would be on a BIOS chip like a computer, but it would make sense that your phone is just simply registering the time wrong. If you check/uncheck that and it still does it, simply hard-set the time two minutes ahead.
Recently I've started having the same exact problem, except I have the Samsung Epic. Called customer support once and they "reset messaging" which didn't help at all. Installing any third-party messaging apps haven't helped, and neither has switching between local and network-provided time. Also, its random, so most incoming messages are messed up, but some are actually correct.
I'll try manually setting the time ahead two minutes and bugging some people to text me.
Edit: No luck, with the time set ahead two minutes, incoming timestamps are two minutes ahead of the new setting as well.
av91 said:
Recently I've started having the same exact problem, except I have the Samsung Epic. Called customer support once and they "reset messaging" which didn't help at all. Installing any third-party messaging apps haven't helped, and neither has switching between local and network-provided time. Also, its random, so most incoming messages are messed up, but some are actually correct.
I'll try manually setting the time ahead two minutes and bugging some people to text me.
Edit: No luck, with the time set ahead two minutes, incoming timestamps are two minutes ahead of the new setting as well.
Click to expand...
Click to collapse
Please call technical support and get everything into the Sprint system. Ask them to push it to a network engineer. I have to wait until one of them get a hold of me but they may end up just replacing the phone. I'm glad to hear that other people are having the problem also. Also an update, it is text messages from all networks that do this, including Sprint. I will keep this thread updated because I need to get this problem solved. At this point, I don't think there is anything left for me to do from the user end. I just have to wait for Sprint to get it all figured out. I do have insurance and they said they might just put in a request for a new one at no cost to me......also sounds like bs because I thought you had to pay a 100$ deductible no matter what. The Sprint tech said you don't have to pay for the deductible if its a software or network issue and there is no screen crack or water damage. My EVO is in perfect condition but the software doesn't work. Hopefully they will give me a reconditioned one that actually works.
This is a Sprint network problem. Various sprint phones (not just Androids) are notorious for this type of behavior (wrong time stamps, messages out of order, delay in receiving and sending messages, etc etc). It's very frustrating indeed.
For the time being, try using one of the SMS apps on the market like Handcent or ChompSMS. You may still get incorrect time stamps from time to time, but your messages will arrive/send in order.
twoslo said:
This is a Sprint network problem. Various sprint phones (not just Androids) are notorious for this type of behavior (wrong time stamps, messages out of order, delay in receiving and sending messages, etc etc). It's very frustrating indeed.
For the time being, try using one of the SMS apps on the market like Handcent or ChompSMS. You may still get incorrect time stamps from time to time, but your messages will arrive/send in order.
Click to expand...
Click to collapse
I appreciate the response but I really don't like using aftermarket apps that don't go along with the theme of the phone. I'm real OCD like that. I don't even like apps that have free next to their name. If you pay 350$ for a piece of electronics, everything should work on it, including software and hardware. The sprint engineers need to get this figured out. This is unacceptable. The amount of money they are getting from their customers is ridiculous so why can't everything work. I realize their stock has taken a murdering but you have to keep your customers happy, that's number one. Anyways, I'm waiting too hear from Sprint but they said 72 hours not including the weekend so If I don't hear from them by next Tuesday, they will be getting a nasty call.
Exact same problem!
It has been driving me crazy. I will receive a text at 9:05, respond to it, and it will say it's 1-2 minutes earlier.
Another thing: we have four Sprint phones in the house. If we're all looking at them at the same time, they don't all say the same time. So, I tend to think that the time that shows when I receive a text is actually the time the sender's phone says. (Is that confusing enough for you?) Could that be the difference?
It only started recently, probably when I updated my phone last month.
This happens randomly on my Evo. Certain people I'm texting with, the time stamps will be out of whack, ranging from 2 minutes off, to over an hour off. My time stamp is always accurate, it's just the other person's that is inaccurate. I can be texting with a different person, at the same time, and the other thread will be perfectly normal. It's annoying. My phone also thought it was somewhere in Amsterdam (i wish i was there with it too) for a few hours, and nothing I tried would get it to show my actual location. I attribute all of this to google issues, and not actual problems with the phone.
k2buckley said:
This happens randomly on my Evo. Certain people I'm texting with, the time stamps will be out of whack, ranging from 2 minutes off, to over an hour off. My time stamp is always accurate, it's just the other person's that is inaccurate. I can be texting with a different person, at the same time, and the other thread will be perfectly normal. It's annoying. My phone also thought it was somewhere in Amsterdam (i wish i was there with it too) for a few hours, and nothing I tried would get it to show my actual location. I attribute all of this to google issues, and not actual problems with the phone.
Click to expand...
Click to collapse
Alright still not fixed as of Monday....I have one more day until I can call Sprint and give them hell which I love...not....but anyways I've been doing some testing on when actually the time stamp is off. The time stamp is off from any network including Sprint only when the phone is asleep (or the screen is off). Then the time stamp comes in 2-3 minutes in the future. When my phone is on everything comes in fine and one time and all the time stamps are good. It seems like when the phone is asleep its grabbing things from the network 2 min ahead for some reason.
Alrigth just an update on the situation.....called Sprint back they said they had no recollection of my callings the last couple of days....completely unacceptable. Anyways I got real nasty with them and got sent up to retentions (I told them the iphone for verizon looks really good right now.) Walked all over the retentions people and they said just go to a store and get a warranty swap (since I pay the 7 dollars a month or whatever.) I went to the local store (Lafayette, IN 47909) and they said that I was the first one with this problem but not the last. Apparently right after I left the store the first time I went, about 10 to 15 people came in right after that with the same problem. The manager at the store finally got a technician ticket in and apparently the problem has reached a ton of people all the way down to Indianapolis. Even some of the workers at the store are having problems with their EVOs and Epics. The explanation I got was it has to do with android and the text messaging server within the Sprint Network. If anyone else is having this problem...PLEASE CALL SPRINT AND ***** TO THEM. They need to fix this as soon as possible but they won't recognize it as THEIR problem unless a bunch of people call in about it. It should be getting fixed but I will check back on Friday.
I noticed this same problem on mine. Looks like I'll be calling Sprint tonight and stopping by my local store. Maybe I'll just go to Sprint World HQ here in KC and talk to them about it.
pscalett said:
I noticed this same problem on mine. Looks like I'll be calling Sprint tonight and stopping by my local store. Maybe I'll just go to Sprint World HQ here in KC and talk to them about it.
Click to expand...
Click to collapse
Please do....I'm wondering if there is a bug in the sms server that is causing this and it is slowly spreading nationwide. I call dibs on pointing this out if this is the case. This was from the mouth of a Sprint Employee. "Sprint will not do anything on an individual level but if the problem spreads to more than enough people, they will jump on it immediately." Now how much people is the real questions? I think the Sprint people thought I was crazy and now they are gonna be like....damn we should have listened to him. It's been going on for about 2 weeks now and I'm hoping it gets fixed before the end of the billing cycle.
Hey OP...as you may have figured by now your not the only one. I get it too. I kind of just let it go since it was minor. Mine also, when someone sends me a pic it goes to the very top of the conversation as opposed to in line with the rest of the texts...again i kind of let it go, but i do understand that we all paid our money, we should have perfection or at least 99.9. Thing is i dont want to swing by sprint and them see warm 2.2!!!! Then i'm really screwed!!!!!!!!!!!!!!!!!!!!!!!
Just do a backup and flash a stock RUU.....sprint needs to know about this..It has nothing to do with our phones but everything to do with their servers and they wont do anything until enough people complain. Anybody in the midwest that is getting text message problems, please call Sprint and complain. Explain to them exactly what is happening and tell them to give you a ticket number and tell them you expect a call within 72 hours. Get you case in so this can be fixed for everybody.
Is there an issue with text messeges taking like YEARs for them to be delivered to a non-sprint device? I have a buddy who has this phone. We were at the bucs game and he was trying to text me a few times. I did not get them until we met back up. I thought it was due to the high congestion of the local tower but it continued through out the day. Anyone else experience this? I was ready to go out and buy this phone until I found out about this. BTW I have VZW.
eakrish said:
Is there an issue with text messeges taking like YEARs for them to be delivered to a non-sprint device? I have a buddy who has this phone. We were at the bucs game and he was trying to text me a few times. I did not get them until we met back up. I thought it was due to the high congestion of the local tower but it continued through out the day. Anyone else experience this? I was ready to go out and buy this phone until I found out about this. BTW I have VZW.
Click to expand...
Click to collapse
Just today at work me and a buddy who run different departments were shooting pics back and forth, they appeared on his phone nearly instantly after they officially left mine...I have an ET4G he has a E4GS.
Sometimes that happens. Depending on if you ever got away from that one tower there could have been a message queue a mile long that needed to be processed first..Hell, it could have been your Verizon service. I know that sometimes that same thing happens to me with people on Verizon though that never happens to me with anyone else.
I think just consider it 'random' and feel better about it as there are so many variables that may or may not be involved that it isn't worth worrying about. In my experience in my area with my friends this is not typical at all. That may be completely opposite to you, but, I doubt it. Test more if you want to be sure. I feel confidant that you'll both come up with nearly random in-explainable results...and if the results are so repeated that it's obvious what the problem is I doubt it's that ET4G's send messages slowly.
...though I have been wrong before...
It did happen a few times when I had the Photon also. Maybe its just sprint.... When I had the photon it was between myself and my wifes iPhone on ATT.
I am having issues sending picture mail in the first place due to the data issues on this phone
eakrish said:
Is there an issue with text messeges taking like YEARs for them to be delivered to a non-sprint device? I have a buddy who has this phone. We were at the bucs game and he was trying to text me a few times. I did not get them until we met back up. I thought it was due to the high congestion of the local tower but it continued through out the day. Anyone else experience this? I was ready to go out and buy this phone until I found out about this. BTW I have VZW.
Click to expand...
Click to collapse
Sent from my SPH-D710 using XDA App
Ive been working on this for a few days but i cant figure it out. Ive googled around and cant find any code for it. It works out to a point, at certian times of the day it will say good morning, but then when its going to switch to afternoon it displays like "morningafternoon" same for evening and night as well. This is the closest ive gotten for this to work correctly.
Good $#DHH#<=12?morning$$#DHH#>= 12?afternoon$$#DHH#<=16?evening$ sir
If anyone could help that would be great. Thanks all
Sxnill said:
Ive been working on this for a few days but i cant figure it out. Ive googled around and cant find any code for it. It works out to a point, at certian times of the day it will say good morning, but then when its going to switch to afternoon it displays like "morningafternoon" same for evening and night as well. This is the closest ive gotten for this to work correctly.
Good $#DHH#<=12?morning$$#DHH#>= 12?afternoon$$#DHH#<=16?evening$ sir
If anyone could help that would be great. Thanks all
Click to expand...
Click to collapse
First off, your logic flows like this:
If it's less than or equal to 12, print morning
If it's greater than or equal to 12, print afternoon
It it's less than or equal to 16, print evening
Try this.
Code:
Good $#DHH#<=12?morning$ $#DHH#>=16?evening$ $#DHH#<16&&#DHH#>12?afternoon$, sir.
If it's less than or equal to 12, print morning.
If it's greater than or equal to 16, print evening.
Otherwise, print afternoon.
Let me know if that works, but I think it should.
EDIT: It would appear as though you can't nest conditionals in Zooper. I guess you learn something new every day. Seems kind of silly to not be able to do that, but I've fixed my code snippet to what I believe should work.
Sxnill said:
Ive been working on this for a few days but i cant figure it out. Ive googled around and cant find any code for it. It works out to a point, at certian times of the day it will say good morning, but then when its going to switch to afternoon it displays like "morningafternoon" same for evening and night as well. This is the closest ive gotten for this to work correctly.
Good $#DHH#<=12?morning$$#DHH#>= 12?afternoon$$#DHH#<=16?evening$ sir
If anyone could help that would be great. Thanks all
Click to expand...
Click to collapse
The problem with your conditionals is that they are overlapping each other. Morning and afternoon booth have an "equal 12" part in their condition meaning while the hour is twelve, both will be displayed. The next problem is that your evening string is checking for "smaller 16". Every hour between midnight and that time is smaller as the number 16, so evening should be displayed the whole time.
What you need to do is limit the conditionals so they don't overlap each other and only one condition is true at the same time. For your example this should look more like this:
Good $#DHH#<12?morning$$#DHH#>= 12 && #DHH#<16?afternoon$$#DHH#>=16?evening$ sir
If you have more conditions then the one you listed or if you need other boundaries (for instance if "morning" should only be displayed between 7 and 12) you need to adapt this further. I hope you understood the principle of this though Oh and here is a link to the description of Zooper conditionals and the available symbols, might be worth a read: http://zooper.themerapp.com/support/solutions/articles/158018-conditionals-and-boolean
xancgy said:
First off, your logic flows like this:
If it's less than or equal to 12, print morning
If it's greater than or equal to 12, print afternoon
It it's less than or equal to 16, print evening
Try this.
Code:
Good $#DHH#<=12?morning$ $#DHH#>=16?evening$ $#DHH#<16&&#DHH#>12?afternoon$, sir.
If it's less than or equal to 12, print morning.
If it's greater than or equal to 16, print evening.
Otherwise, print afternoon.
Let me know if that works, but I think it should.
Click to expand...
Click to collapse
EDIT: It would appear as though you can't nest conditionals in Zooper. I guess you learn something new every day. Seems kind of silly to not be able to do that, but I've fixed my code snippet to what I believe should work.
kwerdenker thanks alot, that makes alot more since now, i just got started with using zooper so coding this so somewhat different than writing php. Still figuring it out though. Thanks everyone for all the responses.
I want to create two side by side bars to show my exact position in my monthly billing cycle and my data used to give me an accurate idea of how well I am doing data-usage wise. I have tried a bunch of stuff but I cant get it and was hoping somebody here could help me out. This is what I have tried so far.
My billing cycle restarts on the 7th.
My first attempt was to get the number of days since last months 7th and today and subtract the number of days since this months 6th using "#D...Td#" to get the number of days in the last billing cycle but the strings ended up really long and I couldnt figure out how to subtract one from the other.
My next try was using the number of days in this month if it is after the 6th and use the number of days in last month if it is before the 6th. This is what I came up with.
Code:
[B]#$0$# [/B]#D$#DM#=1?[B]2014[/B]:#Dy#$$#DM#>1&&#DM#<11?0$$#DM#=1?12:[B]7[/B]$010000l#
This is the logic I use to get a datetime stamp of last month:
If this month equals 1 then append last year else append this year
if this month is greater than 1 and less than 11 then last month is a single digit so append a 0
if this month is 1 append 12 else append this month minus 1
append 01 for the first day
append 0000 for HHMM
I use the generated string in #D...l# to get the number of days in last month. Doing this I ran into two(maybe three?) major problems. The one is that i dont know how to perform an operation inside the if/else without breaking the containing "#D...l#" call. The second was that while I was testing things out (I had a few different strings to try and get last months days or the cycle day count) I removed all of the stuff I wasnt using it broke the working one. I trimmed as much as I could without breaking the semi-working string. if I remove the (useless) "#$0$# " from the beginning the second half stops working again.
The last problem is that I am not completely sure how to use this once I get it. I was going to set the progress bar to start at 1 and end at the number of days in this cycle but then I would have to do a bunch of checks on the current day of the month to find out which day in the cycle it is.
So... Is there an easier way to do all of this? Either way I would like to see how to make the line I quoted above work.
Thanks!
Wrong thread
You should also keep in mind that the data usage info that Zooper displays resets when you reboot (I believe it also resets if you wipe the app cache).
Wrong thread
Mokum020 said:
For me it doesn't reset when I reboot, only when I wipe app cache.
Oh and I forgot to mention, you can use this as value for the data usage progress bar: #NTMTMM7#
Click to expand...
Click to collapse
It looks like it maintains across restarts for me too (using an S5).
I actually came up with another solution which I *think* is completely accurate for cycle time and I was leaving it go to make sure the numbers always looked right. About half way through the billing cycle my data usage broke 1GB and #NTMTMM7# started reporting in GB rounded down to one decimal place. Is there any way to force it to display in MB or, if not, make it display two decimal places? With two I could just check if usage is < 3 and if so, assume GB and multiply by 1024, else assume MB and multiply by 1. It won't be accurate for the first 3MB but that will pass quickly enough.
Looks like I was using the wrong string here after all. I switched it to #NTMTMM6# (#NTMTMM7# seems to be way off, 6 is closer but still like 12MB off...)
The strings I am using to get the min and max values for my day progress bar are....
Min: -$#Dd#>6?(#Dd#-7)$$#Dd#<7?#D$$#Dd#<7&&#DM#>1?#Dy#$$#Dd#<7&&#DM#=1?(#Dy#-1)1207$$#Dd#<7&&#DM#<9?0$$#Dd#<7&&#DM#>1?(#DM#-1)$$#Dd#<7?070000Td#$
and
Max: $#Dd#<7?(7-#Dd#)$$#Dd#>6?#D$$#Dd#>6&&#DM#<12?#Dy#$$#Dd#>6&&#DM#=12?(#Dy#+1)0108$$#Dd#>6&&#DM#<9?0$$#Dd#>6&&#DM#<12?(1+#DM#)$$#Dd#>6?090000Td#$
Which shows -23 (days since 7th of last month) to 8 (days until 6th of next month) right now. I just set Value to 0.
I tried setting min to 0, Value to my current Min, and max to my current Min + my current max but I don't know how to get them to add together. I don't plan on having numbers once I figure out how to make this accurate so that isnt an issue. I just need to test them for another week or two to make sure the cycle end/starts are correct and test them for December/January to make sure the month/year corrections are right. Of course all of this is for nothing if I can't figure out how to get the data accurately.
Mokum020 said:
I think this is what you're looking for, from exactly a year ago http://forum.xda-developers.com/showthread.php?t=2679504
Click to expand...
Click to collapse
I saw that before I posted but I was hoping to come up with something more accurate. I guess I don't know how Sprint works internally but the data used in my account and if I am charged an over usage fee seems to be based on 7th-6th cycles, not 30 day cycles.
Edit:
I finally tested my script with a few different days and made some changes. It looks like it works pretty well. If anybody else needs it...
Day of Cycle (replace all (0)6s with the last day of your billing cycle, add a - sign to use as the min value for a progress bar)
$#Dd#>6?(#Dd#-6)$$#Dd#<=6?#D$$#Dd#<=6&&#DM#>1?#Dy#$$#Dd#<=6&&#DM#=1?(#Dy#-1)$$#Dd#<=6&&#DM#=1?12$$#Dd#<=6&&#DM#>1&&#DM#<10?0$$#Dd#<=6&&#DM#>1?(#DM#-1)$$#Dd#<=6?060000Td#$
Days left (replace all (0)7s with the first day of your billing cycle)
$#Dd#<7?(7-1-#Dd#)$$#Dd#>=7?#D$$#Dd#>=7&&#DM#<12?#Dy#$$#Dd#>=7&&#DM#=12?(1+#Dy#)$$#Dd#>=7&&#DM#=12?01$$#Dd#>=7&&#DM#<9?0$$#Dd#>=7&&#DM#<12?(1+#DM#)$$#Dd#>=7?070000Td#$
Have me 5.1.1 on My Note 4ART model, now the step count has stopped increasing (and yes I have been walking around ).
Any ideas as to the cause? I've opened up the app on both th watch and the phone an I can see my past counts but from the update on none.
stevenlong said:
Have me 5.1.1 on My Note 4ART model, now the step count has stopped increasing (and yes I have been walking around ).
Any ideas as to the cause? I've opened up the app on both th watch and the phone an I can see my past counts but from the update on none.
Click to expand...
Click to collapse
My 360 works still. Check that the 360 is still showing as connected in Android Wear. Then check your Moto Body settings. That's all I can suggest.
Sent from my SAMSUNG-SM-N910A using Tapatalk
Thanks for the suggestions I've tried both of those and don't see a obivious problem. Though it might be all the messing with the date I did Friday night to get the update to download (5 times ), and it show that I did 150,000 steps on Friday, just a little more than my usuall 12,000
stevenlong said:
Thanks for the suggestions I've tried both of those and don't see a obivious problem. Though it might be all the messing with the date I did Friday night to get the update to download (5 times ), and it show that I did 150,000 steps on Friday, just a little more than my usuall 12,000
Click to expand...
Click to collapse
Just an FYI: Make sure that you are using Moto Body and not Google Fit. Fit doesn't support the 360.
I've had that situation too a few times when steps wouldn't count, but then one day I suddenly walked like 150,000 steps... my average is 15,000 per day.
Sent from my SAMSUNG-SM-N910A using Tapatalk
Thank you all for your help.
It started working the next day so appears to be connected with all the date/time changes I did to get the update.
Thanks again.
steve