{
"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. 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.
Base source code is available in the LineageOS Github repo. And if you would like to contribute to the project, please visit our Gerrit Code Review.
Device source code:
msm8974-common (shared by all Samsung msm8974 devices): LineageOS/android_device_samsung_msm8974-common
klte-common (shared by all klte* devices): LineageOS/android_device_samsung_klte-common
klte: LineageOS/android_device_samsung_klte
klteactivexx: LineageOS/android_device_samsung_klteactivexx
kltechn: LineageOS/android_device_samsung_kltechn
kltechnduo: LineageOS/android_device_samsung_kltechnduo
klteduos: LineageOS/android_device_samsung_klteduos
kltedv: LineageOS/android_device_samsung_kltedv
kltekdi: LineageOS/android_device_samsung_kltekdi
kltekor: LineageOS/android_device_samsung_kltekor
Kernel source code:
LineageOS/android_kernel_samsung_msm8974
Build Compatibility:
The noted models are the only ones supported. If you have a model that isn't listed and ask politely then I might work to add compatibility.
BuildModelklteSM-G900F, SM-G900M, SM-G900R4, SM-G900R7, SM-G900T, SM-G900V, SM-G900W8klteactivexxSM-G870FklteaioSM-G900AZ, SM-S902LkltechnSM-G9006V, SM-G9008VkltechnduoSM-G9006W, SM-G9008W, SM-G9009WklteduosSM-G900FD, SM-G900MDkltedvSM-G900I, SM-G900PkltekdiSC-04F, SCL23kltekorSM-G900K, SM-G900L, SM-G900S
Downloads:
Lineage - https://download.lineageos.org/
Firmware - https://www.androidfilehost.com/?w=files&flid=325192
Installation Instructions:
https://wiki.lineageos.org/devices/
Reporting Bugs:
https://gitlab.com/LineageOS/issues/android
Compatibility Notes:
Bootloader version doesn't matter. Anyone who tells you so doesn't know what they are taking about. My Developer Edition G900V is still running the original 4.4.2 KK aboot. My G900W8 is running the latest 6.0.1.
All builds except for klteactivexx and klteaio MUST be running a marshmallow (6.0.1) radio for RIL to work. If you are about to report that RIL/radio isn't working then I pretty much guarantee this is your issue.
You MUST be running a marshmallow (6.0.1) NON-HLOS for the fingerprint reader to work. If you are about to report a fingerprint reader problem then you either have old firmware (update it), your /data was previously encrypted and you performed a "clean" flash without FORMATTING /data (start over and FORMAT /data), or your reader is just broken.
External SD cards don't support POSIX (ext*, f2fs) or NTFS filesystems anymore. If this affects you then just bite the bullet, copy any data off you really want to save, and reformat as exfat.
The latest TWRP seems like it works, but if someone has issues then perhaps try using the actual supported recovery.
Donations:
I absolutely don't personally accept them. If you really feel that this work deserves it, then find a local food bank or animal shelter/rescue and throw some money their way. You can also throw some the way of LineageOS, but we're actually doing pretty well right now.
[Reserved]
Hi,
Thanks for maintaining our phone !
I just upgraded to LineageOS 18.1 as I explained in this post and got stuck in the lock screen :
[OFFICIAL] LineageOS 17.1 for Galaxy S5 klte + Variants
Edit: FYI the LineageOS S5 klte family maintainer created a new thread here: [ROM][OFFICIAL][11] LineageOS 18.1 for Samsung Galaxy S5 (klte*) *** #include "std_disclaimer.h" /* * Your warranty is now void. * * I am not responsible for bricked...
forum.xda-developers.com
Do you know how can I solve this ?
Logcat :
https://paste.chapril.org/?86ff7c1c0ddf2642#5BDBqxDBmYJKjheUpjDSvhBvDL3EGv4ALYQaECGPwkNq
Some of my reference posts in this thread:
Galaxy S5 LineageOS 17.1 Upgrade to 18.1 + OTA Update Success Using TWRP
Clean Install with TWRP.
TWRP & Lineage Recovery - Format Data vs. Wipe
Warning: Cannot Unlock the S5 After Upgrading from LineageOS 17.1 to 18.1
S5 Connecting to PC - adb Wireless Debugging
Galaxy S5 LineageOS 18.1 - Magisk Installation
S5 klte LineageOS 18.1 Battery Usage @ Idle Test - Sleeps Like a Rock
S5 Low Mobile Network Battery Usage @ Idle
S5 Mic Boost Magisk Module - Stereo Recordings
***
Massedil said:
Hi,
Thanks for maintaining our phone !
I just upgraded to LineageOS 18.1 as I explained in this post and got stuck in the lock screen :
[OFFICIAL] LineageOS 17.1 for Galaxy S5 klte + Variants
Edit: FYI the LineageOS S5 klte family maintainer created a new thread here: [ROM][OFFICIAL][11] LineageOS 18.1 for Samsung Galaxy S5 (klte*) *** #include "std_disclaimer.h" /* * Your warranty is now void. * * I am not responsible for bricked...
forum.xda-developers.com
Do you know how can I solve this ?
Logcat :
https://paste.chapril.org/?86ff7c1c0ddf2642#5BDBqxDBmYJKjheUpjDSvhBvDL3EGv4ALYQaECGPwkNq
Click to expand...
Click to collapse
Weird that you are getting caught by that, I explicitly tested the upgrade path. Try deleting the lockscreen files from recovery (/data/system/gatekeeper.*.key, /data/system/locksettings.db*). If that doesn't work, wipe data.
haggertk said:
Weird that you are getting caught by that, I explicitly tested the upgrade path. Try deleting the lockscreen files from recovery (/data/system/gatekeeper.*.key, /data/system/locksettings.db*). If that doesn't work, wipe data.
Click to expand...
Click to collapse
Thanks I'll try now !
I've noticed default email app is gone on 18.1. Any way to get it back or is there a free, open-source alternative for it?
Garry58 said:
I've noticed default email app is gone on 18.1. Any way to get it back or is there a free, open-source alternative for it?
Click to expand...
Click to collapse
I use K9 and/or Fairmail
haggertk said:
Weird that you are getting caught by that, I explicitly tested the upgrade path. Try deleting the lockscreen files from recovery (/data/system/gatekeeper.*.key, /data/system/locksettings.db*). If that doesn't work, wipe data.
Click to expand...
Click to collapse
I don't have any .key file, maybe it is the problem ?
Code:
/data/system # find /data/system -name '*key*'
/data/system/sensor_service/hmac_key
/data/system/dropbox/[email protected]
/data/system/dropbox/[email protected]
/data/system/dropbox/[email protected]
/data/system/dropbox/[email protected]
/data/system/dropbox/[email protected]
/data/system/dropbox/[email protected]
/data/system/recoverablekeystore.db
If it can helps :
Code:
sqlite3 locksettings.db
sqlite> SELECT * FROM locksettings ;
1|lockscreen.disabled|0|0
2|migrated|0|true
3|migrated_user_specific|0|true
4|lockscreen.password_type_alternate|0|0
5|migrated_biometric_weak|0|true
6|migrated_lockscreen_disabled|0|true
7|migrated_frp|0|1
8|lockscreen.enabledtrustagents|0|org.lineageos.profiles/.ProfilesTrustAgent
9|lockscreen.password_type|0|NNNNNN
11|sp-handle|0|NNNNNN
12|lockscreen.profilechallenge|0|1
13|lockscreen.passwordhistory|0|
14|lockscreen.istrustusuallymanaged|0|1
15|lockscreen.power_button_instantly_locks|0|0
22|lock_screen_owner_info_enabled|0|1
23|lock_screen_owner_info|0|XXXXXXXXXX
haggertk said:
Weird that you are getting caught by that, I explicitly tested the upgrade path. Try deleting the lockscreen files from recovery (/data/system/gatekeeper.*.key, /data/system/locksettings.db*). If that doesn't work, wipe data.
Click to expand...
Click to collapse
Thanks !
I just deleted /data/system/locksettings.db and I can now access the phone.
I have kept a copy of this database before removing, if you need it for investigation I can send it to you.
Thanks again !
Hey guys! I'm now on 18.1 (of course a clean flash) ....great ROM so far but I have the same problem as on 17.1 ...whenever I lose GSM it does not come back ...I receive the message that SIM Card is missing - service not available (Keine SIM-Karte - Dienst nicht verfügbar) ...someone else with a klteactivexx here with the same experience? Never had a problem with Lineage 16.0 ...hope for someone who can confirm my problem...
[OFFICIAL] LineageOS 17.1 for Galaxy S5 klte + Variants
Edit: FYI the LineageOS S5 klte family maintainer created a new thread here: [ROM][OFFICIAL][11] LineageOS 18.1 for Samsung Galaxy S5 (klte*) *** #include "std_disclaimer.h" /* * Your warranty is now void. * * I am not responsible for bricked...
forum.xda-developers.com
@haggertk @curiousrom the journey goes on!
haggertk said:
Donations:
I absolutely don't personally accept them. If you really feel that this work deserves it, then find a local food bank or animal shelter/rescue and throw some money their way. You can also throw some the way of LineageOS, but we're actually doing pretty well right now.
Click to expand...
Click to collapse
Many THX for givin' the good old S5 a continued life again. Will look for food/money for the local animal shelter, our cat comes from there
Beautiful
@haggertk thank you for your amazing work !! One question: Why arent navigation gestures enabled by default ?? Have to edit build.prop file to get it..
Regards !
bersem said:
@haggertk thank you for your amazing work !! One question: Why arent navigation gestures enabled by default ?? Have to edit build.prop file to get it..
Regards !
Click to expand...
Click to collapse
The Galaxy S5 has physical keys, in particular, the home key. Since this key cannot be "hidden", our standards are that key disabler must not be able to be activated through normal user interaction.
First, I want to thank Haggertk and LineageOS for keeping the Galaxy S5 alive.
DISCLAIMER: I don’t know as much as I’d like about what’s behind the Android curtain. I’m especially ignorant about the Android file system, but I’m learning.
We’re in the process of switching from older Galaxy S2 Skyrockets (we keep our phones waaaaay too long) to SM‑G900Ts (newer, but still pretty old). For the past month or so, all three of our SM-G900Ts have been running unofficial 18.1 (20201225) with NikGapps Pico. This morning, I downloaded LineageOS 18.1-20210425-nightly-klte-signed and installed it on two of our SM-G900Ts via TWRP (which I had previously installed via ODIN).
We have two problems we didn’t have before:
In 20210425, the 18.1 camera app doesn’t work. It tries to open (quick flash of a black background), then immediately stops. Trying the camera app a second time, it again tries to start, again immediately stops and then throws up a "camera keeps stopping" message. If I tap OK, the message closes and the phone continues to work normally. The camera app in unofficial 18.1 works fine (one of our three phones hasn’t been updated yet). The problem doesn’t seem to be hardware: Open Camera works fine on 20210425 after being side loaded.
The Play Store app (installed by either Open Gapps or NikGapps) categorically refuses to install apps on 20210425, complaining there’s not enough space. The app offers to delete other apps to make space, but since there aren’t any (yet), it can’t. The problem doesn’t seem to be related to the size of the app: I tried to install a really small app (APK = 3.3KB) and that failed, too. The problem also doesn’t seem to be related to user partition space, I side loaded DiskInfo and it says Data/data/user/0 has 10.9GB free. Further, I can side load apps via APK: The not-small Open Camera, for example. The Play Store installs/installed apps just fine on 20201225.
Another quirk is that the phone s still running 20201225 refuses to run Google Maps (stops immediately after trying to start).
Yet another clue may be the fact that I haven’t been able to recreate whatever combination of OS version, GAPPS version and procedure I used to create the phone that’s still running 20210425. Perhaps I did something differently this time.
Does anyone else have these problems? If so, are there fixes? Did I do something wrong? Is there something I need to do differently?
Thank you in advance,
Tenaya
Tenaya43 said:
First, I want to thank Haggertk and LineageOS for keeping the Galaxy S5 alive.
DISCLAIMER: I don’t know as much as I’d like about what’s behind the Android curtain. I’m especially ignorant about the Android file system, but I’m learning.
We’re in the process of switching from older Galaxy S2 Skyrockets (we keep our phones waaaaay too long) to SM‑G900Ts (newer, but still pretty old). For the past month or so, all three of our SM-G900Ts have been running unofficial 18.1 (20201225) with NikGapps Pico. This morning, I downloaded LineageOS 18.1-20210425-nightly-klte-signed and installed it on two of our SM-G900Ts via TWRP (which I had previously installed via ODIN).
We have two problems we didn’t have before:
In 20210425, the 18.1 camera app doesn’t work. It tries to open (quick flash of a black background), then immediately stops. Trying the camera app a second time, it again tries to start, again immediately stops and then throws up a "camera keeps stopping" message. If I tap OK, the message closes and the phone continues to work normally. The camera app in unofficial 18.1 works fine (one of our three phones hasn’t been updated yet). The problem doesn’t seem to be hardware: Open Camera works fine on 20210425 after being side loaded.
The Play Store app (installed by either Open Gapps or NikGapps) categorically refuses to install apps on 20210425, complaining there’s not enough space. The app offers to delete other apps to make space, but since there aren’t any (yet), it can’t. The problem doesn’t seem to be related to the size of the app: I tried to install a really small app (APK = 3.3KB) and that failed, too. The problem also doesn’t seem to be related to user partition space, I side loaded DiskInfo and it says Data/data/user/0 has 10.9GB free. Further, I can side load apps via APK: The not-small Open Camera, for example. The Play Store installs/installed apps just fine on 20201225.
Another quirk is that the phone s still running 20201225 refuses to run Google Maps (stops immediately after trying to start).
Yet another clue may be the fact that I haven’t been able to recreate whatever combination of OS version, GAPPS version and procedure I used to create the phone that’s still running 20210425. Perhaps I did something differently this time.
Does anyone else have these problems? If so, are there fixes? Did I do something wrong? Is there something I need to do differently?
Thank you in advance,
Tenaya
Click to expand...
Click to collapse
you somehow have a media storage issue they changed the permission set with the way apks communicate with "sdcard" internal storage for less vulnerabilities at the user app level....and stopped external sd support....we had a legacy media patch for old devices....now heres the catch if you flashed with the external sdcard in with older TWRP it thinks that external is internal SD then when u boot internal is blank external don't work and the play store thinks you used up....also any music app doesn't see media... this happened to me... what i did was cracked back and format data and wiped all partitions took external out wiped everything in twrp...went to download mode in odin reflashed full four file G900TUVU1GQC2_G900TTMB1GQC2_G900TUVU1GQC2_HOME.tar.md5
somethimes its nice to boot Android 6.01 then look in the newer threads and see how people complain so much about this and that and remember The TOUCHWIZ days....lol....
Then flashed new 18.1 clean using the lineage recovery..... so that means I had to flash twrp once in odin to install the new recovery file to install the official build because I dont like hemidall
... with lineage gapps https://androidfilehost.com/?w=files&flid=322935
Google maps only works in incognito mode, in normal mode does not works . I hope it will be fixed
Andresine said:
Google maps only works in incognito mode, in normal mode does not works . I hope it will be fixed
Click to expand...
Click to collapse
works fine on my device ...
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"
}
This ROM is Abandoned as Cyanogen pulled the plug on CyanogenMod
As soon as Lineage OS build farm is setup, it'll return as Lineage OS. A new topic will be started. In the mean time, building from source is an option.
This project is the official continuation of the http://forum.xda-developers.com/tab-s2/development/rom-cyanogenmod-13-0-tab-s2-9-7-t3397682]unofficial build.
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community
First I would like to thank the following developers :
@RaymanFX
@CTXz
I used @RaymanFX's T815 image to base my cm 13.0 build on.
Before you start
THIS ROM IS ONLY FOR THE SM-T810
Code:
*
* Your warranty will be voided !
*
* I am 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 me for messing up your device, I will laugh at you.
*
About the ROM
Current state of ROM : testing
Everything except what's reported below is working. Nothing 'fixed' yet, first build.
What is Fixed
What is not working
Important
Fingerprint scanner not working
Minor
Limited wifi 5GHz support (channels above 100 give issues)
Compass is 180 degrees mis-aligned
About says 'Phone' instead of 'Tablet' (haven't found any other issues, other then text)
Instructions
How to install CM13.0
If you haven't run stock Android 6.x, flash that first with odin. (image won't boot without this step)
If you don't have TWRP yet, get it from here : TWRP by ashyx
Download the ROM and the Gapps that are located below to your device
Reboot into TWRP by holding VOL UP + POWER + HOME on boot
In case things go wrong make a backup
After the backup has completed return to home and select Wipe and then Advanced Wipe
Now ONLY tick Dalvik Cache, System, Data and Cache
After ticking those, Swipe below to wipe
Once the wipe has completed return to home and select the ROM
After you selected the ROM swipe below to install it
After the ROM has installed flash the Gapps
When all of this is done, reboot into system, wait, and enjoy CM12.1
How to ROOT
In CM 13.0 Enable the developer options
Select Root access
Select Apps Only
Done
Questions and bug reporting
The following questions will be ignored
Inappropriate questions
Forced orders, EX. : "PLS FIX!!!!!!"
ETA's
Often repeated questions usually by the same user
Requests that are out of CM's framework (Ex. Adding Samsung Apps)
How to report a bug/issue
Explain exactly what happens
Mention a log if you can (Please use hastebin or any other paste site to keep the thread clean)
If you can't mention a log, explain as precise as possible when, why and where it occurs!
Changelog
Code:
**********
17-07-2016 - Corrected last noop usage to bfq in /init.samsung.rc
**********
11-07-2016 - Recompile UNOFFICIAL BETA build with latest CM patches.
**********
05-07-2016 - Enabled multi user in UNOFFICIAL BETA build.
**********
29-06-2016 - 1st Nightly build
- Changelog limited to changes in gts210wifi sources, updates in gts2-common and other general parts are included via nightly system.
**********
Downloads
All CM 13.0 Nightly releases can be found here: http://get.cm/?device=gts210wifi
All UNOFFICIAL BETA versions van be found here: https://www.androidfilehost.com/?w=files&flid=68015
Recommended GAPPS by opengapps.org : http://opengapps.org/ (I use pico)
Source
Special Thanks to @RaymanFX for releasing his Exynos 5433 source, without him this ROM would most likely not be possible!
All my sources can be found here : https://github.com/CyanogenMod/android_device_samsung_gts210wifi
Screenshots
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
XDA:DevDB Information
CyanogenMod 13.0 for Samsung Galaxy Tab S2 9.7 T810, ROM for the Samsung Galaxy Tab S2
Contributors
T_I,CTXz, Sub77, Moonbutt74, RaymanFX, Hennymcc
Source Code: https://github.com/Galaxy-Tab-S2
ROM OS Version: 6.0.x Lollipop
Based On: CyanogenMod
Version Information
Status: Beta
Created 2016-06-13
Last Updated 2016-06-27
XDA:DevDB Information
CyanogenMod 13.0 for Tab S2 9.7 wifi, ROM for the Samsung Galaxy Tab S2
Contributors
T_I, RaymanFX, CTXz
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Stock Android 6.x flashed at least once before install
Based On: CyanogenMod
Version Information
Status: Abandoned
Created 2016-06-29
Last Updated 2017-01-08
Great to see the journey resulting in an official nightly. Well done.
Sent from my A0001 using Tapatalk
Fritzy62 said:
Great to see the journey resulting in an official nightly. Well done.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Thanks, I'm totally happy. Looks nice, even with my dark theme...
Sent from my T810 running cm-13.0
This awesome love your work just one thing when I try to format my SD card as internal it just gets corrupted why is this
Delta wolf said:
This awesome love your work just one thing when I try to format my SD card as internal it just gets corrupted why is this
Click to expand...
Click to collapse
Can't think of a reason why it should do that. (and why you should do that, with 32 Gb internal)
I'm currently out of large enough SD's so I could transfer internal to external.
Does a format as regular card work?
Can you get a logcat (start before format, stop after it failed) of the format as internal and when regular fails, one of that action as well?
Congratulations, all your hard work is paying off. Great stuff sir. Love your ROM. ?
Sent from my SM-T810 using XDA-Developers mobile app
Not sure how to get logcat but formatting as portable works while formating as internal it all goes through says Sd card is working I hit done and it says corrupted EDIT***: some other people were having this issue on different devices it appears it was an issue with cm 13 that got patched in a different nightly likely the same issue here
---------- Post added at 03:13 PM ---------- Previous post was at 02:27 PM ----------
So formating as internal still goes corrupt but when entering twrp to erase the Sd twrp says it can't mount adoptable storage unit
Thanks for your hard work.
As I am still on the "unofficial" build, do I need to clean flash the official nightly ?
Edit:
Did a clean flash, to on the safe side. Unfortunately though I still cannot get the quicksettings to. I don't even the option in my menu.
Incase embedding doesn't work: https://www.youtube.com/watch?v=tp6c60Andgk
OK so I have a floating logcat did the format and stopped it how do I send it over can't find option to save the log EDIT**** I FOUND HOW TO SAVE but won't let me upload I can send an email with it if that is OK? And only reason I'm doing it is because I have a bunch of big apps and a lot of music I had 2gb free before I erased everything and flashed cm also if I may request a close all button for closing out application
Thank you for the CM port! I am testing this on my tab and like others say, Netflix does not work (cannot find the liboecryptXXX to remove or change filename) and sd card is always corrupt no matter which option you choose (64GB SD card). Let me know if there is anything I need to send to help.
akiradavis said:
Thank you for the CM port! I am testing this on my tab and like others say, Netflix does not work (cannot find the liboecryptXXX to remove or change filename) and sd card is always corrupt no matter which option you choose (64GB SD card). Let me know if there is anything I need to send to help.
Click to expand...
Click to collapse
Netflix seems to be working for me I downloaded the tablet version from Google play store I did get a Google play services error but just closed app and opened again and everything worked fine was watching an episode of walking dead
EDIT: just tried again and now all it says is loading I prefer to use kodi so not a big deal to me
Delta wolf said:
Netflix seems to be working for me I downloaded the tablet version from Google play store I did get a Google play services error but just closed app and opened again and everything worked fine was watching an episode of walking dead
Click to expand...
Click to collapse
Where can I find the tablet version of Netflix? I only see the one app in the Play Store.
EDIT: Also - I am on version 13.0-20160629-NIGHTLY-gts210wifi - Maybe this nightly broke Netflix?
---------- Post added at 02:10 PM ---------- Previous post was at 02:03 PM ----------
Delta wolf said:
Netflix seems to be working for me I downloaded the tablet version from Google play store I did get a Google play services error but just closed app and opened again and everything worked fine was watching an episode of walking dead
EDIT: just tried again and now all it says is loading I prefer to use kodi so not a big deal to me
Click to expand...
Click to collapse
Ahh, just saw this. Yeah, it appears its down. But at least ChromeCast works!
Wow. Official for the T810. Nice job! Should hopefully be somewhat soon before the 710 gets it aswell. I'm thinking of getting a 713 to learn this on. Good stuff!
Nice work! This may just get me off my year-long break from flashing.
Sent from my SM-G935T using Tapatalk
Thanks TI for all the hard work in getting this ROM running on our S2's, it's running really nice and smooth for me and I thank you and those who helped for putting forth all the effort in making it happen, it's much better than TW IMO. :good:
Idk if it's OK to post a request in this thread but can someone in the community please create a custom under/overclock/under volt kernel for this ROM? I was spoiled using the ROM and custom kernel that Engine95 made for Lollipop TW and it seemed to take my S2 to the next level especially with battery savings, adjusting the BIG processor down to 500mhz really had a noticeable impact. Idk what settings he used for the undervolting but he set the oc parameters for the little processor up to 1.6ghz and the BIG from 500 to 2.2ghz on the interactive governor and my S2 was running great. I can only imagine what this ROM would do with a similar custom kernel but I know the performance would make our S2's jump to the next level. Thanks again :good:
Is it also possible to add multi user support
pilspeda said:
Thanks for your hard work.
As I am still on the "unofficial" build, do I need to clean flash the official nightly ?
Edit:
Did a clean flash, to on the safe side. Unfortunately though I still cannot get the quicksettings to. I don't even the option in my menu.
Incase embedding doesn't work: https://www.youtube.com/watch?v=tp6c60Andgk
Click to expand...
Click to collapse
Embedded didn't work (here). Thanks for the video, learning more about android every day. I have the option set to right and when I turn it off nothing changes, so I can confirm, it doesn't work. Will have to check on the phone what it should do though and then look into it.
Delta wolf said:
OK so I have a floating logcat did the format and stopped it how do I send it over can't find option to save the log EDIT**** I FOUND HOW TO SAVE but won't let me upload I can send an email with it if that is OK? And only reason I'm doing it is because I have a bunch of big apps and a lot of music I had 2gb free before I erased everything and flashed cm also if I may request a close all button for closing out application
Click to expand...
Click to collapse
Emailing would be fine. There is a site to share logs online, but I've forgotten which one that is. (will look into that as well)
akiradavis said:
Thank you for the CM port! I am testing this on my tab and like others say, Netflix does not work (cannot find the liboecryptXXX to remove or change filename) and sd card is always corrupt no matter which option you choose (64GB SD card). Let me know if there is anything I need to send to help.
Click to expand...
Click to collapse
I'm using 32 and didn't need to format. Will test.
Nandr0idC0nsumer said:
Wow. Official for the T810. Nice job! Should hopefully be somewhat soon before the 710 gets it aswell. I'm thinking of getting a 713 to learn this on. Good stuff!
Click to expand...
Click to collapse
The T713 is snapdragin, not exynos, different base. I don't know if you can use the common we have, I guess not, as that one depends on the exynos libs.
Towle said:
Nice work! This may just get me off my year-long break from flashing.
Click to expand...
Click to collapse
A whole year without flashing? I select my devices on the option to flash... (when no image available, I'll build )
Welcome back to the light.
At the moment the rom is on phone mode. For multiuser etc. you have to set android to tablet mode.
As Cyanogen pulled the plug on CyanogenMod, this project will continue under Lineage OS
{
"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"
}
This ROM is Alpha and not ready for daily use at the moment
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community
First I would like to thank the following developers :
@RaymanFX
@CTXz
I used @RaymanFX's T815 image to base my cm 13.0 build on, which in turn is the base of this cm-14.1.
Before you start
THIS ROM IS ONLY FOR THE SM-T810
Code:
*
* Your warranty will be voided !
*
* I am 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 me for messing up your device, I will laugh at you.
*
About the ROM
Current state of ROM : testing
Everything except what's reported below is working (or not yet reported as not working).
What is Fixed
In '20-09' build reboot to recovery triggers message 'Factory reset'. (wrong messagem not resetting)
Camera not working in selinux enforcing
Front facing camera unable to save image
Bluetooth not working
Hardware codecs not working (fallback to software for mp3/flac works)
Limited wifi 5GHz support (channels above 100 give issues)
Video recording not working? (not tested on T810, reported not working on T815)
What is not working
Important
Fingerprint scanner not working
Minor
Compass is 180 degrees mis-aligned
Mic not working (no input routing)
Instructions
How to install CM13.0
If you haven't run stock Android 6.x, flash that first with odin. (image won't boot without this step)
If you don't have TWRP yet, get it from here : TWRP by ashyx
Download the ROM and the Gapps that are located below to your device
Reboot into TWRP by holding VOL UP + POWER + HOME on boot
In case things go wrong make a backup
After the backup has completed return to home and select Wipe and then Advanced Wipe
Now ONLY tick Dalvik Cache, System, Data and Cache
After ticking those, Swipe below to wipe
Once the wipe has completed return to home and select the ROM
After you selected the ROM swipe below to install it
After the ROM has installed flash the Gapps
When all of this is done, reboot into system, wait, and enjoy CM12.1
How to ROOT
In CM 14.1 Enable the developer options
Select Root access
Select Apps Only
Done
Questions and bug reporting
The following questions will be ignored
Inappropriate questions
Forced orders, EX. : "PLS FIX!!!!!!"
ETA's
Often repeated questions usually by the same user
Requests that are out of CM's framework (Ex. Adding Samsung Apps)
How to report a bug/issue
Explain exactly what happens
Mention a log if you can (Please use hastebin or any other paste site to keep the thread clean)
If you can't mention a log, explain as precise as possible when, why and where it occurs!
Changelog
Code:
**********
08-12-2016 - Compile with curren cm-14.1 source and [URL="https://review.cyanogenmod.org/#/c/173951"]this patch[/URL].
**********
25-11-2016 - Cm-14.0 is abandoned upstream, limiting uploads to cm-14.1.
- Recompile with camera fix merged in cm sources.
**********
21-11-2016 - Fixed camera (again).
**********
20-11-2016 - Broke camera in enforcing mode (unable to save picture).
**********
17-11-2016 - Recompile from clean tree, camera and youtube work now.
- Confirmed lock-screen-rotate fixed, but only after clean flash and [b]no restore of device ID[/b].
**********
14-11-2016 - First succesful cm-14.1 boot. (Switched project to cm-14.x)
**********
31-10-2016 - Selinux set to enforcing.
**********
12-10-2016 - Disabled telephony that got included regardless specifying I don't want it.
- Fixed several bluetooth issues
- Removed use of old api (v1) by camera
**********
03-10-2016 - First build with cm-14.0 release (previous were staging builds)
- Fixed bluetooth
**********
25-09-2016 - Fixed selinux contexts for camera so it works in enforcing mode
- Fixed front facing camera so it is able to save images.
**********
22-09-2016 - Reboot to recovery now triggers correct message
- 2nd build selinux permissive.
**********
20-09-2016 - 1st cm-14.0 build
**********
Downloads
Latest CM 14.1 build : https://www.androidfilehost.com/?fid=673368273298915423
All CM 14.1 releases can be found here : https://www.androidfilehost.com/?w=files&flid=128488
Recommended GAPPS by opengapps.org : http://opengapps.org/ (I use pico)
Source
Special Thanks to @RaymanFX for releasing his Exynos 5433 source, and already patching the common sources to cm-14.0, without him this ROM would most likely not be possible!
All my sources can be found here : https://github.com/CyanogenMod/android_device_samsung_gts210wifi
Screenshots
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
XDA:DevDB Information
CyanogenMod 14.1 for Tab S2 9.7 wifi, ROM for the Samsung Galaxy Tab S2
Contributors
T_I, Raymanfx, CTXz
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Stock Android 6.x flashed at least once before install
Based On: Cyanogenmod
Version Information
Status: Alpha
Created 2016-09-22
Last Updated 2016-12-29
Nice! Thank your very much for this early build!
I will try it as soon as I am able.
Sent from my SM-T810 using XDA-Developers mobile app
GO hard brother, thanks for all your efforts!
I've been using cm-14 since the 20-9 build, it's running pretty stable, although it's even more stable with selinux in permissive. Looks like some contexts have changed a bit in cm-14. (or the camera and some other routines ignore them)
I found 1 game not playing nicely with Nougat, CSR Classics, but the racing set from CSR work nicely, so I think that's a CSR related bug.
Fixed camera so it'll work in selinux enforcing (not yet activated) and front facing camera is able to save images.
Updated OP.
Awesome thank you!
@T_I Thought you might like 2 comments re your really great adaptation of CM14. Have been using your CM13 nightly downloads for about the last 5 weeks on my T810 and was so pleased with the result that I was slightly hesitant about trying CM14, however this afternoon I took the plunge and installed it as per your instructions. First impression is that I can hardly believe how problem free the installation of the Rom and the Open Gapps 7.0 pico proved to be.
I don't have a huge number of apps installed, about 30, but with one exception they are all performing as scheduled and I couldn't be more pleased, the one app that doesn't work is "Set CPU", there is no "forced closure", no error message, it just doesn't work. There are no forced closures of any other app including the Google Play & Services.
One point which might interest you as you mentioned it in your "OP" notes. I play mp4 movies using the app "MX Player Pro" with the Arm 7 codec installed and they play using the HW+ codec perfectly,
Was initially disappointed that "Theme Chooser" was missing from "Settings" but I can live with that considering how well everything else performs.
Once more congratulations on a really superb "port".
EDIT on 09.27.... @T_I I know this point is insignificant and pure "eye candy" but I love the touch ..... I'm talking about when one connects a usb connection from PC to S2 then the "icon" displayed at top left is now "N" (for Nougat ?) instead of the normal CM icon.
planning to attempt with the t710 again?lol
NalNalas said:
I've had this flashed since last night, and the battery so far has been great. Thanks a ton for this.
Click to expand...
Click to collapse
How much better would you say the battery life has been?
Would also appreciate input from anyone else whos noticed a difference (good or bad) with the battery life.
This ROM is working great so far!!
samsung_xoom said:
planning to attempt with the t710 again?lol
Click to expand...
Click to collapse
I can run a cm-14 build for T710 to see if that one boots.
I can test it and let you know , in my limited time I have lol
This rom is very stable, fast and reliable. The battery life is excelent. I use it as my daily driver since sept. 22!!! (Now i have a sept. 27 update)
Thanks T_I for your hard work!!!
Uploaded new image. @RaymanFX got bluetooth working on his device and the fix works on T810 as well. Also CM switched cm-14.0 from staging to release. There is still work to be done, but build shows working bluetooth (at least I can connect a keyboard and that one works).
I noticed crashing phone app and saw one ExchangeServices crash. (don't use both) Updates OP.
Latest build works wonders after I deleted from /system/app and /system/priv-app all the apks related to telephony/SMS/MMS/etc. for my T810.
EDIT: After some time, it all came crashing down, Play Services didn't like the removal of the packages, and some apps auto-removed themselves. Better wait until dev ships out another build.
Just tried to install the Oct 3 version of this ROM and as soon as it boots a box appears saying "com.android.phone has stopped". No matter how many times I click OK, the message just reappears and I can't get past it. Even have to use the power-home-vol- button combination to power off. This is on a T810 after full wipe, install ROM and install 7pico gapps. Tried the install three times. Coming from cellular south 6 ROM.
Please don't forget T710....
lewmur said:
Just tried to install the Oct 3 version of this ROM and as soon as it boots a box appears saying "com.android.phone has stopped". No matter how many times I click OK, the message just reappears and I can't get past it. Even have to use the power-home-vol- button combination to power off. This is on a T810 after full wipe, install ROM and install 7pico gapps. Tried the install three times. Coming from cellular south 6 ROM.
Click to expand...
Click to collapse
I got the same message, but can mute. Don't know where it comes from. I was working on the staging version of cm-14 and switched to the release version. Looks like there are some bugs left. (it's now less stable then with the staging cm-14)
T_I said:
I got the same message, but can mute. Don't know where it comes from. I was working on the staging version of cm-14 and switched to the release version. Looks like there are some bugs left. (it's now less stable then with the staging cm-14)
Click to expand...
Click to collapse
Just by clicking the OK button? Message just pop right back up when I do that.
lewmur said:
Just by clicking the OK button? Message just pop right back up when I do that.
Click to expand...
Click to collapse
I get the message with the 2 options 'stop application' and 'Mute until reboot'. The Mute option silences the warnings, but the app will still misbehave.
Exchange services I've been able to freeze, the phone app is also used for syncing contacts and I think calendar.
{
"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 14.1 for Huawei Nova CAN-L11
DISCLAIMER:
Code:
* Your warranty is now void.
*
* I am 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
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
NOTES
1) If you've found a bug, please report it along with a logcat.
2) If you experience a random reboot, please share /sys/fs/pstore/console-ramoops.
3) It should work on all models, just like LOS 13.
4) Lineage`s root is included (Settings > Developer Options > Root Access. If you want to install Magisk or something else, please uninstall Lineage`s root by flashing addonsu-remove-14.1-arm64-signed.zip in TWRP before installing Magisk or something else.
5) I would appreciate if you could write the Nova model on which you've flashed LOS14, if your model is other than CAN-L11.
Click to expand...
Click to collapse
LineageOS is a free, community built, aftermarket firmware distribution of Android 7 (Nougat), 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
Wifi
Bluetooth
Camera and Camcorder(video recorder)
Video Playback
RIL (Calls, SMS, Data)
Audio ( Recording and Playback )
Sensors
Fingerprint
Notification LED
FM Radio
GPS
NFC
Hotspot
What's not working / bugs:
Camera is / looks zoomed when recording a video (it seems to be same on stock)
HDR?
IMS/Volte
Requirements
Huawei Nova CAN-L11 (should work on the other models too)
Unlocked bootloader ( here's a guide about how to unlock it)
TWRP. The TWRP made by @Grarak is also working fine. You can find it here.
Click to expand...
Click to collapse
Installation
Starting with January 2018 builds you need Nougat /product partition otherwise you'll get bootloop. To get Nougat product partition, you must install / flash EMUI 5 or restore this TWRP backup of Nougat /product partition (more details here). You don't know how to restore that backup? Check the steps from this post.
Make sure you meet the requirements listed above.
Download the ROM and put it on sdcard. If you want GAPPS too, then download Open Gapps too (choose arm64, 7.1 and pico).
Reboot in TWRP by pressing all 3 buttons (Volume UP + Volume Down + Power).
Wipe system, data, cache and dalvik-cache.
Flash the ROM from the directory where you've placed it.
Flash GAPPS (OPTIONALLY).
Reboot.
Click to expand...
Click to collapse
Download
ANDROIDFILEHOST | MEDIAFIRE
Sources
LineageOS: https://github.com/LineageOS
Device: https://github.com/skinzor/android_device_huawei_hwcan
Vendor: https://github.com/skinzor/proprietary_vendor_huawei
Kernel: https://github.com/skinzor/android_kernel_huawei_msm8953-1
Click to expand...
Click to collapse
Donations
You don't have to, but if you like my work and you wish to support the development:
Donate via PayPal:
https://www.paypal.me/Henkate
https://forum.xda-developers.com/donatetome.php?u=4471434
I would use the money to upgrade my PC, so i can build with my own PC instead relaying on Google Cloud Platform.
Credits
@Grarak
@gt_o
@abhishek987
@crpalmer
@FrozenCow
@franciscofranco
@flar2
@Sultanxda
@zx2c4
@ Google for their cloud platform and free trial
@ LineageOS
@ Huawei
XDA:DevDB Information
[ROM][7.1.2][UNOFFICIAL] LineageOS 14.1 [25.05.2018], ROM for the Huawei Nova/Nova Plus
Contributors
#Henkate, Grarak, gt_o
Source Code: https://github.com/skinzor/android_kernel_huawei_msm8953-1
ROM OS Version: 7.x Nougat
ROM Firmware Required: Unlocked bootloader, TWRP
Version Information
Status: Stable
Created 2017-11-13
Last Updated 2018-05-25
Changelog
25 May 2018
* security patch level 5 May 2018
The development has been resumed and is possible thanks to @wangdaning who helped me to get a new Nova. Thank you!
Click to expand...
Click to collapse
15 February 2018
Read this small, but important F.A.Q.
* synced Lineage sources
* security patch level 5 February 2018
* switched to enforcing selinux
Click to expand...
Click to collapse
25 January 2018
ROM
* synced Lineage sources
* security patch level 05.01.2018
* fixed in-call volume slider, mic/sound recorder (it's louder now) thanks to @gt_o. Read more here.
* updated audio configs to B382 and synced few audio props with stock ones
* show "HUAWEI NOVA" instead "Android" when phone is plugged to PC
* removed substratum support.
* added two blobs to fix two errors in logcat
* added the missing device_qcom_common (i don't know how i haven't noticed that till now lol). Now there are 5 profiles: powersave, efficiency, balanced (default), quick and performance. This can be configured at battery settings. As an idea, the powersave profile seems to turn off 3 cores (the cores doesn't seems to turn on when there is a high load though), while the performace one sets all cores to 2ghz. The power hal being used is the one of msm8937, which is also an octa core CPU. This is defined in the power hal's makefile on Lineage's repo (if the processor is msm8953, use the power hal of msm8937). I recommend it to keep the balanced profile (which is enabled by default), but it's up to you.
Kernel
* merged stock kernel source into the CAF one (tag LA.UM.5.6.r1-01300-89xx.0 as this one semeed to be the closest to stock, but also based on the Adreno log)
* got rid of many drivers from Huawei. You can see the commits here. Thanks to @gt_o, huawei's bootfail monitor (HWBFM) has also been removed. Although HWBFM was disabled till now, it was better to get rid of it, to get a cleaner kernel, but also being easier to merge the stock source into CAF.
* cpuset updates (also in ramdisk)
* added WireGuard support, thanks to @zx2c4. WEBSITE | XDA
* removed fsync/crc toggles as it's better to not mess with them
Click to expand...
Click to collapse
9 December 2017
ROM
* synced Lineage sources
* added Substratum support
* fixed blinking mode of notification light
* allow minimum brightness 1 (it was 4 before)
* possibly fixed the power usage reported by bluetooth ( i can't test right now as phone is charging and can;t reset the battery stats)
* Reverted this commit (more details there)
Kernel
* fixed hotspot
* cleaned ramdisk
Click to expand...
Click to collapse
25 November 2017
ROM
* security patch 6 November 2017
* fixed signal icon on 3G (it isnt empty / gray anymore)
* fixed flac audio playback
* updated media configs to N B382
* hide sRGB toggle in developer options
* increased the number of voice call steps from 5 to 8, and media volume steps
from 15 to 20
* increased the handset volume from the default (84) to 88 to improve UX with voice calls
* added ext4 support for /data
* added f2fs support for /cache
* added glove mode (Settings > Display > High touch sensitivity)
* from now on, Lineage`s root is included (Settings > Developer Options > Root Access. If you want to install Magisk or something else, please uninstall Lineage`s root by flashing addonsu-remove-14.1-arm64-signed.zip in TWRP before installing Magisk or something else.
Kernel
* fixed logd/klogd issue (the high cpu usage)
* disabled HUAWEI_DEBUG_MODE config
* added DriveDroid support: allows you to boot your PC from ISO/IMG files stored on your phone [UNTESTED]
* added USB HID gadget support
* CRC toggle; enabled by default (disable it for 30% performance improvement at the risk of data corruption, according to its description)
* FSYNC toggle; enabled by default (disable it to possibly increase performace at the risk of data corruption
Click to expand...
Click to collapse
13 November 2017
* initial release
Click to expand...
Click to collapse
Reserved
Dowloanding ^^
As soon as I can, I'll report back =)
Thank You #Henkate for keeping Nova alive!
Hi, i was waiting for LOS14 so much, thank you for the hard work <3. I just have a few concerns about the unlocking bootloader/rooting/twrping stuff of my MLA-L11, since noone of the methods has been confirmed to work on that model.. And i simply can't risk a 300 € brick. I'm confident with modding, the method seems crystal clear.. Just asking the Dev if he thinks it should works for me. Also, if i should take some cautions and how. Android 7, EMUI 5, full stock. Of course modding is always a risk, but.. you know what i mean. Thanks in advance, i hope that's not off the topic!
Works fine here, thanks a lot for the hard work !!!
Will give it a shot this weekend. I am a teacher and students are doing mid term exams this week, so I kind of need my phone.
For some reason, I can't get it to boot. It is on LOS bootanimation and doesn't boot =/ can't even get a log.
Clean format always, I tried with stock open gapps, pico open gapps, without open gapps. It seems something is wrong with my phone.
then i thought the issue could be I'm coming from EMUI 5.
Then I tried to restore bluesmoothie backup and put LOS over it, nothing =/
I don't know why =/
To all people: I would appreciate if you could write the Nova model on which you've flashed LOS14, if your model is other than CAN-L11.
GertFromTheWell said:
Hi, i was waiting for LOS14 so much, thank you for the hard work <3. I just have a few concerns about the unlocking bootloader/rooting/twrping stuff of my MLA-L11, since noone of the methods has been confirmed to work on that model.. And i simply can't risk a 300 € brick. I'm confident with modding, the method seems crystal clear.. Just asking the Dev if he thinks it should works for me. Also, if i should take some cautions and how. Android 7, EMUI 5, full stock. Of course modding is always a risk, but.. you know what i mean. Thanks in advance, i hope that's not off the topic!
Click to expand...
Click to collapse
Hi there!
Thank you too for the kind words!
I don't know if it'll work, but it has been confirmed that MLA-L03 has been unlocked with the same method. Theoretically, it should work on your MLA-L11 too since it's one of MLA series.
Also, the process of unlocking bootloader is "general", it isn't meant only for one or two phones/models. If I'm not mistaken, I think you can't even brick a phone when you're trying to unlock the bootloader.
If you'll unlock the bootloader and by any chance LOS14 isn't booting on your model, you'll have to relock the bootloader, download EMUI 5 firmware from Firmware Finder and install it.
LOS 13 could be flashed from EMUI 5, so it shouldn't matter for LOS 14 neither.
Vinnom said:
For some reason, I can't get it to boot. It is on LOS bootanimation and doesn't boot =/ can't even get a log.
Clean format always, I tried with stock open gapps, pico open gapps, without open gapps. It seems something is wrong with my phone.
then i thought the issue could be I'm coming from EMUI 5.
Then I tried to restore bluesmoothie backup and put LOS over it, nothing =/
I don't know why =/
Click to expand...
Click to collapse
What's your Nova model? I've forgot .
Did you take a look at the recovery log after you're flashing LOS 14 or the output from recovery itself? Does it really gets flashed properly?
LOS 13 could be flashed from EMUI 5 too, so that shouldn't matter neither with LOS 14.
I'll make an eng boot.img later (when I'll get access to PC), so you'll be able to take a logcat during booting.
#Henkate said:
To all people: I would appreciate if you could write the Nova model on which you've flashed LOS14, if your model is other than CAN-L11.
Hi there!
Thank you too for the kind words!
I don't know if it'll work, but it has been confirmed that MLA-L03 has been unlocked with the same method. Theoretically, it should work on your MLA-L11 too since it's one of MLA series.
Also, the process of unlocking bootloader is "general", it isn't meant only for one or two phones/models. If I'm not mistaken, I think you can't even brick a phone when you're trying to unlock the bootloader.
If you'll unlock the bootloader and by any chance LOS14 isn't booting on your model, you'll have to relock the bootloader, download EMUI 5 firmware from Firmware Finder and install it.
LOS 13 could be flashed from EMUI 5, so it shouldn't matter for LOS 14 neither.
What's your Nova model? I've forgot .
Did you take a look at the recovery log after you're flashing LOS 14 or the output from recovery itself? Does it really gets flashed properly?
LOS 13 could be flashed from EMUI 5 too, so that shouldn't matter neither with LOS 14.
I'll make an eng boot.img later (when I'll get access to PC), so you'll be able to take a logcat during booting.
Click to expand...
Click to collapse
Mine is CAZ-TL10 (chinese). I'll try again (today I won't be able to, maybe thursday or friday) and take the recovery.log which I forgot :/
However, the twrp output was fine. I had some bad lines:
Failed to mount /cust (always have it)
E: unknown command (two lines of this message after flashing the ROM)
Enviado de meu HUAWEI CAN usando Tapatalk
Vinnom said:
Mine is CAZ-TL10 (chinese). I'll try again (today I won't be able to, maybe thursday or friday) and take the recovery.log which I forgot :/
However, the twrp output was fine. I had some bad lines:
Failed to mount /cust (always have it)
E: unknown command (two lines of this message after flashing the ROM)
Enviado de meu HUAWEI CAN usando Tapatalk
Click to expand...
Click to collapse
I see.
I have the second error too, after flashing the ROM. I haven't checked why, but it doesn't seems to affect anything.
As I've said, i'll provide an eng boot.img later, so you'll be able to take a logcat during boot.
#Henkate said:
As I've said, i'll provide an eng boot.img later, so you'll be able to take a logcat during boot.
Click to expand...
Click to collapse
@Vinnom
Here you go. Install it from recovery.
I have a MLA-L03 and I was on LOS13, followed the steps and everything works fine for me.
sk8buoy said:
I have a MLA-L03 and I was on LOS13, followed the steps and everything works fine for me.
Click to expand...
Click to collapse
Are you having the no sim card bug as well ?
Vive le quebec !!!:good:
icutzo said:
Are you having the no sim card bug as well ?
Vive le quebec !!!:good:
Click to expand...
Click to collapse
Nope, this bug is gone now. When I'm on LTE the icon don't show LTE (it show only the signal strength) but data works fine.
I thought it would be possible for me to try and flash again only in thursday, but I could today.
I tried to different ways:
Clear flashing;
Formating data;
Neither worked.
I took 2 recovery logs, before and after formating data.
I took a logcat while booting, thanks to the eng boot.img provided.
The logs can be found here.
I don't have a clue why it doesn't boot =/
I took a look at the logs, everything seems to be flashed without any problem and I can't understand right the logcat. I hope it can be useful
Runs good in MLA-L11 with some issues:
The camera stop ramdon
-the front camera have issues with post processing.
Using the OP Camera works good.
-all the cores are 2.02ghz all the time the phone is active
-When you get the kernel CAF will be a perfect ROM. thanks for the hard work hetanke !
Vinnom said:
I thought it would be possible for me to try and flash again only in thursday, but I could today.
I tried to different ways:
Clear flashing;
Formating data;
Neither worked.
I took 2 recovery logs, before and after formating data.
I took a logcat while booting, thanks to the eng boot.img provided.
The logs can be found here.
I don't have a clue why it doesn't boot =/
I took a look at the logs, everything seems to be flashed without any problem and I can't understand right the logcat. I hope it can be useful
Click to expand...
Click to collapse
The recovery logs looks fine. I see that you have also installed Magisk and a Titanium Backup zip. Just to be clear, you have tried to install it without anything else too?
1) Did you wait about 5 mins ( although i dont think that much time is required)?
2) Can you take a kernel log too?
Run the following command, while booting (let it run few seconds after you think that you have got bootloop):
Code:
adb shell "cat /dev/kmsg"
I cant find anything wrong in logcat neither. I think the stock kernel may not be compatible with your model, so i will need to use the kernel source for your model or compare the two sources and import changes from CAZ-TL10 source into the one im using now.
The stock kernel source which is being used right now is CAZ_NG_EMUI5.0_opensource. According to Huawei`s website, it is meant for:
HUAWEI Nova,HUAWEI Nova Plus, CAN-L10, L11, MLA-L01,L11,L12,L13, Android 7.0, EMUI 5.0
Click to expand...
Click to collapse
When i search for "CAZ" on their website, i find nothing. But there seems to be:
Cannes-AL10_TL10 HUAWEI nova, Cannes-AL10, TL10, Android 7.0, EMUI 5.0
Click to expand...
Click to collapse
Perhaps thats the right one for CAZ-TL10 too?
imkoma said:
Runs good in MLA-L11 with some issues:
The camera stop ramdon
-the front camera have issues with post processing.
Using the OP Camera works good.
-all the cores are 2.02ghz all the time the phone is active
-When you get the kernel CAF will be a perfect ROM. thanks for the hard work hetanke !
Click to expand...
Click to collapse
Thank you too for your words!
By the way, its Henkate. You can also call me Robert .
1) When exactly camera is stopping and how? I didnt encounter this on my CAN-L11
2) What kind of issues does have front camera? My Nova`s front camera got damaged / broken when my Nova has been damaged, therefore i cant use it nor test it.
3) Regarding the cores, ive wrote at "notes" in first post:
The first thing you want to do after first reboot is to install a file manager and rename /system/bin/logd to "logd.bak" and reboot. You have to do this in order to get rid of the high CPU load. Consider this a workaround until the issue gets solved. Note that this breaks logcat, so you'll have to rename it back to "logd" and reboot to be able to take a logcat.
Click to expand...
Click to collapse
Would be nice if you could share a logcat regarding 1) and 2).
{
"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"
}
Moto Z2 Force
Code:
- Your warrenty is now void.
- You have been warned.
- Use at your own risk.
Introduction:
This is the official Lineage OS thread for the Motorola Moto Z2 Force, codename nash.
We support both the Sprint, International, and T-Mobile variants, as their bootloaders are unlockable, while we can 't support the Verizon and AT&T variants, as their bootloaders are permanently locked.
How to install:
Necessary Base Firmware: 8.0.0 (OCSX27.1.2, May 2018) (for TMO, or equivalent security patches for other variants)
Boot the newest TWRP .img from the Official TWRP Project Site.
In TWRP, click "Wipe", "Format Data", then type "yes" as prompted.
ADB sideload the newest weekly
(Optionally) You can flash the newest TWRP Installer also found at the Official TWRP Project Site if you wish to maintain TWRP, though the pre-installed Lineage Recovery instance will do everything you need it to in most cases. We don't recommend or support the use of the TWRP installer, as it is overwritten on every update (will need ot be re-installed every update), and has no addon.d-v2 persistence.
Click "Reboot, then choose "Recovery", this will boot you to either Lineage Recovery or TWRP depending on your choice to install TWRP or not. It is necessary to reboot between ROM flash and GApps/Addon flash due to verity/slot-swap logic.
(Optionally) Flash GApps - MindTheGApps arm64 are recommended, OpenGApps are compatible with A/B as of 09102018, but I still only reccoemend and support MindTheGApps.
(Optionally) Flash SU - you'll need to turn it on from in developer settings after first boot Lineage OS SU Addon. - Magisk works fine, though is not supported.
Reboot
Known Problems:
Audio Mods don't work (this includes headphone jacks on mods) -- We can't fix this, don't use custom ROM's if you care about these.
Official Lineage OS builds will not ever allow Moto's Battery Mod "Efficiency Mode" to work -- though these can be made to work unofficially, join our discord if you're interested in this feature.
Wi-Fi Calling won't work until either the International or T-Mobile variant gets 8.1 blobs.
Ultrasonic Proximity Sensor doesn't work -- likely won't ever. It is used my Motorola's Active Display, but by nothing in Lineage.
Compass doesn't work -- no clue why.
Stock Display Color Profiles (the ones in Settings, "Display", "Colors") -- The ones in Settings, "Display", "LiveDisplay" work.
The default LiveDisplay "Natural" setting in Settings, "Display", "LiveDisplay", will occasionally dispaly color corruption, to deal with this, just swap to the "SRGB" profile, and swap back to "Natural", or leave it on "SRGB if you don't mind, then you won't experience those infrequent issues.
Notes:
Official Lineage OS builds will not pass CTS/SafetyNet -- due to the AVB flag's "red" status.
Official Lineage OS builds ship with full treble compatibility, with VNDK runtime enforcement! This means that unlike most "ported treble" you'll see, ours is just as it would be from the OEM, and can run any GSI (yes, even Pie!) without need for hacks or additional flashable zips. We relabeled /oem as /vendor (as /oem isn't used in custom ROM's anyway). To use a GSI, flash official Lineage, then flash your GSI, it's that simple! Flashing a factory image will likely write over /oem and remove the mock vendor image. Please don't report GSI bugs here, report them instead to the GSI's maker.
Download:
LineageOS Updater
XDA:DevDB Information
[OFFICIAL] [WEEKLIES] [TREBLE] Lineage OS 15.1, ROM for the Moto Z2 Force
Contributors
npjohnson, invisiblek, erfanoabdi
Source Code: https://github.com/LineageOS
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
ROM Firmware Required: 8.0.0 (OCSX*)
Based On: LineageOS
Version Information
Status: Stable
Created 2018-07-15
Last Updated 2019-03-18
first (always wanted to do that)
thanks for this, nice work everyone!!!
Nice, I was wondering when we were going to get an official thread. I'll be waiting for the 17th to install the weekly.
I have the international version (-05) and have installed plenty of these version (since unofficial release from both invisiblek site and ods.ninja site) as well as the official weeklies (all versions already released) and everything works (based on the description here and known issues), so I'd say it's safe to say intl version had been tested and known to be working as well.
Let me know if you need additional/specific tests that I can do here.
Thanks the official post!
Also, how about volte support? Is it supposed to work?
felipevsw said:
I have the international version (-05) and have installed plenty of these version (since unofficial release from both invisiblek site and ods.ninja site) as well as the official weeklies (all versions already released) and everything works (based on the description here and known issues), so I'd say it's safe to say intl version had been tested and known to be working as well.
Let me know if you need additional/specific tests that I can do here.
Thanks the official post!
Also, how about volte support? Is it supposed to work?
Click to expand...
Click to collapse
If it isn't in the bugs list, its expected to work, it works on TMO and SPR. And I'll flag the international as compatible, thanks.
Since it isn't in known issues, I assume VoIP compression was fixed?
Edit: known workaround is use Bluetooth for video/VoIP calls. I don't know if USB audio would work or not.
Uzephi said:
Since it isn't in known issues, I assume VoIP compression was fixed?
Edit: known workaround is use Bluetooth for video/VoIP calls. I don't know if USB audio would work or not.
Click to expand...
Click to collapse
Added to OP as an issue.
??? for listing known accurate issues ???
I was pissed after installing Invictrix rom only to find out sound mods don't work.
I'm having an issue with video calls on Whatsapp and Duo. The other person can't hear me and I can't hear the other person.
Some other issues:
- Ok google not working with screen off (but it's fine to me)
- Overview is messy sometimes when using multi-window (doesn't show previews of multi-windowed apps)
- Even when installing Moto Camera the app does not show secondary camera functions (Portrait, B/W, etc)
For my daily usage the audio on video calls is the most serious issue that drives me back to stock. I hope they fix it soon.
fixed, can remove this.
DTHayakawa said:
I'm having an issue with video calls on Whatsapp and Duo. The other person can't hear me and I can't hear the other person.
Some other issues:
- Ok google not working with screen off (but it's fine to me)
- Overview is messy sometimes when using multi-window (doesn't show previews of multi-windowed apps)
- Even when installing Moto Camera the app does not show secondary camera functions (Portrait, B/W, etc)
For my daily usage the audio on video calls is the most serious issue that drives me back to stock. I hope they fix it soon.
Click to expand...
Click to collapse
Anything that uses VoIP compression is broken. Most video calling or internet calling apps in general use it.
DTHayakawa said:
I'm having an issue with video calls on Whatsapp and Duo. The other person can't hear me and I can't hear the other person.
Some other issues:
- Ok google not working with screen off (but it's fine to me)
- Overview is messy sometimes when using multi-window (doesn't show previews of multi-windowed apps)
- Even when installing Moto Camera the app does not show secondary camera functions (Portrait, B/W, etc)
For my daily usage the audio on video calls is the most serious issue that drives me back to stock. I hope they fix it soon.
Click to expand...
Click to collapse
1. Added to known bugs.
2. I don't experience this (and if it is present, its platform wide, and not our problem specifically).
3. I can't really easily support a prebuilt app all that easily. The B&W cam us supported in the default Snap camera.
Also, OTA will be broken until we figure out why signing server's aren't signing our payload zips right.
To work around this, you can update weekly by sideloading the nightly, rebooting to recovery (important), re-sideloading any mods you use (GApps, AddonSU, etc.).
fixed, can remove post now.
Uzephi said:
Anything that uses VoIP compression is broken. Most video calling or internet calling apps in general use it.
Click to expand...
Click to collapse
So I assume this would apply to hangouts and hangouts dialer?
npjohnson said:
Also, OTA will be broken until we figure out why signing server's aren't signing our payload zips right.
To work around this, you can update weekly by sideloading the nightly, rebooting to recovery (important), re-sideloading any mods you use (GApps, AddonSU, etc.).
Click to expand...
Click to collapse
Resolved.
Unable to install Lineage su addon (using TWRP 3.2.2-2)
_BEGIN_
Installing su addon...
set_metadata: Error on lstat of "/system/etc/init/superuser.rc": too many symlinks encountered
Updater process ended with ERROR: 7
_END_
Thoughts?
MattKilla said:
Unable to install Lineage su addon (using TWRP 3.2.2-2)
_BEGIN_
Installing su addon...
set_metadata: Error on lstat of "/system/etc/init/superuser.rc": too many symlinks encountered
Updater process ended with ERROR: 7
_END_
Thoughts?
Click to expand...
Click to collapse
I was literally plugging in to try this ROM until I read this. Have you tried Magisk yet?
Magisk Works
3's&7's said:
I was literally plugging in to try this ROM until I read this. Have you tried Magisk yet?
Click to expand...
Click to collapse
I have ran into this same issue when flashing build > lineage-15.1-20180721-nightly-nash-signed.zip
I can confirm that it happens with both TWRP 3.2.2-2 & TWRP 3.2.1-1
I flashed Magisk 16.4 and it works flawlessly no issues.
I am very happy with this ROM it works great for me. Thank You Devs! :good:
MattKilla said:
Unable to install Lineage su addon (using TWRP 3.2.2-2)
_BEGIN_
Installing su addon...
set_metadata: Error on lstat of "/system/etc/init/superuser.rc": too many symlinks encountered
Updater process ended with ERROR: 7
_END_
Thoughts?
Click to expand...
Click to collapse
was TWRP installed or did you just boot to 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"
}
Samsung Galaxy S4
Code:
- Your warranty is now void.
- You have been warned.
- Use at your own risk.
Introduction:
This is the Official Lineage OS 18.1 thread for all Galaxy S4 variants.
Downloads:
Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed.
Official Builds:
jactivelte (GT-I9295)
jflteatt (SGH-I337) - Please note you will need to be on bootloader I337UCUAMDB or I337UCUAMDL
jfltespr (SCH-R970/C/X, SPH-L720)
jfltevzw (SCH-I545) - Please note you need to be on bootloader I545VRUSMDK
jfltexx (GT-I9505, SGH-I337M, SGH-M919) - NOTE: GT-I9505G is supported in this build, but due to system size space limitations it will not fit any form of GApps package.
jfvelte (GT-I9515/L)
Unofficial - built once a month by me, includes GApps and Pixel goodies:
jactivelte (GT-I9295)
jflteatt (SGH-I337) - Please note you will need to be on bootloader I337UCUAMDB or I337UCUAMDL
jfltespr (SCH-R970/C/X, SPH-L720)
jfltevzw (SCH-I545) - Please note you need to be on bootloader I545VRUSMDK
jfltexx (GT-I9505, SGH-I337M, SGH-M919) - NOTE: GT-I9505G is supported in this build, but due to system size space limitations it will not fit any form of GApps package.
jfvelte (GT-I9515/L)
If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.
Known Bugs:
MHL doesn't work after LineageOS 14.1, and likely never will again, as Google dropped support for it platform-wide in AOSP.
Find any? Report them according to this guide.
Notes:
The only supported GApps package at the moment is MindTheGapps, linked on our Wiki page about gapps.
Kernel Source: https://github.com/LineageOS/android_kernel_samsung_jf
good and many thanks
Is MindTheGapps like pico or nano Gapps?
Thanks @npjohnson and of course the one how did the most work: @arco68
all seems good so far.
just and only if someone stumbles over it, two hints:
1. Hint:
On an linux box I followed the install instruction " Installing a custom recovery using heimdall" and the following from here:
Install LineageOS on jfltexx | LineageOS Wiki
wiki.lineageos.org
It seems the second TIP on the page is wrong/outdated.
cit.: "TIP: If the process succeeds the output will stop at 47% and report adb: failed to read command: Success."
*I* got no "failed to read command: Success."
Don't wonder, the Rom installed correct !
see attached photo's
2. Hint:
if one is searching for the "advanced power menu", it's now under system => gesture.
AFAIK, for LOS 17.1 it had been under the dev. opt's
I have problems installing apps from google play, it gives me a storage error and my mobile is empty, any solution?
joam280 said:
I have problems installing apps from google play, it gives me a storage error and my mobile is empty, any solution?
Click to expand...
Click to collapse
what is empty ?
try a reboot...
rw_on_xda said:
Thanks @npjohnson and of course the one how did the most work: @arco68
all seems good so far.
1. Hint:
I followed the install instruction and it seems the second Tip is wrong/outdated.
cit.: "Tip: If the process succeeds the output will stop at 47% and report adb: failed to read command: Success."
*I* got no "failed to read command: Success." (see attached photo's)
2. Hint:
if one is searching for the "advanced power menu", it's now under system => gesture.
AFAIK, for LOS 17.1 it had been in the dev. opt's
Click to expand...
Click to collapse
Please note that if you’re currently on an official build, you DO NOT need to wipe your device, unless your device’s wiki page specifically dictates otherwise, as is needed for some devices with massive changes, such as a repartition.
Click to expand...
Click to collapse
What that means @rw_on_xda ? If im on the official 17.1 can i just upgrade to 18.1? "Dirty flash" possible to 18.1 from 17.1 ?
EDIT:
Dirty flash from official 17.1:
Wiped Cache, Dalwik ART Chache, System rebooted to TWRP:
1. Flashed LOS 18.1
2. OpenGapps
3. Magisk
Everything works well for now.
Regards !
bersem said:
What that means @rw_on_xda ?...
Click to expand...
Click to collapse
What does what mean ?
hello!
with here maps I can't select sdcard for saving maps. With previuos lineage OS I haven't any problems
Savatage76 said:
hello!
with here maps I can't select sdcard for saving maps. With previuos lineage OS I haven't any problems
Click to expand...
Click to collapse
That's not a ROM issue. Rules for external SD have changed in android 11. Apps have to comply.
deleted
rw_on_xda said:
what is empty ?
try a reboot...
Click to expand...
Click to collapse
problem solved with a format
@npjohnson Ahaha, well played!
So the april fool of 2021 for S4 has been that LOS18.1 on 1st of April for wasn`t a hoax for real...
I fell for it.
Thx to all involved making 18.1 happen on this device
bersem said:
What that means @rw_on_xda ? If im on the official 17.1 can i just upgrade to 18.1? "Dirty flash" possible to 18.1 from 17.1 ?
EDIT:
Dirty flash from official 17.1:
Wiped Cache, Dalwik ART Chache, System rebooted to TWRP:
1. Flashed LOS 18.1
2. OpenGapps
3. Magisk
Everything works well for now.
Regards !View attachment 5267359
Click to expand...
Click to collapse
Hi,
Which TWRP did you used for that? The official last one is 3.2.3-0 and as far as I remember doesn't work completely on ours S4 (GT-I9505 at least). I only used it to make backups then I changed to LOS recovery un order to have automatic updates.
Thanks in advance
hello!...another question...
I can't find lens for search a song or other in stock music player. where is it?
Hi again,
I also dirty flashed using TWRP 3.2.3-0 (backing up previously) and all works fine for me at this moment. At the end, I flashed LOS Recovery to prevent issues when next updates arrives.
I have noticed that there is a "new?" option into LOS updater preferences that allow to update the recovery. I switched on to see how it works
Gitanitos said:
Hi again,
I also dirty flashed using TWRP 3.2.3-0 (backing up previously) and all works fine for me at this moment. At the end, I flashed LOS Recovery to prevent issues when next updates arrives.
I have noticed that there is a "new?" option into LOS updater preferences that allow to update the recovery. I switched on to see how it works
Click to expand...
Click to collapse
im using the last one:
twrp-3.5.1_9-0-jflte.img
no problems with updater.
EDIT: The secure method to upgrade to 18.1:
LOS upgrade Wiki
bersem said:
im using the last one:
twrp-3.5.1_9-0-jflte.img
no problems with updater.
EDIT: The secure method to upgrade to 18.1:
LOS upgrade Wiki
Click to expand...
Click to collapse
Thanks for the answer, I've checked before and I didn't found this recovery maybe a wrong web... let's see first how it works the recovery update and later will try these TWRP.
And for sure the safest way to upgrade is the LOS Wiky (I upgraded my old S4 since LOS14 ) but sometimes I love to try alternative methods.
Have a good day
@npjohnson
Bah... introduced in Android 11
Code:
/system_ext
wtf
"The /system_ext partition
The /system_ext partition was introduced in Android 11 as an optional partition. (It’s the place for non-AOSP components that have tight coupling with the AOSP-defined components in the /system partition.) The /system_ext partition is assumed to be the OEM-specific extension to the /system partition, without an interface defined across the two partitions. Components in the /system_ext partition can make private API calls into the /system partition, and components in the /systempartition can make private API calls into the /system_ext partition."
AOSP
As i understood, this is a dynamic mounted img, no way to rw (at least i haven`t found a way yet), so you can`t remove some of the default apps under /system_ext/apps or /system_ext/priv-app, like snap or camera.
As mentioned in the link above,
"The /system_ext partition is optional, but it’s beneficial to use it for any custom features and extensions that are tightly coupled with AOSP- based components. This distinction helps you identify changes you need to make, to move such components from the /system_ext partition to the /productpartition over a period of time."
Wouldn`t it be better to move them back to /system/priv-app or product? At least, people, who don`t use these apps could remove them, like they can with i.e. the music or audiofx app. This is somehow inconsistent, or is there a reason, why some of the "LOS-Bloat" ( ;-) ) is located under /system_ext/priv-app and others don`t?
many thanks all developers - great work.
i had dirty flashed from official 17.1 with 65 installed apps yesterday
(SAMSUNG_I9505)
rebooted to TWRP (twrp-3.5.1_9-0-jflte)
0. wiped only system/dalvic/cache:
1. flashed LOS (lineage-18.1-20210401-nightly-jfltexx-signed.zip)
2. MindTheGapps-11.0.0-arm-20210328_143701
3. magisk 22.0
everything works well.
but there was to much google-apps.
i had unzipped MindTheGapps-11.0.0-arm-20210328_143701
and reduced apps like "open_gapps-arm-pico"
deleted:
system/product/app/GoogleTTS
system/product/app/talkback
system/product/priv-app/AndroidAutoStubPrebuilt
system/product/priv-app/Velvet
and zipped again "MindTheGapps-11.0.0-arm-20210328_reduced"
also once again
0. wiped only system/dalvic/cache - rebooted to TWRP:
1. flashed LOS 18.1
2. MindTheGapps-11.0.0-arm-20210328_reduced
3. magisk
everything works well for now.