[ROM][DISCONTINUED] LineageOS 17.1 for F(x)tec Pro1 - F(x)tec Pro1 ROMs, Kernels, Recoveries, & Other De

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 10 (Q), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Base source code is available in the LineageOS Github repo. And if you would like to contribute to the project, please visit our Gerrit Code Review.
GPL compliance:
​
Device tree source code: LineageOS/android_device_fxtec_pro1
Kernel source code: LineageOS/android_kernel_fxtec_msm8998
Working:
Camera (and flashlight)
WiFi
NFC
Bluetooth
Telephony (Calls and Data), including VoLTE
Audio (Record and Playback)
Video Playback
Sensors
GPS
Encryption (FBE)
Built-in keyboard
Broken:
WiFi calling (?)
Compatibility:
Compatible with all F(x)tec Pro1 variants.​Builds are based off the F(x)tec's Android 9 firmware with proprietary blobs from 20200825231445 package.​
Downloads:
Official download links
Notice:
No custom kernels are supported in this thread. Only stock kernel and official builds will be supported. No bug reports if that's not the case.
Installation:
Refer to the official Wiki (link bellow)
Credits & collaborations:
Special thanks to tdm and mccreary for early bringup. All LineageOS team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!​
Device wiki:
Official wiki link

The first official build is up.

There seems to be an IMS issue, not registered. Can anyone else confirtm that?

shubell said:
There seems to be an IMS issue, not registered.
Click to expand...
Click to collapse
That's being worked on at the moment. I can't test IMS myself, so I have to rely on someone else to test. :fingers-crossed:

Wrong Layout for QWERTZ
Hi,
the Build version 17 is just amazing. It works realy great an the Phone is a looooot smoother now with lineage on it.
The only issue that i discovered is that the German Keyboardlayout is shifted by one Key to the left that means an "G" is an "F" and so on.
I also noticed that in Version 17 you dont have the ability to Upgrade your Lineage Version as there is no Option in the System Settings
I hope somebody can help me with the Keyboard Layout.
Regards
Bengele
---------- Post added at 01:42 PM ---------- Previous post was at 01:36 PM ----------
shubell said:
There seems to be an IMS issue, not registered. Can anyone else confirtm that?
Click to expand...
Click to collapse
Can you tell me what App you used to check that? Maybe i can provide some help for Troubleshooting

I found out about the FinQuertyApp it solved my problem for the qwertz layout.
If you need some help for testing purpose just ask

Bengelee said:
Can you tell me what App you used to check that? Maybe i can provide some help for Troubleshooting
Click to expand...
Click to collapse
type *#*#4636#*#* in the phone app
Bengelee said:
Hi,
the Build version 17 is just amazing. It works realy great an the Phone is a looooot smoother now with lineage on it.
Click to expand...
Click to collapse
It is noticeably smoother compared to 16

shubell said:
There seems to be an IMS issue, not registered. Can anyone else confirtm that?
Click to expand...
Click to collapse
It seems that i cant trigger that error for me everything looks normal. The only diffrence that i noticed is that LTE/TDSCDMA as Networktype and Telekom Germany as a Provider

Bengelee said:
I found out about the FinQuertyApp it solved my problem for the qwertz layout.
If you need some help for testing purpose just ask
Click to expand...
Click to collapse
Can you explain your problem in more detail? We have an option to change keyboard layout.

Bengelee said:
The only issue that i discovered is that the German Keyboardlayout is shifted by one Key to the left that means an "G" is an "F" and so on.
Click to expand...
Click to collapse
Are you referring to the broken setting for keyboard layout? We fixed that already and next build will be good, unless you're referring to a different issue.

bgcngm said:
Are you referring to the broken setting for keyboard layout? We fixed that already and next build will be good, unless you're referring to a different issue.
Click to expand...
Click to collapse
I Updated today to lineage-17.1-20201116 but the issue still persist when i enable the German Keyboard Layout:
The red one are what i get when i type

Bengelee said:
I Updated today to lineage-17.1-20201116 but the issue still persist when i enable the German Keyboard Layout:
The red one are what i get when i type
Click to expand...
Click to collapse
There are actually two different layers that affect the keyboard layout, and it seems like you're using FinQwerty over the top of the QWERTY kernel layout. I suggest you disable FinQwerty, and switch to the QWERTZ kernel layout.
To change the kernel layout, open the settings app (the one with the icon that looks like a gear) and navigate through 'system -> buttons -> additional buttons -> layout'. That should open a dialog with QWERTZ as one of the available settings.
Note that the location of this setting has changed since 16.0, and will likely move again to the 'languages & input' settings in the near future. Hopefully it will be happy there, and not move again!

mccreary said:
There are actually two different layers that affect the keyboard layout, and it seems like you're using FinQwerty over the top of the QWERTY kernel layout. I suggest you disable FinQwerty, and switch to the QWERTZ kernel layout.
To change the kernel layout, open the settings app (the one with the icon that looks like a gear) and navigate through 'system -> buttons -> additional buttons -> layout'. That should open a dialog with QWERTZ as one of the available settings.
Note that the location of this setting has changed since 16.0, and will likely move again to the 'languages & input' settings in the near future. Hopefully it will be happy there, and not move again!
Click to expand...
Click to collapse
i uninstalled FinQwerty and selected the Kernel Layout German for the Keyboard. Then i rebooted.
I have still the same error with the shifting. But i had the right layout on the FinQwerty
Regards
Bengele

Bengelee said:
i uninstalled FinQwerty and selected the Kernel Layout German for the Keyboard. Then i rebooted.
Click to expand...
Click to collapse
It's not that option. Go to Settings / System / Buttons / Additional buttons. Then choose the proper keyboard layout.

Bengelee said:
i uninstalled FinQwerty and selected the Kernel Layout German for the Keyboard. Then i rebooted.
I have still the same error with the shifting. But i had the right layout on the FinQwerty
Regards
Bengele
Click to expand...
Click to collapse
I found the Option that you mentioned. Now it works without FinQwerty.
On the Stock Rom for the Pro 1 i also just changed the Physical Keyboard Layout as the picture shows above. Thats why im wondering why its so "complicated".
Anyway thank you so much for your help if i can support you with some testing feel free to contact me

Next weekly build will be big and among misc changes, it includes IMS fix. Thanks to @shubell for all the testing.

Hello,
i spend now many hours to root the Pro 1 with successful installed Lineage 17.1-20201214-nightly and i failed.
I sideloaded magisk v21.1 (successful) installed the Magisk manager apk v8.03
Manager shows:
Newest : N/A
Installed: N/A
Ramdisk: yes
A/B Yes
SAR Yes
Crypto File
I saw special boot.img, Stock Firmware to fix that but nothing worked.
Please someone can write a working How To ? Or add the lineage su addon for 17.1
I miss my Afwall+ ;-D
Thank You very much !
P.S. Whats up with these google usb drivers for pro 1 ?

well the instructions on the lineage wiki are quite well written for a pure lineage system.
If you want gapps you need to skip the last part where it says go “Reboot system now” after OS install but need to go to "Reboot to recovery". After you get to recovery again you flash gapps. After that it is wise to boot the system if it boots . If it works, reboot to recovery and install magisk. Not rly sure how magisk 21.1 works on lineage 17.1 but i had no problems with 20.4.
edit:
Had no issues with pr1 google drivers... at least can't remember that I have had them

Hey shubell,
Yes its okay But nothing said about rooting the Phone ;(
I didnt try gapps, i am using lineage for a google free phone
sideloaded lineage, than magisk 20.4 , rebooted to lineage and installed the manager apk worked well ?
I will test that
These usb drivers are important ?

Schuhabtret0r said:
Hey shubell,
Yes its okay But nothing said about rooting the Phone ;(
I didnt try gapps, i am using lineage for a google free phone
sideloaded lineage, than magisk 20.4 , rebooted to lineage and installed the manager apk worked well ?
I will test that
These usb drivers are important ?
Click to expand...
Click to collapse
start linage magisk free, after that reboot go to recovery and install magisk 20.4

Worked, thank you @shubell

Related

[ROM][unOFFICIAL] LineageOS 14.1 for Nexus 5 (hammerhead)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of android, which is designed to increase performance and reliability over stock android for your device.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Wiki.
Important Info
Information and installation instruction can be found on the LineageOS wiki here.
NOTE 1: The newest version Google Camera app in the play store does not fully support our camera hardware. You need to use an older version of the app if you want 100% working camera. You can download it from here and install it, then immediately go to the camera app in the play store and tap the 3 dot menu in top right corner and disable auto updates.
NOTE 2: I recommend using the newest radio and bootloader from the final factory image released by google (M4B30Z, Dec 2016). You can extract them from the factory image here, or use the ones linked below that I already extracted.
They can be flashed with fastboot.
Tip: If your device already has these versions installed, there's no need to reflash them. You can boot into fastboot mode and see the radio and bootloader version numbers.
* radio-hammerhead-m8974a-2.0.50.2.30.img
* bootloader-hammerhead-hhz20h.img
Download Links
LineageOS: https://download.lineageos.org/hammerhead
Note: Since the lineage build servers no longer make 14.1 builds, I started making them for you. Available here. My older builds here.
Google apps: (optional) http://opengapps.org/?arch=arm&api=7.1&variant=nano (Use arm / 7.1)
SU addon: (optional) https://download.lineageos.org/extras Note: Use 14.1 arm zip. After installing the su addon, you can enable root in developer options.
Weather Provider Addon (Optional)
For those that like the lineage cLock widget, here's the OpenWeather apk you need to get weather info.
https://mirrorbits.lineageos.org/WeatherProviders/OpenWeatherMapWeatherProvider.apk
Note: You'll need an api key from OpenWeather.
Stats
https://stats.lineageos.org/
Credits
Many thanks to the LineageOS team and all the contributors out there in the community :good:
Contributors:
cdesai, droidfivex, razorloves
Source Code:
Device tree: https://github.com/LineageOS/android_device_lge_hammerhead/tree/cm-14.1
Kernel tree: https://github.com/LineageOS/android_kernel_lge_hammerhead/tree/cm-14.1
Vendor tree: https://github.com/TheMuppets/proprietary_vendor_lge/tree/cm-14.1
Android version: 7.1.2 Nougat
Kernel version: Linux 3.4.0
Status: Nightly
Great News
Excellent. Will try and revert with some screenshots.
How is the rom for non caf? What are the bugs? Is it stable? Does it have the pixel nav bar animation?
HammerHead0101 said:
How is the rom for non caf? What are the bugs? Is it stable? Does it have the pixel nav bar animation?
Click to expand...
Click to collapse
why don't you try it for yourself instead of asking what is working or not. that's why there's a custom recovery called TWRP so you can back up and restore your data.
cheeze.keyk said:
why don't you try is for yourself instead of asking what is working or not. that's why there's a custom recovery called TWRP so you can back up and restore your data.
Click to expand...
Click to collapse
Yeah man just flashed it. Working great but no Pixel Nav Bar . Everything working fine
it's a last bootloader and radio img?
HammerHead0101 said:
Yeah man just flashed it. Working great but no Pixel Nav Bar . Everything working fine
Click to expand...
Click to collapse
screenshot pls
Been waiting for this. Will Xposed work on 7.1 though?
FEEDBACK SO FAR:
At first, most of Google made apps didn't work, had to reinstall them. CM Bug Report app keeps crashing at every restart. HDR doesn't work on Google Camera (it's there but it doesn't work). Theme Engine missing is a known fact, we'll have it in future updates. Many CM features from the settings menu, don't work, they are present and active, but no changes occur when using them. Battery charges slow as you can see from the screenshot.
The rest seems ok, after 3 hours of use.
Offtopic opinion. The Navigation dropdown with all it's quicksettings and whatever is a downgrade for me. Lollipop/Marshmallow had better looking system graphics, with floating navigation bar and notifications and nicer animations when pulling the notification bar down. Now it's just fullscreen flat thingy.
Had to take this of my chest regarding Android Nougat...but we have to blend with the evolution right?
Screenshots:
gigis50 said:
FEEDBACK SO FAR:
At first, most of Google made apps didn't work, had to reinstall them. CM Bug Report app keeps crashing at every restart. HDR doesn't work on Google Camera (it's there but it doesn't work). Theme Engine missing is a known fact, we'll have it in future updates. Many CM features from the settings menu, don't work, they are present and active, but no changes occur when using them. Battery charges slow as you can see from the screenshot.
The rest seems ok, after 3 hours of use.
Offtopic opinion. The Navigation dropdown with all it's quicksettings and whatever is a downgrade for me. Lollipop/Marshmallow had better looking system graphics, with floating navigation bar and notifications and nicer animations when pulling the notification bar down. Now it's just fullscreen flat thingy.
Had to take this of my chest regarding Android Nougat...but we have to blend with the evolution right?
Screenshots:
Click to expand...
Click to collapse
What version are you using? 2.7, 3.2 or 4.X? Have you tried video recording?
amnher said:
What version are you using? 2.7, 3.2 or 4.X? Have you tried video recording?
Click to expand...
Click to collapse
Always on the latest updates. It updated by itself after booting, it's 4.2.xxx
Video recording works. Google Camera used to have a bug and it still does on CM13, but on the Nexus 4. When trying to slide to video, it force closes... Same on my tablet with an unofficial CM13, it's a Galaxy Tab Pro 10.1.
I know the HDR doesn't work because usually it deactivates the flash when it's on, or the other way around (turning on flash disables HDR), but now it's doesn't do that and the flash works with HDR on and it shouldn't...
I think something like this was happening in CM12 and it started working after a few updates of the Google Camera and CM...
Still 3.2.045 is the last version supported in official stock rom so its ok
amnher said:
Still 3.2.045 is the last version supported in official stock rom so its ok
Click to expand...
Click to collapse
it downloaded from the Play Store.
Another short feedback: the user avatar is not visible in the lockscreen...
ROM Feedback
I installed CM 14.1 as secondary rom on nexus 5. ROM installed successfully. Here is my feedback
1. Theme engine is missing.
2. Some setting options are not working.
3. Developer Options are enabled but not opening.
4. Charging slowing.
Some screenshots are attached.
gigis50 said:
it downloaded from the Play Store.
Another short feedback: the user avatar is not visible in the lockscreen...
Click to expand...
Click to collapse
Google Camera 4.2 (Play Store) doesnt support HDR+ for hammerhead, you need v3.2
armando_rod said:
Google Camera 4.2 (Play Store) doesnt support HDR+ for hammerhead, you need v3.2
Click to expand...
Click to collapse
That was the lastest version for Marshmallow, right?
Downgraded and it works. Hope to see the latest version work soon, too...
Another short feedback: Apps sometimes have no sound, so you have to restart the phone...
Any CDMA love?
gigis50 said:
That was the lastest version for Marshmallow, right?
Downgraded and it works. Hope to see the latest version work soon, too...
Another short feedback: Apps sometimes have no sound, so you have to restart the phone...
Click to expand...
Click to collapse
Hi,
Would you please check if everything's working with Google Camera 3.2 on this ROM? Mostly video recording, HDR pictures and the panoramas.
Thanks in advance.
New update 02/12, but no changelog..
Fumas said:
New update 02/12, but no changelog..
Click to expand...
Click to collapse
Sent from my Nexus 5 using XDA-Developers mobile app

[ROM][10] LineageOS + PixelExperience // personal builds

This thread hosts personal builds of LineageOS 17.x and PixelExperience 10 for Mix 2. Full credits to Arian, Wight and others doing the actual bringup, allowing us to build upon the awesome work.
Small changes in my builds:
Default stretch-to-fullscreen (force apps to render in 18:9) - LOS official solution defaults to OFF, which complicates setup
Grey-blue DeskClock color scheme (when possible)
Navbar stays on the right side of the screen under 270° rotation (optional - set the behaviour with "setprop persist.ui.seascape.disable <true|false>" in a rooted shell)
Signature spoofing support from MicroG
Revived navbar layout tuning via sysui_nav_bar tunable
...
What's working:
Everything?
Instructions:
Use firmware Stable V11.0.3.0
Use official TWRP
Download the latest build and optionally GAPPS (PE comes with GAPPS though, don't use any from external sources)
Reboot to TWRP
Flash the latest build, GAPPS and whatever other additions you need
Reboot
Extras:
Read here if you want to use unencrypted data - post is from Oreo thread, but still applies
Downloads:
SourceForge folder: https://sourceforge.net/projects/andyyan/files/ - new releases in the "10" folder
Root: use Magisk
Google Apps: http://opengapps.org/
Source Code:
https://github.com/LineageOS/
Donation:
Donate to @NeoArian
Donate to @wight554
Donate to me
XDA:DevDB Information
LineageOS 17.x, ROM for the Xiaomi Mi Mix 2
Contributors
AndyYan, NeoArian, wight554
Source Code: https://github.com/LineageOS/
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: MIUI V11.0.3.0
Based On: LineageOS
Version Information
Status: No Longer Updated
Created 2020-01-11
Last Updated 2020-02-27
Reserved
I don't know for how much longer I'll be able to keep building these, but even if I do stop, these should still serve as a good basis for installing GSIs, so you can leverage many of them out there, including my own. As far as I've tested the only major bug on that front is the proximity sensor.
Compared to the test builds of last year...
- Now using official LOS device trees - you might have to clean flash even if you come from a previous test build by me
- IMPORTANT regarding PE - if you're clean flashing, flash the package twice so that /system can be populated properly. I have no idea why this is happening...
is there any ETA on android 10 Resurrection Remix?
also thanks for your work as usual!
Mollic said:
is there any ETA on android 10 Resurrection Remix?
Click to expand...
Click to collapse
Its customization-centric role has largely been replaced by Havoc nowadays, so with my limited SSD space I'm dropping that as well.
Screen time have a bug, is look like this.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
great job for years
Grick713 said:
Screen time have a bug, is look like this.
Click to expand...
Click to collapse
Have you changed your system font? Seems incompatible.
Have a problem while installing new PE.
Wiped everything (system, vendor, data). Installed zip (twice, as advised), no error messages.
TWRP warns on reboot that no OS is installed. Phone reboots to fastboot.
Tried twice with the same result. Tried re-downloading zip without success.
Ok, managed to solve the problem. As the device tree is from LOS, the solution is in the LOS thread. Need a recovery with support for SAR. Seems like official TWRP does not. So flashed recovery from the first post of LOS thread and the OS have installed just fine.
dairinin said:
Have a problem while installing new PE.
Click to expand...
Click to collapse
Thing is, I tried Wight's SAR TWRP and it's the same thing on my side - I really had to flash it twice (but not in the same queue/go).
This shouldn't have happened in the first place either, as LOS flashed just fine without this hassle.
@AndyYan
Nice to see you again being active, and thx (of course to all users who made it possible) providing LOS 17.
I know, this is probadly the wrong thread for this, but openGapps doesn't provide GAPPS for 10. The option is always greyed-out. Where do i get GAPPS then?
SanHelios said:
@AndyYan
Nice to see you again being active, and thx (of course to all users who made it possible) providing LOS 17.
I know, this is probadly the wrong thread for this, but openGapps doesn't provide GAPPS for 10. The option is always greyed-out. Where do i get GAPPS then?
Click to expand...
Click to collapse
You can find them on Sourceforge: https://sourceforge.net/projects/opengapps/files/arm64/beta/
However, not flashable on LOS: Gapps detect SDK 27 (Android 8.1). @AndyYan, can you look into it?
Update: found that PE prop.default file is fine, but for LOS it's old (says SDK=27 and some stuff more). I think you forgot to include proper props to LOS build.
SanHelios said:
@AndyYan
Nice to see you again being active, and thx (of course to all users who made it possible) providing LOS 17.
I know, this is probadly the wrong thread for this, but openGapps doesn't provide GAPPS for 10. The option is always greyed-out. Where do i get GAPPS then?
Click to expand...
Click to collapse
candiduslynx said:
You can find them on Sourceforge: https://sourceforge.net/projects/opengapps/files/arm64/beta/
However, not flashable on LOS: Gapps detect SDK 27 (Android 8.1). @AndyYan, can you look into it?
Update: found that PE prop.default file is fine, but for LOS it's old (says SDK=27 and some stuff more). I think you forgot to include proper props to LOS build.
Click to expand...
Click to collapse
Aw, I don't use GAPPS so I didn't verify that...
Does manually changing prop.default make it pass? Supposedly there's nothing in the device source dictating that.
AndyYan said:
Aw, I don't use GAPPS so I didn't verify that...
Does manually changing prop.default make it pass? Supposedly there's nothing in the device source dictating that.
Click to expand...
Click to collapse
There are several lines that need to be changed (for instance, arch is set to 'arm' instead of 'arm64'). I decided to go with PE for now and don't want to reconfigure all stuff once more.
What a treat to start 2020 to! Thanks for the new build Andy. I'll be reporting back if I find something buggy or similar =)
candiduslynx said:
You can find them on Sourceforge: https://sourceforge.net/projects/opengapps/files/arm64/beta/
However, not flashable on LOS: Gapps detect SDK 27 (Android 8.1). @AndyYan, can you look into it?
Update: found that PE prop.default file is fine, but for LOS it's old (says SDK=27 and some stuff more). I think you forgot to include proper props to LOS build.
Click to expand...
Click to collapse
Weird, I didn't had this problem yesterday. I used "open_gapps-arm64-10.0-nano-20191209-BETA.zip" on LOS.
@AndyYan Thanks for your build of LOS, it's working like a charm here.
Just gotta need a patch for my provider APN. (I'm on it)
Great news!!! Thank you Andy. Can i dirty flash from LOS16 to LOS17?
The problem is solved，thanks！
SanHelios said:
@AndyYan
Nice to see you again being active, and thx (of course to all users who made it possible) providing LOS 17.
I know, this is probadly the wrong thread for this, but openGapps doesn't provide GAPPS for 10. The option is always greyed-out. Where do i get GAPPS then?
Click to expand...
Click to collapse
I recommend flamegapps
Thanks @AndyYan for the build. I have flashed the PixelExperience version and it is working fine. Using Parrot043's GCam version and the photo quality is also fine.
The major issue I have is regarding VoLTE incoming call support on my carrier (Airtel/India). Outgoing calls are fine, but for incoming (VoLTE) calls my phone doesn't ring at all, but on the caller side it looks as if it is ringing and I am not answering calls. For the time being I have switched to WCDMA mode.
Any input to solve the VoLTE issue is highly appreciated. I have tried creating an APN named IMS with type as ims, but that didn't work.

[ROM][UNOFFICIAL] LineageOS 19.1 for Xiaomi Mi 8 Pro(15/6/2022)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 11.0 (R), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Note: This ROM uses FBE encryption, any current existing recovery won't be able to decrypt data!
Working:
Camera
WiFi
Bluetooth
Audio (Record and Playback)
Video Playback
Sensors
GPS
NFC
Encryption (FBE)
Under display fingerprint
Broken:
You tell me.
Downloads
Need TEST, please report to me whether it works for you(October patch): download
Old version: AndroidFileHost
Recommended firmware
V12.0.5.0.QECCNXM
How to flash
Reboot to recovery
Format /system, /data and /cache
Flash the firmware(optional, but you'd better do it)
Install LineageOS zip package
Install a Google Apps package of your choice(optional)
Contributors
bgcngm, rtx4d, YumeMichi, shivatejapeddi, jjpprrrr, jwhan​Sources:
Common device tree
equuleus device tree
Xiaomi SDM845 common kernel
Common vendor blobs
Last edit 15/6/2022
2021.06.09 Changelog
June security patch
2021.07.12 Changelog
July security patch
Fix contactless payments with Google Pay
Have you thought about making your build an official LineageOS build ?
What's missing from your build to meet the LineageOS charter for being accepted as an officially supported build ? Except face unlock which as far as i know it's not part of the LineageOS charter
sunfire said:
Have you thought about making your build an official LineageOS build ?
What's missing from your build to meet the LineageOS charter for being accepted as an officially supported build ? Except face unlock which as far as i know it's not part of the LineageOS charter
Click to expand...
Click to collapse
Good question, I will take a consider of it.
Hello, I am a simplified Chinese user, English is not very good. This ROM is well done and there is no problem at the moment. Thank you for taking the time to complete this project. But in the process of using it, we found that some options in the settings have not been translated. Is there a simple way to complete the simplified Chinese translation?
kinho0901 said:
Hello, I am a simplified Chinese user, English is not very good. This ROM is well done and there is no problem at the moment. Thank you for taking the time to complete this project. But in the process of using it, we found that some options in the settings have not been translated. Is there a simple way to complete the simplified Chinese translation?
Click to expand...
Click to collapse
Show the screenshot and tell me where to change, I will change them on my next build
jwhan said:
显示截图并我的位置发生了变化，我将在更新时发生的变化
Click to expand...
Click to collapse
View attachment 5343019
View attachment 5343023View attachment 5343025
kinho0901 said:
View attachment 5343017View attachment 5343019View attachment 5343021View attachment 5343023View attachment 5343025View attachment 5343027View attachment 5343029View attachment 5343031View attachment 5343033
Click to expand...
Click to collapse
How to translate the
1. LiveDisplay
2. DSU Loader
3. Helplines
Please tell me how you want to named them.
jwhan said:
Helplines
>求助热线
No helplines found.
Insert a SIM card and try again
>没有找到求助热线，请插入SIM卡后重试
DSU Loader
>DSU挂载
Load a Dynamic System Update Image
>加载一个动态系统更新镜像
KiII foreground app
>关闭前台应用
POWER MENU
>电源菜单
Screenshot
>截屏
Long—press for partial screenshot
>长按选择部分区域截屏
Airplane mode
>飞行模式
User switcher
>用户切换
Bug report
>报告bug信息
Bug reporting is disabled as development settings aren't enabled
>由于未开启开发者选项，报告错误被功能被禁用
Lockdown
>锁定
Lockdown is disabled as keyguard isn‘t secure
>由于没有使用安全键盘，锁定功能被禁用
Emergency
>紧急呼救
Turn off when fully charged
>充满电后关闭
Thermal profiles
>热配置文件
Adjust per—app thermal profiles for optimum performance
>为每个应用调整热配置文件以获得最高性能
LiveDispIay
>实时效果显示
Click to expand...
Click to collapse
There are also some suggestions on whether the multi task manager can be changed into MIUI, which provides a button at the bottom of the screen to clean up all processes, and also removes the screen capture button at the bottom of the screen.
kinho0901 said:
There are also some suggestions on whether the multi task manager can be changed into MIUI, which provides a button at the bottom of the screen to clean up all processes, and also removes the screen capture button at the bottom of the screen.
Click to expand...
Click to collapse
No, I like it. I will edit the string.xml in the next build but won't change the task manager
kinho0901 said:
View attachment 5343017View attachment 5343019View attachment 5343021View attachment 5343023View attachment 5343025View attachment 5343027View attachment 5343029View attachment 5343031View attachment 5343033
Click to expand...
Click to collapse
Sorry to tell you I finally give up it after consider long time. Btw I can tell you to edit which repositories and make a new build if you still want to change them. And it's weird that some strings have been translate into Chinese but it does not show even if we select the Chinese language. :<
jwhan said:
LineageOS is a free, community built, aftermarket firmware distribution of Android 11.0 (R), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Note: This ROM uses FBE encryption, any current existing recovery won't be able to decrypt data!
Working:
Camera
WiFi
Bluetooth
Audio (Record and Playback)
Video Playback
Sensors
GPS
NFC
Encryption (FBE)
Under display fingerprint
Broken:
You tell me.
Downloads
from AndroidFileHost
Recommended firmware
V12.0.5.0.QECCNXM
How to flash
Reboot to recovery
Format /system, /data and /cache
Flash the firmware(optional, but you'd better do it)
Install LineageOS zip package
Install a Google Apps package of your choice(optional)
Sources:
Common device tree
equuleus device tree
Xiaomi SDM845 common kernel
Common vendor blobs
Last edit 2021-08-09
Click to expand...
Click to collapse
Can i install this rom on my device? Mi 8 EE?
AleFeick7w7r said:
Can i install this rom on my device? Mi 8 EE?
Click to expand...
Click to collapse
I think you can't
jwhan said:
Good question, I will take a consider of it.
Click to expand...
Click to collapse
I second this. Please ask LineageOS to include you and make official builds. Thanks!
veloo said:
I second this. Please ask LineageOS to include you and make official builds. Thanks!
Click to expand...
Click to collapse
Sorry, I finally decided to give it up after consider some time. I am not a qualified maintainer as I dont have much time to maintain the rom. We may spend much time on it as the official maintain.
installed and setup with pico gapps running smooth and clean well done developers
Quick question I get error alert from trust on every reboot its nothing major just wanted to know why see screenshots
sajeel said:
Quick question I get error alert from trust on every reboot its nothing major just wanted to know why see screenshots
Click to expand...
Click to collapse
Just because I build this rom with public key. I am a little lazy so I don't do this. You can disable it on trust app if you don't want to see it.
jwhan said:
Just because I build this rom with public key. I am a little lazy so I don't do this. You can disable it on trust app if you don't want to see it.
Click to expand...
Click to collapse
Can I use bank apps with this ROM without needing to install magisk? I don't use root. I'm looking for a ROM that similar to Xiaomi.eu that works 100% bank apps without root.
vinydasilveira said:
Can I use bank apps with this ROM without needing to install magisk? I don't use root. I'm looking for a ROM that similar to Xiaomi.eu that works 100% bank apps without root.
Click to expand...
Click to collapse
The safetynet should pass but I don't know whether your bank app detect other else. Just have a try. However You should not try this rom if you like memeui. It's very difference to the memeui.

[OFFICIAL] LineageOS 19.1 for the Google Pixel 2

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Google Pixel 2
Code:
- Your warranty is now void.
- You have been warned.
- Use at your own risk.[/CENTER]
Introduction:
This is the Official Lineage OS 19.1 thread for the Google Pixel 2.
Downloads:
Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed.
walleye​
walleye - My unofficial with Google Apps/Pixel goodies included. Passes SafetyNet by default. OTA's roll roughly once a month. Support not guaranteed or implied.​
If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.
Known Bugs:
None.​
Find any? Report them according to this guide.​
Notes:
The only supported GApps package at the moment is MindTheGapps, linked on our Wiki page about gapps.​
Firmware is shipped in the ROM package for this device, so no need to worry about updating it on your own!​
Kernel Source: https://github.com/LineageOS/android_kernel_google_wahoo
I just tried this and it all works except the Camera. When trying to open it, I'm getting
Camera keeps stopping
- App info
- Close app
Any idea why that might be?
nschloe said:
I just tried this and it all works except the Camera. When trying to open it, I'm getting
Camera keeps stopping
- App info
- Close app
Any idea why that might be?
Click to expand...
Click to collapse
gah, in the unofficial I included _too new_ a google camera. Will be fixed in next build.
nschloe said:
I just tried this and it all works except the Camera. When trying to open it, I'm getting
Camera keeps stopping
- App info
- Close app
Any idea why that might be?
Click to expand...
Click to collapse
New build is up - fixed.
> New build is up - fixed.
Confirmed working. Thanks!
I'm using Official LineageOS 18.1, and now I'd like to install LOS19. But adb sideload los.zip no response for a long time. even use pure LOS recovery or twrp. In LOS recovery, 'Verifying update package...', In twrp, just keep rolling progress bar. Adb command interface no response. I can use Ctrl+C to cancle it.
I downloaded a software from Chrome.When I try to install it.The system rebooted.
dcshallot said:
I'm using Official LineageOS 18.1, and now I'd like to install LOS19. But adb sideload los.zip no response for a long time. even use pure LOS recovery or twrp. In LOS recovery, 'Verifying update package...', In twrp, just keep rolling progress bar. Adb command interface no response. I can use Ctrl+C to cancle it.
Click to expand...
Click to collapse
yup, it's verifying, leave it and wait for it - or try a different cable.
One stupid question:
As per the instructions here: https://wiki.lineageos.org/devices/walleye/upgrade
to upgrade from 18.1 to 19.1... Is it enough to just sideload the 19.1 zip file with adb? . Is it not a requirement to have flashed the correspondent recovery image for 19.1 beforehand (like in a normal first-time LOS installation)?
cognid said:
One stupid question:
As per the instructions here: https://wiki.lineageos.org/devices/walleye/upgrade
to upgrade from 18.1 to 19.1... Is it enough to just sideload the 19.1 zip file with adb? . Is it not a requirement to have flashed the correspondent recovery image for 19.1 beforehand (like in a normal first-time LOS installation)?
Click to expand...
Click to collapse
nope! that guide is right. Follow it and you'll have a good time.
However, I personally do reccoemnd lineage recovery, so I'd flash 19.1 recovery then start
is this build stable for daily usages?
galibalmasanick said:
is this build stable for daily usages?
Click to expand...
Click to collapse
of course
npjohnson said:
nope! that guide is right. Follow it and you'll have a good time.
However, I personally do reccoemnd lineage recovery, so I'd flash 19.1 recovery then start
Click to expand...
Click to collapse
OK, flashed 19.1 recovery, then sideloaded LOS19.1.zip as per the official guide... everything worked fine, phone rebooted in Android 12.
Testing here and there, everything seems to work fine. The camera app seems to have downgraded to just very basic features compared to the cam app in LOS 18.1. Thanks for that, I will report back if I notice some issue, but so far all good.
cognid said:
OK, flashed 19.1 recovery, then sideloaded LOS19.1.zip as per the official guide... everything worked fine, phone rebooted in Android 12.
Testing here and there, everything seems to work fine. The camera app seems to have downgraded to just very basic features compared to the cam app in LOS 18.1. Thanks for that, I will report back if I notice some issue, but so far all good.
Click to expand...
Click to collapse
Yeah, Snap is gone. Only Camera2 now.
My unofficial ship with Google Camera.
npjohnson said:
yup, it's verifying, leave it and wait for it - or try a different cable.
Click to expand...
Click to collapse
The phone was nearly become a brick because of the laptop. I thought it caused by Anti-Virus software. Then I used another pc to finish the installing. LOS 19 has some small issue in inform displaying, should be fixed in coming future.
dcshallot said:
The phone was nearly become a brick because of the laptop. I thought it caused by Anti-Virus software. Then I used another pc to finish the installing. LOS 19 has some small issue in inform displaying, should be fixed in coming future.
Click to expand...
Click to collapse
What small issue?
I can't fix it if I don't know what it is lol
npjohnson said:
What small issue?
I can't fix it if I don't know what it is lol
Click to expand...
Click to collapse
1, Settings -> Storage -> App usage size incorrect. Initial shown system used 14GB space, after some time(now), System 8.2GB, 'Open Camera' 5.56GB of User Data. The first time I found this issue was that after installing Nova Launch. I tried clear it's app data, not work, then I uninstalled it. Now, the space transfer to Open Camera. Uninstalling doesn't change the total usage ( The app is too small ).
2, Settings -> About Phone -> IP address, always 26.26.26.1 and da26:2626::1. I'm sure it's not my IP.
3, I use V2rayNG which is a VPN service. It has a quick setting Tiles. At once I reboot the phone and enabled v2rayNP from Tiles while the service was still off. Then I found registered VPN service disappeared from settings -> network -> vpn.
dcshallot said:
1, Settings -> Storage -> App usage size incorrect. Initial shown system used 14GB space, after some time(now), System 8.2GB, 'Open Camera' 5.56GB of User Data. The first time I found this issue was that after installing Nova Launch. I tried clear it's app data, not work, then I uninstalled it. Now, the space transfer to Open Camera. Uninstalling doesn't change the total usage ( The app is too small ).
2, Settings -> About Phone -> IP address, always 26.26.26.1 and da26:2626::1. I'm sure it's not my IP.
3, I use V2rayNG which is a VPN service. It has a quick setting Tiles. At once I reboot the phone and enabled v2rayNP from Tiles while the service was still off. Then I found registered VPN service disappeared from settings -> network -> vpn.
Click to expand...
Click to collapse
1. I have no idea why your apps report huge size. That's not a Lineage thing tho.
2. That's... Odd what router do you have?
3. That is definitely an app bug, VPNs work here.
1.As you see, Open Camera show a huge size. But actually, at first, the size was normal. Well, before Open Camera, it was Nova Launcher. It just need some time that the LOS make it so.
2. I'm in China, and I use a VPN service built by myself but it's not located in US. 26.26.26.1 is a US IP, right?
Should I make a clean LOS install? I'm not sure after the adb no response accident, has something went wrong? I don't want to download & backup & restore, that's horrible.
Hi,
I've just installed this ROM. Thanks for the work !
I just have a problem with the customization menu in the settings. The activity is crashing instantly.
It's the menu "Fond d'écran et style" in french (don't know the exact name in english :s).Tthe one allowing to change home and lockscreen background.
Is it working for you ?

Development [ROM][Android 13][OFFICIAL] LineageOS 20 for Xiaomi 11 Lite 5G NE / Mi 11 LE [lisa]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 13 (T), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Downloads
Here
Flashing instructions
Here
Upgrade instructions
Here
Sources:
- LineageOS
- Kernel Tree
Happy modding!
Reserved
Okay but does it run Crysis?
I've been running it and everything seems to work ok
Links provided by you are loopy and I don't seem to find any link to the "firmware.zip" you have mentioned in your website. Please write some more details. I'm very excited to flash it
Edit: Found everything.
Hey @Its_Vixano,
Thank you for this release in the first place, I'm really happy with it. Seems to be stable so far after the few days I've been running it.
I have only noticed some minor UX bugs with the recents(/gestures) while using Trebuchet (I haven't experienced it yet after switching to Lawnchair), but a more important issue is that I cannot play audio on a Bluetooth device.
I tested it with several devices, they show up as connected, but they remain silent even on maximum volume.
My guess (from the logs and my experience) is that for some reason the bluetooth audio connection cannot be built up correctly, it seems like it gets interrupted every second or so.
Other than that, do you know if the camera quality is better with the stock MIUI camera app? If yes, maybe it would also be worth to include it in this ROM as well, since others are starting to include it, I figured it wouldn't be too much of a hassle.
I only meant these as suggestions/observations, if you need more information on the bug, please let me know.
Thanks in advance.
ardrift said:
but a more important issue is that I cannot play audio on a Bluetooth device.
I tested it with several devices, they show up as connected, but they remain silent even on maximum volume.
My guess (from the logs and my experience) is that for some reason the bluetooth audio connection cannot be built up correctly, it seems like it gets interrupted every second or so.
Click to expand...
Click to collapse
Are you sure is not caused by any system modification or modules flashed via magisk ??
I use everyday a bluetooth pair (AAC, Samsung buds live) without any issues
Its_Vixano said:
Are you sure is not caused by any system modification or modules flashed via magisk ??
I use everyday a bluetooth pair (AAC, Samsung buds live) without any issues
Click to expand...
Click to collapse
Thanks for the hint, I tried rebooting to safe mode so that all the 3rd party apps get disabled, and also disabled some system modifications manually (tasker, dev options), but these didn't help unfortunately :/
But now that you mentioned it's working for you, I thought that the reason might be that I flashed your ROM to the V13.0.9.0.SKOEUXM firmware I had installed previously. I will re-test with the V13.0.4.0.SKOMIXM firmware that you recommend in your guide as well, I'll get back with the results.
P.S: I have attached the installed modules list and the error logs.
ardrift said:
Thanks for the hint, I tried rebooting to safe mode so that all the 3rd party apps get disabled, and also disabled some system modifications manually (tasker, dev options), but these didn't help unfortunately :/
But now that you mentioned it's working for you, I thought that the reason might be that I flashed your ROM to the V13.0.9.0.SKOEUXM firmware I had installed previously. I will re-test with the V13.0.4.0.SKOMIXM firmware that you recommend in your guide as well, I'll get back with the results.
P.S: I have attached the installed modules list and the error logs.
Click to expand...
Click to collapse
Can you try reflashing the fw i mentioned ??
Its_Vixano said:
Can you try reflashing the fw i mentioned ??
Click to expand...
Click to collapse
I flashed it now and it fixed the problem, thanks for confirming that it was working for you.
Thank you for sharing this. I have a few questions. Is there a touch head option in fingerprint? Do banking apps give root warning? Camera app snap? Do you have any gcam you recommend or can we install miui camera?
Just pushed august ota
enjoy
by_BenjamiN said:
Thank you for sharing this. I have a few questions. Is there a touch head option in fingerprint? Do banking apps give root warning? Camera app snap? Do you have any gcam you recommend or can we install miui camera?
Click to expand...
Click to collapse
The least i can do for banking apps is to include ih8sn on my builds (which i already do it)
You're doing a remarkable work. What about submit for official build?
Its_Vixano said:
Just pushed august ota
enjoy
Click to expand...
Click to collapse
Thanks a lot for your great work!
AudioSculpt said:
You're doing a remarkable work. What about submit for official build?
Click to expand...
Click to collapse
who knows ?
Not sure where to ask this, I apologize if I'm asking in the wrong place. But how is the lack of the proximity sensor is handled in this ROM?
Do you face any issues when accepting calls or listening to WhatsApp audio messages?
Thanks for sharing your work.
Has anybody managed to get Google wallet working?
Flashed today, so far everything looks very good
Is it possible to get the stock Xiaomi Cam on this rom?
I need makro and ultrawide cam
Thanks a lot for this great Rom
I have a Xiaomi Mi 11 Lite 5G NE (256gb DG - Global Version). I bootloader unlocked it after a week's usage. It is visible to ADB and Fastboot on Windows 10.
Ran into a bit of a problem following the flashing guide.
Downloaded the following files:
boot.img
192 MB17 days ago
dtbo.img
24 MB6 days ago
lineage-19.1-20220824-UNOFFICIAL-lisa.zip
1.1 GB17 days ago
vendor_boot.img
96 MB17 days ago
From the link. Successfully flashed boot.img, vendor.boot.img, and dtbo.img. It automatically selected _b as a destination on the phone. Attempting a reboot with power + volume up never got me to a recovery screen, only had the Mi logo flash before re-entering fastboot.
I re-read the instructions and there's a place where it is a little unclear as to if recovery.img is to be used for all phones or not despite only being in the ys1 repository. So I downloaded that and flashed it (successfully), it auto selected _a as a destination.
Phone still continues to reboot to fastboot, but now without the Mi logo flashing (guessing I blew away whatever was left of the factory ROM on _a with that last move).
Suggestions on what to do next? I'm stuck at a place where the phone is in fastboot mode and connected to a Windows machine with adb and the proper drivers but I'm guessing has no bootable recovery or ROM so sideloading isn't an option.

Categories

Resources