{
"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 12, 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 organization. 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.
Instructions :
https://wiki.lineageos.org/devices/discovery/install
Downloads :
https://download.lineageos.org/discovery
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel, or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
I'm gonna try to flash this today,
any gapps recommendation perhaps please?
also second question, does this rom recieves OTA updates?
maxis123 said:
I'm gonna try to flash this today,
any gapps recommendation perhaps please?
Click to expand...
Click to collapse
No.
maxis123 said:
also second question, does this rom recieves OTA updates?
Click to expand...
Click to collapse
No.
installed and rom is nice everything is fine, except.. Can't get connection to Internet, tryed reseting APNs, writing them on my own, can't get connection to Internet no way...
please ignore post above, turns out it was only my sim card issue..
Ty i will test it this weekend.
Awesome ROM, flawless!
Thanks for keeping this old phone alive.
But i hate the look of Android12...
michaaa62 said:
But i hate the look of Android12...
Click to expand...
Click to collapse
Yes, same here... I am building Android 11 (last amazing version IMO) for my Xperia 5 at the moment, I dont know how to port LineageOS 18.1 but I am building a SODP AOSP ROM atm.
May I ask if the system cannot be updated, have you deleted anything to keep the data?
I am facing issue with SIM2. only one sim is detected at a time.. Any help?
drakost said:
I am facing issue with SIM2. only one sim is detected at a time.. Any help?
Click to expand...
Click to collapse
Can you try to run these commands and let me know if that fixes it? You'll need to enable "Rooted debugging" in developer options before running these commands. FYI
Code:
adb root
adb remount
adb shell "curl https://raw.githubusercontent.com/LineageOS/android_device_sony_nile-common/6aa83e6e8cc00638004bbb3eca6eb347b16e1bbb/rootdir/etc/init.qcom.rc -o /vendor/etc/init/hw/init.qcom.rc"
adb reboot
LuK1337 said:
Can you try to run these commands and let me know if that fixes it? You'll need to enable "Rooted debugging" in developer options before running these commands. FYI
Code:
adb root
adb remount
adb shell "curl https://raw.githubusercontent.com/LineageOS/android_device_sony_nile-common/6aa83e6e8cc00638004bbb3eca6eb347b16e1bbb/rootdir/etc/init.qcom.rc -o /vendor/etc/init/hw/init.qcom.rc"
adb reboot
Click to expand...
Click to collapse
It worked! You are a life saver
Is it a temporary fix or permanent?
drakost said:
It worked! You are a life saver
Is it a temporary fix or permanent?
Click to expand...
Click to collapse
Permanent, now that you confirmed that my patch works.
LuK1337 said:
Permanent, now that you confirmed that my patch works.
Click to expand...
Click to collapse
It stopped working again after the restart... The same issue persists!
drakost said:
It stopped working again after the restart... The same issue persists!
Click to expand...
Click to collapse
Ehh, restart again? idk.
LuK1337 said:
Ehh, restart again? idk.
Click to expand...
Click to collapse
SIm 2 works and Sim1 doesn't.
Might be a bit late. Everything works now.. Took a few restart to fix this. But everything is fine now.
Thank you for the ROM. Amazing work!
first of all thanks for god job
plz i want ask you about crash of dvb finder and other apps on Lineage 19.1 how to fix that plz?
I was trying to sideload days ago from 16 to 19, but first boot never came out, it was just stuck on logo no matter how long I waited.. Any fix for that please?
also second question, long ago when 19 first became available and I tryed clean flash it and it booted, I had annoyance wich wasn't possible to turn off back then, it was when unlocking device with fingerprint it was vibrating everytime, so I'm inteteresed does 19 nowdays still vibrates when doing fingerprint unock ?? if does, can it be turned off somehow?
Thanks!
<3
Related
{
"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 is Project Treble?
Everything is explained here!
What's working:
Boots
Wifi
Bluetooth
Camera ( Videos And Photos )
Video Playback
Audio ( Record and Playback )
Sensors
GPS
RIL
VoLTE
What's not working:
Selinux is permissive
You tell me
Generic System Images:
Here
How to flash:
Use a TWRP with /vendor support
Wipe cache, dalvik-cache, system, vendor and data
Flash the required firmware
Flash the treble_lithium-xxxxxxxx-xxxx.zip
Select "Flash Image"
Flash a Generic System Image in system partition (arm64, A only)
Reboot
Special thanks:
Tranquilitysmile for testing and debugging
XDA:DevDB Information
Project Treble for the Xiaomi Mi Mix
Contributors
Psy_Man
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.x
ROM Firmware Required: 8.8.30
Based On: AOSP
Version Information
Status: Stable
Created 2018-05-01
Last Updated 2018-09-12
Screenshots:
Excellent looking forward to this
Add this line to build prop to enable navbar
Code:
qemu.hw.mainkeys=0
Great job, thanks
02.05.2018 build:
- Forced enable navigation bar (thanks @EvangelineDEV for pointing this out)
- Moved listen_platform_info.xml to /vendor
- Merged changes from LineageOS
Download build
This is awesome!
Thanks Pepsy!!!
Earphone does not work, is it a common problem ?
Great work!
woha, thanks @Psy_Man !
since this took me somewhat by surprise: how will the flashing-process with treble roms differ from the traditional way? after flashing the treble-zip (and doing a factory reset) for the first time, will it be possible to switch the generic system images without a factory reset every time like when switching a "traditional" rom? will you still continue your Pixel Experience rom or is Treble the way to go? and which TWRP meets the /vendor requirement? the TWRP-thread is a bit chaotic...
sorry for all those questions, really appreciate your work!
doumer said:
woha, thanks @Psy_Man !
since this took me somewhat by surprise: how will the flashing-process with treble roms differ from the traditional way? after flashing the treble-zip (and doing a factory reset) for the first time, will it be possible to switch the generic system images without a factory reset every time like when switching a "traditional" rom? will you still continue your Pixel Experience rom or is Treble the way to go? and which TWRP meets the /vendor requirement? the TWRP-thread is a bit chaotic...
sorry for all those questions, really appreciate your work!
Click to expand...
Click to collapse
I believe factory reset and wiping system and data are still needed between GSI's... But it should be tried...
Twrp by raupe-lunden.... Find it linked in most oreo roms threads op's I think.
For flashing generic procedure the instructions are linked right here in Psy_Man's OP
Using RR image, stuck at white android logo. Cannot go into OS, trying format data wipe all, result still same
Fusionist said:
Using RR image, stuck at white android logo. Cannot go into OS, trying format data wipe all, result still same
Click to expand...
Click to collapse
I cannot see logcat here. Ignored.
Psy_Man said:
I cannot see logcat here. Ignored.
Click to expand...
Click to collapse
I still dont know how people want us to solve these problems , if they dont provide logcat we cannot make magic and say OH this is!!!!!!! lol . Thanks Psy_Man for your treble work.
Psy_Man said:
I cannot see logcat here. Ignored.
Click to expand...
Click to collapse
Yup.
I also couldn't boot RR or AOKP... Will try and get logcats from the bootloop and share here a pastebin or the likes.
This treble advances for lithium I believe are awesome and undoubtedly the way to go.
Thanks again Psy_Man.
Psy_Man said:
I cannot see logcat here. Ignored.
Click to expand...
Click to collapse
Sorry for not provided logcat, I dont know how to getting logcat when my phone stuck at boot animation ? How can I get the logcat when stuck at boot?
Fusionist said:
Sorry for not provided logcat, I dont know how to getting logcat when my phone stuck at boot animation ? How can I get the logcat when stuck at boot?
Click to expand...
Click to collapse
If I recall correctly, running
Code:
adb -d logcat>mylogfile.txt
before the phone boots should wait until the phone boots and connects to the computer, provide you with a logcat, and save it to a file. (You won't see the output in the terminal, but the log file should be there. There's more information on this here.)
This looks great, good work! I'll try it in a bit and report back on how it works. Thanks again!
NLivingstonAP said:
If I recall correctly, running before the phone boots should wait until the phone boots and connects to the computer, provide you with a logcat, and save it to a file. (You won't see the output in the terminal, but the log file should be there. There's more information on this here.)
This looks great, good work! I'll try it in a bit and report back on how it works. Thanks again!
Click to expand...
Click to collapse
Many thanks ! I'll try it again
Hello i want to ask what is the benefit using the treble based custom rom? From what i know is the update is faster for oem eg samsung, lg or oem that used treble, but what is benefit using this on custom rom?
billyliem said:
Hello i want to ask what is the benefit using the treble based custom rom? From what i know is the update is faster for oem eg samsung, lg or oem that used treble, but what is benefit using this on custom rom?
Click to expand...
Click to collapse
You flash the treble compatible and then any GSI out there, that are cooked and usable for any treble enabled device. You don't need an aokp (or any other) cooked specifically for lithium.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 10, 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.
Instructions :
Download the latest build and gapps
Reboot to recovery
Flash the latest build and gapps
Reboot
Downloads :
Builds :
https://download.lineageos.org/davinci
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
Donate
PayPal
Liberpay
Telegram Group
Here
XDA:DevDB Information
LineageOS, ROM for the Redmi K20 / Xiaomi Mi 9T
Contributors
PIPIPIG233666, PIPIPIG233666, minz1
Source Code: https://github.com/LineageOS
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: require version-cn=CN,4.3.c5-00052,20.6.30 require version-in=IN,4.3.c5-00052,V12.0.2.0.QFJINXM require version-eea=GLOBAL,4.3.c5-00052,V12.0.0.11.QFJMIXM
Based On: LineageOS
Version Information
Status: Stable
Current Stable Version: 17.1-20200927-UNOFFI
Stable Release Date: 2020-07-22
Created 2019-12-30
Last Updated 2020-10-07
Hyperlink redirects to the Lineage 16 base on Android 9.
ekin_strops said:
Hyperlink redirects to the Lineage 16 base on Android 9.
Click to expand...
Click to collapse
dont worry ill upload soon, my network is kinda slow
PIPIPIG233666 said:
dont worry ill upload soon, my network is kinda slow
Click to expand...
Click to collapse
Not worried, just saying, in case if it's a mistake in the link.
Spam? Because I saw a multiple thread about this
rEsonancE_0404 said:
Spam? Because I saw a multiple thread about this
Click to expand...
Click to collapse
not spam it happens sometimes when xda dosent update post at first time & dev has to click multiple time on post button
good rom.
thanks PIPIPIG233666
link had been posted,enjoy!
Only need firmware based on 10? Or firmware+vendor?
thank u ....
Thank you for this.
What is the kernel you are using here?
Does this changes Mac address or other partition like the old build or it's safe ?
soumyachatterjee said:
Thank you for this.
What is the kernel you are using here?
Click to expand...
Click to collapse
LineageOS one. There's a screenshot of the build details on the original post.
Good job! Keeping the fingers crossed for getting an official status!
Keep rocking!
Sorry, you can't view or download this file at this time.
Too many users have viewed or downloaded this file recently. Please try accessing the file again later. If the file you are trying to access is particularly large or is shared with many people, it may take up to 24 hours to be able to view or download the file. If you still can't access a file after 24 hours, contact your domain administrator.
Click to expand...
Click to collapse
So there is no way to download at the moment
Is it possible to build myself from your source with this howto https://www.lineageosrom.com/2017/01/how-to-build-lineageos-rom-for-any.html
or is there something to be aware of or to add or so so I (with no expericence in Building a ROM) will not be able to do this with this guide?
Please reupload or do something. I can't download from google drive because many people downloaded it. I want too...
Instructions :
You need a PC with ADB & Fastboot available
Download recovery
Reboot to fastboot
Run: fastboot flash recovery recovery.img
Press volume & power up until you see TWRP logo
Enter your password (if it prompts)
Go to Wipe
Select Advanced Wipe
Select system & cache & internal storage and press wipe
Go back (press back twice)
Click to expand...
Click to collapse
I'm currently on MIUI v11.0.3.0 (Android 9) Global stock rom.
I have unlocked the bootloader and installed twrp recovery and magisk. So do I just place the rom zip into my internal storage and flash it via twrp? or there are any prior steps before installation?
Also in the instruction, it says to wipe internal storage as well. Can someone explain why?
This is my first time flashing a MIUI device
ragnar6666 said:
I'm currently on MIUI v11.0.3.0 (Android 9) Global stock rom.
I have unlocked the bootloader and installed twrp recovery and magisk. So do I just place the rom zip into my internal storage and flash it via twrp? or there are any prior steps before installation?
Also in the instruction, it says to wipe internal storage as well. Can someone explain why?
This is my first time flashing a MIUI device
Click to expand...
Click to collapse
I guess that you will need to update to android 10 in prior as it will definitly be based on android 10 vendor.. Or atleast you should flash android 10 firmware (dont have a link at the moment). By wiping internal storage he means format data option in TWRP. This will delete all your data on your phone. The only reason behind this as far as i know is because the storage is encrypted by the MIUI and this new OS would not be able to decrypt it.
Joakin2k said:
Does this changes Mac address or other partition like the old build or it's safe ?
Click to expand...
Click to collapse
My Wifi-MAC got changed!
Edit:Switched back to my old ROM
- MAC addresses were changed (to maybe Pigs?)
- Fingerprint again not working
so I'll wait ...
maroc84 said:
My Wifi-MAC got changed!
Click to expand...
Click to collapse
check when you connect in wifi if you are using randomized mac instead of your device one because it's an android 10 feature
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 10, 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.
Instructions :
Download the latest build and gapps
Boot to recovery
Flash the latest build
Boot to recovery again
Flash gapps
Reboot
Downloads :
Builds : http://download.lineageos.org/mermaid
SemcCamera addon : https://androidfilehost.com/?w=files&flid=305730
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
XDA:DevDB Information
[ROM][OFFICIAL][mermaid][10] LineageOS 17.1, ROM for the Sony Xperia X10 Plus
Contributors
LuK1337
Source Code: https://github.com/LineageOS
ROM OS Version: Windows 8 Mobile
Version Information
Status: Testing
Created 2020-02-16
Last Updated 2020-04-01
oh btw you might want to use this TWRP for flashing my builds.
Just bootlop
Great performance and smoothness.
reintal said:
Just bootlop
Click to expand...
Click to collapse
Did you format data? If that didn't help, mind sending me a msg on irc?
https://kiwiirc.com/nextclient/irc.freenode.net?channel=#titandev
NFC does not work
reintal said:
NFC does not work
Click to expand...
Click to collapse
Works here? I just tried Android Beam.
LuK1337 said:
Works here? I just tried Android Beam.
Click to expand...
Click to collapse
He works with some issues, sometimes i can't read nfc cards and use android beam. I assume this is an application problem.
LuK1337 said:
oh btw you might want to use this TWRP for flashing my builds.
Click to expand...
Click to collapse
X10 plus I4293, use this TWRP 3.3.1-1,
if use fastboot boot twrp.img, the touch is right,
if install Recovery ramdisk, then use Vol- and Power into twrp, the Touch is unavailable！
easyt said:
X10 plus I4293, use this TWRP 3.3.1-1,
if use fastboot boot twrp.img, the touch is right,
if install Recovery ramdisk, then use Vol- and Power into twrp, the Touch is unavailable！
Click to expand...
Click to collapse
Oh. I kinda understand why something like this would happen...
Can you come irc? I don't want to reflash stock just to debug this.
EDIT: Maybe fixed in twrp-3.3.1-2-mermaid.img.
LuK1337 said:
Oh. I kinda understand why something like this would happen...
Can you come irc? I don't want to reflash stock just to debug this.
EDIT: Maybe fixed in twrp-3.3.1-2-mermaid.img.
Click to expand...
Click to collapse
I re-flashed the official firmware, and then flash twrp again, it's right!
thank you
Two sim
LuK1337 said:
Oh. I kinda understand why something like this would happen...
Can you come irc? I don't want to reflash stock just to debug this.
EDIT: Maybe fixed in twrp-3.3.1-2-mermaid.img.
Click to expand...
Click to collapse
Two sim does not work when an SD card is inserted
Stezko said:
Two sim does not work when an SD card is inserted
Click to expand...
Click to collapse
Hmm...I would need you to test something for me in that case. Mind sending me a msg on irc/hangouts/discord?
LuK1337 said:
Hmm...I would need you to test something for me in that case. Mind sending me a msg on irc/hangouts/discord?
Click to expand...
Click to collapse
my english level is zero)
The second question is, is it possible to install Magisk on this rom?
I install Magisk-v20.3.zip via twrp and get a bootloop
Stezko said:
my english level is zero)
The second question is, is it possible to install Magisk on this rom?
I install Magisk-v20.3.zip via twrp and get a bootloop
Click to expand...
Click to collapse
I don't really care whether your english is perfect or not. I just need you to test that for me...
I can't say much about magisk tho, I don't use it.
EDIT: I guess that was too much to ask for... If there's anyone with dsds device who wants to be helpful, please msg me. I would prefer to release something tested rather than hope for the best.
Stezko said:
my english level is zero)
The second question is, is it possible to install Magisk on this rom?
I install Magisk-v20.3.zip via twrp and get a bootloop
Click to expand...
Click to collapse
Everything works without problems https://imgur.com/a/ij094yH
Camera2api
Hello!
I'm using this build for daily use! I can say it's really smooth and, no issues at all!
My only question is if enabling camera2api is possible, and then install a working version of gcam...
Any help will be appreciated!
I'm also willing to provide feedback and make my mobile a Guinea pig to make this work!:fingers-crossed:
Lineage is running stable with semc addons, Gapps, tai chi, and root with magisk 20.3.
fastboot boot boot.img and reboot to recovery ramdisk worked best.
After failing to successfully root flashing magisk.zip, I got a boot image
from a twrp backup. I renamed boot.emmc.win to boot.img and patched
with Magisk. Flashed the new boot.img, magisk.zip, and had root on startup.
Any recommended gapps? Tried both open gapps nano and micro and both force close on account setup
aeppacher said:
Any recommended gapps? Tried both open gapps nano and micro and both force close on account setup
Click to expand...
Click to collapse
Did you even format data?
LuK1337 said:
Did you even format data?
Click to expand...
Click to collapse
Did a full format before installation and then after lineage install. Tried factory reset after gapps installation and tried 3 different dates for gapps in case it was a new bug. Are you suggesting to do an installation, gapps, then full format?
{
"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, 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.
Instructions :
https://wiki.lineageos.org/devices/instantnoodle/install
Downloads :
https://download.lineageos.org/instantnoodle
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
Kernel source: https://github.com/LineageOS/android_kernel_oneplus_sm8250
{Mod edit: Link to kernel source added on request of OP}
Donate:
Many thanks for making op8 officially built. I've been on since yesterday early and no issues other than can't call upon "hey google" to use assistant. But from what I've seen only works on stock. If anyone knows a fix , please share. Long press home button pulls it up but not hands free. ok ultranoob just told me I used wrong gapps using NikGapps. And linked to to correct ones. I will reflash. Said it's working fine on his end
thank you for making op8 officially
niceeee
mattie_49 said:
Many thanks for making op8 officially built. I've been on since yesterday early and no issues other than can't call upon "hey google" to use assistant. But from what I've seen only works on stock. If anyone knows a fix , please share. Long press home button pulls it up but not hands free. ok ultranoob just told me I used wrong gapps using NikGapps. And linked to to correct ones. I will reflash. Said it's working fine on his end
Click to expand...
Click to collapse
Am planning to take the dip... which is the correct Gapps to use? And if you can spare time to write the steps to install them would be appreciated.
sjgoel said:
Am planning to take the dip... which is the correct Gapps to use? And if you can spare time to write the steps to install them would be appreciated.
Click to expand...
Click to collapse
Still unknown. NikGapps work fine but break "hey google". Working with ultranoob one of the maintainers to get sorted out. I'll lyk asap. Use Nikgapps if you don't use your assistant hands free. Adb sideload name of package. Through Lineage recovery
Install LineageOS on instantnoodle | LineageOS Wiki
wiki.lineageos.org
mattie_49 said:
Still unknown. NikGapps work fine but break "hey google". Working with ultranoob one of the maintainers to get sorted out. I'll lyk asap. Use Nikgapps if you don't use your assistant hands free. Adb sideload name of package. Through Lineage recovery
Install LineageOS on instantnoodle | LineageOS Wiki
wiki.lineageos.org
Click to expand...
Click to collapse
Ok. Did you try to use the suggested gapps on the lineageOS website MindTheGapps for lineageOS 11 ?
sjgoel said:
Ok. Did you try to use the suggested gapps on the lineageOS website MindTheGapps for lineageOS 11 ?
Click to expand...
Click to collapse
Yes and Nikgapps both
mattie_49 said:
Many thanks for making op8 officially built. I've been on since yesterday early and no issues other than can't call upon "hey google" to use assistant. But from what I've seen only works on stock. If anyone knows a fix , please share. Long press home button pulls it up but not hands free. ok ultranoob just told me I used wrong gapps using NikGapps. And linked to to correct ones. I will reflash. Said it's working fine on his end
Click to expand...
Click to collapse
Coming from the unofficial build, I assume (also mentioned in the unofficial thread) we can dirty flash since the sources are the same, but could i ask for the specific steps you took? Did you apply the copy partitions step too?
mvmike said:
Coming from the unofficial build, I assume (also mentioned in the unofficial thread) we can dirty flash since the sources are the same, but could i ask for the specific steps you took? Did you apply the copy partitions step too?
Click to expand...
Click to collapse
Tried going to official from unofficial and didn't like it. Had to clean flash to work.
Stoked to have an official build! It installs & runs great, thanks to all who made this possible for OP8!
It's nice to know it will always be updated and maintained - I was on DOT OS and loved it with Hasty kernel but the thread appears dead so here I am.
mvmike said:
Coming from the unofficial build, I assume (also mentioned in the unofficial thread) we can dirty flash since the sources are the same, but could i ask for the specific steps you took? Did you apply the copy partitions step too?
Click to expand...
Click to collapse
I did the copy partions zip only because im coming from fresh msm then unlock. And only had oos on one side.
Copying bugs from the closed thread with some additions:
1) Display is too light on minimal brightness, it's not comfortable to use in darkness. Also, it seems its too dark on maximum brightness, but I am not sure.
2) Phone speaker too loud on minimal volume. Everybody in room can hear my interlocutor.
3) Gravitation sensor work fine in apps like SatStat, but not in camera apps: OpenCamera and GCam. While making a photo, horizontal line in camera react to position change very, very slowly. It take about 15 seconds to display real horizon.
4) Not sure its a software problem, but nevertheless: Acc daemon + AccA app cannot limit battery charging voltage. This feature is very usefull to prolong battery live.
5) Phone setting to check Proximity settings before activation is not working, so, phone aims to go active in pocket. Proximity sensor itself is working (proved with SatStat app).
6) May be related to (1). Light sensor shows illumination value about 2..6 times more that it should be (tested with SatStat on a few devices). Error multiplicator not so big in dark place and grows with illumination level.
passion8059 said:
Tried going to official from unofficial and didn't like it. Had to clean flash to work.
Click to expand...
Click to collapse
Same issue here, but hey, another factory reset it's worth it if we end up with a supported official build
Is it possible to get Magisk or something else like it installed with this? I'd like to root and prevent apps from knowing, so they all function as normal.
Guys do i need to copy partitions a and b if im changing from Pixel Experience?
chriswcs said:
Is it possible to get Magisk or something else like it installed with this? I'd like to root and prevent apps from knowing, so they all function as normal.
Click to expand...
Click to collapse
Lineage never had any issue with Magisk, have both nikgapps (core) + Magisk working perfectly.
Just follow the instructions and remember to let system boot once after fresh install before
mvmike said:
Lineage never had any issue with Magisk, have both nikgapps (core) + Magisk working perfectly.
Just follow the instructions and remember to let system boot once after fresh install before
Click to expand...
Click to collapse
How did you get the boot.img to patch though? I couldn't find one in the .zip file.
chriswcs said:
How did you get the boot.img to patch though? I couldn't find one in the .zip file.
Click to expand...
Click to collapse
Search for payload dumper. Can be used in Windows as a standalone program, or making use of Python3 under Linux as well. Doing so, you will be able to extract the boot.img to be patched with Magisk. Very good explanations on howto, here on XDA.
chriswcs said:
How did you get the boot.img to patch though? I couldn't find one in the .zip file.
Click to expand...
Click to collapse
Although made for Nokia, the steps in this thread generally apply. You have to download your Oneplus OTA of course.
[Guide] How to extract payload.bin from OTA
This is guide for extract payload.bin from OTA zip file ----------------- Pre-requirement: - Python3 ----------------- For extract OTA update Please flow step by step instruction Step 1: Get a OTA for Nokia 7 plus -> here Step 2: Download...
forum.xda-developers.com
{
"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 12, 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.
Instructions:
https://wiki.lineageos.org/devices/lemonade
Downloads:
https://download.lineageos.org/lemonade
Reporting Bugs:
DO NOT report bugs if you're running a custom kernel or you installed Xposed.
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
This section is for updating LineageOS. You must have your device connected to your computer to do this.
To update to newer builds of LineageOS 19.1, follow these steps (assuming you're already on LineageOS 19.1 or updating from LineageOS 19.0):
Reboot to recovery.
Write down which slot you are currently on somewhere. You will need it in case the update does not boot correctly.
Go to Apply Update > Apply from ADB, and use "adb sideload" to flash the newer build of LineageOS.
If you installed Gapps or Magisk or any type of addon previously, go to Advanced > Reboot to recovery. Otherwise, select "Reboot system now".
Go to Apply Update > Apply from ADB, and flash your modules the same way you flashed LineageOS.
When you are done, select "Reboot system now".
If an update does not boot, follow these steps:
Reboot to bootloader. This can be done with "adb reboot bootloader".
From there, use "fastboot --set-active=<slot>", replacing <slot> with the slot you were on previously.
Reboot to system. You can just select "START" with the volume buttons and confirm by pressing the Power button.
Greetings, this build work very well, dev in future you can add advanced reboot?
Thank you!
iaio72 said:
Greetings, this build work very well, dev in future you can add advanced reboot?
Click to expand...
Click to collapse
It's there somewhere hidden. Must seek out. I know it's on lineage. It's the base for almost all aosp build.
mattie_49 said:
It's there somewhere hidden. Must seek out. I know it's on lineage. It's the base for almost all aosp build.
Click to expand...
Click to collapse
not there, I have already checked well!!
iaio72 said:
not there, I have already checked well!!
Click to expand...
Click to collapse
The build is stable?
mattie_49 said:
The build is stable?
Click to expand...
Click to collapse
yes a lot, I was impressed by the functionality
iaio72 said:
yes a lot, I was impressed by the functionality
Click to expand...
Click to collapse
Was gonna wait till second build. I'm gonna flash now tonight.
Does this have the issue on the T-Mobile model where it will show two sim slots, both empty? Or is that problem specific to OOS 12?
Thanks!
Just a curiosity, in launcher settings, it does not put the Google feed, to the left of the display, it does not exist.
Should this be installed ontop of the latest OOS11 or OOS12 image?
P_1 said:
Should this be installed ontop of the latest OOS11 or OOS12 image?
Click to expand...
Click to collapse
OOS 11
Out of curiosity, what is the reason you need to be on OxygenOS 11 for this to be installed? Has something changed internally that conflicts with installing this ROM?
Just got a strange behaviour of brightness becoming mad
bleuthoot said:
Out of curiosity, what is the reason you need to be on OxygenOS 11 for this to be installed? Has something changed internally that conflicts with installing this ROM?
Click to expand...
Click to collapse
Its based on the proprietary blobs from the latest OOS11 release.
This means that while its possible for it to be installed ontop of any other OOS release, there may exist bugs/incompatibility issues when you use something other than what the lineage build is based on.
hi everybody. I found an error. the sound in the speaker is wheezing at maximum volume, is there any solution?
Hi, how about camera? Is this OS support every feature and capabilities of hardware? Thanks
akboy7015 said:
Hi, how about camera? Is this OS support every feature and capabilities of hardware? Thanks
Click to expand...
Click to collapse
This is beta. No oos cam ,is that a serious question?. It's not even available for the 9 series on A11 yet. Little lone A12
Top quality ROM. Works great. Thanks @andr01dfr3ak!