{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 13, 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 our Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Whats working?
Wi-Fi
RIL
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
FM radio
Fingerprint reader
Face unlock
NFC
Lights
Sound/vibration
Known issues
Nothing yet
You tell usMaintainers:
@MajorP93 and @KakatkarAkshay
Instructions:
https://wiki.lineageos.org/devices/avicii
Downloads:
https://download.lineageos.org/avicii
GPL compliance:
https://github.com/LineageOS/android_kernel_oneplus_sm7250
Report bug:
https://wiki.lineageos.org/how-to/bugreport
LineageOS Nord Telegram Community:
https://t.me/lineageos_nord
Donate:
Like our work? You can support us by donating:
MajorP93: https://paypal.me/MajorP93
KakatkarAkshay: UPI: [email protected]
A big congratulations on going official!
Does this mean the LineageOS + microG version is not far behind and will appear on https://download.lineage.microg.org/ soon?
I don't understand much about it, only that the build process is automated.
JustH3reToComm3nt said:
A big congratulations on going official!
Does this mean the LineageOS + microG version is not far behind and will appear on https://download.lineage.microg.org/ soon?
I don't understand much about it, only that the build process is automated.
Click to expand...
Click to collapse
Yes, should appear there soon.
MajorP93 said:
Yes, should appear there soon.
Click to expand...
Click to collapse
Thank you for the response and the hard work!
Your hard work is much appreciated @MajorP93 !
I am attempting to do a typical LineageOS upgrade from the Official 17.1 to Official 20.0, however I get the following error message: "E: Package is for product Nord but expected OnePlusNord". Any thoughts on how to resolve? Thank you in advance
NetHistorian said:
Your hard work is much appreciated @MajorP93 !
I am attempting to do a typical LineageOS upgrade from the Official 17.1 to Official 20.0, however I get the following error message: "E: Package is for product Nord but expected OnePlusNord". Any thoughts on how to resolve? Thank you in advance
Click to expand...
Click to collapse
Please refer to the official setup instructions:
Install LineageOS on avicii | LineageOS Wiki
wiki.lineageos.org
As stated there it is required to be on latest Android 12 firmware before installing LineageOS 20.
Since you are currently running LineageOS 17.1 it will be required to install OxygenOS 12 first and install LineageOS 20 afterwards.
For reverting to OxygenOS 12 I recommend using MSM tool.
MSM tool will bring you to OxygenOS 10. Install all OTA updates until you are on latest OxygenOS 12.
MajorP93 said:
Please refer to the official setup instructions:
Install LineageOS on avicii | LineageOS Wiki
wiki.lineageos.org
As stated there it is required to be on latest Android 12 firmware before installing LineageOS 20.
Since you are currently running LineageOS 17.1 it will be required to install OxygenOS 12 first and install LineageOS 20 afterwards.
For reverting to OxygenOS 12 I recommend using MSM tool.
MSM tool will bring you to OxygenOS 10. Install all OTA updates until you are on latest OxygenOS 12.
Click to expand...
Click to collapse
Whoops! I overenthusiastically jumped straight to the "Upgrade to a higher version" section and missed that completely!
It looks like the MSM tool only works for Windows, so I shall follow this guide when I get a chance and report back the results (in case anyone else on Linux/Mac wishes to attemp the same).
Thanks again!
NetHistorian said:
Whoops! I overenthusiastically jumped straight to the "Upgrade to a higher version" section and missed that completely!
It looks like the MSM tool only works for Windows, so I shall follow this guide when I get a chance and report back the results (in case anyone else on Linux/Mac wishes to attemp the same).
Thanks again!
Click to expand...
Click to collapse
You can also join our Telegram group if you want.
Multiple Linux users got it working by using another method.
For now I will copy the steps from the Telegram group into this post:
Flash OOS12 via fastboot (without MSM tool)
Please note: this is an experimental method, using MSM tool is still the preferred method!
- Download full OOS12 ROM zip from here: Link (https://forum.xda-developers.com/t/oneplus-nord-rom-ota-oxygen-os-repo-of-oxygen-os-builds.4138085/) (Signed flashable zips —> select region —> download latest AC2003_11_F.X)
- Extract ZIP
- Extract payload.bin using payload dumper
- Place all extracted files in a new folder
- Download super_empty.img, flash.bat and flash.sh from here (Link (https://www.androidfilehost.com/?fid=4279422670115720730)), extract and place them in the same folder as extracted payload files
- Put phone into bootloader mode
- Type "fastboot reboot fastboot" and press enter
- Execute flash.bat (Windows) or flash.sh (Linux / MacOS) in command prompt
- Wait until done, OOS12 should be installed now
Click to expand...
Click to collapse
If those steps do not work for you I recommend using a Windows VM (virtual machine) with USB passthrough for running MSM tool.
MajorP93 said:
You can also join our Telegram group if you want.
Multiple Linux users got it working by using another method.
For now I will copy the steps from the Telegram group into this post:
If those steps do not work for you I recommend using a Windows VM (virtual machine) with USB passthrough for running MSM tool.
Click to expand...
Click to collapse
Just joined
That's brilliant! Looks a whole lot simpler. Thanks for the extra help!
Does this support 48mp camera? Or we would end up with 24 or 12 mp? Thanks for answering
Rhasta42067 said:
Does this support 48mp camera? Or we would end up with 24 or 12 mp? Thanks for answering
Click to expand...
Click to collapse
The 48 MP are only marketing, 2x2 pixels of the sensor are always combined into one output pixel, so you always "only" get 12 MP on the Sony IMX586.
Quotation from the Sony page: "... The new sensor uses the Quad Bayer color filter array, where adjacent 2x2 pixels come in the same color, making high-sensitivity shooting possible. During low light shooting, the signals from the four adjacent pixels are added, raising the sensitivity to a level equivalent to that of 1.6 μm pixels (12 megapixels), resulting in bright, low noise images. ..."
Doc Sniper said:
The 48 MP are only marketing, 2x2 pixels of the sensor are always combined into one output pixel, so you always "only" get 12 MP on the Sony IMX586.
Quotation from the Sony page: "... The new sensor uses the Quad Bayer color filter array, where adjacent 2x2 pixels come in the same color, making high-sensitivity shooting possible. During low light shooting, the signals from the four adjacent pixels are added, raising the sensitivity to a level equivalent to that of 1.6 μm pixels (12 megapixels), resulting in bright, low noise images. ..."
Click to expand...
Click to collapse
It's not marketing. With the official camera app you can get 48MP output from the sensor. It's pretty useful for cropping since the phone doesn't have a zoom lens but it's only good in well lit situations. Personally I've only used it a few times since I prefer GCam which doesn't support 48MP output.
mythos_ said:
It's not marketing. With the official camera app you can get 48MP output from the sensor. It's pretty useful for cropping since the phone doesn't have a zoom lens but it's only good in well lit situations. Personally I've only used it a few times since I prefer GCam which doesn't support 48MP output.
Click to expand...
Click to collapse
Maybe that's true what you say, but the original questioner asked if this ROM supports 48 MP and the answer will be rather no.
Can someone try Android Auto? I'm having problems with the build here. It's more about the USB procedure, so it hangs and then closes.
Doc Sniper said:
Doc Sniper said:
Maybe that's true what you say, but the original questioner asked if this ROM supports 48 MP and the answer will be rather no.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
It is true. No mabys about it.
Also your answer was:
Doc Sniper said:
The 48 MP are only marketing, 2x2 pixels of the sensor are always combined into one output pixel, so you always "only" get 12 MP on the Sony IMX586.
Click to expand...
Click to collapse
This is simply false. The sensor fully supports 48MP output. The camera included in this ROM (or possibly the OS itself) simply doesn't support this function.
mythos_ said:
It is true. No mabys about it.
Also your answer was:
This is simply false. The sensor fully supports 48MP output. The camera included in this ROM (or possibly the OS itself) simply doesn't support this function.
Click to expand...
Click to collapse
By the way: this is the case on all custom ROMs for the OnePlus Nord.
OnePlus does not offer an API for developers to make use of the full 48MP.
For custom ROMs we kinda have to live with this "limitation".
In my opinion when using GCam or Aperture the image quality is still very good.
Colors are even more natural compared to OnePlus camera app due to improved image processing.
MajorP93 said:
By the way: this is the case on all custom ROMs for the OnePlus Nord.
OnePlus does not offer an API for developers to make use of the full 48MP.
For custom ROMs we kinda have to live with this "limitation".
Click to expand...
Click to collapse
Yeah I know. I actually read up a bit on the camera when I bought the phone. I was looking for a way to get data from the depth sensor. It's the same situation with that unfortunately. No way to use it outside the official camera (which itself barely ever uses it).
MajorP93 said:
In my opinion when using GCam or Aperture the image quality is still very good.
Colors are even more natural compared to OnePlus camera app due to improved image processing.
Click to expand...
Click to collapse
GCam is way better than the stock camera. The post processing it does (with the right profiles) gives much more realistic results than the too-much-HDR look of the official camera. Also in low light situations it's miles ahead. I wish it could support 48MP just for cropping due to lack of zoom but overall GCam is the clear winner.
Hello, just flashed the latest nightly seems you can't flash Gapps just after the Lineage flash (like said in the tutorial) because he think that the phone is still in Android 12 (because coming from official latest build) so I needed one boot to change the SDK version but :
The Gapps doesn't have internet (but the others apps got it since i'm writing this from the phone)
EDIT : I found a solution (I already had this problem and had forgotten since it was like 10y ago), just factory reset the phone (through the settings not a full recovery reset) to have again the initial configuration of Google which allows to accept the conditions of use (otherwise the applications are blocked)
I will daily this to test it, for now everything seems perfect, I just got 1 weird Bluetooth disconnect
Any advice for the Camera app (AOSP/Lineage one seems very basic), I use the latest GCam Nord compatible right now but I guess no one worked on a Android 13 one or just an newer
So, I was running LineageOS17 and followed the instructions with installing the new firmware before upgrading to 20. I must have screwed up somewhere along the way as I got stuck in the bootloader and found no other way out than to start over and follow the instructions; use the MSM4 tool to install OOS10, upgrade to 12 and then wipe and install LineageOS20.
So far so good. Everything seems to be working as it's supposed to. Until I finalized setting up the phone; for some reason it refuses to locate my Ikea Dirigera hub and two Heos units (2x Denon AVR). It worked perfectly before I started upgrading my phone. I tested with my work phone which has never been on the network previously and it found all 3 units immediately without an issue.
I'm confused. I am considering starting over (again) to see if it'll work with OOS12 installed, but it'll feel like a waste of time if it doesn't change anything.
Is there some fancy WLAN setting I might have missed on LineageOS20? Or should I try to manually install the WLAN firmware (modem.img?) again - and in which case which specific file/version should I use?
Ridou said:
Hello, just flashed the latest nightly seems you can't flash Gapps just after the Lineage flash (like said in the tutorial) because he think that the phone is still in Android 12 (because coming from official latest build) so I needed one boot to change the SDK version but :
The Gapps doesn't have internet (but the others apps got it since i'm writing this from the phone)
EDIT : I found a solution (I already had this problem and had forgotten since it was like 10y ago), just factory reset the phone (through the settings not a full recovery reset) to have again the initial configuration of Google which allows to accept the conditions of use (otherwise the applications are blocked)
I will daily this to test it, for now everything seems perfect, I just got 1 weird Bluetooth disconnect
Any advice for the Camera app (AOSP/Lineage one seems very basic), I use the latest GCam Nord compatible right now but I guess no one worked on a Android 13 one or just an newer
Click to expand...
Click to collapse
You encountered that issue because you did not reboot to recovery prior to installing Gapps.
Maybe you looked into the wrong tutorial, it's mentioned in the correct one here:
https://wiki.lineageos.org/devices/avicii/install --> "Installing Add-Ons"
Regarding camera app: I can recommend GCam. You can find a compatible version in our Telegram group.
Related
WELCOME TO THE SNAPPATCH[ Featured by DroidViews and XDA ]
{
"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"
}
SOME THINGS ARE DIFFERENT TO THE AOSP SNAPPATCH
PLEASE MAKE SURE YOU ARE USING THE RIGHT VERSION FOR YOUR DEVICE / ANDROID OS VERSION AND VARIANT
ABOUT THE PROJECTStarted on the Nexus 6, Years ago is the Patch the Result of evolving custom ROMs to something more. Instead of uploading My Changes combined with a OS, is the POM just delivering the wanted Edits. It can be applied on top of any OS, and makes Android Updates independently from My Work. The latest and already 5th Revision of the POM is called Snappatch, and made for Snapdragon Xperia Devices running the very latest AOSP Systems. Coming with a huge amount of exclusive Configs and Optimizations is the Patch unleashing Your Device on a unexpected Way. You will raise the Performance, Efficiency, and Quality of the whole System, besides adding Features and Services which are not available on unpatched AOSP ROMs. The POM comes also with a Rooting Solution, Busybox and the full set of needed GApps to provide a great Pixel like Experience with the barely minimum of needed Apps out of the Box. Based on 8 Years of research and testing, made with Passion! The Snappatch sets Quality over Quantity...
Already adapted by Others for Stock Firmwares is the Snappatch still the first and Original Patch System. You will face it all over XDA in the next Years! Be Part of the Patch Revolution, get Patched!
FEATURES
Xperia DRM Fix and Kernels included
Xperia Apps cleaned out and replaced
Night Light and Ambient Display Settings
Latest Busybox with 400+ Applets (Excluded on Stock)
Magisk Stable Root included
SafetyNet Passing Changes
Pixel Bootanimation / Apps
Xperia and Pixel UI Sounds
Added advanced VR Capabilities
Added Features and Services
Optimized Google Apps Set
Optimized Camera Handling
Optimized Display Handling
Optimized Rendering Handling
Optimized Storage Handling
Optimized Services Handling
Optimized Multitasking Handling
Optimized Audio Handling
Optimized Microphone Handling
Optimized 4K & HDR Handling
Optimized Hardware Handling
Optimized Software Handling
(Features are summarized to keep the overview)
(Don't trust Lists, try it out by Yourself)
SUMMARY OF THE DEVELOPMENT
-Camera Configs can be still improved (Implented not all Configs right yet)
-Some Camera Apps may not Work. Recommended are:
--Snap Camera HDR (Play Store)
--Open Camera (Included / Play Store)
--Google Camera Mods (Some are working, others don't)
-Some Equalizers don't Process (Audio is routed different)
SUPPORTED AOSP DEVICES (BLUE, EXCEPT NILE DEVICES)
Possible that the AOSP Patch works also on other Snapdragon Devices. Use at Your own Risk!
SPECIAL THANKS TO
@D daydream for buying Me the Daydream View 2017! No VR Development with You!
XDA:DevDB Information
SNAPPATCH, ROM for the Sony Xperia XZ Premium
Contributors
Miustone, Miustone, Miustone, Miustone
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
ROM Firmware Required: ANDROID 8.0 / SDK 26
Version Information
Status: Snapshot
Current Stable Version: 101
Stable Release Date: 2018-04-27
Created 2018-04-27
Last Updated 2018-05-20
Fundamental:
Feedback:
-Which Device are You using?
-Which Patch Version are You using?
-Which Android Version are You using?
Before posting:
-Read, read, read! Make sure You've seen the whole Thread
-Make sure You've followed the Instructions from Post 3
-Make sure You're using the right Patch for Your OS (STOCK / AOSP)
-Make sure You've not used other Mods which could cause Bugs
Infos:
Instructions:
-Download the XperiFirm Tool to Your PC
-Download the NewFlasher Tool to Your PC
-Download Minimal ADB & Fastboot to Your PC
-Download the latest Firmware for Your Device Model
-Place the NewFlasher Tool Files in the Firmware Folder
-Connect Your Device to the USB Cable while holding Volume- (Down)(Green LED)
-Start NewFlasher with Admin Rights (Will not work otherwise)
-Press "n" and Enter (do that twice)
-Flashing should now be done after some Minutes
-Detach the USB Cable
-Connect Your Device to the USB Cable again while holding Volume+ (Up)(Blue LED)
-Go to Your fastboot Location and place the latest TWRP Image in it (from: twrp.me)
-Start Fastboot/ADB and type "fastboot flash recovery nameofyourrecovery.img" without the " Symbols
-Detach the USB Cable
-Done! You can now use Your Device like You want!
-Flash ROMs, Mods and/or the SNAP PATCH. Your Device is now fully upgraded!
Download:
Snappatch Website
Please consider a Donation if You like My Work! [PayPal.Me] [Gift Code]
Just to let everyone know, i will still share My Work with You. But i'm not going to Post anymore on XDA, based on the latest Ban of My Account. If You want My Support please look around for the right Links on My Website! Feel free to use the Thread to talk with Others, and i will also check out what happens on My Threads. But if You want to talk to Me please use the Social Media Way! Thanks to all Supporters and Users in Advance!
This looks great!
I have the 7.1 Yoshino kernel AOSP so I can have the Dynamic Resolution Switch and enjoy native 4K.
I also have Daydream enabled and installed the normal hack way,but it's a bit jittery for head tracking compared to my Axon 7.
Can someone tell me if this will work with 7.1, or if I'll still be able to enjoy true 4K with an 8.1 ROM and this patch? The VR services sound good, along with everything else. Otherwise, I guess I'll just keep waiting for @kholk to finish setting up the DRS on 8.1.
Miustone said:
Just to let everyone know, i will still share My Work with You. But i'm not going to Post anymore on XDA, based on the latest Ban of My Account. If You want My Support please look around for the right Links on My Website! Feel free to use the Thread to talk with Others, and i will also check out what happens on My Threads. But if You want to talk to Me please use the Social Media Way! Thanks to all Supporters and Users in Advance!
Click to expand...
Click to collapse
Dis tout have twitter or Instagram i will use it for tell you any problem or dix that i find thanks for your work
gaijin1% said:
This looks great!
I have the 7.1 Yoshino kernel AOSP so I can have the Dynamic Resolution Switch and enjoy native 4K.
I also have Daydream enabled and installed the normal hack way,but it's a bit jittery for head tracking compared to my Axon 7.
Can someone tell me if this will work with 7.1, or if I'll still be able to enjoy true 4K with an 8.1 ROM and this patch? The VR services sound good, along with everything else. Otherwise, I guess I'll just keep waiting for @kholk to finish setting up the DRS on 8.1.
Click to expand...
Click to collapse
You have the switch working?? Damn is it better than the adb mod??
gaijin1% said:
This looks great!
I have the 7.1 Yoshino kernel AOSP so I can have the Dynamic Resolution Switch and enjoy native 4K.
I also have Daydream enabled and installed the normal hack way,but it's a bit jittery for head tracking compared to my Axon 7.
Can someone tell me if this will work with 7.1, or if I'll still be able to enjoy true 4K with an 8.1 ROM and this patch? The VR services sound good, along with everything else. Otherwise, I guess I'll just keep waiting for @kholk to finish setting up the DRS on 8.1.
Click to expand...
Click to collapse
Did you try this?
It'll be native 4k and AOSP 8.1 but you'd be stuck with it (can't switch to 1080p) which I don't see as problem. Also bootanimation will go weird, but after display off and on once boot is finished everything is fine.
madshark2009 said:
You have the switch working?? Damn is it better than the adb mod??
Click to expand...
Click to collapse
Yes! the switch is native and adb is emulated, which means resized images usually from the lower resolution xxhdpi folders rather than the higher resolution xxxhdpi folders.
---------- Post added at 01:11 PM ---------- Previous post was at 01:06 PM ----------
super_extreme said:
Did you try this?
It'll be native 4k and AOSP 8.1 but you'd be stuck with it (can't switch to 1080p) which I don't see as problem. Also bootanimation will go weird, but after display off and on once boot is finished everything is fine.
Click to expand...
Click to collapse
Can't believe I missed that one. I guess now the question is which one to go for? Is this STOCK version also native 4K full time like the AOSP version?
can any body tell me where is Downloadlink?
gaijin1% said:
Yes! the switch is native and adb is emulated, which means resized images usually from the lower resolution xxhdpi folders rather than the higher resolution xxxhdpi folders.
---------- Post added at 01:11 PM ---------- Previous post was at 01:06 PM ----------
Can't believe I missed that one. I guess now the question is which one to go for? Is this STOCK version also native 4K full time like the AOSP version?
Click to expand...
Click to collapse
It has nothing to do with the patch but with the kernel. I simply built a rom that works great with the Snappatch AOSP version, not the other way round. [emoji3]
And no native 4k always with stock. I really prefer AOSP. It's just slimmer, greater and quite debloated from the beginning.
gaijin1% said:
Yes! the switch is native and adb is emulated, which means resized images usually from the lower resolution xxhdpi folders rather than the higher resolution xxxhdpi folders.
---------- Post added at 01:11 PM ---------- Previous post was at 01:06 PM ----------
Can't believe I missed that one. I guess now the question is which one to go for? Is this STOCK version also native 4K full time like the AOSP version?
Click to expand...
Click to collapse
So if you got the switch working, do the screen pixels look more glued? Cuz here i can still see pixels on the adb commands
And is 120hz working yet?
madshark2009 said:
So if you got the switch working, do the screen pixels look more glued? Cuz here i can still see pixels on the adb commands
And is 120hz working yet?
Click to expand...
Click to collapse
I don't know what you mean by glued, but with my Daydream headset and 20/20 vision the pixels seem like a horizontal wavy zig-zag.
Basically, the emulated adb will enlarge an image from 1080 and give you a 4-block of the same pixel. Worse, if the image is actually for example 1440p, it will first scale it down to 1080 blurring it a bit, then take the blurred image and resize it to 2160p.
gaijin1% said:
I don't know what you mean by glued, but with my Daydream headset and 20/20 vision the pixels seem like a horizontal wavy zig-zag.
Basically, the emulated adb will enlarge an image from 1080 and give you a 4-block of the same pixel. Worse, if the image is actually for example 1440p, it will first scale it down to 1080 blurring it a bit, then take the blurred image and resize it to 2160p.
Click to expand...
Click to collapse
And 120hz option does it work?
madshark2009 said:
And 120hz option does it work?
Click to expand...
Click to collapse
I don't think it's works
Cant I flash twrp on locked bootloader??
I mean we are working with stock fw and a patch flashed in twrp,no kernel modification. All stock...
madshark2009 said:
Cant I flash twrp on locked bootloader??
I mean we are working with stock fw and a patch flashed in twrp,no kernel modification. All stock...
Click to expand...
Click to collapse
The Kernel is edited and patched with Magisk. No chance that it works on Locked Bootloaders (Before unlocking them). But You can maybe lock it after flashing to hide the 5Sec Message after turning the Device on.
Just use "fastboot oem lock" and "fastboot oem unlock" commands. Don't recommend it and i don't try it out by myself, but maybe does it work. Would be good to know since Stock is passing SafetyNet (Device thinks it is unmodified)
Btw. @super_extreme nice work with AOSP! Are Your Builds passing SafetyNet too with the AOSP Patch? Carbon doesn't but that also the case without Patching...
(Damn i'm breaking My promised silence on XDA! Can't resist to talk to My Users
Miustone said:
The Kernel is edited and patched with Magisk. No chance that it works on Locked Bootloaders (Before unlocking them). But You can maybe lock it after flashing to hide the 5Sec Message after turning the Device on.
Just use "fastboot oem lock" and "fastboot oem unlock" commands. Don't recommend it and i don't try it out by myself, but maybe does it work. Would be good to know since Stock is passing SafetyNet (Device thinks it is unmodified)
Btw. @super_extreme nice work with AOSP! Are Your Builds passing SafetyNet too with the AOSP Patch? Carbon doesn't but that also the case without Patching...
(Damn i'm breaking My promised silence on XDA! Can't resist to talk to My Users
Click to expand...
Click to collapse
So with saftey net the device thinks its unmodified, why would it be a problem?
Google play services crashed during set-up and only blackscreen, no way to finish set-up.
Followed installation instructions to the teeth:
-flashed stock .145 BLX
-let it boot to set-up
-completely shut down
-flash twrp in fastboot mode
-boot to twrp
-format data and internal storage (encryption error)
-reboot to recovery and wiped everything again (no encryption error)
-again completely power off
-reboot
Uh-oh no more OS... better start again ?
-flashed stock .145 BLX again
-boot to set-up
-completely shut down
-flash twrp in fastboot
-boot to twrp
-now only wiped systeem, cache, data
-reboot to twrp again
-moved snappatch and snapprop to root of internal storage with adb
-flashed snappatch_v101 stock
-reboot
After this the set-up wouldnt let me pass because of the Google play services crash. This crash happend after entering the Wifi-password. There was only a blackscreen and i could see the clock and battery in the upper right corner.
Tried flashing Opengapps micro afterwards butt stil no luck.
Edit: removed my earlier expression of the Rom, isn't helpful or related to this thread
Miustone said:
The Kernel is edited and patched with Magisk. No chance that it works on Locked Bootloaders (Before unlocking them). But You can maybe lock it after flashing to hide the 5Sec Message after turning the Device on.
Just use "fastboot oem lock" and "fastboot oem unlock" commands. Don't recommend it and i don't try it out by myself, but maybe does it work. Would be good to know since Stock is passing SafetyNet (Device thinks it is unmodified)
Btw. @super_extreme nice work with AOSP! Are Your Builds passing SafetyNet too with the AOSP Patch? Carbon doesn't but that also the case without Patching...
(Damn i'm breaking My promised silence on XDA! Can't resist to talk to My Users
Click to expand...
Click to collapse
Nope, it's not, but luckily I don't need it to be.
{
"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:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/10.0/README.mkdn
Flashing Instructions:
First time installation:
1. Disable AVB with fastboot (fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img)
2. Flash PBRP with fastboot (fastboot flash recovery recovery.img)
3. Reboot to Recovery
4. Wipe Data/Cache
5. Flash the ROM (Could need to unmount system before if it's mounted), then flash GAPPS
6. Format data
7. Reboot to System
Update installation:
1. Download the proper flashable ZIP for your device
2. Reboot to Recovery
3. Flash the ROM and GAPPS
4. Reboot to System
Sources:
ROM: https://github.com/crdroidandroid
Kernel: Prebuilt Kernel from A.83
Device: Click Here
Download:
ROM https://sourceforge.net/projects/cr...ndroid-11.0-20210715-RMX2151-v7.8.zip/downloa
Changelog: https://raw.githubusercontent.com/c...DroidOTA/10.0/changelog_<device codename>.txt
Known issues:
* U tell me
Visit official website @ crDroid.net
crDroid RMX2151 Telegram
crDroid Community Telegram
Donate to help our team pay server costs
TheCloverly said:
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/10.0/README.mkdn
Flashing Instructions:
First time installation:
1. Disable AVB with fastboot (fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img)
2. Flash PBRP with fastboot (fastboot flash recovery recovery.img)
3. Reboot to Recovery
4. Wipe Data/Cache
5. Flash the ROM (Could need to unmount system before if it's mounted), then flash GAPPS
6. Format data
7. Reboot to System
Update installation:
1. Download the proper flashable ZIP for your device
2. Reboot to Recovery
3. Flash the ROM and GAPPS
4. Reboot to System
Sources:
ROM: https://github.com/crdroidandroid
Kernel: Prebuilt Kernel from A.83
Device: Click Here
Download:
ROM https://sourceforge.net/projects/cr...ndroid-11.0-20210715-RMX2151-v7.8.zip/downloa
Changelog: https://raw.githubusercontent.com/c...DroidOTA/10.0/changelog_<device codename>.txt
Known issues:
* U tell me
Visit official website @ crDroid.net
crDroid RMX2151 Telegram
crDroid Community Telegram
Donate to help our team pay server costs
Click to expand...
Click to collapse
I was wondering if someone was ever going to upload 7.8. Thanks a lot; your work is very much appreciated. I'm looking forward to trying this out soon.
OrthodoxOxygen said:
I was wondering if someone was ever going to upload 7.8. Thanks a lot; your work is very much appreciated. I'm looking forward to trying this out soon.
Click to expand...
Click to collapse
Thankyou and welcome
realme part not working. The screen refresh rate does not change. 60-90hz screen refresh location not working
coskun19876 said:
realme part not working. The screen refresh rate does not change. 60-90hz screen refresh location not working
Click to expand...
Click to collapse
Unfortunately wifi and Bluetooth gets break if you flash from A.91 or newer version, same will be applied for all roms. So better rollback to A.71, A.75 or any lower version than A.89 and flash.
TheCloverly said:
Unfortunately wifi and Bluetooth gets break if you flash from A.91 or newer version, same will be applied for all roms. So better rollback to A.71, A.75 or any lower version than A.89 and flash.
Click to expand...
Click to collapse
What do you think is the best firmware at the moment a71, a75, a87?
coskun19876 said:
What do you think is the best firmware at the moment a71, a75, a87?
Click to expand...
Click to collapse
Probably a.71. The earlier it is, the more cracks it has in its security, in all likelihood. If you mean which is best in terms of features, then you're looking for whatever's the latest firmware.
Thank you, this is my favorite ROM mainly because it is 1 of only 2 for this device that doesn't come prepackaged with GAPPS. All features (including screen record) work fine and am loving it so far.
TheCloverly said:
Unfortunately wifi and Bluetooth gets break if you flash from A.91 or newer version, same will be applied for all roms. So better rollback to A.71, A.75 or any lower version than A.89 and flash.
Click to expand...
Click to collapse
I used the firmware you mentioned. still realme part is not working. The screen only runs at 60hz. I can't refresh the screen to 90hz. Any chance to add 60-90hz setting to your display settings?
coskun19876 said:
I used the firmware you mentioned. still realme part is not working. The screen only runs at 60hz. I can't refresh the screen to 90hz. Any chance to add 60-90hz setting to your display settings?
Click to expand...
Click to collapse
Everything is fine here, please join telegram support group for help.
coskun19876 said:
I used the firmware you mentioned. still realme part is not working. The screen only runs at 60hz. I can't refresh the screen to 90hz. Any chance to add 60-90hz setting to your display settings?
Click to expand...
Click to collapse
Try the ROM from the MEGA link here:
[GUIDE] REALME 7 RMX2155 GLOBAL BOOTLOADER UNLOCK
WELCOME, ALL. After a very tiring process of swapping between ROMs and changing regions, APKs, et cetera, we have finally been able to perfect the method for unlocking the bootloader of the RMX2155! This is a detailed guide aimed to give you an...
forum.xda-developers.com
Should work fine for you from then on.
Hey There,
first of all @TheCloverly I really like your work! You've done great! The first time (out of 4 Phones) crDroid runs that smooth and without any crashes.
I have only one problem. Is there any way to get the wide angle camera to work? I know the cameras on that phone are ****ty, but I would really like to use them netherless.
FreeDCam only finds back 0 and front 1. And it seems that other apps aren't supporting multiple lens.
Thank you!!
Givou said:
Hey There,
first of all @TheCloverly I really like your work! You've done great! The first time (out of 4 Phones) crDroid runs that smooth and without any crashes.
I have only one problem. Is there any way to get the wide angle camera to work? I know the cameras on that phone are ****ty, but I would really like to use them netherless.
FreeDCam only finds back 0 and front 1. And it seems that other apps aren't supporting multiple lens.
Thank you!!
Click to expand...
Click to collapse
Aux wont work in gcam (prolly mess from realme so can't be fixed) ;(
As you might know Realme UI 2.0 rolled out to our devices and we had chances to try it out, and do you guys ever wonder what it does to camera on 3rd party apps? Only and only main lens works. Wide Angle doesn't Macro doesn't Front camera doesn't, but only main sensor works.
Thanks for your reply. So there is actually no chance to get the other sensors to work?? That's really sad :/
Other Problem: Do you Guys have Problems with the crDroid Phone App? My Contacts won't be saved. I import them to the device with an App from my Sim Card. Everything is fine, they there use. But when I restart the phone..all contacts will be lost. :/ Any solution there? Thank!!
Edit: I will try to force install the stock camera App. Will report if that works.
Givou said:
Thanks for your reply. So there is actually no chance to get the other sensors to work?? That's really sad :/
Other Problem: Do you Guys have Problems with the crDroid Phone App? My Contacts won't be saved. I import them to the device with an App from my Sim Card. Everything is fine, they there use. But when I restart the phone..all contacts will be lost. :/ Any solution there? Thank!!
Edit: I will try to force install the stock camera App. Will report if that works.
Click to expand...
Click to collapse
We don't have any problem with crDroid Phone App.
you can also join @SriBalajiHub in telegram for quick support.
OK, and completely other question. Is it normal for the phone that the battery temperature goes up to 50 degrees when f.E watching YouTube longer time...?
Givou said:
OK, and completely other question. Is it normal for the phone that the battery temperature goes up to 50 degrees when f.E watching YouTube longer time...?
Click to expand...
Click to collapse
What does "f.E" mean? As for what I understood, no, I have zero heating issues when using 7.8. Did you dirty-flash or update, perhaps?
Givou said:
OK, and completely other question. Is it normal for the phone that the battery temperature goes up to 50 degrees when f.E watching YouTube longer time...?
Click to expand...
Click to collapse
It shouldn't go upto 50° , something is wrong with your handset, please check it.
Unfortunatelly when i try to install a custom rom it says:
"Flashing A/B zip to inactive slot: A
To flash additional zips, please reboot recovery to switch to the updated slot."
But even after a reboot into recovery again it's still the same error. As far as I understand there are nothing like A/B partitions or slots.
Any idea?
darkMamba said:
Unfortunatelly when i try to install a custom rom it says:
"Flashing A/B zip to inactive slot: A
To flash additional zips, please reboot recovery to switch to the updated slot."
But even after a reboot into recovery again it's still the same error. As far as I understand there are nothing like A/B partitions or slots.
Any idea?
Click to expand...
Click to collapse
What is your phone's model number? Also, are you trying to flash multiple .zip files in succession?
{
"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.
Downloads
Here
Flashing instructions
Here
Sources
LineageOS
I was struggling with passing safetynet + cts in particular but in the end this seems to have worked (if anyone is sturggling with this):
- magisk 24 + zygisk + hide magisk app
- denylist: google play services cms + cms.unstable
- universal safetyfix 2.2.1
- hide props: Google Pixel 5 A11
What Magisk modules are working in this ROM?
Guaymas said:
What Magisk modules are working in this ROM?
Click to expand...
Click to collapse
I'm using MagiskHide Props Config, Systemless Hosts and Viper4Android. Magisk 23.
Does the 64 megapixel camera work? ANX bootlooped my LineageOS 17.x unofficial build nomatter what. I've just flashed the latest MIUI to update to Android 11 before flahing this, and it's horrible. Apart from the camera working, which is amazing.
Revelle said:
Does the 64 megapixel camera work? ANX bootlooped my LineageOS 17.x unofficial build nomatter what. I've just flashed the latest MIUI to update to Android 11 before flahing this, and it's horrible. Apart from the camera working, which is amazing.
Click to expand...
Click to collapse
This build didnt support anx, which version you install Will gave bootloop, gcam now eis video work
Media speaker volume is too low
Any fix for that?
Viper4android Magisk module worked for me.
godjob said:
This build didnt support anx, which version you install Will gave bootloop, gcam now eis video work
Click to expand...
Click to collapse
Which gcam has EIS?
Hi there I've got redmi 9s and just successfully installed lineageos 18.1
It's working fine but any messaging app ( for example telegram/ signal) are able to preview and select pictures from the gallery but not send/ attach them to any message.
If sending Files, Contact Cards or even the images as files in uncompressed form, it works, but the Gallery Function seems to have a problem.
It just gives a red error signal but won't Even try to upload pictures although I believe the apps have the necessary permissions ( access to storage)
Any ideas/ suggestions / help on how to approach this bug / where to start the trouble shooting?
I found something that could help me get on the right track to fix this issue, it seems that perhaps it has to do with a new access right scheme in Android 11 (https://developer.android.com/about/versions/11/privacy/storage)
I found some User Messages about this in Bug Reports.
Does somebody have an idea for a workaround, or how to change this in the current lineageOS Version?
Here are some quotes from the Bug Reports, I will provide the links to the threads further below.
Thanks for your help.
P.S.: Just to clarify this problem for me is including the option to send images from the gallery function, to save photos to gallery and to auto-save photos to gallery.
"There's a limit introduced in Android 11 called "Scoped Storage". This is the reason."
"This! This right here is the deal. Telegram is not adjusted for the new access right scheme. It is only allowing media-folders."
"You're right, they just moved "Telegram" folder from root of sdcard to another folder that they have permission to write there but it's not visible to user. I think auto-save option only removes ".nomedia" file from "Telegram" folder so media will be visible in gallery when Telegram is in /sdcard/Telegram, but with scoped storage it's moved to /sdcard/Android/org.telegram.messanger so it won't be visible even without ".nomedia". instead they should save media in /sdcard/Pictures/Telegram when auto-save option is on."
"Attention! Perhaps due to restrictions on Android 11 on access to the "Android - data" folders, media files from Telegram are not saved to the gallery."
"I suspect it relates to the way media-folder access was changed in the newer Android versions (for security reasons)"
[Android 11+/SDK 30+] Auto save to gallery does not work
Despite the fact the 'Save to Gallery' option is enabled in Settings > Chat Settings, still I don't see media in my phone's gallery. Steps to reproduce 1. Enable 'Save to Gallery' in Settings > Chat Settings 2. Open any chat where you see media 3. Check…
bugs.telegram.org
Automatic saving of incoming photos doesn't work
Workaround Disable Automatic Media Download and manually download the images. Automatic saving of incoming photos doesn't work, after the February update (v 7.5) Sometimes random old photo from telegram chat is downloaded to the gallery. Steps to reproduce…
bugs.telegram.org
Manual "Save to gallery" command does not work
Steps to reproduce 1. Open any chat 2. Select a picture or a video, press "..." and choose "Save to gallery". 3. Notyhing is saved to gallery. Device info Telegram Android 8.2.1 (24627), Samsung Galaxy S20 FE 5G, 11 R? (30) Telegram Android 8.2.1 (24627)…
bugs.telegram.org
I was thinking that maybe if I moved the folder or designated it as a media folder, maybe could work? Open for any help and suggestions! Thank You Community!
starseedsawake said:
Hi there I've got redmi 9s and just successfully installed lineageos 18.1
It's working fine but any messaging app ( for example telegram/ signal) are able to preview and select pictures from the gallery but not send/ attach them to any message.
If sending Files, Contact Cards or even the images as files in uncompressed form, it works, but the Gallery Function seems to have a problem.
It just gives a red error signal but won't Even try to upload pictures although I believe the apps have the necessary permissions ( access to storage)
Any ideas/ suggestions / help on how to approach this bug / where to start the trouble shooting?
Click to expand...
Click to collapse
dereference23 said:
Flashing instructions
Click to expand...
Click to collapse
Best camera option for the 64mp note 9 pro (joyeusE)?
I'm thinking gcam port 8.3 for the note 9 pro max?
hmm?
i already did a clean reflash and it didn't fix that problem... assuming that you meant for me to reflash with your reply?
It's a great rom, but battery light brightness level doesn't change when i move the slider. Can you fix that?
starseedsawake said:
hmm?
i already did a clean reflash and it didn't fix that problem... assuming that you meant for me to reflash with your reply?
Click to expand...
Click to collapse
Did you flash from the stated stock ROM version?
starseedsawake said:
hmm?
i already did a clean reflash and it didn't fix that problem... assuming that you meant for me to reflash with your reply?
Click to expand...
Click to collapse
I'm having the exact problem with Telegram app..and also some other Apps are behaving strange.
Please let me know if you found any solution.
I did clean flash, gapps and without gapps, problem is the same. I'm on latest global curtana android 11 firmware (before flashing Lineage OS).
@DyXen @starseedsawake
Just wanting to say that I can post media in messengers like Telegram without issues.
My setup:
- Curtana
- MIUI rom before installing LOS: curtana_global_images_V12.0.4.0.RJWMIXM_20210723.0000.00_11.0_global
- No firmware updates after that
- Latest LineageOS recovery
- Latest LOS
- Magisk
Maybe this rom just doesn't work with the latest firmware? I'd try it out, but it just works too nicely to throw it all away. Maybe give it a try with the MIUI rom from above!
@dereference23
I feel like "rom version that needs to be installed before flashing LOS" is really something that should be part of the lineageos install instructions. It's almost always missing, or vague ("Latest Android 11 firmware" etc.). Every other phone I try to install LineageOS on gives me some kind of trouble that can usually be solved by downgrading the firmware. What MIUI rom where you on before flashing? Can you add that info to the los install page?
But anyways really great work! Absolutely smooth and bug free for me. Thank you.
Last but not least: If anyone got a GCam or ANXCamera version that supports 48MP (or 64MP for those with the better cameras) on this rom let me know! That is literally the only thing I still miss.
I always install latest firmware when upgrading LineageOS and have no problems.
I coudn't find any camera port that worked to even access the different lenses, let alone 64mpx. Note 9 Pro Global, from LineageOS 17.x to joyeuse_global_images_V12.5.3.0.RJZMIXM_20211223.0000.00_11.0_global_adcfb0b103 then this + MindTheGAPPs. Lineage 17.x unofficial worked with OpenCam for me but with no 64mp. Have gone back to MIUI for now just for the camera. Everything else worked perfectly.
Maybe it's because I'm on Joyeuse not Miatoll.
{
"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 Nokia 8 [NB1]
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
Whats working?
Wi-Fi
RIL
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
FM radio
Fingerprint reader
Face unlock
NFC
Lights
Sound/vibration
Known issues
Camera might lag randomly and require a reboot to fix
You tell me
DON'T FLASH GAPPS, THEY'RE ALREADY INCLUDED
Download from PixelExperience website
Donate
Liked my work? Give me a beer
Translation
Help with project translation
Stay tuned
Our Telegram channel
Our blog
Android OS version: 12
Security patch level: May 2022
Build author/Device Maintainer: emufan4568
Device Source code: https://github.com/PixelExperience-Devices/device_nokia_NB1
Source code: https://github.com/PixelExperience
ROM Developer: jhenrique09
July 21st 2022
* Update sources and security patch to July 2022
* Radio and camera fixes
* Kernel rebase and update
* Hotspot 2.0
* No more popup on every boot
emufan4568 said:
PixelExperience for Nokia 8 [NB1]
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
Whats working?
Wi-Fi
RIL
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
FM radio
Fingerprint reader
Face unlock
NFC
Lights
Sound/vibration
Known issues
Camera might lag randomly and require a reboot to fix
You tell me
DON'T FLASH GAPPS, THEY'RE ALREADY INCLUDED
Download from PixelExperience website
Donate
Liked my work? Give me a beer
Translation
Help with project translation
Stay tuned
Our Telegram channel
Our blog
Android OS version: 12
Security patch level: May 2022
Build author/Device Maintainer: emufan4568
Device Source code: https://github.com/PixelExperience-Devices/device_nokia_NB1
Source code: https://github.com/PixelExperience
ROM Developer: jhenrique09
Click to expand...
Click to collapse
Hi there, first of all thanks for providing us stock android custom rom.
Yesterday I flashed pixel experience 12.1 to my Nokia 8 following installation guide, it's pretty good but Note that camera audio not recording properly neither built-in voice recorder is recording sounds.
Kindly guide me what to do?
Hi, I get an error when my nokia-8 (TA-1052) starts up. How can I fix it?
Android System
==========
"There's an internal problem with your device Contact your manufacturer for details"
Hi, I've been a happy user of PixelExperience 11 for several month (first attempt of a non standard Android build for a daily use) and now trying to update to 12.
Can someone confirm that the T-virus 2.0 upgrade is necessary to install this build ? I can't find the answer here or on the intall guide on the PixelExperience website.
jackho2020 said:
Hi, I get an error when my nokia-8 (TA-1052) starts up. How can I fix it?
Android System
==========
"There's an internal problem with your device Contact your manufacturer for details"
Click to expand...
Click to collapse
I have the same message on 11 so its not related to this version. It has never been an issue once the startup is completed for me, since last october. I discarded that as an tiny annoyance for having the guts to unlock the bootloader.
NeuNeuiL said:
Hi, I've been a happy user of PixelExperience 11 for several month (first attempt of a non standard Android build for a daily use) and now trying to update to 12.
Can someone confirm that the T-virus 2.0 upgrade is necessary to install this build ? I can't find the answer here or on the intall guide on the PixelExperience website.
Click to expand...
Click to collapse
T-Virus 2.0 is not necessary. I installed PixelExperience_NB1-12.1-20220528-2114-OFFICIAL.zip on t-virus-20201108.qlz.
CuteAndroid said:
T-Virus 2.0 is not necessary. I installed PixelExperience_NB1-12.1-20220528-2114-OFFICIAL.zip on t-virus-20201108.qlz.
Click to expand...
Click to collapse
Thanks, that's one step less to do
And which recovery did you use ? I currently have TWRP 3.5.2 on the device but saw a newer 3.6.2 version is available.
Thanks, that's one step less to do
And which recovery did you use ? I currently have TWRP 3.5.2 on the device but saw a newer 3.6.2 version is available.
Click to expand...
Click to collapse
I flashed the PixelExperience recovey PixelExperience_NB1-12.1-20220528-2114-OFFICIAL.img with TWRP 3.4.0-0 from t-virus-20201108.qlz to the Boot partition (I hope I remeber correctly but should be "Boot"). Then install PixelExperience_NB1-12.1-20220528-2114-OFFICIAL.zip with the PixelExperience recovey.
CuteAndroid said:
I flashed the PixelExperience recovey PixelExperience_NB1-12.1-20220528-2114-OFFICIAL.img with TWRP 3.4.0-0 from t-virus-20201108.qlz to the Boot partition (I hope I remeber correctly but should be "Boot"). Then install PixelExperience_NB1-12.1-20220528-2114-OFFICIAL.zip with the PixelExperience recovey.
Click to expand...
Click to collapse
Well, thanks to your message I managed to skip another step
Since a recovery was always included with the rom I formerly flashed on my devices, I just flashed this one from TWRP 3.5.2 and it worked (also wiped internal, data and cache from TWRP to be sure).
Hoccane said:
Hi there, first of all thanks for providing us stock android custom rom.
Yesterday I flashed pixel experience 12.1 to my Nokia 8 following installation guide, it's pretty good but Note that camera audio not recording properly neither built-in voice recorder is recording sounds.
Kindly guide me what to do?
Click to expand...
Click to collapse
No sound problem with the camera audio for me,. Regarding the built-in voice recorder, I had to select manually the correct device to use in the app parameter to make it work.
I have two complains about the camera app though. It is a bit slow and contrary to the one included on PE 11, I cannot select the storage, and thus my SD card, on this one. Except this, it seems to work pretty well.
I'll test the GPS and other stuff tomorrow and keep you updated.
Thanks for the great work on this rom @emufan4568
Edit 27/06/2022 :
Tested GPS, mobile data and calls today. General performance and battery drain were on par with PE11, very good.
Mobile data was stuck on HSDPA so I went to mobile data parameters to set it to "Global" instead of "GSM/WCDMA" to unlock LTE-A.
Is this camera lag also present when using GCam?
xabr3 said:
Is this camera lag also present when using GCam?
Click to expand...
Click to collapse
Right now, all NB1 ROMs are experiencing this issue unfortunately. But PE (I think) is the most stable one.
As a temporary solution, you can take pictures using Adobe Lightroom (works for me on CrDroid).
Ok, hopefully this will be fixed asap.
I'm using the camera app built-in the rom. I guess it's GCam.
With 3 more weeks of daily use I can complete my previous statement. The lag is not the main problem on my device as it only happens after a reboot. It's that the device stops saving pictures while displaying the shutter effect and all. If you don't shutdown your phone at night, you'll have to reboot it before you can take a picture. If you have to take several pictures, you'll have to reboot each 3 to 4 shots.
I'm installing Adobe Lightroom right now
I hope this will be fixed soon because this rom looks promising.
Last custom rom was on my Moto X 2nd gen but there was always something wrong.
Waiting for this lag to be fixed.
I forgot to ask but does Netflix and Google Pay work?
xabr3 said:
I hope this will be fixed soon because this rom looks promising.
Last custom rom was on my Moto X 2nd gen but there was always something wrong.
Waiting for this lag to be fixed.
Click to expand...
Click to collapse
Newest update contains many camera related fixes. I'm not sure if it's completely fixed but from my testing the camera should be a lot more stable.
xabr3 said:
I forgot to ask but does Netflix and Google Pay work?
Click to expand...
Click to collapse
Google Pay I can confirm works just fine, I use it for transactions. Netflix I think does too, but has limited quality due to lack of widevine l1 (it gets lost when unlocking the bootloader on 90% of devices).
NeuNeuiL said:
I'm using the camera app built-in the rom. I guess it's GCam.
With 3 more weeks of daily use I can complete my previous statement. The lag is not the main problem on my device as it only happens after a reboot. It's that the device stops saving pictures while displaying the shutter effect and all. If you don't shutdown your phone at night, you'll have to reboot it before you can take a picture. If you have to take several pictures, you'll have to reboot each 3 to 4 shots.
I'm installing Adobe Lightroom right now
Click to expand...
Click to collapse
This bug should be fixed now, or at least that what my testers reported. Please install the current OTA and test as well
emufan4568 said:
Google Pay I can confirm works just fine, I use it for transactions. Netflix I think does too, but has limited quality due to lack of widevine l1 (it gets lost when unlocking the bootloader on 90% of devices).
Click to expand...
Click to collapse
Thank you for answering. Nice that Gpay works. About Netflix, what does this mean, i don't need 4K quality but 720p streams would be nice.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 13 (T), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Downloads
Here
Flashing instructions
Here
Upgrade instructions
Here
Sources:
- LineageOS
- Kernel Tree
Happy modding!
Reserved
Okay but does it run Crysis?
I've been running it and everything seems to work ok
Links provided by you are loopy and I don't seem to find any link to the "firmware.zip" you have mentioned in your website. Please write some more details. I'm very excited to flash it
Edit: Found everything.
Hey @Its_Vixano,
Thank you for this release in the first place, I'm really happy with it. Seems to be stable so far after the few days I've been running it.
I have only noticed some minor UX bugs with the recents(/gestures) while using Trebuchet (I haven't experienced it yet after switching to Lawnchair), but a more important issue is that I cannot play audio on a Bluetooth device.
I tested it with several devices, they show up as connected, but they remain silent even on maximum volume.
My guess (from the logs and my experience) is that for some reason the bluetooth audio connection cannot be built up correctly, it seems like it gets interrupted every second or so.
Other than that, do you know if the camera quality is better with the stock MIUI camera app? If yes, maybe it would also be worth to include it in this ROM as well, since others are starting to include it, I figured it wouldn't be too much of a hassle.
I only meant these as suggestions/observations, if you need more information on the bug, please let me know.
Thanks in advance.
ardrift said:
but a more important issue is that I cannot play audio on a Bluetooth device.
I tested it with several devices, they show up as connected, but they remain silent even on maximum volume.
My guess (from the logs and my experience) is that for some reason the bluetooth audio connection cannot be built up correctly, it seems like it gets interrupted every second or so.
Click to expand...
Click to collapse
Are you sure is not caused by any system modification or modules flashed via magisk ??
I use everyday a bluetooth pair (AAC, Samsung buds live) without any issues
Its_Vixano said:
Are you sure is not caused by any system modification or modules flashed via magisk ??
I use everyday a bluetooth pair (AAC, Samsung buds live) without any issues
Click to expand...
Click to collapse
Thanks for the hint, I tried rebooting to safe mode so that all the 3rd party apps get disabled, and also disabled some system modifications manually (tasker, dev options), but these didn't help unfortunately :/
But now that you mentioned it's working for you, I thought that the reason might be that I flashed your ROM to the V13.0.9.0.SKOEUXM firmware I had installed previously. I will re-test with the V13.0.4.0.SKOMIXM firmware that you recommend in your guide as well, I'll get back with the results.
P.S: I have attached the installed modules list and the error logs.
ardrift said:
Thanks for the hint, I tried rebooting to safe mode so that all the 3rd party apps get disabled, and also disabled some system modifications manually (tasker, dev options), but these didn't help unfortunately :/
But now that you mentioned it's working for you, I thought that the reason might be that I flashed your ROM to the V13.0.9.0.SKOEUXM firmware I had installed previously. I will re-test with the V13.0.4.0.SKOMIXM firmware that you recommend in your guide as well, I'll get back with the results.
P.S: I have attached the installed modules list and the error logs.
Click to expand...
Click to collapse
Can you try reflashing the fw i mentioned ??
Its_Vixano said:
Can you try reflashing the fw i mentioned ??
Click to expand...
Click to collapse
I flashed it now and it fixed the problem, thanks for confirming that it was working for you.
Thank you for sharing this. I have a few questions. Is there a touch head option in fingerprint? Do banking apps give root warning? Camera app snap? Do you have any gcam you recommend or can we install miui camera?
Just pushed august ota
enjoy
by_BenjamiN said:
Thank you for sharing this. I have a few questions. Is there a touch head option in fingerprint? Do banking apps give root warning? Camera app snap? Do you have any gcam you recommend or can we install miui camera?
Click to expand...
Click to collapse
The least i can do for banking apps is to include ih8sn on my builds (which i already do it)
You're doing a remarkable work. What about submit for official build?
Its_Vixano said:
Just pushed august ota
enjoy
Click to expand...
Click to collapse
Thanks a lot for your great work!
AudioSculpt said:
You're doing a remarkable work. What about submit for official build?
Click to expand...
Click to collapse
who knows ?
Not sure where to ask this, I apologize if I'm asking in the wrong place. But how is the lack of the proximity sensor is handled in this ROM?
Do you face any issues when accepting calls or listening to WhatsApp audio messages?
Thanks for sharing your work.
Has anybody managed to get Google wallet working?
Flashed today, so far everything looks very good
Is it possible to get the stock Xiaomi Cam on this rom?
I need makro and ultrawide cam
Thanks a lot for this great Rom
I have a Xiaomi Mi 11 Lite 5G NE (256gb DG - Global Version). I bootloader unlocked it after a week's usage. It is visible to ADB and Fastboot on Windows 10.
Ran into a bit of a problem following the flashing guide.
Downloaded the following files:
boot.img
192 MB17 days ago
dtbo.img
24 MB6 days ago
lineage-19.1-20220824-UNOFFICIAL-lisa.zip
1.1 GB17 days ago
vendor_boot.img
96 MB17 days ago
From the link. Successfully flashed boot.img, vendor.boot.img, and dtbo.img. It automatically selected _b as a destination on the phone. Attempting a reboot with power + volume up never got me to a recovery screen, only had the Mi logo flash before re-entering fastboot.
I re-read the instructions and there's a place where it is a little unclear as to if recovery.img is to be used for all phones or not despite only being in the ys1 repository. So I downloaded that and flashed it (successfully), it auto selected _a as a destination.
Phone still continues to reboot to fastboot, but now without the Mi logo flashing (guessing I blew away whatever was left of the factory ROM on _a with that last move).
Suggestions on what to do next? I'm stuck at a place where the phone is in fastboot mode and connected to a Windows machine with adb and the proper drivers but I'm guessing has no bootable recovery or ROM so sideloading isn't an option.