{
"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 here
Downloads:
Builds: https://lineage.linux4.de
GApps: MindTheGapps
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
DO NOT Report bugs if you're using TWRP
DO NOT Report bugs while having Magisk installed (especially with Zygisk enabled)
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, programminghoch10
Source Code: https://github.com/LineageOS
Kernel source: https://github.com/LineageOS/android_kernel_samsung_gta4xl/tree/lineage-19.1
Requirements:
Any R based firmware installed on your device.
Pre-Install Instructions
Warning: The following instructions will unlock the bootloader and wipe all userdata on the device.
Connect the device to a Wi-Fi network.
Enable Developer Options by pressing the “Build Number” option in the “Settings” app within the “About” menu
From within the Developer options menu, enable OEM unlock.
Power off the device, and boot it into download mode:
With the device powered off, hold Volume Down + Volume Up and connect USB cable to PC.
Now, click the button that the onscren instructions coorelate to “Continue” and/or “Unlock Bootloader”.
Your device will reboot, you may now unplug the USB cable from your device.
The device will demand you format userdata, please follow the onscreen instructions to do so.
Run through Android Setup skipping everything you can, then connect the device to a Wi-Fi network.
Re-enable Development settings by clicking the “Build Number” option 10 times, in the “Settings” app within the “About” menu, and verify that “OEM Unlock” is still enabled in the “Developer options” menu.
Installing LineageOS for the first time
Flash lineage recovery
Only the provided lineage recovery will be supported,
using TWRP might result in a possible data loss!!
If using Odin rename the lineage recovery image for your model to recovery.img and add it to a .tar archive using e.g 7zip.
If using Heimdall use: heimdall flash --RECOVERY recovery.img --no-reboot
Boot lineage recovery
IMPORTANT: Do not boot into system again before booting recovery, or system will restore stock recovery!
If using Odin untick auto-reboot before flashing.
After flashing reboot by pressing Volume Down and Power for approximately 7 seconds,
immediately hold Volume Up and Power to boot recovery
IMPORTANT: As of OneUI 3 your device needs to be connected to a PC via USB cable in order to be able to
boot recovery via Volume Up, Bixby and Power.
Factory reset using Factory reset -> Format data/factory reset
Warning: Unlike TWRP this will also erase internal storage!
Sideload LineageOS by enabling sideload via Apply Update -> Apply from ADB
Then run adb sideload <path to your lineage.zip> on your PC
Optional:
Sideload GApps and magisk by repeating above step
with their zip/apk
Magisk
I strongly recommend to use Lygisk instead,
which is a fork of Magisk that aims to improve support for devices with FBE that can't (and shouldn't anyways!) decrypt userdata in recovery,
this will also fix OTAs getting stuck while having installed Magisk.
Features
SELinux enforcing
AES-256-XTS FBE encryption
Latest Linux 4.14.x kernel
Known issues
LineageOS specific features like livedisplay (for now)
You tell me
I am on your unofficial 18 and this just pop up in updater, is it safe to do OTA? Thanks for your efforts!
fzzt said:
I am on your unofficial 18 and this just pop up in updater, is it safe to do OTA? Thanks for your efforts!
Click to expand...
Click to collapse
Always follow this rule of thumb: it is never safe to dirty flash a completely different build on top of an older build (i.e. flashing 19.0 on top of 18.1, or 18.1 on top of 17.1, etc.). At best, you'll find yourself having random problems all over the place; at worst, the ROM will refuse to load. Best thing to do whenever going from one major release to another (or from one completely different ROM to another) is backup your apps and data, wipe data and caches and perform a clean flash, then restore your apps and data. It's a fair bit of work, to be sure, but it's the best way to avoid problems.
Sim card dont work, IMEI dont show, gapps cant install. Any ideas?
electro_vinyl said:
Sim card dont work, IMEI dont show, gapps cant install. Any ideas?
Click to expand...
Click to collapse
About the SIM issue, there's two things:
1. (more likely) You flashed the wrong build (gta4xlwifi instead of gta4xl) or in other words, flashed the WiFi only version firmware.
2.(Unlikely but could happen) You corrupted your baseband somehow as I had a similar situation with my Redmi Note 9 with a corrupted baseband so basically the IMEI was all zeros. That was also the reason why the SIM card didn't work.
You could try to install the original firmware with odin and check functionality and try again.
About the gapps issue
Did you install it for the correct architecture (arm64 not arm)?
Does it show error messages?
Macuway said:
About the SIM issue, there's two things:
1. (more likely) You flashed the wrong build (gta4xlwifi instead of gta4xl) or in other words, flashed the WiFi only version firmware.
2.(Unlikely but could happen) You corrupted your baseband somehow as I had a similar situation with my Redmi Note 9 with a corrupted baseband so basically the IMEI was all zeros. That was also the reason why the SIM card didn't work.
You could try to install the original firmware with odin and check functionality and try again.
About the gapps issue
Did you install it for the correct architecture (arm64 not arm)?
Does it show error messages?
Click to expand...
Click to collapse
With the latest build, it's all fixed!
Installed Lineage 19 last weekend on my P-610. You can flash the rom.zip, GApps and Magisk in Recovery from SD-card, so no need to sideload with adb. I have a problem with Google Playstore, it lags a lot (pending...) and installing an app like Gmail takes a long time. Now it even stopped working. Will try it later with NikGApps for Android S
Hi, it seems audio is not working.
It's just me?
Any help please.
M
minoltista said:
Hi, it seems audio is not working.
It's just me?
Any help please.
M
Click to expand...
Click to collapse
Are you on today's build already?
If so try again with that please - your device might be hw revision 9 which uses different audio drivers and wasn't supported in my kernel until today
Also could check the output of adb shell getprop ro.boot.revision to confirm it's rev 9
Linux4 said:
Are you on today's build already?
If so try again with that please - your device might be hw revision 9 which uses different audio drivers and wasn't supported in my kernel until today
Also could check the output of adb shell getprop ro.boot.revision to confirm it's rev 9
Click to expand...
Click to collapse
Just installed and it works! Thanks !!!
guys how do you flash this? I follow all the steps and when I do adb sideload <lineage os> it fails at 47%?????
error 21 log on the tab
langamer101 said:
guys how do you flash this? I follow all the steps and when I do adb sideload <lineage os> it fails at 47%?????
error 21 log on the tab
Click to expand...
Click to collapse
got it working guys. no need to help anymore.
Does anyone know why gboard force closes every time i try to install? I cleared all storage, played with permissions. Nothing worked.
First of all, I want to say thank to @Linux4 for this release Secondly, I want to ask comrads how to install MicroG on this build? If you can step by step, I'm new to custom firmware
how is newest recovery
Screenshots please
Working nicely, I'm currently getting a weird issue with the 2021-11-27 gta4xl build.
It's extremely weird but with quiet songs there's some kind of audio ducking going on.
Song it was most obvious on was Air - Bad and Sad 4.2 Vagabond Demo for example but it sounds like it's trying to cut out the audio or something.
Device was bought a few days ago so I'm guessing it'll be the latest hw revision.
lobotomite said:
Working nicely, I'm currently getting a weird issue with the 2021-11-27 gta4xl build.
It's extremely weird but with quiet songs there's some kind of audio ducking going on.
Song it was most obvious on was Air - Bad and Sad 4.2 Vagabond Demo for example but it sounds like it's trying to cut out the audio or something.
Device was bought a few days ago so I'm guessing it'll be the latest hw revision.
Click to expand...
Click to collapse
I have the same thing with any sound on the tablet This is especially noticeable when playing songs on spotify.
Related
LineageOS is a free, community built, aftermarket firmware distribution of Android 8.1.0 (Oreo), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
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. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for Lineage OS is available in the LineageOS Github repo. And if you would like to contribute to Lineage OS, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
NOTE: This build is unofficial, don't report bugs to the official LineageOS bug tracker.
HOW TO FLASH
Download the ROM from here
Download GAPPS from here
Install TWRP recovery from this thread
Boot to recovery
Wipe Data/Factory reset
Flash LineageOS
Flash GAPPS
Wipe Cache/Dalvik
Boot to system
What works
Audio
Camera
RIL (calls, sms, etc)
GPS
Bluetooth
WiFi
Everything else not listed below
What doesn't work
HDR
WiFi Hotspot
Wireless display
Before asking any question read the FAQ below
Big thanks to @voidzero for letting me use his server to build and for the initial device tree
XDA:DevDB Information
[ROM][UNOFFICIAL][m8qlul] LineageOS 15.1 for HTC One M8s, ROM for the HTC One (M8)
Contributors
root-expert, voidzero
Source Code: https://github.com/M8s-dev/
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.10.x
ROM Firmware Required: M firmware base
Version Information
Status: Stable
Beta Release Date: 2018-06-18
Created 2018-06-18
Last Updated 2018-10-27
Changelog
Code:
[B][U]26 October 2018[/U][/B]
* Instagram videos fixed
Code:
[B][U]18 October 2018[/U][/B]
* August/September/October ASB merged
* Use sdFAT instead of exFAT
* Reduce GPS fix time
* Increased speaker volume
* Increased microphone volume
* Increased upper earpiece volume when in-call
* Enabled HDR
* Fixed wakelock
Code:
[B][U]26 July 2018[/U][/B]
* July Android Security updates
* Kernel updated from tag 3.10.49 to tag 3.10.108
* Bluetooth now recognises the correct bt address
* Use low-latency as primary output for notifications and ringtone
* Switched SELinux to enforcing
* When usb composition is on "charge only" adb works
* Enabled audio offloading
* Added the option to disable Double Tap to wake gesture
* Added option to unlock phone with a gesture (you can find it under gestures tab)
* Used newer WiFi configuration files (hope that fixes WiFi problems)
* The name "HTC One M8s" is shown to your pc when connected instead of "Android Phone"
Code:
[B][U]20 June 2018[/U][/B]
[LIST]
[*]Fixed headphones microphone
[/LIST]
Code:
[B][U]18 June 2018[/U][/B]
[LIST]
[*]Initial commit
[/LIST]
Frequently Asked Questions (FAQ)
Q: I flashed the ROM and I'm getting random reboots and crashes
A: Ensure that before flashing this ROM your last stock rom was Android version 6.0. If not follow the instructions on the post below
Q: I found a bug, what should I do?
A: Describe in this thread the issue as best as you can and include steps to reproduce.
Also include a logcat taken the time that the bug happens.
If you had a random reboot don't bother taking a logcat instead pull /sys/fs/pstore/console-ramoops file and atach it to your post.
Q: I want to root this ROM. Should I flash something?
A: Either download su addon from https://download.lineageos.org/extras or flash Magisk.
If you are coming from CM12.1 (Just like I did) then follow these steps
NOTE: If you do not follow these steps, your final Oreo ROM (LOS 15) will crash, you'll suffer randoms reboots and instability problems due to incompatible radio / HTC firmware. This whole update process to Stock 6.0 can take up to 4 hours! So make sure you have the time to do everything correctly, don't cut corners.
I suffered
1. Create a full backup of your ROM using TWRP (v2.8 or v3.0.2.0), Copy your INTERNAL STORAGE and SD Card contents to PC .
During the upgrade from "CM12.1 > 5.0.1 Stock > 6 Stock > LOS 15" you WILL lose your internal data! (because of bootloader relock & unlock again)
2. Relock your bootloader; (Make sure you are using the htc_fastboot.exe)
Turn off phone
Go into bootloader (Hold down VOL DOWN+Power button
Connect USB and enter Fastboot (Should show as FASTBOOT USB)
Open commandprompt;
Code:
htc_fastboot oem lock
The phone should restart and show up as ***RELOCKED***
3. Get your matching RUU from https://ruu.lalleman.net/HTC_M8S(QL_UL)/
If you dont know which RUU to get, follow this thread; https://forum.xda-developers.com/ht...lp-thread-htc-one-m8s-to-stock-howto-t3190238 (M8sQL_UL > Firmware (Expert)>Firmware Crypted (Original HTC))
If you get the "Device halted due to Large Image update fail" error during installation, just try another RUU - but make sure it matches your CID.
I got it working using a "signed" version. The "combined-signed" version did not work for me. Your mileage may very.
Click to expand...
Click to collapse
4. In Android Stock (5.0.1), continue the setup and after that go to: Settings > Software updates (At the bottom) > Check for updates
At first I only got 2 APP updates: "HTC Sense" and some other app (cant remember). Update both apps and reboot.
After a reboot check again for updates. Now you get a ~400Mb update. Download and install.
After the first update check again for updates. Now you get a ~1.23Gb update (Update to Marshmallow, Part 1 of 2). Download and install.
After that check again, and now you'll get a ~700Mb update (Update to Marshmallow, Part 2 of 2.)
That's it for going back to the most recent stock version. You now have Android 6.0 Stock running.
To install TWRP (if you want to flash LOS 15)
1. Unlock your bootloader again.
Go to https://www.htcdev.com/bootloader/ and follow the instructions.
2. Flash TWRP.
Code:
htc_fastboot flash recovery twrp-recovery-image-name-and-version.img
After that:
Wipe Cache/Dalvik, Data and System
Install LOS15
Wipe Dalvik again
Flash Gapps
Wipe Dalvik
Boot
Say thank you to @root-expert for keeping this phone alive with the development and @voidzero for providing the build-environment / mirrors
- Jeroen
Nice job! Great work on the rom and keeping the one m8s alive!
New build up!
Headphones microphone is now fixed.
Grab it as usual from here
-Chris
For the users who want to remove the"root icon" ( the status bar), there is no setting to disable it.
{
"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"
}
To remove it:
Connect your M8s to PC with USB
Open CMD
Code:
adb shell settings get secure icon_blacklist
The output is:
Code:
[COLOR="Red"]rotate,headset[/COLOR]
Now enter the output + su
Code:
adb shell settings put secure icon_blacklist rotate,headset,[COLOR="red"]su[/COLOR]
And after that:
Code:
adb reboot
Now the "#" icon is gone from the status bar.
- Jeroen
My battery time is very bad. Clean install with everything wiped. Rom is slick, clean, easy, snappy. Can't install shortcut for greenify. Xposed installed without problems, pico gapps, I like this rom. Only battery life is bad. I might try reinstalling when I get a chance to see what happens. All in all, slick rom, kudos to Developer !
brunkonjaa said:
My battery time is very bad. Clean install with everything wiped. Rom is slick, clean, easy, snappy. Can't install shortcut for greenify. Xposed installed without problems, pico gapps, I like this rom. Only battery life is bad. I might try reinstalling when I get a chance to see what happens. All in all, slick rom, kudos to Developer !
Click to expand...
Click to collapse
Hello, thanks for flashing. In what way you battery life is bad? When you use it or when it's idle?
I suggest you to run the ROM for 1-2 days and take a look at battery statistics.
-Chris
root-expert said:
Hello, thanks for flashing. In what way you battery life is bad? When you use it or when it's idle?
I suggest you to run the ROM for 1-2 days and take a look at battery statistics.
-Chris
Click to expand...
Click to collapse
I'll run it for a few days and screenshot battery stats. Then I'll reinstall the whole thing and compare new batery stats with old ones. Maybe if I format data prior to flashing things will be different
brunkonjaa said:
I'll run it for a few days and screenshot battery stats. Then I'll reinstall the whole thing and compare new batery stats with old ones. Maybe if I format data prior to flashing things will be different
Click to expand...
Click to collapse
I don't believe you have to do that. The only requirement is that your last stock android version was Android 6.0
Post battery statistics here
After using for about 13hours work Perfect. Ok 1 time i got crash but i try to install a same time 5 apps + download about 2gb for sekund 2 apps + copy via usb to sd some files + copy via usb to internal memory another thing + run google play store update apps just installed :silly: :silly:
But otherwise work realy great wasnt any problems.
Oh one more thing to install rom via TWRP NEEEEEED twrp-3.2.1-0-m8qlul.img at twrp-3.0.2-0-m8ql.img get error 7
Of course except
HDR
Wireless display
SELinux
WiFi hotspot
You tell me...
GeoEgbA said:
After using for about 13hours work Perfect. Ok 1 time i got crash but i try to install a same time 5 apps + download about 2gb for sekund 2 apps + copy via usb to sd some files + copy via usb to internal memory another thing + run google play store update apps just installed :silly: :silly:
But otherwise work realy great wasnt any problems.
Oh one more thing to install rom via TWRP NEEEEEED twrp-3.2.1-0-m8qlul.img at twrp-3.0.2-0-m8ql.img get error 7
Of course except
HDR
Wireless display
SELinux
WiFi hotspot
You tell me...
Click to expand...
Click to collapse
Hello, can you give me the error of twrp? If it is an assert error i'll fix it real quick and upload a new TWRP image.
-Chris
Problem with google play services
Hi
first thank you very much for your great work. :good:
I've got a problem with the Google Play Services / TWRP / GAPPS
Okay first what I've done:
1. followed your steps until installation of gapps
2. recognized the error: Failed to mount '/persist' (GApps: ARM64/8.1/nano)
3. ignored the error
4. system is running without problems
5. try to start play store -> "Google Play Services Has stopped" message continually popping up
Do you have any idea?
Greetings and thank you in advance
root-expert said:
Hello, can you give me the error of twrp? If it is an assert error i'll fix it real quick and upload a new TWRP image.
-Chris
Click to expand...
Click to collapse
Sure give me 5 min
root-expert said:
Hello, can you give me the error of twrp? If it is an assert error i'll fix it real quick and upload a new TWRP image.
-Chris
Click to expand...
Click to collapse
Sure give me 5 min
Click to expand...
Click to collapse
View attachment recovery.log
Try by twrp-3.0.2-0-m8ql.img
View attachment twrp-3.0.2-0-m8ql.zip
GeoEgbA said:
View attachment 4533829
Try by twrp-3.0.2-0-m8ql.img
View attachment 4533830
Click to expand...
Click to collapse
Look again on the flashing instructions. I state you should flash a TWRP recovery from one specific thread. YOu are using outdated recovery. Use the new one and it will fix this error
EDIT: I read agian your initial post, and yes you need the newer recovery to flash the rom and i said i state on flashin instructions
-Chris
monkyMatys said:
Hi
first thank you very much for your great work. :good:
I've got a problem with the Google Play Services / TWRP / GAPPS
Okay first what I've done:
1. followed your steps until installation of gapps
2. recognized the error: Failed to mount '/persist' (GApps: ARM64/8.1/nano)
3. ignored the error
4. system is running without problems
5. try to start play store -> "Google Play Services Has stopped" message continually popping up
Do you have any idea?
Greetings and thank you in advance
Click to expand...
Click to collapse
Hello,
Ensure that you flashed GAPPS straight after flashing the ROM WITHOUT rebooting to system. If you reboot to system and then flash GAPPS you'll have problem and crashes like you do. Also ensure that your previous stock andorid version was android 6.0. If not follow the instructions on this thread to revert back to stock and then try to flash the ROM
-Chris
root-expert said:
Look again on the flashing instructions. I state you should flash a TWRP recovery from one specific thread. YOu are using outdated recovery. Use the new one and it will fix this error
EDIT: I read agian your initial post, and yes you need the newer recovery to flash the rom and i said i state on flashin instructions
-Chris
Click to expand...
Click to collapse
Yes yes that why i wrote that need 3.2.1..0 becouse on 3.0.2.0 get error 7. I flash 3.2.1.0 anf LOS and work great for 15h now sorry for confusion
How long should the first boot take? i followed the instructions, twrp 3.2.1 gave a /persist error but everything else seemed fine. its been 20m and im at the lineage os boot screen.
{
"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
Boot to recovery
Flash the latest build
Boot to recovery again
Flash gapps
Reboot
Downloads :
Builds : https://download.lineageos.org/pioneer
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 /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:
XDA:DevDB Information
[ROM][OFFICIAL][pioneer][9] LineageOS 16.0, ROM for the Sony Xperia XA2
Contributors
LuK1337
Source Code: https://github.com/LineageOS
ROM OS Version: Windows 8 Mobile
ROM Kernel: Linux 4.x
Version Information
Status: Testing
Created 2018-08-30
Last Updated 2020-02-28
How to flash latest firmware
[ protip: 20191010+ builds require 50.2 FW (at least bluetooth, dsp, modem from it) If you're still running 50.1 you can flash this package in TWRP: https://androidfilehost.com/?fid=4349826312261716572 unless you're fine with having partially broken audio and broken Egistec fingerprint sensor ;3 ]
However if you want to flash whole firmware package onto both slots, you can follow the guide below:
1. Download latest firmware with XperiFirm.
NOTE: When using mono XperiFirm will fail to unpack the firmware, you can do it manually using following commands:
Code:
for f in FILE_*; do unzip $f; done
unzip boot.zip -d boot
2. Go to the directory where the firmware got downloaded to and remove following files:
- boot_X-FLASH-ALL-18AE_0x00.hash
- boot_X-FLASH-ALL-18AE.sin
- persist_X-FLASH-ALL-18AE_0x00.hash
- persist_X-FLASH-ALL-18AE.sin
- system_other_X-FLASH-ALL-18AE_0x00.hash
- system_other_X-FLASH-ALL-18AE.sin
- system_other_X-FLASH-ALL-9B8D_0x00.hash
- system_X-FLASH-ALL-18AE_0x00.hash
- system_X-FLASH-ALL-18AE.sin
- system_X-FLASH-ALL-9B8D_0x00.hash
- userdata_X-FLASH-CUST-18AE.sin
- vendor_X-FLASH-ALL-18AE_0x00.hash
- vendor_X-FLASH-ALL-18AE.sin
- vendor_X-FLASH-ALL-9B8D_0x00.hash
3. Turn off your phone, hold vol dn and plug in the USB cable, the screen should be off and green LED lit.
4. Run Newflasher, it'll flash entire FW to your current slot then unplug the USB cable and power on your phone.
5. Turn off your phone, hold vol up and plug in the USB cable, the screen should be off and blue LED lit.
6. Enter this command: `fastboot getvar current-slot`, it should return something like this:
current-slot: _b
Finished. Total time: 0.001s
7. Now switch to the opposite slot by entering command: `fastboot set_active a` if the current slot is `_b` or `fastboot set_active b` if its `_a`, you should see this:
Setting current slot to 'a'...
OKAY [ 0.012s]
Finished. Total time: 0.014s
or
Setting current slot to 'b'...
OKAY [ 0.012s]
Finished. Total time: 0.014s
8. Unplug usb cable and repeat steps: 3, 4
9. Profit?
Jozinek said:
Reccomended Gapps for this build?
Click to expand...
Click to collapse
dunno, just try any gapps you want.
btw I recommend downloading new build, I fixed wvm and camera no longer takes an eternity to launch.
Does it use 4.9 kernel or 4.4?
Casserole said:
Does it use 4.9 kernel or 4.4?
Click to expand...
Click to collapse
4.4
Unable to boot?
hello, thanks for this build. I have flashed the latest build in TWRP but for some reason keep getting thrown back into TWRP after flashing everything and rebooting. I'm not entirely sure why this is occurring.
techboy11 said:
hello, thanks for this build. I have flashed the latest build in TWRP but for some reason keep getting thrown back into TWRP after flashing everything and rebooting. I'm not entirely sure why this is occurring.
Click to expand...
Click to collapse
Stop flashing twrp lol.
LuK1337 said:
Stop flashing twrp lol.
Click to expand...
Click to collapse
I did not flash TWRP at first, but it still threw me into the default Lineage/Android recovery. Flashing TWRP or not doesn't make a difference for me.
Edit: I should mention the recovery screen I get without flashing TWRP says that my data is corrupt and I should try factory resetting or try booting again. Doing a factory reset option brings it to the same screen again.
techboy11 said:
I did not flash TWRP at first, but it still threw me into the default Lineage/Android recovery. Flashing TWRP or not doesn't make a difference for me.
Edit: I should mention the recovery screen I get without flashing TWRP says that my data is corrupt and I should try factory resetting or try booting again. Doing a factory reset option brings it to the same screen again.
Click to expand...
Click to collapse
Try fastboot -w reboot.
LuK1337 said:
Try fastboot -w reboot.
Click to expand...
Click to collapse
That worked. Now boots. Thanks for your help!
Thanks dude
Thanks for your work.
Front camera picture is upside down and i am unable to make photos with it.
EDIT: Works with Footej camera!
Schritti said:
Thanks for your work.
Front camera picture is upside down and i am unable to make photos with it.
EDIT: Works with Footej camera!
Click to expand...
Click to collapse
Yeah it's a temporary camera app until Snap is back so I won't bother figuring out what's wrong with it.
Do you publish changelog for new versions somewhere? Would be nice to know the changes.
Sent from my Sony H3113 using XDA Labs
Schritti said:
Do you publish changelog for new versions somewhere? Would be nice to know the changes.
Sent from my Sony H3113 using XDA Labs
Click to expand...
Click to collapse
No, I don't.
please fix screen mirroring function
i have found this
https://www.youtube.com/watch?v=1wIM67kVVL8
instructions:
1. change the following code line in /system/etc/wfdconfig.xml:
ContentProtection
Valid1/Valid
to
ContentProtection
Valid0/Valid
2. then add a line in /system/build.prop after "persist.debug.wfd.enable=1"
persist.debug.wfd.appmonitoring=1
3. and then from ADB
"adb shell su setprop persist.debug.wfd.appmonitoring 1"
4. reboot your phone and it will work
thanks
zsolt64555 said:
please fix screen mirroring function
i have found this
https://www.youtube.com/watch?v=1wIM67kVVL8
instructions:
1. change the following code line in /system/etc/wfdconfig.xml:
ContentProtection
Valid1/Valid
to
ContentProtection
Valid0/Valid
2. then add a line in /system/build.prop after "persist.debug.wfd.enable=1"
persist.debug.wfd.appmonitoring=1
3. and then from ADB
"adb shell su setprop persist.debug.wfd.appmonitoring 1"
4. reboot your phone and it will work
thanks
Click to expand...
Click to collapse
yeah i need to figure out a way to test it without leaving my room first.
LuK1337 said:
yeah i need to figure out a way to test it without leaving my room first.
Click to expand...
Click to collapse
THX your hard work!
Keep it Up.
Hi
Everything is working on latest build what i probed,
only the video playback is lagging
the smaller resolution is ok, but the HD and full HD playing is lagging with youtube app, and also in browser.
zsolt64555 said:
Hi
Everything is working on latest build what i probed,
only the video playback is lagging
the smaller resolution is ok, but the HD and full HD playing is lagging with youtube app, and also in browser.
Click to expand...
Click to collapse
i cant reproduce that, on youtube and twitch with 1080p 60fps everything is smooth, no lags and no glitches
{
"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/voyager
Downloads :
https://download.lineageos.org/voyager
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:
[ protip: These builds require 50.2 FW (at least bluetooth, dsp, modem from it) If you're still running 50.1 you can flash this package in TWRP: https://androidfilehost.com/?fid=4349826312261777345 unless you're fine with having partially broken audio and broken Egistec fingerprint sensor ;3 ]
However if you want to flash whole firmware package onto both slots, you can follow the guide below:
1. Download latest firmware with XperiFirm.
NOTE: When using mono XperiFirm will fail to unpack the firmware, you can do it manually using following commands:
Code:
for f in FILE_*; do unzip $f; done
unzip boot.zip -d boot
2. Go to the directory where the firmware got downloaded to and remove following files:
- boot_X-FLASH-ALL-18AE_0x00.hash
- boot_X-FLASH-ALL-18AE.sin
- persist_X-FLASH-ALL-18AE_0x00.hash
- persist_X-FLASH-ALL-18AE.sin
- system_other_X-FLASH-ALL-18AE_0x00.hash
- system_other_X-FLASH-ALL-18AE.sin
- system_other_X-FLASH-ALL-9B8D_0x00.hash
- system_X-FLASH-ALL-18AE_0x00.hash
- system_X-FLASH-ALL-18AE.sin
- system_X-FLASH-ALL-9B8D_0x00.hash
- userdata_X-FLASH-CUST-18AE.sin
- vendor_X-FLASH-ALL-18AE_0x00.hash
- vendor_X-FLASH-ALL-18AE.sin
- vendor_X-FLASH-ALL-9B8D_0x00.hash
3. Turn off your phone, hold vol dn and plug in the USB cable, the screen should be off and green LED lit.
4. Run Newflasher, it'll flash entire FW to your current slot then unplug the USB cable and power on your phone.
5. Reboot to recovery mode (both Lineage recovery and TWRP will work)
6. Flash https://androidfilehost.com/?fid=4349826312261712574
7. Profit?
First things first...Thank you!
Also, probably a noob question but, I am on 17.1 already, will I have to flash it via Lineage recovery or twrp to test it?
I suppose the update will only work when there is an official version.
hamirali said:
First things first...Thank you!
Also, probably a noob question but, I am on 17.1 already, will I have to flash it via Lineage recovery or twrp to test it?
I suppose the update will only work when there is an official version.
Click to expand...
Click to collapse
Official lineage recovery won't accept my dev-keys so you need to go with TWRP. I don't recommend trying to update data from 17.1 tho.
LuK1337 said:
Official lineage recovery won't accept my dev-keys so you need to go with TWRP. I don't recommend trying to update data from 17.1 tho.
Click to expand...
Click to collapse
I was able to flash Lineage 18, everything seems ok except that the SD card is not visible when in system, however can access it if removed and reinserted.
Can manage.
hamirali said:
I was able to flash Lineage 18, everything seems ok except that the SD card is not visible when in system, however can access it if removed and reinserted.
Can manage.
Click to expand...
Click to collapse
Are you on first or second build?
LuK1337 said:
Are you on first or second build?
Click to expand...
Click to collapse
Oops! first build. Didn't realise there was another. Btw can you please advise on the gapps version. Thanks!
hamirali said:
Oops! first build. Didn't realise there was another. Btw can you please advise on the gapps version. Thanks!
Click to expand...
Click to collapse
No idea about gapps, I don't have them on my current R devices.
LuK1337 said:
No idea about gapps, I don't have them on my current R devices.
Click to expand...
Click to collapse
Successfully flashed and running well without any issues. Thanks!
LuK1337 said:
No idea about gapps, I don't have them on my current R devices.
Click to expand...
Click to collapse
On the 4th build, all seems to be working fine, apart from a small issue that when making calls the dialling screen doesn't appear, but it does successfully place the call. The issue is when I want to close the call (hang up) as that screen hasn't loaded.
Can manage, as usually I just let the other person hang up. Receiving calls is fine.
Otherwise, great work!
hamirali said:
On the 4th build, all seems to be working fine, apart from a small issue that when making calls the dialling screen doesn't appear, but it does successfully place the call. The issue is when I want to close the call (hang up) as that screen hasn't loaded.
Can manage, as usually I just let the other person hang up. Receiving calls is fine.
Otherwise, great work!
Click to expand...
Click to collapse
This sounds like gapps issue. Make sure that phone app is set in Settings -> Apps & notifications -> Default apps.
LuK1337 said:
This sounds like gapps issue. Make sure that phone app is set in Settings -> Apps & notifications -> Default apps.
Click to expand...
Click to collapse
You were absolutely right...issue resolved. Thanks!
Currently on lineage-18.0-20201011 and enjoying the slide out volume panel and enhanced display size setting. Great!
Testing lineage-18.0-20201019 and all seems good. The only small issue I keep having is with the camera, it freezes.... but I do not use it that much anyway.
how to update lineage-18.0-20201019 on LineageOS 18.0 20201018 without deleting
jacky51 said:
how to update lineage-18.0-20201019 on LineageOS 18.0 20201018 without deleting
Click to expand...
Click to collapse
I am no expert, but I don't think we can at this moment update without deleting or wiping out. Usually it takes less than 30 mins for me to update, flash gapps and restore everything else. If you use WhatsApp a lot, remember to back it up.
I will wait for LineageOS 18.0 20201018 to work fine thanks
hamirali said:
I am no expert, but I don't think we can at this moment update without deleting or wiping out. Usually it takes less than 30 mins for me to update, flash gapps and restore everything else. If you use WhatsApp a lot, remember to back it up.
Click to expand...
Click to collapse
lol, just do the same thing as in initial installation except no wipes. Make sure to not skip rebooting to recovery between flashing Lineage and gapps.
LuK1337 said:
lol, just do the same thing as in initial installation except no wipes. Make sure to not skip rebooting to recovery between flashing Lineage and gapps.
Click to expand...
Click to collapse
OK, I was rebooting to recovery between flashing Lineage and gapps, but I was doing an initial wipe before flashing the newer build...
Everything works fine. Thanks for your 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 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 here
Downloads:
Builds: https://exynoobs.github.io/OTA/
GApps: MindTheGapps
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
DO NOT Report bugs if you're using TWRP
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
josip-k
Linux4
Synt4x.93
Source Code: Exynoobs
Kernel source: https://github.com/Exynoobs/android_kernel_samsung_universal9810
Requirements:
Latest firmware
Pre-Install Instructions
Warning: The following instructions will unlock the bootloader and wipe all userdata on the device.
Connect the device to a Wi-Fi network.
Enable Developer Options by pressing the “Build Number” option in the “Settings” app within the “About” menu
From within the Developer options menu, enable OEM unlock.
Power off the device, and boot it into download mode:
With the device powered off, hold Volume Down + Volume Up and connect USB cable to PC.
Now, click the button that the onscren instructions coorelate to “Continue” and/or “Unlock Bootloader”.
Your device will reboot, you may now unplug the USB cable from your device.
The device will demand you format userdata, please follow the onscreen instructions to do so.
Run through Android Setup skipping everything you can, then connect the device to a Wi-Fi network.
Re-enable Development settings by clicking the “Build Number” option 10 times, in the “Settings” app within the “About” menu, and verify that “OEM Unlock” is still enabled in the “Developer options” menu.
Installing LineageOS for the first time
Flash lineage recovery
Only the provided lineage recovery will be supported,
using TWRP might result in a possible data loss!!
If using Odin rename the lineage recovery image for your model to recovery.img and add it to a .tar archive using e.g 7zip.
If using Heimdall use: heimdall flash --RECOVERY recovery.img --no-reboot
Boot lineage recovery
IMPORTANT: Do not boot into system again before booting recovery, or system will restore stock recovery!
If using Odin untick auto-reboot before flashing.
After flashing reboot by pressing Volume Down and Power for approximately 7 seconds,
immediately hold Volume Up, Bixby and Power to boot recovery
boot recovery via Volume Up, Bixby and Power.
Factory reset using Factory reset -> Format data/factory reset
Warning: Unlike TWRP this will also erase internal storage!
Sideload LineageOS by enabling sideload via Apply Update -> Apply from ADB
Then run adb sideload <path to your lineage.zip> on your PC
Optional:
Sideload GApps and magisk by repeating above step
with their zip/apk
This build does not use the stock vendor, instead it's built on top of new trees which have been worked on for some time. The source is on our github, link in OP. You also get a few neat features like fingerprint gestures, and bixby button that actually works with both normal and long press.
I suggest using OpenCamera since stock one has some issues with flash.
These builds are signed with our release keys.
star2lte and crownlte support will come a bit later as i don't own the devices, but they will be supported eventually.
THESE BUILDS HAVE FORCE ENCRYPTION ENABLED, AND ONLY LINEAGE RECOVERY IS SUPPORTED. THESE THINGS WILL NOT CHANGE. IF YOU DON'T USE LINEAGE RECOVERY, AND SUFFER FROM DATA LOSS, DON'T COMPLAIN HERE.
Build uploaded, enjoy
Woah!!! Nice
How did you get OTA to work, I wanna try it too
nice
will try
been trying your work in PE, congrats on that and now curious to try this rom,
if I understood correctly this is your work along with Rob now?
Keep up the good work and thanks once again for reviving our devices
does LTE is supported in this ROM ?
quakze said:
does LTE is supported in this ROM ?
Click to expand...
Click to collapse
LTE/4G works with this ROM
Hey, thank you very much for this ROM, it's really smooth! Everything works except my second SIM.
For the first release this is pretty nice... and ... this is my first experience with Android 12 / LineageOS 19
star2lte build is up as well, find it at the link in the OP
BIG THANKS to the devs... NOW my S9+ will get a new life.
Edit: Did a test with 2 SIMs and only SIM1 is detected - no SIM2 so far... the Rest is really great work!!!
Great Job, Fresh install and my S9+ is (almost) Brand New!
I installed it with Samsung tool Odin recovery Lineage
Installing the rom with a sd card in de recovery, no sideload use! That works great!
Keep up the great work!
Razuuu said:
LTE/4G works with this ROM
Click to expand...
Click to collapse
does not work, JIO which works on only VoLTE.
When accessing the *#*#4636#*#* service menu (Testing) → Phone information, all the toggles for: VoLTE, Video Calling, WiFi Calling, EAB are off and greyed out (unable to be toggled on).
From the ... drop menu → IMS Service Status:
IMS Registration: Not Registered
Voice over LTE: Unavailable
Voice over WiFi: Unavailable
Video Calling: Unavailable
UT Interface: Unavailable
quakze said:
does not work, JIO which works on only VoLTE.
When accessing the *#*#4636#*#* service menu (Testing) → Phone information, all the toggles for: VoLTE, Video Calling, WiFi Calling, EAB are off and greyed out (unable to be toggled on).
From the ... drop menu → IMS Service Status:
IMS Registration: Not Registered
Voice over LTE: Unavailable
Voice over WiFi: Unavailable
Video Calling: Unavailable
UT Interface: Unavailable
Click to expand...
Click to collapse
See my picture
Feels damn fast but no second sim in S9
Can someone tell me why Lineageos Recovery is the only way to go?
And does it bring the same features as TWRP or is it really based for LineageOS?
Thanks for the info!
Since Magisk Guru is working for Google I hear a lot of complains about Magisk 24.
Does anyone have some good experience with Magisk 24 and rooting and hiding?
Mr-Dutch said:
Can someone tell me why Lineageos Recovery is the only way to go?
And does it bring the same features as TWRP or is it really based for LineageOS?
Thanks for the info!
Since Magisk Guru is working for Google I hear a lot of complains about Magisk 24.
Does anyone have some good experience with Magisk 24 and rooting and hiding?
Click to expand...
Click to collapse
I don't know the reasons (time/effort?), but TWRP doesn't support encrypted partitions which this rom forces.
Is there a list of working/non working features in this rom?
I just wanna say : This ROM is amazing, is blazing fast, super easy install flow, no problems at all; I have no seconds SIM to test however, in my phone the "App Switcher" from the bottom nav bar isn't working, I'm the only one? Keep the amazing work @DeHuMaNiZeD
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 13, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Instructions:
Follow the instructions here
Downloads:
Builds: https://lineage.linux4.de
GApps: MindTheGapps
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
DO NOT Report bugs if you're using TWRP
DO NOT Report bugs while having Magisk installed (especially with Zygisk enabled)
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:
Contributors
Linux4
Source Code: https://github.com/LineageOS
Kernel source: https://github.com/Linux4/android_kernel_samsung_gta4xl/tree/lineage-20.0
Pre-Install Instructions
Warning: The following instructions will unlock the bootloader and wipe all userdata on the device.
Connect the device to a Wi-Fi network.
Enable Developer Options by pressing the “Build Number” option in the “Settings” app within the “About” menu
From within the Developer options menu, enable OEM unlock.
Power off the device, and boot it into download mode:
With the device powered off, hold Volume Down + Volume Up and connect USB cable to PC.
Now, click the button that the onscren instructions coorelate to “Continue” and/or “Unlock Bootloader”.
Your device will reboot, you may now unplug the USB cable from your device.
The device will demand you format userdata, please follow the onscreen instructions to do so.
Run through Android Setup skipping everything you can, then connect the device to a Wi-Fi network.
Re-enable Development settings by clicking the “Build Number” option 10 times, in the “Settings” app within the “About” menu, and verify that “OEM Unlock” is still enabled in the “Developer options” menu.
Installing LineageOS for the first time
Flash lineage recovery
Only the provided lineage recovery will be supported,
using TWRP might result in a possible data loss!!
If using Odin rename the lineage recovery image for your model to recovery.img and add it to a .tar archive using e.g 7zip.
If using Heimdall use: heimdall flash --RECOVERY recovery.img --no-reboot
Boot lineage recovery
IMPORTANT: Do not boot into system again before booting recovery, or system will restore stock recovery!
If using Odin untick auto-reboot before flashing.
After flashing reboot by pressing Volume Down and Power for approximately 7 seconds,
immediately hold Volume Up and Power to boot recovery
IMPORTANT: As of OneUI 3 your device needs to be connected to a PC via USB cable in order to be able to
boot recovery via Volume Up and Power.
Factory reset using Factory reset -> Format data/factory reset
Warning: Unlike TWRP this will also erase internal storage!
Sideload LineageOS by enabling sideload via Apply Update -> Apply from ADB
Then run adb sideload <path to your lineage.zip> on your PC
Optional:
Sideload GApps and magisk by repeating above step
with their zip/apk
Features
SELinux enforcing
AES-256-XTS FBE encryption
Known issues
VoLTE/VoWiFi
You tell me
Likely more
If we already have LOS 19.1 and recovery, do we still need to install the new recovery and factory reset?
edit: I renamed the new recovery image to recovery.img and then used 7zip to make recovery.tar and flashed it with Odin. But when I booted to recovery, all I got was a blank screen. Had to reflash the 19.1 recovery to get it back.
Linux4 said:
Requirements:
Any Q, R or S based firmware installed on your device.
Pre-Install Instructions
Warning: The following instructions will unlock the bootloader and wipe all userdata on the device.
Connect the device to a Wi-Fi network.
Enable Developer Options by pressing the “Build Number” option in the “Settings” app within the “About” menu
From within the Developer options menu, enable OEM unlock.
Power off the device, and boot it into download mode:
With the device powered off, hold Volume Down + Volume Up and connect USB cable to PC.
Now, click the button that the onscren instructions coorelate to “Continue” and/or “Unlock Bootloader”.
Your device will reboot, you may now unplug the USB cable from your device.
The device will demand you format userdata, please follow the onscreen instructions to do so.
Run through Android Setup skipping everything you can, then connect the device to a Wi-Fi network.
Re-enable Development settings by clicking the “Build Number” option 10 times, in the “Settings” app within the “About” menu, and verify that “OEM Unlock” is still enabled in the “Developer options” menu.
Installing LineageOS for the first time
Flash lineage recovery
Only the provided lineage recovery will be supported,
using TWRP might result in a possible data loss!!
If using Odin rename the lineage recovery image for your model to recovery.img and add it to a .tar archive using e.g 7zip.
If using Heimdall use: heimdall flash --RECOVERY recovery.img --no-reboot
Boot lineage recovery
IMPORTANT: Do not boot into system again before booting recovery, or system will restore stock recovery!
If using Odin untick auto-reboot before flashing.
After flashing reboot by pressing Volume Down and Power for approximately 7 seconds,
immediately hold Volume Up and Power to boot recovery
IMPORTANT: As of OneUI 3 your device needs to be connected to a PC via USB cable in order to be able to
boot recovery via Volume Up, Bixby and Power.
Factory reset using Factory reset -> Format data/factory reset
Warning: Unlike TWRP this will also erase internal storage!
Sideload LineageOS by enabling sideload via Apply Update -> Apply from ADB
Then run adb sideload <path to your lineage.zip> on your PC
Optional:
Sideload GApps and magisk by repeating above step
with their zip/apk
Click to expand...
Click to collapse
May I ask for screenshots? This is amazing work
HippoInWindow said:
May I ask for screenshots? This is amazing work
Click to expand...
Click to collapse
It appears the dev wants you to use Telegram for support and doesn't answer questions here in XDA. But I didn't get much support there either. When I asked what gapps to use, It just pointed to the Nikgapps site. But when I flashed the CORE version for T, Play Store didn't recognize the internet connection. Tried to revert to 19.1 and it wouldn't let me. Claimed it was a downgrade and not allowed. Had to flash the latest stock version via Odin, with all of the Samsung and Google bloat.
Well, I got it to work in spite of the lack of support. Had to use the OMNI version of Nikgapps instead to CORE. One little nit pick discovered so far. /Setup/System/Status Bar setting to change the battery icon to text and show percent doesn't work. But that is easy to live with.
lewmur said:
If we already have LOS 19.1 and recovery, do we still need to install the new recovery and factory reset?
edit: I renamed the new recovery image to recovery.img and then used 7zip to make recovery.tar and flashed it with Odin. But when I booted to recovery, all I got was a blank screen. Had to reflash the 19.1 recovery to get it back.
Click to expand...
Click to collapse
https://dl.linux4.de/lineageos/releases/gta4xlwifi/
LOS 20 recovery here. I do think we have to use same recovery version as the instructions say.
The image has been updated today and now I see the lineage OS 20.0 recovery.
xsw2 said:
https://dl.linux4.de/lineageos/releases/gta4xlwifi/
LOS 20 recovery here. I do think we have to use same recovery version as the instructions say.
The image has been updated today and now I see the lineage OS 20.0 recovery.
Click to expand...
Click to collapse
if flashed it with the old recovery but the zip check false and then you have to flash anyway
i check and the file size of both recovery where the same thought that is just for the ones that need it for flash for the first time
Just downloaden every thing with a AVG Antivirus alert.
For now I'll wait and maybe test later.
edit: the alert was from a know false positive.
For me better safe than sorry.
reef2009 said:
Just downloaden every thing with a AVG Antivirus alert.
For now I'll wait and maybe test later.
View attachment 5705853
Click to expand...
Click to collapse
Well I built that zip myself, I can assure you there's no malware.
BTW Antivirus apps on android are only a waste of resources.
Updated with September securitypatch and more lineage features
Is the changelog link broken? When I try it to see if I want to flash the latest version, it just times out.
lewmur said:
Well, I got it to work in spite of the lack of support. Had to use the OMNI version of Nikgapps instead to CORE. One little nit pick discovered so far. /Setup/System/Status Bar setting to change the battery icon to text and show percent doesn't work. But that is easy to live with.
Click to expand...
Click to collapse
You're not owed support by anyone. OP could flip off every user and **** off forever, but they'd still have done their work for the community. Thanks for the tips, though!
okno13 said:
You're not owed support by anyone. OP could flip off every user and **** off forever, but they'd still have done their work for the community. Thanks for the tips, though!
Click to expand...
Click to collapse
I didn't claim I was owed support. I merely stated that I didn't get any and that I was able to get it working in spite of that.
Device reboots after opening camera. Probably issues with camera hal
So far so good, except I cannot for the life of me get the Google keyboard to work...all other gapps are fine...
Well, the dev for this ROM has convinced me to sell my S6 and buy a newer tablet that has support here in XDA. Apparently, he will only offer support in Telegram because, in that app, he can ban anyone who disagrees with him. So, no support if you want, TWRP, Magisk, Nixgapps, custom kernels or anything else he doesn't like.
lewmur said:
Well, the dev for this ROM has convinced me to sell my S6 and buy a newer tablet that has support here in XDA. Apparently, he will only offer support in Telegram because, in that app, he can ban anyone who disagrees with him. So, no support if you want, TWRP, Magisk, Nixgapps, custom kernels or anything else he doesn't like.
Click to expand...
Click to collapse
What reason would we have to ban people who want support? He doesn't provide support for TWRP because it's a discontinued project and because it worked terribly on the tablet. That's like asking Samsung for help on a flip phone you bought in 1994 that's been discontinued for quite a while. I don't think I recall him actively rejecting people's technical support for Magisk, NikGapps, or Custom Kernels when I was in his Telegram, he only said that he recommends alternatives to Magisk and NikGapps. I don't know if you're writing this after you were banned but the only time he proactively rejected support in people's devices is when TWRP was in the equation.
{Mod edit: Quoted post has been deleted}
It is being actively supported by legacy devices that can't handle encryption and on ROMs made by unknowingly devs.
Also you were told multiple times that encryption is not an optional thing, especially on T. And some users do care about their data not being just accessible when the device gets stolen.