[ROM][OFFICIAL][13] LineageOS 20.0 for the SM-T290 (gtowifi) - Samsung Galaxy Tab A series ROMs, Kernels, Recover

WARNING: Samsung rolled out a new firmware update starting roughly at the end of January 2023.
This contains bootloader version 4. From what we understand with SM-T295 bootloaders, this may or may not permanently lock you out from ever flashing anything custom. Considering that we even have to downgrade our bootloader to the Android 9 version to get anything going, updating your bootloader this time will very likely block you from downgrading it, ever.
Our last known bootloader version is T290XXU3CVG3. Do not update past this, you will not be able to flash custom anything again.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 13, which is designed to increase performance and reliability over stock Android for your device.
* Your warranty is now void.
(But I mean it's probably already void at this point... bleh.)
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features
* included in this ROM before flashing!
* YOU are choosing to make these modifications and if
* YOU point the finger at us for messing up your device,
* WE will laugh at you.
Click to expand...
Click to collapse
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS GitHub organization. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review. You can also view the changelog for a full list of changes & features.
Instructions :
https://wiki.lineageos.org/devices/gtowifi/install
Downloads :
https://download.lineageos.org/gtowifi
Device source code:
https://github.com/LineageOS/android_device_samsung_gtowifi
https://github.com/LineageOS/android_kernel_samsung_sdm429
Credits:
LineageOS team
@Magendanz for TWRP
@SebaUbuntu for twrpdtgen
AndroidDumps on Telegram for help extracting blobs
@retiredtab for much initial testing and feedback

reserved

Changelog from before official:
Build 20221230:
Initial, very broken release
Build 20221231 (being hotfixed many times):
GPS now turns on but doesn't do anything useful
Fixed sensor service
Screen rotation works now
Fixed display issues
Fixed Widevine
Fixed Wi-Fi not turning back on after turning off
Build 20230102:
GPS fully working
Some proprietary blob cleanup
Build 20230103:
SELinux enforcing
ZRAM
Fix SafetyNet basicIntegrity
Build 20230108:
Android 12L
FM Radio is dropped
Nothing in the stock ROM suggests that this device actually supports FM Radio, despite online specifications saying otherwise. There is no hardware abstraction layer present for FM Radio anywhere I've found.
This will be disabled until someone can confirm it does work on stock. In which case, I will attempt to dig deeper, but I'm not sure how far I will get.
Build 20230115:
USB file transfer (MTP) fixed by switching to basic USB HAL
OTA updates have been implemented (maybe) (possibly) (idk)
Build 20230117:
Android 13
Performance upgrades:
Some kernel changes to improve performance (VDSO32 backport)
Various system services pinned in memory for UI responsiveness

Happy (belated) new year.
New build: 20230102 (more hotfixing)
Changelog:
GPS fully working
Some proprietary blob cleanup
Available at DL link in OP.
I'm going to be frequently releasing builds until I consider the ROM fully working (at least in the scope of my usage of this device). Afterwards, it'll probably be monthly builds with the usual ASB merging.

Glad to see there is a dedicated ROM for the T290!
I installed it on a T295 and a simple test found no issues.
Compared with GSI ROM, auto brightness and headphone jack can be used normally without any settings, and what's even better is that Bluetooth audio can be enabled with aptX!
Is it possible to add zRAM function in ROM? This can slightly alleviate the situation with only 2G RAM
Thank you so much for your work!

xperiazu21 said:
Glad to see there is a dedicated ROM for the T290!
I installed it on a T295 and a simple test found no issues.
Compared with GSI ROM, auto brightness and headphone jack can be used normally without any settings, and what's even better is that Bluetooth audio can be enabled with aptX!
Is it possible to add zRAM function in ROM? This can slightly alleviate the situation with only 2G RAM
Thank you so much for your work!
Click to expand...
Click to collapse
Interesting. I assume just as I expected cellular functionality doesn't work?
ZRAM is a TODO. For now, everything hardware-wise is working on the Wi-Fi model, so I am working on SELinux.

lifehackerhansol said:
Interesting. I assume just as I expected cellular functionality doesn't work?
ZRAM is a TODO. For now, everything hardware-wise is working on the Wi-Fi model, so I am working on SELinux.
Click to expand...
Click to collapse
Yes, after inserting the SIM card and restarting, there is no related cellular option. There is no IMEI number displayed in the system

xperiazu21 said:
I installed it on a T295 and a simple test found no issues.
Click to expand...
Click to collapse
@xperiazu21 , does the FM radio app work for you if you plug in headphones? Traditionally this doesn't work on wifi-only devices, but may on LTE devices due to modem chipset?
xperiazu21 said:
Is it possible to add zRAM function in ROM? This can slightly alleviate the situation with only 2G RAM
Click to expand...
Click to collapse
lifehackerhansol's upcoming build have should zram + enforcing. I built my own using his repos that incorporates the zram + enforcing. I suggest waiting for his build.
Code:
gtowifi:/proc/sys/vm # free -m
total used free shared buffers
Mem: 1845 1813 32 18 23
-/+ buffers/cache: 1789 56
Swap: 1369 124 1245
gtowifi:/proc/sys/vm # getenforce
Enforcing

New build: 20230103
Changelog:
SELinux enforcing
ZRAM
Fix SafetyNet basicIntegrity
Known issues:
SafetyNet doesn't seem to pass the CTS check.
Available at DL link in OP.

retiredtab said:
@xperiazu21 , does the FM radio app work for you if you plug in headphones? Traditionally this doesn't work on wifi-only devices, but may on LTE devices due to modem chipset?
Click to expand...
Click to collapse
After I plugged in the headset and opened FM APP, the operation failed and it seems to be not working.
After updating to version 20230103, zRAM works fine and now I can switch between multiple APPS without reloading!
@lifehackerhansol, Is there any plan to fix the cellular function for T295? Even though I don't use it often, I always want all the features to work properly.
If so, I can help with testing.
Thank you.

xperiazu21 said:
After I plugged in the headset and opened FM APP, the operation failed and it seems to be not working.
After updating to version 20230103, zRAM works fine and now I can switch between multiple APPS without reloading!
@lifehackerhansol, Is there any plan to fix the cellular function for T295? Even though I don't use it often, I always want all the features to work properly.
If so, I can help with testing.
Thank you.
Click to expand...
Click to collapse
Given I don't have the device, I do not want to blindly try to take a crack at the cellular function. So until I get my hands on one, I have no plans to support it.
I hope that is reasonable.
I'll check on FM in a bit. I'm not even sure if this device supports it, I saw the libraries and thought hmm, maybe.

So, I was wondering if there are any big differences between your rom and andy yan's GSI builds? (https://sourceforge.net/projects/andyyan-gsi/files/lineage-20-light/)
I have Lineage 20 running on the sm-t290 , rooted with magisk and it's running great. As in everything works fine. Does this one add something that the other doesn't?
Either way, I love to see development on this device, Thanks!

SunSlide said:
So, I was wondering if there are any big differences between your rom and andy yan's GSI builds? (https://sourceforge.net/projects/andyyan-gsi/files/lineage-20-light/)
I have Lineage 20 running on the sm-t290 , rooted with magisk and it's running great. As in everything works fine. Does this one add something that the other doesn't?
Either way, I love to see development on this device, Thanks!
Click to expand...
Click to collapse
The big difference is that this ROM isn't a GSI. It's specifically built for this device. i.e. what LineageOS should have been.
GSIs are very interesting in that you can simply load a generic image of a ROM onto any Treble-enabled device. It's very easy to do so as well. However, while tailor building a ROM for the device ends up being a lot of work, it ultimately ends up in a better experience at the end of the day as there will be edge cases a GSI doesn't always cover.
For now we're at 18.1 because it's the same release version as the stock ROM and I figured it'd be easier to start there. Am working on 19.1 right now, but my SSD just died so I need to go fix that first.

New build: 20230108
As of this build, we are LineageOS 19.1.
To dirty flash from 18.1 to 19.1:
Flash LineageOS.
Before rebooting to OS for the first time:
If you use gapps, flash Android 12 gapps
LineageOS recommends MindTheGapps: https://wiki.lineageos.org/gapps
If you use Magisk, then flash latest Magisk
If you use gapps and Magisk, then flash them in that order
Changelog:
Android 12L
FM Radio is dropped
Nothing in the stock ROM suggests that this device actually supports FM Radio, despite online specifications saying otherwise. There is no hardware abstraction layer present for FM Radio anywhere I've found.
This will be disabled until someone can confirm it does work on stock. In which case, I will attempt to dig deeper, but I'm not sure how far I will get.
Known issues:
SafetyNet doesn't seem to pass the CTS check.
Camera is not working. (hotfixed)
Available at DL link in OP.

Clean flash LineageOS 19.1.
The camera is working fine and seems to have no problems.
Sometimes the start-up animation of the app is not displayed.
There is also a missing animation in the settings.
Your browser is not able to display this video.

xperiazu21 said:
Clean flash LineageOS 19.1.
The camera is working fine and seems to have no problems.
Sometimes the start-up animation of the app is not displayed.
There is also a missing animation in the settings.
View attachment 5804899
Click to expand...
Click to collapse
Yeah, the camera wasn't working the first time I uploaded it. Worked fine after I fixed it quickly and reuploaded.
I'm uncertain if this settings thing is a bug or not. I wonder if other devices with low RAM also have this?

This tablet is the only low RAM device that I can flash to Android 12+.
But before I used LineageOS 20 GSI, I didn't encounter this problem. Maybe this is possible to fix?

Just flashed this to my T290, Wayyyy faster then stock rom. I haven't had a chance to play around with it to much yet. I can say so far it seems to be working amazing! good work!

New build: 20230115
Changelog:
USB file transfer (MTP) fixed by switching to basic USB HAL
OTA updates have been implemented (maybe) (possibly) (idk)
I consider this to now be fully functional hardware wise. Hope this sparks some new development across other developers with this device out there.
I now have OTA updates! Next build will (hopefully) show in the built-in updater app! (at least I hope that's the case.)

New build: 20230117
As of this build, we are LineageOS 20.0.
To dirty flash from 19.1 to 20.0:
Flash LineageOS.
Before rebooting to OS for the first time:
If you use gapps, flash Android 13 gapps
LineageOS recommends MindTheGapps: https://wiki.lineageos.org/gapps
If you use Magisk, then flash latest Magisk
If you use gapps and Magisk, then flash them in that order
Changelog:
Android 13
Performance upgrades:
Some kernel changes to improve performance (VDSO32 backport)
Various system services pinned in memory for UI responsiveness
Available at DL link in OP. While the built-in updater can download it, it will not allow you to flash from it directly. Use a custom recovery to dirty flash.
At this point I will start moving to monthly builds, and each build will have an Android security patch level uprev (unless someone reports an important bug, then I'll try to release right after fixing). I'll be moving on to figuring out how to get LineageOS recovery going.

Related

[ROM][Unofficial] LineageOS 13.0 for OnePlus 2 [06/01]

{
"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:
/*
* Your warranty is... still valid?
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
LineageOS is a free, community built, aftermarket firmware distribution of Android 6.0.1 (Marshmallow), which is designed to increase performance and reliability over stock Android for your device. LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review ( http://review.lineageos.org ).
Important:
This thread is for stock LineageOS 13.0 and any mods, kernels or Xposed framework will not be supported.
If features, options or code is NOT in the official source code, it will not be in my builds.
Recommended Firmware:
Most recent firmware for OOS 3.6.1 is recommended.
Known Bugs:
None
Installation:
Download the zip(s)
Install a compatible Recovery (TWRP recovery recommended)
Perform a nandroid backup of your current ROM (Optional)
Wipe data/factory reset
Flash LineageOS
Optional: Install the Google Apps addon http://opengapps.org/ ( I tested nano and stock pkgs)
Reboot
Note: Built in root is available in Dev Options, but I'd use magisk
Source code:
https://github.com/lineageos
Credits:
LineageOS Team & Contributors
Code Aurora Forum
Downloads:
AFH
How to enable Volte.
You can read the full instructions HERE
XDA:DevDB Information
LOS 13.0 Unofficial, ROM for the OnePlus 2
Contributors
monark88, LineageOS Team & Contributors
Source Code: https://github.com/LineageOS
ROM OS Version: 6.0.x Marshmallow
ROM Firmware Required: OOS 3.6.1
Based On: LOS-13.0
Version Information
Status: Stable
Created 2018-01-21
Last Updated 2018-06-24
I know some of you may wonder why even post something as old as marshmallow. I still get a lot of use from LOS 13, and have been building it for myself for a while. I figured I'd upload the latest with Jan security patches, for those who want it. Happy flashing.
Not sure about the support we'll get from LOS going forward. They never merged February security patch, but they may have just been busy. We'll see.
does it have hal3 with hdr and all that cool quality we used in marshnallow?
chxei said:
does it have hal3 with hdr and all that cool quality we used in marshnallow?
Click to expand...
Click to collapse
It does, HAL3 and hdr
I run mine with amplify, greenify, android n-ify, gravitybox, and alert slider app
monark88 said:
LOS 13.0 Unofficial, ROM for the OnePlus 2
Click to expand...
Click to collapse
wow, this is great!
thank you mate!
You can get volte by flashing the kenzo patches. Just saying.
I also built this ROM myself to which I had mentioned in another post. Good job!
Any chance you're able to build with release keys instead? This will then allow some apps (its quite minimal) to run correctly.
Woodzrul said:
I also built this ROM myself to which I had mentioned in another post. Good job!
Any chance you're able to build with release keys instead? This will then allow some apps (its quite minimal) to run correctly.
Click to expand...
Click to collapse
The download link now points to a signed version. You can download it here:
https://www.androidfilehost.com/?fid=673956719939814327
using 22nd Jan build since yesterday.
I missed so much the great customization that CMTE brings to LOS!
as far as I can see 'til now, there's no issue at all with your ROM.
excellent work, thank you!
utkarsh102 said:
You can get volte by flashing the kenzo patches. Just saying.
Click to expand...
Click to collapse
More info on this, please?
Kenzo is redmi note 3 iirc
Would the .zips work for OP2?
GuyGotMadNameGame said:
More info on this, please?
Kenzo is redmi note 3 iirc
Would the .zips work for OP2?
Click to expand...
Click to collapse
Yes. They will. Flash the patch1 zip, boot up the phone, wait 10-15 seconds until you start seeing that the com.android.phone has stopped working. Then go to recovery and flash patch2 zip, clear dalvik cache and reboot. Voila.
utkarsh102 said:
Yes. They will. Flash the patch1 zip, boot up the phone, wait 10-15 seconds until you start seeing that the com.android.phone has stopped working. Then go to recovery and flash patch2 zip, clear dalvik cache and reboot. Voila.
Click to expand...
Click to collapse
I'll add this to the first post
utkarsh102 said:
Yes. They will. Flash the patch1 zip, boot up the phone, wait 10-15 seconds until you start seeing that the com.android.phone has stopped working. Then go to recovery and flash patch2 zip, clear dalvik cache and reboot. Voila.
Click to expand...
Click to collapse
Thanks for this. I updated first post.
Does anyone know of any cm13 theme which properly themes all the essential apps?
This ROM has been a really good ride for the past month or two for me - very stable and actually there is not much new in Android 7.x which really matters. LineageOS unfortunately made 14.x unstable by reworking the kernel in the middle. It's ok for the most time but then some random event happens and it will drain your battery in few hours.
I think I will stay on this ROM assuming Android security patching still happens in future. Thanks monark88!
aiwan3 said:
This ROM has been a really good ride for the past month or two for me - very stable and actually there is not much new in Android 7.x which really matters. LineageOS unfortunately made 14.x unstable by reworking the kernel in the middle. It's ok for the most time but then some random event happens and it will drain your battery in few hours.
I think I will stay on this ROM assuming Android security patching still happens in future. Thanks monark88!
Click to expand...
Click to collapse
I've got a new build, but nothing is significantly changed. I've been working on a custom kernel for MM, with extra governors and upstream merges. I'm running this ROM myself, so you can bet when there is a security patch, I'll upload it for us all.
I'm with you on anything above android 6.0. When LOS 14.x kernel was reworked, I was on RR unofficial. I remember the drastic changes. I compiled this not soon after and have been on it since. I've watched on the forums as everyone has scrambled after HAL3, and balancing HAL3 with HDR (or the lack there-of) and all the non-sense that goes with it.
Meanwhile we've got manufacturer supported blobs and code for everything our phone was meant to do, in a nice stable OS.
If you're reading this, and thinking about trying it, just download the ROM, flash xposed (or use xposed magisk) and get Android N-ify, Amplify, Greenify, Alert Slider, and GravityBox. You'll be kicking it on the OP2 old school, updated, and stable.
That's right. Many people don't seem to be very methodical when testing new ROMs. Mostly noted on comments about battery life. I don't use my phone much as the majority of my daily work / comms happens on PC - so its easy for me to see changes when I update the phone. I don't use gapps either, so my testing is purely based on the kernel and the ROM performance. This ROM can go up to 5-6 days in idle / light usage, whereas the latest official LineageOS 14.x is probably around 4 days same use. Feel free to test. Same applies to boeffla-kernels, they consume much more battery on idle than the LineageOS stock.
I'm not a developer myself but it's easy to understand that all this hacking for newer Android versions than the source code provided by manufacturer, can very easily lead into problems. It could be ok, but unfortunately many people always think that the latest is always better. I think it's fair to say that new android versions just complicate the menus and slow down devices more than the useful features provided. As long as security is updated, I don't really see any need for Oreo in my phone.
It's nice to hear that you are also testing for new things in kernel, I might test them if provided as separate update.zip. However I assume most people using LOS 13 or your build are probably after stability.
Hold on right here...i need a minute to comprehend...so, basically, if i flash this, i will get the most stable android experience there is, it will most likely improve my battery live over N/O roms, i will have all the OOS 3.6.1 OP2 features working (including things such as slow motion, HDR and panorama), the latest security patch will be installed and the only drawback is that it will be a MM release? whats the catch ?
Jackill said:
Hold on right here...i need a minute to comprehend...so, basically, if i flash this, i will get the most stable android experience there is, it will most likely improve my battery live over N/O roms, i will have all the OOS 3.6.1 OP2 features working (including things such as slow motion, HDR and panorama), the latest security patch will be installed and the only drawback is that it will be a MM release? whats the catch ?
Click to expand...
Click to collapse
Lol, for the most part (and in my opinion) yes.
The catch is that if you like the latest cutting edge features, we don't have that built-in here. All we offer is a stable phone that has ALL of the features working in some form or another, without wondering what will break in the next build.
For the record, I still flash Oreo ROMS on MultiROM to stay aware, but I run this as a daily driver.

[ROM][8.1][A3 2016] ResurrectionRemix 6.2.1 for Galaxy A3 2016 | a3xelte | SM-A310xx

{
"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"
}
Galaxy A3 2016 | a3xelte | SM-A310xx
UNOFFICIAL | Android 8.1
Download: HERE​
Changelog:
Code:
[COLOR="Teal"]2019-02-08[/COLOR]
- Upstreamed new Kernel again from v3.10.61 to 3.10.108 for enhanced security and performance
- Fixed audio recording issue by not allowing to record with a bitrate below 48000 in the audio policy
- Updated stock vendor blobs from CRG1 to CRH1 for better security and stability (this time it mostly improved GPS)
- Fixed bluetooth calling
[COLOR="Teal"]2019-01-30[/COLOR]
- Initial release
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
Click to expand...
Click to collapse
Installation instructions:
1. Make sure you have TWRP installed on your device to be able to flash the rom.
2. Download the latest build from the link above and copy it to a place where you can find it later.
3. Optionally download GApps for using the Play Store and other Google related services from here: https://opengapps.org. Choose ARM as architecture and 8.1 as the OS version. The size of the GApps package is upon to you how much apps you want to have preinstalled. Copy this zip aswell to a place where you can find it easy later. If you download it with Chrome or with the Google Drive App it should be by default in the Download folder.
4. Turn your phone off and press Volume UP + Home Button + Power button at the same time until the splash screen appears. Then your device should boot into the recovery. There you wipe following partitions: Data, System, Cache, Dalvik if this is your first install. All of your installed applications get lost by this. Your photos, videos etc. won't get deleted if you haven't ticked the box for internal storage. As the kernel also supports F2FS i would change the filesystem for the cache partition from ext4 to f2fs for a better system performance. Now go to the main TWRP menu, click on install and go to the place where you have placed your zips and first select the rom and then click on the left button if you have downloaded the optional GApps package to add another zip to the queue. Now swipe the slider at the bottom to install and reboot the phone to the system. The first boot can take a while and after booting you could experience some lags because of the GApps initialization but they should disappear after some time.
5. Now you have successfully installed the rom and you're ready to use ResurrectionRemix on your device. Congratulations!
Bugs:
- VoLTE (isn't working on samsung devices and won't work anytime in the future too)
- Same as LineageOS 15.1
Credits:
@danwood76 for maintaining the a3xelte device tree
@Stricted for maintaining the common device tree
Contributors:
@Borduni
Source Code:
https://gitlab.com/dariotrombello
https://github.com/ResurrectionRemix
https://gitlab.com/Exynos7580
Version Information
Android: 8.1 Oreo
Kernel: Linux 3.10.108
Status: Stable
Stable Release Date: 2019-30-01
Created: 2019-30-01
Last Updated: 2019-02-08
reserved
Many thanks:good:
I would just like to thank @Borduni @danwood76 @Stricted and all the devs that are helping maintain our device and bringing us updated ROMs! This was a rom i was wishing for very much! Thank you for all your efforts and time dedicated for us.
4-core processor or 8-core processor?
If 8 core enabled, can we get 4 core enabled version?
Also thank you all of you guys for still developing for A310F users. I wish i can donate for you guys but PayPal is not avalaible in our country.
senemir said:
4-core processor or 8-core processor?
If 8 core enabled, can we get 4 core enabled version?
Also thank you all of you guys for still developing for A310F users. I wish i can donate for you guys but PayPal is not avalaible in our country.
Click to expand...
Click to collapse
Quad Core Kernel. I won't publish any of my new roms with Octa Core Kernel's because of the high battery drain.
You don't need to donate me anything. I don't even have set up PayPal :laugh:.
Borduni said:
Quad Core Kernel. I won't publish any of my new roms with Octa Core Kernel's because of the high battery drain.
You don't need to donate me anything. I don't even have set up PayPal :laugh:.
Click to expand...
Click to collapse
Thanks bro. I will try this rom tomarrow.
And i dont like Octa Core too. Phone overheats and battery drain is too much like you said.
Keep up that great work !
Does sound work in all apps? I've used three other 8.0 roms and they all recorded mic very quietly in apps like Snap and Insta.
hajdud said:
Does sound work in all apps? I've used three other 8.0 roms and they all recorded mic very quietly in apps like Snap and Insta.
Click to expand...
Click to collapse
This will be fixed soon, it's on my list
2019-02-08
- Upstreamed new Kernel again from v3.10.61 to 3.10.108 for enhanced security and performance
- Fixed audio recording issue by not allowing to record with a bitrate below 48000 in the audio policy
- Updated stock vendor blobs from CRG1 to CRH1 for better security and stability (this time it mostly improved GPS)
- Fixed bluetooth calling
As I see this rom audio recording is working fine right? I had another issue with L15.1 which was that I couldn't get faceunlock to work at all, it didn't even show up in the setings. It wasn't the gapps cause I use those same gapps on extendedAOSP and it worked. Also at some point the mic stopped working, etheir for calls nor audio recording. I'm on 14.1 now but it doesn't play flac natively and the music player I use doesn't support flac by itself, all the rest is great en 14.1. So, if anyone is kind enough to advice me about this ROM that'd be great, I'm getting a little tired of flashing, mostly because I need the phone for work during the day and the microphone dying is not cool XD Thanks in advance.
LucasNerv said:
As I see this rom audio recording is working fine right? I had another issue with L15.1 which was that I couldn't get faceunlock to work at all, it didn't even show up in the setings. It wasn't the gapps cause I use those same gapps on extendedAOSP and it worked. Also at some point the mic stopped working, etheir for calls nor audio recording. I'm on 14.1 now but it doesn't play flac natively and the music player I use doesn't support flac by itself, all the rest is great en 14.1. So, if anyone is kind enough to advice me about this ROM that'd be great, I'm getting a little tired of flashing, mostly because I need the phone for work during the day and the microphone dying is not cool XD Thanks in advance.
Click to expand...
Click to collapse
Most audio issues are fixed in the latest version.
RR should be as stable as my Lineage OS builds as it is based on my trees. Only current issue is buggy MTP but this will be mostly solved in our kernel tree soon.
RR-Pie-v.7.0.1 is coming soon
Hi,
(This is my first post on xda, so I'm not sure I'm doing it right. Tell me if I should do it differently so I learn)
I like this rom, and have used it in various versions of several devices, so I'm happy to see it is developed for this device too.
However, when i try to flash it to my SM-A310F, I get the error that this rom is for a3xelte, while my device is (blank space) .
I use TWRP v. 3.0.2.1 and have flashed the revolution OS rom with success. This rom works ok, but I just miss some the customizations and functionalities in RR.
-And also the lack of samsung software, which I use none of and just disable.
I general, I can install roms which are based on the stock samsung rom in some way or another (like the revolution OS), but not roms like RR, dotOS or lineages.
From Software settings (running revolution OS):
Baseband: A310FXXU2BPG6
Kernel version: 3.10.105-NOUGAT-ALX-0.0.2
So, do any of you clever people have a good idea why my SM-A310F is not considered worthy for RR? Is there a way to flash it anyway, or is this a hardware issue of some sort?
And thanks!
Bobbobelob said:
Hi,
(This is my first post on xda, so I'm not sure I'm doing it right. Tell me if I should do it differently so I learn)
I like this rom, and have used it in various versions of several devices, so I'm happy to see it is developed for this device too.
However, when i try to flash it to my SM-A310F, I get the error that this rom is for a3xelte, while my device is (blank space) .
I use TWRP v. 3.0.2.1 and have flashed the revolution OS rom with success. This rom works ok, but I just miss some the customizations and functionalities in RR.
-And also the lack of samsung software, which I use none of and just disable.
I general, I can install roms which are based on the stock samsung rom in some way or another (like the revolution OS), but not roms like RR, dotOS or lineages.
From Software settings (running revolution OS):
Baseband: A310FXXU2BPG6
Kernel version: 3.10.105-NOUGAT-ALX-0.0.2
So, do any of you clever people have a good idea why my SM-A310F is not considered worthy for RR? Is there a way to flash it anyway, or is this a hardware issue of some sort?
And thanks!
Click to expand...
Click to collapse
You need to update TWRP. Here you find the latest official build: https://eu.dl.twrp.me/a3xelte
And also you could do a baseband update. Flash the newest firmware for your country via ODIN and install TWRP and RR after that again.
I recommend you to use RR 7 (Android 9) instead of this. I haven't published a build since a long while.
Thanks so much for the very quick response! I will give both a try starting with updating twrp. I'm not sure where to look for the baseband update, but I will try to find it if twrp update does not work.
Bobbobelob said:
Thanks so much for the very quick response! I will give both a try starting with updating twrp. I'm not sure where to look for the baseband update, but I will try to find it if twrp update does not work.
Click to expand...
Click to collapse
You can use the tool samfirm (google it) or updato.com
Baseband updates can improve signal strength/battery life. But it is not necessary.
Thanks again, I really appreciate your help.
I'd love to try RR7, but I can't find the download link in the relevant thread (it says removed by OP) or in the RR homepage. Therefore I chose this version instead. Is RR7 available somewhere else.
https://forum.xda-developers.com/sa...m-rr-7-0-1-galaxy-a3-2016-a3xelte-sm-t3919153

[ROM][OFFICIAL][NIGHTLIES] LineageOS 17.1 Harpia

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 10 (Q), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Base source code is available in the LineageOS Github repo. And if you would like to contribute to the project, please visit our Gerrit Code Review.
Known issues:
....
Instructions:
Download the latest build, official TWRP (3.3.0 and newer)
Boot the downloaded TWRP via fastboot
Flash the latest build
Reboot
Downloads:
Unofficial build: SourceForge-CAN EAT YOUR CAT
Official Rom and recovery: LineageOS
Google Apps: OpenGapps
XDA:DevDB Information
LineageOS 17.1 Harpia, ROM for the Moto G4 Play
Contributors
jeferson1979
althafvly
Device tree
ROM OS Version: Android 10
ROM Kernel: Linux 3.10.x
Based On: lineage
Version Information
Status: Stable
Current Stable Version: 17.1
Stable Release Date: 2020-03-22
Created 2020-03-22
Last Updated 2020-03-22
Reserved
Always giving thanks to @facuarmo and @Akyanonimous for the great support
Help. i tried to flash this ROM and my phone have bootloop.
I was a long term user of Pixel Experience ( Android 9 / Pie) and enjoyed it's stability. As it is no longer maintained I thought I would try out some of the latest Android 10 / Q ROMs to see how they compared. I still kept the zip file for Pixel on my SD card by way of a fall back if I wasn't happy with the latest unofficial Android 10 ROMs.
I gave Havoc OS a try for a few days and to an extent I liked it with the ability to very much set up the ROM as you like with multiple customisation options. I , however, found that the overall experience wasn't very good with quite a bit of lag and some random crashes of apps etc. I am sure with future updates it will be a much better ROM and I may well give it another try out.
After Havoc I went back to Pixel Experience for a few weeks until the next unofficial Android 10 ROM was released. Thus far I have been very happy with Lineage 17 with no bugs , lag , crashes or issues at all thus far. The only slight grumble is that the music app widget is not really required on the ' 2nd page ' and indeed was just a big black blob. I deleted it straight away. I will probably continue to use this as my daily driver for some time to come and give thanks to @jeferson1979 and any other Devs who contributed for all their hard work and for us to be able to keep our old Harpia phones going with the latest android version.
Indiawallah71 said:
I was a long term user of Pixel Experience ( Android 9 / Pie) and enjoyed it's stability. As it is no longer maintained I thought I would try out some of the latest Android 10 / Q ROMs to see how they compared. I still kept the zip file for Pixel on my SD card by way of a fall back if I wasn't happy with the latest unofficial Android 10 ROMs.
I gave Havoc OS a try for a few days and to an extent I liked it with the ability to very much set up the ROM as you like with multiple customisation options. I , however, found that the overall experience wasn't very good with quite a bit of lag and some random crashes of apps etc. I am sure with future updates it will be a much better ROM and I may well give it another try out.
After Havoc I went back to Pixel Experience for a few weeks until the next unofficial Android 10 ROM was released. Thus far I have been very happy with Lineage 17 with no bugs , lag , crashes or issues at all thus far. The only slight grumble is that the music app widget is not really required on the ' 2nd page ' and indeed was just a big black blob. I deleted it straight away. I will probably continue to use this as my daily driver for some time to come and give thanks to @jeferson1979 and any other Devs who contributed for all their hard work and for us to be able to keep our old Harpia phones going with the latest android version.
Click to expand...
Click to collapse
How you installed this ROM? Because i flash with TWRP 3.2.1-0 (the last version for Harpía) and use ARM Gapps for Android 10 but dont boot (have bootloop).
Sakul94 said:
How you installed this ROM? Because i flash with TWRP 3.2.1-0 (the last version for Harpía) and use ARM Gapps for Android 10 but dont boot (have bootloop).
Click to expand...
Click to collapse
I have indeed installed the latest Lineage 17.1 Rom and it works great. I , too , have the latest TWRP and found it very straight forward to install the zip file for Lineage , with ARM GAPPS for Android 10 and the latest Magisk for rooting my device. I assume when flashing the Rom etc you did a clean install by doing an Advanced wipe of Davlik/ART Cache , System , Data and Cache before proceeding. Good luck and hope you are able to get it going.
Indiawallah71 said:
I have indeed installed the latest Lineage 17.1 Rom and it works great. I , too , have the latest TWRP and found it very straight forward to install the zip file for Lineage , with ARM GAPPS for Android 10 and the latest Magisk for rooting my device. I assume when flashing the Rom etc you did a clean install by doing an Advanced wipe of Davlik/ART Cache , System , Data and Cache before proceeding. Good luck and hope you are able to get it going.
Click to expand...
Click to collapse
Yes, i did every step to flash this ROM but no result. The phone have bootloop.
latest TWRP for harpia is 3.2.3-r1. find that here - https://forum.xda-developers.com/devdb/project/?id=16870#downloads
try that and see if it bootloops.
bacanos said:
latest TWRP for harpia is 3.2.3-r1. find that here - https://forum.xda-developers.com/devdb/project/?id=16870#downloads
try that and see if it bootloops.
Click to expand...
Click to collapse
Thank you very much. You are an genius.
@jeferson1979 Your roms are what a rom should be! I have never thought that android 10 can run this smooth in this tiny device. All Thanks to you. Rom is very stable and is best rom available right now after AEX pie which is again your offering.
Unlike past developers your focus is more towards usage and fixing things rather than pure compiling/half baked pieces and that's what old time developing was...
Thanks to keeping this device alive. I use it because of it's light and small and easy to carry.
Now the only thing remaining is- I guess SELinux.
Thanks for all the work, I will flash this later today and post my feelings. Would it be possible to make this an official build? I loved the automatic updates via OTA from the official builds.
The ROM works great, however SELinux is not enabled, would it be possible to enable it?
Sakul94 said:
How you installed this ROM? Because i flash with TWRP 3.2.1-0 (the last version for Harpía) and use ARM Gapps for Android 10 but dont boot (have bootloop).
Click to expand...
Click to collapse
Liteh said:
The ROM works great, however SELinux is not enabled, would it be possible to enable it?
Click to expand...
Click to collapse
you can manually set SELinux to enforcing by enabling the terminal shell in the Developer options and using the command, "setenforce enforcing"
this enables enforcing but i have no idea if the SELinux policy is written or doing what it needs to be doing, and this manual enforcing only lasts until reboot. does anyone know more on this subject?
Liteh said:
The ROM works great, however SELinux is not enabled, would it be possible to enable it?
Click to expand...
Click to collapse
Selinux is on mode permissive, but you can expect next update to be on enforcing mode, by now don't turn enforcing
jeferson1979 said:
Selinux is on mode permissive, but you can expect next update to be on enforcing mode, by now don't turn enforcing
Click to expand...
Click to collapse
That's great, I'll be waiting for the next update. After a day using it, I have to say that it is indeed a wonderful ROM, very fluid and responsive.
Flashed this ROM, till now everything works great. Thank you!
Gesendet von meinem GM1903 mit Tapatalk
jeferson1979 said:
Selinux is on mode permissive, but you can expect next update to be on enforcing mode, by now don't turn enforcing
Click to expand...
Click to collapse
Can you please also release Android GO variant of Lineage. Recently I have seen one Go device, and it was so smooth even with 1GB RAM. We have 2GB so I guess Android GO will improve responsiveness and battery life slightly? Please correct me if I'm wrong.
newinnov said:
Can you please also release Android GO variant of Lineage. Recently I have seen one Go device, and it was so smooth even with 1GB RAM. We have 2GB so I guess Android GO will improve responsiveness and battery life slightly? Please correct me if I'm wrong.
Click to expand...
Click to collapse
You will see some minor improvement at memory management, but we will loose in other side. Maybe we can do some tests
I agree with newinnov. In fact i think it should be nice for the LineageOS team to keep supporting older devices (like ours) officially but in Android GO form. It would keep millions of phones out of landfills.
In our case I think the benefits overcome the loses. At this point i'm sure all of us are using our g4p for bare minimun tasks like whatsapp, email, browsing, social networking, and such. Mostly no functionality-intensive apps. Given that all of that can be done with Android GO i don't think we would lose that much

[ROM][UNOFFICIAL][12] LineageOS 19 for Xperia X [FINAL]

{
"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:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
About LineageOS
LineageOS is a free, community built, aftermarket firmware distribution of Android 12, which is designed to increase performance and reliability over stock Android for your device.​​LineageOS is based on the Android Open Source Project, with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.​​All the source code for LineageOS is available in the LineageOS GitHub organization.​And if you would like to contribute to LineageOS, please visit our Gerrit Code Review.​You can also view the changelog for a full list of changes & features.​​Official LineageOS website : http://lineageos.org​About LineageOS Legal : http://lineageos.org/legal​
Important Information
1. This ROM operates without ODM images, just follow the installation instructions.​2. This ROM does not intended to support Google Camera, but you can try some mods.​​Downloads Links
LineageOS 19:​Unofficial: https://sourceforge.net/projects/loire-development/files/lineageos-19.1/suzu​​Google Applications (optional):​MindTheGapps: https://androidfilehost.com/?w=files&flid=322935 (Android 12.1 -> arm64)​XDA post about GApps: https://xda-developers.com/download-google-apps-gapps​​Recommended Recovery (optional):​TWRP 3.x: https://forum.xda-developers.com/-/-t3786431​
Flashing and updating
​Please install the latest version of TWRP to avoid further issues with recovery!​
LineageOS clean install:​
Download the latest build of LineageOS ROM
Full wipe and factory reset (recommended / backup to make sure not to loose data)
Flash the LineageOS ROM zip from the Recovery
Flash the GApps to have the Google Applications (optional)
Every additional zip you want to flash (optional)
Reboot
LineageOS update/upgrade:​
Download the latest build of LineageOS ROM
Wipe cache and dalvik cache
Flash the latest LineageOS ROM zip from the Recovery
Every additional zip you want to flash (optional)
Reboot
You can also update using the built-in Updater (requires at least TWRP 3.6.x or LineageOS Recovery)​
About the builds:
Kernel sources: https://github.com/Chippa-a/android_kernel_sony_msm8956​
Issues and reports
Report issues only if you are using the ROM kernel
If an additional mod is installed, make sure it's unrelated, and mention it
Make sure the issue wasn't discussed earlier in the threads
Grab a logcat right after the problem has occurred
(Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing)
If it is a random reboot, grab /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0
(Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
Also thanks to:
The LineageOS Team
The SODP Team
Everyone involved in working and testing
Contributors
Chippa_a
ROM OS Version: 12.x
ROM Kernel: Linux 4.9.x
Version Information
Status: Stable
FEATURES AND ISSUES
Boot: Ok
Bluetooth: Ok
WiFi: Ok
WiFi Hotspot: Unknown
RIL - Phone - Data: Ok
GPS: Ok
Camera: Ok
Camcorder: Ok
Lights: Ok
MicroSD: Ok
Accelerometer: Ok
Compass: Ok
Gyroscope: Ok
QTI sensors: Ok
Touchscreen: Ok
FM Radio: N/A
Fingerprint: Ok
Vibrator: Ok
Microphone: Ok
Audio & music: Ok
Bluetooth audio: Ok
NFC: Unknown (HCE: Unknown)
Kernel: Ok
Graphics: Ok
3D Rendering: Ok
Clock: Ok
DRM: Unknown
Offline Charging: Ok
USB: Ok
USB Tethering: Unknown
USB OTG: Ok
Encryption: Ok
SEPolicies: Enforcing
It's amazing that msm8956 platforms have this day. Thanks a lot!
I have installed from lineageos 9 to this Version without GAPPs...
Now I wanted to install the gapps, but I no longer have twrp on it. Where can I find a suitable twrp version? as APK, because I don't have a picture on my smartphone with adb reboot bootloader.
What can I do?
Edit: Error: This GApps pkg is for Android 12.0.x ONLY Please download the correct version for your ROM: 12 (SDK32)
Edit1: I have now Installed 17.1... you can ignore this Post or Delete...
Thanks @Chippa_a for your effort. I've installed and it is really a snappy and responsive release: wifi, lte, voice calls and fingerprint are working fine.
I've tried to enable device encryption, procedure completed but then got stuck in reboot loop.
At startup:
- black screen with text that device cannot be trusted because unlocked
- white screen with sony logo
- lineage OS loading screen
- <repeat>
I've installed TWRP 3.6.1_9.0: Are anyhow meaningful the logs from there?
They're attacched, just in case. If there's any other procedure I can do to obtain more meaningful data, please link it to me and I'll try to do it, prior wiping system and reinstall.
thanks for this beautiful ROM
The rom is great but has anyone experienced a bug? Everytime I play a recorded video my speakers make a high pitched noise, a noise that sounds like a radio is out of tune. That noise totally roasted my speakers, had to swap them. Not sure why that happend, other than that the roms is really amazing. Is there any possibilitiy for the gapps to cause this? I was using Mind The Gapps.
speakers some times not work
New build is available!​
April 2022 security patches
Fixed critical audio related issues
LineageOS upstream updates and fixes
Note: To make the new app icons take effect, just clear the data of Trebuchet application.
You can install the new build manually or using the built-in Updater (requires at least TWRP 3.6.x or LineageOS Recovery).
What about GCam?
is it possible to add support?
Just noticed that my back camera doesn't focus, anyone faced this problem?
SalamiPUNCH said:
Just noticed that my back camera doesn't focus, anyone faced this problem?
Click to expand...
Click to collapse
Chippa_a said:
Camera: Partially ok (main camera: broken focus)
Click to expand...
Click to collapse
This is a known issue, but it has been fixed and will be included in the upcoming build.
bluetooth audio works fine,tested with my aptx headphone。But front camera can not take photos with accurate color.
As far as I have tested, the rom is working pretty well so far, however I'm getting a pretty strong screen retention effect for some reason. Calibrating all colors to 80% in LiveDisplay settings fixes it, but makes the phone feel stuttery as hell. This also happens when enabling Night Light, regardless if LiveDisplay settings were modified or not.
I attached some logs. Hope they're of help to you.
Chippa_a said:
Please install the latest version of TWRP to avoid further issues with recovery!
Click to expand...
Click to collapse
Chippa_a said:
You can also update using the built-in Updater (requires at least TWRP 3.6.x or LineageOS Recovery)
Click to expand...
Click to collapse
Please read these notes carefully and do not report any issues with older TWRP.
Also it is not recommended to reboot from recovery (to recovery) if you have wiped the system partition (OS is not installed), or you will get stuck with TWRP splash screen as well. This issue will be investigated and probably fixed.
Thanks!
Good colleagues, could someone tell me about their experience with this rom, what works and what doesn't.
I'm about to install it but I want to be sure if it's worth it compared to the stock rom, as well as if the quality of the camera drops a lot.
thanks :3
I love this rom, i use it since two weeks and I don't have had any issues with it! Camera quality is still very good, as expected for a custom rom.
So, I can highly recommend it, it's the best thing you can do for your Xperia X!
Pay your device it's last respects and install this rom
jediknight23 said:
I love this rom, i use it since two weeks and I don't have had any issues with it! Camera quality is still very good, as expected for a custom rom.
So, I can highly recommend it, it's the best thing you can do for your Xperia X!
Pay your device it's last respects and install this rom
Click to expand...
Click to collapse
Aren't you having any issues with LiveDisplay and/or night light? What about screen retention (fake burn in)? I'm loving the rom and the Material You design, but those 2 problems are ruining my experience.
Btw, battery life is quite good in this rom.
Absolutely no screen retention!
I don't use LiveDisplay or night light, so no problems on my device
Is there any way to get video stabilization on this ROM? Also magisk doesn't show the modules that are available for download through the magisk app, modules fails to flash even if I download it from the magisk site and try to flash it. Is there any way to flash the modules? I wanted to flash the Pix3lify magisk module. Any help would be great
Edit: I found out why magisk doesn't show the modules so that's not an issue, but installing the module is, maybe I'm doing something wrong?

[GSI][13] LineageOS 20 "Light"

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android, 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. 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 Gerrit Code Review.
Click to expand...
Click to collapse
MUST-READ BACKGROUND - Android 13 and the two approaches:
As some of you already know, due to various reasons, @phhusson , who kickstarted the GSI trend and committed to it over the years, is backing out from future development - there won't be any AOSP 13+ builds or patches directly from him. He did most of the heavylifting for fixing bugs and implementing features, and selflessly supported more than his AOSP GSIs and more than devices he own. For the situation of GSIs today, we owe him a big thank-you.
Since PHH made up his mind, a number of existing builders incl. myself have formed the TrebleDroid organization, with PHH himself helping us in technical issues. TD will forward-port PHH's final patches (v415) onto Android 13 and attempt to fix new issues. This is still a new and ongoing process, but if done right, will have compatibility and feature-completion on par with past PHH-based GSIs.
Meanwhile, I'm aware that at least I myself am not as capable as PHH, and won't be able to look after the myriad of patches and devices, esp. legacy ones (pre-A10). Therefore, inspired by @PeterCxy , I'm taking a different approach - start over from AOSP's generic gsi_* target, add in the minimum amount of fixes needed for my own devices, shaking off much of the legacy burden in the process and making it easier for myself to follow/maintain. This is a radical, selfish approach that by definition won't work for legacy devices anymore, and won't work as well as PHH-based GSIs that you've come to love either. However, I've fixed it up to my own daily-driver standards, and I figured it should still be of use to many. For now, I call this the "light" approach.
Disclaimer:
No flashing instructions will be offered. If you're here in this forum, you should know what you're doing.
No guarantees that everything would work. This is a GSI, bugs are bound to happen.
The selfish nature of this approach means I can and will ignore certain bugs as I see fit. Deal with it or kindly go try something else.
Download:
https://sourceforge.net/projects/andyyan-gsi/files/
Scroll down for the naming rules of variants.
Compressed as .xz archives - extract first.
Stuff on GitHub (builders-only):
Most things should be self-explanatory. Not the cleanest code, but should help if you need some clues.
lineage_build_unified - my unified script for building
lineage_patches_unified - my unified patches for building
device_lineage_gsi - my device tree that extends native generic targets
Thanks to:
The LineageOS team - helping me out even when they don't offer GSIs themselves
@phhusson - shaped the treble community, and even the "light" approach uses his fixes/infra extensively
@PeterCxy - inspired me with his personal-use GSI, and coded critical fixes such as sysbta
...and more
Donate?
https://paypal.me/AndyCGYan
This post documents my progress on top of the native generic targets.
Already implemented/fixed:
Built-in root (PHH-SU)
Device overlays
Screen resolution & refresh rate - improved upon PHH's implementation
Alternative audio policy (Qualcomm)
Disable soundvolume effect (Qualcomm)
Alternative backlight scale (MediaTek)
resetprop/copyprop tool
In-call audio
BT audio
VoLTE on Qualcomm/MediaTek pre-S vendors
VoLTE on Qualcomm/MediaTek S vendors - new, backported to PHH-based
GAPPS - using MindTheGapps for now
Securized - "on-demand" reversible toggle
Disable A2DP offload
Alternative audio jack detection
Signature spoofing - limited to priv-app for the same security reason as in PHH/TD-based
Optional FP lockout (set persist.sys.fp.lockouts.disable to true to disable timeout on failed FP attempts)
Built-in PHH-SU app for *S variant
Override minimum brightness
Override navbar availability
Exfat
In-call audio on Snapdragon 8 Gen 2 (SM8550) and newer Qualcomm devices
To be implemented/fixed at a later time:
VoLTE on Motorola Qualcomm S vendors - situation did not improve with stock T, lowering priority
Known but will not implement/fix:
Compatibility with legacy (pre-A10) devices, A-only, VNDKLite
FOD/UDFPS (commonly known as in-display fingerprint) - not skilled enough for it and not interested either
MediaTek kernel BPF bug (#9)
VoLTE on non-Qualcomm/MediaTek vendors
Samsung/Huawei oddities
Notes:
I now have a rather taxing day job, and can't devote nearly as much time/effort into this as I did as a student, or even a year ago.
No A-only or VNDKLite builds. These are concepts that don't exist natively.
GAPPS builds are offered as-is without guarantees. As a Chinese I can't/won't help with GAPPS/SN issues - please help each other out.
ADB is intentionally insecure, even on first boot (turned on by default and no authentication needed). GSIs are more fragile compared to device-specific custom ROMs, both on first boot (no-boot issues) and on subsequent boots (after tuning certain Treble settings), and I insist that no-auth ADB is a must-have for debugging and general fail-safe.
Signature spoofing (MicroG) is supported, but only for priv-apps. This is a security consideration from PHH.
Refer to #9 for explanation/workaround of an MediaTek-specific kernel bug that causes no internet.
TD-based LOS20 will be offered as well, but at a later date - I've only made a first test build of it today. At its current state though, it doesn't work as well as PHH-based A12 either, so don't get your hopes up too high.
Good job!
Yay!!!
yay!!!! thank you!!!!
Thank you very much for your great work. I've been waiting for this for a long time.
I ran into a very, very strange bug.
I have a Qin F21PRO (MT6761).
This model has two sub-models:
4GB RAM + 64GB storage
3GB RAM + 32GB storage.
My device is
4GB RAM + 64GB storage
But after flashing this GSI, it is shown that there is only 32GB storage.
edit: after factory reset via twrp, i getting 64GB storage
There's a known kernel bug in some recent MTK devices that breaks BPF badly, resulting in broken networking features since Android 13, and no-boot since r11 (Google decided to tighten the check). I've reverted the no-boot, but the actual bug can't be fixed from platform-side.
This affects LOS in that it has Restricted Networking Mode turned on by default, and with the bug in place, apps cannot be added to the allow list, resulting in no internet in even system apps.
If you own an MTK device and notice such a thing, as a temporary workaround, you can turn the feature off manually with:
Code:
adb shell settings put global restricted_networking_mode 0
If you're on the gN variant, SetupWizard would also have no internet, so just skip the setup entirely, turn on USB Debugging once you're in the OS, run the above, then re-initiate the setup from the status bar.
As for a more persistent fix - thanks to @Rortiz2 , there's now a way to manually patch the kernel binary, however I no longer have an affected device for testing this. Feel free to try out the patcher here.
There might be other broken networking features that I'm unaware of. In the long term, the one true solution is to upgrade to a newer vendor base, hoping that the OEM has merged the kernel-side fix.
AndyYan said:
TD-based LOS20 will be offered as well, but at a later date - I've only made a first test build of it today. At its current state though, it doesn't work as well as PHH-based A12 either, so don't get your hopes up too high.
Click to expand...
Click to collapse
There is no Navigation key or gesture options, How to do it?, I can install it on my Samsung device but without navigation, no home/back key
redymedan said:
There is no Navigation key or gesture options, How to do it?, I can install it on my Samsung device but without navigation, no home/back key
Click to expand...
Click to collapse
Ugh, a Samsung oddity. I didn't implement the force overide switch - if a non-Samsung hits this as well, I might.
If you know how to, try adding "qemu.hw.mainkeys=0" to /system/build.prop. These images are EXT4 unshared blocks, so as long you have verity disabled and root, you should be able to edit/save it.
redymedan said:
There is no Navigation key or gesture options, How to do it?, I can install it on my Samsung device but without navigation, no home/back key
Click to expand...
Click to collapse
AndyYan said:
Ugh, a Samsung oddity. I didn't implement the force overide switch - if a non-Samsung hits this as well, I might.
If you know how to, try adding "qemu.hw.mainkeys=0" to /system/build.prop. These images are EXT4 unshared blocks, so as long you have verity disabled and root, you should be able to edit/save it.
Click to expand...
Click to collapse
Same problem with Redmi Note 10 (mojito)
@redymedan @spider1163 Can you give me the full result of "getprop" from shell? Paste it to e.g. Pastebin.
D
AndyYan said:
Ugh, a Samsung oddity. I didn't implement the force overide switch - if a non-Samsung hits this as well, I might.
If you know how to, try adding "qemu.hw.mainkeys=0" to /system/build.prop. These images are EXT4 unshared blocks, so as long you have verity disabled and root, you should be able to edit/save it.
Click to expand...
Click to collapse
Done! I just added "qemu.hw.mainkeys=0" to /system/build.prop and the navigation keys enabled. also in Gesture menu "System navigation" option appeared. It works now on my Galaxy A50, Thanks
Other problem: Google Play Protect certified "This device isn't Play Protect certified"
amazing! waiting for gapps variant now.
redymedan said:
Done! I just added "qemu.hw.mainkeys=0" to /system/build.prop and the navigation keys enabled.
Click to expand...
Click to collapse
Thanks for confirming it's that simple! Given that "light" won't look back on legacy devices, I think I'll just enable this prop globally in the next releases.
This is exactly what I was waiting for, it will be fun to test on my old Huawei P smart 2019 with Android 9 vendor so let's see what happens. Any result of this experiment will be shared here.
THX for your great work.
But how can I install gapps?
I've tried to install BitGApps with Magisk as a Magisk module, but it says 'insufficient partition size'.
There's no working TWRP for my device
michael_hamada said:
THX for your great work.
But how can I install gapps?
I've tried to install BitGApps with Magisk as a Magisk module, but it says 'insufficient partition size'.
There's no working TWRP for my device
Click to expand...
Click to collapse
you wait... ..
THX for your great work. but auto brightness not working Is this expected behavior?

Categories

Resources