Hi @keesj
As the update to FP GMS is out now, any news about
?
Thanks
Klaus
5 Likes
Yesterday on twitter they said that FP2 OSOS was “imminent”…
The policy of announcing a date for a release reminds me of little me when my mother would ask me when I would tidy up my room, though I didn’t exactly use the word “imminent”, I guess.
9 Likes
When in Star Trek a core breach was imminent, everyone ran as hell… 
I don’t understand what the matter is with not given any clearer information. I mean it wouldn’t have been more complicated to write something like:
Our Dev-Team is working hard to release the fposos version. We hope to manage a release this week but can’t be sure because of that nasty bug.
I mean, this is a very mature community, everyone would understand that such things happen in complex software development and appreciate the communication.
3 Likes
If Scotty was in charge of the OSOS…
“Scotty, how long does it take until we have the OSOS?”
“I need like 14 days”
“I can only give you a week”
“Ok, then I’ll finish it by tomorrow.”
2 Likes
it is still android 
Was the latest update 1.2.8 generated from the the same sources I wonder? I don’t see a lot of action in the official repo. Or do they support two repos and the official one is hidden? There shouldn’t be any difference between the two builds, except for the Google stuff, or?
$ repo sync && repo forall -c git log | grep "FP2-" | sort -n
Looks boring, but maybe I’m doing it wrong. The latest comments I can see in are from Jan 2016. Maybe there is another branch, but I’m not really that interested in the code anymore – if it is kept separated, there is no benefit.
I was always expecting that the “fixed” code would be “synced” with the published repo. Or is it hosted somewhere under code.fairphone.com/gerrit?
Update: Can someone who knows more about git, gerrit & repo verify this? @jftr?
1 Like
Can you explain what you are trying to achieve with this command? I don’t quite get the intention.
What I’ve gathered from posts by Fairphone staff is that the public repository is up-to-date with releases (sorry, I currently can’t find the source). What exactly are you missing anyway?
The bugs fixed in the 1.2.8 release. The command just sync’es the repo and gets all the git logs/commits and checks them for a “FP2-” entry, this is how the bugs are tracked (I think). You will get a list like this:
FP2-1009: Dual SIM improvements
FP2-1023:com.android.settings' ANR when connect Wifi
FP2-1056:[ST_2][Gallery]Video doesn't stop playing when ...
FP2-1121:The music volume gets lower than normal ...
FP2-1177: Contact name can not display on calling screen
FP2-1185: Can't start recording in FM Radio
FP2-1196: [Monkey] 'com.android.gallery3d' crash
FP2-1197: fix a crash issue in packageinstaller
FP2-1197: [ST_2][Monkey] 'com.android.packageinstaller' crash
FP2-1200:make device visible over bluetooth. scan device
FP2-1211:WIFI Direct connect failed mostly
All the bug fixes from the 1.2.8 release. All the newest commits I can see here are from Jan 2016.
@keesj compiling for over a week now? And the release was imminent… What is the reason for the delay? 
Hi all,
I’m using Fairphone Open Source OS on my FP2 in order to stay away from GAPPS. The updater app only offers me the old 1.1.7 version (which is probably intended by the developers), so I suppose I need to install the 1.2.8 update manually.
However, the patches of this update seem not to be included in FP-OSOS (I tried repo sync but it obviously didn’t pull any source code changes at all), so I’d have to flash the image provided at the Fairphone-OS download page, I assume. But that would install GAPPS as well on my phone, wouldn’t it?
So, how can I get the update now without accidentally installing the Google Services?
1 Like
I’ve moved your post here, as your question actually touches a lot on the roadmap for the open source version of Fairphone OS. As you can read from the posts above, it’s a bit unclear what the current status is, but there should be a pre-compiled release of FPOSOS soon.
That’s probably because many of the changes are in the binary blobs. They won’t show up in version control.
I thought so too, that’s why I think changelogs for the blobs would be helpful. And shouldn’t the Android monthly patches show up?
I did a diff (it’s complicated, because java applications are used as well, there is a lot of “other” software in there.) for fp2-sibon-2.0.0-blobs.tgz and fp2-sibon-2.0.1-blobs.tgz. Nothing has changed. I’m too lazy to compare fp2-sibon-2.0.3-blobs.tgz(?), because all I could possibly find out is that now “something has changed”. And I’m a bit tired of playing Sherlock Holmes … it’s not making things better.
I guess all one can do is download the fp2-sibon-2.0.3-blobs.tgz and compile again (There are things getting linked …).
1 Like
I have another question:
What makes you think only changes starting with “FP2” are relevant?
I don’t have a clue how Fairphone handles commit messages. However I know that a very common model is to start each commit with the bug ID in the bug tracker to mark that bug as resolved. Of course this only is the case if the code is actually submitted as a single commit and written by Fairphone staff.
But there are other scenarios in which stuff gets fixed but the bug ID is not the first element in the commit message. Maybe bug fixes are merged from another branch (then the message likely starts with “Merge”) or commits from elsewhere are cherry-picked (then the message might be totally different).
Long story short: I’d consider all changes as part of the release and not only those which start with “FP2-”.
Edit: For clarification, you’d have to ask Fairphone staff managing the repository and/or writing code for Fairphone 2. They’ll know.
I have no clue, I just looked for the usual suspects (CVE, FPII, FP2) that normally contain “new” stuff.
You are right that all changes are part of a new release. All I want to know is: Is the code that is currently offered in the repo (the stuff you get with repo sync) code from the 1.2.8 release? I don’t think so, but I don’t know for sure, so I ask the community.
I stoppend asking the Fairphone staff, they are too busy. That’s why we have a repo so we don’t need them if they are busy doing their main job (making new builds for all FP users). The code here is just a very cool extra.
$ repo forall -c git log | grep -i 2016
Date: Tue Jan 5 17:14:27 2016 +0800
Date: Mon Jan 18 18:26:40 2016 +0000
Date: Fri Jan 15 16:02:56 2016 +0800
Date: Thu Jan 7 11:20:46 2016 +0800
commit cb137fc11dcf87be7592016eeab44d924d6227b2
Date: Mon Jan 11 16:06:19 2016 +0000
Date: Mon Jan 11 16:15:55 2016 +0000
Date: Wed Jan 6 17:20:05 2016 +0800
Date: Tue Jan 19 09:56:34 2016 +0800
Date: Wed Jan 13 17:48:02 2016 +0800
Date: Tue Jan 12 15:11:43 2016 +0800
Date: Mon Jan 11 14:36:18 2016 +0800
Date: Mon Feb 29 17:30:22 2016 +0100
Date: Tue Jan 5 15:39:26 2016 +0800
Date: Mon Jan 18 14:22:51 2016 +0000
Date: Tue Jan 12 11:30:16 2016 +0800
Date: Wed Jan 13 18:08:51 2016 +0800
Date: Wed Jan 6 18:33:28 2016 +0800
Date: Thu Jan 14 15:16:34 2016 +0800
Date: Mon Jan 11 14:34:25 2016 +0800
Update: TLDR: Is there a way to get the “new” code from the repo that was used in the new build?
I spend time searching around. I think the new branch could be fp2-sibon-2.0.2. I will sync and report back.
This approach is also flawed because commit times are kept even if a commit is cherry picked from another branch. That means, is someone (e.g. at Google) has committed something last year but the Fairphone team only took over that code this year, it would still show the old date.
I don’t know of a good way either. But the tree view of git is already sorted by time of addition of a commit (to this particular branch). That means you can just run repo forall -c git log --oneline (or similar) and see what happened recently for each project separately.
There also seems to be a subcommand that gives a changelog for all projects together. I haven’t tried it yet.
In any case, marking a particular point in time before syncing is possible with tags. For instance:
$ repo forall -c git tag REMEMBER_THIS_COMMIT
Another way of watching new commits is by partially syncing with repo sync -n. That fetches all commits but leaves HEAD (your working directory) at the current state.
These are but building blocks and I have not found a satisfactory way of getting a definite changelog.
Thanks. I will sync -n and play around with the repo extension. I think by now git can also handle multiple git repos itself.
Anyway, there has to be some working branches/tags or trunks to get code for the current image. It cannot be that hard. All the fixed CVEs should show up in there.
AAaaaaaand another week passed by without any information… Or are there any news about the fposos?? 
