However, I just did my moving back to Germany and did not have loads of time up to now to look into it and will go to sleep now to be able to understand all instructions and not make too many silly mistakes
so you are saying that what Tom sees is the OS we get, when we compile
it as described above? Somehow I did not read anything about this, so
thanks for this valuable info.
So, can I assume that the system itself is the same, only Gapps and
other apps you mentioned are missing? Will I be able to use all hardware
(like e.g. the FM radio) with this self compiled version of the OS?
@Michiel: is there really no way to flash the correct system ourselves
and do the affected people really need to send the phones back? Well, a
little bit of Linux experience might be necessary to do it. But can’t
Thanks for the info. I’m not sure if I understood you completely. Could you elaborate on following questions please:
When do you believe you will be able to release that version (days/weeks/months)? (I know, a nasty question, just a rough estimation )
What belongs to the “Fairphone specific apps” you talk about? Will Gapps and Google Services be included in the version you release or not?
Background: I’d like to have a google free phone (e.g. get rid on the red block shown on in the diagram on code.fairphone.com), I don’t mind about Fairphone specific apps e.g. like special launcher or “Peace of mind” app
With what would I end up following the build instructions on code.fairphone.com? Does any google service specific stuff (the “red box”) installed by that?
So is there a difference in following that build instructions and the version you will release?
@paulakreuzer, that’s how I would have imagined as well. But please reread @keesj’s post: [quote="keesj]
On FP1 the pure AOSP release caused quite a few calls to Customer support for people “loosing” their google services. The plan is to keep the Fairphone specific apps in the build e.g. this version will not be a pure AOSP Android release
That’s what got me confused. If people complained that their Google stuff was missing after installing the img and Fairphone wants to prevent the complaining, they’ll include them. Right? I mean, fair enough. Just not what I personally would want.
Thanks for the clarification @paulakreuzer, so if I got it right the list expanded to FP specific Apps would look like that:
Fairphone OS w/o Google Apps, with FP specific apps - preinstalled
Fairphone OS with Google Apps, with FP specific apps - by installing Google Apps through the Updater App
Stock Android w/o Google Apps, w/o FP specific apps - also installed through the Updater App
FP OS with GAPPS, with FP specific apps - preinstalled
FP OS w/o GAPPS, with FP specific apps - how? we’ll know more soon I hope (speculation by @sjjh (that’s me): following the build instructions on code.fairphone.com will give you that-- anybody here to verify/falsify?)
Stock Android, w/o FP specific apps - not announced yet, maybe just as a community build?
With regards to having a google free version: Before Christmas we
released the source code, blobs and instructions that allow to build
such a google services free version on http://code.fairphone.com/2
. The next step is to release a version that can be installed by end
users. This does require us to do some additional quality assurance and
make sure nobody accidentally installs the GMS free version. On FP1 the
pure AOSP release caused quite a few calls to Customer support for
people “loosing” their google services. The plan is to keep the
Fairphone specific apps in the build e.g. this version will not be a
pure AOSP Android release (this exercise is left to the reader).
Maybe I am a bit naive but if you already released the code to compile AOSP Android, I suppose you already built such an image. Wouldn’t it be possible to provide this img-file to buyers of the FP2, so that non-dev people who would just like to get rid of GMS etc could do so until the GMS-free FP version is available?
Since it seems that compiling the code - + enabling root - is not as straight-forward even for devs judging by the entries in different threads on the forum as compiling fairphone open source and FP2 root or not root? how?, I suppose other people like me would appreciate it.
Concerning people accidentally installing the GMS-free version: Wouldn’t it be enough to call it “GMS-free (NO google services) FP OS”?
I’ve tried following this post (and all posts regarding a rooted FP2) and cannot quite follow. I have only ever owned iPhones (pleeease no comments… I finally got there myself and bought a FP2) so I am new to the GAPPS and Androids systems.
As soon as FP release the root-Infos - I will have total access to my phone an can install apps w/o GAPPs. But will GAPPS still be possible - just in case I don’t figure out how to install anything w/o GAPPS? Or will the phone never ever have GAPPS again?
I prefer the “Nano” package w/o the Calendar Sync (you can taylor each package to your needs) as I rely on GCM for Threema, K9 and Signal. Hope for a reliable open source push service provider in the future to go completely Google-free…
Maybe I am a bit naive but if you already released the code to compile
AOSP Android, I suppose you already built such an image. Wouldn’t it be
possible to provide this img-file to buyers of the FP2, so that non-dev
people who would just like to get rid of GMS etc could do so until the
GMS-free FP version is available?
you can see that I have compiled the system. As it seems it is Gapps free. If there is anyone hosting an ftp or sftp server / cloud service etc… I could upload the img files (about 450MB). I am just not quite sure if I should recommend this. The compiler said “Complilation successfull”, but if anything went wrong unseen… So, a prior backup is mandatory!