Related
CHEFS: Disregard what I said below. I'm not convinced this is an issue in the ROMs after all. At least not yet. Mods, feel free to move this to the regular Raph forum or wherever's appropriate. Still investigating ...
-----
Hey Chefs -- Looks like at least some ROMs floating around are missing the latest Daylight Savings information. I discovered it using Proven, but since you guys build on one another's work, I'd be surprised if it's not in some of the other ROMs too.
Fix is here:
http://www.microsoft.com/downloads/...92-3142-4473-b435-b514e4b360a5&DisplayLang=en
Full description of the issue is here:
http://forum.xda-developers.com/showpost.php?p=3296818&postcount=2525
Wordsmith9091 said:
Hey Chefs -- Looks like at least some ROMs floating around are missing the latest Daylight Savings information. I discovered it using Proven, but since you guys build on one another's work, I'd be surprised if it's not in some of the other ROMs too.
Fix is here:
http://www.microsoft.com/downloads/...92-3142-4473-b435-b514e4b360a5&DisplayLang=en
Full description of the issue is here:
http://forum.xda-developers.com/showpost.php?p=3296818&postcount=2525
Click to expand...
Click to collapse
WM6.1 roms have this build in. That fix was from wm 5 and 6.
This is the Microsoft Windows Mobile 5.0 and Windows Mobile 6 (Pocket PC and Smartphone) update to address DST related issues in 2008 due to revised Daylight Saving Time laws in many countries.
Click to expand...
Click to collapse
That's what I thought, but the issue I described with my scheduling problem was indeed fixed by installing it.
Maybe something in my setup is an anomoly -- can any one else check on their post-March 8 events and see if they have a similar problem? And then see if this fixes it? It likely only comes up if you create an event in a system that knows the correct DST, then sync it to your phone.
It's possible that my DST information was overwritten somehow by some other software I've installed, but I can't think of what. I'll experiment after a hard reset and see if I get the same problem.
Wordsmith9091 said:
That's what I thought, but the issue I described with my scheduling problem was indeed fixed by installing it.
Maybe something in my setup is an anomoly -- can any one else check on their post-March 8 events and see if they have a similar problem? And then see if this fixes it? It likely only comes up if you create an event in a system that knows the correct DST, then sync it to your phone.
It's possible that my DST information was overwritten somehow by some other software I've installed, but I can't think of what. I'll experiment after a hard reset and see if I get the same problem.
Click to expand...
Click to collapse
It is possible the fix was accidently removed from you rom. Or an older file was used for compatibility.
Stranger and stranger. The issue came back. Reinstalled the cab, it was fixed. Then it came back again (not sure if a soft reset triggered it, or possibly a sync with nuevasync). So probably not a ROM issue after all. I'd invite any mod to move this thread somewhere more appropriate. Still investigating ...
yupp i just looked at mine and it seems to have the same issue. I'm running RRE V4.4
edited
could have happened through outlook sync
I appear to have solved, or at least worked around, this issue by turnign off the option to change time zones and clocks in settings-personal-phone-time zones.
I imagine this is either: Something screwy with AT&T, or an unanticipated issue with AT&T's US settings and the ROM, since the ROM wasn't built specifically for the US (but certainly works on US devices).
I'd also guess that these events might correct themselves once we're actually in the DST period, but appear wrong until then. Probably because AT&T would compensate for the DST on its official clocks, as not all phones are smart enough to just work with the GMT behind the scenes and adjust appropriately.
However, just like before when I "fixed" it with the cab -- timed events have been corrected to their right times. Existing all-day events remain on the wrong day. New all-day events show up on the correct day.
If you believe something is missing from a rom, please post it in the thread for that rom so the chef would actually see it.
I -think- I finally found more on this:
It seems to come up if the phone is both:
1) Set to get Time Zones and clocks from the carrier
AND 2) If the registry setting to automatically change over for DST is turned off (this can be found in the misc. section of Advanced Config).
At least, this combo seems to cause it on AT&T.
If I'm not mistaken, these are both the default settings in the ROM I've been using.
It would come up if you create a time after the DST switchover (March 8) in something that syncs with the phone (in my case, my google calendar). You'd see the entry on the phone be one hour too early after it syncs.
Just a note: I'm still testing to make sure this is really the issue, but it seems to be bearing out so far.
I figure that as long as bugs are being ironed out, this one is worth a try.
As most people have noticed, Rogers networks seem to have SMS timestamping issues that have to do with the network and phone itself. These issues seem to be fixed by replacing the stock Rogers Mms.apk with the stock Google one (since this is what I think HotWeiss did with the HoFo community rom with some help from Nk02). I myself have noticed that the majority of ported Dream roms (such as Cyanogen's mods) also have this issue fixed with no additional tweaking. This leads to two important questions:
1) What makes the two Mms.apk different enough that one suffers from the timestamp issue and the other doesn't? Is is something that can be simply fixed by swapping a few files and resigning, or is it buried deeper in the code?
2) If it is as simple as swapping some files, can we use this knowledge to fix the 4 hour discrepancy that exists in the Hero ports? It seems to be one of the main bugs keeping people from using it.
I myself have been looking into various ways to fix it and have been coming up emptyhanded. Maybe we can use this space to bounce ideas and collaborate to come up with a solution. Please do not use this thread to complain about the timestamp issue. If you have a rom specific problem, post it in that thread. Try to use this space for coming up with ideas on the timestamp issue.
As usual, thanks for all the hard work, and hopefully we can find a solution!
I would really apreciate and suport this issue resolved.
I have a 32b from Vodafone Spain and using portuguese Vodafone but all the sms received are 1h behind.
It's the only thing stoping me from using a Hero rom.
I don't know if it's related, but when I turn on Location options (just wireless, not GPS) it boots my phone's system time back a couple of hours.
Although even when I do that, SMSes still come in stamped with GMT time, so instead of being 4 hours behind, they're six hours behind for that duration.
Is it always four hours? Or is it just GMT? Do people in Vancouver who have this problem have timestamps seven hours behind?
[Edit: System time is okay with location services on now. I'll keep an eye on it. Maybe it's related to the time glitches people were having on Rogers yesterday.]
[Edit the second: Nope. At lunch my time got thrown back by two hours. Fixed itself when I turned off wireless location again.]
I second that too.
I am staying away from all the Hero ROMs because of this issue as well. The only rom that works with no notible bugs is the HoFo ROM, but that's just not HERO. Sure, it's possible to push camera.apk to the Hero ROM, but it's not possible to do the same with the mms.apk file. All that really needs be done is compare the fixed mms.apk file with the Hero one, and find out where it was fixed.
Alright, I did some digging and found a few things. I dunno if this info is useful at all but at least it's a start.
After rooting around in the Android Developers guide, I found there was reference to getTimestampMillis in being used to return the service center timestamp. After dedexing the Hero Mms.odex (no classes.dex in the apk), I could not find any reference to the getTimestampMillis line, but instead found reference to a mTimeStamp in com/android/mms/dom/events/EventImpl.ddx. It also looked like there were references to the local time:
Code:
invoke-static {},java/lang/System/currentTimeMillis ; currentTimeMillis()J
and a reference to another timestamp related thing:
Code:
.method public getTimeStamp()J
.line 67
iget-wide-quick v0,v2,[obj+0x18]
return-wide v0
.end method
So that seems to be what I've found. I'm not saying it means anything, since I know squat about coding in Java, but at least its a start.
This isn't a fix but at least my texts aren't 4 hrs behind anymore. The clock widget shows my city and the current time with the texts stamped correctly.
http://forum.xda-developers.com/showthread.php?t=549291
hope it helps
Well, I dunno if anyone cares anymore, but here is a new update for Rogers Magics direct from HTC that supposedly addresses the original timestamp bug.
http://www.htc.com/ca/SupportDownloadList.aspx?p_id=270&act=sd&cat=2
I have no idea if this does anything for Hero roms. I suppose if there is someone more technical minded, they could extrapolate the fix and apply it to further roms.
Hmm
I have a HTC from Orange (PL) with a hero ROM and me and my half we trade sms's in almost in *realtime.. I'll test right a way again from the Orange website!
If something is going up, I never noticed!!
yes a fix would be nice for us canadians... i use the method origins81 uses but a real fix would be great
Seems to be a ROM update for Rogers on the HTC site. One fix is the timestamp issue.
http://www.htc.com/ca/SupportDownloadList.aspx?p_id=270&act=sd&cat=2
Could this ROM be examined for a fix?
Can anyone put up an alternate link elsewhere, rapidshare or megaupload? I keep getting "Sorry, this software download is not suitable for your device"
Thanks
*No need, you can pick it up from the Rogers website*
So I'm going to ask a dumb question, but does the published HTC source give any insight into fixing the timestamp issues? It's still pretty much the only annoying bug.
Alright, this is a strange one. I'm wondering if anyone else can confirm this, although I bet few have probably noticed it.
I normally update my installed apps by going to the Market app and selecting "My Downloads." Often times I'll see "update available" and then I install the update, which wipes out the previous version.
Last week, I found an app called aTrackDog, which basically is a version tracker for your apps. It goes out and finds new versions and notifies you, so you can go download your updates. It not only follows the market, but also the app developer's homepage, in case they release their update through different mediums. I don't use it to install or uninstall, just track my versions.
This is when I started paying attention to the version numbers of a few apps. For this example, we'll talk about Advanced Task Manager and Pandora. I updated ATM from 3.5 to 3.6, and Pandora from 1.0.0 to 1.1.0. To do this, since the market didn't say there was an update, I uninstalled each app, and then reinstalled from the market. Everything was great, and each app showed its new version, from the splash screen on Pandora, to how ATM was listed in Task Panel, as version 3.6.
I just rebooted my phone because I was getting the 99% uptime thing, and wanted to mess around with killing the messages task to see if that made a difference. Much to my surprise, when my phone restarted, my phone has reverted many of my apps back to older versions.
My Advanced Task Manager now is back to version 3.5, Pandora is back to 1.0.0, and many other apps are affected.
This seems like a MAJOR BUG. Can anyone else confirm this at all?
To recreate this issue, if you have Pandora version 1.0.0 currently, or 1.1.0, uninstall and reinstall it. You then will have version 1.1.1 I believe. Then reboot your phone, and start Pandora back up. Does it still say 1.1.1?
I have found this also happens with Advanced Task Manager, and Mileage. I'm sure there's others, but those are a couple of examples. This has happened to me at least twice that I'm aware of.
EDIT-- Here's three links on other Android forums where someone else is experiencing this same thing.
http://androidforums.com/htc-hero/12577-app-updates-cause-problems-icons-etc.html
http://androidcommunity.com/forums/f41/apps-reverting-to-old-version-27414/#post262526
http://community.sprint.com/baw/message/127189
I've noticed this too. I've really noticed it with NewsRob because it will pop up a message stating " A new version is available", but the Market knows what I downloaded last so it states that there is no update. I was wondering, since I too had Atrackdog installed (not anymore) if it was an issue with that program, maybe an issue with just what version was listed in certain programs (as in some piece of code to display the version number got messed up) or if there really was automatic downgrading going on...
jakeblues55 said:
I've noticed this too. I've really noticed it with NewsRob because it will pop up a message stating " A new version is available", but the Market knows what I downloaded last so it states that there is no update. I was wondering, since I too had Atrackdog installed (not anymore) if it was an issue with that program, maybe an issue with just what version was listed in certain programs (as in some piece of code to display the version number got messed up) or if there really was automatic downgrading going on...
Click to expand...
Click to collapse
I've tried to remove aTrackDog, and I'm still getting the same behavior. I really doubt that it has to do with that app, but rather the people that use that app are more aware of version numbers, and are the ones noticing it.
I'm assuming lots of people have Pandora on this board (or mileage, Advanced Task Manager or NewsRob for that matter) so we need more people to try to reproduce this issue!
What I'm trying now is to uninstall the app (in my case I'm using Pandora as it says the version number on launch) then reboot the phone, and then reinstall, use it to see the new version, and then reboot to see if it gets reverted.
What's the result? IT REVERTED AGAIN. This is definitely a bigger issue than we realize...but WE NEED PEOPLE TO REPRODUCE THIS.
EDIT:
I also emailed Pandora support to see if they can't reproduce the issue or help me figure out what's up.
I also emailed the devs for aTrackDog to see if they can't shed some light on what might be going on. Hopefully they'll be quick to help, so we can squash this biznatch.
I also posted a question in the App Market Google Forum, and hopefully someone at Google will help figure this out. http://www.google.com/support/forum/p/Android+Market/thread?tid=56ff6f465d6e5e34&hl=en
I also reproduced this issue with TEN more apps:
Astro File Manager
Google Sky
Google Voice
Backgrounds
Barcode Scanner
Shop Savvy
Battery Widget
Daily Horoscope
Facebook
Movie Finder
Google, you got some 'splaining to do.
I use Astro to backup files to my SD card. After I reboot I go through all the "red" files (ones where the SD card version is newer than the installed version) and "upgrade" them with the SD card version.
Alas the Market app tends to "lose" the fact I downloaded some of these apps and no longer tracks them for updates
Something is definitely wrong somewhere.
I'm seeing the same issue, I even tried a factory reset and still happening.
You can add to the list:
Touchdown
Sipdroid
I think it is just about all apps. Even if you uninstall and reinstall the latest version seems to revert back to original version you installed for the first time.
Locale...
This happened to me this week with Locale. I had beta .68 and upgraded to beta .69.
A couple of days later, I noticed I was still running beta .68. I thought maybe they had forgotten to update the name in the app itself, but after seeing this thread, I'm betting it's an HTC Sprint Hero bug.
I also re-visited the Android Market to see if I could re-download beta .69, but it didn't recognize that the program could be updated. It must think I'm running beta .69, but I'm pretty sure I'm still rocking beta .68.
Verrrrry strange...
I just reproduced this as well, with AK Notepad.
I had 1.9.3b installed; upgraded to 1.9.4. rebooted; now it shows 1.9.3b again
I'm using modaco's rom with apps2sd setup. Is this happening on stock heros too?
edit:
From what I've been able to gather from Handcent SMS's version changelog and look for in the actual application I have on my phone, it appears that it is only the display of the version that is reverting, not the application itself. I have this issue with Handcent and even the "about" dialog inside the application reports the older version, but I am seeing features and changes that only appear in later versions according to the changelog. We'd need a major update of an application to test this further.
edit2:
grinched from #android on EFNet helped test this on a stock CDMA Hero and was able to replicate it with Barcode Scanner.
lonequid said:
I just reproduced this as well, with AK Notepad.
I had 1.9.3b installed; upgraded to 1.9.4. rebooted; now it shows 1.9.3b again
I'm using modaco's rom with apps2sd setup. Is this happening on stock heros too?
Click to expand...
Click to collapse
<ignore, wrote in wrong thread>
See my fix in
http://forum.xda-developers.com/showthread.php?t=581806
gilroykilroy said:
See my fix in
http://forum.xda-developers.com/showthread.php?t=581806
Click to expand...
Click to collapse
I'm going to root my Hero and give this a shot tonight. A HUGE preemptive THANK YOU!!!!!
This has been driving me nuts!!!
Nathan, you might want to try this one too (maybe first)?
http://forum.xda-developers.com/showthread.php?t=582176
Basically the same thing, but you delete the entire cache directory instead of just the broken ones one at a time. The cache is recreated after you reboot.
mercado79 said:
Nathan, you might want to try this one too (maybe first)?
http://forum.xda-developers.com/showthread.php?t=582176
Basically the same thing, but you delete the entire cache directory instead of just the broken ones one at a time. The cache is recreated after you reboot.
Click to expand...
Click to collapse
Just an FYI, I'm married, but I friggin love you guys!! This is why XDA is my favorite place. Such a wealth of knowledgeable and great people. Thanks again everyone, MUCH MUCH appreciated.
Ooops... forums are acting buggy.
I have a Xoom MZ604 WiFi purchased in Canada. I have updated the OS to HC 3.2 US version. My rationale for this is that I will never be satisfied with the device remaining "Canadian" as any updates will always be delayed or, maybe, never will happen (ref. Motorola Dext/Cliq) for those of us outside of the US. I am not going to waste any more of my time with what might be a semi-orphaned Canadian version of the OS.
The upgrade to HC 3.2 appeared to go without a hitch. However, I have a few questions. If anyone can offer some answers, I would be most grateful.
1. I have found little difference in the stock browser performance when using HC 3.2 compared with HC 3.0.1. Many people seemed to have reported major improvements. I haven't seen these. I am wondering why. I was not really dissatisfied with the browser performance under 3.0.1, though occasionally there were pauses of a few seconds when pages were being loaded. Is my experience unusual?
2. In fact, I have found what seems to be a degradation of stock browser performance under HC 3.2 in two respects. First, I have noted that, when a page is reloaded, e.g. when scrolling, I often see blank rectangles of the screen (maybe 10%), which don't load immediately. There is a delay of a second or so before the page is completely written with these last few pieces of the screen. Second, there have been a few occasions when a browser page has disappeared without me doing anything, and the screen returns to the desktop. When this happens, there is no forced close indication, the web-page just disappears. I have found this to happen particularly on forum.xda-developers.com web-pages, though it may happen on others as well.
3. I noticed this morning that my personally installed apps had disappeared from the desktop. I was just left with the standard ones that come with a clean device. These apps were still in the My Apps list and I restored them by dragging them to the desktop. I am wondering if anyone else has seen this happening.
4. I want to be able to use micro-SDHC cards with full R/W capability and would also like to have a fully functional micro-USB capability (via an OTG cable, which I have), which can see flash-drives formatted with FAT32. For these functions to work, I understand that I will have to use the Tiamat kernel and be rooted. However, what is making me hesitate is that I have seen several notices relating to this, saying that the procedure should only be attempted with US WiFi Xooms. I am speculating that this may simply be because these procedures were tested on a US WiFi Xoom. Can somebody please confirm for me that it should be just as safe to update to rooted/Tiamat with a Canadian-purchased Xoom as it would be for a US one and that the instructions will be the same.
Thank you.
Gordon
Gordon1M said:
I have a Xoom MZ604 WiFi purchased in Canada. I have updated the OS to HC 3.2 US version. My rationale for this is that I will never be satisfied with the device remaining "Canadian" as any updates will always be delayed or, maybe, never will happen (ref. Motorola Dext/Cliq) for those of us outside of the US. I am not going to waste any more of my time with what might be a semi-orphaned Canadian version of the OS.
The upgrade to HC 3.2 appeared to go without a hitch. However, I have a few questions. If anyone can offer some answers, I would be most grateful.
1. I have found little difference in the stock browser performance when using HC 3.2 compared with HC 3.0.1. Many people seemed to have reported major improvements. I haven't seen these. I am wondering why. I was not really dissatisfied with the browser performance under 3.0.1, though occasionally there were pauses of a few seconds when pages were being loaded. Is my experience unusual?
2. In fact, I have found what seems to be a degradation of stock browser performance under HC 3.2 in two respects. First, I have noted that, when a page is reloaded, e.g. when scrolling, I often see blank rectangles of the screen (maybe 10%), which don't load immediately. There is a delay of a second or so before the page is completely written with these last few pieces of the screen. Second, there have been a few occasions when a browser page has disappeared without me doing anything, and the screen returns to the desktop. When this happens, there is no forced close indication, the web-page just disappears. I have found this to happen particularly on forum.xda-developers.com web-pages, though it may happen on others as well.
3. I noticed this morning that my personally installed apps had disappeared from the desktop. I was just left with the standard ones that come with a clean device. These apps were still in the My Apps list and I restored them by dragging them to the desktop. I am wondering if anyone else has seen this happening.
4. I want to be able to use micro-SDHC cards with full R/W capability and would also like to have a fully functional micro-USB capability (via an OTG cable, which I have), which can see flash-drives formatted with FAT32. For these functions to work, I understand that I will have to use the Tiamat kernel and be rooted. However, what is making me hesitate is that I have seen several notices relating to this, saying that the procedure should only be attempted with US WiFi Xooms. I am speculating that this may simply be because these procedures were tested on a US WiFi Xoom. Can somebody please confirm for me that it should be just as safe to update to rooted/Tiamat with a Canadian-purchased Xoom as it would be for a US one and that the instructions will be the same.
Thank you.
Gordon
Click to expand...
Click to collapse
Hi, since you flashed the US WIFI image, I think it is now, for all intents and purposes, a US Xoom. Root to your heart's content. You will love the Manta Ray Rom, and I use Dolphin HD browser most of the time, and I also use ADW Ex as my launcher. Scrolling between pages (I have 6 of them) is super smooth and the launcher bar is customizable and really handy. There are many really nice themes, too.
Thanks for the reply okantomi. You've added to my confidence to proceed! I think that I have seen that I might have to go back to HC 3.1 before rooting and proceeding to Tiamat, but I am not sure. Still researching.
Thanks again.
Gordon
[Edit] Just noticed the thread http://forum.xda-developers.com/showthread.php?t=1170774. I guess I can go straight from stock HC 3.2 to Tiamat.
Anyone else having issues with chrome not opening all the way?
http://imgur.com/Mp68AJf
Have to minimize it then goto recent apps to get it to load full.
http://imgur.com/86l0E4N
I realize this may not be solely a OPO issue but it's starting to really annoy me.
First started on mandi rom and now most roms I've tried since then.
Looks like your running lollipop? Isn't that a feature in Chrome? That tabs appear as separate apps in the system wide task manager? Correct me if I'm wrong. If so, I have no idea what your problem is, but I haven't experienced it.
Should be fixed in the next update. :good:
https://code.google.com/p/chromium/issues/detail?id=423685
https://productforums.google.com/forum/m/#!topic/chrome/QYjPMToRj-Q
Cheers!
Haha. Figures. Been going through roms like underwear lately and thinking I'm crazy.
Install Chrome Beta, the fix has already been applied but only on the Beta channel.
https://play.google.com/store/apps/details?id=com.chrome.beta&hl=en