Hi all,
I'm working on an app that sets reminders on an Android Wear Smartwatch.
I'm using the Google DataAPI to sync data between phone and watch.
Everything worked fine, till now...
The onDataChanged() method on the watch isn't called any more when I send data from my phone.
I know the data actually has to change between different calls, so I include the current time in Mills as a long variable in every post.
The problem started when I changed the clock of the phone to some time in the future. (In order to simulate the reminder alarms).
With the time set in the future, I synced the data a couple times.
But when I set the clock back to the current time, no calls are made to the onDataChanged() method.
Only when I set the clock back to the future, it correctly calls the method.
Even rebooting my emulators, doesn't solve the issue.
Any ideas where my error comes from?
I can expect my phone to keep living in the future...
Related
I've recently started to have odd time related things happen on my HD2. Alarms set for 4:45, for instance, go off at 3:45 (not always; just occasionally). With my local time set to US Central Daylight Savings, times for other zones, including Eastern in the US and Central America are off by an hour (fast).
Anyone have an idea of what settings I should check?
The real oddity is that these times change from day-to-day or even during the same day. Today for instance, the times in other zones were off in the morning, but show correctly this afternoon.
Any suggestions will be appreciated. Thanks in advance.
-Bob-
Is this a custom ROM? I know I've seen several chefs posting changelogs like "Timezone issue fixed, hopefully" lately.
jdwrrzmm said:
Is this a custom ROM? I know I've seen several chefs posting changelogs like "Timezone issue fixed, hopefully" lately.
Click to expand...
Click to collapse
Standard ROM. This morning all times are correct. ??? Can't figure it out.
could it be your pc is causing it? i once came across a situation where the user had chosen 'no' when his pc had asked him 'do you want to automatically adjust for summer time', and he set the pc time manually himself, , but this then sent his phone wacky because it WAS trying to auto adjust, but every time he synced it would move back an hour, and then re adjust when he restarted it (the phone), and so half the time it was an hour different than the PC.
Probably a long shot, but your post brought it to mind.
samsamuel said:
could it be your pc is causing it? i once came across a situation where the user had chosen 'no' when his pc had asked him 'do you want to automatically adjust for summer time', and he set the pc time manually himself, , but this then sent his phone wacky because it WAS trying to auto adjust, but every time he synced it would move back an hour, and then re adjust when he restarted it (the phone), and so half the time it was an hour different than the PC.
Probably a long shot, but your post brought it to mind.
Click to expand...
Click to collapse
I have my PC clock set to automatically adjust for DST. So far today everything is correct. Just plain odd.
Thanks for your reply.
-Bob-
are You experimenting with android? it's my main suspect. on my device I set g-alarm for 5:00 am just to be surprised with alarm at 6:00 am. :/
today I am testing my hd2 again w/o any androboots during the day. we shall see...
just to let You know, today everything was as it should be. ... I don't like android that much anyway...
Hi there,
I live in Australia and today daylight savings for us has just started. We were supposed to put the clocks one hour forward and that is exactly what I did. My time is correct everywhere besides incoming sms messages. They are time stamped exactly an hour behind to what the current time is; i.e my old time. This is a huge inconvenience because when I'm having a conversation via sms, I will send a message and it'll be correctly timestamped and then I'll get a message back time stamped an hour behind, so when I'm looking at the sms messages I have to scroll up to read the newest one received.
I am currently on Tom Codons ROM and a I have just installed the "SMS fix" which I knew wouldn't do anything because Tom Codons ROM is based on the newest ROM available. Is there a way to fix this issue?
Any help is appreciated,
Alex
The way i understand it, the received SMS time-stamp is taken from the network system. Not from the phone clock. At least, that's how it works in our country.
Of all the phone i used, including HD mini, they always work that way. Except a couple of generations of Sony Ericsson feature phones, which would base the time-stamp from the phone's clock. (But the network's time-stamp still show up in the details of the sms.)
Maybe the network needs to adjust their system.
Hey there,
Thanks for your quick reply we shall see if the network systems clock has been changed in the upcoming days.
Thanks
Alex
You're welcome.
Hey all,
I have encountered a similar problem. If I receive 2 SMS of the same contact and I reply, if that all happens in the same minute (and it does ), HTC's Message-stuff puts the messages in the wrong order.
For example, I got an SMS and then I got another, then I reply, HTC will put them in this order:
SMS 1
My Reply
SMS 2
Instead of
SMS 1
SMS 2
My reply
That's because your phone time does not match the network time. Maybe off by a few minutes. Your sent message is stamped with phone time, logically. And received message is stamped with network time. So if you're engage in a continuous exchange, each sent and received messages differ by only a few seconds or minutes, then this kind of incorrect order happens.
Try to sync your phone time with internet time. This will lessen the chances of wrong order. But you can't totally eliminate it 100%. Unless the conversation exchanges happen very slowly (for example, one or both of your compose text slowly), with several minutes gap between each text.
bart3385 said:
That's because your phone time does not match the network time. Maybe off by a few minutes. Your sent message is stamped with phone time, logically. And received message is stamped with network time. So if you're engage in a continuous exchange, each sent and received messages differ by only a few seconds or minutes, then this kind of incorrect order happens.
Try to sync your phone time with internet time. This will lessen the chances of wrong order. But you can't totally eliminate it 100%. Unless the conversation exchanges happen very slowly (for example, one or both of your compose text slowly), with several minutes gap between each text.
Click to expand...
Click to collapse
Thanks for the explanation! I thought it was a bug
You're welcome.
Hey there,
Just wanted to confirm that my problem has been fixed. The network finally decided to change its time, resulting in the received messages to be time-stamped correctly.
Thanks bart for clearing up what was causing it. (I was tempted to hard reset lol...)
Alex
alex2g said:
Hey there,
Just wanted to confirm that my problem has been fixed. The network finally decided to change its time, resulting in the received messages to be time-stamped correctly.
Thanks bart for clearing up what was causing it. (I was tempted to hard reset lol...)
Alex
Click to expand...
Click to collapse
Wow, great! I like how your network respond to customers. Big company responding to individual users. Very good. Total opposite of HTC tech support.
Hey all, the clocks have gone back an hour today to gmt. However my nexus one with cm6.1 is still showing the bst time. I have automatic time selected in settings, so it's supposed to be taking it from the network. I don't want to have to go to manual time selection if possible.
Anyone else seeing this problem?
I'm on O2 and it changed over without any problems.
Not sure if its a phone setting or it comes from the network but either way it worked
Orange here and time changed automatically
Fixed itself
Hmm... After selecting and selecting the automatic time option a few times, it seems to have fixed itself.
I wish out had done it automatically - my alarm went off an hour early!
You can use ClockSync to avoid such problems in the future http://www.appbrain.com/app/clocksync/ru.org.amip.ClockSync
I know that most phones sync without such apps, but I'm a bit OCD about exact time, so I sync my phone daily with atomic clock
Basically, first things first, if there are any Vodafone users in the UK that uses their time servers, can you tell me if you are getting the correct time? Because when I select it, it's always 2 weeks behind for some reason.
Secondly, whenever I pull my battery (for whatever reason), doesn't matter if it's WP7, Android etc, my clock messes up and I need to re-adjust my time and dates.
Just wondering if anyone else had this problem?
TonyCubed said:
Basically, first things first, if there are any Vodafone users in the UK that uses their time servers, can you tell me if you are getting the correct time? Because when I select it, it's always 2 weeks behind for some reason.
Secondly, whenever I pull my battery (for whatever reason), doesn't matter if it's WP7, Android etc, my clock messes up and I need to re-adjust my time and dates.
Just wondering if anyone else had this problem?
Click to expand...
Click to collapse
hi..... i have the same problem like yours.... in andoid or wp7... i´m not using wm6.5
and for now... set time to automatic doesn´t work. if i set the time manually it setup manually after freezes or restarts...
sorry i have no solution for this...
same issue... the time does not "re-sync".
noticed that if I have it connected / plugged in when I remove the battery (to change the SIM) the issues does not happen.
sorry, no solution
turn off the automatic time from the carrier
I'm running the MoDaCo JR5 ROM with no other modifications (rooted as standard etc) but for around 5 days now the calendar prompts from Google Now have been delayed. I have an appointment in my calendar for each day I work (shift rota and I'm horrendous for remembering which start time I'm on) so the first few days running stock, the time to leave reminders were a pleasant surprise. Since flashing the MoDaCo ROM these reminders have been delayed to the point that I'm already half way to work before my phone prompts me to leave.
E.g: Work start time of 7:30am and Google Now cards shows a travel time of 20 minutes. When it was working I would get a prompt 10 minutes before the 20minute time to travel (7am) but now I'm driving to work at 7:25 when it springs up saying I need to leave in 10 minutes!
I can't find any examples of this on the entire forum (or anything on Google for that matter!) Would anyone be able to help? My clock is set correctly btw, and I can't see any other issues what may be causing this so any assistance would be greatly appreciated.
markquinton55 said:
I'm running the MoDaCo JR5 ROM with no other modifications (rooted as standard etc) but for around 5 days now the calendar prompts from Google Now have been delayed. I have an appointment in my calendar for each day I work (shift rota and I'm horrendous for remembering which start time I'm on) so the first few days running stock, the time to leave reminders were a pleasant surprise. Since flashing the MoDaCo ROM these reminders have been delayed to the point that I'm already half way to work before my phone prompts me to leave.
E.g: Work start time of 7:30am and Google Now cards shows a travel time of 20 minutes. When it was working I would get a prompt 10 minutes before the 20minute time to travel (7am) but now I'm driving to work at 7:25 when it springs up saying I need to leave in 10 minutes!
I can't find any examples of this on the entire forum (or anything on Google for that matter!) Would anyone be able to help? My clock is set correctly btw, and I can't see any other issues what may be causing this so any assistance would be greatly appreciated.
Click to expand...
Click to collapse
I have the same behavior on my devices... i'm completely stock and rooted. Galaxy Nexus and Nexus 10.
Since a couple of months the reminders to leave for work(i have an appointment in my calender for every day i go to work) come always after the appointment has started, but show that i had to leave around 30 minutes ago... very strange behavior... i am thinking if being late for work somehow confused the whole algorithm...
Any guesses?
griefman said:
I have the same behavior on my devices... i'm completely stock and rooted. Galaxy Nexus and Nexus 10.
Since a couple of months the reminders to leave for work(i have an appointment in my calender for every day i go to work) come always after the appointment has started, but show that i had to leave around 30 minutes ago... very strange behavior... i am thinking if being late for work somehow confused the whole algorithm...
Any guesses?
Click to expand...
Click to collapse
I'm having a similar problem, and also stock rooted on my GSM Galaxy Nexus. Sometimes the notifications appear as expected (10-15 minutes before I have to leave), and sometimes they appear at or near the time I'm supposed to be there, telling me to leave some time in the past to arrive on time. This is only a recent issue - maybe the last 2-3 weeks, possibly since the update to 4.2.2?
Whatever is causing it, it's very annoying, since about a month before this started happening I stopped adding individual reminders on my calendar events that include addresses, making Google Now the ONLY reminder I receive.
I used to include less specific addresses (like "town high school", or "Tony's Pizza") on my calendar events, so I could just tap on the address in the event for navigation and let Google Maps figure out what I meant, but Google Now doesn't seem to like that too much. Have you done anything similar? I'm wondering if the existence of such events are contributing to the problem.
Google Now is still taking baby steps, it's about 6 major updates away from being moderately useful. There's no way I would depend on it for anything critical, it's still a cute toy that works about half the time.
Sent from my Nexus 4 using xda app-developers app
Google Now completely ignored my most recent appointment. It came and went without Google Now making a peep. Very disappointing.
Same here like all of you.