Related
does anyone has any idea why we can't flash aroma zips on U12+ ? same thing applies to OP6
I know AROMA is an abandoned project from almost 4 years ago, but popular devs like Team Venom @LeeDroid @flar2 etc... still use it for custom ROMs and kernels for the ability to provide customizations and different variants of the same device and/or carriers. that being said I call any user with coding skills to help bring this project back to life since the original dev abandoned his amazing work for quite some time but the source code is available at:
https://github.com/amarullz/AROMA-Installer
for those interested to help
also I have created an issue on TWRP github & AROMA github itself
https://github.com/TeamWin/Team-Win-Recovery-Project/issues/1291
https://github.com/amarullz/AROMA-Installer/issues/38
I know the issue has probably nothing to do with TWRP but I thought it would get more attention there than on AROMA github since it was abandoned, but at the same time it is related to custom recoveries since AROMA itself doesn't work on it's own it depends on a custom recovery in this case TWRP being the only custom recovery being widely available for newest devices.
possible reasons for failure (brainstorming)
1. AROMA source code needs updating
2. apparently the issue it only affect Treble A/B devices
3. the newest devices doesn't have a cache partition
4. you tell me
here are some logs with different aroma zips
Disclaimer:
LineageOS (Lineage Android Distribution) members or anyone else on this website is 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 the products you find here 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. Your warranty will be void if you tamper with any part of your device / software.
How to Install:
1- BACKUP, BACKUP, BACKUP, All will be WIPED!
2 - Unlock bootloader instructions here
3 - Flash the new mandatory TWRP Recovery
4 - Move Rom & Gapps (optional) into device storage
5 - Full Wipes
6- Flash Rom & Gapps (gapps are OPTIONAL)
for GAPPS:
Choose Gapps Package "ARM" > "6.0" > "Pico" or "Nano" visit OpenGAPPS
Working:
Boots
Storages
Bluetooth
Wifi
GPS - GNSS
Audio
Charging
Offline Charging
Video decoding/ Playback (i.e.: Youtube) up to 720p
android marshmallow new features: Adoptable Storage / Multi Window / etc
DRM Widevine : For Netflix, Amazon Prime, etc
Sensor: magnetometer: akm8963
Front Camera: mt9m114_mipi_raw
Front camera: GC0339_RAW
etc ....
NOT Working:
Rear Camera: a5142_mipi_raw
Front Camera: GC0339_RAW (ME173X 8GB) Fixed on build 20220629
Sensors: accelerometer (autorotation)
You tell me
Special Thanks
OMNI Rom
LineageOS
DerTeufel1980 & fire855 ( my Team mates from M.A.D)
GPL Compliance:
GitHub - dragonpt/android_device_asus_me173x: ASUS ME173x device for LineageOS 12.1 & LineageOS 13
ASUS ME173x device for LineageOS 12.1 & LineageOS 13 - GitHub - dragonpt/android_device_asus_me173x: ASUS ME173x device for LineageOS 12.1 & LineageOS 13
github.com
GitHub - dragonpt/android_kernel_asus_me173x_new: ASUS ME173x [MT6589 - MT8125] Custom Kernel for LineageOS 12.1 / 13 / 14.1
ASUS ME173x [MT6589 - MT8125] Custom Kernel for LineageOS 12.1 / 13 / 14.1 - GitHub - dragonpt/android_kernel_asus_me173x_new: ASUS ME173x [MT6589 - MT8125] Custom Kernel for LineageOS 12.1 / 13 / ...
github.com
--> "asus_mm" branchs
FAQ
Small FAQ:
Q: How can i Unlock the Bootloader?
A: Instructions for Unlocking the Bootloader can be found here
Q: After locking the screen, the screen is all black, and/or flickering and I'm forced to reboot, how can I fix this?
A: If you have this issue, then your device uses the second screen/lcm hardware revision
( the lgld070wx3_dsi_vdo ), please use the second kernel.zip for this variant, it'll be added an second kernel . zip for people with this variant, on the download section with the ROM release
Q: how to flash this second kernel for the new hardware variant ?
A: After flashing the ROM, flash the second kernel afterwards
Q: Where are the Developer Options?
A: Go to Settings>About Tablet, and tap 7 times on the Build Number
Q: Where is the multi-window mode?
A: in the developer options, you can enable it there
Q: How can i root this rom?
A: you can use Magisk , or SuperSU
Magisk: v.23
SuperSu v2.82
note: Magisk builds v24.x and v25.x do NOT work.
Q: Do i really need to update recovery?
A: YES
Q: I can't flash this Rom on recovery, why?
A: You need to update your recovery to TWRP
Q: how to work with twrp?
A: in the first time TWRP boots, it'll ask if you want to allow modifications, slide to YES
Q: how to wipe and flash in twrp?
A: Go "mount" and mount "system"
then go "wipe" > and wipe dalvik / cache / data / System
Q: How can i flash the new recovery?
A: If you already have an custom recovery installed:
Download the new TWRP recovery zip
flash the new recovery
reboot to recovery again, TWRP should be now installed
If you don't have any custom recovery installed:
- You can extract the "recovery.img" from the .zip
- Open an terminal
- Boot to fastboot mode, and type:
Code:
fastboot flash recovery recovery.img
then reboot:
Code:
fastboot reboot
Q: I Love your work, how can i thank you?
A: You can press the "Thanks" button, and if you wish, you can pay me a beer
..
Changelogs
Build 20201221
First Release
Build 20210821
Kernel:
DCT / Power resolve more issues
LCM: nt35521_dsi_vdo: Add backlight enable ctrl function
Fix magnetometer sensor: akm8963
Battery: Corrections
Camera LENS AF (for the rear camera) fixed
Front Camera : mt9m114_mipi_raw ( ME173X 16GB Version) fixed
mmc: more handling fixs
msdc: more fixs
Touch Panel: GT927: Implement a proper suspend & resume
Some other small fixs.
LineageOS source and device:
LineageOS LiveWallpapers, Wallpapers are now included ( as per-user requests)
Gello browser removed, it's depricated and has security risks
Disable Live Display by default (not supported by this device)
Some device clean up
Fix some eGL crashs
Fix some core missing symbols
Added Front camera support ( Pictures )
Some other small fixs.
Build 20220629
Kernel:
Security: Fix the following security issues:
PG SU daemon security fix
CVE-2017-1000365
CVE-2017-2618
CVE-2017-2671
CVE-2016-10208
CVE-2016-10208
CVE-2013-4312
CVE-2016-2550
CVE-2017-9074
CVE-2017-9075
CVE-2017-9076
CVE-2017-9077
CVE-2017-9242
LVT-2017-0002
CVE-2012-6703
CVE-2015-8944
CVE-2016-3857
CVE-2016-9555
CVE-2017-8890
ARM: spectre-v1
ARM: spectre-v2
ARM: Merge some bug fixs
imgsensors:
mt9m114_mipi_raw: Enable NightMode & Improve NightMode handling (better handling of Low light pictures)
gc0339_raw support added (CMOS front camera used in some HW revisions)
Memory management / Others:
Merge ZRAM from Kernel 3.10 version, and backport K 3.10 ZRAM fixs
Merge zsmalloc from Kernel 3.10 version, and backport K 3.10 ZRAM fixs
Add support for LZ4 decompression in the Linux Kernel
Other minor fixs
LineageOS source and device:
device: Added 512 MB Virtual SWAP Memory
Fix GPU PowerVR blobs crash, leading to random reboots & wakeup reboots
Disable OpenGL preloading with PowerVR drivers
SHIM: Add UI shim lib to fix some other random crashs
Remove max app limit
ART: Increase and fine tune the heap limit
Camera & nvram blobs fixs
Other minor fixs
Build 20220718
Fixed Bluetooth, that got broken by mistaque on 20220629 release
Downloads
TWRP 3.1.1
TWRP_3.1.1_ME173X.zip | by superdragonpt for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
Build 20220718
https://androidfilehost.com/?fid=15664248565197191338If you have the second hardware Screen revision by LG (check FAQ), flash this
kernel for the Build 20220718
https://androidfilehost.com/?fid=15664248565197191342
Old Builds
Build 20220629
https://www.androidfilehost.com/?fid=15664248565197184858If you have the second hardware Screen revision by LG (check FAQ), flash this
kernel for the Build 20220629
https://www.androidfilehost.com/?fid=15664248565197184860
Build 20201221
lineage-13.0-20201221-UNOFFICIAL-me173x.zip | by superdragonpt for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
If you have the second hardware Screen revision (check FAQ), flash this
kernel for the Build 20201221
Kernel_rev2_Build_20201221.zip | by superdragonpt for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
Build 20210821
https://www.androidfilehost.com/?fid=7161016148664790672If you have the second hardware Screen revision by LG (check FAQ), flash this
kernel for the Build 20210821
https://www.androidfilehost.com/?fid=7161016148664790675
Man, you're awesome
But I have issue with wifi. Cant turn it on and my mac adress is 02:00:00:00:00
Bluetooth also not working
gadom92 said:
Man, you're awesome
But I have issue with wifi. Cant turn it on and my mac adress is 02:00:00:00:00
Click to expand...
Click to collapse
Same here
Awesome work, thx and merry xmas
gadom92 said:
Man, you're awesome
But I have issue with wifi. Cant turn it on and my mac adress is 02:00:00:00:00
Bluetooth also not working
Click to expand...
Click to collapse
This seems to be the very same issue some users had with Lineage 12.1...
can** replicate this on my units.
EDIT: i meant, can't replicate this
please try this:
[ROM] [UNOFFICIAL] LineageOS 12.1 |ASUS Memo Pad HD 7 (me173x) [MT8125]
Disclaimer: LineageOS (Lineage Android Distribution) members or anyone else on this website is not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if...
forum.xda-developers.com
Settings > Backup & reset
superdragonpt said:
This seems to be the very same issue some users had with Lineage 12.1...
can replicate this on my units.
please try this:
[ROM] [UNOFFICIAL] LineageOS 12.1 |ASUS Memo Pad HD 7 (me173x) [MT8125]
Disclaimer: LineageOS (Lineage Android Distribution) members or anyone else on this website is not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if...
forum.xda-developers.com
Settings > Backup & reset
Click to expand...
Click to collapse
Did not solve the problem so far. Wifi is even broken after restoring the los 12.1 backup which worked before
Edit: uploaded logcat
Ok, i reflashed the old carliv recovery via fastboot after installing Los13 and i got wifi back ...
And afterwards i flashed twrp again via fastboot and wifi is still working...
Previously i flashed the twrp zip from carliv, i guess this was part of the problem
reflashing recoveries in fastboot not worked for me :/
I also wiped everything including internal storage before, and bootet into each of the two recoveries and to the system from there.
Maybe the carliv recovery changes some things on the system, idk.
Hi, I am so glad that this is still alive project
I upgraded recovery via mtk flesher. Just rename twrp 3.1.1... into recover.img and click "download".
My wifi and bluetooth are working. Sometimes bluetooth have conflict with wifi and plain reboot fix things.
It is strange that not a single one sensor work(acceleration and gravity, magnetic field, orientation and rotation. They all worked in 12.1 beside rotation. Hope thing are going to get fixed up.
Had a few freezes also(hard reset do the job)
Overall I have a feeling that this is smoother than 12.1.
EDIT: It was misleading about recovery flash. You need to extract from twrp_3.1.1_ME173X.zip "recovery.img" and replace in folder where scatter file with old "recovery.image" is.
Gronkdalonka said:
I also wiped everything including internal storage before, and bootet into each of the two recoveries and to the system from there.
Maybe the carliv recovery changes some things on the system, idk.
Click to expand...
Click to collapse
interesting... likely the wiping of internal storage fixed it..
if anyone is having this issue, please try and report back if the following fixs:
in twrp:
Flash this test kernel
AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
cheers
Merry Xmas
superdragonpt said:
interesting... likely the wiping of internal storage fixed it..
if anyone is having this issue, please try and report back if the following fixs:
in twrp:
Flash this test kernel
AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
cheers
Merry Xmas
Click to expand...
Click to collapse
not working :/
edit: Flashed old recovery trough Flash Tool, than TWRP in Flash tool wipe all what i can and then install LOS 13. Wifi working like a charm
Any chance you can help with source patches?
First of all thanks to snapdragon for the new LOS13 support.
I'm sorry to tell you that all of your mentioned ways to get WiFi back to work did not work for me. What I did and what I tried:
Normal installation way:
Flashed new recovery via old custom recovery
complete wipe
flashed new LOS13 via new TWRP recovery
WiFi not working!
Going back to old custom recovery and back to TWRP
Flashed old custom recovery via TWRP
complete wipe
flashed new TWRP custom recovery via adb sideload since my sd card can only be mounted via new TWRP recovery
complete wipe
flashed new LOS13
WiFi still not work!
This is all I did. I realized that fastbood mode is not working for my device, could be a driver problem since my device is installed as ùó something when plugging it into the pc in fastboot mode, so I tried the way via adb.
Hint: I have the model with the alternative hardware, so the second kernel is required to fix flickering display issue.
I realized that the new TWRP recovery has this issue aswell, so my display is flickering from the right side to the center sometimes in TWRP recovery.
Any ideas what could help getting WiFi back to work?
Thanks in advance!
Edit: Could it be that this WiFi problem has something to do with the following thread:
FIX FOR MAC 02:00:00:00:00(WiFi and hotspot not turning ON)
Important. Root required..... Hey everyone,I saw so many posts regarding Android & iOS that the Mac address is changing to 02:00:00:00:00 and WiFi is greyed out. None of the WiFi or hotspot not turning on.I get the same problem in my Condor and...
forum.xda-developers.com
I read over some postings and googled the mac address 02.00.00.00.00 and it seems that a lot of devices had this problem when updating from android 5 to 6. It seems that it could have something to do with the partitions where the info (mac address, IMEI) are stored, but in general I have not found a solution and a specific description of the problem.
Anyway: If the problem can be solved by doing the steps described in the thread I provided above I’m not able to solve this. I would not describe me as a noob, but it seems that I need root and knowledge of permission management for the fix, and I am not very familiar with Linux.
Could you do the following test:
In twrp:
Full wipes ( system, etc etc and internal storage) be sure you back up your stuff
Then reboot to recovery
( It'll warn there's no OS installed)
Back to recovery
Do full wipes again , plug the tab into pc and copy the rom to internal storage
Reboot to recovery again
( It'll warn again, there's no OS installed)
Proceed to flash the rom
This has worked with a user
Issue: for an unknown reason some devices seems to fail mounting / reading nvram
@ twrp I'll do a build for people with this second hardware revision, flickering is annoying...
Thanks for your fast reply.
I did two full wipes with rebooting into recovery after each wipe as you said, then I copied the OS zip file to internal storage and rebooted again to recovery.
After installing the ROM I rebootet to system and LineageOS was preparing the first start. I started without flashing the kernel for alternative hardware (2nd kernel) to check if it works first.
I'm sorry to tell you that I still got no WiFi and Bluetooth connections, Mac address still is shown as 02-00-00-00-00, WiFi cannot be turned on.
Edit: Seems that is has nothing to do with wipes (on my device). I've tried all kind of wipes via TWRP
Format Data -> yes -> reboot to recovery
Advanced Wipe -> check all (Davlik, Cache, Data, Internal Storage, System -> Again format data -> Yes -> reboot to recovery
flashed ROM, 2nd Kernel and GApps -> Reboot to recovery -> reboot to system
Still no WiFi. Perhaps I should try to go back to stock rom and see if WiFi works there? Do you think this could make the deal?
test this
full wipes
flash rom, then this kernel afterwards
AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
Again, thanks for your efforts, it seems to be a really tough and bugging one, since the new kernel did also not fix the problem.
Edit: Just to keep u updated: I just flashed old recovery and afterwords old LineageOS 12, WiFi is working well. So there must be some problem with the update or the update process. I will try to wipe first and then install new recovery and again install new OS, perhaps this will do the job.
Edit2: BTW I forgot to tell you that I had problems with settings -> about tablet -> status on lineageos 12. Just remembered because i wanted to have a look to the mac address. I get an error telling me "unfortunately, settings has stop". Perhaps important for the update?
Important Edit3:
Guess what: I made it to work. I did the following to do it:
1. Format Data and do all wipes possible with TWRP recovery. Reboot to recovery and do the same again.
2. TWRP recovery -> install old recovery
3. In old recovery -> install via sideload (adb sideload) lineageOS12 and second Kernel (for me because of hardware)
4. Boot to system and check if WiFi works well (finish the initialization of the device and connect to a WiFi)
5. Boot to recovery (old recovery) -> WITHOUT WIPING install via sideload TWRP recovery
6. Boot to system. (Still lineageos12) check if WiFi still works
7. Boot to TWRP recovery -> WITHOUT WIPING install lineageos13.
8. Boot to system, finish initialization if necessary and check if WiFi still works.
9. Go to setting and do a factory reset from lineageos13 settings
10. Device will reboot to recovery and do the factory reset and automatically will boot back into system.
11. Finish. All should work now.
I don't know what exactly did the job, so I wanted to provide all steps I did.
Since I never flashed an android custom Rom over another without wiping I don't know what errors this procedure can cause. So if someone knows that please let me now that I can have a look if there are errors.
Thanks again for your assistance.
{
"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"
}
Disclaimer:
Not responsible for any injuries you do to yourself or your device being damaged caused by this ROM.
Big thanks goes to @Steel01 for all the hard work and the Sources.
LineageOS is a free, community built, aftermarket firmware distribution of Android, 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.
Hi Everyone
After some months of learning how to build my own Roms and how to edit the proprietary files of this Device i was able to build my first edited version of LineageOS 15.1 with HW Acceleration and the Camera working.
Its a slim an snappy Rom for everyone that´s looking for a monthly updated Android 8.1 Rom to keep this unique Device alive.
This first release is really basic because i deleted everything that doesn't work right.
My plans for this Rom are to keep it updated in case of Security Patches and add some Features here and there as i still learn how this Device and Android is working in general.
Also the official release of LineageOS 16 will end the development of this Rom for the reason i don't want to rival the official contributors of this Device.
Little FAQ to this Rom:
Do i need to Wipe my existing Rom even its LineageOS 15.1 based ?
Yes because i use my own Release Keys for this Rom you need to Wipe your existing one.
Is this Rom compatible with every Shield Tablet ?
Yes this Rom is working with every Shield Tablet
I have a Shield LTE Version and after flashing this Rom i cant connect my device for Data Transfer with my computer anymore.
For some Reason i still didnt found out on LineageOS 15.1 there is no Drop Down Menu for this Device to change the type of connection.
To change it go to Settings > Connected Devices > USB
I found a Bug with this Rom i didnt had on any Rom before what should i do before i post it here ?
Before you post any Bugs and Errors here make sure you installed this Rom correct as i told with a full wipe in your recovery first and if there are modifications installed like Magisk
Moduls or Xposed or you changed this Rom in any way, you should reinstall it fresh first to take a look if the issue still occurs.
If yes post a detailed report of the Error with a Logcat.txt File
Can i install and use Apps like Netflix, Amazon Prime,.. and watch content in HD again with this ROM ?
As this is a Problem with the Widevine Services and this Device itself this Rom doesn´t change anything on that. If you want to use the Netflix App for example you still have to use the liboemdecrypt modul on Magisk and its SD only
Thanks goes to:
@Steel01 and the whole LOS Team for doing all the hard work to keep this Device alive
@Artemka2008 for figuring out the OMX fix
@Triodexe for uploading his work on his Github so i could figure out how to edit the vendor files
@john_matrix for teaching me how to set up my build enviroment and being really helpful when i´m stuck with errors
Requirements:
Bootloader Unlock
Bootloader Version 4.00.2016.04
Custom Recovery installed (use Version 9.5.0_9-0 of TWRP or Lineage Recovery)
Instructions:
Download the latest build and gapps if needed (8.1 / arm / pico)
Reboot to recovery and wipe your existing Rom
Flash the latest build and gapps
Reboot
Downloads:
Builds : https://www.androidfilehost.com/?w=files&flid=325335
Root addon : https://download.lineageos.org/extras
Google Apps : http://opengapps.org/
Firmware Update : N/Stock 5.0
Whats working now:
HW Acceleration
Snap Camera
Whats still not working:
Nvidia Games App (Deleted)
Console Mode UI (Deleted but HDMI still working fine)
Encryption (will lead to a Bootloop if tried)
Screen Mirroring ( In App Cast like on the Youtube App still working fine)
Contributors:
@Steel01
Source Code: https://github.com/LineageOS
@Scavenger87
Device: https://github.com/Scavenger-87/android_nvidia_device_shield-common
https://github.com/Scavenger-87/android_device_nvidia_shieldtablet
Vendor: https://github.com/Scavenger-87/android_vendor_nvidia_shield
ROM OS Version: 8.1 Oreo
ROM Kernel: Linux 3.10.96+
Version Information:
Status: userdebug
SELinux: Enforcing
Security Patch: 5.10.2021
Build Signature: Own Release Key
Created 14.05.2021
Last Updated 18.10.2021
Scavenger87 said:
View attachment 5308899
Disclaimer:
Not responsible for any injuries you do to yourself or your device being damaged caused by this ROM.
Big thanks goes to @Steel01 for all the hard work and the Sources.
LineageOS is a free, community built, aftermarket firmware distribution of Android, 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.
Hi Everyone
After some months of learning how to build my own Roms and how to edit the proprietary files of this Device i was able to build my first edited version of LineageOS 15.1 with HW Acceleration and the Camera working.
Its a slim an snappy Rom for everyone that´s looking for a monthly updated Android 8.1 Rom to keep this unique Device alive.
This first release is really basic because i deleted everything that doesn't work right.
My plans for this Rom are to keep it updated in case of Security Patches and add some Features here and there as i still learn how this Device and Android is working in general.
Also the official release of LineageOS 16 will end the development of this Rom for the reason i don't want to rival the official contributors of this Device.
Little FAQ to this Rom:
Do i need to Wipe my existing Rom even its LineageOS 15.1 based ?
Yes because i use my own Release Keys for this Rom you need to Wipe your existing one.
Is this Rom compatible with every Shield Tablet ?
Yes this Rom is working with every Shield Tablet
I have a Shield LTE Version and after flashing this Rom i cant connect my device for Data Transfer with my computer anymore.
For some Reason i still didnt found out on LineageOS 15.1 there is no Drop Down Menu for this Device to change the type of connection.
To change it go to Settings > Connected Devices > USB
I found a Bug with this Rom i didnt had on any Rom before what should i do before i post it here ?
Before you post any Bugs and Errors here make sure you installed this Rom correct as i told with a full wipe in your recovery first and if there are modifications installed like Magisk
Moduls or Xposed or you changed this Rom in any way, you should reinstall it fresh first to take a look if the issue still occurs.
If yes post a detailed report of the Error with a Logcat.txt File
Can i install and use Apps like Netflix, Amazon Prime,.. and watch content in HD again with this ROM ?
As this is a Problem with the Widevine Services and this Device itself this Rom doesn´t change anything on that. If you want to use the Netflix App for example you still have to use the liboemdecrypt modul on Magisk and its SD only
Thanks goes to:
@Steel01 and the whole LOS Team for doing all the hard work to keep this Device alive
@Artemka2008 for figuring out the OMX fix
@Triodexe for uploading his work on his Github so i could figure out how to edit the vendor files
@john_matrix for teaching me how to set up my build enviroment and being really helpful when i´m stuck with errors
Requirements:
Bootloader Unlock
Bootloader Version 4.00.2016.04
Custom Recovery installed (use Version 9.5.0_9-0 of TWRP or Lineage Recovery)
Instructions:
Download the latest build and gapps if needed (8.1 / arm / pico)
Reboot to recovery and wipe your existing Rom
Flash the latest build and gapps
Reboot
Downloads:
Builds : https://www.androidfilehost.com/?w=files&flid=325335
Root addon : https://download.lineageos.org/extras
Google Apps : http://opengapps.org/
Firmware Update : N/Stock 5.0
Whats working now:
HW Acceleration
Snap Camera
Whats still not working:
Nvidia Games App (Deleted)
Console Mode UI (Deleted but HDMI still working fine)
Encryption (will lead to a Bootloop if tried)
Screen Mirroring ( In App Cast like on the Youtube App still working fine)
Contributors:
@Steel01
Source Code: https://github.com/LineageOS
@Scavenger87
Device: https://github.com/Scavenger-87/android_device_nvidia
Vendor: https://github.com/Scavenger-87/android_vendor_nvidia_shield
ROM OS Version: 8.1 Oreo
ROM Kernel: Linux 3.10.96+
Version Information:
Status: userdebug
SELinux: Enforcing
Security Patch: 5.5.2021
Build Signature: Own Release Key
Created 14.05.2021
Last Updated 14.05.2021
Click to expand...
Click to collapse
Thank You for breathing new life into this great little tablet!
Thanks for keep this device alive!
Any ideas why clash of clans will not work on this ROM? Installed COC from Amazon App Store right after flashing this ROM and the game closes with no error right after it fully loads at the loading screen. Tried Lineage OS 16.0 and had the same exact issue using the google play store version with pico opengapps. I just want to use a smooth running ROM and play clash also QQ. Clash ran like trash on the stock 7.0 rom even after doing everything possible to make the tablet smoother.
Thank you very much and nice job Scavenger for keeping our tablet up and running!
Tried this ROM and was very happy to finally see one above Nougat on my shield tablet k1 that has 1080p 60 FPS videos playing smooth with no artifacts and doesn't crash. Also super smooth. Very nice, congratulations and many thanks.
However after I rebooted to recovery and flashes magisk it got stuck forever on Nvidia logo
Wiped everything again, reinstalled (ROM and gapps) and it booted without magisk. Tried flashing magisk again, same problem
I never had this issue with magisk before on this tablet (and I've tried several ROMs).
Anyone else faced this issue? Any advice?
@ogremalfeitor How do you tried to install Magisk? Refer https://topjohnwu.github.io/Magisk/install.html
What would be the right way to install it?
@Scavenger87 Besides your LOS build we find also a recovery.img at androidfilehost.com - do we have to patch this one with the Magisk app? I never tried the LOS recovery before.
marrol said:
@ogremalfeitor How do you tried to install Magisk? Refer https://topjohnwu.github.io/Magisk/install.html
What would be the right way to install it?
@Scavenger87 Besides your LOS build we find also a recovery.img at androidfilehost.com - do we have to patch this one with the Magisk app? I never tried the LOS recovery before.
Click to expand...
Click to collapse
I tried many ways.
Usually with the latest magisk versions I rename the APK to ZIP and install it via TWRP (you can't do that with normal APKs but magisk one is special). This method has worked for me with other ROMs. From then on, when there are Magisk updates, I use the magisk manager app.
Meanwhile I tried dumping the boot partition from TWRP and use the manager to patch it, then flash it via fastboot. Same problem. If I then flash the unmodified boot image back, the system boots fine.
I'm now trying everything again, with the 3.5.0_9-0 version of TWRP (I had 3.4.0 installed). Also I was using aroma opengapps (costumizing what I want), I'm now going to try with pico as said in the first post. Will post back results.
ogremalfeitor said:
I tried many ways.
Usually with the latest magisk versions I rename the APK to ZIP and install it via TWRP (you can't do that with normal APKs but magisk one is special). This method has worked for me with other ROMs. From then on, when there are Magisk updates, I use the magisk manager app.
Meanwhile I tried dumping the boot partition from TWRP and use the manager to patch it, then flash it via fastboot. Same problem. If I then flash the unmodified boot image back, the system boots fine.
I'm now trying everything again, with the 3.5.0_9-0 version of TWRP (I had 3.4.0 installed). Also I was using aroma opengapps (costumizing what I want), I'm now going to try with pico as said in the first post. Will post back results.
Click to expand...
Click to collapse
No luck, same problem
Root addon from lineage os works, but fails safety net check pretty badly and does not support modules like Magisk...
@Scavenger87 do you have any advice to get Magisk working with this ROM? Are there any place logs are generated when the tablet is booting on the nvidia logo where mine is getting stuck? Thanks in advance.
Hello,
I have a question.
What should i Do with
Firmware Update : N/Stock 5.0
I have installed the Rom and the Gapps. And IT runs, on My K1
summerstyle said:
Hello,
I have a question.
What should i Do with
Firmware Update : N/Stock 5.0
I have installed the Rom and the Gapps. And IT runs, on My K1
Click to expand...
Click to collapse
It's just there for people that might have an outdated stock firmware. If it worked for you without it, you don't need it. Someone correct me if I'm wrong
ogremalfeitor said:
No luck, same problem
Root addon from lineage os works, but fails safety net check pretty badly and does not support modules like Magisk...
@Scavenger87 do you have any advice to get Magisk working with this ROM? Are there any place logs are generated when the tablet is booting on the nvidia logo where mine is getting stuck? Thanks in advance.
Click to expand...
Click to collapse
Maybe we have to patch boot.img from NVidia Stock Recovery 5.2 and flash this one?
ogremalfeitor said:
It's just there for people that might have an outdated stock firmware. If it worked for you without it, you don't need it. Someone correct me if I'm wrong
Click to expand...
Click to collapse
This is a separate blob update. What for do we need this?
marrol said:
Maybe we have to patch boot.img from NVidia Stock Firmware 5.2 and flash this one?
Click to expand...
Click to collapse
That's not it. The boot.img is unique to every ROM. It contains the kernel and the initial ramdisk (initrd, if you're interested in details search for that and there are a lot of interesting articles explaining the boot process of Linux and derivates like Android).
I know magisk modifies the initrd to sort of "inject" itself during that early boot process, but it doesn't make the system hang with other ROMs, hence before assuming it's a bug in magisk I'd like to know if anyone has any idea or if the ROM is missing anything that could cause this?
marrol said:
This is a separate blob update. What for do we need this?
Click to expand...
Click to collapse
I believe it has to do with outdated bootloaders, which will be the case for people who never used recent stock firmwares, and it's there should you have problems (but don't confuse bootloader with boot partition or boot.img that I mentioned in another post). I think the script in the Zip detects it when you flash in twrp and gives an error if necessary but please correct me if I'm wrong.
I have try to installed the Firmware Update : N/Stock 5.0 in TRWP. It doesnt work. A Error Shows and it cant installed.
Well meanwhile I went on and started using this ROM without magisk. Started to have crashes here and there not long after, like most (if not all) ROMs for my tablet above android 7... until the video started to get corrupted in YouTube Vanced too which is a deal breaker for me.
Guess this is not the one ROM to solve my problems with this tablet after all, but still it's a great effort. Hope others enjoy it and thanks to the dev for sharing.
Hi everyone after a little vacation and some testing out of your reported issues this is what i found out so far:
Hworangg said:
Any ideas why clash of clans will not work on this ROM? Installed COC from Amazon App Store right after flashing this ROM and the game closes with no error right after it fully loads at the loading screen. Tried Lineage OS 16.0 and had the same exact issue using the google play store version with pico opengapps. I just want to use a smooth running ROM and play clash also QQ. Clash ran like trash on the stock 7.0 rom even after doing everything possible to make the tablet smoother.
Click to expand...
Click to collapse
I installed that game on a Tablet with LOS 14.1 and LOS 15.1 and in both cases the Game crashes because it run out of memory. I did a quick test on my Rom with adding ro.config.low_ram=true to the build.prop which activate the Go Version of Android and decreased the usage of Ram this way .
The Game runs but it started to get really sluggish after around 30 seconds.
It seems this Game just needs more than the 2GB Ram this device can offer.
ogremalfeitor said:
Tried this ROM and was very happy to finally see one above Nougat on my shield tablet k1 that has 1080p 60 FPS videos playing smooth with no artifacts and doesn't crash. Also super smooth. Very nice, congratulations and many thanks.
However after I rebooted to recovery and flashes magisk it got stuck forever on Nvidia logo
Wiped everything again, reinstalled (ROM and gapps) and it booted without magisk. Tried flashing magisk again, same problem
I never had this issue with magisk before on this tablet (and I've tried several ROMs).
Anyone else faced this issue? Any advice?
Click to expand...
Click to collapse
After trying to flash many Versions of Magisk starting by 21.4 over 22.0 and the actual 23.0 via the TWRP Recovery Version (9.5.0_9-0) i mentioned in the Start Thread and trying to flash it with the Magisk App i also wasnt able to install Sucessfully Magisk without running into a Bootlop which is really a Bummer.
I dont know why this happends and i check my Kernel Logs i pulled with TWRP but for the moment we have to use the SU Addon by LOS.
Maybe it has something to do with that my build is signed with a personal key i will check that out.
summerstyle said:
I have try to installed the Firmware Update : N/Stock 5.0 in TRWP. It doesnt work. A Error Shows and it cant installed.
Click to expand...
Click to collapse
Thats just the Blob File that needs to be flashed when the Bootloader isnt updated to the latest Version (4.00.2016.04)
ogremalfeitor said:
Well meanwhile I went on and started using this ROM without magisk. Started to have crashes here and there not long after, like most (if not all) ROMs for my tablet above android 7... until the video started to get corrupted in YouTube Vanced too which is a deal breaker for me.
Guess this is not the one ROM to solve my problems with this tablet after all, but still it's a great effort. Hope others enjoy it and thanks to the dev for sharing.
Click to expand...
Click to collapse
On some rare ocassions you get those same green artefacts on videos like you get with the LOS 16.0 Rom but at least in my case it happends once a week or so and it seems it have something to do with memory managment again.
My guess is that the tegra drivers arent working really well with Android Versions above Nougat (7.0) and this leads to a memory leak but like i said its just a guess by me maybe @Steel01 can say more about that.
I try to optimize the memory management in the future builds if possible.
Hi Everybody
I think its time to give you a little update of my work on this build
After i got a good example of the problems with the ram management of this device i was looking for a solution last few days and i began testing with the Android Go Settings as i mentioned in the last Thread.
With that settings i was able to start that Game mentioned by @Hworangg and i even was able to play it a bit as you can see on one of the added Screenshots below. But you could also see this Game is a real RAM Hog with needing up to 484MB at the last session i played but it is kinda playable you just have to stay in that Game and turn off every notification as it might crashes otherwise. Speaking of crashes while the GO Settings really helping on reduce the usage of Ram by the System itself and let the device take more Memory Pressure it also leads to freezes where you often have to Hard Reset the Tablet because it seems to not close the Main App when its in a Out of Memory Situation. This is something i have to invest more time and research even after i played a lot with the Dalvik VM Settings.
I also found out that my Personal Key Signature is the reason that the install of Magisk is leading to a Bootloop. Here i also have to figure out why this is happen and if its even possible to install Magisk on a Signed Custom Rom as you change out the BOOT.img on this Device to achieve that and it seems the Magisk installer isnt able to resign the File with my Key.
TLDR:
I was able to set up my Build to use the optimized Android GO Settings to withstand more Memory Pressure so that Games like COC and heavy Browsing Sessions with lots of Tabs and Sites with a lot of Pictures doesn't crash that soon but it lead in both cases to a freeze of the whole Device.
The Magisk installer does not work when i sign my build with my own key.
For this Reason i decided to release a another Build for you to test with this Settings as a Nightly Release before i release my next Regular Build when the next Security Patch is out
You find it here : Nightly Build and i´m curious about your opinion.
Flashed the nightly onto a freshly wiped K1 along with opengapps and Magisk 23 using patched boot, no problems there. Video playback - Netflix played about as well as it could with level 3 widevine, with Jellyfin no obvious visual problems streaming 1080p over lan. Got hard freezes when running memory heavy apps (firefox, manga reader, 3d unity games) but it was expected.
Ended up downgrading back to factory stock Lollipop as the memory management is best there, even better than stock Nougat. But will keep an eye on your builds because the K1 could still be a great little tablet if the memory issues in newer versions of Android was fixed. Thank you for your hard work
ѕαмαя νιѕρυтє
ALL CREDIT TO SAMARV-121
Original on samarv121.cf/lineageos-19.0-m20lte/
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.
Features
Enforcing SELinux
AES-256-XTS File Based Encryption (FBE)
Passes SafetyNet out-of-the-box
Signature spoofing support (for microG)
Google Sans as a default font
Monet theme engine customizer (Display settings)
Fast charging disabler (Battery settings)
High touch sensitivity Mode (Display settings)
Swipe fingerprint for notification (Settings->System->Gestures)
Ambient display gestures (Settings->Display->Lockscreen->Ambient Display)
Known issues
IMS (VoLTE,ViLTE,VoWiFi)
Wide angle camera
Reporting Bugs
Don’t report bugs if you have any custom kernel or module installed
Create new issue here or Report it here.
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)
Changelog2022-01-09
January ASB (android-12.0.0_r26)
Implemented almost every LineageOS feature
Added seperate built-in gapps build
Replaced AOSP Camera app with GrapheneOS Camera
Passes SafetyNet out-of-the-box
Unshipped Pixel Launcher and GBoard from Vanilla build
Added option to disable Fast charging (Battery settings)
Added option to enable High touch sensitivity Mode (Display settings)
Added LiveDisplay (Display settings)
Added setting to manually customize monet theme engine (Display settings)
Unlimited Google Photos storage
2021-12-102021-11-20
ScreenshotsExpand
Device info
Kernel - 4.4.x
Chipset - Exynos7904
Telegram channel
Click here
Support group
Click here
InstructionsIf you are coming from stock ROM or any custom ROM
Boot into custom recovery
Format data
Flash latest build
Flash gapps package (optional)
Reboot your device once the installation is done
If you are already on LineageOS-19.0
Boot into custom recovery
Flash latest build
Reboot your device once the installation is done
FAQsI’m getting bootloop
Don’t flash any additional package if you are flashing
FORMAT data (not WIPE)
TWRP isn’t booting after flashing this rom
Yeah, It’s not supported. just reboot your device. Lineage Recovery will automatically get installed.
MTP not working
Disable USB debugging from developer options if you have it enabled.
Safetynet is failing after rooting the device
If you are on Magisk 23.0:
Enable MagiskHide from Magisk Manager app
If you are on newer version (Zygisk):
Enable “Zygisk” option from the Magisk Manager app
Reboot your device
Enable “Enforce DenyList” option
Go in “Configure DenyList”
Enable “Show system apps” option then search ‘Google Play Services’ and tap on it (but NOT on the tick box!) to expand activities
Enable “com.google.android.gms” and “com.google.android.gms.unstable”
Downloads
LineageOS-19.0(Vanilla) - Download
LineageOS-19.0(Gapps) - Download
Lineage Recovery - Download
Hi. There's a new build almost everyday. Where can I find the change log?
Could IMS and Wide Angle Camera work on future builds or is it next to impossible?
Hi ..
I m looking for a custom Lineage os for my Samsung m20 .UI : core 2 . M20 - DS20F , can you help me with this .
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:
Unlock bootloader
Boot into download mode
Flash recovery using heimdall or odin
Boot into recovery right as it finishes flashing
Flash ROM using adb sideload path_to_ROM.zip command
Optionally flash GAPPS the same way you flashed ROM
Format data in recovery
Reboot to system.
Downloads:
RECOVERY
ROM
GAPPS
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
Credits
Doomer231
A2L5E0X1
DeHuMaNiZeD
Linux4
Device tree and kernel source code:
R8S-OSS
Issues:
voLTE[wont fix, unless any samsung gets voLTE fixed]
fingerprint scanner might not work
overlays might need some tweaking
no encryption
permissive SELinux
Steps I followed from @Gully.Moy that worked perfectly:
Unlocked bootloader as per guides no problem
Downloaded latest stock firmware from Frija and extract
Copy the AP_xxxxxxxxxxx.tar.md5 file to phone storage
Copy Magisk manager on your phone https://github.com/topjohnwu/Magisk/releases/tag/v25.2
Open Magisk manager, select 'install' next to Magisk, select the .tar.md5 file and patch it
Copy newly created magisk.tar file from phone download folder to computer
Flash via Odin 3.13.3 with standard BL CP and CSC from Frija download, but the magisk .tar file in AP slot.
Boot into android and reenable USB debugging (not sure if necessary).
(Recovery mode combination is volume up + side button with USB plugged in)
I am now in the first boot of the ROM that I copied to the internal storage and flashed with TWRP (as my device is not recogised in fastboot and doesn´t let me sideload via adb it closes) but seems to be in an endless startup loop and it failed to install the gapps also when I tried to, the provided recovery cannot be flashed with Odin @Doomvrr thank you.
BraskOviedo said:
Steps I followed from @Gully.Moy that worked perfectly:
Unlocked bootloader as per guides no problem
Downloaded latest stock firmware from Frija and extract
Copy the AP_xxxxxxxxxxx.tar.md5 file to phone storage
Copy Magisk manager on your phone https://github.com/topjohnwu/Magisk/releases/tag/v25.2
Open Magisk manager, select 'install' next to Magisk, select the .tar.md5 file and patch it
Copy newly created magisk.tar file from phone download folder to computer
Flash via Odin 3.13.3 with standard BL CP and CSC from Frija download, but the magisk .tar file in AP slot.
Boot into android and reenable USB debugging (not sure if necessary).
(Recovery mode combination is volume up + side button with USB plugged in)
I am now in the first boot of the ROM that I copied to the internal storage and flashed with TWRP (as my device is not recogised in fastboot and doesn´t let me sideload via adb it closes) but seems to be in an endless startup loop and it failed to install the gapps also when I tried to, the provided recovery cannot be flashed with Odin @Doomvrr thank you.
Click to expand...
Click to collapse
I need to update the ROM to boot on latest firmware, because samsung updated bootloader. So for now it won't boot unless you're on august firmware, don't try to downgrade firmware. Just wait.
Doomvrr said:
I need to update the ROM to boot on latest firmware, because samsung updated bootloader. So for now it won't boot unless you're on august firmware, don't try to downgrade firmware. Just wait.
Click to expand...
Click to collapse
Thank you for the ROM and the quick answer, if I can help out with something please let me know, thank you.
Doomvrr said:
I need to update the ROM to boot on latest firmware, because samsung updated bootloader. So for now it won't boot unless you're on august firmware, don't try to downgrade firmware. Just wait.
Click to expand...
Click to collapse
Forgot to ask, is there an ETA? Is it LineageOS 20? Thank you
Doomvrr said:
I need to update the ROM to boot on latest firmware, because samsung updated bootloader. So for now it won't boot unless you're on august firmware, don't try to downgrade firmware. Just wait.
Click to expand...
Click to collapse
It´s the October 2022 patch
Doomvrr said:
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
Click to expand...
Click to collapse
What is the context of the above statments, I ask because -
One of the primary reason for running a custom ROM is for rooting, and the primary reason for rooting for a LOT of users is the ability to run Magisk and EdXposed/Riru.
This one is exspecially confusing, the vast majority of users flash custom ROMs with TWRP. Does the recovery that needs to be flashed with this ROM as comprehensive as TWRP..?
b1k3rdude said:
What is the context of the above statments, I ask because -
One of the primary reason for running a custom ROM is for rooting, and the primary reason for rooting for a LOT of users is the ability to run Magisk and EdXposed/Riru.
This one is exspecially confusing, the vast majority of users flash custom ROMs with TWRP. Does the recovery that needs to be flashed with this ROM as comprehensive as TWRP..?
Click to expand...
Click to collapse
Agreed.
b1k3rdude said:
What is the context of the above statments, I ask because -
One of the primary reason for running a custom ROM is for rooting, and the primary reason for rooting for a LOT of users is the ability to run Magisk and EdXposed/Riru.
This one is exspecially confusing, the vast majority of users flash custom ROMs with TWRP. Does the recovery that needs to be flashed with this ROM as comprehensive as TWRP..?
Click to expand...
Click to collapse
Xposed modules may cause stability issues on the system due to their nature. Debugging the issue becomes a hard task because there can be a ton of reasons as to why it happens, and you'll be most certainly reaching out to the ROM maintainer to help you fix something not even related to his work.
I can't say for sure but I guess it's because TWRP has had some problems to keep up with the changes made to Android on recent years due to the maintainers' private life and the fact that some changes were groundbreaking, like moving the recovery to the boot partition instead of having its dedicated partition, as it used to be until a couple of Android versions.
TL;DR: maintainers post these statements so users can discard possible known causes of issues beforehand, and to avoid complaints about pieces of work that aren't their responsibility at all.
All-In-One said:
Xposed modules may cause stability issues on the system due to their nature. Debugging the issue becomes a hard task because there can be a ton of reasons as to why it happens, and you'll be most certainly reaching out to the ROM maintainer to help you fix something not even related to his work.
I can't say for sure but I guess it's because TWRP has had some problems to keep up with the changes made to Android on recent years due to the maintainers' private life and the fact that some changes were groundbreaking, like moving the recovery to the boot partition instead of having its dedicated partition, as it used to be until a couple of Android versions.
TL;DR: maintainers post these statements so users can discard possible known causes of issues beforehand, and to avoid complaints about pieces of work that aren't their responsibility at all.
Click to expand...
Click to collapse
Imho and experience this nearly always down to the Xposed modules not xposed itself. I have been using xposed since my Galaxy S and its been reliable and solid enough that after 10 Samsung devices later (S, S2, S4, S5, Note5, S6, S7, S7edge, Note9, S20FE) I will always install it. And the Xposed modules I run ar XpirvacyLua, Firefds kit [Q], GravityBox [Q] which are then Managed by EdXposed. I tend not to update the modules unless there is a specific issue that an update will fix.
Nope, check the twrp thread i the section we are upto 3.7.x which supports Android 12 (and should support 13 due to it being an incrmental update on 12).
Thats a fair comment.
Hello, is there a possibility to release this also for snapdragon?