Obsolete
Status Update
Comments
ca...@gmail.com <ca...@gmail.com> #2
find attached files for reproducing:
gd...@gmail.com <gd...@gmail.com> #3
Could this update be also related to GSM operators (network provider)?
Although my system is LG G2 Android 4.4.2 and automatic date & time and time zone selected
( in other words
. use network-provided time option checked and
. use network-provided time zone option checked)
system time zone is automatically set to GMT+03:00, East Africa Time as of October 30.
Although my system is LG G2 Android 4.4.2 and automatic date & time and time zone selected
( in other words
. use network-provided time option checked and
. use network-provided time zone option checked)
system time zone is automatically set to GMT+03:00, East Africa Time as of October 30.
ch...@gmail.com <ch...@gmail.com> #4
The problem is about the timezone database of Android. Google should update the timezone DB accordingly.
For Istanbul timezone should be "GMT+03:00", currently it shows "GMT+02:00".
My device is HTC One M8 and it has the same issue.
For Istanbul timezone should be "GMT+03:00", currently it shows "GMT+02:00".
My device is HTC One M8 and it has the same issue.
ay...@gmail.com <ay...@gmail.com> #5
I have same problem with General Mobile 4G (Android 7.0 with November 5, 2016 security patch)
[Deleted User] <[Deleted User]> #6
I also have the same issue with my GM5 Plus (Android 7.0 with latest security patches)
[Deleted User] <[Deleted User]> #7
This problem seems to be Android related, not brand. My HTC 10 does the same.
Looks like the system time zone database needs updating.
Shouldn't be a big deal to fix - but it's been more than a month and no go.
Looks like the system time zone database needs updating.
Shouldn't be a big deal to fix - but it's been more than a month and no go.
tr...@gmail.com <tr...@gmail.com> #8
I had the same problem with a galaxy s6.
It happened on October 30th, the day I had a plane to catch. Luckily had a friend with iOS.
It happened on October 30th, the day I had a plane to catch. Luckily had a friend with iOS.
se...@gmail.com <se...@gmail.com> #9
Is preparing a small patch and distributing to all android users a big issue? If Apple & Microsoft could do it so easily, why can't google fix it as well? It's been more than a month and still no fix.
[Deleted User] <[Deleted User]> #10
Apart from Nexus devices, these changes originate from Google and propagate to OEMs (Sony, HTC, LG, Samsung, Huawei etc), which in turn distribute the patches.
But first Google must issue it. Google does not control Android the way Microsoft or Apple control their platforms.
But first Google must issue it. Google does not control Android the way Microsoft or Apple control their platforms.
ul...@gmail.com <ul...@gmail.com> #11
Are we still waiting for the patch?
dn...@google.com <dn...@google.com> #13
Please check the issue on android 7.1.1 and let us know the result.
If issue reproduces please share the bug report for the same.
Android bug report:
After reproducing the issue, navigate to developer settings, ensure ‘USB debugging’ is enabled, then enable ‘Bug report shortcut’. To take bug report, hold the power button and select the ‘Take bug report’ option.
Note: Please upload the files to google drive and share the folder to android-bugreport@google.com, then share the link here.
If issue reproduces please share the bug report for the same.
Android bug report:
After reproducing the issue, navigate to developer settings, ensure ‘USB debugging’ is enabled, then enable ‘Bug report shortcut’. To take bug report, hold the power button and select the ‘Take bug report’ option.
Note: Please upload the files to google drive and share the folder to android-bugreport@google.com, then share the link here.
dn...@google.com <dn...@google.com> #14
Please provide the information requested in comment #13 to investigate this issue further.
om...@gmail.com <om...@gmail.com> #15
Fixed thanks
dn...@google.com <dn...@google.com> #16
As per the comment #15 . Closing this issue.
ca...@gmail.com <ca...@gmail.com> #17
I think you should not close the issue since the suggestion at comment #13 is only for 7.1.1, I'm using 6.0.1 and Istanbil is shown still in GMT+2, see the attached file, thanks.
dn...@google.com <dn...@google.com> #18
Can you please mention the device name which is running on 6.0.1?
ca...@gmail.com <ca...@gmail.com> #19
It's LG G4 with Android 6.0.1, just had software updates for motherboard change of the device with common issue in this type
mw...@gmail.com <mw...@gmail.com> #20
I still have the problem istanbul being gmt+2 on hwawei p9lite android 6.0
al...@gmail.com <al...@gmail.com> #21
I have same problem at my Samsung Note 5 too.
[Deleted User] <[Deleted User]> #22
I confirm that it's solved in my General Mobile 5 Plus with Android 7.1.1.
ca...@gmail.com <ca...@gmail.com> #23
I see most of the folk here is having the issue on their personal devices, for that you can simply change the timezone to GMT +3 like Bahrain
On the other hand, for the ones having the problem in app-wide you need to do some workaround as getting current time and add or extract hours. For further help you can contact to me, I've done it in two of our apps :)
On the other hand, for the ones having the problem in app-wide you need to do some workaround as getting current time and add or extract hours. For further help you can contact to me, I've done it in two of our apps :)
ay...@gmail.com <ay...@gmail.com> #24
So you guys telling me that the problem solved for only 0.3% percent of all users?
Description
Steps to reproduce:
(LG G4 Android 6.1)
- Open Settings > General > Date & Time
- Uncheck both "Auto-date&time" and "Auto-time zone"
- Change the date which will be after 30 Oct like 9 Nov
- It shows Turkey in GMT+2, but it should stay at GMT+3