Hi!
I've finally updated to android pie with ACIP 14.0. Everything runs smooth and a lot of issues that I was experiencing caused by my old ROM (CM11) are solved now and a lot of new apps are finally working as expected.
The only issue that I was hoping also to solve with the upgrade to pie, are the date and time problem related with the GPS after the rollover. In the part of Europe where I'm living the Rollover took place the 3th of November. Since then, when I get a fix, the time stamps read by the GPS sensor are off by 19 years. That is not a huge issue, because the navigation is working, but is preventing me to use some tracking app, especially Strava.
I've tried to reset the GPS with the GPS Fix app, and also to clear cache and data, but nothing seems to work.
Is there someone out there who is experiencing the same problems? Does anyone have an idea how to solve it?
Many thanks,
Valde
Valde_91 said:
Hi!
I've finally updated to android pie with ACIP 14.0. Everything runs smooth and a lot of issues that I was experiencing caused by my old ROM (CM11) are solved now and a lot of new apps are finally working as expected.
The only issue that I was hoping also to solve with the upgrade to pie, are the date and time problem related with the GPS after the rollover. In the part of Europe where I'm living the Rollover took place the 3th of November. Since then, when I get a fix, the time stamps read by the GPS sensor are off by 19 years. That is not a huge issue, because the navigation is working, but is preventing me to use some tracking app, especially Strava.
I've tried to reset the GPS with the GPS Fix app, and also to clear cache and data, but nothing seems to work.
Is there someone out there who is experiencing the same problems? Does anyone have an idea how to solve it?
Many thanks,
Valde
Click to expand...
Click to collapse
Hi.
Thanks for your hint. I didn't noticed this issue so far but can confirm it with lineage 17. It seems to be really fresh.
I don't have much hope this can be fixed easily. At first we have to find out where the date gets calculated wrong. Most likely this happens in the gps chip firmware. Then we have nearly no chance.
Maybe doing the calculation on our own in a middle layer (kernel driver or HAL).
But at first some research is needed to make well-grounded statements.
115ek said:
Hi.
Thanks for your hint. I didn't noticed this issue so far but can confirm it with lineage 17. It seems to be really fresh.
I don't have much hope this can be fixed easily. At first we have to find out where the date gets calculated wrong. Most likely this happens in the gps chip firmware. Then we have nearly no chance.
Maybe doing the calculation on our own in a middle layer (kernel driver or HAL).
But at first some research is needed to make well-grounded statements.
Click to expand...
Click to collapse
Hi 115ek,
Thanks for your reply. Do you know if Sony is still supporting the Z1c for major issue? I was looking for a firmware upgrade related to this problem, but I didn't find anything. If i search the Xperia website with my IMEI for updates it states "Sorry, the information is currently not available. Please try again later. " . Do you have any hint?
Thanks,
Valde_91 said:
Hi 115ek,
Thanks for your reply. Do you know if Sony is still supporting the Z1c for major issue? I was looking for a firmware upgrade related to this problem, but I didn't find anything. If i search the Xperia website with my IMEI for updates it states "Sorry, the information is currently not available. Please try again later. " . Do you have any hint?
Thanks,
Click to expand...
Click to collapse
No, forget about sony support. The device is too old.
We have to find a solution on our own. Live with it, fix it or buy a new device.
Most likely even sony can't do anything about it because they also just bought the GPS chip + its firmware from a supplier...
115ek said:
No, forget about sony support. The device is too old.
We have to find a solution on our own. Live with it, fix it or buy a new device.
Most likely even sony can't do anything about it because they also just bought the GPS chip + its firmware from a supplier...
Click to expand...
Click to collapse
Hi,
Could be spoofing app a workaround for this issue? I've tried many of the one available on the market, but I didn't find any that allows to spoof the date and time but not the position. Does anyone have any idea if there is an app out there that could work?
Many thanks!
Although the issue was fixed some weeks ago, I think it's worth to mention it here. Maybe someone else will stumble over this thread later on.
The issue is described here and affects many legacy devices.
@jason972000 fixed it by editing the GPS HAL. Basically the missing 1024 weeks are added to the timestamp, when it is considered to be lying in the past. The fix for amami (Z1 compact) can be found here.
LineageOS 16.0 and 17.1 as well as AICP 15.0 now include the fix and will show a correct timestamp.
Related
There's a problem with gps on my phone Samsung FOCUS ,Gps is not working even in the open sky, tried several app like -> gpsinfo,wingps and others like RunKeeper,RunSat etc
Phone is Dev unlocked as well as Interop Unlocked with internet sharing enabled.
The update was done using forced method.Updated from stock firmware->7008->7032->7043->7720.68.
Versions ->
Diag app-> 0103
firnware - 2103.11.8.1
hardware rev. no. - 3.1.0.7
Bootloader ver. - 5.8.0.2
radio software ver. - 0.0.0.3
Please help?
Microsoft released a statement saying they don't blame people or doing the forced update... it doesn't do anything bad to the phone so I don't think that's the issue. You might want to try rolling it back to nodo, checking your gps and then reloading mango. if still no go. Hardware issue maybe??
Issue solved,thanks anyway
So, what was the problem?
Don't know, flashed mango again.That's it.
Gps locked in under 10 sec inside the room.
Hmm. My GPS will find my location fine but getting directions is terribly slow now and turn-by-turn will always just say "can't connect to satellites." Now I'm wondering if a rollback and updating again to Mango will fix this.
I'm on official Mango on an AT&T Focus (and I didn't force the update), and I'm having problems just like the previous posters with GPS fixes and 'can't connect to satellite' errors when trying to get directions.
I found a solution by going into another application that uses GPS, getting a GPS fix in there, then going back into the maps. The program I use is "GPS & GPX Logger." After that finds the satellites, the maps work as they should.
For background info, my phone went from NoDO->Mango Beta 2 (7661)->Mango Beta 2 Refresh (7712)->Unforced official Mango including "Samsung Update"
I tried the turn-by-turn again this morning and it actually worked. This is the first time it has since updating last wk. I didn't change a thing, so I have no idea why it work suddenly.
GPS works on Samsung Focus even after Tango update
I own samsung focus 1.3 (AT&T). I purchased it in the beginning of Sep. 2012 (quite late). As soon as I got the phone, I connected it to Zune for updates. After having updated to 7.10.7720.68, I started using the phone. The GPS did not work. I then updated it to 7.10.8773.98 with the hope that updates may make GPS working. I tried all possible tricks available on XDA as well as other forums. I tried following tricks with various permutation & combination:
(i) Pulling out the battery for 30 minutes.
(ii) Changing the MOLR CP/UP setting in GPS diagnostic to UP and CP (one by one),
(iii) Rebooting the phone with location off & again rebotting with location on
(iv) Apps like GPS info & others
& few more which I do not recall now.
After having tried for about a month, I reverted back to original OS version 7.0.7004.0 just to ascertain the availability/ functionality of GPS hardware as on some of the forums I read that their GPS stopped working after No-Do updates. The GPS did not work even after trying all above tricks on 7.0.7004.0 version of OS.
Finally I accepted my GPS to be faulty or not being there and again updated to latest OS version.
One day I read on some forum that putting off the location service & then switching on makes GPS working. Wow, I tried it today, IT WORKED. On bing map it locked, initially with a bigger circle & then reducing down to a dot. In areas covered with thick trees or high-rise buildings, the circle used to become bigger but again in clear sky area it used to reduce down to dot. I am keeping my fingers crossed. Let me observe for some more days to ascertain that this trick actually works.
Those who have not been able to make their GPS working with other tricks, please try this & let us have your feedback on this forum/ thread.
GPS not reliable
In continuation to my previous post, the working of GPS is not reliable. It sometimes works very fine & some times doesn't work at all during the entire journey of 15 Km. You cannot depend on this GPS for navigational aid. It appears to be some software issue. But anyway, I am happy that my GPS is not faulty. Hoping for some fix in future which will make GPS work reliably.
A. K. Jain said:
In continuation to my previous post, the working of GPS is not reliable. It sometimes works very fine & some times doesn't work at all during the entire journey of 15 Km. You cannot depend on this GPS for navigational aid. It appears to be some software issue. But anyway, I am happy that my GPS is not faulty. Hoping for some fix in future which will make GPS work reliably.
Click to expand...
Click to collapse
GPS working perfectly for me with my Nokia 800 with Nokia Drive.
Some cars have some sort of coating on the windscreen which sometimes blocks GPS, although I wouldn't expect that to be on US cars.
gilesjuk said:
GPS working perfectly for me with my Nokia 800 with Nokia Drive.
Some cars have some sort of coating on the windscreen which sometimes blocks GPS, although I wouldn't expect that to be on US cars.
Click to expand...
Click to collapse
The issue is not related with car glasses as I have tried a lot in clear sky on foot. The issue seems to be specific to Samsung focus drivers.
So I've had this problem as far back as I've been trying the various builds of xdandroid where if my T-mobile TP2 is in full sleep and it receives a call it fails to wake properly causing it to lose the ability to accept or make calls until rebooted. It's been there regardless of build version, ril version, rootfs version, and kernel version. Pretty much the only thing I haven't tried is changing the radio rom since I figure that shouldn't be where the problem lies since I'm using the same radio version as the guy who designed the current ril according to his XDA profile.
I've tried dealing with the xdandroid guys directly but they refuse to accept it's a problem with their code instead of my phone despite the fact everything else the should work in android works flawless and no such problem exists in Winmo. So I come to you the public of the XDA forums does anyone else have this problem with this model of TP2 so I can point out it's not my phone but in fact an issue with their code. I've also tried contacting highlandsun directly via email and PM with no response.
Oh and before anyone suggests sending them log dumps I did that. I even pointed out to them exactly where the ril fails during the incoming call and how when I attempt to make outgoing calls before a reboot how the oncreate function for the new call never finishes because the ril has gone screwy.
If you know where the issue is occurring, then why not fix it?
You say you've sent logs, yet you don't attach them here.
You say you know where the issue occurs, but don't document it here, for everyone...?
If you honestly feel there's an issue with the code (which we all know there are still many) then please, submit a patch. Improvements are always welcome, there's GIT repo's which you can make merge requests and everything.
This also belongs in the Android section, but it seems you don't have enough posts to post in that section...
arrrghhh said:
If you know where the issue is occurring, then why not fix it?
You say you've sent logs, yet you don't attach them here.
You say you know where the issue occurs, but don't document it here, for everyone...?
If you honestly feel there's an issue with the code (which we all know there are still many) then please, submit a patch. Improvements are always welcome, there's GIT repo's which you can make merge requests and everything.
This also belongs in the Android section, but it seems you don't have enough posts to post in that section...
Click to expand...
Click to collapse
First of all I'm not looking for help fixing the problem from the forum at large. I'm looking for additional people with the error in order to prove it's not unique to my phone, something that you personally tried to claim on the bug tracker.
Second I know enough to be able to diagnose where the problem lies but unfortunately cell phones aren't my specialty so I have neither the knowledge of the android source code nor the code for interacting with cell phone hardware necessary to fix it or else I would have long before approaching the team with the problem. I figured giving you guys all the necessary details on the issue including all the dumps would have been enough to get it fixed in a time frame faster then I could have done it myself since you already know the system quite well but instead you blew off the issue claiming that since it doesn't happen to all Rhodium 210's it can't be a problem with the code and it must be my phone.
If you'd like me to resubmit the bug to the bug tracker I can do so with a fresh set of logcats and dmesg with the problem spots highlighted to make them easy to find along with any other details you might need about firmware versions, running software and condition under which android was launched since we both know having certain things on in Winmo will effect how things run in android.
Daemeon6.7 said:
First of all I'm not looking for help fixing the problem from the forum at large. I'm looking for additional people with the error in order to prove it's not unique to my phone, something that you personally tried to claim on the bug tracker.
Second I know enough to be able to diagnose where the problem lies but unfortunately cell phones aren't my specialty so I have neither the knowledge of the android source code nor the code for interacting with cell phone hardware necessary to fix it or else I would have long before approaching the team with the problem. I figured giving you guys all the necessary details on the issue including all the dumps would have been enough to get it fixed in a time frame faster then I could have done it myself since you already know the system quite well but instead you blew off the issue claiming that since it doesn't happen to all Rhodium 210's it can't be a problem with the code and it must be my phone.
If you'd like me to resubmit the bug to the bug tracker I can do so with a fresh set of logcats and dmesg with the problem spots highlighted to make them easy to find along with any other details you might need about firmware versions, running software and condition under which android was launched since we both know having certain things on in Winmo will effect how things run in android.
Click to expand...
Click to collapse
Pretty hard to fix an issue that only you can reproduce.
hyc hasn't had much time at all for XDAndroid lately. C'est la vie. He is the best one to look at it, but PMing him about the problem over and over isn't going to do any good. The bug you already submitted is fine. I don't know what else to tell you other than good luck.
arrrghhh said:
Pretty hard to fix an issue that only you can reproduce.
hyc hasn't had much time at all for XDAndroid lately. C'est la vie. He is the best one to look at it, but PMing him about the problem over and over isn't going to do any good. The bug you already submitted is fine. I don't know what else to tell you other than good luck.
Click to expand...
Click to collapse
Hence why I'm looking for more people with the problem. Once I find them then I can start searching for commonalities to help make it easier to fix by ruling out causes or if lucky find a specific trigger such as how having bluetooth on in Winmo will cause android not to go into full sleep.
Also only tried both once so as not to needless fill up his inbox. I figured he'll read one or the other eventually unless he's prone to deleting things without reading them.
Daemeon6.7 said:
Hence why I'm looking for more people with the problem. Once I find them then I can start searching for commonalities to help make it easier to fix by ruling out causes or if lucky find a specific trigger such as how having bluetooth on in Winmo will cause android not to go into full sleep.
Click to expand...
Click to collapse
I wish you luck.
i have the same problem too... xdandroid 2.3, thaidai nice, everything works fine, but when i click Call End, the htc sleeps, and it suck for wake again.
htc Diamond
i find this on google, i think solve the problem, but i'm a android newbie ^^
This same thing was happening to me as well, up until a week ago. I had the latest incremental updates on FRX 7.1 , AT&T TILT 2 (Rhodium 300).
In addition, I was also seeing very bad performance lag, freezes, often eventually leading up to a reboot, and other issues which I chalked up to being I/O related whenever more than 3 or 4 large programs were running at once (such as Facebook, Google Maps, Browser, and Market 3.0).
After doing some research, I found out that my PNY 16GB Class10 MicroSD Card may be to blame since Class 10 cards (and maybe Class 6) have built-in hardware read-ahead, and doing any kind of Random Access I/O on them like these Android builds is less than ideal...
So I ditched the Class 10 card (gave it to my wife to use on her BB Torch) went up to Walmart and bought the Class4 Sandisk for only $29, formatted it in the same way with the HP USB FW format Tool using the card's native cluster size (32K), copied all files over as-is and sure enough using, the exact same installation, every last stability and performance issue has completely gone away. Froyo has been running rock-solid for three days now, and the call-answer bug isn't happening anymore either!
Hello friends,
since June 19th I'm having severe issues with location accuracy on my OP3. I'm running the most recent sultan Lineage 14.1 build from June 15th, flashed it on June 17th. On 17th and 18th location was fine, since then it became inaccurate (I'm a daily ingress player). I did not make any changes to phone settings or setup between flashing the rom and the location service going bad. Then I went through different firmware files from https://forum.xda-developers.com/oneplus-3/how-to/radio-modem-collection-flashable-zips-t3468628 (Open Beta 16 through 18, 4.1.6 builds) without any improvement. Also cleared cache, reverted to the previous sultan build, all to no avail.
I have all possible location services enabled and I'm outside, consistently maintaining a lock with about 6 to 8 GPS satellites and 2 to 4 GLONASS satellites according to "GPS Status and Toolbox" (https://play.google.com/store/apps/details?id=com.eclipsim.gpsstatus2&hl=de). I tried re-downloading aGPS data through that app as well as re-calibrating everything it allowed me to but even then and with those 10+ satellites, I'm seeing location error of +-70m or even more. Also, I'm moving around in an area with buildings not higher than 2 floors or even in small parks.
In Ingress, I'm drifting from one side of the street to the other, wrongly going into side alleys, not moving at all for several minutes, and so on. Before June 19th I could effortlessly navigate through the game with pretty much perfect accuracy, now I have problems accessing portals I'm standing on top of for 2+ minutes.
I'll attach some screenshots of GPS Status app from today. You can see errors of 30+ and 70+ meters with 14 satellites available. When taking those screenshots, Ingress was basically unplayable. I'd be grateful for any input on how to tackle this issue.
Does the same thing happens if you use the previous build? If the answer is yes, then there's something wrong with the June 15th build.
You can also try with the latest OxygenOS stable or official LineageOS to see if it's a ROM or hardware problem.
Download https://play.google.com/store/apps/details?id=com.chartcross.gpstest&hl=de and then go to the 3 Dots> AGPS > Clear and update
Thank you both for your input!
S4turno said:
Does the same thing happens if you use the previous build? If the answer is yes, then there's something wrong with the June 15th build.
You can also try with the latest OxygenOS stable or official LineageOS to see if it's a ROM or hardware problem.
Click to expand...
Click to collapse
I reverted to the previous build but the issue remains. I plan on eventually trying OxygenOS if I can't find another solution. This will have to wait until next week though. Not enough spare time right now.
cheptii said:
Download https://play.google.com/store/apps/details?id=com.chartcross.gpstest&hl=de and then go to the 3 Dots> AGPS > Clear and update
Click to expand...
Click to collapse
I think that's the same thing that "GPS Status and Toolbox" does. Still, I'll give it a shot and test during lunch break.
I used to get erratic gps info when i was near high tension electric line...
HI,
i've also bad signal GPS but with FASTERGPS ( https://play.google.com/store/apps/details?id=org.fastergps&hl=fr) i've solved the problem.
But i'm on citrus CAF i hate LOS
Ted
halleyrokz said:
I used to get erratic gps info when i was near high tension electric line...
Click to expand...
Click to collapse
As I've been living and playing in the area for years, I doubt this issue is about external influences
teddybear3k said:
HI,
i've also bad signal GPS but with FASTERGPS ( https://play.google.com/store/apps/details?id=org.fastergps&hl=fr) i've solved the problem.
Click to expand...
Click to collapse
The app you recommended doesn't seem to be able to change the gps.conf file on my phone. I made the NTP server change manually, though. Sadly, I can't see any improvement.
I just don't get what's wrong. It has to be something about my phone or how it processes the data. I know that GPS has some leeway, but I have a lock 12 satellites and only 70m accuracy. I can't comprehend how this is even possible. :crying:
Silkeyway said:
As I've been living and playing in the area for years, I doubt this issue is about external influences
The app you recommended doesn't seem to be able to change the gps.conf file on my phone. I made the NTP server change manually, though. Sadly, I can't see any improvement.
I just don't get what's wrong. It has to be something about my phone or how it processes the data. I know that GPS has some leeway, but I have a lock 12 satellites and only 70m accuracy. I can't comprehend how this is even possible. :crying:
Click to expand...
Click to collapse
--> You must be to root. This soft modify without error my 'gps.conf'.
Despite an improvement, I remain decadent of the quality of the GPS. I do Geocaching and I can not rely 100% on my position (20M Margin with 20/25 Sat).
Here is a link from the ONEPLUS forum that talks about this: https://forums.oneplus.net/threads/fix-the-horrible-gps.465819/
OOS 4.1.5 Beta have good result with GPS: http://downloads.oneplus.net/oneplus-3/oneplus_3_oxygenos_openbeta_15/
EDIT : I Forgot --> test to activate only hardware GPS without WIFI, BT, data.... Only GPS --> Go to setting - location.
Regards,
Ted
Silkeyway said:
As I've been living and playing in the area for years, I doubt this issue is about external influences
The app you recommended doesn't seem to be able to change the gps.conf file on my phone. I made the NTP server change manually, though. Sadly, I can't see any improvement.
I just don't get what's wrong. It has to be something about my phone or how it processes the data. I know that GPS has some leeway, but I have a lock 12 satellites and only 70m accuracy. I can't comprehend how this is even possible. :crying:
Click to expand...
Click to collapse
Try some of the fixes in this thread: https://forum.xda-developers.com/oneplus-3/help/gps-issues-t3416544
tnsmani said:
Try some of the fixes in this thread: https://forum.xda-developers.com/oneplus-3/help/gps-issues-t3416544
Click to expand...
Click to collapse
The beter isue is to modify the GPS.Conf manualy, and fastergps make this change automaticaly just selecting continent and land.
I have the same issue with beta18.
If I select location only by gps it works perfect, but if I select high precision (wifi+network+gps) it see satellites but never get a fix.
kakatua20 said:
I have the same issue with beta18.
If I select location only by gps it works perfect, but if I select high precision (wifi+network+gps) it see satellites but never get a fix.
Click to expand...
Click to collapse
Yes, same problem. I use only GPS and work good.
Interesting, I have been having the exact same problem and first noticed it with Ingress. Using a OnePlus 3T running open beta 18 Will try changing GPS mode to device only and see how that goes. I'm sure this only started a week or two ago, it worked well for a while after flashing open beta 18.
Sorry for abandoing my thread for so long. Been on vacation. While on the highway, GPS suddenly died completely, had to take a break to reboot the phone.
After that, I reflashed opengapps because I was bored one evening. Like two days later, it felt like it improved a bit. Playing ingress got easier again, but it's still... "wonky" up to this day, which it wasn't before.
I'll try GPS only mode asap.
i was on AOSPA 7.2 when this issue started, switched over to OOS beta 19 (freedomOS), and now updated to OOS beta 20 (freedomOS), and still this issue persists.
already tried clearing AGPS data once, has anyone figured out a permanent fix?
+1
ALL other GPS apps work.
Just Ingress is fussy.
P.S. Seems like Ingress has a slalom algorithm that manages to navigate around portals and avoiding them for hacks/capture...
Waze, Google Maps, etc. - are SMACK on location.
I'd like Ingress to constantly update it's location, even when screen is off.
Plus, force-keep internet connection alive.
Hi, new on here, looking for help for the following (searching found no solution):
Xtron TE706PL
PX5
Android Oreo 8.0
(let me know if you need more info)
1) A lock screen for the Xtron stock firmware (tried Nova launcher to no avail)
2) WiFi is intermittent (bluetooth is ok), it will work until the car is switched off and then when i switch it back on it stops randomly and won't find any wifi signals (tons in the area). I thought it may be some sort of 'sleep' setting, but it's set to always on under wifi settings. Usually a full reboot of the system activates it again, so possibly a software issue?
I've not seen the WiFi issue you speak of, but it's probably a configuration issue. Have you tried with your phone hotspot rather than random wifi hotspots dotted around?
No idea about a lock screen. Mine doesn't even offer that functionality. Quite frankly, I don't see why anyone would want one lol
skezza said:
I've not seen the WiFi issue you speak of, but it's probably a configuration issue. Have you tried with your phone hotspot rather than random wifi hotspots dotted around?
No idea about a lock screen. Mine doesn't even offer that functionality. Quite frankly, I don't see why anyone would want one lol
Click to expand...
Click to collapse
There's tons of wifi's in the area, my mobile hotspot, my house + 7 other wifi signals. When it's working it picks all of them up, this is without moving. When it's working i can be on the move with my hotspot and it's ok, as soon as i turn the car off and go to start it again the wifi stops working. Xtron are sending a new aerial, but i do believe it's a software issue.
The lock screen would be ideal to secure the unit if it's stolen or whilst the car is being valeted. Even if an external finger print scanner can be programmed, it would be preferable. There must be something out there, would consider a custom firmware if need be.
300cnewbie said:
There's tons of wifi's in the area, my mobile hotspot, my house + 7 other wifi signals. When it's working it picks all of them up, this is without moving. When it's working i can be on the move with my hotspot and it's ok, as soon as i turn the car off and go to start it again the wifi stops working. Xtron are sending a new aerial, but i do believe it's a software issue.
The lock screen would be ideal to secure the unit if it's stolen or whilst the car is being valeted. Even if an external finger print scanner can be programmed, it would be preferable. There must be something out there, would consider a custom firmware if need be.
Click to expand...
Click to collapse
It's definitely a software issue. No amount of aerials are going to fix that issue. I would update to the latest MCU and update.zip. Do you know how?
Wow, do you like live in the Bronx lol? You're aware if someone wants to steal the unit, they could easily factory reset it then your lock screen will do nothing. Not a clue on the external fingerprint scanner. No idea where you take your car to get it valeted either, but most of the time, you sit in the foyer watching while they do it. That is why they have a big glass window at garages/valet places etc.
skezza said:
It's definitely a software issue. No amount of aerials are going to fix that issue. I would update to the latest MCU and update.zip. Do you know how?
Wow, do you like live in the Bronx lol? You're aware if someone wants to steal the unit, they could easily factory reset it then your lock screen will do nothing. Not a clue on the external fingerprint scanner. No idea where you take your car to get it valeted either, but most of the time, you sit in the foyer watching while they do it. That is why they have a big glass window at garages/valet places etc.
Click to expand...
Click to collapse
I believe the MCU is the latest version for GS installed MTCE_GS_V2.78_3
However, the android 8.0 version is 15th Jan 2018, which is old.
Reading on the forum, there's a post with android updates on the stock Rom up until March, however no new firmwares posted on there after then. But i know that there is June versions out there, do you know where they will be posted?
https://forum.xda-developers.com/an...5-mtcd-e-head-unit-discussion-thread-t3734189
Also regarding the lock screen, User Malaysk shows in his custom Rom that lock screen is activated, so it is possible. However, I'd prefer to try a stock Rom first to see if it fixes the WiFi issue, if it doesn't then i can return the unit to the seller. https://forum.xda-developers.com/an...-malaysk-roms-px5-2-4-gb-8-0-android-t3762724
Wifi issue is fixed by upgrading/changing MCU. Check out this post, https://forum.xda-developers.com/showpost.php?p=76666402&postcount=547
Try if you have latest version of MCU before trying with some other MCU.
As per this post, https://forum.xda-developers.com/showpost.php?p=76824916&postcount=772
Latest version MCU version for GS is, 2.84
smnrock said:
Wifi issue is fixed by upgrading/changing MCU. Check out this post, https://forum.xda-developers.com/showpost.php?p=76666402&postcount=547
Try if you have latest version of MCU before trying with some other MCU.
As per this post, https://forum.xda-developers.com/showpost.php?p=76824916&postcount=772
Latest version MCU version for GS is, 2.84
Click to expand...
Click to collapse
Ah right, i can't find a download link, just someone saying that there's an update, can you find a download link anywhere?
I have the same problem of wifi with PB78ATTRP. I've just updated the MCU to v2.84 but nothing changed. Any solution?
giannnnn said:
I have the same problem of wifi with PB78ATTRP. I've just updated the MCU to v2.84 but nothing changed. Any solution?
Click to expand...
Click to collapse
Not found a solution so just gunna return it. If you can't return yours, it may be worth trying a custom firmware like Malaysk rom
I found a new rom for the XZ1 Compact.
Until now only a few regions are available. Probably the June patch.
SkyHigh76 said:
I found a new rom for the XZ1 Compact.
Until now only a few regions are available. Probably the June patch.
Click to expand...
Click to collapse
Yep. None for Customized DE just yet.
It also comes a little bit late. Am I right?
The xz1c was released on 7.31.17 and I wonder if we will get more security updates after the two years after the release date.
Flash this yesterday using the FTF found here: https://xperiafirmware.com/sony-xperia-xz1-compact/
Can't really see any difference so far, but also no issues with it
Seems to have improved GPS performance on my end. Connection is still a bit weak, but it catches more satellites and doesn't lose tracking suddenly.
The GPS bug is still there and things have gotten even worse. I use a lot of GPS (Waze) and during the weekend I experienced that three times... I just dont get it how Sony cannot resolve that issue (((
mEREHAIGE said:
The GPS bug is still there and things have gotten even worse. I use a lot of GPS (Waze) and during the weekend I experienced that three times... I just dont get it how Sony cannot resolve that issue (((
Click to expand...
Click to collapse
I came across this problem on my XZ1c, but I found a fix.
Go into airplane mode and make sure GPS is disabled.
Settings\Apps & notifications\App info - find Maps
Force stop - Storage - Clear cache - Clear data
Restart phone
Enable GPS, airplane mode off.
If that doesn't work use the following service settings number to go in the gps settings :
on your phone keypad dial *#*#7378423#*#*
Go into service tests, select gps then purge test data
reboot
mEREHAIGE said:
The GPS bug is still there and things have gotten even worse. I use a lot of GPS (Waze) and during the weekend I experienced that three times... I just dont get it how Sony cannot resolve that issue (((
Click to expand...
Click to collapse
what GPS bug is this? I can't say that I've noticed anything off when using Google Maps for directions.
Didgesteve said:
I came across this problem on my XZ1c, but I found a fix.
Go into airplane mode and make sure GPS is disabled.
Settings\Apps & notifications\App info - find Maps
Force stop - Storage - Clear cache - Clear data
Restart phone
Enable GPS, airplane mode off.
If that doesn't work use the following service settings number to go in the gps settings :
on your phone keypad dial *#*#7378423#*#*
Go into service tests, select gps then purge test data
reboot
Click to expand...
Click to collapse
OK, I'll try that and report back in a few days if it helped, thanks!
nakster said:
what GPS bug is this? I can't say that I've noticed anything off when using Google Maps for directions.
Click to expand...
Click to collapse
Usually it happens when I finish using Waze or Google Maps (or any GPS driving app) and after a while I start it again and then it just does not find any satellites. Sometimes after a few minutes its back but sometimes even an hour waiting does not help nor restart nor anything you can think of. And of course it usually happens when you are in hurry It really p....s me off when thing does not work as they should be, especially when you have no time to waist
Well, everything worked fine couple of days and then I started losing GPS again. Seems that purging test data from service menu is the best solution for this bug, sometimes I dont even have to reboot. Still that is very annoying and one more reason not to buy Sony anymore... zero customer support, all this nonsense preventing people to root their phone, bug after bug that dont get fixed etc. They just don't care about anything after you've made your purchase. I've been loyal customer with 3 different phones for 7 years but seems that current XZ1c is the last phone for me that bears the Sony label. Shame on you Sony.
SkyHigh76 said:
I found a new rom for the XZ1 Compact.
Until now only a few regions are available. Probably the June patch.
Click to expand...
Click to collapse
Can you please upload it on mega or drive if possible
Here you are:
https://drive.google.com/file/d/1-sMa_DwDyikHbzJo4zSRgZo3uBulwnX5/view?usp=sharing
Has anyone experienced loosing GPS signal after a 1-2-3 hours of Google Maps ? It may be like the device is overheating. GPS is back usually after resetting.