yashsingh1/xdaforums huggingface dataset:
[Fairphone 1] benkxda:
Hey [MENTION=5326336]Fisher_AZ[/MENTION], the amount of people who repartitioned can be very large. My brother, usually just a user and absolutely no geek, surprised me when he told me he followed the instructions of [MENTION=5400999]arghwhymustiregister[/MENTION] and did a repartition. I was really surprised. So I assume it's even idiot proof and every Fairphone user who's facing app storage problems could do this.

Very good points. Especially for already repartitioned devices we should see a save solution.

I really hope the Fairphone OS update will not delete/format the data partition and the users have to fight with losing their apps.
[Fairphone 1] joemier:
News on software update - 8 May 2014

More news on the software update (8 May 2014):

We're currently finalizing long-term stability and field testing on the latest build. We had two cases where we need to verify that those were false positives which would not happen in a user environment. Once we're confident that those incidents were caused by the testing procedures, we'll release the build.

In terms of more significant software development and support, I am trying to get a colleague directly from software team to answer your questions. You deserve answers to these questions, but at this moment our resources are focused on this software update to all users. Thanks for your patience.

Joe

FP Community Manager
[Fairphone 1] JYPDWhite:
Hi everyone,

does anyone can explain me how to fake the serial number with XPrivacy so that the Apps can see the right serial number (which is located under the battery) I tried for about an hour but I didn't get it work for now.

I need that for Navigon which I can't use anymore since I switched from my Samsung S1 to the Fairphone.
[Fairphone 1] mexmorris:
Hi, had the same problem. Simple blocking the identification worked for me with navigon app. I did not fill in any serial number but just blocked identification (serial).
[Fairphone 1] 9x6:
I'm assuming this follows up on these posts in this thread:

Haven't tried this myself for this app, but the general principle should be:

Open the Navigon item in XPrivacy (tap on the app icon in the list)

Tap the menu button (the left-most of the three hardware buttons at the bottom of the front face of the phone)

Select 'Settings'

Depending on what you want, deselect 'use global fake data' (if you want to only provide Navigon with this serial number)

Change the default 'DEFACE' serial number to the relevant serial number. Don't select the check box in front of the number (as it will give you a randomised serial).

Make sure Identification/Serial is still selected (otherwise the problematic serial will still show).

Leave XPrivacy and reset the data Navigon app (Settings > Apps > Navigon > Clear data).

In the troubleshooting forum one user trying to get navigon to work reported a bootloop that they think was caused by using an XPrivacy based approach. Just in case, it may help to be familiar with disabling XPosed from recovery if things do go bad.
[Fairphone 1] Donat.Callens:
Please move your posts to a new thread

Please open up a new thread for unrelated matters. This is in no way relevant.
[Fairphone 1] haiag:
Hey

The update should be live.

I got an email, it should get distributed within two days.

Forced update via clearing the data of Fairphone updater should work.

It did not yet worked for me.

Regards
[Fairphone 1] joemier:
Software update 1.3 is ready

The latest software update for Fairphone OS, v1.3 called Chestnut, is now ready (as of evening 13 May 2014). The Fairphone Updater app should check for the update every 24 hours. You can also manually install the update by following our Q&A to manually install v 1.3. Thanks for everyone's patience as the developers worked to deliver this update.

We look forward to hear your results with it! There are some issues that will have to keep being perfected, eg only certain Bluetooth profiles are optimal. We are getting more resources on the Software team in the next weeks to coordinate this kind of testing and development (among other things).

Regarding questions on internal storage partitioning, we are finalizing proper storage partitioning to prevent separating app from data storage (to unify this storage). We are currently working on fixing last remaining issues and getting the updating mechanism ready for users. We will add a Support Q&A to our website once we have more information to share.

And finally, you can find the full software update log for v 1.3 published here.

Best,

Joe

FP Community Manager
[Fairphone 1] benkxda:
Hey folks, please share your experience with the update process and the new Fariphone OS. Do you see improvements, bugs, what is annoying and what makes you smile? :D
[Fairphone 1] MarcoToo:
That is because those who care gave up on hackability and those with enough cash moved on to a different device, leaving us (those who love their FP) alone with those who don't care - and don't post.
[Fairphone 1] Fisher_AZ:
I actually was referring to the very short term: the software update has been live for more than one week, and no-one had given any feedback here in this thread (BTW, thanks to [MENTION=4465234]benkxda[/MENTION] for reviving the thread). That seemed to indicate at least that the subscribers to this thread hadn't massively encountered problems, given that in the weeks before there still was some activity in the thread.

But on the longer term you certainly are right: Fairphone has lost much of its buzz among the more tech-oriented, and the declining activity here on XDA is not a good sign. Let's hope Fairphone is aware this is a problem, as for the Fairphone project to succeed (in particular their vision of open software design and software durability) they need to retain a critical mass of interested techies/hackers. Hopefully it will get better once the new position of Software Engineer at Fairphone gets filled (@joemier: any news on this ?).

[MENTION=4465234]benkxda[/MENTION]: I just now noticed a separate thread has been created where users report their experience/issues with the Chestnut update:

http://xdaforums.com/showthread.php?t=2750470 (but you probably already knew that)
[Fairphone 1] simsalonaut:
Personally, I just don't have anything to say about the Fairphone OS update, because I am still waiting for the first update to the Stock Android ROM. [MENTION=5382171]joemier[/MENTION] stated twice that the update would roll out shortly after Chestnut. So here are my questions for your next forward to Joe:

1. When can AOSP users expect our first update? What FP OS update will it be based on?

2. If the Fairphone was made 1mm thicker in order to have the glass of the display easily exchangeable, why is it glued on like on any other smartphone, thus forcing the users to exchange the entire display assembly?

Thank you very much.

PS: [MENTION=5697096]9x6[/MENTION], I tried to include your post in the wiki, but I continuously got the error "Sorry! We could not process your edit due to a loss of session data. Please try again. If it still does not work, try logging out and logging back in."

If anyone can help out, please add it, and point people to the wiki. Bunch of useful information for newbies out there.
[Fairphone 1] haiag:
Same queston here! Got into my head today, when I read on the spare part website, that they are glued together.
[Fairphone 1] benkxda:
Oh, did not know that one. Thanks for it. Added this thread to the rare but still updated Fairphone index. Some custom ROMs/kernels as well as mods and themes would push me to update in a higher frequency as well as vivid the Fairphone community on XDA.

Added both of the requests.

I am pretty interested about the glued display. This is what I never did in repairing devices and honestly don't ever want to. It's like using a hot air blower / hairdryer

against

electronics, if you want to "unglue" the parts. Maybe there is a good reason? I don't know. Hopefully it's not that difficult as this iPhone ... really crazy.

Anyway, you can see your requests here:

Requests to Fairphone
[Fairphone 1] boondiordna:
Re: experience with Chestnut

Hey everyone,

my experience was rather... mixed. (Don't get me wrong in the following, it's mostly my fault.)

I had trouble updating: first, the download would not start automatically for three days. Whenever I tried to push the updater, it would start downloading and stop. Hitting the button several times as explained in multiple postings somewhere on the webz did not do anything.

Then, after three days, I pushed it again and had a 178 mb download - which did not install. Again, hitting the button several times as explained in multiple postings somewhere on the webz did not do anything.

I left it at this for another two days, because I had a lot of other things to do. When I checked again, the button now showed "install update". I installed the update, which went smoothly.

Then, disaster struck. Or rather: I was stupid. (Note, FYI: Going to back-link this post on the other thread.)

I only found time five minutes ago to try the following (which did not help):

* reboot into recovery mode

* install from adb [adb sideload googleapps.zip]

* reboot

Meep. Still stuck with the microphone. adb actually installed the gapps (success message, also "optimizing" 37 installed apps on booting).

I then tried installing FP1_Fairphone_OS_v1_3_OTA_2014-05-09.zip as described for the manual update, including the "wipe cache partition".

Again, Android "optimized" some apps, 11 now.

Nothing. Still stuck with the microphone.

I thought to be smart and re-install the googleapps.zip again. And again wiped the partition. Again, Android optimized 11 apps during reboot. And I'm still stuck with the microphone.

I am seriously considering now to restore factory settings, and try to restore my last backup. ****.
[Fairphone 1] Fisher_AZ:
[MENTION=4465234]benkxda[/MENTION], would you mind also including a link to my post #596 in your "Requests for Fairphone" list ? A possible short description could be "Please allow for a considerable amount of time for users to give feedback, prior to a final release of your repartitioning solution. Also, please make this solution optional so users have the option not to modify the partition structure (for whatever reason) without being locked out from future OS updates."

This isn't an issue/question Fairphone isn't aware of already (@joemier has already announced an upcoming Q&A on the support pages), but its importance cannot be overstated. On the one hand, more & more users will run into problems with the small amount of factory-set internal storage. On the other hand, any partitioning/unification solution Fairphone may come up, has the potential to wreak havoc if not every possible scenario has been carefully considered (and preferably tested) in advance.
[Fairphone 1] benkxda:
Added, thanks for your reminder. Will be sent in a couple of hours.

Requests to Fairphone

.
[Fairphone 1] benkxda:
Hey folks,

an article at heise online (German) showed a ranking from rank a brand.

The question was: HOW SUSTAINABLE ARE YOUR FAVOURITE BRANDS?

The title of the blog entry says enough: FAIRPHONE SHAKES UP ELECTRONICS BRANDS (English)

And here you get the image of their contest:
[Fairphone 1] dirtycutmaster:
Mediatek opening their treasure box?

Unfortunately I may not (yet) post new threads, so I have to bring it in here:

Mediatek plans to launch a developer centric ecosystem in Q3/2014 and everyone is like "yeah, finally we will have Custom ROMs for the Fairphone!" We'll see.

http://www.xda-developers.com/android/mediatek-taking-steps-to-be-more-open/

http://www.mediatek.com/en/computex2014/mediatek-labs-launches-a-developer-centric-ecosystem/
[Fairphone 1] haiag:
[MENTION=4465234]benkxda[/MENTION] [MENTION=5382171]joemier[/MENTION] any reactions on the two questions?

I also would like to know, if all the other parts of fairphone version 2 will be the same?

So it would be possible to change the motherboard and get a new chipset?

And I would l would like to know, why does the frontfacing camera makes pictures up to 5 MP, when the technical detail site still says 1.3 MP?

And as last point: Is it possible to include into next update, to decrease the minimum brightness of the display? At night it's still to bright.

Regards
[Fairphone 1] simsalonaut:
Thanks for the link. I get the impression that these folks from rankabrand.de have the same approach to their work as Fairphone itself: "We don't have the capacity to do the perfect job, but we try everything within our limits." So the study is far from thorough or even representative - they only use the information they find on the companies' websites, no follow-up investigation, no long-term tests; if you look at how they work, they only take what everyone can read for themselves and then repackage it.

But then again, that's all Greenpeace does, as well - and you gotta start somewhere. So far, they're only volunteers, let's hope that they get bigger and can do in-depth analyses of the big manufacturers!

Yay, then it's only a matter of a few more years now! :p

Interesting questions - I'd like to know more, as well. Regarding our old requests: Given the speed of Fairphone's replies, I wouldn't expect an answer to these questions until next month. However, it's been almost 8 weeks since the question regarding proper kernel sources was sent out... so I think it's about time we deserve to know what's up with that.

And that brings me to my final gripe: If you want a quick reply from Fairphone, you've got to complain on their Facebook page. It sucks to resort to such measures, but apparently the publicity of it makes them reply on the same day. So if [MENTION=5382171]joemier[/MENTION] doesn't show up here next week, I'd be happy if someone could start *****ing and moaning about it on their FB page... :cool:
[Fairphone 1] joemier:
17 June, update to XDA

Hi all,

Thanks for your feedback under recent requests. I've sent them to the software team, and they'll be replying to you.

We've recently welcomed a new software team member, so I'm eager to introduce him.

Cheers-

Joe

FP Community Manager

---------- Post added at 12:25 PM ---------- Previous post was at 11:40 AM ----------

I should also add about the list of requests:

Software developers are still working on the difficult business of pushing a fix for the internal storage partitioning to all users. More on that soon from Kees, our new software team member.

Cheers,

Joe
[Fairphone 1] _keesj:
Hi,

I am Kees and I have started working for Fairphone at the first of June. As

Embedded software developer and Open Source addict I spent most of my career

doing what I like most: writing software and playing with hardware.

I joined the Fairphone team because I believe that a Fairphone phone deserves

to be running Open Source software. I will do what I can, certainly in the

future, to make this happen.

Currently? Currently I am working on getting the software for the second batch

ready for production. The new phones are to come with an slightly updated

software stack and will be using the new unified partition scheme (Using fuse

to emulate external storage)

At the same time I am looking at the technical possibilities of upgrading the

current phones to the new partition scheme (this is where I hope to get some

technical input form XDA members).

the xrteamer forum has a nice write-up on the layout changes (I might post the

link once I have permission to post links on the forum). and their current solution

(that involves wiping the data). I am currently basing my work on theirs.

One of the biggest (annoying) changes to user is that the phone will no longer

provide mass storage functionality unless an external SD-card is inserted. This

has impact on how a proper backup and recovery can be done (backup using mass

storage and recovery using MTP?). For the typical Fairphone user I estimate

that this will be to much hassle and we need to find an alternative solution.

I was thinking of perhaps requesting the user to temporarily insert an SD-card

for the update. But for now I am still simply looking at the upgrade (not the

backup/restore yet) and this involves changing the partition layout while

upgrading.

I am not used to using forum's much as I tend to prefer using irc and mailing

list but I will try to keep you posted and use your minds as much a possible.
[Fairphone 1] benkxda:
Hi Kees and very welcome here on XDA Developers. Great to have you in here.

I see you have a few ideas, which are also discussed in here, like the partition issue. You're allowed to post links after your post number 30. Until then, just post your link as text. I think you'll soon find out the advantage of those open forums and get used to use it.

If you have questions about XDA Developers or this thread organization, I'll try to answer, but you can also ask with a post in the thread and others might be faster with an answer.

All the best and may the source be with you... yadda yadda yadda you already knew that one :cool:
[Fairphone 1] MoreThanADev:
In early June, a critical security issue was discoverd in the linux kernel

Leading to the devloppement of this app http://towelroot.com/ wich allow user to gain root acces on their phone.

More here.

My phone is already root thanks to Fairphone and I wish no application could get root acces unless I give it to it.
[MENTION=5382171]joemier[/MENTION] Is FairPhone affected by this issue, and if so, are you planning an update to fix it soon ?
[Fairphone 1] _keesj:
Hi,

The Fairphone has been quite "open" in that respect (e.g. root by default) and adbd running as root. We started fixing a few of those issues (for the sake of security) but there is a still long way to go.

About the kernel vulnerability: as you mention it does affect the kernel but has limited impact on the Fairphone.
[Fairphone 1] moddux:
OpenSSL

Hello all,

i just want to say hi and thank you all for the discussion and work done here.

I've read the posts which state the complexity of rolling out updates and that the chip-manufacture is not releasing all sources. But as most of you know Google fixed some OpenSSL stuff with the 4.4.4 update as ArsTechnica mentions ( arstechnica.com/gadgets/2014/06/android-4-4-4-is-rolling-out-to-devices-contains-openssl-fix/ ). What about the fairphone which is stuck at 4.2.2? As this matter deeply infacts security i would like to here an official statement from [MENTION=5382171]joemier[/MENTION] or [MENTION=5757561]_keesj[/MENTION] otherwise it should be forwarded in the next bulk update?

Another thing which I have read in the official forum was that [MENTION=5382171]joemier[/MENTION] ( fairphone.zendesk.com/hc/communities/public/questions/200675058-Native-SIP-support ) would forward the native sip support internally, but i can not find any answers from them. I would really appreciate an update on this matter, because using some third-party software is not always possible especially when you have to test software written by others who only have native sip support on there devices.

Thanks again to anyone participating here.
[Fairphone 1] benkxda:
Hey folks, I added a poll, which is open for 60 days. It's basically to get a better overview. Just for your information, your vote and choice is public, but this won't harm anyone :cowboy:

EDIT:

To see who voted, you have to click on the votes counter of any choice (between the colored bar and the percentage numbers) - a bit tricky to find.
[Fairphone 1] Jisifus:
Nice to meet you, Kees!!

Three things:

1) Are you guys gonna get the stuck-at-14%-battery-bug fixed soon?

2) I'm moderating a tiny subreddit about the topic, and already asked one of your employees once if he could add our community in the social section of your website. No response. Could you ask for me if that's possible?

3) How do you get to work for fairphone? I once met a guy in a mall representing and selling Samsung devices, he completely wigged out when he saw my fairphone, he told me it's his big career goal, working in the netherlands for this device. What kind of people are they looking for? How's the working environment there?
[Fairphone 1] _keesj:
Hi,

I am a developer and will try do do what I can, I won't lie but do not expect 'official' statements from me either as I don't even know what that is. That said I take security seriously and agree we currently are not in great shape. The target for the next build is to start using our own set of keys and close down the biggest holes(root shell).This is the build to be used as a base for the next batch of phone(and upgrades later) but we need more eyes! As you might be aware we don't have full access to the sources but we will need to address the issues stated here within our possibilities. I will come back to you soon.

I can't look into that now.
[Fairphone 1] haiag:
http://www.golem.de/news/android-sm...per-sms-zum-neustart-zwingen-1406-107372.html

[MENTION=5382171]joemier[/MENTION] [MENTION=5757561]_keesj[/MENTION]

After this article you can get a fairphone to restart by sending only a "=" (equality sign). After the article it's probably related to Mediathekprocessor and it can be solved by installing another sms app, which isn't that easy with a dual sim device.

What will be done here?
[Fairphone 1] _keesj:
Hi,

My German ain't that good. can you try and find a English source? The phone should not just reboot like that so we need to fix this.
[Fairphone 1] manu_26:
Ok, I just tried sendind a SMS with only a "="-character as content to myself and indeed the phone reacted with a soft reboot. I use the latest Fairphone firmware.

Here's my translation of the linked article (compressed to the essential information):

###BEGIN of TRANSLATION###

Smartphones can be forced to reboot by SMS

Especially Wiko Smartphones are affected: A simple SMS can trigger a reboot. But there is already a solution.

Many Wiko phones, some Alcatel One Touch, one Acer device and the Fairphone are affected. A reboot is triggered if the phone receives a SMS that contains an equal sign (=).

Smartphones with Mediatek-chip affected

The exact cause of the problem has yet to be found. But it seems that the problem is linked to the used CPU. All affected devices use a Mediatek chip.

The french Blogger Korben[1] was the first to notice. The french blog What If I Told You[2] started assembling a list of affected devices. This was continued by the Technoviel-blog[3].

13 Wiko devices are affected. Not affected: the Bloom by Wiko although also using a Mediatek chip, but already running Android 4.4.

Users can bypass the problem by using a different SMS app (Hangouts for example). But many of the affected devices are dual-SIM-devices, which is not supported by Hangouts. The user doesn't see which SIM SMS's are coming from and cannot choose a SIM for sending. Users report that the app Go SMS Pro[4] supports dual-SIM.

Golem.de asked Wiko about the problem but hasn't got a statement yet.

###END of TRANSLATION###

Please check the original artice for links [1]-[4] since I cannot post links here (yet).

Reading the other sources it seemes that the problem is caused by the default SMS app in the Mediatek sources for Android 4.1 and 4.2. Android 4.4 doesn't seem to be affected. And devices with 4.1/4.2 that are not affected probably have a customized SMS app.
[Fairphone 1] haiag:
[1] http://korben.info/faire-planter-telephone-wiko.html

[2] http://wiity.net/2014/06/14/faille-permet-faire-redemarrer-smartphone-distance/

[3] http://www.technoviel.de/2014/06/vi...nes-lassen-sich-per-sms-zum-neustart-bringen/

[4] https://play.google.com/store/apps/details?id=com.jb.gosms
[Fairphone 1] _keesj:
Here is a description of the bug in french(sorry no link permission) I can confirm the bug.

korben.info/faire-planter-telephone-wiko.html