Develop Bugs

Kaiser 110 problems

Greetings all --
I am posting this request for help because I've exhausted just about every other resource. The community support and documentation is great and I have learned quite a bit in a matter of days. You all are great!
Here's my situation. I have the HTC 8900 (KAIS110). Not the 8925 like most seem to have. It is my understanding that 3 versions of the "Kaiser" were made, or at least submitted to FCC for approval, and that the 8900 was to go to AT&T (branded on phone), but was canceled in lieu of the 8925. This is the non-camera version.
For reference, the following information is listed in the battery compartment:
HTC 8900
KAIS110
FCC ID: NM8KS
SKU: 64760
P/N: 99HCY091-00
Made in Taiwan
Currently:
HardSPL 3.56
Radio: 1.71.09.01
Myn's Warm Donut RLS5
kallt_kaffe's kernel 2010-06-06 (kaiser/240x320/donut/panel 2/tilt options used in LoserSkaters NBH Editor)
Problems:
1. Installing OS (Sys+Data on NAND), dmesg output shows "Block 711 is bad". Under normal circumstances, this wouldn't be a problem as the OS would remap to a new block. This could also be an issue with yaffs, or a few other things, and not even be bad. But the question remains, is this causing problems?
2. Attempting to run Calibrate Screen results in error with the following message: "The application Calibrate Screen (process org.isageek.dasbrennen.CalibrateScreen) has stopped unexpectedly. Please try again. [Force close]". I have not seen a recent post in response to whether this problem persists with all builds, or if I am just lucky like that.
3. GPS does not want to play nice. From the app store, I install GPS by Andrea Baccega. Sometimes I get a single satellite to display, once I saw 3 on screen. Unfortunately, none of the other fields (long/lat) were populated which tells me something is wrong.
Dmesg output:
GPS:env_mask=0
GPS:date=00002000
GPS:time=000000 hlat=0 llat=0 hlng=0 llng=0
GPS:speed=0 bearing=0
GPS: has been tickled!
4. Using the phone on T-Mobile, why can I not get 3G working? It keeps going back to EDGE. I have the Android data plan as well.
5. Voice search is quite flaky. Sometimes it works great once, maybe a few times in a row, and then it just stops working and presents me with the Try Again / Cancel screen, after which, there is no longer audio for phone calls. From what I can tell using Dev Tools, looks like VoiceSearch is hanging due to an issue with Mediaserver. I recall seeing this issue, or a similar one, surface in the forums but there was not much information pertaining to it that I could find.
6. The following errors appear in the dmesg output; I am posting the list just in case one or more messages are beyond the scope of normal operations:
mmc1: host does not support reading read-only switch. assuming ite-enable.
Init: cannot open '/initlogo.rle'
[RR] ERROR no local ept for prog 02000031 replying anyway!!
audio_enable()
audpp: DMA missed
audio timer expired
audio_disable()
audmgr: DISABLED
binder: send failed reply for transaction 5448 to 149:221
7. As stated above, this phone lacks a camera. The slot where the camera goes, just has a cover over it. Looks like I should be able to pop a replacement in the spot. Anyone know the part number of the rear camera, or where I might find one? I can only seem to locate the front-camera on various web sites.
Thanks all!

1. bad blocks are common, yaffs reports them, and marks them as unusable, they have no effect on running Android, ( one of my kais130's has about 10 bad blocks, works fine).
2. Thats normal also, not sure if calibration app has ever worked, although i think there is a console based one that does, never had to use it though.
3. GPS may or may not work properly depending on a number of factors, which build and NBH are used, also which gps software is used also, best combo I have found so far are the Kallt_Kaffe NBH's and Myn's warm Eclair, with GPS test (free or pro). Also note that initial fixes take some time, up to, or over 5 minutes, depending on conditions, etc.
4. Not sure, could be a number of factors again, build, local 3G coverage, APN setup, etc.
5. Never used voice search, but it is known to be pretty flakey, again build plays a large part.
6. I know that there are normally errors on boot, the audio ones are not normal however, could be due to using an older radio, or perhaps some rare kais110 issue, can't actually recall anyone reporting issues with kais110 hardware.
7. Not sure if it's possible to just add a rear camera, it'll depend if the supporting electronics were fitted to allow it to work or not, also unsure where to look for one, although you may be able to get a part number off the service manuals, ( should be in the xda-wiki pages ).

TMobile and AT&T use different 3G frequencies, so an AT&T phone such as your won't do 3G on TMobile. The EDGE will work fine, but slow of course.

purpleonyx said:
3. GPS does not want to play nice. From the app store, I install GPS by Andrea Baccega. Sometimes I get a single satellite to display, once I saw 3 on screen. Unfortunately, none of the other fields (long/lat) were populated which tells me something is wrong.
Dmesg output:
GPS:env_mask=0
GPS:date=00002000
GPS:time=000000 hlat=0 llat=0 hlng=0 llng=0
GPS:speed=0 bearing=0
GPS: has been tickled!
Click to expand...
Click to collapse
Use GPS Test (chartcross ltd), free version from Market. Configure it to not turn off display (keep it from going to sleep). Plug in a charger (if you wan to) and leave it near a window.
Within 5-10 minutes you should have a fix. After that, getting a fix normally happens within seconds. Depending on how much time has passed since you last used your GPS and also the distance you moved it while having it turned off also affects the time to get a fix.
Also blocking the top of the phone with your hand is not a good idea as it seems to be an effective way of blocking the GPS signals.

kallt_kaffe said:
Use GPS Test (chartcross ltd), free version from Market. Configure it to not turn off display (keep it from going to sleep). Plug in a charger (if you wan to) and leave it near a window.
Within 5-10 minutes you should have a fix. After that, getting a fix normally happens within seconds. Depending on how much time has passed since you last used your GPS and also the distance you moved it while having it turned off also affects the time to get a fix.
Also blocking the top of the phone with your hand is not a good idea as it seems to be an effective way of blocking the GPS signals.
Click to expand...
Click to collapse
Thanks for the response -- I had tried that over the past 2 nights, but it never took. It just did however, during the day, which is odd. I also switched to a 1.64.08.21 version of the radio today, and it worked. Previous attempts were under 1.71.09.01, 1.70.19.09 and 1.70.18.02 that resulted in failure. Odd.
Is there a way to view all roms installed, for everything? OS, kernel, radio, splash/boot, etc? I am wondering if something got hung up during flashing, or something didnt get wiped out.
Thanks!

purpleonyx said:
Thanks for the response -- I have done this several times (left it going for 10+ hrs at the max time), and it picks up 4-5 satellites, but nothing ever occurs. It sits there with the yellow light, and all of the numbers show in the 20's to very low 30's, which seems like it's a very weak signal, or a high signal/noise ratio. Could this be a radio issue?
Click to expand...
Click to collapse
20-30 actually should be enough. Anything above 40 is excellent and not seen very often. And I'm using the same Radio so that should be the problem. Don't know really. Does it work in WinMo?

kallt_kaffe said:
20-30 actually should be enough. Anything above 40 is excellent and not seen very often. And I'm using the same Radio so that should be the problem. Don't know really. Does it work in WinMo?
Click to expand...
Click to collapse
I had no problem working under winmo before i flashed android to nand. It had no delay in picking it up either. I just rebooted the phone and launched google navigator, and it's taking forever again, searching for gps it says.
If you want to use me as a guinea pig, feel free. I ended up ordering the nokia n900, as i need something working now. I am considering keeping the kaiser 110 to screw around with though. It would make a good backup device anyways. I tried Myn's Warm Eclair on it, but it dragged its legs and had too many problems. Myn's Warm Donut however, functions near perfectly and is quite fast. I've oc'd the processor to 450 MHz which provides a noticeable speed boost. I'm using your latest 2010.06.06 kernel with it. I've been questioning whether or not display 2 and 3 are the same on this model -- sure behaves the same.
-update: Phone comes to a crawl, and then locks up when GPS is used. Both the GPS Test and Google Nav.

[GUIDE] Change your Xoom wifi adapter MAC address [UPDATE: 28/11]

First things first:
By reading and following this guide,
you accept *ANY* and *ALL* responsibility
for the possible damage, loss of data and/or other
consequences to your device which may follow.​
All the following procedures have been tested on a US Motorola Xoom Wifi only. They *might* (and probably do) work on other devices, including the 3G, Euro, etc., but are not guaranteed to do so.
Now that we're straight, let's get to the point.
Foreword:
Once I had this problem of accessing my brother's MAC filtered access point. I had my notebook MAC added to the access list, whilst my Xoom was left out. Of course, my brother was out and I didn't know the AP credentials. It was then, when the idea of a MAC change came to me.
During my brief "on the spot" research I discovered a file named 'bcm4329.cal' residing at '/system/etc/wifi/'. It has a line, notably 'macaddr=xx:xx:xx:xx:xx:xx'. Changing the contents, however, did not yield any changes to my MAC address. That time, I left the issue unsolved, but later, tinkering with my Huawei U8500, I discovered something that helped solve my Xoom MAC issue.
The solution was quite straightforward, but involved a kernel recompile. So, here I am, offering several kernel modules (drivers) - for the stock 3.2 kernel and for the Tiamat 2.0.0-2.2.0 kernels.
Prerequisites:
a stock 3.2, Tiamat 2.0.0 Katana, Tiamat 2.1.0 Tachi or Tiamat 2.2.0 Odachi running Motorola Xoom Wifi
ClockworkMod Recovery installed (author uses ClockworkMod 3.2.0.0 R4c by solarnz)
Procedure:
The procedure involves changing the appropriate wifi kernel module to a 'patched' one which allows MAC change through the 'bcm4329.cal' file. All this will be done in ClockworkMod Recovery.
1. Download one of the attached files (according to your running kernel version which you will find in Settings -> About tablet -> Kernel version)
2. Place the appropriate file on your SD card
3. Boot into Recovery by rebooting, waiting until the Motorola logo appears, count to 3, press the Volume down button, then the Volume up button
4. Select 'install zip from sdcard'
5. Select 'choose zip from sdcard'
6. Browse to your 'mac_change_mod_xxx.zip' (steps 1 and 2)
7. Select 'Yes - Install mac_change_mod_xxx.zip'
8. After its done it's job, reboot by returning to the main menu and choosing 'reboot system now'
Voila! You now have a Xoom with a custom MAC address. You can change it by editing the 'macaddr=...' line in the '/system/etc/wifi/bcm4329.cal' file. The author uses Root Explorer for this.
NOTE: The kernel module will probably be removed when installing a new kernel, so the procedure should be repeated.

Great work!!

LOL, I love it. I just changed my MAC address to look like an Apple Laptop. Even shows up that way on scanners that resolve the OUI to the manufacture. Now I'm stealthy!
Did I mention I luv it. Maybe tomorrow I will look like a Commodore 64!

is purpose just for personal preference? What would be the benefit of changing it?

One of the possible uses of MAC changing is described in the head of this thread. IMHO it's the most useful one. Other purposes may not be so legit, but the author takes no responsibility ;-)

tdaliviu said:
One of the possible uses of MAC changing is described in the head of this thread. IMHO it's the most useful one. Other purposes may not be so legit, but the author takes no responsibility ;-)
Click to expand...
Click to collapse
Lol I guess I was too dumb to understand what you did in the op, but I will still put this on my sd card just in case I find a use or need it

Purpose for MAC change
Maybe I did explain myself in a little too a technical language The basic idea is that if you have a wireless access point (i.e. a router) that accepts only one of your devices (i.e. your notebook), but does not accept your Xoom, you can try and change the Xoom's MAC address to mimic the notebook. The only thing to remember is that you can not use two devices with the same MAC on a network at once. If you follow that rule, you're golden.
P.S. Ah, and forgot to mention that this update will not work on the 3.2.2 for 4G Xooms.

tdaliviu,
Question for you. Since I applied this update I have noticed that my "WiFi Disconnect Policy" keeps reverting back to "When Screen Turns Off" no matter what I change it to.
I am not saying this patch is the cause, but what do you think are the possibilities? Again, I love the capability, and will live with the issue even it turns out to because of this patch, but I just wanted to check your thoughts on it, or see if you thought it might be something to do with the Tiamat ROM.
Thanks for looking at this.
UPDATE: Well I may have gfinally gotten the disconnect settings to stick. Instead of just changing it, letting it sit and coming back later to find out that it didn't, I changed it to the setting I wanted, then immediatley rebooted. Now it seems to be holding the setting. I will let go for a while and see what it does. Will provide an update either way. Thanks again.

For those wondering what this MOD might be good for, there are multiple things. Some ethical and some not so ethical. For instance, as "tdaliviu" mention, if you are trying to simply get around a MAC address problem, you might need to change it. If you were into hacking/cracking or just sniffing around wireless nets that weren’t yours and you didn't want to be discovered or tracked via your MAC. If you just want anonymity. I like it from this standpoint and that of security.
For instance, assume you are sitting in an Airport with your Xoom WiFi up and running, and someone is scanning the airwaves for likely targets to hack. If they seem your MAC address, they will know you are coming from a Motorola device, and might even be able to tell it is a Xoom. If there are any known security flaws, they automatically know which exploits to use against you to gain access. Just being a Xoom might make you a more attractive target. Who knows. But, if you can change your MAC address so that it appears as belonging to a different kind of system, say a "network device" like a wireless repeater, wireless AP, or some other boring target then not only would the attacker not know what exploits to run, but they would most likely just leave you alone without any further investigation or possible portscans.
And of course if you want real anonymity, you might consider changing the name your Xoom provides to DHCP servers when requesting an IP Address. Right now it uses "android_xxxxxxxxxx" with the x's being some number that is specific to your Xoom. I believe that could be used to track back your identity as well. I found several threads and ideas on how to do this. I used the one at http://forum.xda-developers.com/showthread.php?t=760314.
Anyway, thanks again for the MOD!

Quite a strange issue there, Krpto1973. At a loss to what might be the problem. I myself am running Moray, so will do some testing...

Well like I said, I may have gotten it taken care of. It's been holding steady since I set it and immedialty rebooted. It probably had nothing at all to do with your MOD. If anything changes I will let you know.

Guess I spoke too soon. After it sat idle for quite a couple hours, I came back and found it with "No Internet Connection". Once it fully woke up(just a second or so) it immedialty reconnected but when I checked the WiFi Disconnect Policy settings, it was back at "When Screen Turns Off".
Any thoughts?

Sorry, tested on my side. No such problem... Did you do a wipe when you switched to Tiamat's ROM? Maybe there are some leftovers from Stock? I am almost outruling a module problem since it's compiled from Tiamat's source using Tiamat's config.

Krpto1973 said:
For those wondering what this MOD might be good for, there are multiple things. Some ethical and some not so ethical. For instance, as "tdaliviu" mention, if you are trying to simply get around a MAC address problem, you might need to change it. If you were into hacking/cracking or just sniffing around wireless nets that weren’t yours and you didn't want to be discovered or tracked via your MAC. If you just want anonymity. I like it from this standpoint and that of security.
For instance, assume you are sitting in an Airport with your Xoom WiFi up and running, and someone is scanning the airwaves for likely targets to hack. If they seem your MAC address, they will know you are coming from a Motorola device, and might even be able to tell it is a Xoom. If there are any known security flaws, they automatically know which exploits to use against you to gain access. Just being a Xoom might make you a more attractive target. Who knows. But, if you can change your MAC address so that it appears as belonging to a different kind of system, say a "network device" like a wireless repeater, wireless AP, or some other boring target then not only would the attacker not know what exploits to run, but they would most likely just leave you alone without any further investigation or possible portscans.
And of course if you want real anonymity, you might consider changing the name your Xoom provides to DHCP servers when requesting an IP Address. Right now it uses "android_xxxxxxxxxx" with the x's being some number that is specific to your Xoom. I believe that could be used to track back your identity as well. I found several threads and ideas on how to do this. I used the one at http://forum.xda-developers.com/showthread.php?t=760314.
Anyway, thanks again for the MOD!
Click to expand...
Click to collapse
Fantastically stated there, sir. I wasn't aware of the DHCP request issue. You've successfully made me that much more paranoid.

Hmm this mod doesn't seem to work on 3.2.1 (breaks wifi functionality). Planning on updating by any chance?

Sorry, but I'm on Tiamat's Moray ROM right now, which is based on the 3.2 kernel. I certainly plan on an update when Tiamat releases a ROM based off 3.2.1 (or 3.2.2 for that matter).

If you attach a patch ill add it to the repo and give you bunches of credits

Oh, didn't quite expect such a turn of events One patch coming up...

mac_change_mod patch
Here's the patch. It's quite obvious, though took some time to figure it out. It's against the stock Makefile, but as I understood, there were no changes to the WiFi module from Team Tiamat.
Is it going to make it to a future release of Tiamat ROM/Kernel or will it live only as a patch file in the repo?
Code:
--- /home/liviu/Desktop/Xoom/Makefile 2011-08-03 09:27:45.000000000 +0300
+++ /home/liviu/Desktop/Xoom/stock/drivers/net/wireless/bcm4329/Makefile 2011-08-01 21:27:35.395212384 +0300
@@ -6,7 +6,7 @@
-Wall -Wstrict-prototypes -Werror -DOOB_INTR_ONLY -DCUSTOMER_HW2 \
-DDHD_USE_STATIC_BUF -DMMC_SDIO_ABORT -DDHD_DEBUG_TRAP -DSOFTAP \
-DEMBEDDED_PLATFORM -DARP_OFFLOAD_SUPPORT -DPKT_FILTER_SUPPORT \
- -DGET_CUSTOM_MAC_ENABLE -DSET_RANDOM_MAC_SOFTAP -DCSCAN -DHW_OOB \
+ -DSET_RANDOM_MAC_SOFTAP -DCSCAN -DHW_OOB \
-DKEEP_ALIVE -DPNO_SUPPORT \
-Idrivers/net/wireless/bcm4329 -Idrivers/net/wireless/bcm4329/include

Sweet. Cooking and testing. I don't see why this cant make a release. We gotta play with it a bit, but I like this mod. Goes nice with the BT5 concept too

[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.

(Partial solution)NFC goes "to sleep"

Hi Y´all!
Deleted this post in the original forum. Decided to move it here instead.
I have a really annoying problem which i hope someone has an opinion about.
I´ve begun using nfc tags recently and have all sorts of ideas of how to make my day more automated.
The NCF concept however loses a great deal of value if you have to restart tag detection nearly every time you want to scan something. This however is a sad fact in my case.
What happens is that i turn nfc on, e.g. at work. Now tags are detected and everything is just peachy .
I get off, go home, ect. without changeing anything whatsoever.
The next day at work i scan a tag again and now it isn´t detected. NFC is STILL on but tags aren´t detected.
I restart nfc tasker without any effect.
Only when i shut off nfc entirely and restart in the basic wireless & network settings are tags scanned again. The next day everything starts all over.
Do anyone know anything at all about how tags are detected on the software side of things then please i could really use your input.
I found something here about nfc within android which mentions a "tag dispatch system" that evidently decides which app a tag is intended for when it is "discovered"
What i can´t figure out however is which part of android is "responsible for keeping a lookout"
The basic NFC app has been found to be running wether tags are discovered or not.
Please advise.
Regards
ELO
Update april 10th:
Unfortunately i have not yet been able to pinpoint the root of the problem. I have however figured out a workaround.
I´m fairly new to Tasker so perhaps there is a more elegant solution than the attached screendump shows.
I know - i know - crude symptomatic treatment at its worst. Basically a timer toggles the NFC setting on&off once every hour.
But it works.
Regards.
ELO

Polar67 said:
Hi Y´all!
I restart nfc tasker without any effect.
ELO
Click to expand...
Click to collapse
what's your "nfc tasker" app? and what's your phone & ROM & version?
Do your hear the "tag tap sound" when you scan the tag but the "nfc tasker" has no effect?

madfish73 said:
what's your "nfc tasker" app? and what's your phone & ROM & version?
Do your hear the "tag tap sound" when you scan the tag but the "nfc tasker" has no effect?
Click to expand...
Click to collapse
Hi Madfish & a huge thanks for the interest.:fingers-crossed:
Nfc tasker app is NFC task launcher which can be seen here: https://play.google.com/store/apps/details?id=com.jwsoft.nfcactionlauncher
As previously stated restarting this app has absolutely no effect when the problem is present.
Phone: Samsung Galaxy S 3 / GT-I9300
ROM: I9300XXEMA2 / for nordic countries.
Android: 4.1.2
Radio: I9300XXELLA
Root: yes
When i try scanning a tag i get absolutely zero response. No tag tap sound, no nothing.
Only when i shut down & restart basic nfc in settings, as shown in attached sreendump, can i scan tags again and everything works as it should (for a while that is - next day problem is present again).
Regards
ELO

Polar67 said:
Hi Madfish & a huge thanks for the interest.:fingers-crossed:
Nfc tasker app is NFC task launcher which can be seen here: https://play.google.com/store/apps/details?id=com.jwsoft.nfcactionlauncher
As previously stated restarting this app has absolutely no effect when the problem is present.
Phone: Samsung Galaxy S 3 / GT-I9300
ROM: I9300XXEMA2 / for nordic countries.
Android: 4.1.2
Radio: I9300XXELLA
Root: yes
When i try scanning a tag i get absolutely zero response. No tag tap sound, no nothing.
Only when i shut down & restart basic nfc in settings, as shown in attached sreendump, can i scan tags again and everything works as it should (for a while that is - next day problem is present again).
Regards
ELO
Click to expand...
Click to collapse
Something odd is happening. NFC tag detection and dispatch is handled at the system level by the NFC service itself. What tags?

Polar67 said:
Hi Madfish & a huge thanks for the interest.:fingers-crossed:
Nfc tasker app is NFC task launcher which can be seen here: https://play.google.com/store/apps/details?id=com.jwsoft.nfcactionlauncher
As previously stated restarting this app has absolutely no effect when the problem is present.
Phone: Samsung Galaxy S 3 / GT-I9300
ROM: I9300XXEMA2 / for nordic countries.
Android: 4.1.2
Radio: I9300XXELLA
Root: yes
When i try scanning a tag i get absolutely zero response. No tag tap sound, no nothing.
Only when i shut down & restart basic nfc in settings, as shown in attached sreendump, can i scan tags again and everything works as it should (for a while that is - next day problem is present again).
Regards
ELO
Click to expand...
Click to collapse
when problem present, you can try these steps to see what happens:
1. run Terminal emulator (you can download from play store)
2. type in terminal command line:
su
logcat
3. try to scan the tag again, and see what messages come out at then.

krohnjw said:
Something odd is happening. NFC tag detection and dispatch is handled at the system level by the NFC service itself. What tags?
Click to expand...
Click to collapse
Hi krohnjw. I use Xperia smart tags like these. My neighbour had a couple and he didn´t use them for anything. I will most likely get something else down the road but wanted to try this out first. I´ve been using the same tag all along. You think it might be flawed?
madfish73 said:
when problem present, you can try these steps to see what happens:
1. run Terminal emulator (you can download from play store)
2. type in terminal command line:
su
logcat
3. try to scan the tag again, and see what messages come out at then.
Click to expand...
Click to collapse
Interesting. Didn´t know that handy trick. Two questions please:
1: How do i exit logging without shutting down Terminal emulator, so that i can review whats been logged?
2: Is there an easy way to copy the entire logged entries to - say a mail for review on a bigger monitor?
Regards
ELO

Polar67 said:
Hi krohnjw. I use Xperia smart tags like these. My neighbour had a couple and he didn´t use them for anything. I will most likely get something else down the road but wanted to try this out first. I´ve been using the same tag all along. You think it might be flawed?
Interesting. Didn´t know that handy trick. Two questions please:
1: How do i exit logging without shutting down Terminal emulator, so that i can review whats been logged?
2: Is there an easy way to copy the entire logged entries to - say a mail for review on a bigger monitor?
Regards
ELO
Click to expand...
Click to collapse
hold down vol- & press "c"== ctrl + c
you can try logcat -d -f log.txt ( current dir must be writable), then copy log.txt to PC

madfish73 said:
hold down vol- & press "c"== ctrl + c
you can try logcat -d -f log.txt ( current dir must be writable), then copy log.txt to PC
Click to expand...
Click to collapse
It worked. Thanks. I´ll sift through the file and report back my findings.
I also installed Android SDK. Using USB debugging it should, allegedly, be possible to monitor error messages from a single app.
I´ll need to do some further study into that.
Does anyone know of a good beginners tutorial in this regard?
Regards
ELO

Logcat result:
Hi again!
Did stumble across this:
( 2272): Process com.jwsoft.nfcactionlauncher (pid 4900) (adj 10) has died. I/ActivityManager
Any thoughts appreciated!
Regards
ELO

[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