Development [ROM] [13] PixelPlusUI v5.x [OFFICIAL]

Development [ROM] [13] PixelPlusUI v5.x [OFFICIAL] - Redmi Note 11 (spes/spesn)

{
"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"
}
Code:
* Your warranty is now void.
* We are not responsible for anything that may happen to your phone by installing any custom ROMs and/or kernels.
* You do it at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected developers.
"This is a user-friendly thread, all your suggestions, and proper bug reports are important to us but don't be disrespectful to anyone here. Your suggestions and proper bug reports will be taken into consideration.."
PixelPlusUI is another aftermarket AOSP ROM Minimal UI & close to Stock Android ROM. What differentiates us from the rest, you ask? LET'S FIND OUT. It has additional localized and personalized functionality while preserving the stock Android look by adhering to Material Design guidelines. Unlike OEMs' slow and untimely updates, we closely follow Google to bring the latest updates to our users, and even prolonging support to devices that have been declared obsolete by OEMs. Our ROMs' source code is open-source, secure, stable, and outstanding. Your experience using PixelPlusUI will be butter smooth with added convenience and features. The main aim of this form is to give the user a better experience without compromising the quality of the Android experience so that no one struggles with any kind of difficulties while using their device. PixelPlusUI brings a better UI/UX to Android with a seamless experience coupled with customizations and user security. In short, it's perfectly balanced between Great Performance, Security, Stability, Minimal UI & Awesome features including pixel goodies But this doesn't mean we aim to provide all the customization available on the planet. So do not hesitate anymore, join us now and start enjoying the beauty of stock Android. Download and enjoy PixelPlusUI on your respective devices!
- Kostya Maslennikov - Founder
- Saurav - Co-Founder & Co-lead Developer
- Hamza - Co-lead Developer & Team
- And Also Our Hardworking Maintainers
// Checkout the latest changes you get //
Latest Changelog: Tap Here for changelog
NOTE : Well here you get all the useful features and with updating source every month it's hard to keep all the threads updated everytime everywhere so kindly visit our website for latest changes and screenshots.
// A screenshot is worth of thousand words //
Latest Screenshots :
PixelPlusUI
ppui.site
NOTE : Well here you get all the useful features and with updating source every month it's hard to keep all the threads updated everytime everywhere so kindly visit our website for latest changes and screenshots.
--------- Official Download Server ! ---------
Note: You can check our Website for more details, guides , changelog etc related to build !
-- DEVICE UPDATE TELEGRAM CHANNEL --
-- SUPPORT/DISCUSSION TELEGRAM GROUP --
-- Visit our OFFICIAL Website
-- OUR OFFICIAL TWITTER HANDLE --
NOTE: It is STRONGLY recommended to fully wipe your device before flashing and please avoid restoring system apps and system data with Titanium Backup (or with any backup/restore app) as this can cause stability issues that are very hard to debug, restoring regular apps is fine.
If you believe you know what you're doing - then fine, go ahead, but please don't complain if you experience any strange behavior.
CLEAN FLASH :
- Download the latest build
- Reboot to recovery.
- Take a backup.
- Format Data
- Flash the latest build
- Reboot
What works?
Wifi | RIL | Mobile data | GPS | Camera
Flashlight | Camcorder | Bluetooth | Fingerprint reader | Lights | Sound | vibration
Almost everything
What doesn't work?
Nothing yet
You tell me!
BUG REPORT !!
As soon as the problem occurs, take a logcat and please inform us via Telegram or XDA.
for more READ THIS
- Android Open-Source Project
- Pixel Experience
- LineageOS
- Others, I forgot to mention
- Android OS version: 13
- Security patch: October 2022
- Build author/Device Maintainer : imannig
- DEVICE: Redmi Note 11
- DEVICE CODENAME: Spes/n
Sources and Documentation
- ROM Source Code
- Kernel Source
- OFFICIAL DEVICES
// Giving little CAN HELP A LOT //
- As you know build is free but building ROM needs a server. And Maintaining source and device stuff needs a server and it's pretty expensive for a student.
- Do consider donating on Patreon for sustainable support and rewards or buying me a coffee if you want to appriciate our work.
- Thank you for your support !
* UPI ID: [email protected] (Indian Users)
* Paypal:
Pay Sourav Ghosh using PayPal.Me
Go to paypal.me/uglykid24 and type in the amount. Since it’s PayPal, it's easy and secure. Don’t have a PayPal account? No worries.
www.paypal.me
* Bitcoin (BTC): 3Pm6JtwqCuTfKe1Szn23C8ZutF32eFtzf9
* Buy me a Coffee: https://www.buymeacoffee.com/Uglykid/membership

Nice update

I'm about to flash this right now bcs I'm sick of stock miui copycat ios experience. I hope there will be no major bugs, and it would be smoth just like tthe previous update.

Very nice ROM! Some fun: now google seen my device as "Huawei Nexus 6P"

Oops... Can't achieve USB file transfer mode.

USB doesn't works (exept charge) while system run.
In "fastboot" and "recovery" modes USB works fine.

very nice stable rom thanks much imanning and sourav for the support

I just had the weirdest bug with this ROM. Google Play Services doesn't work with my WiFi (both 2.4 & 5GHz) that means nothing gets downloaded from Play Store, but everything works fine with a different WiFi or mobile data. My WiFi is fine, checked on a different phone and it was working fine a while ago on MIUI. Nothing makes sense!

TorAllex said:
USB doesn't works (exept charge) while system run.
In "fastboot" and "recovery" modes USB works fine.
Click to expand...
Click to collapse
do you already have a way to solve it, here is the same as usb only charging can't transfer files and allows usb debugging

When update?

There's problem in hotspot. Can't able to change password or wpa

xstage said:
do you already have a way to solve it, here is the same as usb only charging can't transfer files and allows usb debugging
Click to expand...
Click to collapse
Yes it not working bro.. also hotspot's password problem.

KAPPI1925 said:
Yes it not working bro.. also hotspot's password problem.
Click to expand...
Click to collapse
I had the same problem. I solved it by changing the shutdown time to 1 hour. After that I managed to change the password and the network id.
My problem now is that the microphone on the bluetooth headset is not working, only from the cell phone.

aelson.moura said:
My problem now is that the microphone on the bluetooth headset is not working
Click to expand...
Click to collapse
I use BT (car hands free) daily, no problems. Are you've try any different headset?

TorAllex said:
I use BT (car hands free) daily, no problems. Are you've try any different headset?
Click to expand...
Click to collapse
I use QCY T17, with the stock ROM the mic worked fine before. Do I need some configuration to get it working again?

TorAllex said:
Very nice ROM! Some fun: now google seen my device as "Huawei Nexus 6P"
Click to expand...
Click to collapse
Is google services work ok?

aelson.moura said:
Do I need some configuration to get it working again?
Click to expand...
Click to collapse
Can't help, sorry. I don't have QCY T17, my Parrot (car handsfree) and Mi True Wireless EBs - both work fine.
reg1stration said:
google services work ok?
Click to expand...
Click to collapse
Yes, no problems.

aelson.moura said:
I had the same problem. I solved it by changing the shutdown time to 1 hour. After that I managed to change the password and the network id.
My problem now is that the microphone on the bluetooth headset is not working, only from the cell phone.
Click to expand...
Click to collapse
This rom has more problems. So i switched to crdroid. Now the bugs are tool less. It was nearly 2 day. I haven't found any bugs in crdroid.
In Pixel experience:
I had problem in calling. When I use ear speaker(speaker for calls) after 2 or 5 sec the sound get off. But when i turn on speaker i can receive sound in my speaker.
So PE has too bugs. Which i have switched to crdroid.

KAPPI1925 said:
This rom has more problems. So i switched to crdroid. Now the bugs are tool less. It was nearly 2 day. I haven't found any bugs in crdroid.
In Pixel experience:
I had problem in calling. When I use ear speaker(speaker for calls) after 2 or 5 sec the sound get off. But when i turn on speaker i can receive sound in my speaker.
So PE has too bugs. Which i have switched to crdroid.
Click to expand...
Click to collapse
I switched to PE, and the only bug I noticed is the bluetooth headset mic doesn't work in most apps, it only works in PE's voice recorder app.

aelson.moura said:
I switched to PE, and the only bug I noticed is the bluetooth headset mic doesn't work in most apps, it only works in PE's voice recorder app.
Click to expand...
Click to collapse
If it works means no problem.

Related

[June 23] Sailfish OS for early adopters released for Nexus 4

Hello guys.
Here is the third update for Sailfish OS for Nexus 4:
Dear early adopter of SailfishOS for Android devices. This is important - read this whole mail through and follow all steps exactly as written.
IMPORTANT: If you choose to publish this mail through blogs, news sites, forums, or others, quote it as-is and in complete form ONLY, or people's devices may be at risk.
We're happy to publish the third Early Adopter Release of SailfishOS (1.0.7.16) for Nexus 4 (mako) to you.
We are still working on the SailfishOS Hardware Adaptation Development Kit, which describes how to port SailfishOS to existing devices based on CyanogenMod 10.1. Newer versions of CM will be supported eventually. We'll publish the HADK in the very near future.
This installation image is for early adopters only, meaning we know that some things are not functional or perhaps even broken -- please see the release notes below. We are excited to get all of you properly included in the early stages of the project. Do note that this SailfishOS image is strictly for personal and non-commercial usage only.
We've prepared a 'demo' version of the image which contains the kind of preinstalled 'marketing' content and the core apps used for demonstrations - this helps you quickly get a feel for all the interactions that are avalable on a device that has been used for a while but isn't really what you want for personal use. You can however cleanly remove the demo content.
We want to build a community around SailfishOS for Android devices that is based on mutual trust and respect for what we are all doing. Hence -- we ask that whenever you do screenshots, videos, forum or blog posts (and we're happy if you do!) or the like, you emphasise that this is an under-development snapshot and not a final product release.
It is important for Jolla that the correct expectations are set for those who might be users of the final product -- and that they understand what they see is not a released product. If you do demo videos, you can take advantage of our new 'demo content' image that has pre-set contacts/imagery/messages/etc to show full functionality of SailfishOS.
WARNING: Modifying or replacing your device’s software may void your device’s warranty, lead to data loss, hearing loss, hair loss, financial loss, privacy loss, security breaches, or other damage, and therefore must be done entirely at your own risk. No one affiliated with this project is responsible for your actions but yourself. Good luck.
NOTE: You will lose your on-device data (including /sdcard), so make a proper backup and make sure to copy that backup to your PC.
NOTE: Make sure to read all the release notes below. Please DO NOT contact Jolla Care for any issues encountered with this Early Adopters build, instead use communication channels listed below.
To install this release of SailfishOS on a Nexus 4 device:
* Install adb and fastboot
a. Debian/Ubuntu: apt-get install android-tools-adb android-tools-fastboot
b. Fedora: yum install android-tools
c. Mac OS X: Install Homebrew from http://brew.sh/, then: brew install android-platform-tools
d. Windows: See http://wiki.cyanogenmod.org/w/Doc:_fastboot_intro for instructions
* Install Android 4.2.2 (JDQ39) to your Nexus 4
a. Instructions here: https://developers.google.com/android/nexus/images#instructions
b. Download links can be found here: https://developers.google.com/android/nexus/images#occamjdq39
* Download CyanogenMod 10.1.3 for your Nexus 4
a. Perform Factory Reset and wipe contents of the /data/ partition in case of leftovers from previous ROMs
b. The file you want to download is cm-10.1.3-mako.zip
c. Download links can be found here: http://wiki.cyanogenmod.org/w/Install_CM_for_mako
* Download the SailfishOS for Android image for "mako"
a. The file you want to download is http://releases.sailfishos.org/sfa-ea/sailfishos-mako-release-1.0.7.16-EA3.zip
b. Another flavour filled with demo content: http://releases.sailfishos.org/sfa-ea/sailfishos-mako-release-1.0.7.16-EA3-demo-content.zip
* Install CyanogenMod 10.1.3 on your Nexus 4
a. Follow the instructions at: http://wiki.cyanogenmod.org/w/Install_CM_for_mako
* After flashing the "cm-10.1.3-mako.zip" file, flash the SailfishOS .zip file in the same way ("on top of it")
* Reboot bootloader, SailfishOS should boot and be visible
We recommend reading through http://jolla.com/guide/ -- some parts may not apply to Nexus 4
If you want to go back to normal CyanogenMod:
a. Boot into recovery mode
b. Choose "Wipe data / factory reset"
c. Flash cm-10.1.3-mako.zip
d. (to go back to SailfishOS, flash the SailfishOS .zip on top of it)
If you want to go back to stock Android:
a. Download the stock image from https://developers.google.com/android/nexus/images#occam
b. Extract the package and follow the instructions for reflashing/re-locking
To SSH into your device via USB (Linux)
1. Enable remote connection in Settings->System->Developer mode
2. Set your USB interface on host machine to IP 192.168.2.2
3. ssh [email protected]
4. Use the password from developer mode to log in
5. Use the 'devel-su' command with the same password in order to gain root
6. To SSH over WLAN, use IP listed in developer mode under "WLAN IP address"
Read Sailfish OS release notes:
https://together.jolla.com/question/45064/release-notes-software-version-10716-saapunki/
Release notes/Known issues in EA3:
* EXPERIMENTAL: Jolla Store is now available, you'll need to register with your Jolla Account
* NOTE: Booting Nexus 4 with SIM first, and then removing SIM (or vice versa) may cause Jolla Store to see it as two different devices and cause potential breakage. Please stick to either SIM available or not when running SailfishOS on Nexus 4.
- There may be a bug with oFono RIL support that makes it not report IMEI value causing this and will be sorted out in a later update.
* DISCLAIMER: Using Jolla Store with Jolla Account might break applications on your other devices, use it at your own risk!
* Android support is not available from the Store, even if you can see Android apps listed (those will be removed eventually from store view)
* This functionality means that image comes with only minimal set of pre-installed apps. Use Store to download the ones you need.
* The backlight is dark during first launch, but can be fix by switching the currently-not-working ambient light sensor off (uncheck Settings->System->Display->Adjust automatically)
* When display is blanked, power management sets WLAN to the lowest speed state
* Can be noticed in a SSH-over-WLAN session
* Chat notifications may arrive with a slight delay
Fixes after EA2:
* Watermark removed
* Phone-call audio volume can now be changed with the help of volume buttons
* Improved responsiveness when waking phone up with the power button
* Settings->System->Developer Mode or About Product do not freeze anymore
* Reverted to the original (non-Silica) Fingerterm
Fixes after EA1:
* Phone-calls with audio work
* Timers and alarms (with device powered on) work
* HTML5 video+audio works in Browser (tested splash on http://jolla.com )
* Update is based on SailfishOS version 1.0.5.16
Release notes/Known issues in EA2:
* To securely power off the device, during its boot-up keep Volume Down pressed to enter bootloader mode. Using volume keys, select "Power off" option, then press the Power key
* If not auto-detected from SIM, set-up mobile internet data settings via Settings->System->Mobile network->(long tap on the first toggle-item under "Mobile data" section)->(enter settings given by your operator)
Nexus4-specific known issues reported by the adopters (in EA2):
* Chinese text input not working
* Localhost name is shown as Jolla
* Switching between the online and offline status in the status information setting takes very long and often doesn’t switch properly
* Google contacts which are put together with different information, are now split up into several contacts in Sailfish
* The battery display seems to be a bit buggy because it loses about 15% from one second to another
* The calendar overview when filled with events seems to be a bit laggy
* The email push is not working correctly, I do not receive any emails until I push the refresh button
* Splitting words in the German translation: e.g. in the open apps on the home screen it says: "Kurzzeitmesse" and in the next line the missing "r"
* NOTE: all other Sailfish OS issues have already been reported on TJC - http://together.jolla.com - and many of them were fixed in this 1.0.5.16 release
Release notes/Known Issues in EA1:
* Developer mode is activated at all times
* There has been no throughout testing of telephony related functionality (roaming, airplane mode, etc) and any use of this functionality is at your own risk
* Sensors, Device lock, Reset device, Bluetooth, USB control + MTP, Bluetooth, WLAN hotspot, Camera (photography, video recording), and video playback is not supported in this release
* The image SW is not currently upgradeable, nor is any typically licensed multimedia codecs (MP3, etc), HERE maps, Android application compatibility layer, or word prediction for virtual keyboard preinstalled
* This image does not include any typically licensed multimedia codecs (MP3, etc), HERE maps, Android application compatibility layer, Microsoft Exchange support, or word prediction for virtual keyboard preinstalled
* It is not possible to double-tap to wake up the device
* Powering off device puts it into a state of deep slumber; possible to get out of by holding power button and volume down key with a bit of persistence
* Fingerterm keyboard is not at its best due to the portrait-only mode
* FPS drop while scrolling in homescreen due to non-batching when rendering of application icon grid
* Icons/graphics appear unproportionally small in browser toolbar, time select widget, and Settings favourite icons
* Multiboot/Multirom is not supported yet but we're happy if you would like to teach/help us
We will all meet in #sailfishos-porters (note, new location) on irc.freenode.net and please use us (thp, alterego, Stskeeps, lbt, sledges) to work together, report any bugs, graphical glitches or missing functionality that you find, which are not included in the release notes above. You can also find the hardware adaptation source code at http://github.com/mer-hybris .
You are also welcome to participate in threads at http://forum.xda-developers.com/nexus-4/general about Nexus 4 and SailfishOS as well as for more general SailfishOS topics at http://forum.xda-developers.com/jolla-sailfish/general
Best regards,
Carsten Munk (Stskeeps) on behalf of the SailfishOS for Everyone team.
Chief Research Engineer @ Jolla
Click to expand...
Click to collapse
Video: Watch Sailfish OS on Nexus 4
====
Video: Watch Sailfish OS on SGS III 4G (i9305)
====
Video: Watch Sailfish OS Launcher for Android Beta
====

saraghon said:
We all know now that Sailfish OS from Jolla is coming soon to our beloved Nexus 4. This would be really great but I think it's taking more time than we expect. Here is the progress:
{
"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"
}
What's working:
===========
+ Display
+ Touch
+ Audio
+ GSM (SMS)
+ Vibration
+ Haptics
+ Power Management
+ USB (Networking, Charge)
Not working:
=========
- Wifi
- GPS
- Camera
- Sensors (ALS, Accerator, Gyroscope, Magn.)
- Vol +/- keys
Not tested:
========
* GSM (Voice)
Click to expand...
Click to collapse
Source..?

prateek80 said:
Source..?
Click to expand...
Click to collapse
https://wiki.merproject.org/wiki/Adaptations/libhybris

That's quite a long list of non-working hardware. Almost all of those are essential things I use every day, though I don't doubt the porters are doing the best they can do make these features available as fast as possible.

It's quite outdated. Voice calls ARE WORKING . and a few other things too.

LightingZ said:
It's quite outdated. Voice calls ARE WORKING . and a few other things too.
Click to expand...
Click to collapse
Source? ...

saraghon said:
Source? ...
Click to expand...
Click to collapse
i asked the people at #sailfishos irc

LightingZ said:
i asked the people at #sailfishos irc
Click to expand...
Click to collapse
Ok. That's great!

Want to touch it
Sent from my Nexus 4 using xda app-developers app

asuperpig said:
Want to touch it
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I think Jolla is soon going to releaser the Sailfish OS Launcher for Android Smartphones to give us the opportunity to have an idea about Sailfish experience before releasing the OS for Android powered devices.

Good news!
I updated the thread due to progress done on Nexus 4. There are new changes.
I think Jolla guys are focusing on Nexus 4 first before other Devices.

Come on,baby ! Just waiting for sailfish
Hope it improves fast and smooth,waiting for sailfish. thanks all DEV

saraghon said:
I think Jolla is soon going to releaser the Sailfish OS Launcher for Android Smartphones to give us the opportunity to have an idea about Sailfish experience before releasing the OS for Android powered devices.
Click to expand...
Click to collapse
It couldn't be better

LightingZ said:
It's quite outdated. Voice calls ARE WORKING . and a few other things too.
Click to expand...
Click to collapse
like wi-fi.. I can't wait!
do you know when they will release early builds?

mirkoziocan said:
like wi-fi.. I can't wait!
do you know when they will release early builds?
Click to expand...
Click to collapse
I think it'll be shortly after the 1.0.4.1 Update release simply because these builds are running that (1.0.4.1) update.

huh...
So there aren't any flashable zip file for this, eh?

saraghon said:
I think Jolla is soon going to releaser the Sailfish OS Launcher for Android Smartphones to give us the opportunity to have an idea about Sailfish experience before releasing the OS for Android powered devices.
Click to expand...
Click to collapse
I think the same, or something like the miui launcher they released for non suported devices
Enviado desde mi Nexus 4 mediante Tapatalk

Thread updated.

ddaggebi said:
So there aren't any flashable zip file for this, eh?
Click to expand...
Click to collapse
Not yet my friend!

looks like smart. i wanna try this os with n4. i think will be so good

[OFFICIAL] LineageOS 18.1 for the Google Pixel

{
"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

[ROM][OFFICIAL][R] LineageOS 18.1 for Xiaomi Mi 10T / Mi 10T Pro / Redmi K30S Ultra [apollo/apollopro]

{
"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.
Maintainers
- Ramisky
- SebaUbuntu
Recommended firmware
V12.1.3.0.RJDMIXM
Downloads
Here
Flashing instructions
Here
Sources
LineageOS
Happy modding!

Reserved

Thank you! Running since yesterday, using it as daily driver, no bugs encountered. Flashed MindTheGaps, and installed MGS Gcam latest 8 version.

Perfect wow,batery long?performance ?

whatsek said:
Děkuju! Běží od včerejška a používá jej jako každodenní ovladač, žádné chyby nenarazily. Flashed MindTheGaps a nainstalovaná nejnovější verze MGS Gcam 8.
Click to expand...
Click to collapse
What batery And peeformace?pls review

Hi,
great news !
is there the "sync" on/off in the quick tiles ?
does the NFC feature work?
How is the picture quality vs stock camera ?
how is the battery drain while in airplane mode for a few hours ?
Thanks

Thank you! Running since yesterday, using it as daily driver, no bugs encountered. Flashed MindTheGaps, and installed MGS Gcam lates
wiz.wiz said:
Hi,
great news !
is there the "sync" on/off in the quick tiles ?
does the NFC feature work?
How is the picture quality vs stock camera ?
how is the battery drain while in airplane mode for a few hours ?
Thanks
Click to expand...
Click to collapse
- Yes, sync button is in the quick tiles
- NFC is working fine, I can pay with my banking APP
- The stock camera is not good, replace is with a Gcam alternative, see other XDA Thread
- 0.8% drain per hour when sleeping. I do not use airplane mode.

whatsek said:
Thank you! Running since yesterday, using it as daily driver, no bugs encountered. Flashed MindTheGaps, and installed MGS Gcam lates
- Yes, sync button is in the quick tiles
- NFC is working fine, I can pay with my banking APP
- The stock camera is not good, replace is with a Gcam alternative, see other XDA Thread
- 0.8% drain per hour when sleeping. I do not use airplane mode.
Click to expand...
Click to collapse
Thanks a lot! That sounds good !
I don't know "MindTheGaps".
I like to have a very reduced set of gapps and google services, in that way the NikGapps with its customizable config file is great to me. Do you know if it is working with LineageOS ?
I'll migrate to it soon, maybe this w.e. as I don't want to be "phoneless" during the workdays

老哥们，快充问题有没人解决一下啊，唯一的问题了，感恩的心
K30s has a 33w fast charge, but when I use los, she even charges less. For example, from 30% to 29%. This makes it impossible for me to use it. I have been rooted and installed xposed, I don’t know if there is a reason for this. I hope someone who can solve it can help

wiz.wiz said:
Thanks a lot! That sounds good !
I don't know "MindTheGaps".
I like to have a very reduced set of gapps and google services, in that way the NikGapps with its customizable config file is great to me. Do you know if it is working with LineageOS ?
I'll migrate to it soon, maybe this w.e. as I don't want to be "phoneless" during the workdays
Click to expand...
Click to collapse
MindTheGaps was preferred by lineageos: https://wiki.lineageos.org/gapps.html I also did not know this version, but it is verry minimal and worked perfectly. I did not try NikGapps.

whatsek said:
MindTheGaps was preferred by lineageos: https://wiki.lineageos.org/gapps.html I also did not know this version, but it is verry minimal and worked perfectly. I did not try NikGapps.
Click to expand...
Click to collapse
Thanks for the details.
I can't find any info on the MindTheGaps contents... On NikGapps content is detailed and you can decide to skip any package installation, almost fully configurable.
Therefore I'll try the NikGapps 1st I think

prosby přidat game turbo a herní centrum
----------
MOD EDIT: English Translation Below
please add game turbo and game center

skorpicz said:
prosby přidat game turbo a herní centrum
Click to expand...
Click to collapse
can't you write in English ?
If everyone uses its native language it is going to be a huge mess...

Is LineageOS more fluid than MIUI? Is everything working properly? Is there any bug?

Possible bug found: when using android auto, all sounds come from the speakerphone I stead of the audio sumystem. I tried 2 different cars, same behaviour. And ofcourse I checked the settings. Looks like something in the Bluetooth connection.
Edit: anybody tried android auto with this rom?

whatsek said:
Possible bug found: when using android auto, all sounds come from the speakerphone I stead of the audio sumystem. I tried 2 different cars, same behaviour. And ofcourse I checked the settings. Looks like something in the Bluetooth connection.
Edit: anybody tried android auto with this rom?
Click to expand...
Click to collapse
Hi, I will install it hopefully this w.e. but I won't install android auto.
Did you test not using android auto and selecting the car BT as the audio output (for music player for instance), or using BT for any headset ?

wiz.wiz said:
Hi, I will install it hopefully this w.e. but I won't install android auto.
Did you test not using android auto and selecting the car BT as the audio output (for music player for instance), or using BT for any headset ?
Click to expand...
Click to collapse
Yes, normal Bluetooth functions such as calling and music streaming work fine on the same car system when Android Auto is not used. I'll just wait until somebody will test Android auto.

Hi man, I'm facing the problem, I can't disable the 5g network in the system, when I switch NR/LTE/GSM/WCDMA to GSM/WCDMA/LTE, it doesn't work, the network is still 5g. By the way, the network operator is China Unicom. Any chance to fix this problem? Thanks a lot.

Can I change screen refresh rate to 144Hz in this ROM? I can't find that option. Another - how can I flash recomended gaps? I tried many time without success.

panpetar said:
Can I change screen refresh rate to 144Hz in this ROM? I can't find that option. Another - how can I flash recomended gaps? I tried many time without success.
Click to expand...
Click to collapse
Search for: smooth display, which should increase it to 144Hz, although the text says 90Hz. Just flash the gapps.zip in your recovery, if that does not work you have a wrong gaps.zip

[ROM][UNOFFICIAL] LineageOS 18.1 for onyx

(reserved)

Thank you so much, I''ll be installing it tomorrow and will be active here if I found some bugs will report with logs once again thank you so much, much appreciated your work

The in call volume is very high even at the lowest volume level and screen doesn't go off when answering a call or dialing a call
let me know that do I need to post logs for this issue

thanks for trying it! i will be playing a bit trying to reintegrate into upstream lineage, if that does not work, i will continue down this path.
should have some news pretty soon, though it's summer

qsnc said:
The device specific source code can be found in the LineageOS Github repo.
OnePlus X device tree
OnePlus X kernel
Click to expand...
Click to collapse
Hmmm... But these are sources for tree 15.1, not for 18.1.

as ive said in the other thread, this is pretty much just built on top of the trees of Yume. you can find the sources there, or on my github (linked in my profile).
however, also, just a post above, ive stated i am working on re-upstreaming the whole thing, i am not done yet. and its summer ;P once ive got news, i'll update the thread.

new release. beware: quite a lot of changes, mostly bringing configs back to stock (original maintainers didnt understand the usage of i2s in the sound config apparently). however: this may cause unexpected problems, so please let me know if anything new goes wrong here
also, current source links are updated

just quick update
clean Installed it and so far it's fine. in call volume is perfect and screen also goes of now
I'll test it and see if I find any other bugs.. hopefully not
1 update: when it boots up it says signed with public keys

Random reboots keeps happening. Mainly when I try to switch between more than two apps or it could be something else. I've attached logs if it helps

niravnn said:
Random reboots keeps happening. Mainly when I try to switch between more than two apps or it could be something else. I've attached logs if it helps
Click to expand...
Click to collapse
Same here it crashes a lot and also the download manager seems to disappear.

I can confirm that it often crashes and just restarts for no reason

sadface. did the other build crash for you guys too?

qsnc said:
sadface. did the other build crash for you guys too?
Click to expand...
Click to collapse
no other build was fine it wasn't rebooting like your latest build. but the in call volume was so high at the lowest volume that it was unsable as daily driver and also screen wasn't turning off when receiving a call or dialing a call so it was also creating issue. so I only used your other build for like 30 minutes but not a single reboot at that time.
but with your latest build, it rebooted every 5 minutes. so it's completely unusable..

The version of the lineage-18.1-20220612-UNOFFICIAL-onyx.zip runs so far well with me no restart without reasons present.
Unfortunately, the display does not go off when making calls with the version lineage-18.1-20220612-UNOFFICIAL-onyx.zip when the phone is at the ear.
For me, the volume was ok, but not perfect either, I felt it was more quiet than loud.
It could be a bit louder.
Their new version lineage-18.1-20220623 I tested only briefly and then went back to the old one because of the constant reboots.

EDITED: pretty sure zram was the culprit in the new build, so please download from the first post again and try it, works okay on my device.
AFTER you have downloaded it, please let me know if volume issues still persist, it's been back and forth a bit

Sorry I noticed something else
So for one the proximity sensor still doesn't work and the display doesn't turn off while on the phone and just stays on when the phone is at your ear.
What also does not work is the interactivity display.
My settings are set to: Wave On, Pick Up On and Pocket On.
however nothing happens so I guess the sensor is not working because the phone just stays dark when in standby.

new build is up, quite a lot of changes. proximity sensor works fine for me, in call and also during inactivity display. unless i make some progress on my "internal" goals, this will be the one to get for some time, as it works for everything i need it to.

Great respect good work thank you it runs as far as I can tell now everything.

Good work for this old Phone!! And we have nothing to pay...! One Question ist there an Option to customize the Navbar (center Clock, change Battery Icon, etc.)? I can't find anything.

[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