yashsingh1/xdaforums huggingface dataset:
[Fairphone 1] Teeyee3k:
I can confirm this. I tried smoothing the output voltage of my car usb charger with capacitors, but that did not have any affect. As soon as I turn off the engine or unplug the charger from my car, I get a gps fix again.

It usually gets a lot better once the phone is fully charged.
[Fairphone 1] manu_26:
Yeah. While charging sometimes the touchscreen also behaves weirdly depending how you hold and where you touch the phone. Seems to be an electrical propblem.
[Fairphone 1] ralf_xda:
It seems you have a bad (noisy) charger.

I own two USB wall chargers and one USB car charger. One of the two wall chargers makes the gps non-functional while charging, once the phone is fully charged gps works again. The other wall charger and the car charger both have no noticeable influence on gps. I do not own the equipment to measure the power quality but I am pretty sure that the one which prevents the phone from getting a gps fix emits noisy power while the other two do not. None of them shows any influence to the touchscreen.

There is an interesting article about this:

www . righto . com/2012/10/a-dozen-usb-chargers-in-lab-apple-is.html

(pls remove the white spaces I had to include since I am not allowed to post links).

And last but not least a google search shows how common this problem is with all kind of phone brands.
[Fairphone 1] FP1U:
Hi there,

I recived my FP1U last week and I think I already made a terrible mistake.

I used the partition app below.

Months ago this has worked very well on my wife's FP 1st. edition.

But I didn´t notice that there is a different storage layout on the new FP.

Now I´ve got an 5GB internal storage and you can imagine I´m pretty angry with myself....

Is there a way to revert my mistake?

Looking forward to hearing from you :)

Cheers
[Fairphone 1] _tmp:
Thanks for the test!

In fact the elevation data from the various fairphones is a lot better than the S2, at least in this test:

Amsterdam average elevation is 2m so the ~60m of the S2 seem quite off.

On http://www.gpsvisualizer.com/elevation you can upload any gps track and view the SRTM elevation profile corresponding to the stored coordinates. The values are around 0-5 meters and not around 60.

I used the gpsvisualizer site to replace the coordinates in the galaxy s ii track with the correct srtm elevation values and added this to another gps view: http://www.mygpsfiles.com/app/#LemYkE5y

In summary the fairphone gps elevation looks quite good (keeping in mind that the vertical accuracy of gps will always be worse than the horizontal).
[Fairphone 1] manu_26:
This is what I get using GPS. Sometimes it's ok, but most of the time the fairphone is 20-50 meters off.
[Fairphone 1] drcyber:
i can confirm this but once i got a fix ( plugged off) it seems to work also when i re-plug the Charger in..
[Fairphone 1] _keesj:
Hi,
[Fairphone 1] dbrgn:
Are you saying that AGPS only "kicks in" when EPO is completely disabled?
[Fairphone 1] _keesj:
Hi,

This is what it looks like to me yes but I have no proof yet.
[Fairphone 1] dbrgn:
That would explain why the GPS seems to suck so much... Especially in the car. And as long as I'm in a urban / semi-urban area, quick fixes are much more important than long-term predictions.
[Fairphone 1] chrmhoffmann:
Teaser...
[Fairphone 1] Dr-Shadow:
Is there any news about uart ? I wonder where I should probe it on the board.

I got pics : http://goo.gl/A1zPQD

Faea F2S, uart is on TX/RX/GND

But what's about Fairphone ? There is UTX*/URX*, is this the uart ?
[Fairphone 1] manu_26:
Nice. CM would be awesome.
[Fairphone 1] Dr-Shadow:
Please let this thread be a tech discussion, just use button thanks.

I got more information there : http://droiddevice.ru/download/mtk6589/MT6589_Technical_Brief_v0.2.pdf

It seems URXD1 is RX for uart1 (same for others pins, UTXD1 = TX uart1)

Now I need to locate GND pin and I wonder what is the UTXD1 pin (check the picture, it seems confusing a bit)
[Fairphone 1] paalsteek:
My guess would be

GND TXD4

VCC RXD4

TXD1 RXD1

But it's hard to tell from the pictures and use a voltmeter to check at least vcc and gnd
[Fairphone 1] chrmhoffmann:
After the teaser, now the ROM. Head over to the fairphone original android development forum and get some kitkat love.

Beware that not all is working (no Bluetooth,video recording, hw video decoding and lots of bugs).

Be sure to make an entire backup first and know how to restore it.

Chris
[Fairphone 1] Dr-Shadow:
It seems the kernel source is the same for both FP1 and FP1U (not sure about this)

The detection of model is done there :

https://github.com/keesj/alps-fairp...2550571b/mediatek/config/mt6589/init.rc#L1373

EDIT : Confirmed compatibility for kernel between FP1 and FP1U

I don't know about system (I think partition layout might be different even with 1.6 OS update)
[Fairphone 1] _keesj:
The kernel *is* the same but it is good to keep in mind that different kernels are needed for the different partition layouts.

FYI: Setting of ro.product.model at runtime is not functional yet. The init.rc does not allow using such sh syntax commands and the replacement that uses a oneshot service also doesn't. After boot cat /proc/gpufreq/gpufreq_var_dump | grep "clk_cfg_0 = 1" does reliably discriminates between the model but not at that point in the boot process.
[Fairphone 1] Dr-Shadow:
different kernels or different ramdisks ?
[Fairphone 1] superdragonpt:
I would say different ramdisks, considering its the same kernel Source...

Regards
[Fairphone 1] _keesj:
I described how the MTK partition layout works here https://github.com/keesj/alps-fairphone-gpl/wiki/MTKPartitionLayout . What it boils down to is that a based on an xls file many files are generated that end up in the kernel, bootloader, recovery and flasher. Between the old partition layout and the new one we use less partitions and EBR2 is no longer used but we have ensures=d that the /system partition remains on the same place.

The result of that is that pre and post unified partition the kernels are "mostly" compatible but not in all situation. I expect problems the when swapping the binaries in place like the flasher.

The normal recovery also for example checks for a scatter file inside OTA and compare thems againts a binary version of the partition table.

The differences between 1.6 1G13G and 1.6 FUSE are caused by this change and not different hardware. We use the same kernel and ramdisk for both the models. To keep things simple I would suggest to only support the new unified partition scheme (that will work on both the FP1 and FP1U).
[Fairphone 1] simsalonaut:
Feedback on AOSP 4.2.2 (v2014-08-05)

AOSP user reporting in, thanks for not forgetting about Stock Android!

Red camera tint removed, though might have gone a bit too far, as there is a blue halo visible around the center now

Battery no longer stuck at 14%. Instead, it now drops instantly from ~12% to zero, and glitches when recharging. Doesn't happen everytime though; is it possible that the system needs a few cycles to recalibrate?

EPO: I noticed a few small changes in settings (Update period setting), but with the servers at Mediatek being so unstable, that doesn't really help. This solution by [MENTION=609649]BlaY0[/MENTION] seems to be the best, but since I am a noob regarding baksmaling, I'd appreciate it if this could be implemented into the next update. How about it, [MENTION=5757561]_keesj[/MENTION]? :)

Organizational issue: This thread is getting too long to read - I think it's time to start separate threads for issues like GPS accuracy and so on. What do you guys think?

And last but not least: Over a year since the first post, this subforum is finally dealing with the topics it's meant to deal with: Not just feedback on bugs, but actual ROM development - and that is awesome.
[Fairphone 1] _keesj:
We have confused a few people who accidentally installed AOSP and contacted us because the edge swipe no longer worked. Are many people using Stock Android?

The EPO download will be fixed to the next release but this will be as good as it gets. We are very happy to see ROM development picking up!
[Fairphone 1] madde-:
Problem with the battery suddenly dropping from 1X % to zero also occurs with FPOS after update to 1.6 and repartitioning.
[Fairphone 1] fredflegel:
True! Maybe we should move bug reports etc to another thread?
[Fairphone 1] Unrelashade:
Yes, that's what they are for. Also to have a nice overview over everything and being able to help each other (usually the OP must include everything in their post) use the wiki! :) http://xdaforums.com/wiki/Fairphone_Fairphone
[Fairphone 1] benkxda:
I appreciate to bring up other threads, like bug reporting. And for developing threads it's always better to start a DevDB thread, where you can assign a Q&A thread and you have options to display, like feature requests and

bug reports

.

The wiki needs some work I think. For example there is another Fairphone out there, means, for the Fairphone 2014 you can remove the "M" from the SoC. Maybe we can push it a bit more? Can you place it in your signature? I included it in the (still very unknown) Fairphone index.
[Fairphone 1] _keesj:
xda:devcon 2014

Hi,

We will be joining the xda devcon this year. I hope we can get in touch with some of you. I personally hope to get a better understanding of the XDA eco system and I am also looking forwards to talk to some MediaTek people.

See you there!
[Fairphone 1] Dominik K:
xda:devcon -> Mediatek contact

Good to hear you want to get in contact with Mediatek. Maybe you can get a hint why they're disclosing information about their GSM baseband processor that much. Harald Welte gives in chapter 7 of his

phone "anatomy" paper

[1] reasonable arguments why there's no need for it.

I wish all of you a good conference and best wishes getting in contact with the Mediatek guys. :)

[1] laforge.gnumonks.org/papers/gsm_phone-anatomy-latest.pdf
[Fairphone 1] joemier:
Hackathon/think tank next week in The Hague - win a ticket!

Hi,

To those based around the Netherlands (and not going to xda:devcon), there's an exciting event on the beach near The Hague next week: WTHX. It's a 2-day hackathon/think tank on 25 & 26 Sept. More here:

http://wthx.org

"WTHX is part hackathon and part think-tank, bringing together a diverse group of thinkers and makers to address the themes of Peace, Justice and Security"

And for those in the area who can attend - we have a ticket to give away! Reply with a line about why you want to go, and we'll put you in a random drawing for a free ticket. Hope you can attend!

[hopefully this kind of giveaway is in accordance with XDA guidelines?]
[Fairphone 1] benkxda:
No problems with XDA rules here. :good:

But fix your link, remove the "1". Well, probably all of us know how tho reach the website anyway ;)
[Fairphone 1] Becomebasti:
Does this work for any android devices?

I got the s308 Cubut i can only install on 1gb of 16 gb internal.
[Fairphone 1] haiag:
Is the Fairphone vulnerable though the AOSP browser bug?

Are there plans for a security patch?

Regards
[Fairphone 1] haiag:
[MENTION=2438866]keesj[/MENTION] Sry, I did not linker you here.
[Fairphone 1] Unrelashade:
Hi haiag,

I guess yes, because afaik there is no patch for this security hole. Just don't use the AOSP browser (Firefox is a great alterative) and you'll be safe.
[Fairphone 1] Schnuerschuh247:
I managed to get my FP-Notification-LED to display multiple colors by using the lights.default.so from this thread: [MOD] Multicolor Notification LED

The device used there is something completely different, but it utilizes a MediaTek65xx chipset, so I gave it a shot. I copied the file via terminal directly on the phone, which in hindsight probably wasn't that clever, because it crashed the phone. After battery removal and reboot everything worked fine though. Using LED-tester, I was able to generate 7 colors (yellow/orange and magenta/purple are indistinguishable, the rest works fine). I am using GravityBox for my notifications, which works just fine with the new colors.

Do this at your own risk. It definitely proves that colormixing on the FP is possible though.
[Fairphone 1] haiag:
I would like to get this functionality via the next update.

For me it would bring a much functionality as I have all the colors used by more than one app.

I would even like to manage different colors for different people on the same messenger e.g. Telegram

I also do not like the actual situation with the webkit-bug and other problem with an out-of-date system. Normal users won't do anything for their security... With the next update, the AOSP-Browser should get deinstalled and instead FF should get preinstalled with imported bookmarks (IMHO).

Some heartbeatdevices just work with 4.3+. A friend of mine with a FP has this problem and he's not that of a technical nerd, but he's not satisfied with this update-problem.

This "we-would-like-to-get" thing should be really used like when the design was choosen by the user.

Also I think the information about the ongoing development wasn't perfect with FP1. This whole 1GB/13GB partition thing would have been much more easy, if FP hat communicated this while having the prototypes...

So they wouldn't had to get a way to "repair" it afterwards...
[Fairphone 1] chrmhoffmann:
Fairphone should use Qualcomm. It is the only soc vendor that still has at least some sort of open source approach with codeauroraforum. Mediatek is the wrong approach.

Chris
[Fairphone 1] mexmorris:
I totally agree with you. I am rather disappointed in this os thing too and in fairphone also: only thing they do is let people discuss over at fairphone forum how bad situation is. There are several discussions and polls running you were asking for ( https://forum.fairphone.com/categories). But nothing is done and will be done for FF1. So people can complain, but in the end are left alone. FF's solution: FF2. That's not sustainable.
[Fairphone 1] JYPDWhite:
I totally agree with you too. In the past fairphone said "if you can't open it you don't own it" OK in hardware point of view the fairphone is open (as any other smartphone too...) but in software it's closed like Fort Knox... And that the fairphone 1 owner now will stay at android 4.2.2 is bad...

One year back in time I moved from Samsung s1 to fairphone and I thought "ok this is also a step back in Android version, but that's only temporary" but now I have to state that I have to live with an outdated and buggy android version...

Not nice.
[Fairphone 1] Unrelashade:
Maybe someone or even fairphone can get a crowdfunding up for developing updates and regarding the issues you mentioned above?

edit: i found on the forum though that they are still working on an update

https://forum.fairphone.com/t/software-update-v1-8-temporarily-postponed/3474/12
[Fairphone 1] ShotRu:
Just for the record, as of March 1st 2015 the Google Apps installer from the FP1U (w/ Kola Nut 1.8) grabs a new 123191025-bytes file (dated 27-06-2014) named gapps_1.5.zip from amazonaws.com.

As per fairphonegapps.cfg it has a md5 sum of 9444e40ed5afc9d61530681542f97b97.

Can't post links obviously, but check by yourselves ;)

HTH...
[Fairphone 1] haffenloher:
According to this article, the second Fairphone will indeed come with a Qualcomm SoC.
[Fairphone 1] superdragonpt:
Good News :cool:
[Fairphone 1] Unrelashade:
Would anyone of you like to inform/ make noise at Fairphone about this critical issue that all smartphones have:

http://www.replicant.us/freedom-privacy-security-issues.php
[Fairphone 1] benkxda:
The new Fairphone 2

The upcoming device from Fairphone: The Fairphone 2​

[IMG="Fairphone 2"]https://www.fairphone.com/wp-content/uploads/2015/06/Fairphone2-Header.jpg[/IMG]

Read the article: The architecture of the Fairphone 2: Designing a competitive device that embodies our values

Article at heise: Fairphone 2: Android-Smartphone in Modulbauweise

...including technical data:

OS	Android 5.1

Display	5", 1920 x 1080

SoC / RAM	Qualcomm Snapdragon 801 / 2 GB

Flash Storage	32 GB + microSD slot

Camera	8 Megapixel

Data Connections	LTE/HSPA, Wi-Fi (802.11 b/g/n/ac), Bluetooth 4.0, GPS, Dual-SIM

Battery	2420 mAh (replaceable)

Price	525 €

...yes, that's the price.

Check out this nice animated website.

Official Fairphone 2 video

[YOUTUBE]6DW733G76BY[/YOUTUBE]

...and I already asked about a place for the Fairphone 2 here on XDA. Maybe a forum merge (FP 1+2 in one forum) or maybe a second forum... we'll see :D
[Fairphone 1] Tentos:
Thank you for the overview of the next Fairphone. There has even been an article on XDA News about it. (It was very critical, and while I think that the Fairphone team is always interested in feedback, the article was too negative IMHO).

I just wanted to add that the current Fairphone OS version 1.8.5 has been released. I was one of the lucky few where the original OS version 1.8 worked withouth any problems, and I got accustomed to the KitKat-style launcher. Version 1.8.5 comes with the old launcher, but the KitKat launcher can be downloaded at

ht tp://storage.googleapis.com/fairphone-updates/FairphoneKitKatLauncher_10.apk

The link has been provided by Rick on the Fairphone forum.

I would of course be interested what the current situation is for an update to KitKat, but if I have understood correctly, there are not any real news (unfortunately).
[MENTION=5757561]_keesj[/MENTION] posted an article about the software situation back in December: ht tps://ww w.fairphone.com/2014/12/09/our-approach-to-software-and-ongoing-support-for-the-first-fairphones/
[Fairphone 1] Hyst:
FYI

https://www.fairphone.com/2015/09/16/long-term-software-support-fairphone-1/

Wonder if they could provide the sources so that the community can also start porting other roms. But probably the license prohibits that.
[Fairphone 1] Vinnl:
Perhaps, but this is already fantastic news! I'd be so happy if I could run Ubuntu or Firefox OS :) [MENTION=2438866]keesj[/MENTION], thank you very much for all your hard work up til now :)
[Fairphone 1] _keesj:
Hello,

If you guys want to interact and talk about the future of FP1 (but also talk about Fairphone 2!! ) please join me at

https://www.eventbrite.com/e/opening-up-the-fairphone-2-software-supply-chain-tickets-18756253459

Have you also read this article?

https://www.fairphone.com/2015/09/23/opening-up-fairphone-to-the-community-open-source-fairphone-2/

Greetings
[Fairphone 1] Unrelashade:
Yeah, app terminating doesn't effect how RAM is handled, if it's full then something gets terminated by the system.

However terminating can be useful in other circumstances, for example when an app does stuff like checking for something on the internet. It may make sense then to terminate it, because it won't use ressources then (like data and/or processor usage).

I don't see why 1 GB shouldn't be enough since my device has less than 1 and runs perfectly smooth. It might be useful in the future for newer Android versions, but I am quite happy with how Android is now anyway (I'm using 4.2). Also there may be alternatives in the future which are faster/ more lightweight. Getting rid of Google Apps makes it faster/ more lightweight as well. And it's too late to debate this now anyway, I guess.
[Fairphone 1] asmaron:
So does it make sense to kill apps in cache or open apps to save battery life? Or has it no effect? In my preferences i can see that there are "active" apps and apps in "cache". Do the apps in cache also take battery life? Makes it sense to kill them, to save battery life?

Regards,

Asmaron
[Fairphone 1] topnomi:
Apps only use power when they do something. Sitting in RAM or cache doesn't use power. Android already has advanced task management, the only reason to kill apps is if they are misbehaving (ie, using data or gps when you don't want them to).

If you're concerned about battery life install an app called "cpu spy reborn" from market, and get "better battery stats" (paid in market, free on xda). Check cpu spy later and see how much time your phone is spending in deep sleep. if it is spending a large percentage in deep sleep then your apps are not causing issues. If it's not using deep sleep, or spending lots of time in the next level up (200-300mhz usually) then you have apps causing wake locks. You can investigate with better battery stats to see what apps are causing wakelocks. then look into updating/replacing them.

if it's an android system component causing wakelocks, then it's a rom/kernel issue.
[Fairphone 1] drcyber:
"1024 MB ought to be enough for anybody." ;)
[Fairphone 1] KimHansenDenmark:
Hi Asmaron,

I have some data from ChangHong in regards to the SAR:

I also have more detailed information I can send you if you are interested.

Best,

Kim
[Fairphone 1] benkxda:
Yes, unused RAM on Linux is wasted, ok. But no, it's not completely useless, because of...

..."if it's full then something gets terminated by the system". I don't want that the system kills a running app, which I don't want to be killed. I want to select the app(s) which can be killed.

I have no problem with my 1 GB device as well. Currently it's no problem. But again to [MENTION=4407430]drcyber[/MENTION] it will be not enough in several years. Like I told, I used the HTC Hero in 2009 with 288 MB. Are you sure, a device with 288 MB RAM would work properly with Android 4.3? I just checked my Google+ app on my tablet. It uses 102 MB, would be 186 MB for the system and all other apps and background services - this wouldn't be a pleasure to use. We only can hope that development not only consumes more RAM in the Android future.
[Fairphone 1] drcyber:
This should have been just a funny Quote , guess who said this originally? but not with 1024mb , with 640kb ;)

i have a 512mb Device (xperia arc) atm and it runs like it should, of course there should always be more Ram , more CPU-power and so on ,but i think im happy with the 1Gb of the FairPhone :) at least for now.

I know what it means to have not enough Ram with android, i had the HTC Magic, 198Mb or something..but i had Gingerbread running on it , and it was quite useable ;)
[Fairphone 1] ivifly:
Hi to everybody!

I follow the developing of the fairphone and i hope to get here a answer...

I looking for the possibility, to cut the right of the user app. Like with PDroid.

Is something coming about that ?

Thank you for your anser!

Lg ivi