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"
}
Other roms not giving you the performance or battery life you want? Try SAMSTOCK rom. It's so stock that its stock. Some rom makers like to customize their rom by branding it with their name, and I have nothing against that.
This rom however has none of that.
KNOX WARRANTY VOID: 1 (0X1)
Features:
-Untouched. Completely stock out of the latest zip from sammobile.
-December Security Patch
-Multi CSC just like stock firmware
-Safetynet Passed
-Private Mode working
-System Status = Official (In DL mode and in about phone)
-Can check for latest updates from samsung
-Play Store > Settings > Device Certification > Certified (MOST ROMS FAIL THIS)
-No branding by me at all
-No changes to any apk
-SE for Android Status: ENFORCING
-Samsung Health working fully
-Latest ROOT by topjohnwu
Whats customized
-this line from build.prop : "ro.config.tima=0"
But why DEV? You said stock.
To make Samsung Health work again.
NO OTHER FILE IN THIS ROM HAS BEEN TOUCHED ABSOLUTE STOCK!!
-Removed Samsung Pass (Does not work on any rom unless official not rooted)
-Removed Samsung Pay (Does not work on any rom custom or stock after knox trip)
Debloated apps include:
All available to reinstall from aroma.
-Facebook
-Instagram
-Onenote
-Peel Smart remote
-Skype
-WhatsApp
-Microsoft Excel
-Microsoft PowerPoint
-Microsoft Word
-Microsoft OneDrive
-Hancom Office
-Samsung Health
-S Voice (Honestly don't torture yourself)
-Yahoo Edge Panels (EDGE ONLY)
Requirements:
-Device SM-G920F/W8/I, SM-G925F/W8/I
-Flash latest firmware from Samsung
-Must be latest Bootloader and modem
-If you come to me with bricked devices I'll honestly just laugh. It says what you need right above this.
Installation:
-Backup your garbage
-Power off
-Charge to 80% or higher
-Boot into TWRP
-Advanced wipe ALL partitions except for /usbstorage
-Install Zip
-Select the garbage you want
-Let it install
-Reboot
FAQS
Q: I see a new update can you update the rom?
A: No those are generally region specific updates. Not major patches. Just carrier fixes. If I did it I would sit here for days.
Q: I checked for and downloaded a new update. I reboots into recovery and then nothing. What happened?
A: You cannot install OTA updates because they require the stock recovery to be installed. TLDR: Ignore the update.
Q: When are you updating this rom?
A: When samsung releases the next MAJOR/MONTHLY security patch update.
Q: When are you adding [Insert feature name here]?
A: Never. Its stock what ever stock comes with is what you get. There are other roms available for that.
Q: My phone is taking too long to boot. What should I do?
A: Did you follow all instructions? First boot takes 10-15 minutes.
Q: Fingerprint reader doesn't work. What do I do?
A: Device needs to be restarted.
Q: Can you remove/debloat [INSERT APP NAME HERE] and put it in aroma?
A: Sure when there's a new patch from Samsung I will.
Q: Does this work with my device?
A: If its a G920F/W8/I OR 925F/W8/I. Yes. Yes it does. If not. Get out.
Q: OK dev my garbage works like you said. Now what?
A: Let me know how you like it. Drop a like and enjoy. :laugh: :good:
Q: Why isn't there just one zip for all devices?
A: Because these aren't custom roms. They are stock. If i did one zip for all devices zip size would be 4GB+
Q: Will this work with my carrier?
A: Please click below to see a full list of supported CSC's.
SM-G920/5W8
-BMC (Bell Mobility)
-BWA (SaskTel)
-ESK (East Link)
-FMC (Fido Mobile)
-GLW (Freedom Mobile)
-KDO (Koodo)
-MTA (Manitoba Telecom)
-RWC (Rogers Wireless)
-TLS (Telus)
-VMC (Virgin Canada)
-VTR (VideoTron)
-XAC (Unlocaked Canada)
SM-G920F
-BTU (United Kingdom)
-CPW (United Kingdom)
-DBT (Germany)
-ITV (Italy)
-KOR (Korea)
-NEE (Finland)
-XEF (France)
-XEO (Poland)
SM-G925F
-BTU (United Kingdom)
-CPW (United Kingdom)
-DBT (Germany)
-ITV (Italy)
-KOR (Korea)
-NEE (Finland)
-XEF (France)
-XEO (Poland)
-XSG (UAE)
SM-920I
-BNG (Bangladesh)
-INS (India)
-INU (India)
-NPL (Nepal)
-SLK (Sri Lanka)
SM-G925I
-BNG (Bangladesh)
-INS (India)
-INU (India)
-NPL (Nepal)
-SLK (Sri Lanka)
Thanks to:
-amarullz for Aroma
-topjohnwu for Magisk 14 Root
-Samsung for the stock rom
-Carriers for doing nothing
DROP THESE GUYS A LIKE TOO THEY DESERVE IT.
For Developers:
-If you want to use this as a base for your rom please PM me and i'll reply asap
-If you want to help add features to aroma them PM me so we can talk business
Samsung Official Security Bulliten:
This is the security patch status. Here you'll be able to see the vulnerabilities that were fixed by Samsung and google.
JULY:
Code:
SMR-JUL-2017
Samsung Mobile is releasing a maintenance release for major flagship models as part of monthly Security Maintenance Release (SMR) process.
This SMR package includes patches from Google and Samsung.
Google patches include patches up to Android Security Bulletin - July 2017 package.
The Bulletin (July 2017) contains the following CVE items:
Critical: CVE-2017-0564, CVE-2016-9794, CVE-2015-7555, CVE-2017-0540, CVE-2017-0673, CVE-2017-0674, CVE-2017-0675, CVE-2017-0676, CVE-2017-0677, CVE-2017-0678, CVE-2017-0679, CVE-2017-0680, CVE-2017-0681, CVE-2017-0469
High: CVE-2017-6423, CVE-2015-9004, CVE-2014-9940, CVE-2017-0648, CVE-2017-6074, CVE-2017-8253, CVE-2017-8273, CVE-2014-9979, CVE-2015-8595, CVE-2017-0664, CVE-2017-0665, CVE-2017-0666, CVE-2017-0667, CVE-2017-0669, CVE-2017-0670, CVE-2017-0671, CVE-2016-2109, CVE-2017-0672, CVE-2017-0684, CVE-2017-0685, CVE-2017-0686, CVE-2017-0688, CVE-2017-0689, CVE-2017-0690, CVE-2017-0691, CVE-2017-0692, CVE-2017-0693, CVE-2017-0694, CVE-2017-0695, CVE-2017-0696, CVE-2017-0697, CVE-2017-0700, CVE-2017-0701, CVE-2017-0702, CVE-2017-0703, CVE-2017-0642
Moderate: CVE-2017-7368, CVE-2017-7364, CVE-2017-8237, CVE-2015-5707, CVE-2016-5863, CVE-2017-8246, CVE-2017-8256, CVE-2017-8257, CVE-2016-3924, CVE-2017-0493, CVE-2015-7995, CVE-2017-3544, CVE-2017-0698, CVE-2017-0699
Low: CVE-2017-8241
※ Please see Android Security Bulletin for detailed information on Google patches.
Along with Google patches, Samsung Mobile provides 16 Samsung Vulnerabilities and Exposures (SVE) items described below, in order to improve our customer's confidence on security of Samsung Mobile devices.
Some of the SVE items may not be included in this package, in case these items were already included in a previous maintenance release.
SVE-2017-8290: Crash via sending broadcast (AdaptiveDisplayColorService)
Severity: Low
Affected versions: KK(4.4), L(5.0/5.1), M(6.0), N(7.x)
Reported on: February 14, 2017
Disclosure status: Privately disclosed.
Lack of appropriate exception handling for Intents including Serializable instance allows attackers crash several system processes resulting in a possible DoS attack.
The patch prevents system crashes by handling unexpected exceptions.
SVE-2017-8888: Buffer overflow in tlc_server
Severity: Medium
Affected versions: M(6.0), N(7.x)
Reported on: April 11, 2017
Disclosure status: Privately disclosed.
There is a potential buffer overflow vulnerability due to not confirming if the size of source data is smaller than the destination buffer.
The patch removes the problematic code.
SVE-2017-8973: Buffer overflow in process_cipher_tdea
Severity: Low
Affected versions: M(6.0), N(7.x)
Reported on: April 11, 2017
Disclosure status: Privately disclosed.
There is a potential buffer overflow vulnerability due to not verifying input and output parameters’ sizes.
The fix avoids a buffer overflow by checking if the size of output data is the same as input data.
SVE-2017-9109: Unintended memory is disclosed in rkp log
Severity: Medium
Affected versions: M(6.0), N(7.x)
Reported on: May 4, 2017
Disclosure status: Privately disclosed.
The vulnerability allows reading data outside of rkp log buffer boundary due to not checking the boundary.
The applied patch avoids an illegal access to memory by checking the boundary.
SVE-2017-9122, SVE-2017-9123, SVE-2017-9124, and SVE-2017-9126: Crash system server via sending broadcast
Severity: Low
Affected versions: N(7.x)
Reported on: May 10, 2017
Disclosure status: Privately disclosed.
Lack of appropriate exception handling for some Intents which cause NullPointerException allows attackers crash a system process resulting in a possible DoS attack.
The patch protects the receiver by changing to protected intent.
Some SVE items included in the Samsung Android Security Update cannot be disclosed at this time.
Acknowledgements
We truely appreciate the following researchers for helping Samsung to improve the security of our products.
- Ryan Johnson and Angelos Stavrou of Kryptowire : SVE-2017-8290, SVE-2017-9122, SVE-2017-9123, SVE-2017-9124, SVE-2017-9126
- Daniel Komaromy : SVE-2017-8888, SVE-2017-8973
- David Berard : SVE-2017-9109
AUGUST:
Code:
SMR-AUG-2017
Samsung Mobile is releasing a maintenance release for major flagship models as part of monthly Security Maintenance Release (SMR) process.
This SMR package includes patches from Google and Samsung.
Google patches include patches up to Android Security Bulletin - August 2017 package.
The Bulletin (August 2017) contains the following CVE items:
Critical: CVE-2017-0714, CVE-2017-0715, CVE-2017-0716, CVE-2017-0718, CVE-2017-0719, CVE-2017-0720, CVE-2017-0721, CVE-2017-0722, CVE-2017-0723, CVE-2017-0745, CVE-2017-0407, CVE-2017-9417
High: CVE-2017-0576, CVE-2016-10286, CVE-2016-10244, CVE-2017-0713, CVE-2017-0724, CVE-2017-0725, CVE-2017-0726, CVE-2017-0727, CVE-2017-0728, CVE-2017-0729, CVE-2017-0730, CVE-2017-0731, CVE-2017-0732, CVE-2017-0733, CVE-2017-0734, CVE-2017-0735, CVE-2017-0736, CVE-2017-0687, CVE-2017-0737
Moderate: CVE-2017-0583, CVE-2016-5346, CVE-2017-6425, CVE-2016-10236, CVE-2017-6426, CVE-2017-7370, CVE-2017-7372, CVE-2017-7373, CVE-2017-0451, CVE-2017-7308, CVE-2017-8264, CVE-2017-8266, CVE-2017-8268, CVE-2017-8258, CVE-2017-0560, CVE-2017-0712, CVE-2017-0738, CVE-2017-0739
Low: CVE-2017-0452
※ Please see Android Security Bulletin for detailed information on Google patches.
Along with Google patches, Samsung Mobile provides 12 Samsung Vulnerabilities and Exposures (SVE) items described below, in order to improve our customer's confidence on security of Samsung Mobile devices.
Some of the SVE items may not be included in this package, in case these items were already included in a previous maintenance release.
SVE-2017-8889, SVE-2017-8891, and SVE-2017-8892: Stack overflow in trustlet
Severity: Low
Affected versions: M(6.0), N(7.x)
Reported on: April 11, 2017
Disclosure status: Privately disclosed.
Lack of boundary checking of a buffer in trustlet can lead to memory corruption.
The applied patch adds boundary checking.
SVE-2017-8890: Over-read in trustlet
Severity: Low
Affected versions: M(6.0), N(7.x)
Reported on: April 11, 2017
Disclosure status: Privately disclosed.
Lack of boundary checking of a buffer in trustlet can lead to unauthorized access to data outside of boundary.
The applied patch adds boundary checking.
SVE-2017-8893: Arbitrary write in trustlet
Severity: Low
Affected versions: M(6.0), N(7.x)
Reported on: April 11, 2017
Disclosure status: Privately disclosed.
Assuming privilege escalation is achieved, lack of boundary checking in a trustlet can lead to arbitrary write.
The applied patch adds boundary checking.
SVE-2017-9008 and SVE-2017-9009: Integer overflow in trustlet
Severity: Low
Affected versions: N(7.x)
Reported on: April 24, 2017
Disclosure status: Privately disclosed.
Lack of boundary checking of a buffer in trustlet can lead to memory corruption.
The patch removed the part of code related to Integer overflow.
SVE-2017-9383: Abnormal screen touch via malformed input with multiwindow_facade API
Severity: Low
Affected versions: M(6.0)
Reported on: May 31, 2017
Disclosure status: Privately disclosed.
Lack of appropriate validation check for display ID can halt system due to NullPointException problem caused by mismatch to a non-existing display.
The supplied patch prevents unexpected exception by confirming the validation of display ID.
Some SVE items included in the Samsung Android Security Update cannot be disclosed at this time.
Acknowledgements
We truely appreciate the following researchers for helping Samsung to improve the security of our products.
- Daniel Komaromy : SVE-2017-8889, SVE-2017-8890, SVE-2017-8891, SVE-2017-8892, SVE-2017-8893, SVE-2017-9008, SVE-2017-9009
- Qing Zhang of Xiaomi and Guangdong Bai of Singapore Institute of Technology (SIT) : SVE-2017-9383
NOVEMBER:
Code:
SMR-NOV-2017
Samsung Mobile is releasing a maintenance release for major flagship models as part of monthly Security Maintenance Release (SMR) process. This Security Update package includes patches from Google and Samsung.
The following CVE items from November 2017 Android Security Bulletin are included in this Security Update package:
Critical
CVE-2017-11053, CVE-2017-9714, CVE-2017-0832, CVE-2017-0833, CVE-2017-0834, CVE-2017-0835, CVE-2017-0836, CVE-2017-0841
High
CVE-2017-9075, CVE-2017-11063, CVE-2017-0830, CVE-2017-0831, CVE-2017-0839, CVE-2017-0840, CVE-2017-0842, CVE-2017-0852, CVE-2017-0853(M 6.x), CVE-2017-0854(M 6.x), CVE-2017-0857(M 6.x), CVE-2017-0858(M 6.x), CVE-2017-0859(M 6.x), CVE-2017-13077, CVE-2017-13078, CVE-2017-13079, CVE-2017-13080, CVE-2017-13081, CVE-2017-13082, CVE-2017-13086, CVE-2017-13087, CVE-2017-13088
Moderate
CVE-2017-0824, CVE-2017-0825, CVE-2017-7187, CVE-2017-9686, CVE-2017-11050, CVE-2017-11067, CVE-2017-11056, CVE-2017-11046, CVE-2017-9706, CVE-2017-11048, CVE-2017-9697, CVE-2017-11051, CVE-2017-9715, CVE-2017-9717, CVE-2017-11054, CVE-2017-11055, CVE-2017-0845, CVE-2017-0847, CVE-2017-0848, CVE-2017-0849, CVE-2017-0850, CVE-2017-0851, CVE-2017-0853(N 7.x, O 8.0), CVE-2017-0854(N 7.x, O 8.0), CVE-2016-2105, CVE-2016-2106, CVE-2017-3731, CVE-2017-0860
Low
None
NSI
CVE-2017-0857(N 7.x, O 8.0), CVE-2017-0858(N 7.x, O 8.0), CVE-2017-0859(N 7.x)
Already included in previous updates
None
Not applicable to Samsung devices
CVE-2017-7374, CVE-2017-0827, CVE-2017-9683, CVE-2017-0826, CVE-2017-0828, CVE-2017-0829, CVE-2017-11062, CVE-2017-9687
※ Please see Android Security Bulletin for detailed information on Google patches.
Along with Google patches, Samsung Mobile provides 6 Samsung Vulnerabilities and Exposures (SVE) items described below, in order to improve our customer's confidence on security of Samsung Mobile devices. Some of the SVE items may not be included in this package, in case these items were already included in a previous maintenance release.
SVE-2017-8973, SVE-2017-8974, SVE-2017-8975: TA Scrypto v1.0 Vulnerability
Severity: Low
Affected versions: M(6,x), N(7.0)
Reported on: April 17, 2017
Disclosure status: Privately disclosed.
A race condition may occur in Secure Driver resulting in potential buffer overflow vulnerability.
The patch prevents race condition and buffer overflow by checking boundary of a buffer.
SVE-2017-10086: Arbitrary file read/write in locked device via mtp
Severity: High
Affected versions: KK(4.4.x), L(5.x), M(6.x), N(7.x)
Reported on: August 17, 2017
Disclosure status: Privately disclosed.
Device responds from malicious MTP command on the locked state.
The patch prevents the device from responding from a malicious MTP command when it receives MTP command on the locked state.
SVE-2017-10465: Bug in MSM8998 chipset’s bootloader that checks integrity of system image (SamFAIL)
Severity: High
Affected versions: N(7.x)
Reported on: October 08, 2017
Disclosure status: Privately disclosed.
A vulnerability in verification logic within the bootloader in Qualcomm MSM8998 chipset allows an attacker to successfully boot the Samsung Galaxy Note8 device with root privilege.
The patch prevents an Attacker from booting Note8 successfully by checking an integrity of system image.
Some SVE items included in the Samsung Android Security Update cannot be disclosed at this time.
Acknowledgements
We truly appreciate the following researchers for helping Samsung to improve the security of our products.
- Salvatore Mesoraca : SVE-2017-10086
- Daniel Komaromy : SVE-2017-8973, SVE-2017-8974, SVE-2017-8975
DECEMBER:
Code:
SMR-DEC-2017
Samsung Mobile is releasing a maintenance release for major flagship models as part of monthly Security Maintenance Release (SMR) process. This Security Update package includes patches from Google and Samsung.
The following CVE items from December 2017 Android Security Bulletin are included in this Security Update package:
Critical
CVE-2017-11013, CVE-2017-11015, CVE-2017-11014, CVE-2017-0427, CVE-2017-0872, CVE-2017-0878, CVE-2017-13151, CVE-2017-13160, CVE-2015-3868, CVE-2017-0675, CVE-2017-6211
High
CVE-2017-0871, CVE-2017-9077, CVE-2017-7541, CVE-2017-0843, CVE-2017-11092, CVE-2017-11028, CVE-2017-0838, CVE-2017-0807, CVE-2017-0870, CVE-2017-13153, CVE-2017-0837, CVE-2017-0873, CVE-2017-0874, CVE-2017-0880, CVE-2017-13148, CVE-2017-13156, CVE-2017-13157, CVE-2017-13158, CVE-2017-13159, CVE-2017-13077, CVE-2017-0879(L5.1, M6.x), CVE-2017-13149(L5.1, M6.x), CVE-2017-13150(M6.x)
Moderate
CVE-2017-11057, CVE-2017-11059, CVE-2017-11061, CVE-2017-11060, CVE-2017-11052, CVE-2017-11064, CVE-2017-0861, CVE-2017-1160, CVE-2017-11073, CVE-2017-11035, CVE-2017-11012, CVE-2017-11085, CVE-2017-11091, CVE-2017-11032, CVE-2017-11024, CVE-2017-11025, CVE-2017-11023, CVE-2017-11029, CVE-2017-11018, CVE-2017-9702, CVE-2017-11089, CVE-2017-8239, CVE-2017-11090, CVE-2017-11093, CVE-2017-8279, CVE-2017-9696, CVE-2017-11058, CVE-2017-11022, CVE-2017-0879(N7.x, O8.0), CVE-2017-13149(N7.x, O8.0), CVE-2017-13150(N7.x, O8.0), CVE-2017-13152
Low
None
NSI
None
Already included in previous updates
None
Not applicable to Samsung devices
CVE-2017-6264, CVE-2017-9690, CVE-2017-11017, CVE-2017-6001, CVE-2017-0862, CVE-2017-0863, CVE-2017-0864, CVE-2017-0865, CVE-2017-0866, CVE-2017-6274, CVE-2017-6275, CVE-2017-11026, CVE-2017-11038, CVE-2017-9719, CVE-2017-9721, CVE-2017-9701, CVE-2017-11027, CVE-2017-0876, CVE-2017-0877
※ Please see Android Security Bulletin for detailed information on Google patches.
Along with Google patches, Samsung Mobile provides 10 Samsung Vulnerabilities and Exposures (SVE) items described below, in order to improve our customer's confidence on security of Samsung Mobile devices. Some of the SVE items may not be included in this package, in case these items were already included in a previous maintenance release.
SVE-2017-8907: Information disclosure on Samsung gpu
Severity: Moderate
Affected versions: M(6.x), N(7.x)
Reported on: April 14, 2017
Disclosure status: Privately disclosed.
kbase_context address in gpu memory node is exposed and it may result in unauthorized information disclosure.
The patch prevents kernel memory address exposure which includes kbase_context address in gpu node.
SVE-2017-10011: muic_set_reg_sel heap_overflow
Severity: Moderate
Affected versions: L(5.1), M(6.x), N(7.x)
Reported on: August 17, 2017
Disclosure status: Privately disclosed.
System can be crashed by non-existence of null pointer check; and buffer overflow vulnerability exists because the size to be copied from user space is not checked.
The patch prevents Null Pointer dereference and buffer overflow when muic register values are read.
SVE-2017-9414: panel_lpm sysfs stackOverflow issue
Severity: Moderate
Affected versions: M(6.x), N(7.x) with Qualcomm chipsets
Reported on: June 5, 2017
Disclosure status: Privately disclosed.
The size of user data is not checked and it makes buffer overflow when user data is copied into an array.
The patch prevents buffer overflow when user data is copied in lpm ctrl debug function.
SVE-2017-10598: Arbitrary Code Execution in the Samsung Bootloader
Severity: Moderate
Affected versions: L(5.x), M(6.x), N(7.x) with Exynos chipsets
Reported on: October 8, 2017
Disclosure status: This issue is publicly known.
S Boot copies ramfs data to its memory without checking validation of the size making it possible to overwrite the code segment of S Boot which can result in arbitrary code execution in bootloader.
The patch prevents arbitrary code execution in bootloader by checking the limit of ramdisk size.
Some SVE items included in the Samsung Android Security Update cannot be disclosed at this time.
Acknowledgements
We truly appreciate the following researchers for helping Samsung to improve the security of our products.
- Yaoguang Chen of Ant-financial Light-Year Security Lab : SVE-2017-8907
- Yu Pan and Yang Dai of Vulpecker Team Qihoo 360 Technology Co. Ltd : SVE-2017-10011, SVE-2017-9414
- Hung Chi Su of Team T5 : SVE-2017-10598
Development Status:
This is the development status section here you will be able to see what I am currently doing for this rom. If I have an older firmware version listed as latest please inform me as I only have worked with W8 devices in the past. Refer to the legend below to see what each status means.
LEGEND
STOPPED: Latest link available. No updates till next patch.
IN DEVELOPMENT: New build uploaded by sammobile. Development begins.
TESTING: Development ended. Ensuring rom is functional.
UPLOADING: Testing has ended now uploading.
BEFORE APPLYING NEW BUILDS. DOWNLOAD NEW STOCK FIRMWARES AND FLASH THEM THROUGH ODIN. THEN FLASH TWRP VIA ODIN THEN MY ROM.BEFORE APPLYING NEW BUILDS. DOWNLOAD NEW STOCK FIRMWARES AND FLASH THEM THROUGH ODIN. THEN FLASH TWRP VIA ODIN THEN MY ROM.BEFORE APPLYING NEW BUILDS. DOWNLOAD NEW STOCK FIRMWARES AND FLASH THEM THROUGH ODIN. THEN FLASH TWRP VIA ODIN THEN MY ROM.
PLEASE BE VERY CAREFUL AS THESE ARE STOCK ROMS THEY ARE NOT CUSTOMIZED SO FLASHING EDGE ROMS ON FLAT MODELS COULD RESULT IN SOFT BRICK, IMEI LOSS OR DEAD EMMC. YOU HAVE BEEN WARNED. IF YOU CLICK THE DOWNLOAD BUTTON YOU AGREE THAT YOU TAKE FULL RESPONSIBILITY FOR ANY DAMAGES YOU MAY CAUSE. IF YOU BLAME ME OR ANY OTHER DEVELOPERS FOR YOUR FAILURE TO UNDERSTAND THESE MESSAGES THEN WE WILL NOT HELP YOU SOLVE YOUR PROBLEM.
GALAXY S6
920W8 STATUS: STOPPED
BUILD NUMBER: G920W8VLS5DQK1
Security LEVEL: 2017-11-01
REASON: Waiting for December patch from Samsung. Nov. Patch Available.
NEXT UPDATE ETA: December (Date Unknown)
LINK: DOWNLOAD
920F STATUS: STOPPED
BUILD NUMBER: G920FXXS5EQL1
Security LEVEL: 2017-12-01
REASON: December patch Finished. Link Available.
NEXT UPDATE ETA: January (Date Unknown)
LINK: DOWNLOAD
920I STATUS: STOPPED
BUILD NUMBER: G920IDVS3FQL5
Security LEVEL: 2017-12-01
REASON: December patch Finished. Link Available.
NEXT UPDATE ETA: January (Date Unknown)
LINK: DOWNLOAD
GALAXY S6 EDGE
925W8 STATUS: STOPPED
BUILD NUMBER: G925W8VLS5DQH1
Security LEVEL: 2017-08-01
REASON: Waiting for December patch from Samsung. Aug. Patch Available.
NEXT UPDATE ETA: September (Date Unknown)
LINK: DOWNLOAD
925F STATUS: STOPPED
BUILD NUMBER: G925FXXS5EQL1
Security LEVEL: 2017-12-01
REASON: December patch Finished. Link Available.
NEXT UPDATE ETA: January (Date Unknown)
LINK: DOWNLOAD
925I STATUS: STOPPED
BUILD NUMBER: G925IDVS3FQL5
Security LEVEL: 2017-12-01
REASON: December patch Finished. Link Available.
NEXT UPDATE ETA: January (Date Unknown)
LINK: DOWNLOAD
Bugs:
-Samsung Internet Secret Mode works initially then never again.
TEMP FIX: Use internet beta from play store. (Basically same app but allows p0rn mode to work.)
XDA:DevDB Information
SamStock ROM, ROM for the Samsung Galaxy S6
Contributors
Moiz Ahmed
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Latest Modem and Bootloader
Based On: Samsung Stock
Version Information
Status: Stable
Stable Release Date: 2017-07-31
Created 2017-08-01
Last Updated 2017-12-25
Reserved
DECEMBER BRANCH STARTED
Devices updated:
S6 FLAT
-920I
-920F
S6 EDGE
-925F
-925I
Devices not yet updated:
S6 FLAT
-920W8 (NOV)
S6 EDGE
-925W8 (AUG)
FIXES:
-Removed SVCAgent from rom to aroma. (PART OF S-Voice)
-root updated to magisk 14
-Added DTM CSC for 920F
-other fixes include bug fixes in samsung source code found in the SMR and during installation.
Reserved
Moiz Ahmed said:
Other roms not giving you the performance or battery life you want? Try SAMSTOCK rom. It's so stock that its stock. Some rom makers like to customize their rom by branding it with their name, and I have nothing against that.
This rom however has none of that.
Features:
-Untouched. Completely stock out of the latest zip from sammobile.
-July Security Patch
-Multi CSC just like stock firmware
-Safetynet Passed
-Private Mode working
-System Status = Official (In DL mode and in about phone)
-Can check for and DL latest updates from samsung
-No branding by me at all
-No changes to any apk
-SE for Android Status: ENFORCING
-Samsung Health working fully
-Latest ROOT by topjohnwu
Whats customized
-this line from build.prop : "ro.config.tima=0"
But why DEV? You said stock.
To make Samsung Health work again.
NO OTHER FILE IN THIS ROM HAS BEEN TOUCHED ABSOLUTE STOCK!!
Debloated apps include:
All available to reinstall from aroma.
-Facebook
-Instagram
-Onenote
-Peel Smart remote
-Skype
-WhatsApp
-Microsoft Excel
-Microsoft PowerPoint
-Microsoft Word
-Microsoft OneDrive
-Hancom Office
-Samsung Health
-S Voice (Honestly don't torture yourself)
-Yahoo Edge Panels (EDGE ONLY)
Requirements:
-Device SM-G920W8, SM-G925W8
-Flash latest firmware from Samsung
-Must be latest Bootloader and modem
-If you come to me with bricked devices I'll honestly just laugh. It says what you need right above this.
Installation:
-Backup your garbage
-Power off
-Charge to 80% or higher
-Boot into TWRP
-Advanced wipe all partitions except for /usbstorage
-Install Zip
-Select the garbage you want
-Let it install
-Reboot
FAQS
Q: When are you updating this rom?
A: When samsung releases the next update
Q: When are you adding [Insert feature name here]?
A: Never. Its stock what ever stock comes with is what you get. There are other roms available for that.
Q: My phone is taking too long to boot. What should I do?
A: Did you follow all instructions? First boot take 10-15 minutes.
Q: Fingerprint reader doesn't work. What do I do?
A: Device needs to be restarted.
Q: Can you remove/debloat [INSERT APP NAME HERE] and put it in aroma?
A: Sure when there's a new patch from Samsung I will.
Q: Does this work with my device?
A: If its a G920W8/925W8. Yes. Yes it does. If not. Get out.
Q: OK dev my garbage works like you said. Now what?
A: Let me know how you like it. Drop a like and enjoy. :laugh: :good:
Thanks to:
-amarullz for Aroma
-topjohnwu for Magisk 13.3 Root
-Samsung for the stock rom
-Carriers for doing nothing
DROP THESE GUYS A LIKE TOO THEY DESERVE IT.
For Developers:
-If you want to use this as a base for your rom please PM me and i'll reply asap
-If you want to help add features to aroma them PM me so we can talk business
Development Status:
This is the development status section here you will be able to see what I am currently doing for this rom.
920W8 STATUS: STOPPED
BUILD NUMBER: G920W8VLS5DQG1
REASON: Rev 1.2 Uploaded. No new updates from samsung.
ETA: August (Day Unknown)
920F STATUS: IN DEVELOPMENT
REASON: Working on initial release. 920F Testers needed.
ETA: Unknown
925W8 STATUS: STOPPED
BUILD NUMBER: G925W8VLS5DQG1
REASON: Uploaded. No new updates from samsung.
ETA: August (Day Unknown)
925F STATUS: IN DEVELOPMENT
REASON: Working on initial release. 925F Testers needed.
ETA: Unknown
Bugs:
-Samsung Internet Secret Mode works initially then never again.
TEMP FIX: Use internet beta from play store. (Basically same app but allows secret mode to work.)
Download:
PLEASE BE PATIENT AS I TRANSFER FILES TO A NEW DRIVE ACCOUNT. LINKS WILL BE UP SOON.
SM-G920W8NOT AVAILABLE
SM-G925W8NOT AVAILABLE
SM-G920F NOT AVAILABLE
SM-G925F NOT AVAILABLE
XDA:DevDB Information
SamStock ROM, ROM for the Samsung Galaxy S6
Contributors
Moiz Ahmed
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Latest Modem and Bootloader
Based On: Samsung Stock
Version Information
Status: Stable
Stable Release Date: 2017-07-31
Created 2017-08-01
Last Updated 2017-07-31
Click to expand...
Click to collapse
What about SM-G925I?
nokia_16 said:
What about SM-G925I?
Click to expand...
Click to collapse
If a lot more people want it i'll do a 925I and 920I. I have a Ryzen 5 CPU and extraction and compression of these firmwares simultaneously doesn't take too much time but i need people to actually use it otherwise my work is worth nothing.
Hi,
Thanks for uploading the Rom. I'd like to have a look. Though two questions :
A) the description about support for g920f is a bit inconsistent. It says it is stopped and you say only the g920w variants work, but then there is a download link.
B) which csc is this based on? Does VoLTE work? Especially on German t-mobile? It usually requires a DTM csc
Br
Johannes
orgler said:
Hi,
Thanks for uploading the Rom. I'd like to have a look. Though two questions :
A) the description about support for g920f is a bit inconsistent. It says it is stopped and you say only the g920w variants work, but then there is a download link.
B) which csc is this based on? Does VoLTE work? Especially on German t-mobile? It usually requires a DTM csc
Br
Johannes
Click to expand...
Click to collapse
Hi sorry for the confusion. Stopped means i'm not doing any work on it anymore till next samsung update. As for csc when I unpacked the stock zip there was only one csc which led me to believe its an unlocked csc. All other models had multi csc support. Try it and let me know please i only have the W8 model. I'll take a look tomorrow morning.
Moiz Ahmed said:
If a lot more people want it i'll do a 925I and 920I. I have a Ryzen 5 CPU and extraction and compression of these firmwares simultaneously doesn't take too much time but i need people to actually use it otherwise my work is worth nothing.
Click to expand...
Click to collapse
May be once you do for 925I a lot user may opt to your rom coz there is no stock debloated nought rom for G925I. Hence its my request to make your rom for G925I. This is only an request. Also if you decided to do so go for INS csc or multi csc whch has INS or INU, coz both csc volte will work.
nokia_16 said:
May be once you do for 925I a lot user may opt to your rom coz there is no stock debloated nought rom for G925I. Hence its my request to make your rom for G925I. This is only an request. Also if you decided to do so go for INS csc or multi csc whch has INS or INU, coz both csc volte will work.
Click to expand...
Click to collapse
Ok I think I'll start tomorrow morning. Please link me to the latest multi csc for 920I and 925I from sammobile.com
Moiz Ahmed said:
Ok I think I'll start tomorrow morning. Please link me to the latest multi csc for 920I and 925I from sammobile.com
Click to expand...
Click to collapse
Sammobile has not yet updated latest version for g925i ..I am sending you direct link for g925i. Updated one similar to sammobile.
Here is the link...
nokia_16 said:
Sammobile has not yet updated latest version for g925i ..I am sending you direct link for g925i. Updated one similar to sammobile.
Here is the link...
Click to expand...
Click to collapse
Great downloading now. Could you also send me the 920I link usually same last 4 characters as 925I.
nokia_16 said:
Sammobile has not yet updated latest version for g925i ..I am sending you direct link for g925i. Updated one similar to sammobile.
Here is the link...
Click to expand...
Click to collapse
Great downloading now. Could you send me the 920I link. It's usually same last 4 build number characters.
Can anyone point me in the direction where I can find the latest modem and bootloader for my SM-G920F? And does the region of the modem matter? tnx
amgat said:
Can anyone point me in the direction where I can find the latest modem and bootloader for my SM-G920F? And does the region of the modem matter? tnx
Click to expand...
Click to collapse
Hi yes region does matter. the simple way would be to go HERE download the latest firmware for your model and region then flash using odin. then return here and flash this. TO find out your region go to dialer type *#1234# and the values that appear will guide you in finding your region.
Thank you Moiz Ahmed!. Does the firmware contain the latest modem as well? Or is not that important to update the modem?
amgat said:
Thank you Moiz Ahmed!. Does the firmware contain the latest modem as well? Or is not that important to update the modem?
Click to expand...
Click to collapse
Very important to update both modem and bootloader. Best to do a complete wipe flash latest stock then this.
The firmware file is 1.8GB in size. So the firmware file from updato is actually the stock ROM right? Sorry for asking dumb questions
Does Secure Folder work with this rom?
amgat said:
The firmware file is 1.8GB in size. So the firmware file from updato is actually the stock ROM right? Sorry for asking dumb questions
Click to expand...
Click to collapse
Yes it is.
huyhung411991 said:
Does Secure Folder work with this rom?
Click to expand...
Click to collapse
Nope
I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
If you want to check firmware - please make backup.
Instructions
1. Install latest TWRP
2. Download the zip(s) - firmware and Google Apps additional package (optional)
3. Backup all partitions (it least efs) and store somewhere - it need to do - because you can loose imei
4. Full wipe all
5. Flash firmware and gapps
Work
almost all
Known Issues
-
LineageOS Builds
Code:
few notes about 20190316 update:
1. New kernel, our is very old 3.18.14, new one is 3.18.91. this is latest M105FDDU1ASB2 from relative exynos7870
2. Our wifi driver depends on the kernel. I can't just take a new kernel (or update the current one), it will most likely cause a kernel panic with the current wifi module. For some reason, samsung cut out the wifi sources/config from kernel. So I spent a week and was able to add the source of the wifi driver to the kernel and made a config for it. As result we can forgot about stand alone .ko wifi module, now it's part of kernel. And as bonus: our old wifi module's version is: 4.0.10.205Y_0903, new one is: 4.0.11.213X
3. I reviewed the defconfigs, make it similar to m10 from latest kernel, updated the file systems config (thanks to [user=5480152]@followmsi[/user]), activated pie sdcardfs sources, fixed vibrator for T585 (it was big misunderstand with dtb blocks)
4. I fixed the build logic of the dtb part (now it's part of defconfig)
5. I added doze service (power consumption)
6. I added fingerprint from xiaomi sagit (for pass safetynet check in Magisk, thanks [user=5480152]@followmsi[/user])
Code:
few notes about 20181223 update:
1. rebrand wifi, now it is loaded during the run of the wifi service, and not in init scripts, as before
2. made small updates in hwc for smooth gui
3. fixed gps for T585, may be it's quite slow, but working
4. fixed hostap for T585 (it's still buggy and sometimes turn on not from first attempt, but working)
Code:
few notes about 20181204 update:
this is huge update, a lot of changes here:
1. update for hew hardware support, now we use proprietary files from latest 8.1
- new mali driver r22 (early was old r15 version)
- new camera (new with exynoscamera3, it was missed for our tablets in 7.0)
- new OMX libs
2. latest official kernel (I asked samsung about sources few weeks ago)
- with new r22 mali support
- with new wifi driver
3. now with new hardware almost no any shims (only one missed symbol for camera), now no any shims for OMX with libui and etc
P.s. thanks [user=5480152]@followmsi[/user] for some fixes and hints.
SM-T580
17. 20191211: december security patch: https://drive.google.com/file/d/1gkEA0A7VH0DGIvI2yJWYWSwyfCbXdTn3/view?usp=sharing
16. 20191113: november security patch: https://drive.google.com/file/d/1xt8L8C8WuhEzA8x4mHyErzrmq3Ylm8Qr/view?usp=sharing
15. 20191023: october security patch: https://drive.google.com/file/d/17zVXccAuJV-Ojyh8gJBJBG6oM-IqnZ_7/view?usp=sharing
14. 20190911: fix front camera, september security patch: https://drive.google.com/file/d/1RkzvX9FE3ilut01OBSgOFP45JgICzcVl/view?usp=sharing
13. 20190811: august security patch: https://drive.google.com/file/d/16-7M4rc0q-IzCVUnTaSy9wwEOJZG6Zdg/view?usp=sharing
12. 20190707: july security patch: https://drive.google.com/file/d/1CkiJjWDfY1pq5KcF_kCNUQtqAA6n6ouw/view?usp=sharing
11. 20190518: update wifi driver (4.0.10.206A_20181017): https://drive.google.com/file/d/1v33yHO7zBi0UCswqZaB7vj1aYJvCtvq0/view?usp=sharing
10. 20190331: another test version: wifi driver from codeaurora, correspond to our stock 4.0.10.205 version, update wifi\bt drivers and configs, remove mobicore, 3.18.137 kernel with OC (thanks @followmsi), update interfaces (health, trust, netd, composer, mapper) to new versions: https://drive.google.com/file/d/1m77GggfDTINHqxaXxzTrR0MMsThnO_ni/view?usp=sharing
9. 20190320: fix flip: https://drive.google.com/file/d/1WO1tAx8wyMJim-07Z3oaea6YWiuwZmmo/view?usp=sharing
8. 20190319: fix flip: https://drive.google.com/file/d/18tcp3h7Eh06OAPWnWTAJQqgtTo0e58rg/view?usp=sharing
7. 20190316: test version with huge update (but it look very stable): fix vibrator, new kernel, new defconfig, new wifi driver, doze (see notes): https://drive.google.com/file/d/1Kf42kG8dnK7lxwBKXr2SjVvyqmH6bzZC/view?usp=sharing
6. 20190208: security patch level - february 5, 2019: https://drive.google.com/open?id=1p9rQWrHg-icHdm94g1PohaeOzwoDZhOs
5. 20190126: https://drive.google.com/file/d/1cqt_kSSjDzkDETpVhuyzkCF9EMVo5oDd/view?usp=sharing
4. 20181223: https://drive.google.com/file/d/1fWRfB3kl2vAnCwUEVzRPGOysm7Vs594k/view?usp=sharing
3. 20181204: https://drive.google.com/file/d/1xI_H5HP9gS1iL8femUaw5UltHzBrCkae/view?usp=sharing
2. 20181027: https://drive.google.com/file/d/1EAGuOUcL5Rw6_E5ZPGurRo9NYVx9dgNy/view?usp=sharing
1. 20180920: https://drive.google.com/file/d/1BFxGIqJKb0VYyaPyq9ejhWBHIOcfJ7kN/view?usp=sharing
SM-T585
15. 20191211: december security patch: https://drive.google.com/file/d/1-SjMSP6fhk8XsQ1IBZj1I2psKLaZT55Y/view?usp=sharing
14. 20191113: november security patch: https://drive.google.com/file/d/1E8KZdoXWXyZU8xop3OtdZISCX6v5fmnd/view?usp=sharing
13. 20191023: october security patch: https://drive.google.com/file/d/1o5EiqTDawP_cZYEMHKePxEGsLONw5iSh/view?usp=sharing
12. 20190911: fix front camera, september security patch: https://drive.google.com/file/d/1cz4ThdAxVFfnbk9-1rHbUd0_ue9RHOb5/view?usp=sharing
11. 20190811: august security patch: https://drive.google.com/file/d/1tY8WNyVkqS7cCeP82H8SF0n-QTlZVZtt/view?usp=sharing
10. 20190707: july security patch: https://drive.google.com/file/d/1HZoLhDRrOTU2I2a1walYPbhg35CVJCvp/view?usp=sharing
9. 20190518: update wifi driver (4.0.10.206A_20181017): https://drive.google.com/file/d/1zPZM0Z9ItaZgfiZd13x4zT495L5LP5ux/view?usp=sharing
8. 20190331: another test version: wifi driver from codeaurora, correspond to our stock 4.0.10.205 version, update wifi\bt drivers and configs, remove mobicore, 3.18.137 kernel with OC (thanks @followmsi), update interfaces (health, trust, netd, composer, mapper) to new versions: https://drive.google.com/file/d/16JdWMFQLFj1lsTZ1LcJkS-B_suHQUDmJ/view?usp=sharing
7. 20190320: fix flip: https://drive.google.com/file/d/1NgVwKv_58nzO_HnPIOzPE_iCqhl9XbH1/view?usp=sharing
6. 20190319: fix flip, access point, gps: https://drive.google.com/file/d/1Qr62AXurpt97UyNMz8Po8eYauiFQDuJJ/view?usp=sharing
5. 20190316: test version with huge update (but it look very stable): fix vibrator, new kernel, new defconfig, new wifi driver, doze (see notes): https://drive.google.com/file/d/1tk2hEe0yo4Bi9TdXVELEJr71vwl5AhE8/view?usp=sharing
4. 20190208: security patch level - february 5, 2019: https://drive.google.com/open?id=1StiJuRDl5DMERHOhkpxKfJvrGRgay2tH
3. 20190126: https://drive.google.com/file/d/1pEpEtf0vf9AUNtrkhXHilE0QO9okboIi/view?usp=sharing
2. 20181223: https://drive.google.com/file/d/1bYv4SpBAnXHr6Q7xw7CX2eCLicI-WUKm/view?usp=sharing
1. 20181204: https://drive.google.com/file/d/1FQL9SRNqHFOozlcJfSDs96VW344tTl3f/view?usp=sharing
Gapps
https://opengapps.org
Platform: ARM64
Android: 9.0
Variant: any
Root
Install official Magisk. if Magisk Manager missed in apps - install Magisk Manager apk
TWRP
official twrp:
SM-T580: https://twrp.me/samsung/samsunggalaxytaba101wifi2016.html
SM-T585: https://twrp.me/samsung/samsunggalaxytaba101lte2016.html
Sources
Sources: https://github.com/Lineageos
Kernel: https://github.com/Valera1978/android_kernel_samsung_exynos7870
Device: https://github.com/Valera1978/android_device_samsung_gtaxlwifi
Vendor: https://github.com/Valera1978/android_vendor_samsung_gtaxlwifi
Thanks
Thanks to LineageOS team
Right now I have only the SM-T580. Soon will back my SM-T585 and I will then make Lineage 16.0 for SM-T585 too.
Can you release this for the T350?
Valera1978 said:
Right now I have only the SM-T580. Soon will back my SM-T585 and I will then make Lineage 16.0 for SM-T585 too.
Click to expand...
Click to collapse
I can't wait for 585!!!
Does 3.5 jack works on this rom?
I am asking this because it was dead on 64-bit treble Oreo/Pie and it was not mentioned in bugs section too.
tank0412 said:
Does 3.5 jack works on this rom?
I am asking this because it was dead on 64-bit treble Oreo/Pie and it was not mentioned in bugs section too.
Click to expand...
Click to collapse
The connection works, have tested.
Is the pie guesture navbar avaliable?
Cast not working
Good work.:good: Seems to work well. But, as with every other 64bit ROM I've tried, casting to a regular Chromecast dongle just gives a black screen and no audio. People with a Chromecast Ultra dongle tell me theirs works, but I'm retired and living on SS, so I'm not going to spend for a new dongle when it works fine in 32bit RR Oreo.
Since this seems to be a problem with all 64bit ROMs, and not just this one, I guess I'll just have to wait until it's fixed somewhere up the line.:crying:
Nice work! Would it be possible to get the pie gestures or navbar customization options added in the settings?
Currently the dark or black theme for the UI doesn't work.
As for the Chromecast problem that Lewmur is reporting as not working: can anybody confirm this? For me it is rather vital it works.
And what is actually meant by the "FC problem" with the camera. Does it just mean it is "f*cked up" or what ?
Thanks...
Valera1978 said:
Right now I have only the SM-T580. Soon will back my SM-T585 and I will then make Lineage 16.0 for SM-T585 too.
Click to expand...
Click to collapse
Really looking forward for that build. Will try it as soon as released on my T585.
I tried "Cast" with my Microsoft Wireless Display Adapter - does not work Seems to be the same than with the Android dongles.
Will this work on the P580, just without the ability to use the pen? I don't frequently use or even really like the pen anyway, so I'm fine with that, I bought the S-Pen version for the extra gig of RAM.
Good Rom, thanx. But for me GPS not working. Can you fix it please.
I have installed the Rom for a few days ago.
It's works fine and the battery is okay.
But, I have found 2 Problems / fails.
1. I can not wake up the tablet with the homebutton.
2. the Displays goes short black, when I turn it from vertical to horizontal.
Sorry for my english
AlbertHB said:
I have installed the Rom for a few days ago.
It's works fine and the battery is okay.
But, I have found 2 Problems / fails.
1. I can not wake up the tablet with the homebutton.
2. the Displays goes short black, when I turn it from vertical to horizontal.
Sorry for my english
Click to expand...
Click to collapse
Those to are lineage related i think.
Installed it on my sm-t580 and works perfekt.
Gesendet von meinem HTC U11 mit Tapatalk
Keep getting an error:7 in twrp when I go to flash the rom. Any suggestions? Also any alternate links to d/l file from?
arachniac1 said:
Keep getting an error:7 in twrp when I go to flash the rom.
Click to expand...
Click to collapse
Hi,
error 7 means (AFAIK) that the image does not fit the model of your device.
Do you have the SM-T580?
Yes, I have the Samsung tab a SM-T580 (2016) wifi gtaxlwifi. Do you think I need a different version of twrp?
As I said several times, if someone starts to build the current version of the lineage that I do, I completely close the project.
In May, I closed the port, based on 10 android and now the time to completely close all work on exynos7870. There was only one reason why I didn't do it earlier - I promised to fix the sound during calls in the LTE version. Now all done, I dont have any desire and motivation to do anything for the exynos7870.
This decision is final, I switched now to the work on note pro 12.2 wifi variant, my smart home and think about starting tab s6.
Thanks to everyone who has been with me all these years, I will see you on other projects.
I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
If you want to check firmware - please make backup.
Instructions
1. Install latest TWRP
2. Download the zip(s) - firmware and Google Apps additional package (optional)
3. Backup all partitions (it least efs) and store somewhere - it need to do - because you can loose imei
4. Full wipe all
5. Flash firmware and gapps
Work
almost all
Known Issues
Lineage Builds
SM-T580
15. 20200815: august security patch: https://drive.google.com/file/d/1m67wMYmMbQOCoNLxalgJ9Pv6T7ruQ2G6/view?usp=sharing
14. 20200630: june security patch, review device tree, switch to samsung stock sound: https://drive.google.com/file/d/1xgvXjydnklYZeVHz6Mumgf7jUAm6oSEz/view?usp=sharing
13. 20200412: april security patch: https://drive.google.com/file/d/1Isqa8WAlghmCGTMSGnKEsfUX9dUicM0n/view?usp=sharing
12. 20200211: latest sources, February security patch: https://drive.google.com/file/d/1jY2riYpLUJ8EFtOMFSXo9o57_Ijr-qVm/view?usp=sharing
11. 20200113: latest sources, January security patch: https://drive.google.com/file/d/1hnEUDgcugxBLbhQw5d-q9mU75rierlZX/view?usp=sharing
10. 20191202: rollback video driver to r22, merge kernel up to 3.18.140 (thanks @followmsi), aptx driver (thanks @followmsi): https://drive.google.com/file/d/1K_K6yfJHmjCNJSR12eAh46-7FhagcT4Z/view?usp=sharing
9. 20191116: november security update: https://drive.google.com/file/d/1CcX6FnTon8OxM99qbUad9NW6rPrJbUgw/view?usp=sharing
8. 20191114: beta version: update video driver up to r28, update omx codecs, latest updates from @followmsi: https://drive.google.com/file/d/18axNa2sq6ekZeADBzTZeXlOOaJ1dg8WN/view?usp=sharing
7. 20191028: disable Codec2.0 components (long delay on start youtube) (thanks @followmsi), fix vulkan libs (thanks @followmsi): https://drive.google.com/file/d/1mAAEstZz9sOSCFWZiujaGKv-kkslIEwV/view?usp=sharing
6. 20191013: audio from sources: https://drive.google.com/file/d/1R6JDLG-H8bP6eGvex7R2PTYsCbrfQpdu/view?usp=sharing
5. 20191007: fix sensors: https://drive.google.com/file/d/1XsQ5qlP22XBGFQK6o1zKT0GLbVd_WlC7/view?usp=sharing
4. 20191003: https://drive.google.com/file/d/1LpthwW1Lf4fJW0nGwsThnJcZ8ToTKpUf/view?usp=sharing
3. 20190929: improved stability: https://drive.google.com/file/d/1qfKSQhDOI4LkthCpOckJLew0zIAZHo67/view?usp=sharing
2. 20190928: fix charger, home button: https://drive.google.com/file/d/1HBaqEwLux9XjTVgHT3IGMXnrCuJaqgTw/view?usp=sharing
1. 20190926: https://drive.google.com/file/d/1z5VCwOX9M8-ckb1Wt75oON6aUjMpx2hT/view?usp=sharing
SM-T585
15. 20200815: august security patch: https://drive.google.com/file/d/1OgIcsnfRRr5bFx5gd1kvKvtb8lELIMQa/view?usp=sharing
14. 20200630: june security patch, review device tree, switch to samsung stock sound: https://drive.google.com/file/d/110Zz5mlotOnDuFAjtuC5vNKa4VU1N0_I/view?usp=sharing
13. 20200412: april security patch: https://drive.google.com/file/d/1-llAbO2lZQ2T1qq743MxXZNtuHp7eAUX/view?usp=sharing
12. 20200211: latest sources, February security patch: https://drive.google.com/file/d/1l0APlqEK20cgJIGbBzaaekBIJrNFkilr/view?usp=sharing
11. 20200113: latest sources, January security patch: https://drive.google.com/file/d/1OskSZS28m268HRcTeTqFO_HQKB7NgWky/view?usp=sharing
10. 20191202: rollback video driver to r22, merge kernel up to 3.18.140 (thanks @followmsi), aptx driver (thanks @followmsi), fix hotspot: https://drive.google.com/file/d/1hbwkqI1jpctUUitA0Zg1a3LPj02KfSTS/view?usp=sharing
9. 20191116: november security update: https://drive.google.com/file/d/1eb_RdaAw6JSCNb_EsSUsPQnvCqGF_OeF/view?usp=sharing
8. 20191114: beta version: update video driver up to r28, update omx codecs, latest updates from @followmsi: https://drive.google.com/file/d/1cewbOdJapapRjBbk1X8k2mv9B5viBPlD/view?usp=sharing
7. 20191028: disable Codec2.0 components (long delay on start youtube) (thanks @followmsi), fix vulkan libs (thanks @followmsi), fix hotspot (there is still a bug - you cannot turn on wifi after activating a hotspot? need reboot tablet, but at least hotspot working): https://drive.google.com/file/d/1mqsNknYnJSh5cbml7dQ-xd5m0a-KlyCm/view?usp=sharing
6. 20191013: audio from sources: https://drive.google.com/file/d/1ymo05w9m9xukDsfLrZz6iBJMKNgarF4x/view?usp=sharing
5. 20191007: fix sensors: https://drive.google.com/file/d/14jOLZjLPyClboBZ8H3C2O6Dt0kFmXghS/view?usp=sharing
4. 20191003: ril: https://drive.google.com/file/d/18ZPRh19Rao1xRPQ5zI9jz7WfYIdonLZ2/view?usp=sharing
3. 20190929: improved stability: https://drive.google.com/file/d/1H5iinjtP2MBObqE-QWqWP0IMN_rRqK9Y/view?usp=sharing
2. 20190928: fixed charger, home button: https://drive.google.com/file/d/1bog0dKKJ17eXa7vgu9cB0K1U8XWTqBzb/view?usp=sharing
1. 20190926: https://drive.google.com/file/d/1Inx1A-6VNqtJJhTO3rmodKL2tiS1x8LH/view?usp=sharing
Gapps
https://opengapps.org
Platform: ARM64
Android: 10.0
Root
Install latest magisk from canary channel (version 20.1+): https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337
TWRP
official twrp:
SM-T580: https://twrp.me/samsung/samsunggalaxytaba101wifi2016.html
SM-T585: https://twrp.me/samsung/samsunggalaxytaba101lte2016.html
Sources
Sources: https://github.com/lineageos
Kernel: https://github.com/Valera1978/android_kernel_samsung_exynos7870
Device: https://github.com/Valera1978/android_device_samsung_gtaxllte and https://github.com/Valera1978/android_device_samsung_gtaxlwifi
Vendor: https://github.com/Valera1978/android_vendor_samsung_gtaxllte and https://github.com/Valera1978/android_vendor_samsung_gtaxlwifi
Thanks
Thanks to LineageOS team
XDA:DevDB Information
[ROM][SM-T580][SM-T585][UNOFFICIAL] Lineage 17.0 | Android 10 Q | 64bit, ROM for the Samsung Galaxy Tab A series
Contributors
Valera1978, Valera1978
ROM OS Version: Android 10
ROM Kernel: Linux 3.x
Based On: lineage
Version Information
Status: Beta
Created 2019-09-27
Last Updated 2019-09-27
Finally, I finished the first version of the new android q.
Initially I thought it would be an easy walk. But google in the new version made a huge amount of changes. And I spend about weeks to made something working.
I rebuild the config, wrote a library with sensors from scratch, there were big problems with wifi and sound. For the sound, I had to build a 32bit version to get the missing libraries.
hello how r u?
thx for your great works,
i always try your roms and you are the best
please is there any bugs for t585 before i try it?
and can u tell me how can i backup all of my phone with internal storage like norton ghost on windows pc?
can u tell me your telegram channel?
Hi, thanks for your great work.
I have installed and tested. For now this I have found:
- Magisk 19.3 and 19.4 do not work. Do not start the rom after installation.
- The battery percentage cannot be displayed in the status bar.
Seems to work GREAT on the 580, the only problem i have is I cant use the home button to wake the tablet. I've tried to configure the buttons in setting but it doesn't work. Only the power button will wake it....
michaeljr10wv said:
Seems to work GREAT on the 580, the only problem i have is I cant use the home button to wake the tablet. I've tried to configure the buttons in setting but it doesn't work. Only the power button will wake it....
Click to expand...
Click to collapse
Same here thanks for rom Valera
When my T580 boots, I get a message saying there is an internal error and to contact the manufacturer. I just ignore it and everything seems to work ok. That and the battery % are the only two nits I've come across so far.
lewmur said:
When my T580 boots, I get a message saying there is an internal error and to contact the manufacturer. I just ignore it and everything seems to work ok. That and the battery % are the only two nits I've come across so far.
Click to expand...
Click to collapse
I have that fault also with SM-T580 and in the Xiaomi Mi A1. It is a fault of Lineage. Just ignore it.
Clash Royale and Brawl Stars work great. The tablet is very fluid.
Great rom, first custom rome redirects the music via usb to my external dac without
extra app!!! Thanks for your great work Valera1978!
Thanks Valera
It works much smoother than stock and earlier aosp.
In addition to what the colleagues mentioned, it happens to me that in Google Chrome I open two tabs and restart the tablet
On the other hand with Firefox in a quick test of several tabs this did not happen.
Thank you for your spectacular work.
Thanks for the Android 10. Fast rom but some random reboot.
This rom look awsome, i will flash it when i will be able to unlock my tablet with the home button
Reboots
Updated to the 09/28 version. Have a problem with the tablet rebooting. I'm trying to use AZ Recorder to record streams from Tubi TV. Start AZ and then Chrome and try to load the Tubi site and the tablet reboots. Did the same thing on the earlier version.
New version 20190929. Hope random reboots now gone away. Was done set of fixes.
Checking few hrs, no any reboots.
Magisk 19.3 and 19.4 unsupported
Nuzza said:
Magisk 19.3 and 19.4 unsupported
Click to expand...
Click to collapse
Yes, checked a bit, magisk modifing init in the boot and somehow corrupt it and then on load init cann't get partitions information from dtb.
And internal su also not finished yet.
My primary phone is xiaomi mi9 - more then month I'm on android q and magisk 19.3 working great here.
I'll back to check magisk soon, I need root too.
Nuzza said:
Magisk 19.3 and 19.4 unsupported
Click to expand...
Click to collapse
I thought Android 10 you need the Magisk 19.5, still canary builds so might have some issues.
Github Tree
Zip File
You can give it a try if you want
Thanks, valera. But dont' work accelerator.
Keeps giving random errors on the sm-t580
Thanks for update. Random reboot go away. I found few bug. Accelerator and recent files display issue. Thanks
I am not responsible for lost data, identity theft, lost money, security vulnerabilities, bricked devices or any other hardware or software malfunctions that comes as a result of flashing this ROM.
Try this build at your own risk. It's likely to have bugs and is EXPERIMENTAL as it is a work in progress. It boots and seems to work fine on my SM-T350, but I have only tested it for 24 hours. Problems will likley surface later?
BACKUP YOUR FILES and have a copy of your working image BEFORE trying my build.
What works.
1. bluetooth
2. wifi
3. brightness
4. external audio
5. GPS
6. audio through headphone jack
7. Google play store - use pico apps
8. flip flap smart cover
9. audio over bluetooth
Note: first initial boot takes a bit longer, be patient.
Known problems.
1. Home screen text may look fuzzy.
Text on home screen looks funny/fuzzy. This only seems to affect the home screen and nowhere else. I have seen the same problem on the SM-T350, SM-T560NU, SM-P550 and Nexus 7 2013.
Problem is with stock trebuchet launcher and/or its fonts. I tried rootless pixel launcher from fdroid as a quick and simple test and see no problems with home screen text. Rootless pixel uses a different font though. A future LineageOS update could resolve the problem?
Rootless Pixel Launcher | F-Droid - Free and Open Source Android App Repository
F-Droid is an installable catalogue of FOSS (Free and Open Source Software) applications for the Android platform. The client makes it easy to browse, install, and keep track of updates on your device.
f-droid.org
OR you can use nubianprince's crdroid 10.0 build for this tablet. He used his 9.0 repos and has no problems with fuzzy fonts/text. See
[ROM][SM-T350][UNOFFICIAL][crDroidAndroid-10.0][v6.17][ANDROID 10] Galaxy Tab A 8.0
Finally this thread is back :)
forum.xda-developers.com
OR you can use a fairly recent 16.0 build which doesn't have the problem.
2. The stock Jelly browser crashes a lot. Use a different browser. There's lots of better options that are more stable and reliable than the built in Jelly browser.
3. FM Radio is not support since this device doesn't have the LTE functionality.
4. Stock camera does not take picture on front facing camera. Use open camera instead. I don't know when stock camera was broken, but when I tested the March 7, 2021 build, it doesn't work.
Open Camera | F-Droid - Free and Open Source Android App Repository
Camera App
f-droid.org
5. BOE panel
For people who get black or blank screens when trying to flash TWRP 3.3.1 or LineageOS or crDroid SM-T350 roms, it's likely you have a BOE sourced panel.
Code:
adb root
adb shell cat /proc/cmdline
The very last parameter will be mdss_mdp.panel. If you see BOE anywhere in that string, then you have a BOE panel. For example,
mdss_mdp.panel=1:dsi:0:ss_dsi_panel_S6D7AA0_LSL080AL03_BOE_WXGA:1:none
There is a fix as documented at
[ROM][SM-T350][UNOFFICIAL][crDroidAndroid-10.0][v6.17][ANDROID 10] Galaxy Tab A 8.0
Finally this thread is back :)
forum.xda-developers.com
Thanks/Credits
Thanks to @nubianprince and @lividhen99 for ideas and suggestions on getting this build to work. I used one of nubianprince's repos for this build.
FAQ - I spent hundreds of hours building this rom. The least you can do is spend a few minutes reading everything before posting.
Q1) Does the build work on xyz?
A1) I have no idea. I only have the SM-T350. You can try it on variations, but don't be surprised if you get bootloop or bricked hardware. In addition, I won't build it for the 355 (LTE) version.
Q2) Application xyz doesnt' work. Can you fix it?
A2) I only fix what I use. If you use app xyz and it doesn't work, then try 16.0 or going back to the last rom that worked for you.
Q3) My tablet hangs or crashes with 17.1. This build is slow and buggy. Can you fix it?
A3) Go back to the last working stable rom for you. 17.1 is a work in progress and will have bugs and frequent changes.
Q4) Do you plan to update the rom?
A4) Yes as long as I have high speed Internet, I wil try to release the rom monthly to incorporate the security patches.
Q5) What TWRP should I use?
A6) TWRP 3.3.1 or 3.5.0.9. Get it from
https://forum.xda-developers.com/galaxy-tab-a/development/rom-galaxy-tab-8-0-t4158163
Q6) What is the difference between this rom and crdroid?
A6) Use this rom, crdriod or stock. It's not a popularity contest, so use whatever fits your needs. I only offer this as an option for those who want or need a new rom. Most of the code is the same between this rom and crdroid, however, the way we implemented the fixes might be slightly different. In addition, if there is a bug in this rom, it may not be in crdroid due to coding differences and how it's fixed.
Q7) Can I turn off the on screen navigation keys?
A7) To turn off on screen navigation, go to settings, system, advanced, gestures, system navigation, gesture navigation.
Q8) Can I build this rom? Where are the source and kernel source files?
A8) Yes. I have uploaded the repo diff and roomservice.xml file. The kernel source files are at
Samsung MSM8916 Devices
Samsung MSM8916 Devices has 68 repositories available. Follow their code on GitHub.
github.com
The repo diff is what I changed compared to "stock" msm8916 code. The majority of the repo diff is because there's a bug in 17.1 WiredAccessoryManager.java and I reverted back to the 16.0 code. The bug prevents audio through the headphone jack. See
https://forum.xda-developers.com/showpost.php?p=83445681&postcount=13
Q9) Where can I download this rom?
A9) You can find the 2020 17.1 and 16.0 builds at
Downloads for : Samsung Galaxy Tab A 8.0 | 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.
androidfilehost.com
I'm moving to sourceforge for all 2021 uploads. The main reason is that I would like to see the stats of where this rom is being downloaded from worldwide. All 2020 builds will remain on androidfilehost.
2021 builds found at
retiredtab - Browse /SM-T350/17.1 at SourceForge.net
sourceforge.net
TODO
1. document and upload long list of fixes you need to build 17.1 if you want on your own.Done.
2. mirror nubianprince's repo in case it gets deleted.Done.
3. upload some files, fixes and documentation to github for future.Done.
Dec 13, 2021 release notes
1. Dec 5 security patches as per https://review.lineageos.org/q/topic:Q_asb_2021-12
2. Whatever LiineageOS changed since last November release (about 4,400 files had to be recompiled).
Nov 8, 2021 release notes
1. Nov 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/318647
2. Whatever LiineageOS changed since last October release (about 5,100 files had to be recompiled).
Oct 10, 2021 release notes
1. Oct 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/317410
2. Whatever LiineageOS changed since last Sept release (about 4,700 files had to be recompiled).
Sept 17, 2021 release notes
1. Sept 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/316083
2. Whatever LiineageOS changed since last August release (about 49,500 files had to be recompiled).
Aug 7, 2021 release notes
1. August 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/314572
2. Whatever LiineageOS changed since last July release (about 4500 files had to be recompiled).
July 12, 2021 release notes
1. July 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/313448
2. Whatever LiineageOS changed since last June release (about 4500 files had to be recompiled).
June 15, 2021 release notes
1. June 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/312240
2. Whatever LiineageOS changed since last May release (about 5400 files had to be recompiled).
May 10, 2021 release notes
1. May 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/309564
2. Whatever LiineageOS changed since last April release.
April 12, 2021 release notes
1. April 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/307454
2. Whatever LiineageOS changed since last March release. Nearly 59,000 out of the 70,000 files had to be recompiled due to the last set of changes.
Release notes for March 7, 2021
1. Mar 5 security patches.
2. Whatever LiineageOS changed since last February release.
3. Stock camera does not save picture on front facing camera. Use open camera instead. I don't know when stock camera was broken, but when I tested the March 7, 2021 build, it doesn't work. I never use the camera or video recording on the tablets.
Release notes for Feb 10, 2021
1. Feb 5 security patches.
2. fixed audio over bluetooth. Huge thanks to @nubianprince for helping with suggestions and his repos. The problem was that some of the audio xml files weren't being copied over in 17.1 because of some directory changes to hardware/qcom.
3. Whatever LineageOS changed since last Jan 2021 update.
Release notes for Jan 14, 2021
1. Jan 5 security patches.
2. Changed some error messages to verbose to stop spamming log files.
3. Whatever LineageOS changed since last Dec 2020 update.
4. For some reason after flashing the rom, TWRP 3.3.1 now says "unable to mount storage". I had never seen that before. Nevertheless, if you reboot, the rom will work fine. I test all my builds before uploading.
Release notes for Dec 14, 2020
1. Dec 5 security patches.
2. Changed some error messages to verbose to stop spamming log files.
3. Whatever LineageOS changed since last Nov update.
4. Add timekeep functionality since SM-T350 has no real time clock. This allows the tablet to keep time when not used with a NTP (network time protocol) server. It works in Android OS and TWRP.
Nov 8 release
- Nov 5 security patches
Oct 8 release
- Oct 5 security patches
Sept 13 initial release
- Sept 5 security patches
- initial release for testing and help fixing bugs
- CPU and GPU overclocked to 1.6Ghz and 650 respectively - built into 17.1 kernel code
- based on stock github MSM8916 T350 code with a LOT of bug fixes and using one of nubianprince's repos
Oct 8 build released. See post #4 for changes.
I set the time to Oct 18 but it was changed to Jan 18 after reboot, then October 9. I remember that crdroid have the same issue.
See this logcat:
Code:
01-18 08:52:10.608 680 680 I SystemServer: StartAlarmManagerService
01-18 08:52:10.611 680 680 D AlarmManagerService: Kernel timezone updated to -480 minutes west of GMT
01-18 08:52:10.611 680 680 I AlarmManager: Current time only 1471930611, advancing to build time 1602188073000
01-18 08:52:10.611 680 680 D AlarmManagerService: Setting time of day to sec=1602188073
10-09 04:14:33.001 680 680 W AlarmManagerService: Unable to set rtc to 1602188073: Invalid argument
10-09 04:14:33.006 680 680 D SystemServerTiming: StartAlarmManagerService took to complete: 10ms
Backlight problem is still in my BOE device. I don’t know which logs are necessary, so I kept most of them. The logs about BOEpanel of crdroid are same with Los, but may be different in other places.
Hope it could be solved.
Which TWRP image are you using? I've seen a couple different ones, but since there's no official support over at http://twrp.me/ I'd prefer to use the same one you're using to test this ROM installation...
Hexrotor said:
The logs about BOEpanel of crdroid are same with Los, but may be different in other places.
Click to expand...
Click to collapse
I'll take a look, but right now I have a big project that I need to get finished by mid November so my time for building and troubleshooting roms is limited right now.
reukiodo said:
Which TWRP image are you using?
Click to expand...
Click to collapse
TWRP 3.3.1
Hexrotor said:
The logs about BOEpanel of crdroid are same with Los, but may be different in other places.
Click to expand...
Click to collapse
These messages
D modemanager: Panel Name: S6D7AA0_LSL080AL03_BOE_wxga_video_mode_dsi_panel
E modemanager: readXMLOp:Couldn't open OEM XML file!
E modemanager: retrieveMode: Failed to enumerate modes
E modemanager: instantiateModeMgr: Failed to update default cache!
E modemanager: readXMLOp:Couldn't open OEM XML file!
E modemanager: retrieveMode: Failed to enumerate modes
E modemanager: in applyDefaultMode fail to retrieve default mode!
I modemanager: in applyDefaultMode ret = 0 mCurMode = -1
are from the proprietary module (which is why I couldn't find them in the AOSP code)
system/vendor/lib/libmm-qdcm.so
If you search for those keywords above, they all appear in this module.
At this time, I have no idea what the libmm-qdcm.so does and how it controls the backlight, if at all.
can someone provide link for twrp 3.3.1 for t350? i just can't find it.
spiramedia said:
can someone provide link for twrp 3.3.1 for t350? i just can't find it.
Click to expand...
Click to collapse
From
https://forum.xda-developers.com/galaxy-tab-a/development/rom-galaxy-tab-8-0-t4158163
TWRP 3.3.1 is at
https://drive.google.com/file/d/14T99LQaKtEhGeglFxrUm0kMRw_RKopP5/view
me t350 just shut's down on his own. clean install.
spiramedia said:
me t350 just shut's down on his own. clean install.
Click to expand...
Click to collapse
Works fine for me and others.
@spiramedia Maybe your device is using BOE panel, try to Illuminate the screen with a flashlight.
Hexrotor said:
@spiramedia Maybe your device is using BOE panel, try to Illuminate the screen with a flashlight.
Click to expand...
Click to collapse
mine is BOE. But i have no problem with this. The tablet just shuts down when using it. Maybe it overheats.
spiramedia said:
mine is BOE. But i have no problem with this. The tablet just shuts down when using it. Maybe it overheats.
Click to expand...
Click to collapse
@spiramedia, when asking for help, it helps us if you provide maximum information. For example,
1) What are you running when the tablet shuts down? High performance gaming? Watching youtube?
2) How long does the tablet run before shutting down?
3) Maybe your battery is really old and weak especially if you used it daily for 5 years?
4) If you think it overheats, you can download several CPU apps that tell you the temperature of the CPU like
https://f-droid.org/en/packages/com.kgurgul.cpuinfo/
5) If the battery is old and weak, does it shutdown when you have the AC microusb adapter plugged in all the time?
6) When it shuts down, what is the battery percentage at?
7) Is your battery guage calibrated properly? If it says 30%, maybe it's really 0% and you have to discharge/recharge 2 or 3 times to recalibrate?
As you can see, I asked a lot of questions. The more info you can give, the better.
PS. If you have a BOE panel and backlight works, then I have no idea why my rom works with yours and not Hexrotor.
Hexrotor said:
I set the time to Oct 18 but it was changed to Jan 18 after reboot, then October 9. I remember that crdroid have the same issue.
Click to expand...
Click to collapse
@Hexrotor, does this happen if you date and time setup to "use network provided time".
If I turn "use network provided time" off, then yes, the tablet doesn't keep time properly. I think it's due to the Qualcomm RTC being read only? Searching the Internet, a possible fix might be
https://github.com/LineageOS/android_hardware_sony_timekeep
I might try incorporating that into the next rom build which will likely be sometime mid Nov when the next security patches are released.
I think it's defaulting to Oct 9 because the build date is Oct 8, but in your timezone, it might be Oct 9.
Hexrotor said:
Backlight problem is still in my BOE device. I don’t know which logs are necessary, so I kept most of them.
Click to expand...
Click to collapse
The error messages for the BOE panel are just before the system stops the boot animation and gives the 3 dots and says LineageOS. I find that to be confusing because I would think the kernel would enable BOE backlight at the very beginning so you can see what is on the display. It makes no sense to have the backlight completely dark and then enable it just before the 3 dots that says LineageOS.
And if spiramedia's BOE backlight works with my rom, then I don't know why it doesn't work with yours. Maybe there is something persistent in one of the persist partitions where a prop is set?
Hexrotor said:
Backlight problem is still in my BOE device.
Click to expand...
Click to collapse
@Hexrotor, you didn't specify in this thread or the original crdroid thread whether you tried downgrading the stock to marshmellow and then try crDroid 10 or LineageOS 17.1.
Apparently, it fixes the no backlight for some people? See
https://forum.xda-developers.com/showpost.php?p=83488241&postcount=41
It's possible the marshmallow firmware has something coded into the file system partitions that fixes the BOE? Maybe someting in the aboot partition?
Let me know if you have tried downgrading or not as per above.
retiredtab said:
Apparently, it fixes the no backlight for some people? See
https://forum.xda-developers.com/showpost.php?p=83488241&postcount=41
It's possible the marshmallow firmware has something coded into the file system partitions that fixes the BOE? Maybe someting in the aboot partition?
Let me know if you have tried downgrading or not as per above.
Click to expand...
Click to collapse
Nope, I tried this way but no help. I flashed marshmallow firmware then Crdroid6.9 without clean, it was no display but heated up at boot. I waited for about 10min but it didn't boot complete. Edit: I tried again just now, it booted successfully but still no backlight. Now I'm using official marshmallow.
I don't know why this ROM works with spiramedia's BOE device. I have some friends who have T350/P350 BOE devices and all they have backlight problem with 3-part ROMs, that’s why I am sure that the backlight problem is related to BOE.
For Los 17 and Crdroid, my device has no backlight after the "Samsung Galaxy Tab A", but official marshmallow works fine.
PLEASE BEFORE YOU decide to try this rom, you MUST read all of post 1, 2, 3 and 4 (about 10 minute read). If you think this is an unreasonable request, then stop reading now and find another rom. Thank you.
I am not responsible for lost data, identity theft, lost money, security vulnerabilities, bricked devices or any other hardware or software malfunctions that comes as a result of flashing this rom.
BACKUP YOUR DATA AND OLD rom BEFORE trying my rom.
If you are NOT an expert in using fastboot, adb, odin, heimdall, twrp, DO NOT use this rom. You must know how to use these tools to revert back to your old rom.
If you are new to flashing custom roms, do NOT attempt this.
If you need your tablet for work and something important, do NOT flash this rom. This rom could result in a bricked device or boot loop or non booting device or you not being able to revert back to your old rom.
What works
1. bluetooth
2. wifi
3. brightness
4. external audio
5. GPS
6. audio through headphone jack
7. audio over bluetooth
8. selinux enforcing
9. camera
Thanks
1. LineageOS team for source code.
2. Pre alpha testers for the Samsung Tab A/E roms who provided valuable feedback: lpedia, Schaagi, katochwa, Henrick Grimler
3. nubianprince for helping fix audio over bluetooth on SM-T350 on 18.1.
4. Huge thanks to Henrick Grimler https://github.com/Grimler91 for helping me reproduce a major bug in 18.1 which led me to find a solution. Henrick also helped fine tune some of the sepolicy as well.
5. Sebastiano Barezzi https://github.com/SebaUbuntu for giving the msm8916 repo some 18.1 code updates in March 2021.
6. Exynos5420 team for sharing it's knowledge in building roms.
7. msm8916 team for their repos
8. dylux for suggesting a fix for the front camera photo/record crashing by using stock SM-T350 media_profiles.xml.
FAQ - I spent hundreds of hours building this rom. It was frustrating process from Nov 2020 to March 2021 running into bug after bug. The least you can do is spend a few minutes reading everything before posting.
Q1. Where are the source and kernel source files?
A1. The kernel source files are at
GitHub - Galaxy-MSM8916/android_kernel_samsung_msm8916: MSM8916/MSM8929/MSM8939 kernel for Samsung devices.
MSM8916/MSM8929/MSM8939 kernel for Samsung devices. - GitHub - Galaxy-MSM8916/android_kernel_samsung_msm8916: MSM8916/MSM8929/MSM8939 kernel for Samsung devices.
github.com
The device tree files are at
GitHub - retiredtab/android_device_samsung_msm8916-common: Common MSM8916 tree for Samsung devices
Common MSM8916 tree for Samsung devices. Contribute to retiredtab/android_device_samsung_msm8916-common development by creating an account on GitHub.
github.com
GitHub - retiredtab/device_samsung_gt58wifi
Contribute to retiredtab/device_samsung_gt58wifi development by creating an account on GitHub.
github.com
GitHub - retiredtab/device_samsung_gte-common at lineage-18.1
Contribute to retiredtab/device_samsung_gte-common development by creating an account on GitHub.
github.com
The vendor tree files are at
GitHub - retiredtab/vendor_samsung_msm8916-common
Contribute to retiredtab/vendor_samsung_msm8916-common development by creating an account on GitHub.
github.com
GitHub - retiredtab/android_vendor_samsung_gt58wifi
Contribute to retiredtab/android_vendor_samsung_gt58wifi development by creating an account on GitHub.
github.com
In addition, there is a repo diff file for device specific tweaks needed to work and a roomservice.xml (local manifest file) file so you can build this rom yourself.
Q2. Is this BETA rom suitable as a daily driver?
A2. It can be depending on your requirements. I can't test every app so you try it yourself to see if it's suitable. I've been using this rom myself since mid March 2021 with no major issues.
Q3. What if my app, xyz, doesn't work?
A3. I won't answer questions regarding why your app doesn't work. If your app, whatever it is, doesn't work, then go back to your old rom. It's difficult enough building and maintaining these roms. Remember, I'm an unpaid volunteer making a rom for free for your benefit.
Q4. Your rom is laggy and buggy.
A4. If you find the above, then go back to your old rom. There's only so much software can do on a 2015 budget level tablet. Remember a budget tablet will have the slower SoC/CPU and less DRAM than a top of the line model. Your tablet will also run slower when you use gapps (google apps). You can run a lot of software without using gapps. Research fdroid, newpipe, Aurora store etc.
Q5. What TWRP should I use?
A5. You MUST use TWRP 3.5.2_9. Get it from
[ROM][SM-T350][UNOFFICIAL][crDroidAndroid-11.0][v7.10][ANDROID 11] Galaxy Tab A 8.0
I am not responsible for bricked devices, or any other hardware malfunctions that comes as a result of flashing this ROM, Please do some research if you have any concerns about features included before flashing it, this ROM was built for the...
forum.xda-developers.com
Q6. Why should I use this rom?
A6. You don't. If you don't like this rom, then don't use it. Yes, it's that simple.
Q7. Will you offer monthly updates with security patches?
A7. I will try to offer monthly security patches, but that all depends on if I continue to have high speed Internet in the future.
Q8. Can you help me? I'm a newbie. Can you provide step by step instructions?
A8. Do your own research. There are lots of tutorials, videos, etc on how to flash roms. Newbie questions must be posted in the Questions and Answers forum, not here.
Q9. Can I report a bug with respect to the rom?
A9. Yes, but you need to supply the following information. If you don't, I won't look at it.
You must provide an adb logcat of the problem and tell me how to reproduce it. Note I will not be downloading any apps that require money or an userid/password. For example, if you have problems with Netflix, I cannot help you since I don't have a paid subscription. If you use some app that requires an userid/password, I cannot help you as I'm not willing to create another userid/password even if it's free.
To get a logcat, open up a terminal window.
Code:
# clear the logcat first
adb logcat -c
# start logcat trace
adb logcat > problem.txt
# reproduce problem
# wait until problem has occured, then stop trace by hitting ctrl-c
Q10. Will you still build 17.1 for this device?
A10. Yes, for now, but I will probably discontinue building 17.1 at the end of 2021. I will likely be trying to build 19.0 once it's released so I don't want to maintain 3 releases.
Q11. Do I need to erase everything and format my data?
A11. Yes, you MUST erase all the partitions (system, data, dalvik/art cache, cache) using TWRP and MUST format your data before installing 18.1 when you are coming from stock or an earlier version of LineageOS or from another custom rom. If you get stuck at the boot animation for more than 5 minutes, it's likely because you didn't follow the instructions I just wrote. Dirty flashes from stock, other custom roms or older LineageOS versions are not supported and not likely to work.
Q12. What gapps should I use?
A12. I don't use gapps anymore. I use Aurora Store. As of Nov 6, 2021, I no longer make recommendations on which gapps to use as your mileage may vary. It's reported that opengapps does no testing on their daily builds and some version results in bootloops, bitgapps may run out of disk space will installing apps and Mindthegapps as causing overall slowdown of the system.
The only recommendation I can make is to use the SMALLEST version of gapps which is PICO or equivalent naming convention. DO NOT use anything other than PICO. That is, do not use nano, mini, stock, etc.
If you are going to install gapps, flash the rom first, reboot into system/OS, reboot to recovery, flash gapps, reboot into system/OS. That is, do not flash/install the rom and gapps at the same time.
Q13. I'm having problems with gapps, can you answer why it's not working?
A13. I will not answer any questions regarding gapps. This thread is about the rom, not gapps and I don't use gapps so I cannot help you. Android does not depend on gapps in order to work.
Q14. Why isn't my post answered?
A14. It's probably because it's answered in the FAQ or not relevant to the rom. Again, I do not run Windows OS or use gapps. Questions already answered in the FAQ will be completely ignored.
Q15. Can I turn off the on screen navigation keys?
A15. To turn off on screen navigation, go to settings, system, advanced, gestures, system navigation, gesture navigation. It's enabled by default because I find it useful. If you don't like it, you only need to disable once and your preference will be remembered. If you want to invert the onscreen keys, goto settings, system, buttons and enable invert layout
Q16. What speed up/optimization tips do you suggest?
A16.
1. Turn off animations. Go into developer settings, scroll down to the drawing section, and set window, transition and animator scale all to "off".
2. If you don't have a google account, don't install gapps. Use Aurora Store to get your apps as you can get all the same apps from the play store using an anonymous login.
3. Dont' run more than 2 apps at the same time. You can probably listen to music in the background and use a web browser at the same time, but don't expect great performance from a 2015 entry level tablet.
4. Use a web browser like Brave that has built in adblock and privacy features.
5. Use newpipe to watch your streaming content. It has built in adblock so you don't have to watch forced ads.
6. Look for apps that are open source, ad free and lightweight.
Q17. Does this rom support Magisk?
A17. I don't use Magisk myself so I don't know and Magisk is always being updated to fool Google's certification process. Others have reported Magisk as working, but I won't answer any questions regarding it.
Q18. Will this rom ever become official?
A18. Never. I don't want the responsibilities that come with being an official maintainer. In addition, I know my device trees, code organization and git commits will NOT meet LineageOS standards. Remember, I'm an unpaid volunteer doing this in my free time and sharing my work with you for free so you can get hundreds of hours of enjoyment from this tablet.
Q19. What is the difference between this rom and others?
A19. This rom tries to be pure LineageOS with little to no modifications. Other roms may have different UI, different bundled apps, etc. Use whatever meets your requirements.
Q20. Will there be any major 18.1 code modifications in the future?
A20. I don't anticipate any major modifications. There may be some slight tweaking to the sepolicy, small bug fixes and minor code cleanup, but all the hard work in getting the rom up and running and fixing all the major bugs have been done completed. This doesn't mean the code is perfect or well organized, but I won't be doing any major changes now that 18.1 is working. Any major changes will be done in 19.0.
Q21. Why did you fork the device and vendor trees for 18.1?
A21. The msm8916 repos seem geared towards phones and sometimes do not work or cause boot animation loops for tablets so I decided to fork their repos. In other words, what's deemed as msm8916-common code isn't common to all devices.
In addition, since I'm building SM-T350, SM-T550, SM-P550 and SM-T560NU (all use the same msm8916 code), it seems easier to maintain all of them if I can control my own code repos and not worry if my changes affects the phones or not. I still have not figured out the best way to manage all my repos and it's a work in progress.
Q22. Can you build a variant of this device? For example, a LTE or S-pen version.
A22. If I don't physically have the device, I cannot and will not build it unless I can boot and test it myself. Even then, there's no guarantee that I can get those variant features working.
Q23. Can I load this rom on a variant devivce like LTE or S-pen version?
A23. The rom is built for the device explicitly listed. If you are an advanced user and understand TWRP, adb, odin, heimdall, you can try loading it on a LTE or S-pen variant by modifying the updater-script, but it may cause a bricked device, bootloops or non functionality of LTE/S-pen. You have been informed and warned!
Q24. Will this run on the SM-T355 or SM-P355?
A24. No. Someone has tried and it will result in a bootloop.
Q25. How do I know if I have a BOE panel?
A25. Some ST-350 tablets have a BOE display panel. In order for it to work with TWRP and any custom rom, you must have the correct bootloader installed on a BOE panel otherwise you will see a black/blank screen. To check to see if you have a BOE panel, open a terminal and
Code:
adb root
adb shell cat /proc/cmdline
The very last parameter will be mdss_mdp.panel. If you see BOE anywhere in that string, then you have a BOE panel. For example,
mdss_mdp.panel=1:dsi:0:ss_dsi_panel_S6D7AA0_LSL080AL03_BOE_WXGA:1:none
There is a fix as documented at
[ROM][SM-T350][UNOFFICIAL][crDroidAndroid-10.0][v6.17][ANDROID 10] Galaxy Tab A 8.0
Finally this thread is back :)
forum.xda-developers.com
Q26. What is a GO build?
A26. A GO build uses less DRAM, disk space and supposed to be better suited for devices with 2GB DRAM or less. I have no idea whether it's true or not vs a NON GO build, but I figured I would try a GO build.
Some of the features removed in a GO build are documented in post #46 in this thread in addition to work profiles. If you need these features, you can edit a property in the build.prop as documented in post #49.
Q27. Okay, I understand the consequences and that this is BETA rom and willing to take the risks outlined, now where can I find the rom?
A27. Downloads are at
retiredtab - Browse /SM-T350/18.1 at SourceForge.net
sourceforge.net
NOTE: All builds that I upload have been personally tested on my device to boot and function as described in post #1. Having said that, there's still a chance it won't work on your device due to human error, your configuration, your apps, etc. If it won't boot, always start with a complete wipe of everything and format your data. This is known has a clean install. Backup your data before a clean install.
June 9, 2023 release notes
1. June 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2023-06
2. Whatever LineageOS changed since last May release (about 5,500 files had to be recompiled).
May 7, 2023 release notes
1. May 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2023-05
2. Whatever LineageOS changed since last Apr release (about 7,200 files had to be recompiled).
Apr 15, 2023 release notes
1. Apr 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2023-04
2. Whatever LineageOS changed since last Mar release (about 28,000 files had to be recompiled).
March 20, 2023 release notes
1. Mar 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2023-03
2. Whatever LineageOS changed since last Feb release (about 20,000 files had to be recompiled).
Feb 12, 2023 release notes
1. Feb 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2023-02
2. Whatever LineageOS changed since last Jan release (about 12,500 files had to be recompiled).
Jan 8, 2023 release notes
1. Jan 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2023-01
2. Whatever LineageOS changed since last Dec release (about 4,400 files had to be recompiled).
Dec 11, 2022 release notes
1. Dec 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-12
2. Whatever LineageOS changed since last Nov release (about 5,000 files had to be recompiled).
Nov 11, 2022 release notes
1. Nov 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-11
2. Whatever LineageOS changed since last Oct release (about 5,000 files had to be recompiled).
Oct 7, 2022 release notes
1. Oct 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-10
2. Whatever LineageOS changed since last Sept release (about 5,500 files had to be recompiled).
Sept 12, 2022 release notes
1. Sept 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-09
2. Whatever LineageOS changed since last Aug release (about 12,500 files had to be recompiled).
Aug 5, 2022 release notes
1. Aug 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-08
2. Whatever LineageOS changed since last July release (about 4,000 files had to be recompiled).
July 8, 2022 release notes
1. July 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-07
2. Whatever LineageOS changed since last June release (about 1,500 files had to be recompiled).
June 11, 2022 release notes
1. June 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-06
2. Whatever LineageOS changed since last May release (about 9,500 files had to be recompiled).
May 7, 2022 release notes
1. May 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-05
2. Whatever LineageOS changed since last April release (about 11,000 files had to be recompiled).
3. Selfie camera and video no longer crash with stock camera. Thanks to @dylux for suggesting these fixes which are commits
https://github.com/retiredtab/devic...mmit/c9ac11147f83d611e006731aad7c14108f293d64
and
https://github.com/retiredtab/devic...mmit/cfa55e0478b59821f3d16501104b51ceeef8b010
April 10, 2022 release notes
1. Arpil 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-04
2. Whatever LineageOS changed since last March release (about 11,000 files had to be recompiled).
Mar 12, 2022 release notes
1. Mar 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-03
2. Whatever LineageOS changed since last Feb release (about 5,700 files had to be recompiled).
Feb 12, 2022 release notes
1. Feb 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-02
2. Whatever LineageOS changed since last January release (about 34,500 files had to be recompiled).
Jan 20, 2022 release notes
1. Jan 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2022-01
2. Whatever LineageOS changed since last December release (about 10,000 files had to be recompiled).
Dec 10 release notes
1. Dec 5 security patches as per https://review.lineageos.org/q/topic:R_asb_2021-12
2. Whatever LineageOS changed since last November release (about 11,000 files had to be recompiled).
Nov 7 release notes
1. Nov 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/318560
2. I enabled zram swap with size 512MB. I noticed that the last couple of months that Clash Royale would crash/close and logs showed
Code:
10-28 14:26:01.412 0 0 I [2: kswapd0: 91] lowmemorykiller: Killing 'ell.clashroyale' (6730), adj 0,
Hopefully, by enabling zram, that will stop Clash Royale from crashing/closing.
Zswap is enabled on stock Nougat SM-T350 (part of the Samsung Tab A/E family that uses same msm8916 kernel code)
https://github.com/retiredtab/andro...mmit/2a6bf385e6dfe6073fe328b7b1c563ccd60a5ede
https://github.com/retiredtab/andro...mmit/438d5d3ad20cbc98f0f8c18eb610b6268de19395
This code uses the in kernel low memory killer (lmk). I tried using the Android OS lmk, but it doesn't work very well and shows this in the log.
Code:
E lowmemorykiller: /proc/zoneinfo parse error
E lowmemorykiller: Failed to get free memory!
3. Whatever LineageOS changed since last Oct release (about 7,200 files had to be recompiled). One of these changes has removed the built in terminal program from LineageOS as AOSP deprecated this app as per
https://review.lineageos.org/c/LineageOS/android_vendor_lineage/+/304043
Oct 10 release notes
1. Oct 1 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/317001
2. Added https://review.lineageos.org/c/LineageOS/android_frameworks_base/+/316839 to fix landscape mode system UI. This patch is not yet officially merged as of Oct 10 release.
3. Whatever LineageOS changed since last September release (about 6,100 files had to be recompiled).
Sept 10 release notes
1. Reverted the patch to https://github.com/retiredtab/andro...mmit/a32c7a0bed536281d20b7c1cf8d41c84a268cc80
Removing systemUI from pinner services causes a 4 to 6 delay in bringing up the home screen. This is seen when loading or playing a game for about 20 minutes and then either hitting the recents or home button. By reverting this commit, pressing recents or home button brings up the systemUI right away.
2. Sept 5 security patches as per https://review.lineageos.org/c/LineageOS/android/+/315661
3. Whatever LineageOS changed since last August release (about 6,200 files had to be recompiled).
Aug 8 release notes
1. Fix battery status icon. When you plug in AC adapter, settings, battery does not show it charging even though it is. This is due to the sepolicy being too restrictive. I added https://github.com/retiredtab/msm89...mmit/c1eca9f7740b6a384d4fab8a1e8d812f59c17a99
2. Aug 5 security patches as per https://review.lineageos.org/c/LineageOS/android/+/314477
3. Whatever LineageOS changed since last July release (about 11,500 files had to be recompiled).
4. 18.1 continues to be my daily driver since March 2021.
July 10 release notes
1. Initial public release to XDA. This is an ALPHA build.
2. July 5 security patches as per https://review.lineageos.org/q/topic:"android-11.0.0_r39"+(statuspen OR status:merged)
Reserved.
New build called lineage-18.1-20210718-UNOFFICIAL-gt58wifi.zip
July 18 release notes
1. Fix battery status icon. When you plug in AC adapter, settings, battery does not show it charging even though it is. This is due to the sepolicy being too restrictive. I added
Code:
allow hal_health_default sysfs_charger:dir search;
allow hal_health_default sysfs_charger:file r_file_perms;
to the hal_health_default.te file.
Other than that, there are no other changes. So if you already downloaded the July 10 release and don't mind this small bug, you can wait until the August security patches before updating the rom. The August security patches and all future versions will have this bug fix incorporated.
New build called lineage-18.1-20210808-UNOFFICIAL-gt58wifi.zip
Aug 8 release notes
1. Fix battery status icon. When you plug in AC adapter, settings, battery does not show it charging even though it is. This is due to the sepolicy being too restrictive. I added https://github.com/retiredtab/msm89...mmit/c1eca9f7740b6a384d4fab8a1e8d812f59c17a99
2. Aug 5 security patches as per https://review.lineageos.org/c/LineageOS/android/+/314477
3. Whatever LiineageOS changed since last July release (about 11,500 files had to be recompiled).
4. 18.1 continues to be my daily driver since March 2021.
@retiredtab
Thanks for your work on this rom. It's been working very well.
It seems BiTGApps can no longer be downloaded.
ovalseven said:
It seems BiTGApps can no longer be downloaded.
Click to expand...
Click to collapse
Use opengapps then. Remember, this is not the correct place to ask gapps related questions. It's only for the rom. This will be the last time I mention gapps.
FAQ 13
Q13. I'm having problems with gapps, can you answer why it's not working?
A13. I will not answer any questions regarding gapps. This thread is about the rom, not gapps and I don't use gapps so I cannot help you. Android does not depend on gapps in order to work.
retiredtab said:
Q15. Can I turn off the on screen navigation keys?
Click to expand...
Click to collapse
Is there any way to swap the button positions to match the order of the hardware buttons (back button on the right)?
retiredtab said:
Use opengapps then. Remember, this is not the correct place to ask gapps related questions. It's only for the rom. This will be the last time I mention gapps.
FAQ 13
Q13. I'm having problems with gapps, can you answer why it's not working?
A13. I will not answer any questions regarding gapps. This thread is about the rom, not gapps and I don't use gapps so I cannot help you. Android does not depend on gapps in order to work.
Click to expand...
Click to collapse
I was just letting you know your links didn't work.
ovalseven said:
Is there any way to swap the button positions to match the order of the hardware buttons (back button on the right)?
I was just letting you know your links didn't work.
Click to expand...
Click to collapse
@ovalseven, the link in this thread's FAQ still works (for me, anyway) but the download link on that BiTGapps site appears not to be working. The BiTGapps thread [CUSTOM][GAPPS] BiTGApps for Android might have more information / an alternative download site.
ovalseven said:
Is there any way to swap the button positions to match the order of the hardware buttons (back button on the right)?
Click to expand...
Click to collapse
Now added to FAQ.
If you want to invert the onscreen keys, goto settings, system, buttons and enable invert layout
Thanks for the info and for your work on this rom. Been using it all afternoon and it's running smoothly.
lpedia said:
@ovalseven, the link in this thread's FAQ still works (for me, anyway) but the download link on that BiTGapps site appears not to be working. The BiTGapps thread [CUSTOM][GAPPS] BiTGApps for Android might have more information / an alternative download site.
Click to expand...
Click to collapse
Thanks to @lpedia letting me know, but it seems the developer of bitgapps has removed his links because of some "disagreement" with some users. I'm not involved in this and don't want to be, but if people want bitgapps, they should check the link daily to see when/if the developer will re-enable his links.
So I have now removed all gapps links from my FAQ and it's up to the user now to use their favourite search engine to find whatever gapps or Aurora Store they want. And THIS will be the FINAL word I say on gapps again.
New build called lineage-18.1-20210910-UNOFFICIAL-gt58wifi.zip
NOTE: All builds that I upload have been personally tested on my device to boot and function as described in post #1. Having said that, there's still a chance it won't work on your device due to human error, your configuration, your apps, etc. If it won't boot, always start with a complete wipe of everything and format your data. This is known has a clean install. Backup your data before a clean install.
18.1 continues to be my daily driver since March 2021.
Sept 10 release notes
1. Reverted the patch to https://github.com/retiredtab/andro...mmit/a32c7a0bed536281d20b7c1cf8d41c84a268cc80
Removing systemUI from pinner services causes a 4 to 6 delay in bringing up the home screen. This is seen when loading or playing a game for about 20 minutes and then either hitting the recents or home button. By reverting this commit, pressing recents or home button brings up the systemUI right away.
2. Sept 5 security patches as per https://review.lineageos.org/c/LineageOS/android/+/315661
3. Whatever LiineageOS changed since last August release (about 6,200 files had to be recompiled).
This rom runs fantastic to anyone wondering. Easily the best running rom for t350 (i've tried them all). Thank you for your work on this.
Wikdclown said:
This rom runs fantastic to anyone wondering. Easily the best running rom for t350 (i've tried them all). Thank you for your work on this.
Click to expand...
Click to collapse
I totally agree with you! I just installed the Sept. 10th version on the 10th and it has made my tablet usable again. I will be sticking with this ROM from now on!
The ROM works very well, thank you @retiredtab !
All essential functionality works without caveats. Experimented with enabling pip and split screen and went back to this rom's default setting of being a "low memory" device, as it runs *much* smoother. Good choice of rom's default.
I ran into a couple of crashes in non-essential areas (setting a certain wallpaper crashed the settings, but then worked after reboot; turning on the hotspot then turning it off crashed settings, yet that was a pure curiosity, since there is no utility in the hotspot).
Have a question, pls. How to enable "Phone Ringtone" selection on the "Sound" page in Settings? Something in build.prop? [I use google voice as the voip app on other wifi-only tabs with same lineage version, works well, ringtone selection is there, just need to enable it in the rom for this t350 tab somehow].
Yxo 6o6uka said:
Have a question, pls. How to enable "Phone Ringtone" selection on the "Sound" page in Settings? Something in build.prop? [I use google voice as the voip app on other wifi-only tabs with same lineage version, works well, ringtone selection is there, just need to enable it in the rom for this t350 tab somehow].
Click to expand...
Click to collapse
Which wifi-only tabs give you that ringtone selection? I checked all my wifi 18.1 tablets msm8916 family, exynos 5420 and 5433 and none of them show the phone ringtone selection.
Samsung Tab Pro 8.4 SM-T320. Rom by Valera1978.