Hi the original fairphone os nougat 7.1.2 has the exact same issue. I have two identical fp2 one with eos and the other with unchanged fos they both have very often random reboot issues at shutdown. Updates installs clearing cache removing some apps sometimes solves temporarily the problem. I still couldn’t figure out what causes and cures the issue.
Regards everyone
Louis
7.1.2 is the Android version. Which Fairphone OS version are you referring to? The current version FPOS 19.05.3?
It is indeed the fos build 19.05.3.
I forgot to mention it.
Regards
1 Like
Have you tried unofficial /e/ oreo or pie builds if they solve your issue?
1 Like
@ff2u Would an oreo/pie build of e work on a nougat Android? Maybe i missed something
Related question : is an Android nougat upgradable (or downgradable) toward another version?
I work hard on the Android question since i started supporting e but i feel like a beginner still…
Anyway could this reboot thing be a hardware issue of the fp2?
Regards
Louis
If your data partition is not encrypted then I assume updating from nougat to oreo or pie will work without wiping all data (more details).
But keep in mind that (currently) the only official (including OTA updates) /e/ versión for FP2 is the nougat version.
Yes and no.
Yes: it only happens when the “new” camera model is installed in the FP2. It does not happen with the original model. So it’s related to HW.
No: As it’s a driver issue it can be (and was) solved via software fix. So it can be fixed via SW.
@Louis, @rhunault on Fairphone OS Nougat there is a fix from what I’ve been told here:
https://twitter.com/WeAreFairphone/status/1174291272468705281?s=20
Now we need it on /e/.
No idea why it hasn’t been done yet.
I think it’d be better to have a pie based official /e/ versión for FP2 than to backport the fix to nougat.
1 Like
Fine. I just requested it here:
2 Likes
https://gitlab.e.foundation/e/management/issues/418 has a discussion going on. Hopefully @rhunault is working on it.
Calling the /e/ community for help with the latest question on the Gitlab issue please.
Because I’m not sure the /e/ developpers have a clue. Probably the reason why we’re still waiting.
I’m still not sure that it’s worth to invest a lot of energy in fixing the nougat version, while the pie version is not affected and will hopefully be the official version in the near future…
1 Like
People are saying here that we could donate to Lineage or XDA forum to work on /e/ maintenance instead of /e/ developers. and this donation could be targetet to a specific model, like the FP2.
From what I read above, as we speak, neither /e/ nor Lineage have had their Nougat version fixed with the Fairphone patch for this issue. But Lineage developers have experience with it because it is fixed on their Oreo version.
@PNJ88_Beast, @archie, I see that the FP2 LineageOS maintainer is nicknamed ‘chrmhoffmann’. Should we contact him and how?
Hello @cedricoola, chrmhoffmann’s Developer Profile’ no contact address is given. But maybe you can get in touch via →Twitter?
No, that’s not what was said let me clarify things for you.
xda-developers.com is an independent forum where developers share their creations on the different devices available in the market. Among many other things this includes the LineageOS project. What I said is that the creator would typically publish their work and include information on how to contact, donate, contribute, etc.
My suggestion was to check out these forums for any active development outside of /e/ or LOS for your device; which by the way unfortunately there is not as of today. To be clear, since /e/ is based on LOS it makes sense to seek for active projects on both OS, hence again why I suggested. For instance I suggest you ask in their reddit channel: r/LineageOS.
So I’m not saying that we should bypass /e/'s developers since they are the ones maintaining this project. If you specifically want /e/ for your device contribute to them.
@PNJ88_Beast I would like to keep /e/ for my device, indead. I’m not willing to switch to Lineage or another project for now. I wouldn’t be on this forum if it were the case.
or do you mean that LineageOS developers could fix the no-shutdown issue in Nougat Version for FP2 LineageOS build, so that it could then be reflected in /e/ by /e/ developers? I don’t know if LineageOs developers would do that, because the current Lineage build of the FP2 is no longer Nougat so they would have no interest in fixing their Nougat version, unlike /e/.
1 Like
Like LineageOS and LineageOS-for-mircoG should /e/ very quickly put aside the maintenance of e-0.7-nougat and concentrate its manpower on /e/ OS 9-Pie.
The fact is that G°°gle no longer provides official security updates for Android 7.1.1 / 7.1.2 Nougat. The special maintenance of security updates from Android-8-and-9-versions in e-0.7-n- OS ROMs is like a time-consuming handicrafts.
All authoritative customROM developers and helping hands should be considered with donations./e/ anyway, but also Lineage, microG and TeamWin - TWRP. A German proverb says:
Nothing in life is free, only death - and that costs life.
I think you’re answering your own first question.
I can’t imagine that chrmhoffmann will invest time in a fix for the LineageOS Nougat build as he’s currently already working on an LineagOS 17 (Android 10) build for the FP2…
2 Likes
Well, you’re missing a small point here: Fairphone (the company) is supporting the FP2 and they are providing patches and updates on both Fairphone OS (the proprietary one, initially shipped with the phone) and Fairphone Open OS (their open source, free from google OS). They are still on nougat and are still providing support for it. Security patches from google and driver patches if needed. This annoying bug is fixed on the Android 7 version (open source) provided by Fairphone. So it’s not /e/ or Lineage developers who keep Android up to date on the Fairphone,the Fairphone developers are doing it. But /e/ developers need to backport the patch.
2 Likes