[GSI][13] LineageOS 20 TrebleDroid-based
- Thread starter AndyYan
- Start date
D
Deleted member 12393571
Guest
Andy Yan, 100% gratitude for this project, the choice and ability you give back to the user, us, is greatly appreciated.
Im running the lineage-20.0-20230507-UNOFFICIAL-arm64_bvN.img.xz on my s A53 5G. It feels so good and its so snappy. I love it.
The thing is, bluetooth doesn't function as it should, i can connect to all devices without issue, but when i play songs, they start skipping and there is no sound going out of the speaker.
I used to have a build running from september 22 that had no issues with this, same kernel same device. I've been digging into this and i found a couple of option that told me to enable hd audio or enable/disable bluetooth A2DP hardware offload etc. The thing is, these are greyed out in de dev options. I can't acces them or play around with them.
Don't know is this has anything to do with it: For normal heaphone detection i had to enable: use alternate audio policy to get my sam to detect my headphones, plays absolutely perfect since.
Any advice is greatly appreciated, i couldn't find the sept22 build on your page, could you maybe reupload pls ?
Thanks a bunch to everyone involved! Happy to see this community as active as it is.
Have a good one
Im running the lineage-20.0-20230507-UNOFFICIAL-arm64_bvN.img.xz on my s A53 5G. It feels so good and its so snappy. I love it.
The thing is, bluetooth doesn't function as it should, i can connect to all devices without issue, but when i play songs, they start skipping and there is no sound going out of the speaker.
I used to have a build running from september 22 that had no issues with this, same kernel same device. I've been digging into this and i found a couple of option that told me to enable hd audio or enable/disable bluetooth A2DP hardware offload etc. The thing is, these are greyed out in de dev options. I can't acces them or play around with them.
Don't know is this has anything to do with it: For normal heaphone detection i had to enable: use alternate audio policy to get my sam to detect my headphones, plays absolutely perfect since.
Any advice is greatly appreciated, i couldn't find the sept22 build on your page, could you maybe reupload pls ?
Thanks a bunch to everyone involved! Happy to see this community as active as it is.
Have a good one
This thread was created on 11-11-2022, for LOS 20.
And on this page, the oldest archived builds date back to.....11-11-2022:
Coincidence? I think not. It would appear that the September 2022 builds you are looking for simply dont exist. Unless you're looking for LOS 19 builds that date back even further.
Speaking of these things....
The option to Remove Telephony Subsystem - is that supposed to work?
I use the build on a tablet that doesn't have any kind of cellular communications - only wifi - but the option doesn't seem to do anything...
The option to Remove Telephony Subsystem - is that supposed to work?
I use the build on a tablet that doesn't have any kind of cellular communications - only wifi - but the option doesn't seem to do anything...
It works on Samsung, not sure about other OEM devices. It essentially removes the mobile data aspects. In other words, no calls, texts, or internet connection that relies on mobile data. Wifi will still work. However, it doesn't remove things like the stock dialer/messaging app.
I have tried it, and it does work. But I have no reason to use it since both of my devices have active SIM cards.
This option probably won't work on non-vndklite gsis, since their system partition can't be mounted as RW, so the telephony file can't be deleted. You would have to use a Magisk module to systemlessly delete it.
Interesting.... I'm using a vndklite gsi - but nothing seems to happen when I hit that option. I still get the disabled mobile data settings where it just says "No SIM"...
Hello i run LOS 20-20230507-UNOFFICIAL-arm64_bvS on a xiaomi redmi note 11, and i can't send any SMS or MMS in 4G, only 3G mode (By changing prefered network) works well...any idea ?
jonpjingleheimler
Senior Member
I confirm i can acces internet with 4G and send MMS in 3 G
D
Deleted member 12393571
Guest
Hey thanks for your reaction, made me realize the date is mm/dd and not dd/mm. Realized i was using light instead of td. Installed the latest LOS 20 light version and all works fine now. Congrats on this great build!This thread was created on 11-11-2022, for LOS 20.
And on this page, the oldest archived builds date back to.....11-11-2022:
Coincidence? I think not. It would appear that the September 2022 builds you are looking for simply dont exist. Unless you're looking for LOS 19 builds that date back even further.
jonpjingleheimler
Senior Member
Hello, from a former lurker of this particular GSI thread.
I was using this particular GSI for a while until inexplicably, it stopped working for me out of nowhere. My phone's a "Oneplus Nord N10 5G" (which doesn't have a lot of custom roms or recoveries but does have at least Magisk) and I was using this gsi's version of Android 13 some time ago until, for some reason after I updated it, the display started to stutter a lot.
(I'm a newb when it comes to XDA so I apologize for any lack of extra information.)
I then reverted back to stock for some time and after a while, decided to return back to this GSI while thinking that it may have been some bug that may have been patched.
After flashing the GSI, the phone did boot up and was responsive to touch.
The boot animation went well and I came to the setup screen.
It was at this point the phone display started stuttering whenever I'd touch the screen (and sometimes would do so without). The setup process was stuttering throughout the entire process.
At the end of the setup, after I pressed on the final button at the end of the Lineage Setup, the screen finally went black and the only sort of response I could do was to hold the power button, which showed me a minimal power menu.
I am now back on my stock rom and have finally decided to post about this "bug".
Now, the bug could be due to my phone acting up, but I never found out the reason as to why this happened and still happens whenever I decide to flash the GSI. I've tried other GSIs which did work (with some issues), though, not all of them worked after flashing.
Also, thought it was worth mentioning: while lineage 19.1 DOES work for my phone, it is a bit unstable and has some issues..
Thanks in advance.
I was using this particular GSI for a while until inexplicably, it stopped working for me out of nowhere. My phone's a "Oneplus Nord N10 5G" (which doesn't have a lot of custom roms or recoveries but does have at least Magisk) and I was using this gsi's version of Android 13 some time ago until, for some reason after I updated it, the display started to stutter a lot.
(I'm a newb when it comes to XDA so I apologize for any lack of extra information.)
I then reverted back to stock for some time and after a while, decided to return back to this GSI while thinking that it may have been some bug that may have been patched.
After flashing the GSI, the phone did boot up and was responsive to touch.
The boot animation went well and I came to the setup screen.
It was at this point the phone display started stuttering whenever I'd touch the screen (and sometimes would do so without). The setup process was stuttering throughout the entire process.
At the end of the setup, after I pressed on the final button at the end of the Lineage Setup, the screen finally went black and the only sort of response I could do was to hold the power button, which showed me a minimal power menu.
I am now back on my stock rom and have finally decided to post about this "bug".
Now, the bug could be due to my phone acting up, but I never found out the reason as to why this happened and still happens whenever I decide to flash the GSI. I've tried other GSIs which did work (with some issues), though, not all of them worked after flashing.
Also, thought it was worth mentioning: while lineage 19.1 DOES work for my phone, it is a bit unstable and has some issues..
Thanks in advance.
Last edited:
There's a bug with TD based GSI roms on the Legion Y70 that breaks Call audio (no call audio in or out in calls). For project elixir this happens with all versions after 3.6. I saw this reported with the latest evo x gsi rom as well. Where should I report this issue?
Also is the TD based rom, or the light rom expected to have better compatibility with phones like the Legion Y70 (ignoring the call bug)?
Also is the TD based rom, or the light rom expected to have better compatibility with phones like the Legion Y70 (ignoring the call bug)?
"Disclaimer:
No flashing instructions will be offered. If you're here in this forum, you should know what you're doing."
Keep jealously guarding your secrets and let the rest of the world die stupid, you lousy rats!
No flashing instructions will be offered. If you're here in this forum, you should know what you're doing."
Keep jealously guarding your secrets and let the rest of the world die stupid, you lousy rats!
jonpjingleheimler
Senior Member
Buddy... There are so many caveats to every device that putting instructions here would likely screw one of us up. Search your device type Lineage os after that. Hit enter. Folks can be pretty helpful here but they are not spoon feeders.
Set up IMS/VoLTE properly in Treble settings.
This sounds like something crashing hard in the background repeatedly - a logcat would perhaps be useful.
Neither - right now it's a known issue that Moto/Lenovo QCOM S vendor devices have spotty or no SMS reception, and this can easily break daily driving. I've even bought a device just to look into this, but so far I don't know how to solve it within a GSI environment (device-specific ROMs have more room to work with).
Just because this is a generic image doesn't mean there's a generic enough way of flashing it everywhere. I've handled dozens of devices for GSI purposes so far, and many have curious traits that one would never know until a hands-on. You can blame me for being lazy and not summarizing findings on my devices on PHH's wiki, but I won't take blame for not offering an all-encompassing guide that "just works".
Thanks for the response. Turns out the call audio bug is only some versions of TD based rooms. The very latest ones like the newest version of TD builders AOSP, and your LOS roms (both light and TD based) have call working. Project Elixir in particular has it in 3.7 and 3.8.
I wish I knew how to port roms for devices. The stock rom would be pretty great if it didn't have so many network related issues (data doesn't work for me on reboot until I eject and insert the sim again, MMS does not work at all because the apn settings are both bunged and locked down, etc).
Some GSI roms are pretty buggy on this device but a few work pretty good, LOS so far has been good and solves most of the major issues but it is at the loss of things like dc dimming, stock camera, bypass charging, etc. If there was a way to make a better version of ZUI with fixes that would be nice too.. Project elixir worked the best for me outside of the no call audio, it was a little less laggy and took to magisk modules like pixelify better (LOS didn't take to all of it properly).
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
2I've decided that I'm skipping this month's update to LOS20 Light/TD. Please read #290 in Light for details.
At least tell what the apps are? Although in #2 I did state that I can't help with GAPPS/SN, I might still try... when I have time.
SF provides statistics; I doubt torrents would allow me to accumulate accurate statistics?
There also isn't a compelling reason on my side. I need faster and more convenient uploads, and SF offers SFTP which runs at a good rate over VPN.
I've diffed patches before/after the dates you mentioned, there are BT-related patches, but are either dormant (only activates on command) or applies to specific vendors.
If you've pinpointed dates on TD AOSP, please tell me the dates (these are more precise than my monthly updates, you now). If you're fed up with my incompetence/inactivity, try contacting PHH too (the TG group might get you more attention).1
Issues powering off from where? TWRP? Android?
If the partitions in your super partition don't have shared_blocks, you should be able to mount it this way from TWRP terminal:
mount -o rw,remount /
mount -o rw,remount /system_root
This of course assumes you have a super partition.
As for Magisk, just patch your stock boot.img, flash with Odin from download mode.1
Never seen this behavior on any gsi that I've ran on both of my Samsung devices.1
Try another gsi. Probably same behavior on others though, most gsis share a lot of source code. If a bug exists in one, it's probably also in others released around the same date. But some bugs/issues are device-specific. Not much you can do except file a bug report and wait.
The best place to file a bug report is here, it's where most gsis derive their code from:
1 -
33
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.
Earlier, inspired by @PeterCxy , I took the "light" approach, which starts over from AOSP's generic gsi_* target and adds the minimum amount of fixes needed for my own devices, intentionally leaving many legacy devices behind. For more details about it, visit its own thread.
Meanwhile, 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. This thread contains LOS builds based on TrebleDroid's collective work, which supposedly suits legacy devices, Samsung, etc. better than "light".
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.
MUST-READ - reporting bugs:
If you want to report a bug, then you MUST try reproducing on an AOSP reference build of around the same date from TrebleDroid, and ONLY proceed to report here when it's specific to this GSI. This filters out bugs common to all TD-based GSIs, which you should still let me know, but it might not be mine to fix. I might silently ignore your report if you skip this.
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
- The LineageOS team
- @phhusson - shaped the treble community, and still takes care of TrebleDroid at a higher level
- @PeterCxy - coded critical fixes such as sysbta
- The TrebleDroid builders
- ...and more
https://paypal.me/AndyCGYan9Notes:
- 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.
- I now daily-drive "light", so I can't test TD-based builds as extensively as before. For the same reason, I likely won't build/upload any TD-based "personal" build either.
- While most >=A13 GSIs out there are going to be TD-based, some perform better than others - some devs have their own patches that haven't been merged into TD yet. I myself will stay close to TD's raw patchset as much as possible, without picking patches from others left and right. If you find another GSI working better, don't just complain - try to narrow down which ones, and the intersection of them might be an unmerged patch that, if approved, would be merged into TD and benefit all.
- 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.
- On *S variants, install PHH-SU and you'll get basic root for apps, good for devices that don't play well with Magisk or when you don't need modules.
- Refer to this post for explanation/workaround of an MediaTek-specific kernel bug that causes no internet.
6Updated all variants with July security patches. [Insert obligatory backup-and-test warning here]
I just realized that I haven't included PHH-SU app in *S (while I did over at Light) - this has been corrected.
@Jonny - although I still very much doubt that the uname change is related to the alarm, adding it back is trivial, so now it's back.6Updated all variants with Android 13 QPR2 and March security patches. [Insert obligatory backup-and-test warning here]
As usual with "feature drops", things can change or break majorly.
Fixed in-call audio on Snapdragon 8 Gen 2 (SM8550), tested on OnePlus 11, should pave the way for future QCOM SoCs as well. Users of other SM8550 devices like Xiaomi 13 and RedMagic 8 Pro/+ might want to try this out too. Also pushed to TD upstream, so in case you don't like LOS, it's still coming to your favorite TD/-based GSI later.
Imported some SN fixes from HentaiOS - GAPPS users should now get CTS profile match as well.
Fixed videos sometimes getting stuck after pausing and resuming, thanks @Cozzmy13 for working it.
Fixed two-pane layout in Settings for tablets - set an appropriate density then force stop Settings for it to take effect.
And finally for builders, starting this month LOS has moved to Git LFS for hosting their Chromium webviews. Please re-init the repo with "--git-lfs" flag BEFORE syncing again or you will hit errors. If you already have a bad sync, clear the residue and re-init:
Code:rm -rf external/chromium-webview/prebuilt/* rm -rf .repo/projects/external/chromium-webview/prebuilt/* rm -rf .repo/project-objects/LineageOS/android_external_chromium-webview_prebuilt_*
