[OFFICIAL] LineageOS 18.1 for the Google Pixel - Google Pixel ROMs, Kernels, Recoveries, & Other De

[OFFICIAL] LineageOS 18.1 for the Google Pixel - Google Pixel 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"
}
Google Pixel
Code:
- Your warranty is now void.
- You have been warned.
- Use at your own risk.
Introduction:
This is the Official Lineage OS 18.1 thread for the Google Pixel.
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.
Official builds:
sailfish
Unofficial - built once a month by me, includes GApps and Pixel goodies:
sailfish
If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.
Known Bugs:
Sound Trigger (Screen-off "Hey Google" detection) is nonfunctional due to incompatibilities with older proprietary binaries, and lack of system space for needed Google Apps.
Find any? Report them according to this guide.
Notes:
Firmware is shipped in the ROM package for this device, so no need to worry about updating it on your own!
The only supported GApps package at the moment is OpenGApps pico, linked on our Wiki page about gapps.
Kernel Source: https://github.com/LineageOS/android_kernel_google_marlin

npjohnson said:
Google Pixel
Code:
- Your warranty is now void.
- You have been warned.
- Use at your own risk.
Introduction:
This is the unofficial Lineage OS 18.1 thread for the Google Pixel.
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.
sailfish
If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.
Known Bugs:
IMS (VoLTE/ViLTE/WFC) is nonfunctional due to incompatibilities with older proprietary binaries
Sound Trigger (Screen-off "Hey Google" detection) is nonfunctional due to incompatibilities with older proprietary binaries.
Find any? Report them on this thread, and make sure to include logcat/dmesg as applicable.
Notes:
GApps are baked in, alongside other Pixel goodies - No, I will not be building without GApps included for this device. These builds are built, packaged, and signed by me, and not affiliated with LineageOS whatsoever.
This will likely never be official. At minimum, IMS would need to be fixed, and I haven't cracked it (yet). If you can get IMS working, please contact me, and we can work together!
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/npjohnson/android_kernel_google_marlin
Click to expand...
Click to collapse
Thank you so much

Thanks, good work !

Thank you for great work!
Bugs:
- WiFi MAC randomization toggle in Developer Options is not working, but AFAIK MAC randomization isn't even supported by original Pixel devices
- sRGB toggle in Developer Options not working
- Brightness/dimming acts funky and sometimes reduces brightness to 0 by itself, then the screen becomes unresponsive for a short time

DirtyAngelicaSecured said:
Thank you for great work!
Bugs:
- WiFi MAC randomization toggle in Developer Options is not working, but AFAIK MAC randomization isn't even supported by original Pixel devices
- sRGB toggle in Developer Options not working
- Brightness/dimming acts funky and sometimes reduces brightness to 0 by itself, then the screen becomes unresponsive for a short time
Click to expand...
Click to collapse
1. Expected, I disabled the function, it's broken, but there's no easy way to hide it.
2. Yeah, but color profiles through LiveDisplay should work in it's place?
3. I've hit this on stock a few times, wondered if it was my device or what - maybe a hardware digitizer bug?

npjohnson said:
1. Expected, I disabled the function, it's broken, but there's no easy way to hide it.
2. Yeah, but color profiles through LiveDisplay should work in it's place?
3. I've hit this on stock a few times, wondered if it was my device or what - maybe a hardware digitizer bug?
Click to expand...
Click to collapse
Thank you so much for the Sailfish July 2021 update
Edit: what computer 🖥 and OS do you use to compile your Rom's? Would you be so kind to make a guide with the commands you use to compile? I can't get the one from the LOS website to work :/ ty

spiral777 said:
Thank you so much for the Sailfish July 2021 update
Edit: what computer 🖥 and OS do you use to compile your Rom's? Would you be so kind to make a guide with the commands you use to compile? I can't get the one from the LOS website to work :/ ty
Click to expand...
Click to collapse
I use the same one's detailed on the Lineage wiki.
They work.
My personal PC specs: https://pcpartpicker.com/user/npjohnson/saved/#view=dr268d

Does this work with unlimited Google Photos storage? If so, I'm instantly installing it. Thanks in advance.
Edit: It does!!

Thanks for the August update dude! You're one humble dude for not posting that here.

npjohnson said:
1. Expected, I disabled the function, it's broken, but there's no easy way to hide it.
2. Yeah, but color profiles through LiveDisplay should work in it's place?
3. I've hit this on stock a few times, wondered if it was my device or what - maybe a hardware digitizer bug?
Click to expand...
Click to collapse
August 2021 unofficial update for Sailfish is working great ty

My experience these first weeks: the phone is very fast and responsive, battery lasting longer than last official stock firmware (Android 10). The following are the only issues I've found:
Automatic brightness going too low in the dark: This was present at least in the past two releases.
Android Auto not working in the car ("Test App" appears on screen when connecting to car USB). There's a workaround in the forums where you need to copy the .apk to a system folder here, or re-flashing gapps. This was also present in the last releases.
Great job!

I've found issues that the settings app seems to crash if you enter the permission screen on some (all?) apps. Just go into Facebook or Messenger or whatever and try to disable the microphone and there's a good chance for a crash
Also, I've definitely noticed what was mentioned above. This ROM seems to have 0% screen brightness as an option. The official LineageOS 16.1 does not.

rinaldimj said:
My experience these first weeks: the phone is very fast and responsive, battery lasting longer than last official stock firmware (Android 10). The following are the only issues I've found:
Automatic brightness going too low in the dark: This was present at least in the past two releases.
Android Auto not working in the car ("Test App" appears on screen when connecting to car USB). There's a workaround in the forums where you need to copy the .apk to a system folder here, or re-flashing gapps. This was also present in the last releases.
Great job!
Click to expand...
Click to collapse
1. I can take a look into this. Nothing has changed in auto-brightness since 18.0's initial push, so it must be device specific. Does it just go black?
2. Yeah, we can't fit full GMS - AA is one of the things I sacrificed to get GMS to fit.
Melionix said:
I've found issues that the settings app seems to crash if you enter the permission screen on some (all?) apps. Just go into Facebook or Messenger or whatever and try to disable the microphone and there's a good chance for a crash
Also, I've definitely noticed what was mentioned above. This ROM seems to have 0% screen brightness as an option. The official LineageOS 16.1 does not.
Click to expand...
Click to collapse
Permissions: Doesn't happen for me - do you have Magisk or something?

npjohnson said:
1. I can take a look into this. Nothing has changed in auto-brightness since 18.0's initial push, so it must be device specific. Does it just go black?
Click to expand...
Click to collapse
Not absolutely black, but so low the screen is unreadable. The firsts times it happened I thought adaptative brightness will correct it according to my selection, but it doesn't - at least for the lower end. The very next step in the scale is perfect for a minimum.
2. Yeah, we can't fit full GMS - AA is one of the things I sacrificed to get GMS to fit.
Click to expand...
Click to collapse
I undestand. I though this wouldn't be the case when I noticed that the required system app for Android Auto is very small (~3MB), but the truth is our devices really suffer the low storage.
Again, thank you very much, amazing job!

Has auto-brightness been fixed? It really did set itself to 0% last time I tried this ROM. Was there some way to get it back up? What about MAC address randomization and sRGB toggle?
MAC Randomization should be controllable by the OS itself, not hardware.
Your signature says "Lineage OS Developer Relations Manager". Does that mean that you know whether there is a plan to officially bring Lineage OS 18.1 to Pixel Sailfish in the future?

rinaldimj said:
Not absolutely black, but so low the screen is unreadable. The firsts times it happened I thought adaptative brightness will correct it according to my selection, but it doesn't - at least for the lower end. The very next step in the scale is perfect for a minimum.
I undestand. I though this wouldn't be the case when I noticed that the required system app for Android Auto is very small (~3MB), but the truth is our devices really suffer the low storage.
Again, thank you very much, amazing job!
Click to expand...
Click to collapse
I have sailfish, and took it in a pitch dark room, sure it got dark but I could still read it?
Maybe it's panel degradation? Do you see this problem on stock?
And yeah, it's not the devices fault really, LineageOS has grown like 50 mb in the last few weeks.
DirtyAngelicaSecured said:
Has auto-brightness been fixed? It really did set itself to 0% last time I tried this ROM. Was there some way to get it back up? What about MAC address randomization and sRGB toggle?
MAC Randomization should be controllable by the OS itself, not hardware.
Your signature says "Lineage OS Developer Relations Manager". Does that mean that you know whether there is a plan to officially bring Lineage OS 18.1 to Pixel Sailfish in the future?
Click to expand...
Click to collapse
1. See above, I can't recreate.
2. I hid it, LIveDisplay offers an alternative that actually works.
3. MAC Randomization - nah, it's more complicated than that - the controller and firmware have to play nicely - and they don't - so I disabled it.
And lastly, there's a note in the OP about why this won't (likely ever) be official.

Thank you for a prompt response! I never had auto-brightness issue with any ROM's, be they official stock images or Lineage OS official images. This ROM was the only one with that issue.
I hope you don't mind me asking, but why is it necessary for IMS to work? VoLTE doesn't work for some devices with official Lineage releases, but it doesn't get in the way of such releases either.

DirtyAngelicaSecured said:
Thank you for a prompt response! I never had auto-brightness issue with any ROM's, be they official stock images or Lineage OS official images. This ROM was the only one with that issue.
I hope you don't mind me asking, but why is it necessary for IMS to work? VoLTE doesn't work for some devices with official Lineage releases, but it doesn't get in the way of such releases either.
Click to expand...
Click to collapse
Given that the pixel is a US centric phone, and the US is shutting down everything except for voice over LTE this year, we don't want to ship something that's not going to work as an "upgrade".

Thank you for this ROM, it's fast and smooth.

Hii everyone
Thanks for this rom
Working nicely on sailfish
just one problem
a particular app is not working ( banking app )
i have attached the logs
kindly assist

Related

[ROM][10][ARM64] LineageOS 17.1 for the Galaxy J5 Pro [J530][02.02.2021]

IMPORTANT, PLEASE READ THIS
This is a ROM built from source and not a GSI!
Fix Camera stretch & force close for some camera apps
You can do it editing /vendor/build.prop file using MiXplorer (you’ll need ROOT).
Search for the line “vendor.camera.hal1.packagelist”
After the = are the name of different apps. Delete one of these and put the package name of the app that you want to fix. For example, com.facebook.orca is the Facebook package name.
Per default, the ROM comes with Whatsapp, ZOOM, Snapchat and Instagram added. Maximum 4 Apps are allowed in this line and must be separated by comma ",".
If you don’t understand, open this link to see visual steps.
Fix Camera stuck
Sometimes, the camera can get inaccessible if an app has crashed. If it happen, follow this:
Install this app. Open it and tap "Kill camera", then give it ROOT permissions. Done! Camera is working again.
Take in mind that if the camera is broken and you didn't do this, the audio in calls maybe not work.
GCam
This ROM can run GCam. Download a modded version for Exynos HERE. Thanks to Leonardo Estacio for his mod.
Games: this ROM works so good for gaming and can run ARM64 apps/games. If you feel lags, go to Settings > Battery > Battery Saver and performance > Performance Profile and set it to High Performance.
For close, i want to give a huge thanks to @Astrako - Without him this ROM haven't be possible <3

Changelog
===== 02-02-2021 =====
- Initial build

Good ROM , stable. Just sometimes the launcher takes time to load after lock screen

Camera ta stretched

Hi, Thanks a lot for your work!
Just installed, looks very good and fast. I'll report eventual bugs I'd see.
Presently I have to warn to change point five of installation, as it's
for J7:
GonicTEAM said:
Install the lineage-17.1-xx-UNOFFICIAL-j7xelte.zip
Click to expand...
Click to collapse
with "install lineage-17.1-20210202-UNOFFICIAL-j5y17lte.zip".
Another known problem on LOS17.1 is the wrong behaviour of the proximity sensor during calls, that permanently darkens screen, and solves disabling sensors on calls or using headphones.
I know that isn't an issue of your port but instead an internal LOS17, and maybe AOSP bug: I also have the same on an Ananjaser port for Note4, anyway I signal it, in the hope that someone can fix it.
Are you also planning to port LOS18 on J5/2017?
Kind regards

BT no Audio
WiFi keep disconnecting and wifi mac address keep changing after reboot
00:12:34:xx:xx:xx
and wifi mac is not match in
Settings>About and Network details>Advance
All in all rom works great

Hi.good rom. Microphone on call not work. And speaker on call echo sound

I use sim2 slut

Very beautiful! It's very quick and feels light. Unfortunately, the SIM card is not recognized, making the Rom unusable. You are the king if you can make sure that the SIM card is recognized. I carried out the installation according to your instructions. My device is the SM-J530F (J5Y17LTE)

Internet navigation appears to be possible only through WiFi.
With a SIM inserted LTE band appears to be blocked, LTE indicator has a superimposed x.
Pointing the browser to a site gives back "unable to load page"
net::ERR_NAME_NOT_RESOLVED.
Please fix it
Edit: I have reinstalled from scratch after some day, and now it's all OK.

justforlineage said:
Very beautiful! It's very quick and feels light. Unfortunately, the SIM card is not recognized, making the Rom unusable. You are the king if you can make sure that the SIM card is recognized. I carried out the installation according to your instructions. My device is the SM-J530F (J5Y17LTE)
Click to expand...
Click to collapse
I also have the same model, and can see my SIM.
But I cannot navigate (pls see my latter post).
The fact that calls don't work is an old problem in LOS, maybe coming from AOSP. It's due to malfunction of the front sensor, that should turn off screen and touch when the phone is close to cheek. A quick and dirty workaround is to put headphones on, or to disable sensors (Settings ->System ->Advanced ->developer options ->quick settings developer tiles -> Sensors off). Of course, while sensors are disabled, rotation, gps, and all apks needing a sensor output cannot work and possibly crash. At that point the phone app blue screen stays on, and one can tick loudspeaker, call end or launch some other app while on call.

Alvin50 said:
I also have the same model, and can see my SIM.
But I cannot navigate (pls see my latter post).
The fact that calls don't work is an old problem in LOS, maybe coming from AOSP. It's due to malfunction of the front sensor, that should turn off screen and touch when the phone is close to cheek. A quick and dirty workaround is to put headphones on, or to disable sensors (Settings ->System ->Advanced ->developer options ->quick settings developer tiles -> Sensors off). Of course, while sensors are disabled, rotation, gps, and all apks needing a sensor output cannot work and possibly crash. At that point the phone app blue screen stays on, and one can tick loudspeaker, call end or launch some other app while on call.
Click to expand...
Click to collapse
Hey,
On this LOS version i can use SIM ( SMS, Calls, Mobile Data ) ->
lineage-15.1-20180510-UNOFFICIAL-j5y17lte.zip

Hey,
On this LOS version i can use SIM ( SMS, Calls, Mobile Data ) ->
lineage-15.1-20180510-UNOFFICIAL-j5y17lte.zip
Click to expand...
Click to collapse
Ok, but it's an old version.
For newer versions I'm just triying a LOS 18.1 treble from AndY Yan, that looks promising and seems to have solved the previous issue.
Just updated yesterday, but presently may have some erratic reboot, I'm investigating whether it's a problem of mine or not. Minor problem, the signal strength triangle always stays empty.

Alvin50 said:
Ok, but it's an old version.
For newer versions I'm just triying a LOS 18.1 treble from AndY Yan, that looks promising and seems to have solved the previous issue.
Just updated yesterday, but presently may have some erratic reboot, I'm investigating whether it's a problem of mine or not. Minor problem, the signal strength triangle always stays empty.
Click to expand...
Click to collapse
Hey,
does the LOS 18.1 version recognize the SIM card? Are there any more problems besides the regular restarts? If not could you give me the link to the post?
I am currently using LOS 15.1 lineage-15.1-20180510-UNOFFICIAL-j5y17lte.zip but don't dare to root it because I fear that the rooting has led to regular reboots and the subsequent deletion of all data.

justforlineage said:
Hey,
does the LOS 18.1 version recognize the SIM card? Are there any more problems besides the regular restarts? If not could you give me the link to the post?
I am currently using LOS 15.1 lineage-15.1-20180510-UNOFFICIAL-j5y17lte.zip but don't dare to root it because I fear that the rooting has led to regular reboots and the subsequent deletion of all data.
Click to expand...
Click to collapse
Yes, SIM cards are recognized. Making and receiving calls works well, only rings on incoming call aren't working. the bug I claim is a reboot every 24 mins, that in any case doesn't affect the system.

Alvin50 said:
Yes, SIM cards are recognized. Making and receiving calls works well, only rings on incoming call aren't working. the bug I claim is a reboot every 24 mins, that in any case doesn't affect the system.
Click to expand...
Click to collapse
It's a shame that these mistakes exist ... With these mistakes, the rom is no good as a daily companion. I'll keep my fingers crossed that you will get the problem solved or that there will be an update.

Alvin50 said:
Yes, SIM cards are recognized. Making and receiving calls works well, only rings on incoming call aren't working. the bug I claim is a reboot every 24 mins, that in any case doesn't affect the system.
Click to expand...
Click to collapse
Did you root the rome? Have you ever tried booting into Safe Mode to see the rom reboot every 24 minutes? Downloaded another phone app to see if there is a sound on incoming calls? These possibilities just came through my head.

justforlineage said:
Did you root the rome? Have you ever tried booting into Safe Mode to see the rom reboot every 24 minutes? Downloaded another phone app to see if there is a sound on incoming calls? These possibilities just came through my head.
Click to expand...
Click to collapse
This ROM comes pre-rooted, anyway I'm used to Magisk, so I installed it too.
Don't blame at the developer: having some bug on an unofficial, out-of-the-box vanilla release is rather normal. Our job is to collaborate with developers, feeding them with our bug findings, possibly correlated with some log. Such ROMs aren't for daily use, it's well advertised in the first posts, already until the joined efforts of testers and developers achieve a reasonable reliability and stability level.
IMHO, this one is pretty usable, a temporized reset is a minor bug. There are other worse bugs, but with patience and constance they also can be overcomed.
Edit:
I just realized we are in the wrong thread. My latter posts are related to AndyYan's GSI LOS18.1. Better if we move our discussion there.
Kind regards

ROM IS VERY FAST AND VERY CLEAN!ALL WORKS FOR ME EXCEPT SIM CARD CONTACTS i cant see it even with 3RD party app
Edit:anyone know how to push apps into system?Link2sd and similar apps fails.If i push it from recovery phone doesnt boots!

[ROM][12L/12.1][OnePlus8T] PixelExperience [AOSP]

{
"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"
}
PixelExperience for OnePlus8T[kebab]
What is this?
PixelExperience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, boot animation)
Our mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device
Based on Android 12.1
Whats working?
Wi-Fi
RIL
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
FM radio
Fingerprint reader
Face unlock
NFC
Lights
Sound/vibration
Known issues
You tell me
DON'T FLASH GAPPS, THEY'RE ALREADY INCLUDED
Download from PixelExperience website
Donate
[*]UPI-ID:- [email protected]
[*]Paypal:- paypal.me/KakatkarAkshay
Translation
Help with project translation
Stay tuned
Our Telegram channel
Device Specified Telegram Group
Our blog
Android OS version: 12.1.0_r2
Security patch level: March 2022
Build author/Device Maintainer: Rohan Hasabe
Device Source code: https://github.com/PixelExperience-Devices
Kernel Source code: https://github.com/PixelExperience-Devices/kernel_oneplus_sm8250
Source code: https://github.com/PixelExperience
ROM Developer: jhenrique09

Reserved

Reserved

With the abomination that OOS12 is, I am now eager to switch to a custom ROM more than I was before. I will be definitely giving this ROM a try. Perfect timing! Will flash this week.

I can't se the latest build on website

Does Google Now Playing work?

So I haven't installed a custom rom in ages, I used the pixel experience instructions and everything seemed to go well, I tried to relock the device, but it wouldn't boot after it just keep taking back to the bootloader after telling me I had installed a rom (I don't recall exactly what it said), so I unlocked it again and it booted fine, I just assumed it was because I'm using a tmobile 8T+. the only issue I have at the moment is that it's forcing me to setup face unlock, I have absolutely no desire to do that, is there a way around this? it looks like I'll have to set it up to get passed the initial setup and I'm very unpleased about that, but it is what it is.
I'm going to go through with it, but I'm curious if there is a way to, not have to do it in the first place.
If anyone knows, I'd appreciate any tips or advice. thanks!
Edit: Ok, I've tried several ways to setup my phone and all of the force the use of facial unlock and it won't recognize my face so I'm going to try something else. It also told me that my phone was a pixel 6 pro, so that wasn't what I was expecting, I was under the impression from everything i've read that this rom was more of a AOSP made pixel and now I'm thinking it's a pixel rom made AOSPish.
I appriciate the effort, unfortunately it's not for me.

pro_granade said:
Does Google Now Playing work?
Click to expand...
Click to collapse
It doesn't, that's the only true "pixel only" feature

houstontaxi said:
I can't se the latest build on website
Click to expand...
Click to collapse
It's up right now

bookofjoshua said:
So I haven't installed a custom rom in ages, I used the pixel experience instructions and everything seemed to go well, I tried to relock the device, but it wouldn't boot after it just keep taking back to the bootloader after telling me I had installed a rom (I don't recall exactly what it said), so I unlocked it again and it booted fine, I just assumed it was because I'm using a tmobile 8T+. the only issue I have at the moment is that it's forcing me to setup face unlock, I have absolutely no desire to do that, is there a way around this? it looks like I'll have to set it up to get passed the initial setup and I'm very unpleased about that, but it is what it is.
I'm going to go through with it, but I'm curious if there is a way to, not have to do it in the first place.
If anyone knows, I'd appreciate any tips or advice. thanks!
Edit: Ok, I've tried several ways to setup my phone and all of the force the use of facial unlock and it won't recognize my face so I'm going to try something else. It also told me that my phone was a pixel 6 pro, so that wasn't what I was expecting, I was under the impression from everything i've read that this rom was more of a AOSP made pixel and now I'm thinking it's a pixel rom made AOSPish.
I appriciate the effort, unfortunately it's not for me.
Click to expand...
Click to collapse
It's a standard setup procedure even on stock Pixel phones.. You could just ignore any security input during setup, and then just add fingerprint in the settings after the system boot....

Has anyone already determined whether this OS based on A12.1 also has an increased power consumption when using the device?
I first noticed this with the pixel blaster and then with project zepyurus. The device is always warm and the battery is drained properly. However, it only loses 3-5% during overnight standby.

I flashed this rom today!
So far feels very good. I love it.
Question: If there is an new update, can i update inside the rom or must i reflash the new update?

nitroax said:
It's a standard setup procedure even on stock Pixel phones.. You could just ignore any security input during setup, and then just add fingerprint in the settings after the system boot....
Click to expand...
Click to collapse
there wasn't any option to bypass it, it only showed "try again" and "cancel". my last pixel was a 2xl and it didn't force me to add any security. this one forced me to add a pin and then went directly into the face id. I couldn't find any way get arround it, I tried copy from old phone, and setup as a new device and it was the same every time.

bookofjoshua said:
there wasn't any option to bypass it, it only showed "try again" and "cancel". my last pixel was a 2xl and it didn't force me to add any security. this one forced me to add a pin and then went directly into the face id. I couldn't find any way get arround it, I tried copy from old phone, and setup as a new device and it was the same every time.
Click to expand...
Click to collapse
hmm that's odd because i flashed feb build (that had faceunlock) and when it asked me for pin first, i just ignored it and got direct to system.

Is this build online? I think it got removed smh

Seems not online, when I click on the link it says error no file found, anyway if it's ready for download the dev will post the link, so we have to wait patiently

Yeah, the link went down, not sure why. I've asked @RohanHasabe8 on Telegram about an issue which I'm experiencing when trying to open network tab (WiFi/LTE) in the settings app (the app is crashing), but I haven't received a response.
Another issue that I've experienced on a new 12.1 build is that battery consumption is much higher than on a build from February.
To be fair with 12 build I had only one issue - with automatic brightness, it wasn't working perfectly - especially when I was using dark mode mainly and the app which had a white theme was opened at night and a screen went full brightness.

nitroax said:
hmm that's odd because i flashed feb build (that had faceunlock) and when it asked me for pin first, i just ignored it and got direct to system.
Click to expand...
Click to collapse
I'll try again to be sure. I started setup and I set the wifi, then agreed to the location etc, and the it aaked to set up backup (not sure if it did that when I set it up as a new device) then it went straight to set a PIN and there wasn't anything except the key pad, no option to skip, if I hit ->| button with out putting in a PIN it just sat there. No 2ay past it.

bookofjoshua said:
I'll try again to be sure. I started setup and I set the wifi, then agreed to the location etc, and the it aaked to set up backup (not sure if it did that when I set it up as a new device) then it went straight to set a PIN and there wasn't anything except the key pad, no option to skip, if I hit ->| button with out putting in a PIN it just sat there. No 2ay past it.
Click to expand...
Click to collapse
I mean this ,right after backup restore

nitroax said:
View attachment 5573927
I mean this ,right after backup restore
Click to expand...
Click to collapse
As I said there wasn't a skip option. I looked for it. But I'll try again.

[ROM][OFFICIAL][enchilada][13] LineageOS 20

Thank you so much @LuK1337 and happy new year for all!

Thanks~

Thank you @LuK1337 for keeping this device alive! Updated from 19.1, everything went smoothly and working good.
Love the new Aperture camera app, results are really nice - pics are nice and sharp, shutter is quick and snappy, UI is nice and the features are good. One thing I noticed though - pictures are 8 megapixels instead of 16 (I set the capture mode to maximize quality, but it's still 8MP). Also, on the video front, FPS is capped at 30 - can't change it in any of the resolution modes. Otherwise, very nice app, will be interesting to see where it goes next and how it grows

Have also updated from 19.1 to 20.0 without any issues so far, running smooth . Using MindTheGapps and Magisk v25.2 (installed using the unsupported method, by flashing zip in recovery), both without problems.
Thanks for the ongoing support for this device!

CrysisLTU said:
Thank you @LuK1337 for keeping this device alive! Updated from 19.1, everything went smoothly and working good.
Love the new Aperture camera app, results are really nice - pics are nice and sharp, shutter is quick and snappy, UI is nice and the features are good. One thing I noticed though - pictures are 8 megapixels instead of 16 (I set the capture mode to maximize quality, but it's still 8MP). Also, on the video front, FPS is capped at 30 - can't change it in any of the resolution modes. Otherwise, very nice app, will be interesting to see where it goes next and how it grows
Click to expand...
Click to collapse
Google Issue Tracker
issuetracker.google.com

LuK, you are awesome. Thank you LOADS for your work. I will enter my first fulltime job within the next few months, and I'll make sure to send you some bucks then!
Upgrade from 19 to 20 went smoothly, as described in the wiki. I also re-installed Magisk via .zip sideload, no issues at all!

Per the wiki page, we're still instructed to be on Android 11 before upgrading to LOS 20. Is that true if we're on LOS 19.1 right now? Or only for earlier versions of LOS?

Fantastic work Luk1337! I've been running an unofficial LOS20 and it's saved me from having to upgrade my phone to be able to use ASHA features and streaming music to my hearing aids. Seems I need an A13 ROMS to make that work.
With the official LOS20, the next thing I checked was if the fingerprint swipe gesture was restored. Could that be re-added with an update?

maigre said:
Per the wiki page, we're still instructed to be on Android 11 before upgrading to LOS 20. Is that true if we're on LOS 19.1 right now? Or only for earlier versions of LOS?
Click to expand...
Click to collapse
Not sure if that is the answer to your question, but the "Android 11" thing refers to the underlying OOS version. If you are on the latest/last OOS version (which you should be anyways if coming from LOS 19), everything should be just fine.

Spaceoid said:
Not sure if that is the answer to your question, but the "Android 11" thing refers to the underlying OOS version. If you are on the latest/last OOS version (which you should be anyways if coming from LOS 19), everything should be just fine.
Click to expand...
Click to collapse
I just did a clean install of LOS 19.1 last week. I was on Android 11 when I did that. But LOS 19.1 is Android 12. I can install LOS 20 on top of that setup? The wiki makes a strong point of stating Android 11 is a must. But as you're getting at, I think, that was perhaps for the original clean LOS installation. Others here are doing it without any trouble, ti seems.

Samms said:
First thing I checked was if the fingerprint swipe gesture was restored. Could that be re-added with an update?
Click to expand...
Click to collapse
Was that ever a thing? You sure are thinking of OnePlus 6?

maigre said:
I just did a clean install of LOS 19.1 last week. I was on Android 11 when I did that. But LOS 19.1 is Android 12. I can install LOS 20 on top of that setup? The wiki makes a strong point of stating Android 11 is a must. But as you're getting at, I think, that was perhaps for the original clean LOS installation. Others here are doing it without any trouble, ti seems.
Click to expand...
Click to collapse
Yip, if you were on latest Stock OOS before installing 19.1, you can now safely install LOS 20 over 19.1.
The warning in the wiki refers to 'firmware', which is OOS, also if you follow the link on how to upgrade the firmware, you will be forwarded to a page with instructions on how to update OOS to the very last version. So, everything is fine and in place for LOS 20!

Thanks for the update. I see two issues so far:
1. The Status Bar Location Indicator toggle in Developer Options doesn't seem to do anything
2. Whenever I boot I get a notification saying apps are ready to update, even though all are up to date. It then asks me to connect to wifi, even though I'm already connected. I can't go any further

Hi, upgraded smoothly. Two glitches so far :
1. Every once in a while systemui ("Interface") seems unresponsive and asks to wait or close. If I close screen goes dark and when unlocked, everything is fine but my (permanent) vpn icon is then missing in the status bar (vpn is still active though)
2. After first restart and after each systemui force close, cast is shown in status bar, connected (admittedly) to a known device (which is not even in my house...).

LuK1337 said:
Was that ever a thing? You sure are thinking of OnePlus 6?
Click to expand...
Click to collapse
It has been forever since that was a thing, but yes I do recall it was once a thing on the OP6. There used to be an app that was able to bring back this feature but that has stopped working since LOS19.
Another issue I have been bumping into is Bluetooth audio stuttering /w AAC. This was working fine in 19.1. Switching to SBC or disabling A2DP hardware loadoff in developer options seems to fix it for now.

Samms said:
It has been forever since that was a thing, but yes I do recall it was once a thing on the OP6. There used to be an app that was able to bring back this feature but that has stopped working since LOS19.
Another issue I have been bumping into is Bluetooth audio stuttering /w AAC. This was working fine in 19.1. Switching to SBC or disabling A2DP hardware loadoff in developer options seems to fix it for now.
Click to expand...
Click to collapse
I can copy that one here!
Never had issues with Bluetooth Audio before. On LOS20, if I play music over my BT headphones, after around 10 secs the music stops and the music player goes on pause.
In the music player notification, my phone is then shown as the sound device; in the Bluetooth settings, I am still connected to my headphones, though.
Rebooting my headphones fixes the issue, but for 10 seconds only again.
If I disable HD Audio (AAC, if I understood correctly) in the Bluetooth settings, the music works fine without any issues.
Not a big deal for me, I am not that into Bluetooth sound and anyways barely notice any difference, but I thought I'd mention it here.

Spaceoid said:
If I disable HD Audio (AAC, if I understood correctly) in the Bluetooth settings, the music works fine without any issues.
Click to expand...
Click to collapse
BT Audio was my primary reason to switch to an A13-based ROM. Mainly to allow audio streaming to my hearing aid. But now my regular BT earbuds keep stuttering when using AAC/HD Audio. Yes, SBC works fine for now, but it's strange to me that this wasn't an issue on LOS19.1.
On another note, I suppose BLE Audio is not supported on OP6?

Samms said:
BT Audio was my primary reason to switch to an A13-based ROM. Mainly to allow audio streaming to my hearing aid. But now my regular BT earbuds keep stuttering when using AAC/HD Audio. Yes, SBC works fine for now, but it's strange to me that this wasn't an issue on LOS19.1.
On another note, I suppose BLE Audio is not supported on OP6?
Click to expand...
Click to collapse
The last question would interest me, too. Didn't find anything on that matter on Google. Why wouldn't it be supported? As I said, Bluetooth audio is not my main field of knowledge.

Did somebody check if ih8sn still works with LOS20?

Question [ROM][OFFICIAL] LineageOS 19.1 for Moto Edge 20 Pro

{
"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"
}
Moto Edge 20 Pro
Code:
- Your warranty is now void.
- You have been warned.
- Use at your own risk.
Introduction:
This is the Official Lineage OS 19.1 thread for the Moto Edge 20 Pro.
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.
pstar - Official builds
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.
Kernel Source: https://github.com/LineageOS/android_kernel_motorola_sm8250

Is there still a problem with the black screen of death?

wangyi666 said:
Is there still a problem with the black screen of death?
Click to expand...
Click to collapse
It shouldn't no

Will you add the fingerprint variations?

I can't use fingerprint to unlock my phone after install los, even no options in system settings. ls it normal situation?Did los doesn't support fingerprint?

x-new said:
I can't use fingerprint to unlock my phone after install los, even no options in system settings. ls it normal situation?Did los doesn't support fingerprint?
Click to expand...
Click to collapse
We are working on it, some devices use goodix fp, it is not supported right now

Thanks for this, this ROM fixes so many problems that the stock ROM from Motorola has. It's so nice now being able to call fine, use WiFI calling, being able to turn wifi on and off without it crashing and rebooting etc etc! All issues on the stock ROM for myself and others!
And it's amazing to have double tap to wake that works and a screen brightness that lowers like it should .
Only issues noticed are the fingerprint sensor issue as above, which I know you're looking into Elctimon (big thanks!) and one I seem to be getting with third party launchers sometimes which is when returning to the home screen and tapping an app icon, it interacts with the previous app instead. It's fine if you just wait longer...
I've logged a bug report for both following the instructions in the original post.
The only feature I miss from stock is the ability to set refresh rate for games to 120 or 140hz sometimes, otherwise I like my phone to be at 60hz for power savings. I turn off all animations anyway. The dynamic refresh rates sadly don't work below 70% brightness (same as stock ROM behaviour)
I tried to flash the Moto games apk which did this but unfortunately I get a missing library error : "Package com.motorola.gamemode requires unavailable shared library moto-core_services; failing!".
Perhaps a quick toggle setting could be added for refresh rates?
P.S Always on Google listening hotword detection doesn't work if you follow the instructions and install the mindthegapps package linked, it seems that it doesn't install enough packages. It needs the Google app to be installed before the OS first boots it seems? Make sure the gapps you are flashing includes Google app if you care about this.

is dc (anti flicker) works well？ i have flashed los a few month ago but the dc stoping working after lock screen

Thank you Electimon, the black screen issue has resolved for me with the latest releases.

Do you think that merging the Goodix (GF3626 fingerprint sensor) related files from the Berlin (edge 20) LineageOS build would resolve the Goodix fingerprint not working issue?
The files: https://github.com/LineageOS/android_device_motorola_berlin/search?q=goodix
I made a branch of it with the files copied over but I wasn't sure about these two files, if anyone could help me with getting these created for our device that'd be awesome!
android_device_motorola_berlin/rootdir/etc/init/hw/init.mmi.overlay.rc at 136fd799ec84e4d6ed008ab2641cac3e2d5aef3c · LineageOS/android_device_motorola_berlin
Contribute to LineageOS/android_device_motorola_berlin development by creating an account on GitHub.
github.com
android_device_motorola_berlin/modules.load at 71457c4f0467182bf7ae7834efe6dbeffa129cb7 · LineageOS/android_device_motorola_berlin
Contribute to LineageOS/android_device_motorola_berlin development by creating an account on GitHub.
github.com
https://github.com/LaurenceGough/android_device_motorola_pstar (if it helps at all) pull requests were not allowed
Thanks!

Hello Electimon. Thanks for the ROM, it's great to have something different for this underdeveloped device.
I came to Lineage to try to solve a problem with Bluetooth, but it didn't work. The problem remains exactly the same, Bluettoh only works from time to time, most of the time it doesn't even turn on. Still, I'm going to stay in this ROM, because I think it's better than the stock one.
If you have any suggestions of what I can do please enlighten me.
I don't understand how this can happen to some people and Motorola doesn't recognize it and make a fix available. I don't know what else to try, but my problem is the exact one demonstrated by this guy on Reddit:
https://www.reddit.com/r/motorola/comments/ym02hj

Hi guys,
What's up with the random reboots in this ROM? I used to have that problem on the previous Lineage as well as on the latest LMODroid build.

I need the original camera to take 108mb

thomashastings said:
Hi guys,
What's up with the random reboots in this ROM? I used to have that problem on the previous Lineage as well as on the latest LMODroid build.
Click to expand...
Click to collapse
I'm at 71 hrs uptime now, this was not achievable on any previous ROMs for this device. I'm truly thankful for this release, it's just excellent.

thomashastings said:
Hi guys,
What's up with the random reboots in this ROM? I used to have that problem on the previous Lineage as well as on the latest LMODroid build.
Click to expand...
Click to collapse
Ive never had a random reboot on this ROM, well apart for one time which I'm 99% sure was to do with an OTA update.
I've run this ROM for many weeks too.
The only downside is no fingerprint reader for my Edge 20 pro phone and that's it.
It fixes a load of issues with the stock motorola ROM!

rambo2405 said:
I need the original camera to take 108mb
Click to expand...
Click to collapse
It's just pixel binned anyway like all modern phones the 108mp is kinda a waste of time I feel. Look into gcam for our phone that's worth installing.

Well, since the last update (March 28), Bluetooth is working normally. It's still too early to know if it's fixed, but it hasn't worked this well for a while.

Bothrops said:
Well, since the last update (March 28), Bluetooth is working normally. It's still too early to know if it's fixed, but it hasn't worked this well for a while.
Click to expand...
Click to collapse
Is that with the stock ROM?
I wondered if Motorola have also fixed the outgoing call issues that all the edge 20 and 30 phones are getting? Where you cannot make a call unless you reboot or turn off WiFi, which usually causes a reboot.
And when you turn WiFi off and on it reboots the phone...
Factory resetting does not resolve the issue but installing LineageOS does fix the issue. Sadly banks require so many workarounds now to work, and my fingerprint sensor still doesn't work but I know one of the Devs are working on it.
Sadly call quality for me is really bad on this ROM, next to unusable for me. I think it needs some kind of voice technology that's on the stock ROM but is missing from this ROM. But it's better than no calls so I'm running it for now.
Also I'm noticing very high WiFi latency spikes and packet loss jssues that was also an issue on the stock ROM. It uses the same drivers as the stock ROM so I guess that's expected. All other non Motorola devices are fine.

I take back what I wrote. After a few days working normally, Bluetooth became unstable again. For me Lineage has the same problem as the stock ROM. In my case, Wifi works perfectly both on stock and Lineage. But Bluetooth doesn't work properly on either of the 2.
Motorola drivers may not work for all Wifi and Bluetooth modules, as there may be hardware differences between devices. Anyway, it's a serious failure, due to complaints on websites, youtube, Telegram groups, etc... and the worst thing is that I haven't seen the problem acknowledged anywhere.

I do not recommend LineageOS for this device, WiFi/Bluetooth didn't get fixed and are features that is not fully workable as in stock rom. Also, Motorola has rollout the Android 13 stock rom and if you remove some bloatwares, I fully recommend it.

[OFFICIAL] LineageOS 20 for Pro1-X

{
"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"
}
Introduction
LineageOS, an open-source Android distribution, is available for several devices,
with more being continuously added thanks to the biggest, yet ever growing, Android open-source community.
Join us and breathe new life in your device, be it old or new.
Click to expand...
Click to collapse
If you don't know LineageOS and would like to read about it before installing it you can take a look at the official Website.
Features
Individuality
Customization is paramount to productivity.
That’s why LineageOS promises to push for user personalization and preference.
Everyone is unique and your device should be too.
Click to expand...
Click to collapse
Security
Trust will help you understand the security of your device and warn you about possible threats.
We take security very seriously: that’s why we deliver security updates every month to all our supported devices.
And to make your device more secure, lock everything behind an enhanced lock screen.
Click to expand...
Click to collapse
Longevity
LineageOS extends the functionality and lifespan of mobile devices from more than 20 different manufacturers thanks to our open-source community of contributors from all around the world.
Click to expand...
Click to collapse
Installation
If you are on stock OS, you need a custom recovery first. You can get the recommended recovery in the installation instructions below.
If you are coming from stock or other ROMs, you must do a factory reset. If you are upgrading from an older release in this thread, you do not need to reset!
As always, make sure to backup before installing this ROM.
More detailed instructions at:
Install LineageOS on pro1x.
Downloads
Download LineageOS 20
Google Apps package: MindTheGapps
Source code
All the source code for LineageOS is available in the LineageOS Github repo.
If you would like to contribute to LineageOS, please visit out Gerrit Code Review.
The device specific source code can be found in the LineageOS Github repo.
F(x)Tec Pro1-X device tree
F(x)Tec SM6115 kernel
Bug Reports
Please submit bugs and other errors in this thread.
Donate to support development
Donate via PayPal to vware
Or donate to LineageOS project: PayPal donation
Contributors
Georg Veichtlbauer
Sean McCreary
Nolen Johnson
And of course all LineageOS & Android contributors
Version Information
April 27
* Cleanups
* Fix A2DP
Spoiler: Previous Changes
April 20
* We've gone official!
April 11
* Key remapping support
* In-call audio improvements
April 3
* Audio configuration changes
* Haptic text handle
March 29
* Kernel 4.19.275
* Kernel updates from Google and CLO
March 22
* Android 13 QPR2
* aptX / aptX HD support
* Camera fixes for some apps
* Small kernel logging improvements
March 3
* Notification LED brightness settings now work
* Latest kernel updates
* Security updates
February 9
* ZRAM enabled for better multitasking
* Various keyboard updates (i.e. Fn+TAB will now open recents)
January 30
* Audio jack fixed
* Display reverted to Jan 24, had problems on some models
January 27
* Notification light fixed
* Kernel scheduling improvement
* Display now in cmd mode
* Added missing files (btconfigstore)
* Cleaned up some unneeded files
* Keyboard fixes are back (missing in the Jan 24 build)
January 24
* Nfc fixed
* Adjust physical layout of Gboard
January 20
Initial release
OS Version: Android 13
Kernel: Linux 4.19.275
Created 2023-01-20
Last Updated 2023-04-21

Woohoo!

Excellent!

Tested and works a treat!
Not afraid to play captian obvious or help new users here, so adding
Step 2 can be done in adb during android runtime if the finger combo did not work out:
adb reboot bootloader
Step 4 can be:
fastboot reboot recovery
Thanks a lot qsnc! Great work

Is it necessary to backup the persist partition like described here: https://community.fxtec.com/topic/3...o-the-pro1pro1x-available-for-download-links/
Or was that only a problem with early Ubuntu Touch releases?

dicer42 said:
Is it necessary to backup the persist partition like described here: https://community.fxtec.com/topic/3...o-the-pro1pro1x-available-for-download-links/
Or was that only a problem with early Ubuntu Touch releases?
Click to expand...
Click to collapse
Its always advised to backup whatever we can before tampering with anything.
That put upfront. No, the persist problem is only reported to be UT and SFOS related. Since those write into persist while out of SELinux context. Which can easily be repaired when back on stock and rooted.
I have not tested for lineage but i assume it uses the SELinux correctly just like stock and thus no problem should® appear.
If i am wrong here, the fix for the persist problem is reliable and easy to do. Just go for it imo.

Awesome work, thank you!
I have a Pro 1x, and unfortunately it is completely useless for voice calls on LTE, and very unreliable for voice calls on GSM.
It's a notorious fact that at this point the Pro 1x is really just a small Android tablet with a mechanical keyboard, not really a phone at all.
I understand Fx Tec is working on new firmware to try to address the problem, but nobody knows whether that is actually going to happen, or when.
So my question to all who have flashed this version of LineageOS, are you seeing any better result with voice connections, or is that too much to hope for?
It would be so awesome if the LOS devs have solved what Fx Tec hasn't yet (or can't). Multiple beers/coffees would doubtless be forthcoming to them.

I am glad it's working well for you guys!
Regarding the call problem: could you describe in more detail whats wrong? If it's a hardware or modem firmware issue, there is nothing we can do. There are some things we can try if audio quality isn't good for you though. During development, calls have actually been decent for me, I did have trouble with signal strength (nothing we as LineageOS can do about that, unfortunately).

Lots of discussion on Fx Tec's own forum, it's a known issue for a huge percentage of users since they first shipped in August.
Strangely, some people don't have as much of a problem, and the reason for the difference in user experiences is not clear yet.
So it's interesting @qsnc has not experienced it noticeably. Was that also the case for you on stock Android, or only after you flashed it with LOS? If the latter, then that's really good news...
My experience is that with stock Android on LTE, only maybe 10% of the time can I place an outgoing voice call. There is just a "click" and dead air when I finish dialing. It's a much higher percentage of time that I can place calls when I set the phone to use only GSM, but people calling me on GSM usually get a "This user is not available" message, it doesn't even go to voice mail, and does not ring my phone. That is the message that callers get pretty much every time they call me, if the phone is set to use LTE.
Fx Tec rep @Casey at their forum states that this is known to be a notorious problem, and " it is our top priority issue along with the battery protection":
Pro1x - really poor connectivity to both wifi and cellular.
community.fxtec.com
Voice over WiFi seems to work more reliably, both for receiving and placing voice calls. Not perfect, but more reliably.
On those odd occasions where voice calls do connect, regardless of whether using LTE/GSM/VoWiFI, the volume is almost at 0 unless you trigger the speakerphone, then once so triggered you can go back to the normal microphone and it will usually be broadcasting at normal volume (though not always):
Pro1X: Internal microphone/speaker issues - low gain, sensitive feedback avoidance?
Two Pro1-X issues, possibly related. First, the built-in microphone gain is extremely low. it makes my spouse completely inaudible during calls and only barely audible using a sound recording app. When we attach a wired headset, the microphone gain is fine. Second, and this one is really weird, w...
community.fxtec.com

That sounds like a couple of compounded problems. Honestly, I did not use stock at all except for a quick functionality test.
So the connection problem could be firmware and/or antenna related, I heard some people have problems with signal strength, even on our dev team. Not much we can do about that.
The volume problem most likely is not firmware but OS related, and I have not noticed such an issue on Lineage. Have you? Has someone else?
Of course, only Lineage specific problems can be dealt with here...

I just flashed and tested it. Good news: it flashed perfectly and started right up. Thank you!
Bad news: voice telephony behaves just as bad as stock Android. On LTE, placing a call, it just gives a "call ended" message on the screen, and doesn't even try to connect. Also, it will not receive a call on LTE, it just goes straight to voicemail for the outside caller.
Voice calls will work using GSM, but a bit more flaky than stock Android. The phone will sometimes ring, but there is no way to answer an incoming call. After the caller hangs up, I can see their call on the recents list.
Screen touch is a bit odd w/r/t stock Android, too. Swipe up seems to either lag or not work quite often.
Thanks again for including the 1x as a project, and I hope you stick with it.
Also, hopefully Fx Tec deals with the stuff that is beyond the remit of LOS.

limited_imagination said:
Bad news: voice telephony behaves just as bad as stock Android. On LTE, placing a call, it just gives a "call ended" message on the screen, and doesn't even try to connect. Also, it will not receive a call on LTE, it just goes straight to voicemail for the outside caller.
Voice calls will work using GSM, but a bit more flaky than stock Android. The phone will sometimes ring, but there is no way to answer an incoming call. After the caller hangs up, I can see their call on the recents list.
Click to expand...
Click to collapse
Could you tell us the signal strength reported by the pro1x when you are having trouble with voice calls? You can find this in Settings->About phone->SIM status->Signal strength, and it should be something like "-108 dBm 32 asu" (but hopefully better than that).

I must thank a lot for this release, it improved the user experience compared to 2.1.5 non GMS firmware I was using.
So far I observed two bugs:
- NFC cannot be turned ON.
- screen with pin code in landscape mode is distorted, but pin still can be entered on screen or via hw keyboard
As for LTE (and wifi) connectivity, I do not think lineage can fix this, it is either modem firmware (I hope so) or antenna issue (I am afraid of).
Myself I did some measurement and to me it seems the problem is only on some channels/frequencies. Looking at the details I posted in Fxctec forum:
Channel B1, B9, B20 are quite OK to signal level around -110dBm (B1 was far the best), Channel B3 was a big problem even at -85dBm.
The problem I see is that various people complain about "bad signal on LTE", but are not providing details.

new release is up, thanks for all the feedback! our team is working on an improved keyboard driver with more options coming, stay tuned!
see the first post for download options.

Thank you, NFC now works and actually is able to read the only NFC tag I have (it was broken on 2.1.5 stock)

rasva1 said:
Thank you, NFC now works and actually is able to read the only NFC tag I have (it was broken on 2.1.5 stock)
Click to expand...
Click to collapse
That's good news. Do you mind specifying what the NFC tag type was? This'll help us debug the stock firmware. Thanks.

KC_Cheung said:
That's good news. Do you mind specifying what the NFC tag type was? This'll help us debug the stock firmware. Thanks.
Click to expand...
Click to collapse
It is Mifare Classic. On 2.1.5 I was getting someting like "NFC read error"

thanks for the work!
one question, when keyboard is open and I use arrow keys for navigation - the direction is not right. up/down make left/right movement and vice versa (which kind of makes sense if you place the device vertically )
tried in launcher and terminal.
am I the only one who's experiencing this?

Wow, I am not using cursor keys much, but you are right, same here
But PageUp, PageDown, Home and End seem to work correctly.

and another one for the weekend, guys. see the first post.
we will work on the keyboard once our improved driver is done, which should be soonish.

Database Develop

welcome