I have tried a few different roms and the majority of them display the received date 4 hours in the past and I am not sure what is causing it. I first noticed it in the Don Solari rom and the Freya rom (http://forum.xda-developers.com/showthread.php?t=765247)
I have read through the threads and people have reported it but without resolution. Since this spans multiple roms I figured I would post the issue here. DST is enabled and my time zone is -5 Eastern Time (US & Canada). I have seen the work around for the 2016 date but obviously this isn't applicable however I have applied the patch anyways without resolution.
I may just have to revert to the original rom I was using as I didn't experience the problem with that rom.
Cheers.
Related
hi all
Since i updated my Nexus One manually with the here provided Update 2.3.6. My Nexus One loose WiFi every 10 Seconds. On Google Support they are many Threads about this. For Example :
google.com/support/forum/p/Google+Mobile/thread?tid=3251939ebbad21a3&hl=en
Many users have problem with this annoying bug. I wonder why here is nothing to find about this.
Anyone here with the same Problem since 2.3.6. ?
Can´t understand why no one cares here. The Google support Forum is full of the same complains about WiFi rendered useless by 2.3.6.
Nexus one
Nexus S
all areas
Same Problem after update. WiFi drops every 20 seconds and reconnect.
Is here no one with the same problem ?
I believe its been mentioned in a number of threads...
Happens to me as well, I hope Google addresses this issue.
It isn't that I don't care, but I haven't had the issue with my phone (granted, I am not running stock but am running a CM7 nightly).
I am not sure what good it would be to chime in and say that it isn't happening to me. I think a lot of the consistent xda forum respondents aren't running stock, so they probably aren't having the issue.
I've been using Nokia Lumia 920 for more than three weeks. Everything works fine except GPS at least for myself.
I used to have daily running so I installed an app MapMyRun to record all in my previous device Galaxy S2, and now Runtastic in Lumia 920.
However, when started using Lumia, GPS becomes my nightmere. Not like S2 which GPS is fast to position and very stable, Lumia 920 is always unstable and even hard to position my location. Unfortunately I just have one record that keeps all tracks until now. Think the chip boarded in Lumia 920 is supposed to be same as what I realize in Galaxy S2. Therefore, I don't know what's going on and not sure if anyone else here has encounters the same.
It would be appreciated if someone can raise some suggestions or ideas or just wait for Nokia's update.
Many thanks,
Was having some GPS issues (long time to find GPS signal/location, no tracking once location was changed) since my last hard reset (about 2 weeks ago) but this morning updated to the latest firmware release for my region (Firmware version number 1232.5951.1249.1007) and tested Nokia Maps this morning and it was very quick, so maybe the update did something. I saw a press release a month ago talking about what was getting updating with this firmware update but can't recall if it said GPS in there. It is supposed to stop the random reboots that I am having.
HI,
Ever since i rooted my HTC one m7 2 days ago. i have put 2 different roms on, but im having problems syncing my accounts. i have an error saying "sync is currently experiencing problems. it will be back shortly". never had this before. is there problem with the root or is there a general problem with syncing?
Hi there,
I've had the same problem for over a week now. I have a Samsung Galaxy Fame which is rooted for about a couple of months or so. Therefore I don't believe it is related to the root. I have read hundreds of post and tried ALL of the so called fixes but nothing works. I've even gone back to the stock rom (unrooted) and the problem remains. It seems if you do a search there are thousands of people experiencing this issue but no full proof fix. I'll keep searching.
Hi guys.
Since last week I've been having an issue. My phone ramdomly looses signal for like 10 seconds and it generates a folder named "bd-dumps" with 3 archives on it: ramdump_modem_fw.bin, ramdump_modem_sw.bin and ramdump_smem.bin.
I didn't changed anything on the phone when the problem started. I was running LiquidSmooth ROM (Very nice, BTW), and started noticing this issue. In fact, I just noticed because my phone was lacking memory.
Now, I've been searching about this issue, but none of the solutions have worked for me. Some say is a bad SIM Card, others a bad network, but I am pretty sure that the issue is not about that.
Everytime that I turn on Data services, it happens. When data services are off, it doesn't.
Anybody has have this issue or have any idea what is this about? I attached some screenshots. Thanks!
Edit: I already changed ROMS, flashed Stock with RSD and flashed modem, but the problem still the same.
This is old.
http://forum.cyanogenmod.org/topic/79890-modem-crashes-on-102-nightly-28-sept/
Been happening on CM based roms since 10.2 or before, for me it will only crash while on H+, 2G won't crash. Stock rom doesn't crash. Already tried buying a new SIM card too.
Devs are either unaware/not willing to look into it/not capable of reproducing since it only seems to happen to certain unlucky people, probably related to some types of networks, since my crashes only occur while on certain regions of my country.
On the other hand, if anyone capable enough is willing to look into this, i'd glady crash my phone a thousand times to generate logcats, dumps or whatever is needed to debug this ****, after all, this is a dealbraker for CM, this is a phone after all.
jaweinre said:
This is old.
http://forum.cyanogenmod.org/topic/79890-modem-crashes-on-102-nightly-28-sept/
Been happening on CM based roms since 10.2 or before, for me it will only crash while on H+, 2G won't crash. Stock rom doesn't crash. Already tried buying a new SIM card too.
Devs are either unaware/not willing to look into it/not capable of reproducing since it only seems to happen to certain unlucky people, probably related to some types of networks, since my crashes only occur while on certain regions of my country.
On the other hand, if anyone capable enough is willing to look into this, i'd glady crash my phone a thousand times to generate logcats, dumps or whatever is needed to debug this ****, after all, this is a dealbraker for CM, this is a phone after all.
Click to expand...
Click to collapse
In my case, it does crash on Stock too. That's my problem. I flashed with RSD to Stock and still the same.
I have also tried other ROMs but the problem still the same. Any ideas?
Thanks
Modem still crashes for me on anything not based on stock 4.1.1 / 4.1.2 - That said, latest PAC jbbl 20140825 has had the least, but persistent and consistently crashing at the same intervals.
I came from stock 4.1.1 latest ota to 4.1.2MX then PAC jbbl 20140825, only got about 6-7% signal loss. Where as all other roms 4.2 4.3 and 4.4.x have been similar results in the 20-30% signal loss.
In your case, if you've not realized since, your modem might be bad hardware-wise. Since you say it was working and then started suddenly, even on stock. Stock I get 0% signal loss.
Hi all,
On the 6th of April all my GPS loggings (I happen to be using Strava, but I presume all apps will be equally affected) started reporting all events as if they took place back in 1999. I updated my ROM from RR-N-v5.8.5-20180302 to LineageOS 14.1 for P8 Lite which was just released (thanks to DarkJoker360) - hoping it was going to fix this GPS Week Number rollover event - but sadly it didn't. There is a workaround - but it involves exporting a GPX file, running a script which adds 1024 weeks and then uploading it again.
Any suggestions about getting it fixed?
Thanks a lot
Tomasz.
Hi.
I'm having the same problem but using an old Samsung S3 which I use with Oruxmaps kind of as a GPS navigator.
The problem seems to be in the GPS firmware chip, it doesn't take into account this is the third rollover it thinks it's the second rollover again ( 1999 )
I suppose that firmware will never be updated, so fixes should be in software, be the ROM or in the APP post receiving data from GPS.
I still don't find any ROM which fixes this problem.
tjk123 said:
Hi all,
On the 6th of April all my GPS loggings (I happen to be using Strava, but I presume all apps will be equally affected) started reporting all events as if they took place back in 1999. I updated my ROM from RR-N-v5.8.5-20180302 to LineageOS 14.1 for P8 Lite which was just released (thanks to DarkJoker360) - hoping it was going to fix this GPS Week Number rollover event - but sadly it didn't. There is a workaround - but it involves exporting a GPX file, running a script which adds 1024 weeks and then uploading it again.
Any suggestions about getting it fixed?
Thanks a lot
Tomasz.
Click to expand...
Click to collapse
I know it doesn't help, but if you want good GPS and stable rom, use persona's mod.
I am stuck with exactly the same issue since November 3rd (2019). the date is incorrect, and so my paragliding flight apps will not accept the date as valid. huge problem for me, can't find any solutions so far. seems like almost nobody is talking about this issue.
Can anyone help?