{
"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 out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Instructions :
https://wiki.lineageos.org/devices/enchilada
Downloads :
https://download.lineageos.org/enchilada
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:
Great..........
a surprise gift for oneplus 6 thanks for the great things you do !
Thanks , looking forward for this project
Thanks for bringing LineageOS 19 to our device. Everything is working as expected, Just a small bug in Volte/Vowifi calls IMS ringtone is missing.
Ggreat！！！
vikash1994b said:
Thanks for bringing LineageOS 19 to our device. Everything is working as expected, Just a small bug in Volte/Vowifi calls IMS ringtone is missing.
Replacing ims.apk from evolutionX vendors fixed it. Link: https://github.com/Evolution-X-Devi...mmit/b38ca998c8c916cdd2685b07f8aafd89a863e142
Click to expand...
Click to collapse
Did you upgrade from 18 or clean flash?
diemadedrei said:
Did you upgrade from 18 or clean flash?
Click to expand...
Click to collapse
Clean flash
-- posting just to have this thread in my 'new posts' view --
Has anyone tried ih8sn with this version?
And if it works what is recommended in the conf file?
With 18.1 I used this but in 19 I'm unsure since the android version no longer matches, perhaps it is better to use another phones build info.
Code:
BUILD_FINGERPRINT=OnePlus/OnePlus6/OnePlus6:11/RKQ1.201217.002/2111252325:user/release-keys
BUILD_DESCRIPTION=OnePlus6-user 11 RKQ1.201217.002 2111252325 release-keys
BUILD_SECURITY_PATCH_DATE=2021-11-01
BUILD_TAGS=release-keys
BUILD_TYPE=user
BUILD_VERSION_RELEASE=11
DEBUGGABLE=0
MANUFACTURER_NAME=OnePlus
PRODUCT_NAME=OnePlus6
ponanovn said:
Has anyone tried ih8sn with this version?
And if it works what is recommended in the conf file?
With 18.1 I used this but in 19 I'm unsure since the android version no longer matches, perhaps it is better to use another phones build info.
Code:
BUILD_FINGERPRINT=OnePlus/OnePlus6/OnePlus6:11/RKQ1.201217.002/2111252325:user/release-keys
BUILD_DESCRIPTION=OnePlus6-user 11 RKQ1.201217.002 2111252325 release-keys
BUILD_SECURITY_PATCH_DATE=2021-11-01
BUILD_TAGS=release-keys
BUILD_TYPE=user
BUILD_VERSION_RELEASE=11
DEBUGGABLE=0
MANUFACTURER_NAME=OnePlus
PRODUCT_NAME=OnePlus6
Click to expand...
Click to collapse
Worked fine the last time i tried on self compiled lineage 19.1, so should work here too.
Just did a dirty flash from LOS 18.1 and everything works fine.
I had to reinstall some Google apps (YouTube, Gmail, Keep, GCam, Photos), as they stopped working after the upgrade (maybe because I accidentally clicked No on the Signature verification failed screen while flashing Gapps and didn't notice, then the OS didn't boot. whoops. So I went back into the recovery and flashed Gapps again. Sure enough, the install went through. So be careful and make sure to click the correct button, lol)
Everything else seems to work perfectly!
Thanks again LuK for your work!
In case anyone with Gapps and Magisk wants to try a dirty flash from 18.1, here are the steps I did:
(you're on your own if things break! better to do a clean flash! magisk isn't officially supported!)
1. Restored images in Magisk
2. Removed PIN and fingerprints
(Not sure if these first two steps are needed, but did them just in case)
3. adb reboot sideload
4. adb sideload lineage-19.1-20220426-nightly-enchilada-signed.zip
5. Advanced->Reboot to Recovery
6. Apply Update->Apply from ADB
7. adb sideload MindTheGapps-12.1.0-arm64-20220416_174313.zip
8. adb sideload Magisk-v24.3.apk
9. Back->Reboot system now
Wow! I installed from latest oxygenos. I unlocked the bootloader and followed the tutorial. It all works perfectly. Thanks a lot!
Awesome, just updated from 18.1 to 19.1. Everything seems OK.
Reboot to Recovery, then when your device reboots, click Apply Update, then Apply from ADB.
adb sideload lineage-19.1-20220426-nightly-enchilada-signed.zip
Reboot to Recovery
adb sideload MindTheGapps-12.1.0-arm64-20220416_174313.zip
adb sideload Magisk-v24.3.apk
Reboot system now
Couldn't be any easier. Thanks @LuK1337
Thank you all, in particular LuK1337, I've been waiting for this for some time. I have 3 questions:
- Is call recorder implemented?
- I use AFWall+, but iptables is deprecated. How works eBPF? Is a separated app or built-in on generic SO settings (Apps menu)? Some opinion AFWall+ vs EBPF?
- Also, I use Adaway, Magisk works fine?
OP6 is my daily driver and older devices are not supported, for this reason I ask.
Thanks!
Thanks LuK1337. Just installed it in my OP6. Initial impression is good.
pdmr said:
Thank you all, in particular LuK1337, I've been waiting for this for some time. I have 3 questions:
- Is call recorder implemented?
- I use AFWall+, but iptables is deprecated. How works eBPF? Is a separated app or built-in on generic SO settings (Apps menu)? Some opinion AFWall+ vs EBPF?
- Also, I use Adaway, Magisk works fine?
OP6 is my daily driver and older devices are not supported, for this reason I ask.
Thanks!
Click to expand...
Click to collapse
Magisk and Adaway works just fine, not sure about the others
19.1 runs fine so far. but when I relock the bootloader, I always end in fastboot mode (bootloader). with 18.1 it was working.
Hi, the upgrade was smooth. I've noticed that notification sound seems quite loud, even when set to the first notch (lower means muted).
Also sometimes the status bar is a bit off, here the 4G inscription
CrysisLTU said:
Magisk and Adaway works just fine, not sure about the others
Click to expand...
Click to collapse
Thanks! v24.3 and patching boot.img?
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"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 9 (Pie), 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/gts28vewifi
Root addon : https://download.lineageos.org/extras
Google Apps : https://wiki.lineageos.org/gapps.html
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][T713][9] LineageOS 16.0, ROM for the Samsung Galaxy Tab S2
Contributors
LuK1337
Source Code: https://github.com/LineageOS
ROM OS Version: Windows 8 Mobile
Version Information
Status: Testing
Created 2018-08-16
Last Updated 2019-03-02
Anyone installed this yet?
*deleted*
9646gt said:
Anyone installed this yet?
Click to expand...
Click to collapse
Yes, I got it installed after a bit of fumbling around.
The key seems to be the gapps. I first tried the open_gapps-arm64-9.0-stock-20180815-UNOFFICIAL.zip found on XDA, but it caused several problems with Pixel setup, etc.
Finally found BiTGApps-arm64-9.x.x-0.1-unsigned.zip, which is very minimal. It worked great.
HW button lights not working, but otherwise all seems fine.
:good::good::good:
Thx, Luk1337 for your work.
I will wait this time and hope for official (so hopefully no clean Install)
just installed it, looks good, thx
Just installed. All is fine. Thanks.
It is not working for me. No matter which gapps I install, every time google play and bluetooth apps are crashing and randomly also the whole pixel setup. Unfortunately for me unusable.
spacepille said:
It is not working for me. No matter which gapps I install, every time google play and bluetooth apps are crashing and randomly also the whole pixel setup. Unfortunately for me unusable.
Click to expand...
Click to collapse
Try a clean flash of ROM and Gapps?
I tried dirty flash of Gapps over Gapps and it didn't work.
Sent from my SM-T713 using Tapatalk
Dnorris55 said:
Try a clean flash of ROM and Gapps?
I tried dirty flash of Gapps over Gapps and it didn't work.
Sent from my SM-T713 using Tapatalk
Click to expand...
Click to collapse
Yes, I formatted data and system partition before each installation and did factory reset. I tried with all possible pie gapps I could found. Also without installing gapps. Every time the same result. Very strange.
spacepille said:
Yes, I formatted data and system partition before each installation and did factory reset. I tried with all possible pie gapps I could found. Also without installing gapps. Every time the same result. Very strange.
Click to expand...
Click to collapse
Same issue. Are you flashing lineage-16.0-20180815-UNOFFICIAL-gts28vewifi.zip or lineage-16.0-20180817-UNOFFICIAL-gts28vewifi.zip?
---------- Post added at 06:02 PM ---------- Previous post was at 05:06 PM ----------
universeman said:
Same issue. Are you flashing lineage-16.0-20180815-UNOFFICIAL-gts28vewifi.zip or lineage-16.0-20180817-UNOFFICIAL-gts28vewifi.zip?
Click to expand...
Click to collapse
I think I figured it out. The errors only occur when my MicroSD card is inserted. It was prompting me on how to use the card, but I had not formatted the card.
Is Google assistant working for anyone? Half the time says unable connect, the other half the mic doesn't work.
Besides that, very promising and will be my daily rom
Kudos on getting this out so soon, and with minimal bugs. It's really smooth -- ready to be my daily driver.
Minor issues that have cropped up over 2 days of regular use:
- Google Assistant works but it *is* a bit flaky. I have to re-enable it as the default assist app after every reboot.
- None of my apps / widgets that access the SSID information work (they run, but display no information). I'm not sure if this is due to this ROM or to Android Pie in general.
[update: Problem solved. Settings > Security & privacy > Location > Advanced > Scanning > Enable Wi-Fi scanning did the trick! ]
- Battery life was about half of what I was getting with stock Nougat using the "medium" battery saver setting. I fixed that problem with the "Power Booster" app from the store (although any of the CPU tweaking apps should work as well).
I'm really hopeful that we'll get an Xposed version for Android Pie so I can get the rest of my favorite tweaks in.
Lights
and in de the new builds the ligths are on
Any way of rooting this?
Mutje said:
and in de the new builds the ligths are on
Click to expand...
Click to collapse
I was very glad to see that! [emoji106][emoji106]
Sent from my SM-T713 using Tapatalk
Any way of rooting this?
Click to expand...
Click to collapse
I think it's pre-rooted. In any case, I installed Magisk.
Update: There is "root access" setting under "developer options". Mine shows "disabled", presumably because Magisk is controlling root access.
Witch gapps should be used with these rom? Try open gapps micro, but setup keep crashing
chaos90222 said:
Witch gapps should be used with these rom? Try open gapps micro, but setup keep crashing
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=77518499&postcount=20
Deltadroid said:
https://forum.xda-developers.com/showpost.php?p=77518499&postcount=20
Click to expand...
Click to collapse
thanks, gapps works with latest build now
{
"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 9.0 (Pie), 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.
What's working :
Boots
RIL (Calls, SMS, Data)
Bluetooth
Dual-SIM
Wi-Fi
Camera
Video Recording
Video Playback
Audio ( Record and Playback )
Sensors
Flash
Led
Offline Charging
SELinux Enforcing
What's not working :
You tell me
Instructions :
Download the latest build and gapps
Reboot to recovery
Flash the latest build and gapps
Reboot
Downloads :
Builds : https://androidfilehost.com/?fid=1395089523397948075
Gdrive mirror - https://drive.google.com/file/d/1byxYWMV35fx-qQ_80qRoZLqFpnzN28oA/view?usp=drivesdk
Root addon : https://download.lineageos.org/extras (available for Lineage 16.0, use Magisk 18 or newer instead!)
Google Apps : http://opengapps.org/
Reporting Bugs
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--
Phone model:
Lineage version:
Lineage 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:
LineageSettings/Performance settings (other than stock):
Dual SIM:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
Credits :
@Luk1337
@luca020400
@Somcom3X
@kaustubh88 and @crpalmer
@Thecrazyskull
@Carlos Arriaga
@RenanQueiroz
Motorola : For providing the Kernel Source Code
LineageOS Team
Kyle Harrison for his work on osprey
Contributors
anisgvr
chil360
NOTE:
Thanks a lot and lot to chil360 ( Kyle Harrison ) for his work in osprey . He helped a lot in bringing up pie for the device. Whole credits goes to him .
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.10.x
Based On: AOSP
Version Information
Status: Stable , daily driver material
Created 2018-08-28
Last Updated 2019-04-20
Reserved
Screenshots
anisgvr said:
Screenshots
Click to expand...
Click to collapse
See charging speed in screenshots
Seems like you are on a roll with custom roms for osprey, @anisgvr. . Thanks for keeping osprey alive with your work:good:good:. Any plans to make the LOS build official?
superman234 said:
Seems like you are on a roll with custom roms for osprey, @anisgvr. . Thanks for keeping osprey alive with your work:good:good:. Any plans to make the LOS build official?
Click to expand...
Click to collapse
No one in community can make los official As of now because los needs the guy who brought up tree ... unfortunately Alberto97 is no longer developing for osprey.. and we have to wait some magic from sultan Qasim Khan (squid)
I don't understand. Could @squid2 or @Alberto97 or you explain that? This looks like a perfect good rom for official, I asume that you would be willing to carry on the torch but in the end we can't have a perfectly good phone?
Can it be dirty flashed over LineageOS 15.1?
Planning buy this phone as secondary phone, when i saw the development i went happy. Thx for keeping this phone alive!!
Error with wifi connection: buffer space
Hi,
I do not have yet logcat or anything like that. Will try to get some data if that could give more clue.
Flashed that software yesterday - added gapps and su from lineageos.
All looked very nice, but then I got wifi connected but no internet message. Only on that device, so no issues with my home network as first check.
So I used dirty hack with adding settings as suggested:
https://android.stackexchange.com/q...cted-no-internet-but-internet-works-just-fine
but it did not help - so my problem was not detection of internet - but connection on device itself.
In Brave browser the message was like ERR_NO_BUFFER_SPACE.
Restart helped. For a time like few hours.
Now my detection settings are indeed disabled but real problem shows up.
I found some topic on lenovo forum about G5 - close enough - but no real conclusion - for some update helped, some requested phone replacement, and so on. No real root cause explanation.
My plan is to restore back to previous 16 version or even further back to 14.1..
Before going that routine - anyone encountered something like that? Any ideas?
Restart helps, so maybe it is indeed some temp space filling out. Next time I can try to get more from adb - netstat?
Regards
Jan
I installed the PIE Lineage OS a few days ago on my Moto G3 x1541.I've not had one single problem.Fantastic rom.Best yet and the Lineage team have outdone themselves.
Build number Lineage_osprey-userdebug 9PQ2A
190305.002 eng.ubuntu.20190313.090534 test keys
Tip:Before I install any custom rom I do a Hard Reset/Factory reset.
Then once I've installed the rom I let it boot to normal phone mode(Can take quite a while) then reboot to Recovery and do another Hard Reset before setting up my phones.
Also I make Nandroid backups of my Setup Stock rom before installing any Custom roms then I can be up-and-running very quickly.Once I've setup my phone with a Custom rom I again make a Nanroid backup for fast reloading if required.
spljaa said:
Hi,
In Brave browser the message was like ERR_NO_BUFFER_SPACE.
Restart helped. For a time like few hours.
Click to expand...
Click to collapse
Now I was able to observe it via adb. Attaching logcat part. There is successful check, and then failed.
What is odd, DNS and ping like commands do work. It is HTTP calls that fail.
But I had no clue what shortage can be observed on resources.
That socket error in logcat might be something.
I'm quite confident that I run some wipe while installing ROM. But maybe I need to do it over again.
frogzz said:
Can it be dirty flashed over LineageOS 15.1?
Click to expand...
Click to collapse
Clean flash needed to avoid bugs
TWRP treble
https://drive.google.com/file/d/1JJ8bUBSHy5kLBqy3cX-hIAfoijdWKIK5/view?usp=drivesdk
here are almost all rom Osprey
https://androidfilehost.com/?w=search&s=Osprey&type=files
rom extended 6.4
https://builds.aospextended.com/osprey/
I have TWRP 3.2.3.0
Do I need the latest version of TWRP to use this ROM?
Thank you :3
nzkn said:
I have TWRP 3.2.3.0
Do I need the latest version of TWRP to use this ROM?
Thank you :3
Click to expand...
Click to collapse
Use latest
anisgvr said:
Use latest
Click to expand...
Click to collapse
Thanks, but I used the version that I had anyway and it worked without problems.
It is, as people said, a very good ROM. It could perfectly be official. I did not experience any problems at all.
(I did a factory reset before flashing the rom though. normal procedure, as I understand)
Tested:
>Camera: It works. Both photos and videos
>Screen Recording: It works
>Games: I do not play. Emulators work.
>Applications with real-time filters (eg SNOW): They work as expected.
>Netflix works
>Wi-fi and Mobile Data: They work, although in standby, and with Wi-fi, Data uses a lot of battery.
>VOLTE: Not available in my country, sorry
>Battery: It works much better than expected, but it's not magic. It works excellent because it kills applications in the background very aggressively. I did not see battery drains (and my phone is quite old).
Problems:
>Instagram, although it works well, does not show stickers, and neither those weird video recording modes that includes. And boomerang crash the app.
>The way it kills applications in the background is extremely aggressive by default. The first day I did not receive notifications until I opened those apps. I had to go to Battery settings, disable Battery Manager, and Optiization of battery in applications that I did not want it to kill.
This, if I'm not mistaken, is a general problem of Android Pie though
Tested on my Moto G3 8GB / 1GB ram variant.
Thanks for this marvelous 420 rom!
spljaa said:
Now I was able to observe it via adb. Attaching logcat part. There is successful check, and then failed.
What is odd, DNS and ping like commands do work. It is HTTP calls that fail.
But I had no clue what shortage can be observed on resources.
That socket error in logcat might be something.
Click to expand...
Click to collapse
As I saw some odd failed calls for some class with facebook in name I decided to remove one game: "Word Of Words". Plus removed AdAway. As other candidate for creating connections.
And so far so good. It might change, but based on above I'm thinking that even if OS could handle that better - the cause was in software I installed.
Regards
Jan
Does this rom have a separate vendor partition? What's the difference with althafvly's LineageOS 16.0 rom (also based on chil360's trees)?
does encryption work?
{
"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/fajita
Downloads :
https://download.lineageos.org/fajita
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:
LuK1337 said:
[*]Flash gapps
Click to expand...
Click to collapse
Are there any Android 11 Gapps in particular that you recommend?
Only ones I've found so far for 11 are NikGapps?
What is WFD????
Marco89989 said:
What is WFD????
Click to expand...
Click to collapse
Wifi Direct
OhioYJ said:
Wifi Direct
Click to expand...
Click to collapse
WiFi Display.
LuK1337 are you using same android_kernel_oneplus_sdm845 as 17.1 ? Its 18.0 branch isn't on lineageos github yet and did not see anything in your personal github.
dwardo said:
LuK1337 are you using same android_kernel_oneplus_sdm845 as 17.1 ? Its 18.0 branch isn't on lineageos github yet and did not see anything in your personal github.
Click to expand...
Click to collapse
Look at /proc/version and answer this question yourself.
LuK1337 said:
Look at /proc/version and answer this question yourself.
Click to expand...
Click to collapse
I didn't install it...
Was just considering to start building it myself.
Verizon support? Other a11 ROMs Verizon not supported yet.
Flashed this from RR Q Rom.
0)Boot To Recovery from 3.4.0.2 official and
1)Swipe to Factory Wipe
2)Flash Lineage 18
3)Flash TWRP
4)Flash Lineage 18
5)Flash TWRP
6)Reboot to Recovery
7)Flash GAPPS
8)Reboot to System
9)Reboot to Recovery
10)Flash magisk-debug.zip
11)Reboot to System. Done
Magisk 21 doesn't work for me. Anyone having same issue?
https://youtu.be/vxUeUrEcaqY?list=WL&t=85
Front cam crashes when i bring face closer to camera. Logcat given.
Anyone having issues with google drive auto-closing (won't launch)?
Yes buddy... i had the same issue and the phone stuck onto Qualcomm:Crash Dump while booting.
I would have to again install TWRP 3.4.0-2 and it would boot up.
But this magisk-debug.zip works
LuK1337 said:
Look at /proc/version and answer this question yourself.
Click to expand...
Click to collapse
Is the kernel source closed for the moment, last commit in device repo is also from 1st September. Must be some valid reason. Your device sources are key for other custom roms.
@LuK1337 you are a great developer, would really appreciate the local manifest in op if all the dependencies repo does not get synced automatically on build start. You do all the hardwork but some people get very happy just after compiling the rom from your source. Some like me want to add desired features on it. OP6t is about to be an EOL device, you are the only saviour for us.
Bdw, great job done with eleven bring up.
dwardo said:
I didn't install it...
Was just considering to start building it myself.
Click to expand...
Click to collapse
brajesh.sharma87 said:
Is the kernel source closed for the moment, last commit in device repo is also from 1st September. Must be some valid reason. Your device sources are key for other custom roms.
@LuK1337 you are a great developer, would really appreciate the local manifest in op if all the dependencies repo does not get synced automatically on build start. You do all the hardwork but some people get very happy just after compiling the rom from your source. Some like me want to add desired features on it. OP6t is about to be an EOL device, you are the only saviour for us.
Bdw, great job done with eleven bring up.
Click to expand...
Click to collapse
The question was not for me, but I would still like to share something: There are no kernel/config changes needed for R (https://android.googlesource.com/kernel/configs/+/refs/heads/android11-release/r/), so 17.1 and 18 can use the same branch without problems.
This rom is amazing and so smooth all we need now is to pass safety net and if gapps can be included battery life is amazing and very fluid I tried other 11 Roms but this one is very smooth just need to pass safety net and is there a telegram group ?
bigblood104 said:
This rom is amazing and so smooth all we need now is to pass safety net and if gapps can be included battery life is amazing and very fluid I tried other 11 Roms but this one is very smooth just need to pass safety net and is there a telegram group ?
Click to expand...
Click to collapse
Gapps will never be included in lineage.
Anonymous Vagrant said:
10)Flash magisk-debug.zip
Magisk 21 doesn't work for me. Anyone having same issue?
Click to expand...
Click to collapse
Yes. In fact no other canary / debug build works for me except the old one that you linked to. All the updated ones, and Magisk 21 all result in my phone booting straight to Fastboot. Uninstalling them make the phone boot again. That one from September works fine for some reason?
OhioYJ said:
Yes. In fact no other canary / debug build works for me except the old one that you linked to. All the updated ones, and Magisk 21 all result in my phone booting straight to Fastboot. Uninstalling them make the phone boot again. That one from September works fine for some reason?
Click to expand...
Click to collapse
I have had great success in using the Magisk-Modded.zip from the SyberiaOS project, that can be had here:
https://sourceforge.net/projects/syberiaos/files/twrp/Magisk_Modded.zip/download
You might try that and see if it works for you. It should.
verizon CDMA support???
{
"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 out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Instructions:
Follow the instructions on the wiki page of your device https://wiki.lineageos.org/devices/#samsung
Note: You may use Odin instead of Heimdall, for this you will need to rename the recovery image to recovery.img and pack it into a tar archive.
Downloads:
Builds: https://download.lineageos.org
Firmware:
gta4xlwifi: https://lineage.linux4.de/fw_update/gta4xlwifi.html
gta4xl: https://lineage.linux4.de/fw_update/gta4xl.html
GApps: https://wiki.lineageos.org/gapps.html
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:
Support
Telegram group
Contributors
Linux4, haggertk, programminghoch10
Source Code: https://github.com/LineageOS
Kernel source: https://github.com/LineageOS/android_kernel_samsung_gta4xl
reserved
reserved
You are the best. Really appreciate your efforts.
Thank you so much!
Upgrading the Samsung Firmware Without Losing Your Data, Apps & Settings
Thanks for supporting this device & others @Linux4.
Linux4 said:
...Follow the instructions on the wiki page of your device...
Click to expand...
Click to collapse
In both wiki pages Installation and Upgrade to a higher version of LineageOS (e.g. lineage-18.1 -> lineage-19.1) it says in a red box:
WARNING: Before following these instructions please ensure that the device is currently using Android 12 firmware.
Click to expand...
Click to collapse
And you created a convenient custom Samsung Android 12 firmware package that one can use without losing Data, apps & settings: Update Firmware on Samsung Galaxy Tab S6 Lite (Wi-Fi) (gta4xlwifi)
It's also a much smaller download than the full Samsung OS.
Why not include a link to it in the OP of this thread?
For example haggertk did that for the Galaxy S5 klte* family:
haggertk said:
Downloads:
Lineage - https://download.lineageos.org/
Firmware - https://www.androidfilehost.com/?w=files&flid=325192
Click to expand...
Click to collapse
***
curiousrom said:
Upgrading the Samsung Firmware Without Losing Your Data, Apps & Settings
Why not include a link to it in the OP of this thread?
Click to expand...
Click to collapse
Done, thanks for the suggestion
Cool, thanks for all your work Linux4!
- Am I correct that you need to flash the firmware, lineage 19.1, gapps 12 arm 64 in one session before booting for the first time in order to not have to factory reset?
- Does one have to flash firmware before first boot in heimdall, then lineage (via adb), then gapps (via adb)?
- can the android 12 firmware be kept when downgrading back to lineage 18/ can I flash it and use it with lineage 18 before installing lineage 19?
SvenHee said:
Cool, thanks for all your work Linux4!
- Am I correct that you need to flash the firmware, lineage 19.1, gapps 12 arm 64 in one session before booting for the first time in order to not have to factory reset?
- Does one have to flash firmware before first boot in heimdall, then lineage (via adb), then gapps (via adb)?
- can the android 12 firmware be kept when downgrading back to lineage 18/ can I flash it and use it with lineage 18 before installing lineage 19?
Click to expand...
Click to collapse
I'm not Linux4, but I'll still try to answer.
1. Yes, you flash the firmware and all those in one session via Lineage recovery and then you restart
2. You have to use heimdall first, then flash recovery with it and then flash lineage and gapps with adb
3. Don't know
Also sorry if something is incorrect, I'm new to the ROM world and I just flashed Lineage today and this is what I did
- sheep
hey....why there is no lineage os 19.1 for lte version?
And Is it okay to flash linux4's link in my tab s6 lite lte which runs on oneui4.1?
I need to flash my tab before leaving for collge...please reply
lol69 96 said:
hey....why there is no lineage os 19.1 for lte version?
And Is it okay to flash linux4's link in my tab s6 lite lte which runs on oneui4.1?
I need to flash my tab before leaving for collge...please reply
Click to expand...
Click to collapse
DO IT YOUR OWN RISK.
Truelan said:
DO IT YOUR OWN RISK.
Click to expand...
Click to collapse
Yea Ik the risks.I guess it's an upgrade rather than downgrade but problem is it will have lower security patch.Will it pose any risk?
@devs Ty for your work! I just flashed firmware and upgraded from los 18.1 to last nightly (lineage-19.1-20220511-nightly-gta4xlwifi-signed.zip).
I just want to report a minor bug: Mostly (not always) I can't add an installed app (drag and drop) to the screen.
Thanks for the work!
Now that LOS 19 has official support, can I expect the S Pen issues to be resolved?
Last time I installed an unofficial port of the ROM there were some major issues around responsiveness and lag when using the S Pen and it is critical to me (student).
Hi, how to root this rom?
Nevermind, just sideload magisk from adb. Anyway, the rom is great, the pen is working well. I confirm the bug that you can't drag app on the homescreen. Also, I'm facing a weird bug: when I lock the screen through the power button, sometimes the tablet stops responding, pressing the power button does nothing and the screen stays black, I have to force restart with power + volume down
P615. Recovery flashed by Odin and next sideload with ROM, Gapps, Lygisk. Work fine since flash. Zero reboots, crashes, etc.
Bug report
LineageOS version: lineage-19.1-20220525-nightly-gta4xlwifi-signed
LineageOS Download url: https://mirrorbits.lineageos.org/fu...e-19.1-20220525-nightly-gta4xlwifi-signed.zip
Gapps version: not installed
The bug appears after a fresh clean installation. I've installed the required firmware before the update.
I've rebooted after I've first seen the issue.
Modifications: none, it's pure LOS installation without anything else
Here's what happens:
I'm german and therefore sometimes I write in german, sometimes in english. I like to switch my keyboard according to the language I'm using.
With two keyboard languages activated in settings, I cannot get off the lock screen, because the keyboard doesn't appear and it looks weird over all.
I've recorded the screen right after a completely fresh installation and after finishing the setup wizard. First I switch to the lock screen, which I get out of with my password. Then after activating the second language, I cannot get out of the lock screen anymore.
I normally have another setup. I normally use the microG version and have Lygisk installed. But I'll keep my tablet in the current state for the next 2, maybe 3 days to be able to give more information if required.
Same keyboard issue here, when switching to digits --> blank screen.
Another thing. The installation is the same as in my bug report from yesterday.
I've started testing a few things. I use ACCA from the Fdroid repos for battery management. In LineageOS 18.1 the kernel supported battery idle mode, now with LOS 19 it looks like this isn't supported anymore.
Would you please implement this again? It's really helpful for a good battery management so it doesn't charge up to 100%.
New update for LTE version from 28th may.
{
"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 out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Instructions :
https://wiki.lineageos.org/devices/kebab
Downloads :
https://download.lineageos.org/kebab
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:
Thank you for making this. Lineageos's been a blessing ever since the oxygenos became what it is now.
I want to migrate from another rom and wanted to ask if lineageos 19 uses oos12 or oos11 firmware.
Artifter said:
Thank you for making this. Lineageos's been a blessing ever since the oxygenos became what it is now.
I want to migrate from another rom and wanted to ask if lineageos 19 uses oos12 or oos11 firmware.
Click to expand...
Click to collapse
I believe you can find the answer for that in the installation instructions.
Thank you very much for your effort!
I would like to pose a question, although it's not specifically related to LOS 19, is there a way to bypass SafetyNet without rooting the phone? I've always found very irritating to have this kind of problems with some apps, when the turth is one can expect a better longlife service with LOS than with the official OS. Yes, I know it doesn't have to do with LOS but it would be the cherry on top of the cake.
Hello, can i use twrp instead of LOS recovery or is mandatory? Just wondering, thank you.
Thank you for the update !
Sry am now on Android 13 Evolution X
Unfortunately the update does not work on my device. Entering the new recovery build just ends up in a blank screen and booting the ROM enters the crash dump mode. Updating the device firmware to the latest state did not help either.
Reverted back to the other slot without any issue, so no harm was done.
@Draylin Did you follow these steps https://wiki.lineageos.org/devices/kebab/fw_update before installation of LinageOS 12.1?
Do i have DDR4 or DDR5?
Code:
D:\adb>adb shell getprop ro.boot.ddr_type
1
D:\adb>adb shell cat /proc/devinfo/ddr_type
cat: /proc/devinfo/ddr_type: No such file or directory
D:\adb>
edit:
found: 0 for LPDDR4X RAM and 1 for LPDDR5 RAM
right?
exthomeboy said:
Sry am now on Android 13 Evolution X
Click to expand...
Click to collapse
don't care didn't ask
Draylin said:
Unfortunately the update does not work on my device. Entering the new recovery build just ends up in a blank screen and booting the ROM enters the crash dump mode. Updating the device firmware to the latest state did not help either.
Reverted back to the other slot without any issue, so no harm was done.
Click to expand...
Click to collapse
You can also try to flash dtbo, https://mirrorbits.lineageos.org/full/kebab/20220825/dtbo.img. B-but if new recovery boots then you'll want to flash FW to both slots instead of just one.
I added flashing dtbo to wiki, not like it's going to hurt anyway.
If you follow all the step-by-step instructions (https://wiki.lineageos.org/devices/kebab/upgrade), the upgrade process works perfectly.
Many thanks to LuK1337 and the whole Lineage team for their work.
I am doing a complete reset and can't make it boot to lineageos19 at all.
Steps:
1 - Flash dbto
2 - Flash recovery.18.1
3 - Sideload lineageos 19
4 - Reboot to recovery again to install MindGapps
5 - Blank, I can't go again to the recovery screen at all
back2live said:
@Draylin Did you follow these steps https://wiki.lineageos.org/devices/kebab/fw_update before installation of LinageOS 12.1?
Click to expand...
Click to collapse
Yes, I followed these steps.
@LuK1337 Thank you for your response. I flashed the linked dtbo to the new slot, but this did not help. Since it seems to be working fine for others, I think the error must be somwhere on my side.
Draylin said:
Yes, I followed these steps.
@LuK1337 Thank you for your response. I flashed the linked dtbo to the new slot, but this did not help. Since it seems to be working fine for others, I think the error must be somwhere on my side.
Click to expand...
Click to collapse
I had the same problem, but forgot flash the vendor data before.
I am now installing lineageos18 again and try to upgrade.
Draylin said:
Yes, I followed these steps.
@LuK1337 Thank you for your response. I flashed the linked dtbo to the new slot, but this did not help. Since it seems to be working fine for others, I think the error must be somwhere on my side.
Click to expand...
Click to collapse
Just wondering but what firmware version did you flash?
LuK1337 said:
Just wondering but what firmware version did you flash?
Click to expand...
Click to collapse
I used the latest file from the linked site: OnePlus8TOxygen_15.E.31_OTA_0310_all_2202182356_edc3927f4900402e.zip and extracted it using the payload dumper.
Draylin said:
I used the latest file from the linked site: OnePlus8TOxygen_15.E.31_OTA_0310_all_2202182356_edc3927f4900402e.zip and extracted it using the payload dumper.
Click to expand...
Click to collapse
That's OxygenOS 11 firmware.
LuK1337 said:
That's OxygenOS 11 firmware.
Click to expand...
Click to collapse
Could well be, the filename is not very telling to me. I just assumed that the firmware provided would be the latest one.