Database Info

Daylight Savings

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.

Calling Anyone That Can Help: Let's Fix the Timestamp Issues!

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.

SOLVED (kinda): Is Google Blacklisting GMail accounts used on rooted phones?

So here's the situation. I've got a Sprint Hero. I rooted it and installed MoDaCo, and everything was fine. Then I got this spedr.com/1iw9z beta 2.1 ROM just to try out (This ROM doesn't have copy protect apps working).
The problem arose when I went back to my Nandroid backup of MoDaCo (and my backup of the Stock ROM for that matter.) When I did that I couldn't access any protected apps on either stock or MoDaCo.
I thought that maybe this was from the 2.1 ROM but when I wiped and signed in with another GMail account I could view protected apps.
So all that is to say. Has anybody else experienced this problem and if so have you found a way to fix it? I'm thinking about contacting Google, but if they did blacklist my account there may not be much of a point, besides making sure I never get my account unblocked.

ipaq3115 said:
So here's the situation. I've got a Sprint Hero. I rooted it and installed MoDaCo, and everything was fine. Then I got this spedr.com/1iw9z beta 2.1 ROM just to try out (This ROM doesn't have copy protect apps working).
The problem arose when I went back to my Nandroid backup of MoDaCo (and my backup of the Stock ROM for that matter.) When I did that I couldn't access any protected apps on either stock or MoDaCo.
I thought that maybe this was from the 2.1 ROM but when I wiped and signed in with another GMail account I could view protected apps.
So all that is to say. Has anybody else experienced this problem and if so have you found a way to fix it? I'm thinking about contacting Google, but if they did blacklist my account there may not be much of a point, besides making sure I never get my account unblocked.
Click to expand...
Click to collapse
I am not aware of Google blacklisting people, so it's likely a bug. Calling them up might not resolve any problems since they're not bound to helping you if you've broken the warranty on your phone by rooting it, but it can't hurt.

Must be a bug, as mer6 suggested...
I've been running 2.1 ROMs (xROM & CaNNoN202 Complete) on my G1 for a couple weeks and my GMail account has not been locked out.

you have to do a complete wipe and reinstall a rom with all protected apps working...
sometimes its just a screw up
worst comes to worst if u cant get ur apps back...
u can change build.prop files if u knwo how to do all that
or just reset it to stock and sign into the market and then root it again

Yeah, I was inclined to think it was a bug because I haven't been able to find many othere people with the same problem. The thing is I've reflashed MoDaCo 2.2 Fresh 1.1 and I even went back to the latest RUU and tryed to get protected apps before I rooted again and there was still nothing. It doesn't seem like you would be able to get a bug in your Gmail account that would do something like this but I'm not very experianced with all this.
Signing in with another account after a wipe will fix the problem but I've got a few paid apps on this account I'd like to keep.
Changing the build.prop sounds like it might work, can you point me to any places that give any info on that? I've looked around some but so far I haven't seen much.

I doubt if google even cares. After all, they never manufactured any hardware nor do they care on where you use your gmail.
You may use your gmail account while riding a pink pony over the rainbow, for all that they care.

Haha, good point ady.
I think you are right because I just booted up my G1, something I should have already done, with King's 2.1 aosp on it, signed into my account and I can see protected apps.
So now I think I am down to a bug... now to see if I can fix it
If anybody has info on the build.prop file editing that would be helpful, going to look for it some more right now.

Just a quick update for anyone who is interested.
I changed the build.prop file but that didn't work, but just today I thought I would try another 2.1 ROM just for kicks. Sure enough, I flashed damagecontrol and all of my protected apps are back. Strange issue but I don't mind sticking with 2.1 I may go back to a 1.5 ROM just to see if damage control fixed something, or if it is uniqe to 1.5, but for now: Problem solved

This has nothing to do with Google blacklisting Gmail accounts. What's happened is your Market DB has gone out of sync from swapping your account between phones with different apps installed. The DB glitches if your phone and/or account says an app is installed but the apk isn't in /data/app.
It's a known bug on Google Support forums. To avoid I make sure I only have my Google account signed in on one phone at once and do not swap back. Always perform a wipe when changing ROMs. Keeping backups of your APKs with AppManager and using Recovery to both "wipe dalvik-cache" and "fix apk uid mismatch" could be used to solve this, maybe not.
We've all been running rooted phones for ages, Google doesn't care about it.

Fix Bookmarks Order

This is not a new problem but I don't think a fix was ever released. When the official 2.1 for the Sprint Hero was released I noticed that my bookmarks weren't getting saved in the order I had them set at. In other words I would check to have my bookmarks listed in alphabetical order but once the browser was closed and removed from the memory they would not stay that way when I reopened the browser. Though it's not the end of the world it's highly annoying. I remember reading somewhere that this was a known issue as others had noticed and reported it. Months later I've noticed this still hasn't been resolved in any Sense based roms that and was wondering if someone could resolve this.
It wasn't a problem in 1.5 so I imagine there must be some way to fix it.

If you think its the widget try getting the widget from the 1.5 rom and pushing it to your device

Google is still ignoring the MVNO Problem / What can we do?

Hello xda-guys, devs, user and everyone else.
Since I got an Android phone, i startet to love it and still up today I can't imagine to have another mobile OS. When I swapped a few years ago to a MVNO, the pain begun:
When using your Android phone with a MVNO, it is saying that you are roaming. So you have to activate "data usage while roaming", get a lot of annoying warnings and if you live near a border, you can look forward to a very high phone bill.
This issue is only on Android, no Windows phone, no iOS, not even and unbelievable old Nokia does have this problems!
The problem is (well?) known at google since 2009 (!!!) and all over the world, but google is ignoring it:
https://code.google.com/p/android/issues/detail?id=3499
Unfortunately, most people around the world don't even know that this is a problem! Even the manuals from the MVNO's are saying that you just have to activate data usage while roaming, altough they know that this can rise your bill when you live near a boarder... (Or do they want exactley that?!)
I love my Android, but without any hacks or rooting to solve this problem, it is useless!
I don't want anymore to be forced to root my phones and search for a hack, patch or anything else when there is a new version.
Only Samsung implementet it in their firmware which solves this problem. But it can't be that I need to use only Samsung phones in the future?
With upcoming root "problems" of Lollipop and also ART it is getting more difficult to find solutions for that problem.
Maybe here on XDA, there are more people haveing the same annoying problem and are maybe also as fed up as I am about that problem.
So there is my question, what can we all together do, that this problem will be solved once and forever directly by google?!
I can't imagine that this is taking more time then two days of coding by one person sitting on the right place...
Sorry for my bad english and I hope that there are many other people like me sitting there and are also as fed up as I am about that problem. If i start to think about it, I would like to throw my phone away and start useing my brick old Nokias again.... I just can't understand why this problem isn't fixed since years...
PS: If I posted this in the wrong section, I'm sorry. Please move it then to the right section.

Seems that the national roaming issue isn't annoying anyone other?

This is definitely annoying me. My Xperia T had support for my MVNO built in, but my Huawei didn't until the last update (EMUI 3 beta). Xposed framework stopped working after an update, so I couldn't use the National Roaming plugin anymore. I was forced to enable roaming and download an app called network status notification. That way I could at least see if I was using 2g or 3g.
I have no idea how we can ask Google to do something about it, but if someone here on XDA can fix it, why can't Google fix it?
PS: EU roaming option would come in handy too

National roaming improved
Improvement of "National Roaming" plugin
http://forum.xda-developers.com/xposed/modules/xposed-national-roaming-t2420249/page8#post58718130
Testers wanted.

viper2097 said:
Seems that the national roaming issue isn't annoying anyone other?
Click to expand...
Click to collapse
i use the app from this site
https://blog.sprinternet.at/2013/12/android-roaming-statusicon-entfernen-inlands-roaming-mvno/
it works great for me!
it is open source but i don´t know how build apps... if somebody knows how to do the app is more then 1 year old but it works on lollipop and kitkat!
you only need root! no xposed!
direct link to the .apk
http://www.sprinternet.at/uu_wiki/MVNOroaming.apk

Thank you for this tip! I've searched a lot and found only script based solutions or the way via the xposed framework -which I actually do not need!
I'll try this in the evening.

But unfortunately, there is still no solution from google or without root...

That Google ignores it is unbelievable, but due the fact that I have root tyrol made my day with this tipp