yashsingh1/xdaforums huggingface dataset:
[Fairphone 1] boondiordna:
Known issues - mood background

[MENTION=5382171]joemier[/MENTION] : Thanks, we saw this.

My FP started a lengthy FP-OS update download an update this morning while I had a crappy WiFi connection , but I did not pay any attention, and my phone still shows 1.1 Caju. Are you guys testing OTA stuff at the moment?

[MENTION=4465234]benkxda[/MENTION] already forwarded you my note that at least in case a lot of issues vanished after turning off the 'mood background'. Don't know how closely you monitor your own Zendesk forum, but I tried to cross-reference some threads there, asking for feedback after de-activating the mood screen. Some people responded that their problems also got much better or vanished since disabling.

Links, for your convenience:

https://fairphone.zendesk.com/hc/co...s/200700688-FP-Crashes-When-will-it-be-fixed-

https://fairphone.zendesk.com/hc/communities/public/questions/200787378-Reboot-during-calls

https://fairphone.zendesk.com/hc/co...when-Power-button-touched-during-incomig-call

https://fairphone.zendesk.com/hc/communities/public/questions/200754863-n7player-reboots-fairphone

But please check also this, where a problem with the touchscreen persists:

https://fairphone.zendesk.com/hc/communities/public/questions/200826986-Sensibility-and-reboots

HTH.

--

Edith sez, I forgot to mention this:

Thomas Guttsche said, in one of the above threads: "After removing all widgets from the lock screen, everything was fine again. So from my point of view the widget on the lock screen have been the root cause of my sudden reboots."

Just an Idea: [MENTION=5382171]joemier[/MENTION], your developers should really look into that. I'm really a noob, but probably someone at XDA can have a look at the github sources of FP OS? Maybe, something screws up all widgets on the lock screen.
[Fairphone 1] joemier:
Thanks to you all who have tested disabling the Mood Background issue that prevents crashing. Indeed, Fairphone and Kwamecorp are aware that the bug lies in the lockscreen - which involves a lockscreen pattern, widget, or as you mention the Mood Background. We've now added that disabling the Mood Background may help with this issue to the Q&A.

Fairphone Support Team is still formalizing their processes so they can better answer the questions on the forum, but one-to-one issues via Support or by e-mail are top priority (and there's still a backlog there). Thanks for the patience.

Cheers,

Joe

FP Community Manager
[Fairphone 1] benkxda:
Hey guys. To clear this issue, the phone numbers starts with (for example) +49 123456789 but shows up only 0123456789, did I get this right?

And a question to all you hardware hackers. Is there a how to / guide out there for a Fairphone teardown? I did not find any. I have to open my brother's Fairphone to clean the dusty camera lens. As I have quite some experience with opening electronic devices, I am not afraid, but I also know, sometimes things can go bad.
[Fairphone 1] dirtycutmaster:
No, the issue is with numbers that have no country code (and could be only numbers starting with 0151). So a number stored like 0151 1234567 shows chinese signs on the right, a number like +49 151 1234567 shows "Deutschland".
[Fairphone 1] Vinnl:
I guess so, it's just that the post I was replying to was in this thread as well.

In any case, thanks for the help! And for those not knowing how to disable the mood background (I had to look it up): In settings, under Display, it says "Mood background on lock screen". What this does is colour the lock screen red when your battery is low, and blue when it's not. Not that much of a loss to me, and solves quite some bugs apparently.
[Fairphone 1] benkxda:
Ok, I think I got it now. Thanks for clarifying. :o

Teardown

...at least a bit :silly:

My brother complained, he thinks he has some dust underneath the camera lens cover on the back. So I checked that. It was dust. And I remembered a Fairphone quote...

So we owned it :cool:

Here are some screenshots with comments on top.

Opening metal backsided lid.

Removed battery, SIM card and micro SD card.

Close-up of the dusty camera lens cover.

After removing five screws, you can remove the frame which covers the circuit boards.

Removing the frame was a difficult and hard work, as it is clipped very tough and tight. If you have the right tools, don't be afraid, but still be careful.

Picture from inside after cleaning. The square black rubber around the lens cover does not protect well. It probably is just too thin.

Other than that, the whole circuit boards and all electronic components where dusty on the top of the device. Possible reasons: USB port, earphone jack, power button

EDIT:

Just a moment ago, I sent the request to Joe. I hope he has some news for us soon. But of course, now they probably check every announcement twice before publishing it.

Requests to Fairphone
[Fairphone 1] joemier:
Hi all,

I still need to follow-up with a response to XDA and [MENTION=4465234]benkxda[/MENTION]'s requests, but for now a response to the below.

My colleague on the Product team tells me that the AOSP update will hopefully come out a bit after the next Fairphone OS update (expected end of March). We would provide it on our Support Center in the Downloads section.

Product team is trying their best to give more information on this issue, but it requires a collaborative effort from Mediatek and the engineering team at the production factory in China. Unfortunately, I don't have any more news to share with you all.

An important point to keep in mind is that Fairphone did not choose Mediatek as the chipset provider, this is a relationship directly between the chipset provider and factory. Of course, we chose the factory but this adds a layer of complexity and more actors involved than just one line between Fairphone and the chipset manufacturer.

Hope this helps.

All the best,

Joe

FP Community Manager
[Fairphone 1] JY-G3:
Related:

CyanogenMod for MediaTek devices: http://xdaforums.com/showthread.php?t=2274332

OmniROM For MTK Devices: http://xdaforums.com/showthread.php?t=2483238

Faea F2S (MTK6589) Android 4.4 Omni ROM Released: http://www.gizmochina.com/2014/03/13/faea-f2s-android-4-4-omni-rom-released/

Kernel changes between AOSP and MediaTek: https://docs.google.com/document/d/1J2LxPTLSqpq71ivrfyXdKxtPnugISvvNnO-WzyxQBW0

Kernel for MT6589 / MT6589M / MT6589T: http://xdaforums.com/showthread.php?t=2670044

MTK6589 Compile Environment: https://github.com/faeamobile/mtk6589-compile-environment
[Fairphone 1] dirtycutmaster:
I didn't try Facebook, but had this issue with Twitter, also "Simple Image Wallpaper" didn't keep the fullscreen background image during reboot. Another user couldn't keep "Swiftkey" as his standard keyboard and had to re-enable it after every reboot.

Workaround: Moving the related APP from Phone to internal storage helped in all these cases, so it seems to be related to where the APP is installed.

This gets me to the point about the partitions on the FP. I had to root-explore to delete the unneeded log files in log_other_mode folder as described here (fairphone.zendesk.com/hc/communities/public/questions/200806683-Another-query-on-internal-storage)* to free up some memory to be able to move the apps to internal storage. So I would recommend to also have a look if those backup logs are really needed but can be stored wherelse or provide an official and easy to use solution to repartition the phone as described somewhere in this thread (fairphone.zendesk.com/hc/communities/public/questions/200667593-Internal-Storage-)*.

*sorry, not yet allowed to post external links :silly:

Btw: all in all I am really happy with my Fairphone and how you cope with our feedback. Samsungs and Sonys and whatever have other issues - and those seem more and more to be declared as "features" instead of taking care like you do. Fairphone somehow IS a china phone (with all its bugs and capabilities), but a quality one. Love my Fairphone :highfive:
[Fairphone 1] Hyst:
[MENTION=5382171]joemier[/MENTION]
[MENTION=1656095]benxda[/MENTION]

Hey there. I can confirm that it is not personal taste.

As described here http://xdaforums.com/showthread.php?t=2647294 I've got a new phone, becuase the old phone had a broken headphone jack. And now my touchscreen problem is gone.

To give a little more detail on the subject:

It happens when you do light or fast touches. It was the worst, when I tried to barely touch it and just kind of hovered over the screen. When I did a strong and longer press it worked mostly correct.

In the thread I posted above, I also did two screen tests (the one from the engineer mode) and I also posted both screenshots. one is from my old phone (which had the problem) the other one is from my new phone (where I don't feel it anymore).

What I did to produce this screenshots was to barely touch the screen. doing fast and light touches.

As you can see when you compare the screenshots: the old phone hat a lot of wiggeling. It was nearly impossible to get a nice small dot. As for the new phone, you sometimes still see a line where there shouldn't be but the overall picture is much much nicer.

One last remark: I did this test a couple of times with the new phone, and the lines appeared always at the same region. I suggest that this might be a calibration issue or a assembling fault.

hope that helps. If you need something else let me know. As my old phone got replaced I can give you my IMEI-number so that you can try and get your hands on it, to have some phone to reproduce this issue and investigate a little further.

Bye
[Fairphone 1] Tommcal:
Still Wifi Problem

Hello guys on community and [MENTION=5382171]joemier[/MENTION], i'd like to repost about my problem that has not been solved.

I am not able to connect at the wifi and/or bluetooth on my Fp. The situation is that i try to turn on the WIFI via system settings or via the swipe menu on the top side of the screen, and nothing happens.

I want to describe this very clearly: the point is not that i can visualize some wifi and then i cannot connect with one of these; the point is that i CANNOT arrive at the point in which i can select a wifi network. The phone got "lost itself" while turning on the wifi, and never got back. Every once in a while, if i open the top swipe menu, i can see the icon wifi blinking in blue, as if the phone is trying to do something with the wifi (calling for a connection that has to be closed from before? I don't know).

Devices that are gone on my FP

- Wifi connection

- Bluetooth connection

- Wifi Tethering

I got in touch with the tech support and asked for a replacement; they sent me another phone, that worked, but after a week the problem represented itself. I have no some strange wifi router, i have a normal router with no strange settings that, as long as i know, could have caused this problem.

Do a factory reset, you would say. With the Fairphone number one, i tried 15+ factory resets with all the possible isos, and nothing changed. With the phone number 2, i got in touch with Kwamecorp guy Tiago Costa that told me to factory reset at system Almond, which i did, and nothing changed; then told me to revert to AOSP and that the Wifi Issues are going to be fixed in the upcoming update.

I have still not reverted to AOSP because i want to wait for the upgrade and see if this works. Someone has expertise with this type of problem, that as i can see on the internet is something that happens for other devices as well?

Regards

Tc
[Fairphone 1] Fisher_AZ:
Issues with apps installed to Phone Storage

This seems to be a wider issue affecting [potentially] many more apps. I had a problem with the "Delayed Lock" app (https://play.google.com/store/apps/details?id=de.j4velin.delayedlock2.trial). This app requires Device Administrator status to be able to disable the lock screen under certain conditions. However, it would lose that status after some time (and pretty much after each reboot), forcing me to re-activate the Device Admin status of the app each time. As I could see the similarity with the problems quoted above, I moved the app from Phone to Internal Storage. I've rebooted many times since, and haven't encountered the problem anymore.

Because it is rather predictable that more apps may/will not function OK when partially in the Phone Storage, the Internal Storage logically becomes the best choice as the default install location for apps, contrary to the advice given by Fairphone (https://fairphone.zendesk.com/hc/en-us/articles/201154666-How-are-apps-stored-on-my-phone-Internal-Phone-and-SD-Storage-). The next problem is then that given all that, 1 GB of Internal Storage really isn't enough these days (let alone in a few years). This motivated me to go ahead and re-partition the internal/phone storage, before spending more time on customizing my phone (as all user data is inevitably lost in the process of partitioning). I followed the approach as described in the wiki (http://xdaforums.com/wiki/Fairphone_Fairphone/Guides#How_to_partition_your_Fairphone), and it has worked perfectly: I now have 7.03 GB Internal Storage and 6.83 GB Phone Storage.

One observation though: after re-installing some apps, I notice that almost all of them have the "Move to Phone Storage" button greyed out, even for apps where that option was available prior to partitioning (my storage settings are: "internal device storage" as preferred install location for apps and "phone storage" as default write disk). I'm not too worried about this, as I'm quite confident that I will be able to install all my apps in Internal Storage for the lifetime of my Fairphone. And the default write disk option seems to work as well: offline dictionaries for Google Translate are indeed downloaded to the Phone Storage. Oddly enough, Google Translate is the only app I've seen so far for which the "Move app to Phone Storage" button *isn't* greyed out.

So in summary: as far as I can foresee, the applied partitioning will serve me well into the future. But just from a curiousness/[trying to understand things how things work]-point of view, I'm a bit puzzled why the "Move to Phone Storage" button would be available less often than it was pre-partitioning. Does anybody have any ideas/insights into this ?
[Fairphone 1] joemier:
Fairphone OS v1.2 "Release Candidate" now available

Hi XDA,

We've made public the Release Candidate for Fairphone OS v1.2. It's the manual, preliminary version of the official update. The official update still needs a couple weeks before a complete version can be released to everyone, but when it's ready it will come over Wi-Fi with the Fairphone Updater app. We apologize we can't get the official update out sooner.

We expect this Release Candidate version to handle the following issues:

•	Camera issues and black screen

•	False roaming notification

•	SMS app and scheduled on/off not working with Dutch system language

•	Improved compatibility with certain Bluetooth profiles

Any feedback, please write here or on our own forum topic here.

Cheers,

Joe

FP Community Manager
[Fairphone 1] Hyst:
[MENTION=5382171]joemier[/MENTION]
[MENTION=1656095]benxda[/MENTION]

I wrote already in the forum joemier suggested, but I want to do it here, also. Maybe someone has still the same problem, and they don't check the Fairphone support forum.

Hi Fairphone-Team,

I **was** really happy when I saw that there is a new update. As I suffer from a bluetooth problem with my car.

I know this is just a ReleaseCandidate, and you said you still need a couple of weeks. BUT in the "release notes" for the RC one can read:

"Improved compatibility with certain Bluetooth profiles"

So I thought that this would include:

https://fairphone.zendesk.com/hc/en-us/articles/201621453-Bluetooth-Profiles-

or

https://fairphone.zendesk.com/hc/en-us/articles/201896728-Bluetooth-connection-Cars-

But it does not. At least not for me. So I am quite disappointed and hope that you will finally fix this in the next release.

a few more details:

I drive a Toyota Yaris with Toyotas Touch & Go system. Which supports:

HFP, A2DP and AVRCP

As the Fairphone supports all of those listed above according to:

https://fairphone.zendesk.com/hc/en...I-search-for-other-Bluetooth-enabled-devices-

I wish the Fairphone would also support PBAP, DUN or PAN, since my Car is capable of those profiles.

But my phone and my car do not like each other. The car worked with many different devices (iPhones, very old nokia phones, Samsung phones).

Would like to hear from Fairphone about that issue. Are you guys aware of this? Maybe you could try and go to your local Toyota Dealer and ask if you could use a car to troubleshoot or something.

Still hoping for the best here, I really do not want to change my phone.

Bye
[Fairphone 1] joemier:
Hello,

Regarding the Bluetooth profiles: I'm sorry to say this was a miscommunication on our part - the Bluetooth profiles are not yet ready for software update shipment. We'll give more updates as we hear them - Bluetooth profiles are on the bug list for software developers but issues like the camera and crashing had to be prioritized.

Apologies again for the miscommunication.

Best,

Joe
[Fairphone 1] therob84:
Repair and Teardown Manual of Fairphone (iFixit)

Today Fairphone and iFixit released the full Repair and Teardown Manual and the Spare Part Shop for the Fairphone:

Fairphone Guest Blog:

http://www.fairphone.com/2014/04/03/ifixit-guest-blog/

Spare Part Shop:

http://buy-a-phone-start-a-movement.fairphone.com/en/spareparts/

iFixit-Homepage:

http://www.ifixit.com/Device/Fairphone

Cheers, Robert
[Fairphone 1] benkxda:
Great news! Especially the spare parts are fantastic for the Fairphone owner.

Greets and thanks to Miro from iFixit. :good:
[Fairphone 1] chrmhoffmann:
kernel source 2

Hi,

the newer kernel source compiles fine (prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6), but it doesn't run. I replaced the original kernel with the new compiled one, added MTK header and repacked the boot.img. I am normally able to do that (with other MTK devices), but on FP1 the device reboots with blue screen.

Command to compile kernel:

TARGET_BUILD_VARIANT=user TARGET_PRODUCT=ahong89_wet_jb2 MTK_ROOT_CUSTOM=../mediatek/custom/ make -j8

I checked that the boot img has the KERNEL and ROOTFS mediatek headers. Any clue [MENTION=5382171]joemier[/MENTION], [MENTION=4465234]benkxda[/MENTION]?

Rgds

Chris
[Fairphone 1] chrmhoffmann:
Just raised this issue with kernel sources to support. They told me to ask xda or FP forum. I think this is not going well :(
[Fairphone 1] MarcoToo:
At least it compiled. A miracle considering the whacky hacky code provided by mtk..

--
[Fairphone 1] chrmhoffmann:
Other MTK device makers provide kernel sources that compile __and__ work. #failphone.
[Fairphone 1] benkxda:
That sounds to me like "go somewhere else, I don't want to really help" - customer(idont)care

Pointing to XDA or FP forum already states, that they have no clue about this problem.

So still no support from MT for the correct sources. But how should Fairphone help there? Afaik they did not choose MT directly. MT was a contractor of the manufacturing company and this was bundled.

Do you have short title + description? I want to add this to the requests to Fairphone.
[Fairphone 1] chrmhoffmann:
Working kernel sources:

The kernel sources that Fairphone has published do not work. The compiled kernel reboots with a blue screen. Please provide information how to build the kernel correctly or provide working sources.
[Fairphone 1] Hyst:
It is really sad to see that there is really NO development going on. Not even fruitful discussions. It took some time to finally get a subforum on xda and now there is very little activity here. Even my old phone has more going on in it's subforum. And it is in the "low activity device" category.

The only things you see here are complains about some issues the Fairphone has. This is not the way how it should be. The way it should be is, the forum should be very active and be flooded with threads about different custom roms. As the phone was promised to be open.

Besides Fairphone did say somewhere (I think this statement is not online anymore) that porting new android versions would be easy and fast. Well, we still do not have KitKat. And I doubt at the moment that Fairphone will ever provide KitKat support (or later android versions). Just look here

And since there are no custom roms availible we are stuck with jelly bean. If I really want to switch to a newer OS I would have to buy a new phone (which would make me very angry, since this is not why I bought the fairphone in the first place).

Additionally we were promised an Fairphone-OS update at end of March. All we got was a Release Candidate. I know deadlines are a pain. And I do not have a problem with waiting for an update. But now we have end of April and still no new Fairphone-OS release (one month late). I am still waiting for the Bluetooth fix. As this is a Android 4.2 bug it would be solved if Fairphone got a KitKat port. Or if they check with other developers who fixed this bug in various 4.2 custom roms.

I am quite disappointed again how the Fairphone team is communicating to the community. And I am a bit angry, that they promised stuff they could not keep. I know that some things did not turn out in their favour and they cannot do much about some issues. BUT STILL.... I bought the phone because of some assumptions I made, because of the promises the Fairphone made.

:(

Sorry but I needed to get this of my chest.
[Fairphone 1] manu_26:
I have to agree.

My motivation to buy a Fairphone was (besides the effort to achieve fairer production) to have a phone that is mostly open in terms of hardware and software. While I think that the hardware part is on a good way with the availability of spare parts I think that the software part couldn't be much worse.

First of all: When the Fairphone was delivered I already have had KitKat running for months on my old Samsung Galaxy S. So delivering the Fairphone with 4.2.2 is kind of OK but not really awesome. Now I read that Fairphone doesn't even know when or if they will be able to upgrade to KitKat. WTF?! "Buy a Fairphone", they said. "You won't be dependent on evil companies that support their phones for maybe a year and then you're stuck with an old android version", they said. "Fairphone will allow you to install different operating systems", they said.

Right now I have to conclude that we neither get an official up-to-date software nor do we get the ability to have community-developed ROMs. That's a FAIL-FAIL in my eyes.

My understanding is that Fairphone is 100% dependet on Mediatek/A'Hong in terms of Android development for the hardware used in the Fairphone. Furthermore I read in different articles that Mediatek obviously violates software licenses by demanding money for the source code. I really don't know who's to blame for what, but I guess that Mediatek seems to be the worst choice if you're trying to build an open Android phone.

I really would appreciate a more honest and detailed answer from Fairphone like: "Yes, we ****ed up. We didn't realise that A'Hong works with Mediatek and that it's a bad choice until it was to late...Sorry!" or maybe: "The situation right now is not satisfying. This is what we are working on to get you guys a working source code and it will take this much time."

But I only hear: "Here's the source code: have fun (no, we didn't check wheter it was working or not...)."

I'm sorry if these words sound a bit harsh, but I'm really frustrated right now.
[Fairphone 1] MarcoToo:
That is because Fairphone themselves did neither hardware nor software. They had someone do the hardware + firmware part and someone else do the software part, doing the planning, marketing, and distribution themselves. In my opinion, they had no idea what they were getting into, announcing a hard- and soft-hackable smartphone without ever getting involved with either hardware or software. As a result, what they made is a fair trade smartphone which they can't support any longer than their OEM allows them to. And the community can't take over supporting it for the same reason.