yashsingh1/xdaforums huggingface dataset:
[Fairphone 1] _keesj:
Hi Jisfus, I don't know yet about that issue ( I need to get some more info ) but I am currently fighting bigger problems. If there is an easy/quick fix we might.

I subscribed to the reddit. If hope if gets bigger/more active you should ask again (but not me) :p

It is still early days for me here but so far people here are driven by passion and may interesting (not only software) project are happening. Myself I have worked on Linux and Android platforms before and already lived in Amsterdam so Fairphone simply was a good match.
[Fairphone 1] MoreThanADev:
Here is the link.

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

Main ideas are the same as in the previous article:

Receiving the charactere '=' with an sms make the phone have soft reset (no pin cod is asked after reset).

It kills every app curently running and stop phone call as well.

This bug is also apeare on other roms (i.e cynogen). The writer has not much clue about what is the cause of the bug, but suggest it might be in he code of the "baseband chip".
[Fairphone 1] _keesj:
Hello,

The bug is in the GPS location provider. I causes a crash of the system server because it run's in that context. I found similar code (listening to SMS messages) in Android 4.4. to get ephemeris data. From the look of it (and I only have a stacktrace) this code tries to launch some GPS tests and was badly implemented.
[Fairphone 1] Hyst:
Hey [MENTION=5757561]_keesj[/MENTION]

welcome. It is nice to see a developer beeing active here. Apart from all the security issues already mentioned, my question to you would be the same which I already asked here. It concerns the bluetooth stack problem. Some people (including me) have problems when pairing the phone to a bluetooth headset (in my case my car). This issue is already known (link and link).

So do you know anything about the bluetooth issue?

edit: forgot this link for a detailed description of my problem: link
[Fairphone 1] _keesj:
Hi,

We are currently working on different things:

-The SMS reboot bug/ security updates.

-Production images for the Fairphone 1 U.

-An Updated Fairphone updater that allows to switch to between Fairphone OS images and what we call Stock Android builds.

-A method to upgrade from the Fairphone 1 partition layout to the new partition layout(to be able to use a single build/image for the current set of Fairphones)

Once this is done we will looks at what we can fix for the current generation of phones. On the radar (GPS quickfix fixes, small changes and other low hanging fruit). We do have to keep realistic. What I personally would like is for MTK to release a 4.4 update for us.
[Fairphone 1] manu_26:
That would be really nice. On the other hand the next Android version (L) is on its way and is expected to arrive in fall 2014. Maybe it would be even better to skip 4.4 and go directly to the next major release.
[Fairphone 1] moddux:
Hello

That sounds promising, currently there is only one "Stock Android" build, so we can expect more of them?

Talking about security, as i read today the Andorid KeyStore is flawed in versions before 4.4 ( securityintelligence.com/android-keystore-stack-buffer-overflow-to-keep-things-simple-buffers-are-always-larger-than-needed/ ). It's stated that it is not trivial to abuse this vulnerability but still the KeyStore is an essential part. That's another reason to hope for a release by MTK (maybe it can be used as an argument for you).

Thanks for the look into your roadmap.
[Fairphone 1] haiag:
Joe answered our question with the touchscreen on facebook:

I took just one hour, maybe we should put all questions there...
[Fairphone 1] haiag:
The German website golem.de reports, wiko is updating their phones to react to the =-bug.

Maybe fairphone could connect to them to get information about it? [MENTION=5757561]_keesj[/MENTION]

Source:

http://www.golem.de/news/android-wiko-behebt-sms-bug-in-smartphones-1406-107520.html
[Fairphone 1] _keesj:
Don't expect big updates in terms of Android API at this point but yes we will create new "Stock Android" builds and release them.

Thanks for the pointer
[Fairphone 1] benkxda:
New builds are very welcome I guess, as Fairphone is falling behind Samsung. Even they're updating their devices to 4.4.2, I guess.

Well, as Google announced the Android One device at the I/O 2014, it finally came out that they will use a Mediatek SoC. Maybe this will help Mediatek find the way back to a more open relation to the rest of the world.

Kees, good to have you in here. On which other developer platforms are you working for Fairphone? Maybe we can combine Q&A or something like that, would make your work easier, reaching more people with one post... until now it's only a thought.
[Fairphone 1] Hyst:
[MENTION=5757561]_keesj[/MENTION] about the bluetooth issues. A friend of mine found this changeset which might solve the problem. It is already in CM and therefore in many other custom roms, but not in AOSP. But merging this into FP-OS might be a quick task.
[Fairphone 1] _keesj:
Hi,

We got the trivial fix for the crash and have tested builds with this patch. The build also include a few of the changes I mentioned earlier(A new updater and a Stock Android option). The biggest hurdle at this stage, as with all the updates we sent are the google apps installation. Doing a simple update is disruptive for the people who installed gapps. Not only do they have to re-install the google apps they also first have to figure out how to re-add the google appps installer widget to their home screen. Not very smooth.

An other problem we have seen is that if the google apps where updated by google (e.g. re-installed on /data) they start to crash just after an update because they miss critical services (google play store).

We don't have fixes for these problems and I we are therefore a little reluctant to sending out an update right now to unsuspecting users. Doing a few more weeks of development would possibly allow us to include more features in the build (mostly taken from this forum) and possibly find workaround the gapps problems.

An other possibility, if you are in a hurry or want to help out, would be to install an OTA using sideloading. If you are interested in that sort of thing[tm] PM me explaining how you would "unbrick" you phone.
[Fairphone 1] haiag:
[MENTION=5757561]_keesj[/MENTION] thank you for your openess! I appreciate it much more than to be left in the dark about it! Thanks again!
[Fairphone 1] joemier:
Hi,

I'm writing for [MENTION=5757561]_keesj[/MENTION] who is on holiday off and on this month. As mentioned in his 2 July post, software team is still working on the next build that would address some of these request issues like the = Mediatek SMS bug, as well as a new Fairphone Updater app. As you can imagine there is also attention these (past) weeks on the software for FP1U, our 2nd batch phone being shipped this month.

[MENTION=5757561]_keesj[/MENTION] is checking in every now and then while away. When I hear from him, we'll give an outlook for sending out the update for the = SMS bug fix, as well as any other news.

Hope everyone is having a relaxing summer. For current Fairphone buyers, we hope to put out a production update next week (16 July) about what's happening in the factory and delivery outlook.

Cheers,

Joe

FP Community Manager
[Fairphone 1] moddux:
Hello,

it seams I'm a messenger for bad news. The german news-site heise writes once more about a bug in Android < 4.4.4. They write about a bug that allows each App to make calls without asking for permissions first. (heise.de/newsticker/meldung/Android-laesst-Apps-ohne-Rechte-telefonieren-2251912.html) They state that it is possible for Apps to install a call-redirection and the possibility to destroy the sim-card.

I hope this can be addressed as soon as possible, but first enjoy your vacations.
[Fairphone 1] chrmhoffmann:
Still waiting for kernel sources that work. Sigh. The decision to make a sustainable phone with mediatek has been an utter beginner's mistake by Fairphone. Especially since they are now selling a second batch with the same "mistake".

I don't even know why Fairphone is still posting stuff to xda. They are not supporting the developer community at all. It's just another "feedback on bugs" forum.

Chris
[Fairphone 1] benkxda:
I hear you and I think you're right with your first part. Obviously you and of course many other Fairphone customers are very disappointed. But cutting off the communication is not the right way.

I hope Fairphone will learn a lot from the discussions in here and on other developer platforms, as their dreams did not came true: Firefox OS, Ubuntu OS will probably never come to those Mediatek Fairphones. We don't even really get Android - just one single taste of it.
[Fairphone 1] _keesj:
Hello Chris,

Having the kernel sources is of course only part of the problem. I did not spend time on replacing the kernel on a device but it indeed might be a little harder to replace the main kernel because there are more dependencies (loadable kernel modules) and things (ramdisks etc) that need to take place when booting. I am currently not even sure in what partition we can find the kernel. I agree that the choice for a non Open Source friendly provider (mediatek) has been a bad one. Other companies, google included, made such "wrong" decisions.

Please keep in mind that Fairphone is a project. The way I look at it is the following: The second batch is there to fulfill a need (Open Source was apparently not the primary one) and provide some sustainability to the company. Do not buy this phone if you want to own a phone where you have access to the source and can install "custom roms". While I do not give up it is not a risk a paying customer needs to take. Fixing this mistake is high on the agenda and I, as software developer, would never have joined a company with no "source code" without the conviction that we can fix this issue, possibly with different hardware, in the future.

It would be nice to "fix" the problem for Fairphone owners who bought the device expecting it to be open source any suggestions?

Open source still will not be the primary goals of the project and other things on the software side like security and privacy might have an impact on how hackable the phones will be. I personally want a "N900" like developer friendly phone with proper security.

I would like to know what you expect in terms of this xda community(I am quite new to xda and forums in general). How does one support the developer's community?
[Fairphone 1] _keesj:
English version:

http://www.goodgearguide.com.au/article/549394/android_bug_lets_apps_make_rogue_phone_calls/
[Fairphone 1] chrmhoffmann:
Hi,

thanks for your response. I appreciate the fairphone project as such and their primary goals. That's why I bought one.

Just release the proper kernel sources and write a few lines doc how to build them properly. That's not asked too much: this is in fact an obligation by GPL. Otherwise you could just release any sources and claim that they are "the" sources. Again: I am not saying that fairphone violate GPL or anything else. I just think that they should do an effort in that direction. Maybe I just made a building mistake and the stuff works fine?

Chris

EDIT: And concerning your question how else can you help devs:

- Serial Console: Is there a way to enable serial console on the fairphone? This is extremly helpful when people will try to write/upgrade/debug the kernel and it doesn't boot up.

- Bootloader: is it possible to add fastboot? There are MTK 6589 devices that have fastboot (e.g. wiko stairway). That's __very__ handy.
[Fairphone 1] huedrant:
Hi,

just to add to the discussion, as to me as a non-developer, it looked promising: did you ever have a look at this thread: http://xdaforums.com/showthread.php?t=2636257 ?

By the way, to me as a batch 2-buyer, this topic around mtk and not having a community-supportable device in the future scares me quite a bit, I would have waited for the third batch if I had known about this issue and to not buy it. (Just to add another argument)
[Fairphone 1] _keesj:
It is good to remember *I* don't have the sources!

About serial console. The first thing to do is to enable the Linux framebuffer and output the serial to the framebufffer. In my experience this will be enough to discover what is wrong with your kernel.

Having fastboot would be nice as it would allow to upgrade without special MTK tools. Fastboot normally depends on a non u-boot bootloader as the u-boot support for fastboot is bad. I have looked at the partitioning scheme used on our devices and this is all but trivial. There are hidden partitions and non standard partitioning schemes (the ebr1 and ebr2) and special checks using the scatter files so I currently do no assume it is easy to just "enable" fastboot but I will ask. Using DFU might also be an option. I would like a recovery with a Linux fastboot gadget driver. Is there such a thing?
[Fairphone 1] MoreThanADev:
Maybe I got you wrong but, are you saying that it will be hard to get both the source, and a privacy-friendly/secure device ?

I would say it work the other way around. If the source get delivered, the port of some secure & privacy friendly OS like replicant will be much more easier.

(actually seeing how mediateck is reluctante to deliver the sources, I am starting to have some thought on what they want to hide, and how unprivacy-friendly and unsecure these sources are)

Yeah Fairphone was also manipulative for it's first batch

-> I bought a smartphone for some price but in the shope, once i hade made my choice, there was some weird price increase to pay for taxes and delivery. Since I hade no way to select other options a fairer sailer would have displayed the real price right from the start. (Hopefully i ordered no charger, earplugs nor did I use paypall --'

-> Even for fairphone 1, they kept advertising it as an "if you can't open, you don't own it" phone even thought it was alread very clearly said in this thread that the open source support would be very bad beause of mediatek

(btw you can probably cancel your order if that's what you want)
[Fairphone 1] _keesj:
What I mean is that we might make it a little harder to install custom mods on the phone e.g. requiring a "oem unlock" like mechanism to prevent malicious actions and this can sometimes be seen as developer unfriendly.

That is certainly an option and as I said depending on the purpose of the phone this might be the best thing to do. I would hope we can find better solutions, dropping the Fair for the Open is also not very nice. Many buyers of the phone are really happy with the phone and do not want to modify a single thing. My *guess* is that there is a market for second hand or refurbished Fairphones and that their value will not decrease as fast as for normal phones.
[Fairphone 1] _keesj:
The code for fastboot (LK little kernel) is already on the phone but entering fastboot is phone specific. Other phones use the camera button but we don't have that either.
[Fairphone 1] haiag:
A few weeks are somehow over.

Any news or updates about the next update [MENTION=2438866]keesj[/MENTION] ?
[Fairphone 1] _keesj:
Hello,

Yes things are looking good. We will to push an update next week. This will include a few requests from here:

-VOIP calling

-The GPS/SMS = bugfix

-A fix for CVE-2014-0224 OpenSSL

-Lower logcat output and possibly the bluetooth

-GPS fixes (using a different ntp server) and I still hope a fixed EPO downloader.

Currently trying to push the bluetooth fix.

Last week we also finalized the partition upgrader. But before we can push that one we need to push an updated updater that warns users to create a backup.
[Fairphone 1] haiag:
So there won't be a built-in backup function?

The user is responsible by himself?

Will the future updates work without partition uprgader?
[Fairphone 1] JYPDWhite:
[MENTION=5757561]_keesj[/MENTION]

Are you aware of the sms send bug? I mean that it is no possible to send a bulk sms to about 30 recipients. Because of the security system which is blocking this function.
[Fairphone 1] joemier:
Package 3: Linux Kernel Source Code

We've uploaded Package 3 of the Fairphone OS Source Code to our Software Downloads section.

Here's the direct download link of the package (170 MB; .gz file).

Please give us your experiences and feedback here!

Cheers,

Joe

FP Community Manager
[Fairphone 1] _tmp:
I fixed this by changing line 382 of kernel/Makefile to

MTK_INC += -I$(MTK_ROOT_CUSTOM)/$(TARGET_PRODUCT)/common

MTK_PROJECT is not defined at this point.

Concerning the ddp_drv.c I changed a few includes from <...> to "..." as the corresponding headers are in the same folder.

I committed my changes to github which is forked from [MENTION=5757561]_keesj[/MENTION] . My username on github is benlorenz (as I cannot post links), there you should find the alps-fairphone repository.

Thanks for the updated source code.

As far as I can see, the sourcecode is almost complete. Compiling succeeds (after a few minor changes) but linking the kernel does not succeed as the custom settings for two sensors and the display config is still missing. I think the following files are missing:

mediatek/custom/ahong89_wet_jb2/kernel/alsps/stk3171/cust_alsps.c
mediatek/custom/ahong89_wet_jb2/kernel/accelerometer/bma250/cust_acc.c
mediatek/custom/common/kernel/lcm/nt35516_qhd_dsi_cmd/nt35516_qhd_dsi_cmd.c

There are various similar displays but none with this name as set in ProjectConfig.mk

The errors I get at the end of the build process are:

kernel/mediatek/custom/out/ahong89_wet_jb2/kernel/accelerometer/bma250.c:1701: undefined reference to `get_cust_acc_hw'
kernel/mediatek/custom/out/ahong89_wet_jb2/kernel/alsps/stk3171.c:2202: undefined reference to `get_cust_alsps_hw_stk'
mediatek/custom/out/ahong89_wet_jb2/kernel/built-in.o: In function `.LANCHOR1': cust_vibrator.c:(.data+0x1798): undefined reference to `nt35516_qhd_dsi_cmd_lcm_drv'
[Fairphone 1] fredflegel:
Great! I did the almost the same and got the same results.

That is more practical than my solution.

I did the same with the following commands (for documentation):

sed -i 's/<ddp_dpfd.h>/"ddp_dpfd.h"/g' mediatek/platform/mt6589/kernel/drivers/dispsys/ddp_drv.c
sed -i 's/<ddp_dpfd.h>/"ddp_dpfd.h"/g' mediatek/platform/mt6589/kernel/drivers/dispsys/ddp_debug.c
sed -i 's/<ddp_drv.h>/"ddp_drv.h"/g' mediatek/platform/mt6589/kernel/drivers/dispsys/ddp_dpfd.c
sed -i 's/<ddp_dpfd.h>/"ddp_dpfd.h"/g' ../mediatek/platform/mt6589/kernel/drivers/dispsys/ddp_dpfd.c
sed -i 's/<disp_drv_platform.h>/"disp_drv_platform.h"/g' ../mediatek/platform/mt6589/kernel/drivers/video/lcd_drv.c

Git hub i

Thanks a lot, great idea! I did not look at github.

I get the same and then some more:

mediatek/custom/out/ahong89_wet_jb2/kernel/built-in.o: In function `bma250_remove':
lps/kernel/mediatek/custom/out/ahong89_wet_jb2/kernel/accelerometer/bma250.c:1701: undefined reference to `get_cust_acc_hw'
mediatek/custom/out/ahong89_wet_jb2/kernel/built-in.o: In function `bma250_probe':
alps/kernel/mediatek/custom/out/ahong89_wet_jb2/kernel/accelerometer/bma250.c:1686: undefined reference to `get_cust_acc_hw'
mediatek/custom/out/ahong89_wet_jb2/kernel/built-in.o: In function `bma250_i2c_probe':
alps/kernel/mediatek/custom/out/ahong89_wet_jb2/kernel/accelerometer/bma250.c:1575: undefined reference to `get_cust_acc_hw'
mediatek/custom/out/ahong89_wet_jb2/kernel/built-in.o: In function `stk3171_remove':
alps/kernel/mediatek/custom/out/ahong89_wet_jb2/kernel/alsps/stk3171.c:2202: undefined reference to `get_cust_alsps_hw_stk'
mediatek/custom/out/ahong89_wet_jb2/kernel/built-in.o: In function `stk3171_probe':
alps/kernel/mediatek/custom/out/ahong89_wet_jb2/kernel/alsps/stk3171.c:2184: undefined reference to `get_cust_alsps_hw_stk'
mediatek/custom/out/ahong89_wet_jb2/kernel/built-in.o: In function `stk3171_i2c_probe':
alps/kernel/mediatek/custom/out/ahong89_wet_jb2/kernel/alsps/stk3171.c:2026: undefined reference to `get_cust_alsps_hw_stk'
mediatek/custom/out/ahong89_wet_jb2/kernel/built-in.o: In function `bma250_init':
alps/kernel/mediatek/custom/out/ahong89_wet_jb2/kernel/accelerometer/bma250.c:1722: undefined reference to `get_cust_acc_hw'
mediatek/custom/out/ahong89_wet_jb2/kernel/built-in.o: In function `stk3171_init':
alps/kernel/mediatek/custom/out/ahong89_wet_jb2/kernel/alsps/stk3171.c:2221: undefined reference to `get_cust_alsps_hw_stk'
mediatek/custom/out/ahong89_wet_jb2/kernel/built-in.o: In function `.LANCHOR1':
cust_vibrator.c:(.data+0x1794): undefined reference to `nt35516_qhd_dsi_cmd_lcm_drv'
[Fairphone 1] tobwes:
I managed to compile completely. However, I had to tweak a little bit and since I don't have much (or any, so to say) experience, I would be happy if someone could check what I did. I don't have a phone to test it, anyway.

Oh, and since this is the technical details thread, I'm going to post in the kernel sources thread, so that this thread can be used by others for different questions.

P.s.: It'll take a while until I can publish my solution. First I'm gonna find out where I can upload my changes. What I've done basically is to get the missing files from other repositories, eg. [1] and [2] which obviously use the MTK6589 chipset as well and then handle the remaining errors manually.
[Fairphone 1] fredflegel:
May be the best place would be github? You can clone the repository of [MENTION=5959593]_tmp[/MENTION].

Or you simply post your changens in thread here, so we can see what needs to be done. Maybe Fairphone is already working to get this lasts bits together. I would still be interested to know if they build the kernel themselves because they obviously have not tested this package...
[Fairphone 1] tobwes:
See the other thread "Mediatek driver sourcecode". There's more info.
[Fairphone 1] _keesj:
Hello,

What this means is that if you want to upgrade the partition layout you will need to backup/restore.

---------- Post added at 08:53 AM ---------- Previous post was at 08:38 AM ----------

We currently get full builds.
[Fairphone 1] MarcoToo:
How about the files you use to build Android? Can you provide them? I really want to start trying to modify it and port other ROMs, even if they are freaking buggy. Disgusting sources with binary blobs will be just fine, just give us a point to start.
[Fairphone 1] fredflegel:
Thank you!
[Fairphone 1] Fisher_AZ:
First off, I'm glad to see [MENTION=5757561]_keesj[/MENTION] jumping right in on this board with some good results already. Also, very good to observe that several developers have been lying "dormant" (so to speak) for long but are still interested to work with whatever raw source material appears to come to the surface recently. I have no Android developing experience myself, so all I can offer is kudos and good luck to all those participating in that endeavor.

Just to be clear on a few things:

1. I suppose this means that the existing /data partition will be wiped compelety in the process ?

2. Is it documented somewhere what the built-in Fairphone [or MediaTek] backup app precisely backs up (and what it doesn't) ? i.e. contacts ? text messages ? call log ? pictures ? other files ? Android settings ?

Useful as they may be, a part of these are usually backed up in the cloud already (contacts, calendar, pictures). The difficult part is backing up and restoring settings for user-added apps. I am familiar with apps like Titanium and Helium and while useful, they still require of lot of tedious work and are not always 100% effective. I suppose it is too naive to hope for some solution that magically "zips" all app data on the existing /data partition, then (after the OTA update) "unzips" it on the re-partitioned /data partition. Or is such magic possible still ? I had to ask ...

3. The way you formulate it above ("want to upgrade") makes it seem like the partition layout upgrade is optional. Is it optional in the sense that the partition upgrade can be dismissed while still receiving all other software upgrades ? This seemed to be contradicted by an earlier comment implying that you plan to work with a uniform software image for both FP1 and FP1U2, requiring both to have the same partition layout.

Can you shed some light on this ?