I see it on the home screen, opening a icon folder and close it. But it’s only slightly different. It’s the only way to get noticed.
Tried it just now on /e/ and I can’t say I notice a difference between charging/not charging when opening/closing a home screen icon folder (on some launcher I installed, not the default bliss launcher).
Well, glad to see that it seems to be working well, sorry that you have to recompile the ROM again . I’ll also try it when I’ll receive my FP3 (but for that I will have to wait…).
Thank you !
No problem. I build it quite often at the moment
Yes, it’s really very slightly. But if you notice once you’ll see. I always try with the installed Apps overview when you swipe up in the launcher. I don’t know the exact name of that screen. Maybe you mean the same with icon folder. If I scroll there I clearly notice the difference.
Yes, that would be really interesting. I already tried some properties from the stock firmware. But maybe the issue exists there as well. Maybe someone can give a try.
I’m on stock (120) and can’t see any difference, either with Nova nor with the default launcher
I have fixed Microphone in VOIP calls
Hi I managed to get LOS 16.0 on my FP3 up and running thanks for that !
I’m struggling with openGapps, I can’t get my LOS to load once I flashed them.
As you mentionned I may be linked to AVB.
Audio hal has been open-sourced finally https://gitlab.e.foundation/e/os/android_hardware_qcom_audio/-/commits/v1-pie-caf-8996
Nice to hear. Unfortunately I didn’t had much time this week to work on it. Will try it next week.
Maybe disabling verity helps as also used here:
Please feel free to update description here when you find out how to install it.
I have been thinking of getting a FP3 since its release but have been holding of as my current phone was still in a working condition. It has now detoriated to the point of being a ticking bomb before it shows its last pixels.
One of the reasons for waiting this long for getting the FP3 is also because I am interested in running LOS instead of stock android. I have been following the forum and this post for a the past two months to check on the development of LOS for the FP3.
To get to my question. I wonder how stable the last release is for everyday use? Would it be fine to get a FP3 and expect LOS to run without “everyday problems”?
I am also working in IT (but never with android development) and wonder if there is something that I can do to help in the development.
I’ve just flashed the version with microG yesterday and setup everything to suit my needs and I’ve not experienced any crash or instability yet. So I’d safely say the last release is stable enough for everyday use.
I’ve used the stock Android version with Google apps provided by Fairphone for a few months and I’d state this lineageos release is as usable as the latter. It also fixed some issues I had with the stock version, especially the minimum brightness being to high to let me use the phone in the dark.
To put everything into perspective, it’s the first ROM I have ever flashed and I found the process really straightforward.
So big thanks to the devs for their amazing work.
Thanks for the answer. I just did that, I get the same exact result
- I wipe all data + system
- I install both LineageOS + openGapps
- On reboot I get the message “Android system not found : format all data ?”
-> If I say yes and reboot, it works, but I don’t have the Gapps
-> If I say yes, reboot to recovery, sideload install the Gapps again, I get a black screen on reboot (after the usual warning screens)
I’ll keep you in touch if I go further.
That sounds very promising! I will give it a try then when I get my FP3
Quick update on the Gapps : I learned that I need to do the disable-verity commande after installing the OS.
So I get Lineage to boot with Gapps, but I’m stuck with the message “There Was A Problem Communicating With Google Servers”
I tried several common fixes but no luck so far. I keep you posted.
I just got a FP3 and tried installing this LineageOS image on it. The first steps – unlocking the bootloader, booting (then later installing) TWRP – worked fine, but after installing LOS (both using sideload and push + install from TWRP) it wouldn’t boot, instead giving me this broken-English error message:
Can't load Android system. You continue to get this message, factory data reset and erase a device.
I tried wiping data partitions / internal storage / basically everything TWRP offered me, but it wouldn’t help.
While I was writing this, I actually got it to work though! The recovery mode that presented the aforementioned ugly error message to me also had an option for "factory-reset"ting the phone, and once I selected that, it actually started LOS!
I’d be glad if this issue could be added to a troubleshooting section somewhere so other people don’t get stuck with this issue
Thank you for your great work!
I have problems with compiling LOS 16 for FP3.
2fsdroid -p /path/android/lineage/out/target/product/FP3/system -S /path/android/lineage/out/target/product/FP3/obj/ETC/file_contexts.bin_intermediates/file_contexts.bin -f /path/android/lineage/out/target/product/FP3/product -a /product /path/android/lineage/out/target/product/FP3/product.img
__populate_fs: Could not allocate block in ext2 filesystem while writing file “webview.apk”
e2fsdroid: Could not allocate block in ext2 filesystem while populating file system
After that the build aborts. I started building via “brunch FP3 eng” after setting some variables from my previous LOS 14.1 builds (JACK_VM doesn’t seem to be recognized)
export USE_CCACHE=1 && ccache -M 80G && export ANDROID_JACK_VM_ARGS="-Dfile.encoding=UTF-8 -XX:+TieredCompilation -Xmx12G" && LC_ALL=C
I’m not a software engineer, but very interested in LOS development for FP3. Do you have any idea why my build fails?
yes, this is a known issue, inflicted upon us by other LineageOS developers.
You will find a workaround in the issue discussion.
@Max_S: perhaps we should override this setting inside our device tree somehow?
Thanks for your quick answer! It worked for me. Just to pin it here: I added the following lines to my roomservice.xml
<remove-project name="LineageOS/android_external_chromium-webview"/> <project path="external/chromium-webview" name="LineageOS/android_external_chromium-webview" groups="pdk" revision="4a9980d94c632c731e8e8bbcea43467878e4bebd" clone-depth="1" />
Now repo sync hangs at
Fetching projects: 99% (711/712) platform/prebuilts/checkcolor even if i delete the hole lineage folder and re-init/re-sync everything from blank folder.
Is that also a known issue or do you know whats going wrong? I couldn’t find a solution for that. I’m using Ubuntu 20.04
repo sync command can take a very long time and seems to hang if network connections to github fail. If you want to be sure that something is still going on, use
top or the Ubuntu task manager to examine the activity.