Hi there, it would appear that downloads for LOS19-20 are missing from sourceforge, is it a problem on my end or is someone else seeing the same thing?
[GSI][13] LineageOS 20 TrebleDroid-based
- Thread starter AndyYan
- Start date
Scared me too, but on second inspection, seems to be a site display issue, as the files are still there when viewed via FTP (for uploading). Many other people have filed this issue in SF support already, we just gotta wait.
Here are some instructions: https://github.com/phhusson/treble_experimentations/wiki/Xiaomi-Redmi-Note-10-Pro--Pro-Max
the manual dd method is neither safe not straightforward.
Better use fastbootD (which is mainly the part of a recovery).
Google would tell you can run it with "reboot fastboot" from an Android.
I disagree. dd is only unsafe for people that don't know what they're doing. I've been using it for years and have rarely made a mistake, except in the cases of typing errors. It's just a tool, if used wisely and correctly, nothing bad will happen. How do you think I flash all my GSIs?
I generally only use Samsung devices, which usually don't have a functional fastboot mode. So even if I wanted to recommend fasboot, it's not an option for me personally, and I have very little experience with it.
Thank you to all the devs. This TD based release is the most stable for my Xperia 1 III (BC72). The camera is working and no high pitched audio issues in MS-Teams and VoIP. 'Alternate audio policy' option fixed VoIP and 'disable stereo support on VoIP' fixed MS-Teams for me.
With the light version, camera wasn't able to save images and freezes. Also, MS-Teams has high pitched audio even with 'alternate audio policy' toggled on.
I'm one happy camper now! Keep up the good work!
With the light version, camera wasn't able to save images and freezes. Also, MS-Teams has high pitched audio even with 'alternate audio policy' toggled on.
I'm one happy camper now! Keep up the good work!
The stock camera fully works for you? For me, trying to use the rear camera made the app crash, but front camera worked fine. I also tried a few 3rd party camera apps, all working 100%. So it's just the camera app bundled into LOS that has a problem.
Under "light", neither stock nor Sony's Photo Pro camera worked. With TD, both stock and Sony have no issues using front/rear/wide angle. I haven't tried gcam yet.
Ok. I never tried light, only the "regular" TD version. The reason being, @AndyYan has stated that light are personal builds that are custom tailored to his needs. I don't want that, since what he considers optimal may not be good for everyone else.
Maybe the terminal app isn't present at all? That's the only thing I can think of. If it's not there, you can always use Termux or whatever.
Hello, I would like to take this opportunity to thank you. I have repaired a Huawei P10 from a completely destroyed condition with cheap spare parts. I was a little disappointed at first, because the several system images ran poorly or not at all. At last I had installed Lineage OS 19. This stuttered and there were WLAN aborts. Now I have installed the Lineage OS 20 image and it runs flawlessly. The performance is good and there are no problems. I hope such projects will continue forever to give old devices a second life instead of throwing them away.
EDIT:
Huawei P10 still WIFI Disconnects after 2 Minutes turning screen off. Checked the logs and found this issue reported 3 years ago:
github.com
Working workaround:
Activate adb debugging as root in dev options and start adb as root on your pc:
$ abd root
$ adb shell
$ echo 1 > /proc/sys/net/ipv6/conf/wlan0/disable_ipv6
Then WIFI stays connected after you turn the screen off.
EDIT 2:
The workaround i mentioned is just temporary. It works till you reconnect to the WiFi or reboot. Disabling Ipv6 on your router makes it work but then some services might not work for you which rely on IPv6.
Since its TrebleDroid based i tried to install the TrebleDroid Android 13 GSI. In the TrebleDroid GSI the bug is also present. Its not a specific LineageOS problem.
EDIT:
Huawei P10 still WIFI Disconnects after 2 Minutes turning screen off. Checked the logs and found this issue reported 3 years ago:
WiFi disconnects after the screen is turned off · Issue #27 · enesuzun2002/LineageOS-Releases
If I turn off the screen, the wifi connection will be disconnected after a few minutes. Not sure if always, but almost every time This is present in 2020-04-18 and 2020-01-21 Builds. I have SM-G925...
github.com
Working workaround:
Activate adb debugging as root in dev options and start adb as root on your pc:
$ abd root
$ adb shell
$ echo 1 > /proc/sys/net/ipv6/conf/wlan0/disable_ipv6
Then WIFI stays connected after you turn the screen off.
EDIT 2:
The workaround i mentioned is just temporary. It works till you reconnect to the WiFi or reboot. Disabling Ipv6 on your router makes it work but then some services might not work for you which rely on IPv6.
Since its TrebleDroid based i tried to install the TrebleDroid Android 13 GSI. In the TrebleDroid GSI the bug is also present. Its not a specific LineageOS problem.
Last edited:
Is it safe to upgrade from an existing installation (lineage-20.0-20221111-UNOFFICIAL-arm64_bgN-vndklite-secure.img) to the new version (lineage-20.0-20230115-UNOFFICIAL-arm64_bgN-vndklite.img)?
I would update via fastboot flash system lineage-20.0-20230115-UNOFFICIAL-arm64_bgN-vndklite.img.
Of course I would like to take over my existing data incl. the GApps and Magisk.
Would this be the right way?
Would there be any other steps necessary?
I would update via fastboot flash system lineage-20.0-20230115-UNOFFICIAL-arm64_bgN-vndklite.img.
Of course I would like to take over my existing data incl. the GApps and Magisk.
Would this be the right way?
Would there be any other steps necessary?
Just wanted to ask, in the Phh Settings there is an "icon pack" option, how do I exactly add packs to it? I downloaded one from Google play that didn't work. Do I have to flash them? I tried googling for an answer but couldn't find anything.
You can dirty flash with fastboot and keep user data and apps intact. Obviously, don't wipe user data. Just unhide Magisk before you do so and rehide after you're done. When left hidden, you may end up with multiple instances.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
3
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".3
Unfortunately, Play Store is a necessary addition to MicroG. And it's otherwise the only not open source Google app i include. It's pretty much the only way to buy apps or make in-app purchases. And some apps check their licenses to make sure they're not pirated. Without PS, this isn't possible, not without resorting to other apps/methods that coincidentally are forbidden for discussion by XDA rules.Lecture you? Dude, by installing just one Google app after your MicroG exhbition all that you said above failed down deep in the water so better revise your thinking from ground up
If "revise your thinking" means "switch back to GApps" or "buy an iPhone"....no thanks. If I'm just going to play by the accepted rules that Google and the manufacturers push, then this means that I should only run stock ROMs, always keep bootloader locked, etc. No to that too.
On this, we can agree to disagree, and that's the end of this line of conversation, I'm drawing the line by deciding it's not worth discussing with you anymore. It all started because you asked "Why not just flash G variant than?" I interpreted this as you not being aware of MicroG, or why some would choose it over GApps.2
You probably debloated too much. There's not much of a point in doing so, LOS is very clean, even the GApps builds. If you want a gsi that doesn't need debloating, go for Phh's AOSP vanilla builds. No fluff, just raw Android. And its' bugs will be 99% the same as this LOS. For GApps, use vndklite and flash MindTheGApps on top, if you have TWRP.It's strange really, flashed week ago or so and still no stats. We'll keep on looking but at least I know it's me and not for rest of you guys,
Oh, gotta say I debloated a ton of apps from it so I may exaggerated a bit lol2@syneoa: I suggest reflashing the gsi, then using this to debloat:
Magisk Module Systemless Debloater
Magisk Module Systemless Debloater Download...
forum.xda-developers.com
It doesn't really delete anything, so if you debloat too much, just edit your config file and reflash the mod zip. Anything you've "deleted" will be back.
You can also do real deletion without a module, but then it will be harder to put something back if you make a mistake.
For deleting mobile data stuff, I guess you missed the "remove telephony subsystem" option in Phh Treble Settings, Misc menu. -
25
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/AndyCGYan6Notes:
- 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 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_*5Updated all variants with January security patches and in sync with TD 20230104. [Insert obligatory backup-and-test warning here]
During my CoV downtime, A13 QPR1 happened and TD-based had a lot of changes as well, which accumulated to this month and I had to update more patches than expected (way more than "Light" - lower maintenance is why I made that in the first place). I might've made oopsies along the way, so I don't feel quite confident about this batch, and you should exercise extra caution.
Some users have reported that securize bootloops their device, and the current "integrally securize" approach means they can't boot up even once. This month I've changed it yet again to "securize on-demand", which is similar to how you securize on PHH/TD-based (a toggle in Treble Settings), but reversible and doesn't require SU.
For new users who are unsure about whether securize might bootloop your device, please turn on USB Debugging and Rooted Debugging below it, and if/when you do hit a bootloop on the next boot, you'll have a rooted ADB shell available to you, from where you can toggle off manually:
For users who are already on a gN build, be sure to toggle it on and reboot right after you update!Code:adb root adb shell setprop persist.sys.phh.securize false adb reboot
Properly fixed exfat for Samsung/Sony, tested on the one Sammy I still own.
