@lklaus Possibly the wake lock problem that should be closed next week. With me about 1-2 seconds delay.
updated to official updated, with microG and patched. so far so good. i will check how is battery working and come back with info
I installed LineageOS last night because I had the option to go back if I prefer (with a backup).
It works very well!
Not sure yet on the battery usage but its also partly on me.
I had some issues with the Privacy Guard. Although it is a nice feature I had multiple applications spamming for permission even though I already gave permission. Couldn’t exit the dialogues without keeping clicking.
Some issues I stumbled upon. Not sure where to report.
- Auto-rotate works in apps (all?), but not Android itself.
- Unable to disable either 2,4 GHz or 5 GHz WiFi (possible in FPOS not possible in LOS?).
- When changing brightness from the drop-down menu there is a one line artifact of whatever app is in the background. If that’s the settings screen, its likely a white line because the quick settings from the menu remain. If its an application like Firefox or WhatsApp, those quick toggles aren’t there so there is no artifact.
Stock launcher (Trebuchet)? … (I don’t use it, so I can’t check) …
Yep, default launcher indeed. That fixed it as well, cheers. Which launcher do you use?
SquareHome 2 (old Fairphone Open OS screenshot) … for wacky people like me who really like the Windows Mobile UI (but not on the desktop, of course) .
Seems like Google removed the setting … (coming from here) …
Can you give us a screenshot? I don’t see it.
First post here. I would like to join the club. Do I need to install the modem.zip like in the unofficial builds, if I’m coming from FPOOS? Or is this integrated in the LineageOS image somehow?
Thank you all for your effort. It is great that that our phone is now officially supported.
6 posts were split to a new topic: Artifact when changing brightness
Really great, the 14.1-20171024-NIGHTLY-FP2-LOS-version just landed smoothly at my FP2! Lots and lots of thanks to all you made it possible!!!
Edit: Meanwhile within two days I have had two spontaneous reboots at my phone, just laying around and untouched.
Yes, but if you are coming from a recent FP(O)OS, you already have the most recent modem. No need in that case. Later on you’ll need to manually flash modem updates.
Please use the bugtracker to log your issues. I am going to change the status of old issues that are maybe fixed back to retest-state a.k.a. ‘needs info’.
Ok, the battery seems to be quite the same than before. maybe a very little higher drain. but hardly noticeable.
What i have noticed is that the telephone is in general a bit slower. specially when unlocking the screen it takes a second or so to react and turn on the screen.
just wondering what of the steps will be needed for future updates?
su arm addon will be needed every time?
Tingle patch I guess it is needed.
Would it be better to install future releases with TWRP or would it run from the system itself?
TWRP is better of course, because when you are in TWRP anyway you might as well backup the OS state before the update with TWRP, which can not be a bad idea .
System can be updated just by using the updater (OTA). Su addon is a one-time thing and will surive the update. Same thing goes for Google Apps. Not sure about tingle, but I thing that is also a one time thing (@Roboe).
But as @AnotherElk says, backups are always good, and you’ll need to update modem when there is a update and / or a Google Apps updated zip from time to time doesn’t hurt either. (I only backup my system and update Gapps when a new modem is available e.g. once every other month).
Can I go from Android 6 to Lineage OS without losing my data and app installations?
Does it go out to a complete new installation, right?
Yep, you need to factory reset. If you backup your data, you won’t lose data. Titanium backup is good for apps + appdata. Don’t forget pictures and such are not in a backup and should be backuped manually. TWRP is only good if you want your whole system back.
Follow these instructions.
Tingle patches the
framework.jar file (or
framework-res.jar, excuse my memory right now) to inject the signature spoofing feature and permission. That system core library is overwritten on each system upgrade. For obvious reasons (core lib), it cannot be marked to survive OTAs, so the Tingle patch needs to be executed per-installation.