Hello all,
Thanks to the LineageOS-developers and @brunogroa, this is my build containing the June-2023 security patches.
Ever since Broly's help in setting up, I've been building this ROM and have used it for several months.
I plan to keep this build updated with the monthly security patches, for as long as LineageOS supports Android 11. Only the last build will be available for download; I'll keep this post as up-to-date as possible.
Update: OTA
Since the 2022-10-22 build, there is an OTA updater included in this ROM. It asks my download server for an updated build - just like in the official LineageOS. Don't forget to set it to check every month (see Settings / System / Updater). It will download and install automatically; make sure you have a compatible recovery installed (preferably TWRP, see Links below).
Download
zip: lineage-18.1-20230611-UNOFFICIAL-ali.zip (mirror)
zip.sha256sum: lineage-18.1-20230611-UNOFFICIAL-ali.zip.sha256sum (mirror)
zip.sha256sum.asc: lineage-18.1-20230611-UNOFFICIAL-ali.zip.sha256sum.asc (mirror)
(the GPG signature can be verified by downloading my personal GPG-key)
Included/additional features
FM radio
Moto fingerprint gestures
Signed with my personal Android key
(see LineageOS' documentation on signing and verifying)
Known bugs
None, so far
Links
TWRP 64bit custom recovery
OpenGapps ARM64, 11.0, at least pico
Telegram group for support by the community, download links and more
Sources
Recent changes: LineageOS 18.1
Kernel tree: see roomservice.xml below
Device tree: see roomservice.xml below
Vendor tree: see roomservice.xml below
roomservice.xml for building it yourself:
XML:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<!-- Kernel -->
<project name="brunorolak/kernel_motorola_msm8953" path="kernel/motorola/msm8953" remote="github" revision="11.0" />
<!-- Device tree -->
<project name="fwiep/device_motorola_msm8953-common" path="device/motorola/msm8953-common" remote="github" revision="lineage-18.1" />
<project name="fwiep/device_motorola_ali" path="device/motorola/ali" remote="github" revision="11.0" />
<!-- Vendor tree -->
<project name="brunorolak/vendor_motorola_msm8953-common" path="vendor/motorola/msm8953-common" remote="github" revision="11.0" />
<project name="brunorolak/vendor_motorola_ali" path="vendor/motorola/ali" remote="github" revision="11.0" />
<!-- Miscellaneous stuff -->
<project name="LineageOS/android_system_qcom" path="system/qcom" remote="github" revision="lineage-18.1" />
<project name="PixelExperience/packages_resources_devicesettings-custom" path="packages/resources/devicesettings-custom" remote="github" revision="eleven" />
<!-- Override LineageOS's Updater package -->
<remove-project name="LineageOS/android_packages_apps_Updater" />
<project name="fwiep/android_packages_apps_Updater" path="packages/apps/Updater" revision="lineage-18.1" />
</manifest>
Kind regards, see you next month,
FWieP
Installed a few days ago. So far, everything is working well.
The only issue I've noticed is that the phone only charges slowly, no matter what charger I use.
JasonMaggini said:
The only issue I've noticed is that the phone only charges slowly, no matter what charger I use.
Click to expand...
Click to collapse
I've had this issue myself - eventually, it seemed not related to the ROM I used, but to the dirt and dust inside the USB-connector.
I had to clean it with a narrow toothpick. I carry the phone inside my pocket, and it collects loads of dust. Both the USB- and jack-connectors were full of the stuff.
I wish you good luck, kind regards,
FWieP
Unfortunately I don't think this is the case. The phone was fast charging with the stock ROM right before I reflashed. I've cleaned the port, but the problem persists.
JasonMaggini said:
Unfortunately I don't think this is the case. The phone was fast charging with the stock ROM right before I reflashed. I've cleaned the port, but the problem persists.
Click to expand...
Click to collapse
just a visual problem.... since A11... and, have battery protector, after some %... you will see your phone charge from 0 to 80% very fast and afeter it slow.. is normal
I installed this build of LOS a couple of weeks ago and ever since last saturday it keeps freezing on me (SystemUI crashes and brings the system down with it) and eventually corrupts the /data partition forcing me to format the partition. Works perfectly for a couple of days, starts crashing once again, and pop goes /data. Any clue as to what it might be? Cheers, and thanks for the bang up job you've been doing.
flmalegre said:
I installed this build of LOS a couple of weeks ago and ever since last saturday it keeps freezing on me (SystemUI crashes and brings the system down with it) and eventually corrupts the /data partition forcing me to format the partition. Works perfectly for a couple of days, starts crashing once again, and pop goes /data. Any clue as to what it might be? Cheers, and thanks for the bang up job you've been doing.
Click to expand...
Click to collapse
This sounds pretty serious. I have never heard about such a situation - and have not experienced it using any LOS build. Could perhaps an installed/updated app be responsible?
Perhaps a logcat could shed some light on the situation. But only if the hang/crash happens while you are collecting the log.
enable developer options
enable USB-debugging
connect via USB to a computer with adb installed
run adb logcat
The log is then printed to your STDOUT. You can pipe it to a file, or directly write it to a file with -f thelogfile.txt as a parameter.
I hope this can be resolved. Are there any other readers having this same issue?
Kind regards,
FWieP
As of right now I'm on my 3rd reinstall. I have followed Bruno's advice on another thread and went big on the formatting this time and included wiping /system, and /vendor. Here's hoping it works or at least lets me get a proper logcat out of it.
Edit: Ah, sorry, it was your advice! My bad.
flmalegre said:
I have followed Bruno's advice on another thread ... Edit: Ah, sorry, it was your advice! My bad.
Click to expand...
Click to collapse
It might as well have been @brunogroa 's advice; he is an expert and developer who shares his knowledge when asked. Most if not all credits go to him .
Kind regards,
FWieP
Quick update: It keeps freezing randomly when not in active usage. Still no filesystem issues to report. Gonna try and run an adb logcat immediately after the next crash.
Belated update: after checking the ANR logs and running top for a while, I realized that kswapd gets incredibly cycle hungry after a while (over 75%!) and realized that my system may actually lock up due to it running out of memory. Why does it happen only when I'm -not- using it? It's a mystery.
After setting the memory management to be a bit more agressive with background apps I'm happy to say that I've only seen a single reboot in over two weeks! (XT1925-2, 3GB RAM in case anyone wants to know)
What's the proposed method of updating with monthly builds?
Just dl new build.zip > run twrp recovery > install build.zip?
Should I worry about data?
fwiep said:
I plan to keep this build updated with the monthly security patches, for as long as LineageOS supports Android 11.
Only the last build will be available for download; I'll keep this post as up-to-date as possible.
Click to expand...
Click to collapse
Any steps toward making your builds into official los repo?
Can't say that OTA updates are very comfortable
YoShake said:
What's the proposed method of updating with monthly builds?
Just dl new build.zip > run twrp recovery > install build.zip?
Should I worry about data?
Any steps toward making your builds into official los repo?
Can't say that OTA updates are very comfortable
Click to expand...
Click to collapse
That's what I did, no problems so far. (I did do a nandroid backup and a Migrate backup like the paranoid little bastard I am before hand)
YoShake said:
What's the proposed method of updating with monthly builds? Just dl new build.zip > run twrp recovery > install build.zip? Should I worry about data?
Click to expand...
Click to collapse
Yes, this is the recommended way to update.
Download the ZIP and SHA256SUM
verify the checksum
reboot to TWRP (make sure it's the most recent 64bit recovery)
copy-and-flash the ZIP (or use adb sideload if you prefer)
flash any gapps immediately after, before the first reboot
clear cache and Dalvik cache
reboot to system
This method has worked flawlessly for me when I used the LineageOS 18.1 builds myself.
These days, I use a self built LineageOS 19.1 as daily driver; using the same procedure upon each update.
YoShake said:
Any steps toward making your builds into official los repo?
Click to expand...
Click to collapse
No, I think not. Providing two separate builds for the G6 each month feels as quite a big responsibility on its own. Having to live up to the (valid) expectations of being an official maintainer would be too much for me. I'm just a happy human buildbot, not a core developer.
Hope this helps, kind regards,
FWieP
Hello all,
From the 2022-10-22 build on, there is an OTA updater included in this ROM. It can check periodically for an updated build (see Settings / System / Updater). If you have a compatible recovery installed (as you should have TWRP from the OP), it installs fully automatic after download.
In other words: if you install this ROM, next month you will not have to scout XDA or Telegram for updates. They will be available to your device directly.
Tested on my LineageOS 19.1 build, but if things don't work as expected, please let me know.
Kind regards, see you next month,
FWieP
I just installed this a couple days ago. Wiped old rom and flashed just this no gapps.
Very snappy. Runs way smoother than the android 12 rom I tried previously. Think I'm gonna stick
with this until I decide to retire the phone. Thanks for doing this and hopefully the updates will keep coming.
My G6 has mic problems with this ROM - possibly gain settings?
Occurs with calls using phone dialer, signal, google voice. Didn't test any other mic-using apps like a recorder.
In handset mode mic is inaudible unless you pretty much jam it into your mouth, and then it's audible but distorted. In speakerphone mode volume is OK at normal handset distance, but does not work at speakerphone distance.
It was like this with the November version, and the same with the Jan version. ROM installed after a complete format+wipe.
Switched back to the crDroid 11.0 ROM and mic is fine. Mic is also fine in all the 12.1 ROMs.
VenkmanP said:
My G6 has mic problems with this ROM - possibly gain settings?
Click to expand...
Click to collapse
Hi,
Thanks for pointing this out. Together with the G6, I have built LOS18.1 regularly for the Samsung SM-G920F (zerofltexx). Since the most recent build, those users have suddenly got microphone problems, too.
So, it might be some upstream LOS18 issue..? I have no idea.
I'll try to investigate, keep an eye on the official logs and hope that a new build will fix those issues for you (and all others).
Kind regards,
FWieP
I'm having a problem with the google wallet on this ROM: basically, the Google Wallet gets replaced by Google Pay (defunct).
What in the hells name could be doing that ?
I first thought it was Gapps (only pico fits on /system) to blame, then I created a thread about it, but I'm a little on a hurry (I use NFC a lot) and not hopeful that an answer will come on That forum.
If no solution pops soon, I'll have to revert to Android 9
Latest Magisk (Shamiko, MagiskHide Props Config, UniversalSafetynetFix)
Latest LSPosed (HiddenCore Module)
Forgot to mention: I have a Galaxy S7 with this lineage 18.1. Wallet works there with the same modules (and it's wallet, not Pay)
---------------------------------------------------
Big fckn update:
Seems like all of this is NORMAL.
For some reason, on THIS VERY ROM, the google Pay takes precedence over the Wallet.
After some fighting, the app is back at work. No root detected.
On an official 18.1 (I have it on a Samsung), the actual Wallet takes precedence.
----------------------------------------------
Since I'm here, I'll feedback about the ROM overall.
- I REALLY miss the 3-finger screengrab
- I'm also a victim of the erratic battery value;
- Sometimes apps hang where they didn't use to, and I have to force close them. Especially when the keyboard is involved. Even a simple notepad hangs;
- The wifi doesn't connect automatically sometimes: I have to bring it down and select my SSID.
- The phone app hangs for a moment when I try to answer a call. That one is crytical;
- The screen rotation re-enables itself on every reboot. Also, it's very aggressive and overrides my third parties;
- Poor multitasking. It kills my apps.
- A11 removed SDCard access, but this ""can"" be overriden by using the NoStorageRestrict module;
- So many system mandatory notifications that I can't get rid of !
- I'm still struggling a lot to have back the vertical recent apps list. Begging for help.
Don't know which of these problems are due to the porting, IF ANY... But I'm not sticking to this ROM here. Definetely. Too many patches to fix the disgusting stupidities google is making with this OS
Thanks for the February update. Rom working flawlessly.
Related
The Unlegacy Android ProjectIntroduction
Unlegacy-Android started out as the OMAP4-AOSP Project. It was created in late 2015 in order to maintain a clean and organized place for pure AOSP support for various OMAP4 devices, such as the Galaxy Nexus and the Samsung Galaxy Tab 2 series. Over time this evolved to support more than just these devices, but still maintains its roots of supporting "legacy" devices that no longer receive "official" updates: hence Unlegacy Android was born. In our opinion, these ROMs are how the official updates would look.
On top of AOSP, we only include changes which are necessary to support the hardware, be secure, and get acceptable performance. Current features for flo/deb include:
- Linux kernel 3.4.y merged in (currently 3.4.108 - mostly security patches and minor bug fixes)
- BFQ IO scheduler (official kernel 3.4 release), set up so GUI processes have the highest priority
- F2FS support from kernel 4.9 (for /data only!)
- SELinux in Enforcing mode
Installation
If you're planning to install GApps, be sure to read the second post!
Aside from these, installation and upgrading is no different than on other ROMs.
Problems
- No known issues for flo/deb yet.
If you notice anything, be sure to report it in this thread. Stability is our main concern. While I'm kind of busy, I usually read the thread and acknowledge the bug reports, even if I don't reply directly to them.
Downloads
See: http://builds.unlegacy-android.org. Our automated builds ensure that we always have the latest Android security patches merged in, without having to manually start and upload builds
We will have a built-in OTA updater (just like stock) soon (it's a work in progress)
Information about our experimental builds and progress you may find here.
Features?
There isn't much to say here - this is AOSP, if you install GApps, you pretty much get the same thing that's running on the Nexus devices (see the second post). The aim of this project is to create a fast and stable ROM - although, one could use Xposed to add extra features.
As usual, feedback is appreciated
XDA:DevDB Information
Unlegacy Android Project, ROM for the Nexus 7 (2013)
Contributors
Ziyan, Clamor
Source Code: https://github.com/Unlegacy-Android
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.4.x
Version Information
Status: Stable
Current Stable Version: 8.1
Stable Release Date: 2017-03-24
Created 2017-03-24
Last Updated 2019-04-05
Reserved
GApps
If you want to install GApps, we recommend Open GApps Micro.
An important note: as this is a pure AOSP ROM, installing GApps tends to be problematic: in order to try to avoid installation issues, be sure to install GApps immediately after installing the ROM, before booting the system for the first time. If you experience any issues with the Google applications, be sure to go into Settings -> Apps, and grant every permission to every Google application - most importantly, Google Play services.
In the case of an upgrade, be sure to re-install the GApps package, as upgrading wipes /system. You shouldn't need to re-set the permissions afterwards.
Stock-like setup
Disable the following built-in (AOSP) apps:
- Android keyboard (once you installed Gboard)
- Browser
- Calculator
- Camera
- Clock
- Email
- Gallery
Install the following apps from the Play store:
- Google Photos (https://play.google.com/store/apps/details?id=com.google.android.apps.photos)
- Calculator (https://play.google.com/store/apps/details?id=com.google.android.calculator)
- Chrome (https://play.google.com/store/apps/details?id=com.android.chrome)
- Clock (https://play.google.com/store/apps/details?id=com.google.android.deskclock)
- Gboard (https://play.google.com/store/apps/details?id=com.google.android.inputmethod.latin)
- Gmail (https://play.google.com/store/apps/details?id=com.google.android.gm)
- Google Calendar (https://play.google.com/store/apps/details?id=com.google.android.calendar)
- Google Camera (https://play.google.com/store/apps/details?id=com.google.android.GoogleCamera)
- Google Now Launcher (https://play.google.com/store/apps/details?id=com.google.android.launcher)
SafetyNet
The ROM should pass SafetyNet after installing GApps, without anything else. Keep in mind that installing extra stuff (SU, ...) might make it fail!
Rooting
You can flash the latest Magisk to get rooted.
Hello)
Please add a night mode, with the icon in the blind
boom1982 said:
Hello)
Please add a night mode, with the icon in the blind
Click to expand...
Click to collapse
I simply use Darker for night time playing in the bed personally, I reduce brightness to 65% and apply a slight yellow tint. When most websites are white, theming the framework wouldn't matter that much anyways... and we kinda want to feel like a factory image (no dark mode in them either)
@Ziyan
It's a pity)
The rom itself works fine. Good job)
@Ziyan Thanks for your efforts on these older devices. I've used your work on both Gtab 2 and Grouper before I sold them. I just downloaded 0324 builds for Flo and Hammerhead, neither one matched the MD5. I just downloaded Flo again but still no match. I haven't tried flashing any of the roms yet but figured I'd let you know.
Also, don't know if you use Netflix but it's been a problem getting a current version of the app working properly on ANY Nougat rom for Flo. Without any modifications, the Netflix app will load and give you an option to download and watch at a later time. However, if you try to just do a normal streaming of a movie or show, it will give you an error 0013. As is mostly the history of Netflix, it appears to be a drm issue. @Startrek852 was able to compile a zip with drmblobs that will eliminate the error 0013 and allow normal streaming but you lose the ability to download and watch at a later time. Although I don't use Google Movies, it's my understanding that it will not work if you flash the drmblobs.
Anyway, just wondering if "in your travels" you've heard of this Netflix issue and might possibly know of a proper fix. Thanks again.
Mike T
webdroidmt said:
I just downloaded 0324 builds for Flo and Hammerhead, neither one matched the MD5. I just downloaded Flo again but still no match.
Click to expand...
Click to collapse
This issue seems to haunt us... We'll try looking into it again ASAP. Oddly enough, every time I download, I get a match, and it flashes perfectly
webdroidmt said:
Also, don't know if you use Netflix but it's been a problem getting a current version of the app working properly on ANY Nougat rom for Flo. Without any modifications, the Netflix app will load and give you an option to download and watch at a later time. However, if you try to just do a normal streaming of a movie or show, it will give you an error 0013. As is mostly the history of Netflix, it appears to be a drm issue. @Startrek852 was able to compile a zip with drmblobs that will eliminate the error 0013 and allow normal streaming but you lose the ability to download and watch at a later time. Although I don't use Google Movies, it's my understanding that it will not work if you flash the drmblobs.
Click to expand...
Click to collapse
Play Movies works perfectly, so I'm not sure how to debug that either ways - can look into that zip later on.
Ziyan said:
This issue seems to haunt us... We'll try looking into it again ASAP. Oddly enough, every time I download, I get a match, and it flashes perfectly
Play Movies works perfectly, so I'm not sure how to debug that either ways - can look into that zip later on.
Click to expand...
Click to collapse
Thanks for your reply. Here's the D/L for the drmblobs zip if you decide to take a look. https://www.androidfilehost.com/?fid=529152257862690585
Very weird on the MD5 thing, as mentioned I downloaded it twice and on a desktop PC so it shouldn't be a mobile issue??? I'm gonna' flash it later, will report if there's a problem.
Mike T
@Ziyan
Updates come out every day ...?)
And why the cache is not f2fs?
I'm sorry that there are a lot of questions. I just made this rom basic and I want to figure it all out
p.s. That there were no problems with gapps - you need to restart the recovery after flashing the main rom
have volume wake option?
edit: stuck at "patch image "Patching system image unconditionally..."
boom1982 said:
@Ziyan
Updates come out every day ...?)
And why the cache is not f2fs?
I'm sorry that there are a lot of questions. I just made this rom basic and I want to figure it all out
p.s. That there were no problems with gapps - you need to restart the recovery after flashing the main rom
Click to expand...
Click to collapse
Our little build server likes overdoing its job and building even if the changes don't affect flo - until this is fixed, it's enough to update every 3-4 weeks or so to get the security updates, unless I make an announcement here about a change
About /cache f2fs: there's simply no point, as that partition isn't actively used by the system (other than maybe OTA updates). I usually don't support it, as it can lead to more complications than what it worth...
@Ziyan
Thank you for your reply)
I really like the way the rom works.
Only have to use a lot of additional tools to at least somehow expand the settings)))
Good work... but video recording with green lines in Google Camera 3.2, stock kernel, Nexus 5
Dear author when will you fix problems with wi fi? Wi fi does not catch nexus 5 networks
Mayrbek86 said:
Dear author when will you fix problems with wi fi? Wi fi does not catch nexus 5 networks
Click to expand...
Click to collapse
Mind giving me a bit more details regarding this? I can connect to a Wi-Fi Hotspot created with my Nexus 4 (also running Unlegacy Android 7.1) just fine, and can browse the internet with the Nexus 7 through it (mobile data activated on the Nexus 4)
Mayrbek86 said:
Dear author when will you fix problems with wi fi? Wi fi does not catch nexus 5 networks
Click to expand...
Click to collapse
Installed Build "ua_hammerhead-7.1.1-20170328", Wi-Fi also does not work. I had to install wifi-fix, now everything is fine.
Regards.
maksimus0021 said:
Installed Build "ua_hammerhead-7.1.1-20170328", Wi-Fi also does not work. I had to install wifi-fix, now everything is fine.
Regards.
Click to expand...
Click to collapse
Alright. We'll be soon opening a Nexus 5 thread as well.
Ziyan said:
Alright. We'll be soon opening a Nexus 5 thread as well.
Click to expand...
Click to collapse
Good news! Thanks for your work!
Regards.
maksimus0021 said:
Installed Build "ua_hammerhead-7.1.1-20170328", Wi-Fi also does not work. I had to install wifi-fix, now everything is fine.
Regards.
Click to expand...
Click to collapse
Where did you find this fix wi fi, give me a link?
Mayrbek86 said:
Where did you find this fix wi fi, give me a link?
Click to expand...
Click to collapse
Install via TWRP.
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. Better to store all partitions, at least efs and may be modem.
Instructions
1. Install 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
Links
[SM-T820]
5. 20200211: latest sources, February security patch: https://drive.google.com/file/d/1D8lY5z9O3oafqiWlDLvtltFDQCEHnZbN/view?usp=sharing
4. 20200113: latest sources, January security patch: https://drive.google.com/file/d/1enARwIN4oY_IrugrfncONxUGR-jbuY8s/view?usp=sharing
3. 20191224: latest sources, update kernel to 3.18.140: https://drive.google.com/file/d/1Hsl84EDxB_XQqgEPOIvyRjTdYUXuuWtR/view?usp=sharing
2. 20191013: https://drive.google.com/file/d/1z15hqXU-BL4H4MloSqukB2v1XqtUUlU2/view?usp=sharing
1. 20191010: https://drive.google.com/file/d/13gyKGE95kWFk2zbn0zW9GwiTHhyuPohr/view?usp=sharing
[SM-T825]
5. 20200211: latest sources, February security patch: https://drive.google.com/file/d/1fe4Gdlyx4U27RPJVnidhoiO1pqTp0b7I/view?usp=sharing
4. 20200113: latest sources, January security patch: https://drive.google.com/file/d/1duPl5zCv7D7xTvJjIAq6lrC7SfaWTl0c/view?usp=sharing
3. 20191224: latest sources, update kernel to 3.18.140: https://drive.google.com/file/d/1fvQMz0diPKFnzkVqMjLle74gFzn-6-Mq/view?usp=sharing
2. 20191013: https://drive.google.com/file/d/10CclbMYTINKww9dqZ_j6jKOqXcUX9s39/view?usp=sharing
1. 20191010: https://drive.google.com/file/d/1pW17U6PRt3Ptlm6WDCCbWG3HlanhaBx3/view?usp=sharing
Root
Install latest magisk (20.1+) from canary channel: https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337
TWRP
Use twrp from https://forum.xda-developers.com/ga...recovery-twrp-3-1-0-1-samsung-galaxy-t3581359
or my repack: https://drive.google.com/file/d/1KyX6xZ8WrcNyHo73-lHhU2dZjX0KFJc1/view?usp=sharing
Gapps
https://opengapps.org
Platform: ARM64
Android: 10.0
Sources
Sources: https://github.com/lineageos
Kernel: https://github.com/Valera1978/android_kernel_samsung_msm8996
Device: https://github.com/Valera1978/android_device_samsung_gts3llte and https://github.com/Valera1978/android_device_samsung_gts3lwifi
Vendor: https://github.com/Valera1978/android_vendor_samsung_gts3llte and https://github.com/Valera1978/android_vendor_samsung_gts3lwifi
Thanks
Thanks to LineageOS team
Uh nice - thanks Valera! Any chance you can add your manifest? I would like to try building Android once myself.
Error flashed on screen on reboot
I am getting 'There's an internal problem with your device. Contact your manufacturer for detail.' error on every reboot. I've flashed the 'BL_T825XXU3CSH9_CL16530048_QB25611745_REV00_user_low_ship_MULTI_CERT.tar.md5' bootloader but still facing the issue.
See the screenshot for error message.
Camera is not working
Valera1978 said:
I'm not responsible for any damage to your device of any sort.
Click to expand...
Click to collapse
Hi there,
do you have any intention to include palm rejection on Q?
It's the only missing feature on LOS...
Stogie87 said:
Hi there,
do you have any intention to include palm rejection on Q?
It's the only missing feature on LOS...
Click to expand...
Click to collapse
Do custom ROMs have to have palm rejection added? It's not normal feature?
This would be good to know as I got this device to use the pen!
I notice that screen is very hard to wake up. I have to play all buttons in random combination to be able to bring up lock screen. Once it get unlocked, everything works find.
I did once get system UI locked error. I have to push all buttons to force it reboot.
So I tested this rom on my T820 Wifi and in my opinion it works pretty stable, except of some issues I recognised:
- Saving pictures does not work. The pictures I get are scrambled.
- sd cards in ntfs format not working
- Palm rejection is not working
- ed xposed causes boot into download mode
- screen wakup is sometimes slow
- Viper4Android is not working
- Speaker only working on one site (right)
- it's not possible to rename SD Card or uninstall any system app like mail-app via root
- Netflix is not working
- Not possible to activate a custom notification sound
- Adaway only working with systemless host activated in magisk
- trying to use miracast causes a complete crash of system ui and makes a reboot necessary
- digital wellbeing randomly fc if settings menu is open
- sometimes hardware buttons stuck and i have to wait 5 sec until I can use them again
Thanks for your work!
*update: On second build same issues and camera just force close, now
did anyone figure out how to get the camera to work. It takes pictures but to view them they all look scribble.
does this rom work with the T825Y?
MR2_Wei said:
does this rom work with the T825Y?
Click to expand...
Click to collapse
Just try it. I think the specifications are the same like T825.
ghostman256 said:
did anyone figure out how to get the camera to work. It takes pictures but to view them they all look scribble.
Click to expand...
Click to collapse
Just use gcam it 'll work
alvinbw said:
Just use gcam it 'll work
Click to expand...
Click to collapse
Not working on second build for me
Now for the *REAL* question, does this ROM cause graphical glitches when you run a 3D load and heat the processor up to 100c?! That was my experience various unofficial LOS16/RR based Pie builds. I get temps in the worst case up to 97c under extreme load on the stock OneUI ROM, but normally it is way LOWER. Could someone (with the performance level in the power settings set to max) test games like https://play.google.com/store/apps/details?id=com.PnA.Offroad and some heavier ones for an extended period of time, and maybe some benchmarks (AnTuTu, 3DMark, etc...) while watching the CPU temp and General SoC temp with a temp guage overlay (like the one in the paid option on DevCheck).
Sent from my SM-G950U using Tapatalk
@Valera1978
Is there any chance, that you compile Havoc OS 3.0 for our Device?
Thanks in advance
I got it installed and booted but the rotate function isn't working, even when I open youtube and make it full screen it's doesn't rotate
MoSaMiChEs said:
I got it installed and booted but the rotate function isn't working, even when I open youtube and make it full screen it's doesn't rotate
Click to expand...
Click to collapse
Don't expect that anything on this rom will fixed soon.
Always the same with this dev. He releases a build with issues, then he ignores all issue reports and only releases sometimes a new build with security updates and nothing more. I wish a had wait a little bit and bought a tab s5e, because it seems to be the only new Samsung tab with fully working custom roms and palm rejection.
Better you use stock rom for tab s3.
w595shubham said:
I am getting 'There's an internal problem with your device. Contact your manufacturer for detail.' error on every reboot. I've flashed the 'BL_T825XXU3CSH9_CL16530048_QB25611745_REV00_user_low_ship_MULTI_CERT.tar.md5' bootloader but still facing the issue.
See the screenshot for error message.
Click to expand...
Click to collapse
same here
There is something that I cannot understand. The users say that there are problems with the ROM but OP says there aren't...
Quote:
Originally Posted by w595shubham
I am getting 'There's an internal problem with your device. Contact your manufacturer for detail.' error on every reboot. I've flashed the 'BL_T825XXU3CSH9_CL16530048_QB25611745_REV00_user_ low_ship_MULTI_CERT.tar.md5' bootloader but still facing the issue.
See the screenshot for error message.
Not sure if answered but I fixed this by:
Copying the complete line ro.vendor.build.fingerprint.................. from the /system/build.prop file.
Paste replacing the line ro.vendor.build.fingerprint.................. in the /vendor/build.prop file.
These files crosscheck each other looking for this line. The files must be from different builds.
{
"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"
}
Code:
/*
* I'm not responsible for bricked devices, damage, loss of Google services, you getting fired because the alarm app failed, etc. Do this at your own risk.
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications.
* Your warranty may/will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
About LineageOS4MicroG & LineageOS
LineageOS unofficial fork with built-in microG gapps implementation.
Full Play Services compatibility [Well-almost...YMMV]
Our ROM has built-in microG free-as-in-freedom re-implementation of Google's proprietary Android user space apps and libraries. This enables you to use every Google service you need without keeping another closed-source binary blob in your Android system.
Native F-Droid support
LineageOS for microG comes with F-Droid already installed. You can use it to access plenty of FOSS applications or even a Play Store bridge repository like Playmaker or GPlayWeb.
About LineageOS
LineageOS is a free, community built, aftermarket firmware distribution of Android 9 (Pie), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
Learn more at:
LineageOS: https://lineageos.org/
LineageOS4MicroG: https://lineage.microg.org/
Click to expand...
Click to collapse
Rom Built by Bernie_nixKnown issues:
USB-C headphones work for music, watching videos, etc. They don't work in the phone app...yet. (working on this)
Some users report VOIP calls don't work properly. YMMV. Skype, Whatsapp, Nextcloud Talk, working great for me.
Automatic updates not yet implemented but will be in a future build.
You tell me.
Install Instructions(If coming from stock or another rom):
Prerequisites: Coming from stock rom with bootloader unlocked, Developer settings enabled, android debugging enabled.
(1) ADB reboot bootloader,
(2) Fastboot boot twrp.img
(3) Install copy A/B partitions zip,
(4) Select Wipe button, Advanced Wipe, Choose: Dalvik/ART Cache, Data, Internal Storage, System. Then Swipe to Wipe all of these.
(5) Select Back arrow button
(6) Select Format Data Button. Type yes
(7) Select Install button. Choose rom zip. Swipe to confirm flash.
(8) Press back arrow button 2x to get back to main screen. Select Wipe button. Select format data button. Type yes.
(9) Reboot. Phone will mention "no os installed." Ignore it. Proceed with reboot. Phone will boot twice, then take you to the lineage recovery screen. Use volume down button to select Factory data reset, press power button, select yes to delete data. Phone will reboot into lineageos4microg.
DO NOT install twrp installer/orange fox installer until after phone boots into lineageos4microg or it will not boot. After you have setup lineageos, you can then reboot into twrp and install orange fox or twrp and magisk if you choose. Do not ever install any GAPPS on this ROM.
Upgrade Instructions(If coming from one of my previous builds):
(1) ADB reboot bootloader,
(2) Fastboot boot twrp.img
(3) Select Install button. Choose rom zip. Swipe to confirm flash.
(4) Select Wipe button, Advanced Wipe, Choose: Dalvik/ART Cache
(5) Reboot(6) If you had Magisk installed, you can then reboot into TWRP/Ofox and flash magisk.zip
Tips for Use
1. Root can be enabled in this build by going to Developer Settings->Root Access->Apps and ADB
2. To turn off battery led when charging, Settings>Apps & notifications>Notifications>Battery Light
3. To set up Microg,
(1) open MicroG app,
(2) press self-check, press battery optimizations ignored and allow,
(3) go back one screen, select unified nlp settings, configure location backends, press the checkbox next to mozilla location service and ok, configure address lookup backends, press checkbox next to nominatum and ok,
(4) then go through Google services from top to bottom and enter your information.
(5) Enable location from pull-down shade. Open maps, get your location. Go back to Microg. Run self-check. All boxes should show a check.
(6) Microg is setup in less than 5 minutes and fully working.
(7) Turn off location from pull-down shade bc they're tracking you 4. Want a better GPS experience? Install Deja Vu Location Service, GSM Location Service and Radiocells.org Unified Network Location Provider Backend from F-Droid. Works great with Google Maps or OSM.
5. Looking for a great camera? Try Hypercam for Moto G7 from gcambrasil at https://gcambrasil.com.br/motorola
1. After installing, go to internal storage, create folder "gcam" (without quotes), create folder "Configs" inside of "gcam," and place the Pixelmod_byJGB.xml (attached) file in that folder.
2. Open up Hypercam, double tap on black space near camera button, load Pixelmod_byJGB.xml file.
Reporting bugs:
DO NOT Report bugs if you're running a custom kernel or you installed Xposed.
Please report bugs in this thread.
Logcats are helpful but not required. Grab a full logcat right after the problem has occurred.
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues.
Thread Purpose & LimitsThis thread has been created to discuss the installation and use of this rom. If you have questions about building roms, this thread is not the place to do it. Please create a thread under Q/A and/or visit the Telegram group https://t.me/mG7Power. I'm happy to help but going to the telegram group or opening a Q/A thread allows many users to assist you and will help to keep this thread on-topic. Failure to follow this request will result in a warning followed by report to XDA if continued. Some excellent resources for building microg include https://lineage.microg.org/ and https://8192.one/post/lineage_build_with_docker/.
Download:
Change log
1. Latest March security update
Status: Stable
ROM OS Version: 9.x Pie
Android Security Patch Level: Mar. 5, 2020
Download link: https://www.androidfilehost.com/?fid=4349826312261741637
MD5: 54b467570f65ce85f164bd8e99943ab7
Older Versions:
Change log
1. Latest sources
2. Root option enabled in development settings
Status: Stable
ROM OS Version: 9.x Pie
Android Security Patch Level: Feb. 5, 2020
Download link: https://androidfilehost.com/?fid=4349826312261727435
MD5: aeb4aa1141c6d74ac016e8fba797c245
Next update news...:
Mar 10, 2020 - Currently working on USB-C audio during phone calls, increasing audio volume. Once USB-C audio gets fixed, I'll enable OTA updates.
Source and Additional Links
https://github.com/LineageOS
https://github.com/LineageOS/android...otorola_sdm632
Telegram group for additional ROMS, files and support: https://t.me/mG7Power
Rom Last Updated Mar. 10, 2020
Thread Info Last Updated Mar. 10, 2020
Guide on how to build your own posted here: https://forum.xda-developers.com/g7...d-lineageos4microg-16-0-t4070079#post82069641
hi im really interested in this rom but If twrp is already my permanent recovery, this rom won't install correctly?
edit.. tried it anyway since this is a secondary phone, figured i didnt have much to lose, followed instructions to the TEE, and it installed just fine.
clarkkentxda said:
hi im really interested in this rom but If twrp is already my permanent recovery, this rom won't install correctly?
edit.. tried it anyway since this is a secondary phone, figured i didnt have much to lose, followed instructions to the TEE, and it installed just fine.
Click to expand...
Click to collapse
I should have another update with OTA server and a few other fixes soon. It's also super quick to update from current build. Stay tuned and enjoy!
Bernie_nix said:
I should have another update with OTA server and a few other fixes soon. It's also super quick to update from current build. Stay tuned and enjoy!
Click to expand...
Click to collapse
Thanks for your efforts, I've been enjoying it, it's hard to find a rom that offers a little privacy from google, most things are working just fine, one thing I've noticed is that video is super super dark, No matter if it's stock camera or open camera but that's all I've came across in the issues department so far
clarkkentxda said:
Thanks for your efforts, I've been enjoying it, it's hard to find a rom that offers a little privacy from google, most things are working just fine, one thing I've noticed is that video is super super dark, No matter if it's stock camera or open camera but that's all I've came across in the issues department so far
Click to expand...
Click to collapse
Thanks for your feedback! No problems with video if using a different app. Try Hypercam version 1.3.030119.0645build-6.1.021
Bernie_nix said:
Thanks for your feedback! No problems with video if using a different app. Try Hypercam version 1.3.030119.0645build-6.1.021
Click to expand...
Click to collapse
Hypercam works like a charm, thank you for the suggestion! does hyper cam rely on anything google related like services or frameworks or binarys? (not sure what to call it since im not a developer) i'm wondering because I own a pixel 3a and im thinking of installing graphene os but any apps that rely on those ran on those will not work on graphene
clarkkentxda said:
Hypercam works like a charm, thank you for the suggestion! does hyper cam rely on anything google related like services or frameworks or binarys? (not sure what to call it since im not a developer) i'm wondering because I own a pixel 3a and im thinking of installing graphene os but any apps that rely on those ran on those will not work on graphene
Click to expand...
Click to collapse
Hypercam is ported from gcam so YMMV. Given that it works on this ROM with microg, if it has any hooks they probably aren't deep. I'd give it a go
I've been a user of root explorer (pro) for seven+ years or so now. I side loaded the apk that I extracted from a previous setup on my phone and it works perfect. Some may already know that but just figured I'd share. Awesome job on this rom! Appreciate you sharing your builds!! :good:
flash713 said:
I've been a user of root explorer (pro) for seven+ years or so now. I side loaded the apk that I extracted from a previous setup on my phone and it works perfect. Some may already know that but just figured I'd share. Awesome job on this rom! Appreciate you sharing your builds!! :good:
Click to expand...
Click to collapse
Glad you like it and thanks for your feedback; tip on root explorer pro.
Bernie_nix said:
Glad you like it and thanks for your feedback; tip on root explorer pro.
Click to expand...
Click to collapse
Couple questions.. What busy box are you using and where did you get it? I've been using Osmosis’s magisk module busy box for so long idk where to even begin. haha. I attempted to install one from fdroid but it failed install. Can I flash his busy box in recovery? Probably not because we are using the LOS built in root instead of magisk correct? Would all hell break loose if I flashed magisk root now and something would possibly get messed up? Thinking if that's what I wanted I would have had to flash it in the beginning so it would over ride the other root...?
This rom runs better than anything besides ugly stock moto on my device. I was off work yesterday so I started messing with my device, hours went by and my battery barely moved at all. Not having Google play services really saves a good bit of juice. Havoc has spoofing now too. I vote that it becomes mandatory for all roms to have signature spoofing. :victory: Should call it the ImNOtgoingback rom or something. I’ve used micro g and fdroid before on previous devices but never for as long as I've been using this. Im like a binge crackflasher nowadays instead -vs- back when Euroskank CM10 bacon was on and popping every morning at around 6am central time the world would all flash. One last thing.. Do you decrypt your data or leave it encrypted? Reason I ask is I was wondering what method you do or would do if you wanted to decrypt?
This rom really runs great! Anyone who hasn't tried this yet should!
Edit
Ps: I've used many great gcams but HyperCam is most definitely at the top of my list. It reminds me of the pictures my Pixel XL used to take. Awesome camera app! Thanks for recommending it and sharing links!
not being picky, but can we have a regular LOS build please? I mean, without microG.
The last syberhexen one is dated 2019-10-01 so it would be nice to have an update to it.
DanAlucard said:
not being picky, but can we have a regular LOS build please? I mean, without microG.
The last syberhexen one is dated 2019-10-01 so it would be nice to have an update to it.
Click to expand...
Click to collapse
You're right, but it's not easy to be a maintainer - and use your free time to resolve problems for others.
Maybe you should try to create your own build using code created by more advanced users synced with latest LineageOS repo.
If you're interested in that, here's an attached manifest file which would build working LineageOS 16.0 for ocean with February security patch - I'm using such one right now(built 3 days ago), but with microg. It's all possible thanks to LineageOS team and Dark98 (and many others) work, as you can see.
Good luck
robson_89 said:
You're right, but it's not easy to be a maintainer - and use your free time to resolve problems for others.
Maybe you should try to create your own build using code created by more advanced users synced with latest LineageOS repo.
If you're interested in that, here's an attached manifest file which would build working LineageOS 16.0 for ocean with February security patch - I'm using such one right now(built 3 days ago), but with microg. It's all possible thanks to LineageOS team and Dark98 (and many others) work, as you can see.
Good luck
Click to expand...
Click to collapse
Thanks a lot. Will have a look at it. Who knows, maybe I end up maintaining it
DanAlucard said:
Thanks a lot. Will have a look at it. Who knows, maybe I end up maintaining it
Click to expand...
Click to collapse
That would be great!
In the meantime, i've built and updated my LOS 16 as attached - forgot to add screenshot previously.
DanAlucard said:
not being picky, but can we have a regular LOS build please? I mean, without microG.
The last syberhexen one is dated 2019-10-01 so it would be nice to have an update to it.
Click to expand...
Click to collapse
Not from me. I build this for personal use, share it and have no interest in a vanilla los build. Robson is correct. Go with his build of you don't want microg.
flash713 said:
Couple questions.. What busy box are you using and where did you get it? I've been using Osmosis’s magisk module busy box for so long idk where to even begin. haha. I attempted to install one from fdroid but it failed install. Can I flash his busy box in recovery? Probably not because we are using the LOS built in root instead of magisk correct? Would all hell break loose if I flashed magisk root now and something would possibly get messed up? Thinking if that's what I wanted I would have had to flash it in the beginning so it would over ride the other root...?
This rom runs better than anything besides ugly stock moto on my device. I was off work yesterday so I started messing with my device, hours went by and my battery barely moved at all. Not having Google play services really saves a good bit of juice. Havoc has spoofing now too. I vote that it becomes mandatory for all roms to have signature spoofing. :victory: Should call it the ImNOtgoingback rom or something. I’ve used micro g and fdroid before on previous devices but never for as long as I've been using this. Im like a binge crackflasher nowadays instead -vs- back when Euroskank CM10 bacon was on and popping every morning at around 6am central time the world would all flash. One last thing.. Do you decrypt your data or leave it encrypted? Reason I ask is I was wondering what method you do or would do if you wanted to decrypt?
This rom really runs great! Anyone who hasn't tried this yet should!
Edit
Ps: I've used many great gcams but HyperCam is most definitely at the top of my list. It reminds me of the pictures my Pixel XL used to take. Awesome camera app! Thanks for recommending it and sharing links!
Click to expand...
Click to collapse
Thank you for your kind words! I use busybox from osmosis via magisk module; yes, I enjoy magisk on this rom. Busybox (osmosis) actually makes apps like Titanium Backup work great if you've purchased a non-Google play license file from them. This rom is my personal build that I uploaded to xda and shared, and I plan on maintaining it for some time. So...Magisk flashed via twrp/ofox works great, and so does busybox magisk.
+1 on your comment about Hypercam. Completely agree about hypercam. I've tested a lot on this device and of course am open to suggestions.
I will update this rom via the Lineageos patches, however, the Feb update hasn't been pushed yet so no new rom for now. I have isolated a few bugs, e.g. usb-c for calls and am working on OTA, however, I am going to release a surprise test build in the next couple of days (hopefully). It's building as we speak, and I will test before releasing. Stay tuned, and I look forward to yours and others feedback and questions.
P.S. I am a linux user and believe in the power of open-source. If you or others have any questions or comments, feel free to reach me via the telegram link in the 1st post; I usually answer a bit quicker there but also answer on here. Best wishes and thanks again!
P.S.S. Welcome Robson to our open-source team! If any of you are looking for a lineageos build without microg, check out his post a couple of posts above.
generally audio is lower quality than stock rom, it's not as loud and not as clear.
clarkkentxda said:
generally audio is lower quality than stock rom, it's not as loud and not as clear.
Click to expand...
Click to collapse
Did you try the audiofx app that is included?
Bernie_nix said:
Did you try the audiofx app that is included?
Click to expand...
Click to collapse
Indeed sir, it doesn't help all that much for me though.
rottenwheel said:
I accompany this sentiment. It happens with most Motorola Moto G devices I own and use: if kept with stock builds both camera and audio have a far better quality than custom ROMs do. Motorola engineers do hell of a job when working on their OEM firmware. It is a real shame yet not so far from reality that we need to take these tradeoffs to obtain better privacy.
An idea that comes to mind is for us to debloat the stock build, bake in microG and possibly update security patches as they come out. Motorola Moto G1 (falcon) has something alike with IDCrisis - https://forum.xda-developers.com/moto-g/development/rom-identity-crisis-6-t3324595
Thank you for the heads-up, though. I definitely love the audio on stock.
Click to expand...
Click to collapse
Unfortunately you can't do that with stock. Microg requires signature spoofing enabled in the ROM which is a patch applied when building a ROM. You could try patching stock to enable signature spoofing with a tool like Heystack but it most likely won't work on stock. Another route is using another ROM with signature spoofing support e.g. crdroid or omni, applying signature spoofing patch if necessary and then patching in twrp with something like nanodroid patcher.
That being said I am working through desired edits and bugs in this ROM but can't provide any ETAs. I encourage anyone with a bit of coding experience or interest to build their own and learn. Making changes to rom builds is not hard, just time consuming and unfortunately doesnt pay the bills...so its done in hobby time. I do plan on maintaining this ROM for some time though and will probably be on Pie longer than most users until 10 is ready; right now 10 has way too many bugs for me to use or build for daily driver material.
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. camera
What doesn't work
1. selinux is permissive. I have tried to make this build enforcing for weeks, but when I do, the OS doesn't boot and there is no adb logcat output despite making an "eng" build. Without adb logcat output, it's virtually impossible to determine what is wrong and I'm not spending anymore time on it. If having enforcing mode is important to you, use my 18.1 builds.
2. keyboard bug workaround. When prompted to enter something like a Bluetooth pin or text based password, sometimes the keyboard is not shown on the screen or off screen. The workaround is to goto settings, system, languages & input, on-screen keyboard, Android Keyboard (AOSP), appearance & layout, theme and choose "Material - follow system settings".
This keyboard bug is a LineageOS bug as per
https://review.lineageos.org/c/LineageOS/android_packages_inputmethods_LatinIME/+/325438
3. gapps. Some of you require gapps for whatever reason. I use Aurora Store for my purposes and thus have NO KNOWLEDGE of the current state of gapps.
There are various gapps projects (at least 5 in 2022). Each has pros and cons. It's your job to do the research and find a suitable gapps project. I suggest you allocate at least a couple of hours doing your own research. My rom works by itself fine without gapps. DO NOT talk about gapps in this thread. As a courtesy to gapps users, if you want to talk about gapps, I have opened a new thread at
https://forum.xda-developers.com/t/...m-t35x-sm-t550-sm-t560nu-and-sm-p550.4479285/
so you may discuss gapps wrt to the msm8916 platform. I will NOT be participating in that thread as I do NOT use gapps.
Thanks
1. LineageOS team for source code.
2. Kyle Harrison
- looking through the adb logcat and suggesting that my binder code was too old to work with Android 12's keystore2 code
- for the graphics and legacy camera patches to allow msm8916 to work with Android 12
- for his Motorola LineageOS 19.1 device trees so I could use his patches as a template for msm8916
3. @tarkzim
- adding back audio hal 2.0 and legacy camera hal 1.0 into the LineageOS trees
- helping me think through the msm8916 random reboots which was due to the TCP/IP patches
- maintaing and updating his repos so I can study them for learning purposes
4. pre ALPHA testers @breversa , @XDA_username00 for willing to test pre ALPHA builds and leaving feedback.
FAQ - I spent hundreds of hours building this rom. It was frustrating process from Nov 2021 to Aug 2022 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
https://github.com/retiredtab/android_kernel_samsung_msm8916
The device tree files are at
https://github.com/retiredtab/android_device_samsung_msm8916-common/tree/lineage-19.1
https://github.com/retiredtab/android_device_samsung_gt510wifi/tree/lineage-19.1
https://github.com/retiredtab/device_samsung_gte-common/tree/lineage-19.1
The vendor tree files are at
https://github.com/retiredtab/android_vendor_samsung_gt510wifi/tree/lineage-19.1
https://github.com/retiredtab/vendor_samsung_msm8916-common/tree/lineage-19.1
The manifest.xml (or roomservice.xml) and build instructions for 19.1 are at
https://github.com/retiredtab/LineageOS-build-manifests
Q2. Is this ALPHA 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 2022 with no major issues. I suggest you do a clean install, see FAQ 11, and flash this 19.1 ROM BY ITSELF (no gapps, magisk, etc) and see if you like it. If you do like it and want to add gapps then see FAQ 12.
Q3. What if my app, xyz, doesn't work?
A3. If your app doesn't work, then go back to your old rom.
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. 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
https://dl.twrp.me/gt510wifi/
Q6. Why should I use this rom?
A6. If you don't like this rom, then don't use it.
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. I don't have the time to help newbies, so please 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
# attach the problem.txt ZIPPED as text files don't seem to get attached properly
Q10. Will you still build 18.1 for this device?
A10. Yes, for rest of 2022, but I will make a decision in January 2023 on how 18.1 and 19.1 will be maintained. If you like to help by building 18.1/19.1, please let me know.
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 19.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.
Let me by crystal clear. YOU NEED TO DO YOUR OWN HOMEWORK selecting between the various gapps offered. There are 5: opengapps, nikgapps, mindthegapps, flamegapps and bitgapps. Each one will have it's own installation instructions. The only recommendation I will offer to use the SMALLEST version of gapps.
Don't be surprised that whatever gapps you use might have problems like "Just a sec", voice not working, updating google play store please wait, etc. These are NOT problems of the OS as the OS will run fine without gapps. These are gapps problems and you must ask in the gapps forum why it doesn't work.
In addition, some of the gapps may not install properly when using TWRP and say "cannot /mnt/system". For those cases, please use the LineageOS recovery.img you can download from
https://sourceforge.net/projects/retiredtab/files/SM-T550/LineageOS-recovery/
By flashing the LineageOS recovery.img, it will overwrite the existing TWRP and you will get a different UI.
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. Android does not depend on gapps in order to work.
Questions about gapps, for your courtesy, should be asked at
https://forum.xda-developers.com/t/...m-t35x-sm-t550-sm-t560nu-and-sm-p550.4479285/
Q14. Why isn't my post answered or ignored?
A14. Questions already answered in the FAQ will be completely ignored. Again, I do not use Windows OS or gapps.
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.
7. Remove all unused quick setting "bubbles" from the quick pull down menu. I only need and have 6.
Q17. Does this rom support Magisk for root?
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. With 19.1, legacy devices like ours will NEVER be official due to lack of ebpf support. See https://lineageos.org/Changelog-26/
Also, I don't want the responsibilities that come with being an official maintainer.
Q19. What is the difference between this rom and others?
A19. This rom tries to be pure LineageOS with little to no modifications.
Q20. Will there be any major 19.1 code modifications in the future?
A20. I don't anticipate any major modifications. There may be some 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 19.1 is working.
Q21. Why did you fork the device and vendor trees for 19.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-T357W, 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 have completely decommonized and rearranged the 19.1 msm8916-common tree so it's easier for me to maintain and build.
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. What major code changes are in 19.1 vs 18.1.
A24.
- iptables has been removed in favour of ebpf
- keystore v1 has been replaced with keystore v2 which requires that the binder calls have some built-in security
- audio hal 2.0 has been deprecated
- legacy camera hal 1.0 and snap app have deprecated
Q25. I don't like the taskbar, how do I turn it off?
A25. Choose settings, type task into the search bar. Choose enable taskbar and disable taskbar. This will leave the on screen nav bar. If you want to disable that, go to settings, system, gestures, system navigation, gesture navigation.
Q26. Okay, I understand the consequences and that this is ALPHA rom and willing to take the risks outlined, now where can I find the rom?
A26. You can download it from https://sourceforge.net/projects/retiredtab/files/SM-T550/19.1/
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 in TWRP. This is known has a clean install. Backup your data before a clean install.
19.1 has been my daily driver since March 2022.
May 6, 2023 release notes
1. May 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2023-05
2. Whatever LineageOS changed since Apr 5 patches. About 7,400 files had to be recompiled.
Apr 13, 2023 release notes
1. Apr 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2023-04
2. Whatever LineageOS changed since Mar 5 patches. About 23,000 files had to be recompiled.
March 19, 2023 release notes
1. Mar 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2023-03
2. Whatever LineageOS changed since Feb 5 patches. About 24,500 files had to be recompiled.
Feb 12, 2023 release notes
1. Feb 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2023-02
2. Whatever LineageOS changed since Jan 5 patches. 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:S_asb_2023-01
2. Whatever LineageOS changed since Dec 5 patches. About 4,400 files had to be recompiled.
Dec 9, 2022 release notes
1. Dec 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2022-12
2. Whatever LineageOS changed since Nov 5 patches. About 4,700 files had to be recompiled.
Nov 11, 2022 release notes
1. Nov 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2022-11
2. Whatever LineageOS changed since Oct 5 patches. About 5,400 files had to be recompiled.
Oct 7, 2022 release notes
1. Oct 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2022-10
2. Whatever LineageOS changed since Sept 5 patches. About 4,500 files had to be recompiled.
Sept 12, 2022 release notes
1. Sept 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2022-09
2. Switched to different timekeep repo that works with Android 12 and up.
3. Whatever LineageOS changed since Aug 5 patches. About 4,700 files had to be recompiled.
Aug 10, 2022 release notes
1. Aug 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2022-08
2. Initial ALPHA release to public.
Reserved.
Wanted to report no issues with this recent version via in-place upgrade from last month's v19.1 alpha test build.
For anyone still running v17 or v18 wondering if it's worth upgrading, it depends on your use case.
Here's mine if it helps:
I use this SM-T550 tablet on a semi-regular basis for web browsing, reading e-books, and watching video content.
Using v3.6.2_90 TRWP with a microSD card and some Bluetooth headphones.
No gapps, Bromite Chromium browser, NewPipe, and all other apps downloaded via anonymous session using Aurora Store (which also works great with tracking updates).
Apps: Bitwarden (still slow, but faster than when on v18), Netguard, Netflix (no DRM issues), Nova Launcher, Plex, United Airlines app (need the Bromite browser installed for DRM content to play), and Amazon Kindle.
Works great.
bierma32 said:
Works great.
Click to expand...
Click to collapse
can you give more info please. is good for the daily use? thanks
I used now more than 4 weeks and all what I have tested works perfect.
It is my daily driver.
Bluetooth works , WiFi connection is much stable if you have an worse signal.
Battery consumption I much better than Los 18.1
I have the smt550. Do you have a guide to root it and install this rom? Where can i find it? Thanks
vuoshinotizy said:
can you give more info please. is good for the daily use? thanks
Click to expand...
Click to collapse
Everything seems to work (except RIL as mine is an LTE device). Just bear in mind that SELinux is disabled, so you might not want to use the tablet to store sensitive data.
vuoshinotizy said:
I have the smt550. Do you have a guide to root it and install this rom? Where can i find it? Thanks
Click to expand...
Click to collapse
A general guide to install a custom OS for a Samsung device can be found on the LineageOS website. Here's an example for a different Samsung device https://wiki.lineageos.org/devices/beyond1lte/install
The main differences are you'll need to refer to the original post Q5 to obtain a custom recovery (TWRP) and Q26 to obtain the LineageOS build.
New build lineage-19.1-20220912-UNOFFICIAL-gt510wifi.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 in TWRP. This is known has a clean install. Backup your data before a clean install.
19.1 has been my daily driver since March 2022.
Sept 12, 2022 release notes
1. Sept 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2022-09
2. Switched to different timekeep repo that works with Android 12 and up.
3. Whatever LineageOS changed since Aug 5 patches. About 4,700 files had to be recompiled.
retiredtab said:
New build lineage-19.1-20220912-UNOFFICIAL-gt510wifi.zip
Click to expand...
Click to collapse
No issues with in place upgrade. Still works great!
vuoshinotizy said:
I have the smt550. Do you have a guide to root it and install this rom? Where can i find it? Thanks
Click to expand...
Click to collapse
Just sent you PM with the steps I used to get it on mine.
retiredtab said:
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. camera
What doesn't work
1. selinux is permissive. I have tried to make this build enforcing for weeks, but when I do, the OS doesn't boot and there is no adb logcat output despite making an "eng" build. Without adb logcat output, it's virtually impossible to determine what is wrong and I'm not spending anymore time on it. If having enforcing mode is important to you, use my 18.1 builds.
2. keyboard bug workaround. When prompted to enter something like a Bluetooth pin or text based password, sometimes the keyboard is not shown on the screen or off screen. The workaround is to goto settings, system, languages & input, on-screen keyboard, Android Keyboard (AOSP), appearance & layout, theme and choose "Material - follow system settings".
This keyboard bug is a LineageOS bug as per
https://review.lineageos.org/c/LineageOS/android_packages_inputmethods_LatinIME/+/325438
3. gapps. Some of you require gapps for whatever reason. I use Aurora Store for my purposes and thus have NO KNOWLEDGE of the current state of gapps.
There are various gapps projects (at least 5 in 2022). Each has pros and cons. It's your job to do the research and find a suitable gapps project. I suggest you allocate at least a couple of hours doing your own research. My rom works by itself fine without gapps. DO NOT talk about gapps in this thread. As a courtesy to gapps users, if you want to talk about gapps, I have opened a new thread at
https://forum.xda-developers.com/t/...m-t35x-sm-t550-sm-t560nu-and-sm-p550.4479285/
so you may discuss gapps wrt to the msm8916 platform. I will NOT be participating in that thread as I do NOT use gapps.
Thanks
1. LineageOS team for source code.
2. Kyle Harrison
- looking through the adb logcat and suggesting that my binder code was too old to work with Android 12's keystore2 code
- for the graphics and legacy camera patches to allow msm8916 to work with Android 12
- for his Motorola LineageOS 19.1 device trees so I could use his patches as a template for msm8916
3. @tarkzim
- adding back audio hal 2.0 and legacy camera hal 1.0 into the LineageOS trees
- helping me think through the msm8916 random reboots which was due to the TCP/IP patches
- maintaing and updating his repos so I can study them for learning purposes
4. pre ALPHA testers @breversa , @XDA_username00 for willing to test pre ALPHA builds and leaving feedback.
Click to expand...
Click to collapse
Hi, Installed 19.1 recovery, did factory reset, formatted system and installed 19.1 version. No error messages. Unfortunately it keeps booting into recovery only. What did I do wrong?
Zomer123 said:
Hi, Installed 19.1 recovery, did factory reset, formatted system and installed 19.1 version. No error messages. Unfortunately it keeps booting into recovery only. What did I do wrong?
Click to expand...
Click to collapse
At first you have to tell us from which ROM or OS ( Stock ) you are comming.
Which Recovery you have installed ? TWRP or Lineage Recovery.
Have flashed only LOS 19.1 or LOS + Gapps ( which Version ) or have you flashed LOS + Gapps and Magisk ?
Try it again , factory reset and wipe cache , Data ( int. Sdcard ) System.
Flash Los and reboot system.
Is this OK . next step factory reset, flash Los and Gapps
Reboot system and so on.
bierma32 said:
At first you have to tell us from which ROM or OS ( Stock ) you are comming.
Which Recovery you have installed ? TWRP or Lineage Recovery.
Have flashed only LOS 19.1 or LOS + Gapps ( which Version ) or have you flashed LOS + Gapps and Magisk ?
Try it again , factory reset and wipe cache , Data ( int. Sdcard ) System.
Flash Los and reboot system.
Is this OK . next step factory reset, flash Los and Gapps
Reboot system and so on.
Click to expand...
Click to collapse
Coming from los 18.1 (aug 2022)... Installed los 19.1 recovery. Then factory reset etc. Then installed los 19.1 (sept). No gapps, no magisk...
Zomer123 said:
Coming from los 18.1 (aug 2022)... Installed los 19.1 recovery. Then factory reset etc. Then installed los 19.1 (sept). No gapps, no magisk...
Click to expand...
Click to collapse
Is there a reason for going with the LOS recovery image instead of TWRP? TWRP has worked great for me since v17 and haven't had a need for recovery with the SD Card, but then you might have a particular use case.
Remember you'll need to wipe the dalvik/data/internal storage/cache/system partitions first, then format data before installing the OS.
Hope any of that helps.
XDA_username00 said:
Is there a reason for going with the LOS recovery image instead of TWRP? TWRP has worked great for me since v17 and haven't had a need for recovery with the SD Card, but then you might have a particular use case.
Remember you'll need to wipe the dalvik/data/internal storage/cache/system partitions first, then format data before installing the OS.
Hope any of that helps.
Click to expand...
Click to collapse
I already solved it by flashing twrp using Odin.
Zomer123 said:
I already solved it by flashing twrp using Odin.
Click to expand...
Click to collapse
What was the reason that you have flashed the Lineage Recovery, since TWRP worked before ?
bierma32 said:
What was the reason that you have flashed the Lineage Recovery, since TWRP worked before ?
Click to expand...
Click to collapse
Idk, thought that it would be necessary to flash the 19.1 rom... But I also got back to 18.1 version since 19.1 is more laggy and has ugly QS tiles.
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.
NOTE: There is no S-pen support. If you need S-pen, DO NOT USE THIS ROM.
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. camera (selfie photo preview doesn't work), a bit slow to switch from front to back camera and vice versa
9. selinux enforcing
10. DRM level 3
11. deep sleep
What doesn't work/What isn't tested
1. gapps. Some of you require gapps for whatever reason. I use Aurora Store for my purposes and thus have NO KNOWLEDGE of the current state of gapps.
There are various gapps projects (at least 5 in 2022). Each has pros and cons. It's your job to do the research and find a suitable gapps project. I suggest you allocate at least a couple of hours/days doing your own research. My rom works by itself fine without gapps. DO NOT talk about gapps in this thread.
2. full disk encryption has been deprecated in Android 13 (LineageOS 20).
3. S-pen doesn't work and I have no plans to even try to make it work.
Source Code
The build instructions, source code and manifest are listed in post #2 FAQ #1. The kernel source code is at
https://github.com/retiredtab/android_kernel_samsung_msm8916/tree/lineage-20.0
Thanks
1. LineageOS team for source code.
2. LineageOS-UL team for merging, maintaining the legacy patches needed for old devices into one common repository so everyone can benefit.
https://github.com/orgs/LineageOS-UL/people
3. @lpedia for helping test a msm8916 tablet device.
FAQ - I spent hundreds of hours building this rom. If you think it's unreasonable to read this FAQ, then don't use this rom. Thank you.
Q1. Where are the source and kernel source files?
A1. The kernel source files are at
https://github.com/retiredtab/android_kernel_samsung_msm8916/tree/lineage-20.0
The device tree files are at
https://github.com/retiredtab/android_device_samsung_msm8916-common/tree/lineage-20.0
https://github.com/retiredtab/android_device_samsung_gt5note10wifi/tree/lineage-20.0
https://github.com/retiredtab/device_samsung_gte-common/tree/lineage-20
The vendor tree files are at
https://github.com/retiredtab/vendor-samsung-gt5note10wifi/tree/lineage-19.1
https://github.com/retiredtab/vendor_samsung_msm8916-common/tree/lineage-20
The manifest.xml (or roomservice.xml) and build instructions for 20 are at
https://github.com/retiredtab/LineageOS-build-manifests/tree/main/20/msm8916
Q2. Is this ALPHA 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 Jan 2023 with no major issues. I suggest you do a clean install, see FAQ 11, and flash this 20 ROM BY ITSELF (no gapps, magisk, etc) and see if you like it.
Q3. What if my app, xyz, doesn't work?
A3. If your app doesn't work, then go back to your old rom.
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. 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
https://sourceforge.net/projects/retiredtab/files/SM-P550/TWRP/
Q6. Why should I use this rom?
A6. If you don't like this rom, then don't use it.
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. I don't have the time to help newbies, so please 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
# attach the problem.txt ZIPPED as text files don't seem to get attached properly
Q10. Do I need to erase everything and format my data?
A10. Yes, you MUST erase all the partitions (system, data, dalvik/art cache, cache) using TWRP and MUST format your data before installing 19.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.
Q11. What gapps should I use?
A11. 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.
Let me by crystal clear. YOU NEED TO DO YOUR OWN HOMEWORK selecting between the various gapps offered. There are 5: opengapps, nikgapps, mindthegapps, flamegapps and bitgapps. Each one will have it's own installation instructions. The only recommendation I will offer to use the SMALLEST version of gapps.
Don't be surprised that whatever gapps you use might have problems like "Just a sec", voice not working, updating google play store please wait, etc. These are NOT problems of the OS as the OS will run fine without gapps. These are gapps problems and you must ask in the gapps forum why it doesn't work.
Q12. I'm having problems with gapps, can you answer why it's not working?
A12. I WILL NOT answer any questions regarding gapps. This thread is about the rom, not gapps. Android does not depend on gapps in order to work.
Q13. Why isn't my post answered or ignored?
A13. Questions already answered in the FAQ will be completely ignored. Again, I do not use Windows OS or gapps.
Q14. What speed up/optimization tips do you suggest?
A14.
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.
7. Remove all unused quick setting "bubbles" from the quick pull down menu. I only need and have 6.
Q15. Does this rom support Magisk for root?
A15. 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.
Q16. Will this rom ever become official?
A16. Starting with 19.1, legacy devices like ours will NEVER be official due to lack of ebpf support. See https://lineageos.org/Changelog-26/
Also, I don't want the responsibilities that come with being an official maintainer.
Q17. What is the difference between this rom and others?
A17. This rom tries to be pure LineageOS with little to no modifications.
Q18. Will there be any major 20 code modifications in the future?
A18. I don't anticipate any major modifications. There may be some 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 20 is working.
Q19. Why did you fork the device and vendor trees for 20?
A19. 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-T357W, 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 have completely decommonized and rearranged the 20 msm8916-common tree so it's easier for me to maintain and build.
Q20. Can you build a variant of this device? For example, a LTE or S-pen version.
A20. 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.
Q21. Can I load this rom on a variant devivce like LTE or S-pen version?
A21. 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!
Q22. I don't like the taskbar, how do I turn it off?
A22. Choose settings, type task into the search bar. Choose enable taskbar and disable taskbar. This will leave the on screen nav bar. If you want to disable that, go to settings, system, gestures, system navigation, gesture navigation.
Q23. Okay, I understand the consequences and that this is ALPHA rom and willing to take the risks outlined, now where can I find the rom?
A23. You can download it from https://sourceforge.net/projects/retiredtab/files/SM-P550/20/
Release notes
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 in TWRP. This is known has a clean install. Backup your data before a clean install.
June 23, 2023
1. Initial 20 ALPHA public release.
2. Incorporates June 5th security patches as per https://review.lineageos.org/q/topic:"T_asb_2023-06"
Reserved.