Develop Bugs

[GPS Troubleshoot] Sprint ET4G GPS Fix discussion

Unfortunately, I've become a veteran when it comes to ET4G GPS problems.
This thread is intended to summarize ET4G GPS issues, reported fixes, troubleshooting advice, and GPS related conversation in hopes of determining the root cause. Could be fixable, could be hardware, but I really want to get to the bottom of it. Let’s try.
I have been all around XDA and the rest of the interwebs for solutions. My personal frustration has been that most GPS issue posts result in standard advice to: download GPS Test from the market, re-install your ROM, or get back to stock and start over. That's actually great advice, and I've pursued it - just doesn't make a difference for some of us. Still worth a shot though.
Several members have great threads concerning specific approaches, and I'll reference those members and threads here. I don’t know of a true fix, but some trickery/mods appear to help a bit.
I’ll do my best to keep this up to date – referenced threads will include their own updates. If/when a true GPS fix pops-up…that’d be super! Let me know so we can validate and kill this thread.
My reference of “True Fix” refers to getting a fast, consistent, nav worthy GPS lock as the default operation, meaning no special mods of config file edits or special software. Kinda like if the GPS functionality on the device actually did what it was supposed to do. Alot of these options assume that you have root, if you don't want to root your device, best to talk to your local sprint store instead of XDA. The bright side of this approach: it may be the best one if this is purely hardware.
SO, if you have crap GPS on your ET4G and you want to take ownership of the issue (including whatever hell breaks loose when you start changing stuff) here is a fairly comprehensive list of the hoops that you can jump through at your own risk:
#1 USER ERROR Maybe you messed it up. I’m no expert, so when I root a phone and load unsanctioned software on it…I look in the mirror when I have problems.
Go back to stock and play normal. Thank SFHUB for compiling a great thread with reference to root, revert and more.
Wipe and retry flashing a recent release of your favorite ROM. Thank BARNACLES10 who has compiled damn near everything here.
JUST_S has a thorough reference thread (including a GPS section) here.
QBKING77 provides another awesome resource. If you are like me, pictures help. Moving pictures help even more and Qbking makes scores of great preview and instructional picture shows for the community.​
#2 A-GPS tools Try augmenting your A-GPS by downloading apps that help your clear and refresh assisted GPS data and look for sats.
As I mentioned, Just_s has a GPS post on his reference thread listing apps and other goodies to try. I'm not trying replace that list, but will reference some of the same items as we'll refer to these in discussion of test results.
Here are the GPS helper apps that I've know of and have used:
GPS Test (has cool features even if your GPS is working great)
GPS Status & Toolbox
FasterFix
GPS Essentials
These apps are free and provide a myriad of GPS related stuff, including options to clear and update/refresh your A-GPS. ​
#3 Dialer codes
Some dialer codes may require you to enter your MSL (see Just_s thread for how to get yours).
It may be possible to reset the GPS with a dialer code. A code that we used in the past ##GPSCLRX## worked on the EVO 4g. Some users report it to be working on the ET4G, but I have been unable to confirm. This code requests my MSL, but does not appear to reboot after entry (which is what occurred on the EVO when entered).
I would LOVE to provide a link to the ET4G dialer codes here, but until I find a great source and will hold off. Several of the threads I have seen reference other phones and appear to by copy/paste from prior lists. I can get some of them to work, but not all (including the GPSCLRX). I don't want to keep publishing those - I'll list confirmed as working ET4G dialer codes as I validate. Of course, there is a chance (see #1 above) that I am doing something wrong here and will update this section as soon as someone sets me straight.
update: Here are the dialer codes and tests that I've completed. Don't mess with these for fun, just use if you know what you are doing and you need them.
*#2580# - ServiceMode - Works!
*#RIL# - Sec_RIL_Dump - Has the LogFileList Works!
##RTN# - Real-Time Network (RTN) Works!
*#DATA*SCREEN*# - DataCreate Works!
*#0BAT# - BatteryStatus Works!
##UPST# - PhoneUtil - UART/USB Works!
##GPSCLRX# - Reset the GPS - Requires MSL [does not work on ET4G]
*#1472365# GpsSetup [does not work on ET4G]
*#INFO*1111# Testing [does not work on ET4G]
*#0*# LCD TEST [does not work on ET4G]
##DATA# - Data Programming - Requires MSL [NOT TESTED]
##DEBUG# - Debug Menu - Requires MSL [NOT TESTED]
##AKEY# - Data A key menu - Requires MSL [NOT TESTED]
##<MSL># - Master Subsidy Lock - Requires MSL [NOT TESTED]
*#0VIB# - Device Test - Vibration Test [NOT TESTED]
*#0MP3# - MelodyTest [NOT TESTED]
*#7780# - Factory data reset [NOT TESTED]
*#232331# - BluetoothTest [NOT TESTED]
*#2664# - Touchscreen Accuracy Test [NOT TESTED]
*#0RTC# - RTCTimeRead - Displays Date and [NOT TESTED]
*#9900# - SysDump [NOT TESTED]​
Here are some options that are sprinkled throughout XDA, often in forums other than the ET4G.
#4 DRIVERS Leaving room for more here, but as of now there are reports that flashing an alternate GPS driver may do something. This could be a sasquatch siting, but perhaps the sasquatch knocks something into place when flashed from CWM.
EVO Driver. Tough for me to locate the origin of this one, but daryelv is credited elsewhere and ebuechler3 has this thread. This daryelv post includes the file for DL as well.
colorado_al provides a different file to flash in this thread. Thanks!
​
#5 GPS Config file edits
At some point during your ET4G GPS woes, you ask yourself "what more can I do?", which is good! Sniffing around, you'll find that there is a config file used by the device GPS. There are some very interesting and quite brilliant mods being made here, with reports of improvement.
This thread by AngelDeath is incredible. AngelDeath bumped up the logic and intelligence of the GPS config. Impressive stuff, complete with fantastic write-up with pre-made files for your flashing consumption.
Xenova also has a great thread, providing instructions on making your own mods.
interloper also has a config file post here
#6 REPLACEMENT
Of course, taking the device back to Sprint and obtaining a replacement is an option. Might be a really good option and many members have reported it to resolve the issue.
If you took this approach, please share the experience. Specifically:
Did it resolve the issue or did you have to seek a 2nd replacement?
If resolved, did you notice anything identifyably different about the replacement like a different hardware version (menu>settings>about phone) or physical change?
How was the Sprint experience? Did they give you hell? Did they admit that they knew of an issue and were obliged to replace? Any information you can provide here could make it easier or faster for others.
If you have no GPS issues at all, congrats! For those of us that do, let's solidify what works and what doesn't. As great as it would be to find a fix, it will be equally rewarding to pin it down to certain devices so we can at least know that our only option is to exchange the device.
If you do jump in and post something along the lines of "my gps is working great ", please share your ROM, Baseband and Kernel in the hope that we'll discover a combo that is devoid of GPS bug.
I've personally clogged up other threads with meandering GPS talk, I hope this thread can help alleviate that issue while providing a place to discuss GPS specifically.

Will incorporate other information sources here.
The below video (by lattisimo) offers some evidence supporting hardware as the issue source. He received a replacement and demos GPS locking on the old and replacement :
http://www.youtube.com/watch?v=hpkiJeUQpvQ​

Test results:
Re: #1
Here's what I did to mitigate issues that I may have caused:
1. used sfhub's back to stock
2. After allowing everything time to settle down, I turned GPS on and popped into the accuweather on first screen and tried to use my location. Was unable to obtain location.
3. Cleared GPS (##GPSCLRX# from dialer, entered my MSL). Hit OK to clear, but it did not reboot. Since there was no reboot, it is not clear if this did anything at all. I let it sit for 10 min then rebooted manually.
4. Went to GMaps after reboot (GPS on only, no network location) and got the standard "current location is temporarily unavailable" message.
5. Went ahead and cleared VRAM/Sprint login info (##72786# dialer, enter MSL, activation process. Reboot.
6. After reboot, still stock - let her sit for 5-10 mins. Got a notification for update (which is the EK02 2.3.6 official update). DLed and installed. Reboot, let it sit for 5min.
7. Back to maps, hit the location button - waited - after about 60 secs, I was found, accuracy was within 100 meters. Exit maps, back in, was located within 40 meters.
8. Exit maps - turned on sensor aiding, but left wireless network location OFF. Back to maps, "current location is temporarily unavailable", waited and hit it again- "current location is temporarily unavailable".
9. Exit maps, turned sensor aiding off, back to maps. Location found in about 20 secs, within 20 meters. Not too bad - no f'in idea why sensor aiding seemed to screw stuff up for a second. Sats cycled through found and dropped, still flaky.
Finding= GPS issues don't appear to be caused by my meddling​
Re: #2
I used fasterfix initially (which BTW does reset your GPS config file back to original state). This is important to know if you are using GPS config file mods as fasterfix will overwrite them. Quick to find sats, but not a big help when it comes to NAV. Still lost signal a couple of times and flowed in and out of proximity (based on the number of sats connected).
Essentially the same result with all of the others.
Finding= AGPS updates help find sats, but doesn't seem to help keep them locked.​
Re: #3
##GPSCLRX# doesn't work, don't have any leads to pursue here.
Finding = no dice​
Re: #5
The use of custom GPS config files definitely improved my GPS function. AngelDeath's area-customized files are really nice work.
That being said, even while sitting still in my office, I see my location drifting over an area of about 500 meters. When using navigation, I was able to maintain a lock of 5-6 sats, which was useful. Unfortunately, this did cause the NAV to think I was on access roads (when I was on highway) or on the incorrect cross street at an intersection. Impressive work, and a major improvement, but still not solid.
FINDING= Improves lock speed, automates A-GPS refresh, but does not provide enough stability to count on your navigation. You'll get to your location - which is an improvement - but you may have a few missed turns or U turns along the way...​

NICE WORK!
Nice work putting this together. Hopefully some positive things will come from it.
Like you, I have tried everything. Coming to this phone I knew that Samsung was known for crappy GPS performance. From day 1 the GPS has been hit or miss. Seems to work best after a reboot. I never get a lock indoors and outside it's hit or miss. So far I've ran stock, ViperRom and currently on Calkulin's 2.7 ROM. I've tried difference drivers, the config files and all the apps. Things seem great at first and go to crap within a day or so.
Considering that it always seems to be better after a reboot, I've wondered if there could be script or something to reset the GPS automatically. Much like Viper's LOS script and more recently the LOS Repair Daemon by Trifthen.
I'll be watching this closely.

every phone reacts differently to different solutions. the ultimate solution is to just have sprint replace it with a new one that doesn't have gps problems.

This is a pretty major issue so I'm glad you took the initiative to start a GPS specific thread. IMO, this is the last major issue on this phone (LoS and sound/ games bug having been resolved in the latest leaks.)
I'm going to link this thread in the Toolkit because I think it is going to get some good movement. I'm also going to list any new methods that may arise. Don't think you can have too much information on this type of issue. And every phone reacts differently so many options is a good thing. Thanks for doing this.
All that said, as mentioned in the post above mine, based on everything I've learned, I really believe this is a hardware issue. A return may be the only real fix.
Sent from my SPH-D710 using xda premium

Just_s said:
This is a pretty major issue so I'm glad you took the initiative to start a GPS specific thread. IMO, this is the last major issue on this phone (LoS and sound/ games bug having been resolved in the latest leaks.)
I'm going to link this thread in the Toolkit because I think it is going to get some good movement. I'm also going to list any new methods that may arise. Don't think you can have too much information on this type of issue. And every phone reacts differently so many options is a good thing. Thanks for doing this.
All that said, as mentioned in the post above mine, based on everything I've learned, I really believe this is a hardware issue. A return may be the only real fix.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Thanks - agree as to it being the final issue, a shame as I really love the phone. I'm certainly leaning the way of hardware as well. I hope to prove it...somehow...

**** trying to fix it just return yours and get a new one. i did and my gps works absolutely perfect.

paniro187 said:
**** trying to fix it just return yours and get a new one. i did and my gps works absolutely perfect.
Click to expand...
Click to collapse
I hear ya, will be taking mine in soon enough, just want to get to the bottom of the issue (if possible). When you exchanged yours, how did that go? Curious to see if they admitted that it was a known hardware issue - what information did they offer?
I've really let Sprint have it mad more times than I can remember, but it expends alot of time and energy. Since there are many people with the issue, if we can collect enough info from experiences like yours, perhaps we can provide some ammo for them to expedite the replacement when they commence the "confrontation".

It seems like GPS craps out after the phone goes to sleep for me. Looking in GPS Status, it's finding satellites but not locking onto any of them. I've tried to disable and re-enable GPS but that doesn't help, only a restart does.
Edit: Found a fix for my issue! Opened Terminal Emulator, typed gpsd, hit enter and the GPS service came back. Not sure what's causing it to die in the first place but I imagine it can be fixed in an update.
Sent from my SPH-D710 using Tapatalk

paniro187 said:
**** trying to fix it just return yours and get a new one. i did and my gps works absolutely perfect.
Click to expand...
Click to collapse
I'd love to do that except for the fact that I don't want to pay the deductible because of the ****ty GPS. Sigh.

Undervolting really messes up my GPS and Data Speeds. You might want to add this to the list of things to check.

I'M NOT YELLING said:
I'd love to do that except for the fact that I don't want to pay the deductible because of the ****ty GPS. Sigh.
Click to expand...
Click to collapse
Do what I did go to Odin then Odin a kernel in the phone slot. This creates a soft brick. If you want to unbrick Odin a modem in the phone phone slot. Take it to sprint say say I don't know wat happened. (When it tries to boot it will just say you have to update drivers. They sent me a new one to the store with no paying a deductible.
Sent from my SPH-D710 using xda premium

The CM7/EVO driver was the only fix I tried, but currently works for me. May be a placebo effect, but it only takes a few seconds to lock on now. (used to take up to a minute if at all) This is on EK02 rooted stock btw. I'm gonna test it some more once I move back to my college town.

EL29 locks very quickly for me

Korey_Nicholson said:
EL29 locks very quickly for me
Click to expand...
Click to collapse
Had you experienced issues prior to EL29? I am on Calk's 2.8, EL29 all the way. No change for me.

EVO driver was the only fix that reliably works for me. Tried it with all radio/modem updates and first fix is now within 10-20 seconds and GPS position is also more accurate. This is the one I used with my EVO and have been using with the E4GT.
Edit - different driver than posted by OP but is what I used for my CM7.1 EVO and works for my E4GT - this is qualcomm 1.1 driver
I normally don't use any scripts or other GPS setup programs but if a fix is not found within 30 seconds I do try GPS Status. Fix is fastest in GMaps, but also good in GNavigation and TeleNav
PS- must flash after flashing ROM or ROM updates
Curently on Calk's 2.7 and modem EL29

Currently running CM7/EVO driver + a gps script and it's been running way better. Prior to installing driver I just had the script. With the driver, it seems to lock even faster with stronger locks. I'll keep testing it out the rest of the week.
Knock on wood that this is a fix for me. Like others have said, getting a new phone is the only real consistent option.

I've never had GPS issues, running EL29 modem and kernel and Blazer ROM. I guess I got lucky. I used to have so many issues with my old EVO, especially on AOSP. Glad I dodged the bullet on this one

colorado_al said:
EVO driver was the only fix that reliably works for me. Tried it with all radio/modem updates and first fix is now within 10-20 seconds and GPS position is also more accurate. This is the one I used with my EVO and have been using with the E4GT.
Edit - different driver than posted by OP but is what I used for my CM7.1 EVO and works for my E4GT - this is qualcomm 1.1 driver
I normally don't use any scripts or other GPS setup programs but if a fix is not found within 30 seconds I do try GPS Status. Fix is fastest in GMaps, but also good in GNavigation and TeleNav
PS- must flash after flashing ROM or ROM updates
Curently on Calk's 2.7 and modem EL29
Click to expand...
Click to collapse
Thanks, driver testing is next for me. I've updated the postings and actually had some improvement with AngelDeath's config file for my area. Not perfect, but certainly better than before. I kinda hate the config file approach though - I travel for work and need GPS to avoid getting lost (which is a talent of mine). Just want GPS to work. When I was overseas with my good 'ol EVO, the geotagged pictures worked flawlessly - was not connected to any network or wifi the whole time.

Hacked Phone?

Hello everybody, I'm not sure where exactly to post this nor what thread I could search for, as I think my situation is slightly unique and I'm very much confused and concerned.
Just a bit of background, I recently purchased a Galaxy Nexus from Verizon, which has been performing beautifully. I unlocked/rooted immediately, flashed the latest MIUI and franco kernel, and have been enjoying my phone since! Yesterday, however, after failing to successfully update my ROM (forgot to wipe data before the flash and was too lazy to make backups), I reloaded my nandroid and just figured I would rest on my previous version, as it was running fine before.
Today, I found out three of my contacts received calls from me which I did not make, and do not show up on my phone records. I might have dismissed this as some sort of phantom calling, or honestly maybe even butt-dialing, except for the fact that these individuals claimed I spoke to them and said unusual things along the lines of a prank call. During this time, I was at work and my phone was safely in my pocket the entire period in question.
Now, I have absolutely no idea what happened and no idea where to start looking; as such, I'm turning to what I think is an experienced XDA community to perhaps shed some light onto this? I don't want to jump to an extreme conclusion and say that my phone was somehow "hacked," as I don't even know if it's possible that you can hack a phone to call? Or is there any way for someone to make a call that shows up as my phone number on a contact's phone in another fashion? Again, any sort of information would be helpful, and any sort of solution or preventative measure would be even more appreciated.
Thanks in advance!

It could be a rouge app you installed that have permission to place call without your permission. What app did you installed recently?
Pressed from my Maguro

Mach3.2 said:
It could be a rouge app you installed that have permission to place call without your permission. What app did you installed recently?
Pressed from my Maguro
Click to expand...
Click to collapse
I've installed Serve, Documents to Go, and Google Now for ICS from XDA! I actually did google some more, I see that it's possible someone spoofed my number? I don't really know. If it doesn't continue, it won't be a problem, but I'm concerned more malevolent calls may occur.

It's completely possible that someone spoofed your number, there are numerous websites that allow you to do so.
Sent from my Galaxy Nexus using xda app-developers app

It's certainly possible that apps can dial numbers or send text messages. I've yet to come across one that actually tries to have a conversation with the person it's calling however.
Sound more probable the number was spoofed, like someone already stated.
If you want to feel safe about your phone, wipe everything and reflash factory images. No rogue app will survive that.
Sent from my Galaxy Nexus using Tapatalk 2

I'd say go a bit further, re-lock & unlock the bootloader and then flash a factory image. Everything inside the phone has been nuked then.

Thanks for all the replies everyone,
I think I shall do as suggested and reflash a stock ROM at the very least, as a precautionary measure even though I actually am fairly certain my number was just spoofed, due to a certain pattern in the people who were called.
Thank you all for at least quelling my worries that something more serious had occurred.

[Q&A] [ROM][UNOFFICIAL][WIP] Cyanogenmod 11 (4.4.4 - kitkat) for fairphone FP1

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

Samsung Wearable App Crashing?

Hi!.
I've been having this annoying problem with Galaxy Wearable app for the last three days where the app crashes on launch every time. I've been trying to fix it all this time and i have tried different remedies that didn't help at all. I haven't the slightest clue what's wrong and i don't know where to ask for help so i figured i ask for it here first. I'll post a logcat if anyone is willing to help.
Here's what i've tried so far:
1. Cleared cache - Didn't fix the issue
2. Cleared storage - Didn't fix the issue
3. Complete reinstall of the Wearable app and services - Didn't fix the issue
4. Removed the Samsung account - Didn't fix the issue
5. Resetting the watch and setting it back up again - Didn't fix the issue
6. Tried 3 and 5 together - Didn't fix the issue
7. Did a clean install of ROM (Havoc 2.8) - Fixed the issue but it came back in about an hour
9. Rolled back to the previous build of Havoc (2.7) - Same as above, problem came back after some time
10. Dirty flashed 2.8 - Same
11. Restored to 2.8 and uninstalled a bunch of apps that i thought might be clashing with the Wearable app - Didn't fix the issue
ANY help would be much appreciated. I'm starting to think something is wrong with the watch itself.
EDIT: Never mind, i found what's going on. It's Samsung Pay that's making the app crash. I uninstalled it on a whim and now it works!!! Mods, kindly delete this thread.

How much memory your phone got? Try to close all other apps and then try. I have the same behave with other apps on my Moto phone.

Helhound0 said:
Hi!.
I've been having this annoying problem with Galaxy Wearable app for the last three days where the app crashes on launch every time. I've been trying to fix it all this time and i have tried different remedies that didn't help at all. I haven't the slightest clue what's wrong and i don't know where to ask for help so i figured i ask for it here first. I'll post a logcat if anyone is willing to help.
Here's what i've tried so far:
1. Cleared cache - Didn't fix the issue
2. Cleared storage - Didn't fix the issue
3. Complete reinstall of the Wearable app and services - Didn't fix the issue
4. Removed the Samsung account - Didn't fix the issue
5. Resetting the watch and setting it back up again - Didn't fix the issue
6. Tried 3 and 5 together - Didn't fix the issue
7. Did a clean install of ROM (Havoc 2.8) - Fixed the issue but it came back in about an hour
9. Rolled back to the previous build of Havoc (2.7) - Same as above, problem came back after some time
10. Dirty flashed 2.8 - Same
11. Restored to 2.8 and uninstalled a bunch of apps that i thought might be clashing with the Wearable app - Didn't fix the issue
ANY help would be much appreciated. I'm starting to think something is wrong with the watch itself.
EDIT: Never mind, i found what's going on. It's Samsung Pay that's making the app crash. I uninstalled it on a whim and now it works!!! Mods, kindly delete this thread.
Click to expand...
Click to collapse
Yep had the same exact problem the other day after upgrading to Android 10. There's another thread in here where I found the same issue (it's throwing a java ClassNotFound exception on mine). It's especially nefarious because they sideload the pay plugin so you won't see it if you're uninstalling via the play store, and it's not sorted alphabetically with the other Samsung apps so you might not even see it if you're searching manually.
I say nefarious because depending on how bad the crash is (background task vs UI), they may not be able to even push an automatic fix since they're not using the play store. Seems like a pretty terrible approach to me.
Sent from my Pixel 2 using Tapatalk

oxygenes said:
How much memory your phone got? Try to close all other apps and then try. I have the same behave with other apps on my Moto phone.
Click to expand...
Click to collapse
I got 3 gigs and not even half of it being used at idle. And i don't really do memory intensive stuff on my phone anyway. The issue was definitely Samsung Pay. if anyone has this issue where you're running Pie and are rooted with any version of magisk, uninstall Pay. It's been a few days and i haven't had this issue repeat even once.
shmaque said:
Yep had the same exact problem the other day after upgrading to Android 10. There's another thread in here where I found the same issue (it's throwing a java ClassNotFound exception on mine). It's especially nefarious because they sideload the pay plugin so you won't see it if you're uninstalling via the play store, and it's not sorted alphabetically with the other Samsung apps so you might not even see it if you're searching manually.
I say nefarious because depending on how bad the crash is (background task vs UI), they may not be able to even push an automatic fix since they're not using the play store. Seems like a pretty terrible approach to me.
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
I just uninstalled Pay from the app list in settings and rebooted. If there is a sneaky sideloaded plugin somewhere, it doesn't seem to be interfering with the Wearables app anymore.
And I guess you're right about this being a terrible approach. But Pay isn't even supported where i currently live so my question is WHY even sideload it on a device being used in an unsupported region... Such a waste of resources.

Question Help Desperately Needed - Random Reboots

So I posted about this previously but here's more info and a clearer summary
The Issue:
Phone randomly reboots about an average of once per day. Screen freezes, goes black, comes back on for 3 seconds still frozen, then proceeds to reboot. I've kept track and 100% of of the time this seems to happen when I'm typing. Initially I thought it was Textra, but it has happened in Snapchat, and Twitch whenever the google keyboard is up. Google sent a replacement phone and the issues persists, and I find it hard to believe that both phone would have the exact same hardware issue. Furthermore it very much seems like a software issue considering it ONLY happens when the google keyboard is up.
My hope is that someone might have encountered this and has a simple solution although I doubt it. Unfortunately since I don't have another phone, I have to wait to obtain one before I do a safe mode test. And even if I do it's not realistic for me to test it that way because I'd have to spend hours typing away just to try to get the issue to occur (since it's not frequent like every 5 minutes).
I'm suspecting some data or a setting is getting transferred over from my previous backup that's affecting google keyboard or something of the sort. My next step will be a factory reset, and then reinstalling everything bit by bit manually. Of course I have to link my google account, but I won't have it automatically restore the backup. If that doesn't help then I'm at a loss. At that point I'd probably pick up a cheap Pixel 2XL as my daily, and use my P6Pro in safe mode as much as I can to try to trigger the issue I guess?
The Phone:
Pixel 6 Pro
Not Rooted
November 5 Update
Set up done using my google account to restore all apps and settings, not cable

Remind me since I don't recall if it was brought up in your other thread about the issue, did you try Official Google Android Flash Tool yet?

Agree with edor, Android flash tool, flash both slots, start all over

roirraW edor ehT said:
Remind me since I don't recall if it was brought up in your other thread about the issue, did you try Official Google Android Flash Tool yet?
Click to expand...
Click to collapse
I have not tried this. What would this be used for?

ne0ns4l4m4nder said:
Agree with edor, Android flash tool, flash both slots, start all over
Click to expand...
Click to collapse
Not sure what that means sorry, can you elaborate?

MarkAnthony121 said:
I have not tried this. What would this be used for?
Click to expand...
Click to collapse
To wipe the phone and start back fresh.
MarkAnthony121 said:
Not sure what that means sorry, can you elaborate?
Click to expand...
Click to collapse
Just that. To start back fully fresh. Then if you do that take my advice from the other thread, don't restore backups from Google or anywhere, and initially only install your most critical apps. Once you determine you're not having the problem, install some more. Verify, repeat.

ne0ns4l4m4nder said:
Agree with edor, Android flash tool, flash both slots, start all over
Click to expand...
Click to collapse
Not sure what that means sorry, can you elaborate?
roirraW edor ehT said:
To wipe the phone and start back fresh.
Just that. To start back fully fresh. Then if you do that take my advice from the other thread, don't restore backups from Google or anywhere, and initially only install your most critical apps. Once you determine you're not having the problem, install some more. Verify, repeat.
Click to expand...
Click to collapse
Yes but I don't understand what "flash both slots" means. And wouldn't I get the same result by simply doing a factory reset and then proceeding with the method of installing everything manually and not from a backup? Why use the google flash tool vs factory reset?

MarkAnthony121 said:
Not sure what that means sorry, can you elaborate?
Yes but I don't understand what "flash both slots" means. And wouldn't I get the same result by simply doing a factory reset and then proceeding with the method of installing everything manually and not from a backup? Why use the google flash tool vs factory reset?
Click to expand...
Click to collapse
At this point, that's more information than you really need to know to try to fix your phone. I don't want to overcomplicate things. You can look at Google search results for "Pixel flash both slots" if you really want to go down that road right now.
Spoiler: Some of the details you're asking for, but you don't need right now
In short, starting with the Pixel 1 in 2016, they have two copies of almost everything (except only one copy of user data). On a Pixel, and another phone that employs dual slots, when you receive an OTA update, it updates the copy of Android that you're not currently running, then reboots into the one it just updated, and once rebooted it goes ahead and updates the copy that you're no longer running, so they're both now updated.
Not all OEMs use the dual partition strategy, which is frustrating. When I briefly had the Note 10+ before the P6P came out, I was amazed that Samsung still hasn't adopted the method. It beats the old style OTA method that Samsung still uses to this day as far as I know where it takes 15-20 minutes or more to run the update while your phone is unable to be used at all, and then even when it boots up the next time Android has to finish the job "optimizing" your apps for the new update. Dual partitions for Android save a lot of time when updating the phone.
In some manual flashing processes, you end up with one slot with a different copy of what you have in the other slot - and you don't want that. The slots are referred to as Slot A and Slot B.
I can go further into detail but you don't really need that to fix your phone.
All you need to know right now is Official Google Android Flash Tool.
If you haven't already tried the factory reset, et cetera, which we had recommended to you at least once in the other thread, then by all means, you can try that. But if you're going to try that, you might as well just use the Official Google Android Flash Tool and ensure you are 100% stock. Official Google Android Flash Tool has fixed a good dozen or two folks' issues (I haven't been keeping count) in these forums in the past 2+ months.
So if the factory resetting doesn't solve things then you'll still have to try Official Google Android Flash Tool to be closer to sure that you tried everything that you could. We had already suggested the Factory Reset to you in the other thread. Since you created a new thread, I figured you might be looking for information you hadn't been given yet.
So the short answer is because Official Google Android Flash Tool will do an even more complete job of putting your phone back to 100% stock, with a lot less doubt than a simple factory reset. Sure, a factory reset, in theory, should get you the same thing, but there are all sorts of circumstances where a factory reset won't. Something is wrong with your phone and we don't know what it is.
There's the Factory Reset idea and then there's the Official Google Android Flash Tool idea - either coupled with the staggered manual installation of apps until you narrow down if it was a particular app causing the issue. It doesn't matter which one you choose to try first. If you try just a Factory Reset, and things still go haywire, then you'll still have to try Official Google Android Flash Tool after that. It's your choice, now pick one and go forth and hopefully reboot no more.
Also, I wasn't going to mention this but I will now. Forums generally discourage users from creating multiple threads about the same issue or posting about the same issue in multiple threads. You can always update the OP (opening/first post) if you need to, and give an update as a reply to your existing thread.

MarkAnthony121 said:
So I posted about this previously but here's more info and a clearer summary
The Issue:
Phone randomly reboots about an average of once per day. Screen freezes, goes black, comes back on for 3 seconds still frozen, then proceeds to reboot. I've kept track and 100% of of the time this seems to happen when I'm typing. Initially I thought it was Textra, but it has happened in Snapchat, and Twitch whenever the google keyboard is up. Google sent a replacement phone and the issues persists, and I find it hard to believe that both phone would have the exact same hardware issue. Furthermore it very much seems like a software issue considering it ONLY happens when the google keyboard is up.
My hope is that someone might have encountered this and has a simple solution although I doubt it. Unfortunately since I don't have another phone, I have to wait to obtain one before I do a safe mode test. And even if I do it's not realistic for me to test it that way because I'd have to spend hours typing away just to try to get the issue to occur (since it's not frequent like every 5 minutes).
I'm suspecting some data or a setting is getting transferred over from my previous backup that's affecting google keyboard or something of the sort. My next step will be a factory reset, and then reinstalling everything bit by bit manually. Of course I have to link my google account, but I won't have it automatically restore the backup. If that doesn't help then I'm at a loss. At that point I'd probably pick up a cheap Pixel 2XL as my daily, and use my P6Pro in safe mode as much as I can to try to trigger the issue I guess?
The Phone:
Pixel 6 Pro
Not Rooted
November 5 Update
Set up done using my google account to restore all apps and settings, not cable
Click to expand...
Click to collapse
I've heard of freezing problems from others related to gboard. This would indeed appear to be a software flaw. I've never really used gboard since the first step for me was google-free AOSP, then put in my sim card and start using it (I don't like spyware).
Simplest solution for you would likely be to try a different soft keyboard. Personally, I would suggest finding one on f-droid rather than play store because open source.

For what it's worth, I've been using GBoard for 5+ years and have never had a problem.

96carboard said:
I've heard of freezing problems from others related to gboard. This would indeed appear to be a software flaw. I've never really used gboard since the first step for me was google-free AOSP, then put in my sim card and start using it (I don't like spyware).
Simplest solution for you would likely be to try a different soft keyboard. Personally, I would suggest finding one on f-droid rather than play store because open source.
Click to expand...
Click to collapse
I used to root back in the day and use a custom ROM. If I do that there's no automatic updates right? Have to reload a new ROM for updates?

MarkAnthony121 said:
I used to root back in the day and use a custom ROM. If I do that there's no automatic updates right? Have to reload a new ROM for updates?
Click to expand...
Click to collapse
Depends on the ROM. I believe GrapheneOS has OTA updates. I know some others over the years have had that, too. Certainly not most custom ROMs but some.

roirraW edor ehT said:
Depends on the ROM. I believe GrapheneOS has OTA updates. I know some others over the years have had that, too. Certainly not most custom ROMs but some.
Click to expand...
Click to collapse
Thanks for all the help. (sorry for posting twice, I tried to delete the other) And I did appreciate the extra info so that I understood WHY I needed to do it this way and how it all functions. Two final questions. On modern phones like this one, does running a custom rom really improve battery/performance much? It's already pretty snappy for me, so I feel if I don't care about customizability it's probably not worth the effort for minimal reward. And second question, will the flash tool give me the option to clear both slots ?
Oh and third, is it ok to link my google account, (to get my contacts and such) as long as I'm not restoring any backups from it?

MarkAnthony121 said:
Thanks for all the help. (sorry for posting twice, I tried to delete the other) And I did appreciate the extra info so that I understood WHY I needed to do it this way and how it all functions.
Click to expand...
Click to collapse
You're very welcome!
MarkAnthony121 said:
Two final questions. On modern phones like this one, does running a custom rom really improve battery/performance much?
Click to expand...
Click to collapse
In my opinion, no, but the object of some ROMs (like GrapheneOS) are more geared towards very much increased security and avoidance of all the Google data-collecting that goes on with everything Google, although you can use some or most Google apps with GrapheneOS if you choose.
I've never actually tried GrapheneOS, though - I've only kept up with the two threads about them because I was curious about it. To me, starting with my first Pixel (I never owned a Nexus device), I liked stock Android way better for my purposes.
But just as for a lot of phone-related subjects, the answer to this question is very subjective. What's right for me isn't right for everyone. Everyone's needs are different. The only way of knowing for sure is to try it. You might try something and very quickly say "to heck with that, I'm going back", or you might say "oh, I like this loads better". I'm not a betting man unless something is a near 100% chance, so it's really a toss-up whether you would like a different ROM or not.
Also, how I handle my battery works great for me - but it wouldn't for everyone. I don't charge the phone until it gets down to 25%, and I try not to let it get any lower than 25%. I only charge the phone up to 75% when I can. I never charge overnight, and I never quick charge. That 50% range of battery still lasts me about 24 hours. My Pixel 1 battery is in great shape because of this habit. My wife's, on the other hand, since she didn't do this - her battery on her old Pixel 1 is relatively shot.
MarkAnthony121 said:
It's already pretty snappy for me, so I feel if I don't care about customizability it's probably not worth the effort for minimal reward.
Click to expand...
Click to collapse
Sounds as if you already have made up your mind to me. I mean, that's how I feel, and I like using Google's services for the most part. I'm more a function over form person. While I don't want something downright fugly, I really don't care what things look like - only how they do what I want them to do. Yet again, "how they do what I want them to do" is very subjective. The Samsung Galaxy Note 10+ didn't do what my wife and I wanted it to do, but we were both spoiled on the Pixel 1 before that. We don't regret our choice to go back to Pixel via the 6 Pro. For others, the Samsung phones are what they need.
MarkAnthony121 said:
And second question, will the flash tool give me the option to clear both slots ?
Click to expand...
Click to collapse
You don't want to "clear" both slots, you want to flash both slots. In answer to your question, I don't think you'll have a choice via the site (or offline flashing the full factory image). In other words, both slots are going to get flashed whether you like it or not. You would have to go to extra efforts to *not* flash both slots. Hence yet another reason why you don't have to worry about that aspect.
Google's official methods would never flash only one slot by default. That would be just plain idiotic of them.
Before you ask, the reason I recommend the site rather than offline flashing of the full factory image is:
It's more user-friendly.
It has solved problems when manually flashing the full factory image has not for some others with particular problems.
MarkAnthony121 said:
Oh and third, is it ok to link my google account, (to get my contacts and such) as long as I'm not restoring any backups from it?
Click to expand...
Click to collapse
Yes, absolutely, although in some cases I've recommended going completely fresh and not even doing that, at least before testing long enough to see if you have the issue. You certainly could go without putting your Google account in, etc, but I don't feel that's warranted at this point. The only time I think you should do that, in this case, is if you do it the other way (with your Google account), and you still have the same problem right away (without installing any additional apps).
Just remember don't install any additional apps to start with, long enough to be sure that the problem isn't happening. I know it's a painful process - I've done this before on several devices for different reasons. Usually, the cause of issues becomes evident but it's possible it won't be completely obvious.
FYI, just putting your Google account in will, I believe, possibly still automatically restore your phone's most basic settings but I could be wrong about that. You could always try it without your account at first, use the phone in it's limited state for long enough to know there's no problem, and only then put your Google account in.