yashsingh1/xdaforums huggingface dataset:
[Touch Pro, Fuze Accessories] pandaboyy:
Just what I'm looking for. If you have better instruction, I'll do it
[Touch Pro, Fuze Accessories] The Jack of Clubs:
http://www.webnetta.com/2008/12/27/hack-connects-t-mobile-g1-to-ipod-dock/

i was thinking about someway to do that. it would be easier if there was a premade extusb (port on touchpro, android, other htc phones) to the ipod dock for sale.
[Touch Pro, Fuze Accessories] Kraize:
True. I've heard talk that a mass production is being started, but I dont think it'll be anytime soon.

Basically I just looked into this. Later today, I'll be looking into actually making it.
[Touch Pro, Fuze Accessories] arthurbrownleeiv:
This is what is needed to finally justify the way too easy to break non-standard plug.

Audio adapter? Eh, okay, I've used it... A few times... I'd rather use the bluetooth audio.

What would be nice, is for this idea to take off, and also to be able to have a dock like the zune has with the video out. Hell, at that point I'd honestly forget why I ever carried my zune.

Subscribing. Not because I have the time or ability to make this, but I want to see what I can do to help the idea take off.
[Nothing Phone 1] xeCloud:
Anyone facing similar issues whereby when you lock your screen while in a particular app (ie Facebook, chrome, alarm app). But when you unlock your screen, it unlocks into the home page instead of continuing where you left off in the app itself.

Nothing Phone 1

Latest 2.5.2 stable build

Nova Launcher Prime

Note: I tried with stock launcher. Also same issue
[Nothing Phone 1] EllieCat:
It a a bug and there is currently has no fix (try some methods in this thread)

Help! Phone returns to home screen after unlocking.

Whenever any app screen times out it's gets locked but after unlocking the phone goes back to homescreen instead of staying on the last used app. Using Nova launcher. Wondering if this issue is for all users or just me. I have gome through...

xdaforums.com
[OnePlus 12] lloydsw:
So I was following this guide here: https://xdaforums.com/t/android-14-...ll-have-magisk-restore-images-option.4641667/ which I'd used twice on my OP11 with no problem. The problem I NOW have is using it on my fresh-out-of-the-box OP12, I wasn't paying close enough attention to the directory in the adb shell & instead of writing the unpatched images to the two init_boot partitions, I wrote them to the boot partitions. Now the phone just keeps booting into fastboot, sitting there for a minutes then rebooting. It won't power off or go into recovery from fastboot. If someone with the NA version could provide the a boot img, that would be great.
[OnePlus 12] Canuck Knarf:
This for US
[OnePlus 12] lloydsw:
Thanks so much! I'm back up & running.
[OnePlus 12] igslove:
Could you please Global root.img make one too, thank you
[OnePlus 12] Canuck Knarf:
You mean init_boot ...for root???
[OnePlus 12] igslove:
magisk patch file。
[OnePlus 12] flandolf:
just patch it yourself
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
MUST-READ BACKGROUND - "Light" vs. TD-based:

TD-based, as its name implies, is built upon the full TrebleDroid patchset, and has better compatibility with legacy devices, Samsung, etc.

"Light" includes much fewer patches that are known useful first and foremost for my own devices (and modern devices in general), so that I understand and maintain it slightly better. It's also my daily driver and test field.

For more background info, read respective sections of LOS20 "Light" and TD-based threads, where this differentiation started.

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

Thanks to:

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

Donate?

https://paypal.me/AndyCGYan
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Notes:

I now have a rather taxing day job, and can't devote nearly as much time/energy into this as I did as a student, or even a year ago. Expect one-way communication - I might go silent for a month or more when life takes priority.

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.

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.

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 LOS20 "Light" #9 for explanation/workaround of an MediaTek-specific kernel bug that causes no internet.

Refer to LOS21 "Light" #17 for a workaround of SMS reception issue on Qualcomm S vendors, necessary for Motorola devices but also helpful for others.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Initial builds are based on TD patches as of 20240130 and January security patches.
[Treble-Enabled Device Development A/AB ROMS] stanley321:
Huge thanks for your hard work!

Device: Xiaomi Pad 5 Pro 12.4 (dagu)

GSI: lineage-21.0-20240201-UNOFFICIAL-arm64_bgN.img

Just dirty flashed from 20 to 21!

With Light, I've got no Bluetooth audio, but with TD, Bluetooth audio is working!

Report 1: in TD, Webview is somehow disabled by default will cause app to crash. Can be enabled by

pm enable com.android.webview

Report 2: com.tencent.soter.soterserver and org.mipay.android.manager included as system app. I guess these are not needed if you don't live ln China.
[Treble-Enabled Device Development A/AB ROMS] Canbeit:
Wow I was randomly curious about Lineages 21 GSI ROM and came here to check, such lucky timing. Nice work!
[Treble-Enabled Device Development A/AB ROMS] jack_shelack:
Awesome work! Can't wait to practice compiling it as I just finished building LOS20, going to try building with tablet_seeker's script next.

Thanks again!
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
I believe it's part of your vendor.

Repos for LOS21 (Light/TD-based) haven't been uploaded yet. If you use someone else's script/patchset, expect a ton of failed patches...
[Treble-Enabled Device Development A/AB ROMS] skills14:
Updated my Samsung T510 no issues, thanks for doing A64 roms its appreciated
[Treble-Enabled Device Development A/AB ROMS] Canbeit:
I have this same tablet running GSI lineagos 20, did you dirty or clean flash it?
[Treble-Enabled Device Development A/AB ROMS] Marinkovicc:
Hey so i flashed this and it works awesome! Everything works except for sim cards. The phone recognizes both sims but i cant do anything with them. They are unavailable. Also i cant reboot phone without connecting it to pc, otherwise it keeps bootlooping. My device Is Galaxy A12 (A127F Exynos variant).
[Treble-Enabled Device Development A/AB ROMS] skills14:
There were issues initially so wiped and clean flashed, all working spot on now mate
[Treble-Enabled Device Development A/AB ROMS] Marinkovicc:
Also i wanted to ask, when update is available how do i update it without losing any data and having to set up system again?
[Treble-Enabled Device Development A/AB ROMS] Klangerzeuger:
Flash the Update with TWRP or Fastboot, as well es you flashed your gsi.

Nothing needs to be wiped during the update.
[Treble-Enabled Device Development A/AB ROMS] Marinkovicc:
Alright thanks. Now i just need to fix problem with SIM cards.
[Treble-Enabled Device Development A/AB ROMS] Goryna:
Hi!S=

Tablet Samsung Galaxy Tab S6 SM-T865

Why didn’t I find photo password protection?

Russian SIM works.

I did not find the application clone function. Data transfer is enabled manually.

Root got his license.

View attachment 6063811
[Treble-Enabled Device Development A/AB ROMS] Deleted member 12801425:
Hey, sorry for asking multiple times this question but do someone has a workaround for this? I'm using this GSI on my main device and i like it so much but to keep it i need to have access to my sim card. I also wanted to mention that it sometimes doesn't recognize sim card at all like it's not in the phone. I need to restart the phone then but after that sim card is detected but mobile network is not available and card is unusable.

Btw i needed to open new account here cuz my google account will be deleted so i created new one.
[Treble-Enabled Device Development A/AB ROMS] peppet:
Hi, are all 4 speakers working?
[Treble-Enabled Device Development A/AB ROMS] Goryna:
Only 2 bottom ones. Returned to stock.
[Treble-Enabled Device Development A/AB ROMS] gfellow:
I have successfully updated my device from LOS 20 to LOS 21. The installation and setup went smoothly.

However, the device occasionally switches to Qualcomm Crashdump mode after standby mode.

If the WLAN is switched off or flight mode is activated, the problem does not occur.

This problem did not occur with LOS 20. I would appreciate some help as I'm a bit stumped at the moment.

The affected device is a Lenovo Xiaoxin Pad Plus (TB J607F).
[Treble-Enabled Device Development A/AB ROMS] xavier.miller:
Hi!

I tested lineage-21.0-20240526-UNOFFICIAL-arm64_bgN

- on a Medion Mediatek-based tablet : DSU OK, update system partition OK, seems running fine (wifi, keyboard, apps), will test it the next days (this is a device for testing)

- on a OnePlus Nord N100 : DSU: AOSP keyboard crashing, unable to setup wifi password ; tested https://github.com/ponces/treble_aosp/releases/tag/v2024.05.09 (arm64-ab-vanilla flavour): same AOSP keyboard crash.

For my OnePlus Nord N100, I will watcth the TrebleDroid AOSP releases and test them until they run on it, then go for your LOS version ;-)

glad I managed to use DSU loader to test those images :)

anyway, thank you very much for your huge integration work, @AndyYan 👍
[Treble-Enabled Device Development A/AB ROMS] tennyleaz:
Just dirty flash from 0424 to lineage-21.0-20240526-UNOFFICIAL-arm64_bgN.

Dual pane mode is back!
[Treble-Enabled Device Development A/AB ROMS] m0zz:
hello everyone, tried to flash 0526 on my motorola g8 plus and stuck in a bootloop. (fresh stock and patched vbmeta)

last working gsi was from february.
[Treble-Enabled Device Development A/AB ROMS] Themjbrand:
Same here
[Treble-Enabled Device Development A/AB ROMS] temporarium:
I thought you were leaving... Perhaps an apology to Andy would be appropriate 😉
[Treble-Enabled Device Development A/AB ROMS] Themjbrand:
I'm sorry @AndyYan for my words I'm glad that you are supporting by providing monthly update quarterly and new versions after seeing i decided to wait until the solution comes
[Treble-Enabled Device Development A/AB ROMS] larina3315:
I would like to thank @AndyYan for the amazing work he/she has done, my Xiaomi RN13 4G (sapphire) finally feels like a proper, powerful phone with the lineageOS GSI image, instead of feeling like a 50$ budget android with 2GB RAM when it was running on MIUI/HyperOS.

Everything works almost perfectly except the fingerprint sensor, which is entirely broken, but I personally don't use fp.

There is a bug (?) where the screen will go completely black when I slide the brightness slider all the way to the left, or set brightness to 0%, is there any fix for it, or anyway to set minimum brightness percentage ?

Also, has there been any update on the SMS reception issue for newer QC chips ? The SD685 5nm in my RN13 4G is affected too.

The workaround https://xdaforums.com/t/gsi-14-lineageos-21-light.4653433/#post-89312621 works fine but is cumbersome to do, I also need to wait 2mins instead of 30s after boot.
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
I believe we've never guaranteed / tried making VoNR universally work before... VoLTE is spotty already.

For now, Sammy devices just don't have VoLTE on any custom ROMs, be it GSI or device-specific. This might change in the future - you'll want to keep an eye on PHH's FLOSS IMS, maybe even join its testing group.

You could just skip the SUW and/or install a keyboard you prefer - remember, ADB is up by default.

No prob, it's totally fine to ditch this for other GSIs. Even if not for bugs, LOS is kinda bare in features anyway, so people tend to pursue customization-rich ROMs.

Could probably be clamped by writing a correct device overlay.

QC/MTK IMS being closed source, I can do very little with my knowledge. Device-specific ROMs use a technique called "telephony injection", but even that isn't guaranteed to work.

As for the workaround, if you wield dual SIMs, it's said that toggling off/on the affected SIM is enough to work.
[Treble-Enabled Device Development A/AB ROMS] xavier.miller:
Thanks @AndyYan, I will try it
[Treble-Enabled Device Development A/AB ROMS] divinnng:
Is there any plan to support automatic adjustment of screen brightness based on ambient brightness in the future?

Andy帅哥，谢谢你关于5g通话的建议，加入了phh的group。自动亮度也是有类似解决方法的吗？
[Treble-Enabled Device Development A/AB ROMS] BolognaTown:
where i find vbmeta.img?
[Treble-Enabled Device Development A/AB ROMS] Themjbrand:
@BolognaTown in your stock rom
[Treble-Enabled Device Development A/AB ROMS] Juggalo23451:
For my Smt510 I get a boot loop. Is this because the the device is to old I assume 🤔
[Treble-Enabled Device Development A/AB ROMS] Themjbrand:
Like what type of bootloop does it shows lineage os not animation or just samsung
[Treble-Enabled Device Development A/AB ROMS] Juggalo23451:
It shows samsung the reboots again
[Treble-Enabled Device Development A/AB ROMS] Themjbrand:
I also got the same results you can try los20 if you want it also runs very well
[Treble-Enabled Device Development A/AB ROMS] BolognaTown:
thank
[Treble-Enabled Device Development A/AB ROMS] larina3315:
idk if it's a bug, but when trying to copy files from my laptop to my phone with LOS21 TD GSI, the transfer ends when the phone display is off for some time.

does anyone know of a solution/workaround ?
[Treble-Enabled Device Development A/AB ROMS] Virteal:
Hello, I have a phone Doogee S68 PRO. Lineage 17.1. on this phone worked fantastic without any problems. Version 18.1. had one peculiarity. I could not call anyone, but everyone else reached me without any problems. So I switched to another ROM, but there were problems with that one, the phone would randomly reboot on its own under heavy load. So after a long time I went back to this ROM, specifically TD-based (lineage-21.0-20240526-UNOFFICIAL-arm64_bgN.img.xz), because it promised better compatibility with legacy devices. Only wifi works without problems. Phone calling, bluetooth doesn't work, and unfortunately the keyboard crashes, so in order to use the phone at all, I had to disable the system keyboard and install Hacker's keaboard on the phone. So I would like to ask for some help to get at least the telephony working for a start, I will skip the bluetooth, but if I could get the bluetooth working as well, I would be very happy of course. I have the stock firmware if that helps and it is also freely available on the internet. Alternatively, if you could write me where I can get a custom kernel that would work with this phone? The phone has a Mediatek Helio P70 processor (MTK6771 chipset). I don't know how difficult it is to customize firmware for each phone, I have a degree in IT, I don't know anyone from my area who could teach me such a thing, but I would like to be able to do it. Are there any drivers available in the phones similar to a computer or are they just in the kernel? Thank you for every answer.
[Treble-Enabled Device Development A/AB ROMS] Themjbrand:
Did you installed ims apk
[Treble-Enabled Device Development A/AB ROMS] Virteal:
Yes. But unfortunately, nothing has changed.
[Treble-Enabled Device Development A/AB ROMS] BolognaTown:
how give this command with Heimdall?

fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
[Treble-Enabled Device Development A/AB ROMS] rw_on_xda:
you're talking from Samsung SM-T510 ?

if yes:

no bootloop here !

- install the lastest stock

- install @Magendanz LOS20

- let it boot

- boot to TWRP recovery

- factory reset and format /data

- install @AndyYan LOS21

you need a keyboard app, cause the buildin crashes

I installed:

Simple Keyboard | F-Droid - Free and Open Source Android App Repository

Simply keyboard and nothing more

f-droid.org
[Treble-Enabled Device Development A/AB ROMS] chi0:
I want to say, can Red Magic 8pro run this custom ROM
[Treble-Enabled Device Development A/AB ROMS] Themjbrand:
Maybe try it out once 🤔
[Treble-Enabled Device Development A/AB ROMS] chi0:
It has been two years since the release of the Red Devils 8pro, and I am looking forward to having someone create a custom ROM
[Treble-Enabled Device Development A/AB ROMS] Peter12205:
Any tester who has tried the latest version of Android 14 from lineage os 21 td on their Samsung a03s SM-A037X, I want to make the jump to the latest version that Andy released, but I'm afraid of losing everything by getting stuck on the loop.

postscript, maybe this should go to the lineage os 20 td forum, but for some reason the CFE apps or bank apps when using the latest version of Android 13 from LOS 20 by Andy Yan close automatically and always give an error, but on Android 14 they work fine, there are no closures or anything like that and I install the N variant on both, which is the one that does not contain super user access, is there any way to prevent this error from happening?

I'm from Mexico, I don't know if that helps.
[Treble-Enabled Device Development A/AB ROMS] xavier.miller:
Simple Keyboard from F-Droid is working in DSU mode, the ROM seems fine.

I updated my OnePlus Nord N100, a OnePlus Nord N10 and the 2nd Mdiion tablet to you 20240526

4 devices up and running latest LineageOS 21 TD :cool:
[Treble-Enabled Device Development A/AB ROMS] DoogyRev:
Is there an issue with the USB on lineage-21.0-20240217-UNOFFICIAL-arm64_bvN?

I am running it on an iPlay 50 mini and it can't detect USB sticks, etc. It does charge but doesn't show charge notifications.
[Treble-Enabled Device Development A/AB ROMS] esalmot:
Anyone successfully runs LOS21 on Infinix Note 8 ? I got bootloop, so gotta go back to LOS20 for now.
[Treble-Enabled Device Development A/AB ROMS] cyber180:
I'm running lineage-21.0-20240526-UNOFFICIAL-arm64_bgN without issues on the iplay 50 mini. Battery notifications and usb storage devices show up as expected.
[Treble-Enabled Device Development A/AB ROMS] DoogyRev:
QPR2 breaks several other things for me like Quickswitch and my favourite app. Otherwise I would move to that version.
[Treble-Enabled Device Development A/AB ROMS] stopsmokingweed:
I bet there will be no more keyboard issues in the next build.
[Treble-Enabled Device Development A/AB ROMS] Themjbrand:
Waiting for June security patches 😁
[Treble-Enabled Device Development A/AB ROMS] rfresh:
I saw someone post message mentioned June security patch fixed VOLTE issue

Sent from SM-S918U1 using ReLabs
[Treble-Enabled Device Development A/AB ROMS] stopsmokingweed:
Usually after dealing with CalyxOS Michael Bestas continues with LineageOS.

Soon...

https://review.calyxos.org/q/topic:%22jun24%22+status:open
[Treble-Enabled Device Development A/AB ROMS] Themjbrand:
@AndyYan is face unlock going to be implemented in next builds?
[Treble-Enabled Device Development A/AB ROMS] リェンーゆく:
@AndyYan hi, can you kindly please remove or make GMS hooking toggleable? Google had banned most of the old devices' fingerprints to use to bypass Play Integrity's DEVICE check, so using third party Magisk module like PIF would be more advantageous here since it is updated frequently. Even though PIF is able to override the GMS hook, however, someone is recently able to pass the PI's STRONG check without even touching GMS by patching framework.jar. The GMS hook should be disabled since the fingerprint from the old device lacks the ability to pass STRONG, making it interfere with the framework.jar patching.
[Treble-Enabled Device Development A/AB ROMS] Eula13:
anyone here using this gsi was able to root successfully using apatch? I get a bootloop when trying to do so...
[Treble-Enabled Device Development A/AB ROMS] mrspeccy:
I have successfully built a GN variant of the Lineage 21 Light GSI according to the instructions on https://github.com/AndyCGYan/lineage_build_unified . The build date was June 20. I was also successful in building it with a self-signed key to obtain Device Integrity with PlayIntegrityFix.

Since the light variant does not work on all my devices, I would like to repeat the procedure with the full TD variant of Lineage 21, using the branch https://github.com/AndyCGYan/lineage_build_unified/tree/lineage-21-td (as of June 22). I used a fresh folder to initialize the repository and to download the build scripts and patches. However, the build command bash lineage_build_unified/buildbot_unified.sh treble 64GN fails with the error

Do I have to check out a specific commit of LineageOS or the patches?
[Treble-Enabled Device Development A/AB ROMS] Stelios333:
I tried to build the TD variant too and got a similar error:
[Treble-Enabled Device Development A/AB ROMS] AndyYan:
Status update.

For the past 3 weeks, I've deliberately kept myself away from XDA, and ROMs as a whole. After returning from 8-12hrs of coding at work, I don't want to look at code anymore back home, heck I don't even want to know what's broken, for fear of distracting myself from the already complex headaches at work.

Now the IRL stuff has settled down some, but a quick read tells me that Google again broke stuff with QPR3; compound that with the WIP signing builds issue, and it's certain that I'll have to skip June and aim for late July.

I find it harder and harder to keep up with this mess - not just me, many other TD builders have burnt out and quit / thought about quitting. To me, no amount of donation or external motivation can overcome these, the only factor keeping me going now is my personal fleet of devices that I want to customize beyond stock.
[Treble-Enabled Device Development A/AB ROMS] Medionato:
Andy, you've been doing such a great job as a part-time maintainer for so long that giving up seems unimaginable. But there is also a life outside of GSI-LOS builds! I'll be patient and take this opportunity to thank you for the working builds from February that allow me to keep my nearly 6 year old Unihertz Titan up to date and running like a good old BlackBerry PassPort. Thank you so much!!!