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!
Related
I've been trying ( seemingly unsuccessfully ) to troubleshoot an odd problem on my EVO that I was hoping to get some help on. Hoping somebody else has had a similar issue and found a fix because I'm pretty frustrated at this moment. Basically what I'm seeing it this : sometimes ( far too often ) but definitely not always, I have trouble either answering incoming calls and also interacting with texts through Handcent SMS. Given what happens I think they're related. On the calls issue what happens is that the phone rings and I try to slide down to answer but either the slider doesn't move at all or just moves a bit. As soon as the phone stops ringing I can then hit my power button, wait a second and then hit it again and then unlock just fine and I usually then call said person back. Similarly, sometimes when I get a pop up text message from Handcent I can't reply to it or close it, it's as if the screen is locked. Once again, if I hit my power button once and then again and then unlock I can close the message or reply to it. I've tried uninstalling all kinds of stuff like Beautiful Widgets, SetCPU and other such stuff thinking that a low level program or homescreen widget was causing the problem but that doesn't seem to have helped. The problem has now followed me from Azrael's ROM to Myn's ( which tells me it's likely not the ROMs ), so I'm guessing that it's either a configuration issue or possibly a program I have installed that's not playing nice for some reason. I've used Titanium to backup and restore between ROMs, perhaps that's part of the problem too, corruption? Other information that could be important...I have 002 hardware, I'm obviously rooted, and here's a link to my current stable of apps courtesy of AppBrain. If anybody can help I would greatly appreciate it!
http://www.appbrain.com/user/kkryter/apps-on-the-phone
Well it seems that the only constant between everything is Handcent. You mentioned uninstalling just about everything but that program. You should try uninstalling Handcent and seeing if your issue with answering calls goes away.
Khilbron said:
Well it seems that the only constant between everything is Handcent. You mentioned uninstalling just about everything but that program. You should try uninstalling Handcent and seeing if your issue with answering calls goes away.
Click to expand...
Click to collapse
haa right? common sense..
Thanks for the suggestion. I have tried that, went to Chomp and the same thing happened to it! I've done a lot of reading and troubleshooting and one common theme was that Titanium Backup can cause such things as it can drag along corruption from ROM to ROM if you have it in any of your apps. Given this I finally put some serious work into this yesterday : I wiped everything but music and pics off of my SD card, re-flashed Myn's 2.2 RL4 ( after wiping data, cache and dalvik of course ), and then proceeded to manually install most of my apps off of the Market, some I just didn't bother with. Even after all of that it's still doing the same thing! Went to King CFS 11 kernal today as well. At this point I'm getting really frustrated, if anybody has any suggestions it would be very much appreciated!
I've done more reading today and found tons of similar reports from others, especially at AndroidForums...but really no real answers! The best I found were workarounds such as using a program called 'Easy Answer' I think. I can only imagine at this point that it's some odd combination of programs and how they deal with the builds I've tried. The last thing that I think has much hope is that I emailed the author of the program that I have to use due to low Sprint signal in my work building called 'Roam Control'. It basically allows you to 'force roam' as you used to be able to do on just about all phones but can't within native Android. Perhaps it doesn't get along with newer kernals or builds? It worked fine for me for several months on older stuff. Anyway, if anybody can think of anything or find anybody else that has come up with a solution because they're better searchers than me I sure would appreciate it!
I've worked in the IT business for many years, and troubleshooting step number 1 is usually to ask 'what's changed?'...I've tried to figure that out without much luck so far, but something just occurred to me, could the problem be deeper such as Baseband version or PRI version or something like that? It seems like I did upgrade all of those just a while back using a flashable file, my current values are as follows, perhaps they don't agree with my 0002 hardware which is why they were never offered to me automatically? Can't recall what I was on prior to that.
Baseband 2.15.00.09.01
PRI 1.77_003
PRL 60672
This MT3GS is running the latest Cyanogenmod and google apps and hasn't been overclocked, yet it randomly reboots from time to time. I installed logcat but the last entries before reboot aren't consistant or yield any clues to what's going on. Where does one go from here? Is there a debug method that will show me what happened right after that last line recorded (using catlog set to record once a line)?
This is highly frustrating. :/
I tried resetting the phone, deleting the system partition, and reinstalling Cyanogenmod, but its still happening.
Any help in knowing what to look for next would be appreciated.
Second that
Installed ICS Revloution on my HTC Sensation XE and although it worked well, I got frequent random reboots.
I then changed to Insert Coin ICS latest version, and same performance but also same issue.
I cannot ask in the actual ROM thread as I don't have 10 posts as yet, so decided to do as much homework as I could.
Can't see anything obvious in Logcat either.
Well I tried a different ROM and it still did it and still doesn't show **** on logcat... and this time I followed it through ADB connecting to my laptop.
Is this the sign of a dying device? Is this situation so abnormal that there is nothing else that can be investigated?
I feel pretty bad because I handed this phone down to my wife as her first Android device and then is driving her up the wall. I guess it did it when I used it but maybe I just didn't notice it all that much to care.
I've tried posting in many forums... I wonder if I should try an actual google forum?
Use UART. You will need to figure out how to do it on your own. This will show you the problem unless its hardware damage.
AdamOutler said:
Use UART. You will need to figure out how to do it on your own. This will show you the problem unless its hardware damage.
Click to expand...
Click to collapse
Darn, sounds like a dead end for me. I did a google for UART and android and came to the conclusion its waaay over my head. It looks like UART is just a serial communications standard?
fallenturtle said:
Darn, sounds like a dead end for me. I did a google for UART and android and came to the conclusion its waaay over my head. It looks like UART is just a serial communications standard?
Click to expand...
Click to collapse
Yep. And you can use a tool like The Bus Pirate to communicate. It costs $35 for a bus pirate.
Q&A for [ROM][UNOFFICIAL][WIP] Cyanogenmod 11 (4.4.4 - kitkat) for fairphone FP1
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
Bluetooth functionality
Hi, Chris,
amazing work! I am so glad to see that finally someone managed to get CM 11 running on our Fairphones! One question: Is it correct that Bluetooth functionality is still missing? Just asking because the WIKO Stairways, which you also seem to take care of, has a very similar hardware architecture and as far as I understand, the CM 11 ROM provided by you already offers bluetooth functionality. Is there a big difference between these two devices?
Apart from the missing bluetooth functionality I am very tempted to try your ROM ...
Keep up the good work and thank you!
Next steps and what can we do?
Thanks, Chris, for your great work. It's awesome to see that CM on Fairphone is possible after all.
The list of known bugs/missing features still includes some items which are a show stopper for many users. I'm one of them. Therefore I'd like to see some progress in these regards. IMHO it would be of great help for potential contributors if there was some sort of coordination on what has to be done.
Chris, do you mind elaborating what the issues with the known bugs are? What are areas which you already work on? What are problems which someone else could tackle? And, most importantly, where should one start?
I'd like to try and give it a go. However I know already that I'm not likely to get very far unless I can discuss issues and get some help. So, what are you currently working on and what do you suggest to start with?
Regards,
jftr
Error during installation of Cyanogenmod11 on Fairphone 2nd batch
Hi,
I have a Fairphone 1 but the second batch (FP1U)
I follow the install process of Cyanogenmod11 here but I had this error during flashing :
HTML:
set_metadata_recusrive: some changes failed
E:Error in /external_sd/cm-11_FP1-ota-UNOFFICIAL-FULLOFBUGS-0.2.zip
(Status 7)
Installation aborded
(you can this the attachment)
I could restore a backup, but I'm ready to restart flashing if you have idea to pass this error
Spheerys said:
Hi,
I have a Fairphone 1 but the second batch (FP1U)
I follow the install process of Cyanogenmod11 here but I had this error during flashing :
HTML:
set_metadata_recusrive: some changes failed
E:Error in /external_sd/cm-11_FP1-ota-UNOFFICIAL-FULLOFBUGS-0.2.zip
(Status 7)
Installation aborded
(you can this the attachment)
I could restore a backup, but I'm ready to restart flashing if you have idea to pass this error
Click to expand...
Click to collapse
A short Google search suggests to update Clockworkmod to the latest version. Have you tried that?
Here is more information regarding the issue (Unfortunately I can't post any links yet, so you have to remove the space after http)
http ://android.stackexchange.com/questions/62982/flashing-cm-11-i-get-set-metadata-recursive-some-changes-failed
http ://stackoverflow.com/questions/19860479/set-metadata-recursive-failing-on-android-install
"set_metadata_recursive: some changes failed" : solution
I have found the solution in a french forum : remplace the "update-binary" file inside the ROM : /META-INF/com/google/android/update-binary with the version on the forum below
forum-generationmobiles.net/t73067-astuce-regler-le-probleme-du-message-d-erreur-dans-le-recovery-set_metadata_recursive-some-changes-failed-25112013
Settings crashing and other bugs following
I have a series of problems at hand with my FP1 that has Cyanogenmod. I would be very grateful if anyone here could help me out with any of them, as FP zendesk etc. couldn't.
Firstly, the Systems settings menu and now even Manage apps -menu don't open. When I try, they just flash quickly on the screen without allowing any time to even read them. This problem started smaller last winter and then disappeared, but now it has come back and is getting worse and causing other problems. First it was just the system settings menu. But now it concerns also manage apps. I can't even make a downloaded new app work because the phone doesn't let me allow them any superuser rights from the settings.
-The first time this happened I could reformat my phone. But the problem now is that I don't want to loose all my stuff, so I want to do backup first. However: - the phone doesn't detect the SD-card that is inside. -I have Cyanogenmod instead of Google, so backing up using cable+Google Plus is not an option. I downloaded MyBackupPro for this, but the phone doesn't allow me to grant it superuser rights so I can't use it. So is there any other way to backup my phone?
-Now another problem that costs me actual money (I hope that my operator will compensate it later) is that some bug is "sending" non-existent SMS to some Finnish numbers and to one number abroad. In reality there are no SMS sent but on the bill it shows as if I had sent for example 2-4 text messages at the same time. Avast! Mobile security virus scanner didn't find anything. I aimed to remove some of the apps I had lately installed, in case that some of them had brought a bug along, just to notice that I can't even access the apps menu anymore in order to do so.
After schecking detailed call reports from my operator, I also noticed that all the sms that are a couple of rows longer, are sent as 2< messages. So even when I think I sent one longer message, at the bill it is counted as two or more..
Fortunately I could create a bugreport, which I will try to attach here asap (apparently need to compress it first...). It is a few days old, but soon after that I took the simcard off so & haven't used the phone much offline, either, so I guess the report should still be quite up-to-date (?).
So it would be great if someone that can interpret the report/ othwerwise has a clue what this could be about, would tell me their advise in terms of where I might start solving this bunch of problems!
(Should be the last time when person like me who doesn't understand much about software buys an alternative phone and installs an even more alternative operating system for it..and then finds herself in a mess like this with no idea how to get out..)
I'm sorry to hear that. It seems you thoroughly infested your phone with malware. I strongly suggest you reflash to get rid of the malware in its entirety.
Regarding backups: If you feel comfortable using the command line, you could try to connect to your phone from your computer using adb. There is a backup command and you can just copy files directly.
Good luck
Thanks for your reply!
I only use command line when I have step by step-instructions for it, not independently. . . Fortunately the link you gave seems to have quite clear instructions. I'll check that soon!
Try with Helium
AinoV said:
Thanks for your reply!
I only use command line when I have step by step-instructions for it, not independently. . . Fortunately the link you gave seems to have quite clear instructions. I'll check that soon!
Click to expand...
Click to collapse
I would use Helium for you backup. It can use cloud storage as backup destination. This solves your SD card issue. You also can use your PC to enable the backup without having root. This solves your root issue.
Thankyou for your expert tips!
I couldn't install neither Helium nor Android SDK that is needed for ADB , because as I said the phone settings don't open so that I could have allowed any app superuser rights.
(Actually in safe mode the settings do open but that, in turn, doesn't show any appstore available so that I could download anything new.....)
But fortunately I could upload all my photos into Dropbox and eventually managed to download and use a simple app for SMS-backups --> Dropbox. All the rest doesn't matter so much, as the apps I'll need I can download again.
So, now the backup problem is solved and I can proceed to the reformatting phase. It's probably wiser that I choose the default platform (Google ) this time in order to avoid further headaches that easily come when going too alternative with too little skills for that!
Thanks for this nice work! I was waiting long for CM on my fairphone.
Unfortunately I had to change back because of issues with the SIM management. It was not possible to switch on or off a SIM card except by going via Airplane mode and there were issues with connecting to a data network on both SIM-slots. Smaller issues were the missing BT and worse battery life than before.
Impaired battery
Summing up my problems / experiences with the battery performance after using CyanogenMod for a couple of weeks on my fp1: Over time (especially after upgrading to m11) I noticed a steadily growing loss of battery performance over time. The rear part of the device often seems hotter, especially when charging or when extensively using my phone. I can compare with my gf fp1 who uses the original FP OS. Compared with hers, the battery now seems bloated, significantly lasts shorter, shows inaccurate battery percentages (at the beginning dropping from 20 % to 0 in no time. Now even dropping from 40 - 50 % to 0).
I tried to calibrate the battery a couple of times with various apps, but the main problem with that is that I am not able to charge the battery with the phone shut down, as the phone automatically switches on when connected to an active charger. A short search revealed, that it's probably due to a kernel issue with the costum rom. Trying out other types of chargers didn't solve the problem.
Another thing I noticed, is that FPOS as well as CyanogenMod display strange MV values (2 - 4 mV while a fully charges battery should display up to 4200 MV - again see attached picture) in the app Battery calibration.
In order to figure out whether the battery is really impaired, I switched batteries with my gfs FP1. Both have been in use for the same time and both were charged with the same charging cables as well as used in similar patterns.
My battery lasted significantly shorter in my gfs FP with FP OS compared with her normal battery. Her battery worked better in mine, still it didn't lasted as long as her phone.
Another strange thing I found was that sometimes the battery doesn't only drops dead, it sometimes also gets stucked at 1 % for quite a while (see attached files). With no way to resolve this by calibrating the battery.
In all likelyhood no problem with CM as it seems to have appeared with FP OS as well see https: // forum.fairphone.com/t/battery-problem-after-cherry-1-6-update-battery-might-be-dying/
I would be interested if we could issue a bounty for @chrmhoffmann to get him working in the port again?
Click to expand...
Click to collapse
from http://forum.xda-developers.com/showpost.php?p=56379896&postcount=19
I was just thinking the same thing.. maybe using www dot bountysource dot com ?
I too would be very glad to pay and/or to contribute with testing or code in order to get Android 4.3 or 4.4 on my Fairphone.
I need it because of the Low Energy Bluetooth feature, which would enable FP to talk with fitness tracker devices...
Is @chrmhoffmann or anybody else in here still interested in pursuing a full (or at least working) port of CM to FP?
Please note that at present days, there is not defined upgrade path for FP... so this would be quite an effort but also a very nice solution for the future of FP software.
Hi,
has anybody tried to build a custom rom using the SDK provided by Media-Tek?
I've downloaded the four SDK packages granted by Media-Tek. You get the SDK packages only on request from the MediaTek Support, if you are already registred at the MediaTek-Lab.
Kind regards
I've a Win Jr LTE phone & the update ran while I was out, despite telling it not to run updates without my express permission - it has now screwed up touchscreen so the phone is entirely unusable. Does anyone have any suggestions?
NB: telling me to "do a hard reset & lose everything" is NOT a suggestion I want to hear, since its not a viable option in this case, since backup on the phone hasn't worked since I got it on multiple cards & via onedrive.
I can't use browser or keyboard, anything with controls at bottom of screen is useless, there (of course) is no obvious way of re calibrating touch screen so the phone is effectively useless.
Apologies if in wrong place but the site doesn't seem to do anything other than lag, or make choices for me I didn't select.
I would strongly recommend NOT installing this (version ends. 67) as it appears as buggy as usual Microsoft efforts and has been bricking some phones completely I have since found out.
Jemma
the issue is known (by now, think it wasnt the prior cause otherwise the device should not have received the update). the problem is somehow the os uses a wrong resolution 540X960 instead of 480X854 which ****s up the touch
two options: opt in into release-preview-ring of the insiderprogram and get the .82. maybe it already fixed the problem. second option: going back...
use external display application on your pc or pair a bluetooth mouse/keyboard if its impossible to reach the insider options (be ware: if you havent signed up as insider before it may take up to 24hrs till you will find new builds)
Yeah, I had guessed it must be something like that, because the touchscreen reacts differently from one side to other and from top to bottom.
It's frustrating though because I can remember screw ups like this from Microsoft 20 years ago and they're still making same elementary mistakes, and it's not as if specs for these phones are hard to find or there's unknown multitudes of windows 10 phones out there, like with Android..
Windows 10 honestly has the potential to be excellent but if someone with 20 years IT engineering experience can't fix it for herself because the tools just aren't there then what hope non technical people? And they are just the people who will give Windows 10 traction.
Has anyone managed to find any files that set environment variables like in android?
PS if someone builds an equivalent of the Nokia E7 running Android or Windows 10 let me know, I'll happily bite their hands off, much prefer a good hardware kbd.
im pretty sure there is no way on the blu devices to interop it and made registry editing possible (should be an easy task to modify the setting for the screen resolution). you could sideloading vcreg after activating dev mode, but im pretty sure it wont be able to write reg values and cant research atm where the value for the resolution is stored
vcreg works only on Lumia
I've tried the feedback and the insider updates and I can't get to either of them because of the screen. Is it possible someone could put this up on feedback for me as I'm sure I'm not the only person with this issue.. Microsoft would only have to release a very small patch fix to solve this issue..
Thanks in advance
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.