yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] sukimdennis:
Feedback on the soldering points on the DAB adapter...when I write solder it again, then I should solder both and not just one...a bit too much force and it looked like this.

I was able to save it and re-soldered it like the other one.

Feedback on the ATTB antenna. Long story short, I couldn't get it to work properly and switched back to the Eightwood. I suspect that the ATTB antenna simply receives too well, including all the interference, but I can't use it like that at the moment.

And now long story, I laid the cables in all directions but as soon as the roof liner was refitted, the reception was gone, for whatever reason. One option would have been to shorten the cables, which I did with the Eightwood, and lay the cables in the same way as with the Eightwood, but I didn't have the right crimp connections. So that came out and the Eightwood went back in with a few minimal changes to the cable routing.

Before:

Now:

The ferrite core is just for the good feeling.

It was noticeable that no matter which cable or wiring harness that had nothing to do with the antenna or wasn't even connected like the old inactive antenna cable, touched or moved in any way, the reception jumped. So I simply removed the old antenna cable because I had the feeling it was causing interference. I don't think it was, but I didn't care. I was just pissed off.

The stain is coolant from the VW. So my diesel is not leaking.

The only positive thing about this was that the DAB adapter is now within reach, behind the A-pillar trim on the passenger side, and it can be replaced without loosening any screws, so I can at least test the active and passive without moving the cable.

Before that, the adapter was under the roof liner but also on the passenger side near the A pillar. The old antenna cable can also be seen in these pictures.

First impression, but I really have to test this again, one adapter reacts positively to my body in terms of signal strength and the other negatively. I can't make more precise observations on the behavior of both adapters until two weeks from now. There's still some space behind the trim, so I'm open to further experiments.
[Android Head-Units] TorstenH:
I tested two different audio isolators withouth positive result.
[Android Head-Units] sukimdennis:
I came across something interesting.

At least with this cable the shield is connected to ground on both sides and I think it will be the same with the long cables.

PCB is out of this Adapter.

If I'm not completely mistaken, the following situation arises for me.

If additional shielding is used with aluminum foil or something else, there will be additional ground points because the adapter also has 2 shield ground connections, at the input and output. The antenna base also has a thick ground point and the shield is connected there too. In total that makes several shield ground connections.

Not to mention that the circuit board looks as if one or two shields have been forgotten or simply rationalized away.

I can now see at least 2 further starting points. Add the missing shielding and find a single central ground point, which could prove to be quite difficult.
[Android Head-Units] TorstenH:
Might be worth a try:
[Android Head-Units] Jetblack31:
Hello everyone,

I did some tests today to try to improve the DAB quality :

My set-up :

-DAB USB Stick : the one with a black rectangular metallic casing

-I use one of the stock antenna + inline amplifier. The antenna is printed in the rear wind shield (Renault Megane 3).

Test 1: I put a T-bias (from mini circuits, very good quality) between the DAB adapter and the antenna. So I can increase the voltage supplied to the inline amplifier with a battery (low noise voltage source) ==> nothing changed (received signal is not better)

Test 2: I improved some of the solderings of the stick PCB ==> no changes

Test 3: I put 2 capacitors (100 nF and 1 nF) in parallel with the power supply of the stick ==> no changes

Test 4: I grounded the DAB adapter metallic casing ==> no changes

Test 5 : I disconnected the printed antenna from the inline amplifier and put a simple wire instead : DAB radio is received with nearly the same quality

Test 6 : I disconnected the printed antenna and the amplifier and put a simple wire as a basic antenna (with no amplication) ==> DAB radio is received and quality can be better than with the stock configuration, in particular when the wire is vertical, i.e. aligned with the polarisation of DAB.

My conclusion : first thing to improve now : antenna + amplifier connected to the DAB USB stick. They seems to be the main weak point of my setup.

Jetblack
[Android Head-Units] cleverdicky:
So what make / model rod antenna did you use? It isnt always just the type of antenna but the design / quality matters a great deal.
[Android Head-Units] Scale&Hardwarebox:
I got this antenna:

DAB+GPS 12V antenna

I've been using it for 3 weeks now and I'm very happy. Almost interference-free reception.

The problems with houses with disruptive WiFi signals are gone. The quality of the antenna also seems very good. The base is made of soft silicone which adapts well to the roof and seals well.

The built-in GPS receiver works perfectly and navigation runs without errors.
[Android Head-Units] brodzik:
I just got myself Mekede M7 plus and I get signifianctly better reception. I don't know if it has anything to do with the actual headunit or maybe cable management but I just wanted to share that now I have reception comparable to a factory unit in my other car.
[General Questions and Answers] stevep:
Hi everyone

About every three(ish) years when I change my Android phone - usually Samsung - I go through the ritual of transferring everything from the old to the new. In recent times, SmartSwitch has made that a lot easier and quicker, although sometimes, I do a 'clean' install and start from scratch. I've developed a productive workflow, but there are a few tasks that still seem to take ages to complete.

One of those tasks is transferring email accounts. I have quite a few that I manage through the Gmail app, and one of the 'chunks' of data that doesn't get picked up by SS is all my email settings - passwords/server settings/signatures etc. I'm not worried about the emails themselves - it's just the 'settings'. I have about 10 separate addresses across multiple providers, and it's a real balls-ache to have to set each one up manually. I wondered if there's an ini/xml or 'something' file somewhere that holds all this information? I'm not into rooting my phones, so that might restrict what's doable.

Thanks, in advance! Steve
[General Questions and Answers] xXx yYy:
AFAIK you can export emails from Gmail using Google Takeout:

Google Takeout allows you to download your Gmail data. It includes message content, headers, attachments, labels, and more.

To use Google Takeout:

Sign in to Gmail.

Visit the Google Takeout page.

Select “Deselect All” to uncheck all services.

Scroll down and find “Mail.”

Click the “All Mail data included” link to customize what you want to export (e.g., select specific labels or date ranges).

Click “Next.”

Choose the export format (e.g., MBOX, ZIP).

Click “Create export.”

Google will create an archive with your Gmail data, and you’ll receive a download link via email.
[General Questions and Answers] stevep:
Ahh, thanks, xXx yYy. I didn't think the exported data included the server settings and passwords, so I haven't tried that!

Cheers!
[General Questions and Answers] stevep:
Thanks for your help. I've followed your advice and used Google Takeout. I have now downloaded a massive 20Gb zip file but I'm not clear how I apply it to my Android phone. From what I can see, the zip file contains mostly the actual emails - which I don't need. I only require the SETTINGS for each separate email account. Also, in terms of applying the data, the download only seems to work with the gmail DESKTOP application, and I'm trying to set up myANDROID phone. A bit confused now! (BUT THAT'S nothing unusual!). Cheers again, Steve
[General Questions and Answers] xXx yYy:
A: Moving the emails to Android device is easy. You have 2 options, IMO:

Using USB Device & USB Cable:

Extract the ZIP file to find a “Mail” folder containing your Gmail emails in MBOX format.

Copy the "Mail" folder to USB drive.

Use a USB cable to connect your Android device to the USB device (e.g., a USB flash drive).

Ensure that your Android phone or tablet supports USB On-The-Go (OTG) functionality. Most modern Android devices do.

After connecting the USB device, you’ll receive a notification on your Android device saying “USB storage added” or displaying the name of the drive.

Tap the notification and select “Open” to browse the contents of the USB drive using the default file explorer on your Android device.

To transfer files from your Android device to the USB drive:

Use the built-in file manager or apps that support file transfer.

Tap and hold the file you want to move, select “Move,” and choose the destination folder on the USB drive

Files by Google:

Install the Files by Google app from the Play Store.

Extract the ZIP file to find a “Mail” folder containing your Gmail emails in MBOX format.

Copy the "Mail" folder to USB drive.

Launch the app, connect your USB drive if needed, and navigate to the "Mail" folder.

Choose the method that suits you best!

B: Import Your Gmail Emails into Mozilla Thunderbird:

Download Mozilla Thunderbird, a free email client.

Open Thunderbird and follow our guide to import the MBOX file.

Now you can browse and search your Gmail archive offline using Thunderbird.
[General Questions and Answers] stevep:
Sorry, my bad. I didn't explain my situation clearly. I know how to physically move the file to my phone, but I don't know what to do to import JUST the account settings into the Gmail app from the zip file.
[General Questions and Answers] xXx yYy:
Can't help you further, I discontinue.
[General Questions and Answers] stevep:
Thanks for your suggestion. Best wishes.
[Lenovo Legion Y700] hou2315:
Help me please!
[Lenovo Legion Y700] hou2315:
I flashed the latest version of pixelos for my Y700 2023
[Samsung Galaxy S20 FE Questions & Answers] irgendeinname:
I have the model SM-G780G/DS. Sytem info app says CPU ist Snapdragon 865. It sems like i only have 4g but in the internet i read that the LTE/4g version has an exynos CPU and is called SM-G780B or sth, and the SM-G780G which i own has 5g. I'm confused about it. I wonder if someone can help me figure it out. Thanks
[Samsung Galaxy S20 FE Questions & Answers] Zxalilh:
There are 3 models. S20fe(Exynos 990 4G/LTE), S20fe(Snapdragon 865 4G/LTE), and a S20fe(Snapdragon 865 5G/4G/LTE). Take a look at this if you'd like to know more.
[Google Pixel XL Guides, News, & Discussion] master-hax:
this is a quick guide to mount an external drive into the pixel's internal storage. photos/video on this drive do appear in google photos, and can be backed up as well as cleared.

we don't need to copy files onto the pixel anymore! using ext4 also supports files greater than 4gb unlike mounting with the OS in fat32. save your pixel's internal storage from terabytes of unnecessary writes.

picture here

Spoiler content hidden.

i have some scripts to help automate this in my repository here: https://github.com/master-hax/pixel-backup-gang but this is the quick and dirty version. this method requires root access and has only been tested on the stock rom/kernel. it should work on both pixel & pixel XL. warning: running commands as root is dangerous. i'm not responsible if you brick your device.

plug in your ext4 formatted drive, ignore the os notification that the drive is not supported. then run the following shell commands. note that they must be run from the global mount namespace (master mount namespace). also the block device name (/dev/block/sdg1) rotates when devices are plugged/unplugged, so you'll need to double check which block device is your drive.

mkdir -p -v /mnt/my_drive
mount -t ext4 -o nosuid,nodev,noexec,noatime /dev/block/sdg1 /mnt/my_drive

mkdir -p -v /mnt/my_drive/the_binding
chmod -R 777 /mnt/my_drive/the_binding
chown -R sdcard_rw:sdcard_rw /mnt/my_drive/the_binding

mkdir -p -v /mnt/runtime/write/emulated/0/the_binding
setenforce 0
mount -t sdcardfs -o nosuid,nodev,noexec,noatime,gid=9997 /mnt/my_drive/the_binding /mnt/runtime/write/emulated/0/the_binding

everything under /the_binding on the drive should now be acessible by apps. you might need to force kill google photos for it to immediately notice the new folder.
[Google Pixel XL Guides, News, & Discussion] PIXELPLZ:
any updates or new methods and can u make a video pls
[Android Q&A, Help & Troubleshooting] Baratman:
Hi everyone, I have a Samsung Tab Pro S 12" model SM-W708 with Windows 11. How can I turn it into an Android tablet? Thanks
[Redmi K20 Pro / Xiaomi Mi 9T Pro Questions & Answe] PhosperX:
Hey guys, I want old version of K20 Pro which was most stable. I don't want the latest version of MIUI because I think that there is slow performance in that rom, tell me that I am correct. Also please let me know the most stable version of MIUI for K20 Pro.
[Nothing Phone 2] mollex:
What is the function of slots A and B?

Is that a multiboot version of Android, just like in Windows?

Can I install the original recovery image in slot A and then install TWRP in slot B?

Can I install ""Pong U2.5-240327-2140 (2.5.3)" in Slot A and "crDroidAndroid-14.0-20240512-Pong-v10.5"" in slot B?
[Nothing Phone 2] dlads:
Afaik, it's the way that android updates for a while now.

It's not a direct multiboot, they work in parallels so that when you update, certain images are pushed to certain partitions, like boot.img..

Not the entire system is duplicated...

You could have two separate boot images flashed, however this will cause problems when you update because they'll be cross referenced when installing an update.

Best practice is to keep them duplicated with the same firmware.
[Nothing Phone 2] theq86:
A/B (seamless) system updates | Android Open Source Project

source.android.com

Prior to A/B Seamless updates, all of the heavy work was done via recovery and overwriting the single partitions. This was, however error prone in some cases and could lead to failed updates which render the device unusable.

Now, most of the OTA can be done while running the system, so you can use your device meanwhile. The new OS is copied to the currently inactive slot partitions. After installing, the active slot is swapped and the phone rebooted.

If any error prevents normal boot, the system can detect that and re-swap the slot to the pre-updated version so you can go on using your device, not loose data and maybe try the OTA again.

Well, in fact, it is and must be. When changing from A to B, no more A partitions are consolidated. They are inactive then and will be used for the next update. During OTA, the inactive partitions are checksummed since it expects those partitions to match the software state prior to the OTA, since most OTAs are incremental.

If the inactive slot is found to be corrupt or not matching the checksum (can be the case after you unbricked the device and have slot B filled with a custom rom still, because unbrick tool flashes A only) then the current active slot partitions are copied over to the inactive ones prior to updating.

Regarding Multiboot: It is worth noting, that /userdata and /metadata are not using an a/b scheme and are unique. So when trying to multiboot, you WILL end up with changed data that might be interpreted differently by different kinds of roms. You may lose important data or configuration which is not recoverable without you having a nandroid backup.
[Nothing Phone 2] dlads:
I wasn't referring to that. There isn't two different /sdcards iirc and as you've already said there isn't two userdatas

I also said AFAIK...

Either way multiboot doesn't work.
[Nothing Phone 2] pawelmiernik:
It's in case something goes wrong during updating, if for some reason it failed, it will return to running from the slot the update was initiated from, this was designed to save user's data, not for the purpose of multi boot. Be glad it's this way, in the days before A/B slots if an update failed, your device was almost always bricked. As an added bonus, you can use your phone while it's updating, and it does all kinds of optimizations before it has to restart.
[Nothing Phone 2] dlads:
If an update failed it almost always bricked? I have never once experienced that once on any phone and I've had 1-2 phones per year since the G1?

The only time I have ever bricked a device is my Sony z1 which I installed the wrong firmware onto then stupidly rebooted, the device was done, nothing anybody could do, no power no nothing.

Anyway, it's not going to change because of this thread and I'm not grateful for the A/B slot choice.... I'm not a fan of it, never will be "glad" about it.
[Nothing Phone 2] pawelmiernik:
Are you familiar with the definition of anecdotal evidence? Look it up.
[Nothing Phone 2] dlads:
Are you familiar with being a tool?
[Nothing Phone 2] pawelmiernik:
Buddy it takes one to know one, lol
[Xiaomi Pad 6] Anjillou:
When i put game turbo in custom mode and then the settings texture filtering quality to high speed it make my game blurry
[Sony Xperia 1 Questions & Answers] Galaxy S7 Nutzer:
I don't know where to search now, so here:

After trying EVERYTHING I know and saw, but for some reason either ADB doesn't work or the phone isn't recognized or I can't install the drivers. Like... Wtf?

I I COMPLETELY deleted the phone from Windows and tried to install the USB drivers, of course that didn't work. So I looked around and have installed a Sony specific driver. The cell phone was recognized, OK.I started the terminal, went into the phone's fastboot, tried to flash it, but of course it did NOT have to work. It just said “Waiting for device" THANKS FOR NOTHING! Sry, just a bit frustrated...

I genuinely don't know what to do now, does anyone have a WORKING step by step tutorial for baby brains like me? Would appreciate it.
[Sony Xperia 1 Questions & Answers] Omar_ahmed-1:
Have you installed fastboot drivers for your device?
[Sony Xperia 1 Questions & Answers] Galaxy S7 Nutzer:
what are fastboot driver?
[Sony Xperia 1 Questions & Answers] Galaxy S7 Nutzer:
well thank you, you saved my life.
[Sony Xperia 1 Questions & Answers] Galaxy S7 Nutzer:
uhmm.. it seems like i f-ed up.. is it supposed to say "Erasing" and "your device can't be checked"? i waited a bit and now it boots but now everything is gone xDD
[Sony Xperia 1 Questions & Answers] Omar_ahmed-1:
WHAT DID YOU DO??
[Sony Xperia 1 Questions & Answers] Galaxy S7 Nutzer:
I DON'T KNOW xD

So: I did everything i could and it endet up like that, i don't care that it is wiped, the bigger problem is that i cannot find any good roms working on my barely living phone
[Sony Xperia 1 Questions & Answers] Omar_ahmed-1:
To know: you could boot the recovery to test it by:

fastboot boot recovery.img

I think the stock rom is good enough (it has android 11)

you can find it on https://xperiastockrom.com/ .
[Samsung Galaxy A32 4G] rickyreyne:
Hello everyone, it happens that on my mobile I have the developer options activated and I have several activated, for example: force MSAA X4, processing profile, limit of background processes, I change the limit, but when I restart my mobile they appear deactivated to activate again, does anyone know the solution to this?

Thank you
[Samsung Galaxy A32 4G] Badger50:
Greetings. As a friendly reminder, we ask all members to please post in English as stipulated in XDA Rule #4:

Spoiler content hidden.

Thank you for your cooperation, and have a pleasant day.

-Regards: Badger50
[Xiaomi Mi 8 Questions & Answers] savana88:
<Mod Translations>

English:

Hi, I want to go back to using my old xiaomi mi8. But it's blocked. If I try to turn it on it won't turn on, black screen, and it won't even go into recovery mode. Can you help me solve the problem?

********************

Italian:

Ciao, voglio tornare ad utilizzare il mio vecchio xiaomi mi8. Ma è bloccato. Se provo ad accenderlo non si accende, schermo nero, e non entra nemmeno in modalità ripristino. Potete aiutarmi a risolvere il problema?
[Xiaomi Mi 8 Questions & Answers] khusika:
Greetings @savana88. As a courtesy, I have translated your post above. As a friendly reminder, we ask all members to please post in English or add at least an English translation to your Italian posts, as part of XDA Rules No 4.

Spoiler content hidden.

Regards,

Khusika - Moderator.
[Xiaomi Mi 8 Questions & Answers] savana88:
Sorry, you're right. Next time I will write English
[Android Software/Hacking General [Developers Only]] Windy_007:
# Introduction

This is a tool that can inject xposed into one App from command line on Android rooted device.

Unlike traditional xposed module, this tool also support loading binary files in the xposed module.

For example, System.loadLibrary() can be used to load the so file in the xposed module.

Source Code: https://github.com/WindySha/Poros

# Features

Support Java hook using Xposed api.

Support loading native libraries in Xposed modules.

Support arm64 and arm32.

Support running command on multi platform (macOs, Windows, Linux).

Easy to use: execute only one command to do the injection.

Injection is completed during the early stage of the app's launch.

# Usage

1. Download binary file for target platform;

2. Execute the command:

$ poros-Darwin-x86_64 -p com.android.settings -f ./xposed_module_sample.apk

Then, Settings App will be started and the xposed module is injected into the Settings App process.
[General Questions and Answers] Teelads:
I want to root my Infinix x688b, I have downloaded my build firmware. I want to copy the vbmeta so that I can flash my image. But am seeing 3 images named:

Vbmeta, vbmeta_system, vbmeta vendor

Pls which one should I choose and must I rename the vbmeta to vbmeta_system if the correct choice is vbmeta_system

my code:

fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
[General Questions and Answers] xXx yYy:
To clarify things:

vbmeta: This image contains the verified boot metadata. It’s essential for the device’s security and integrity checks during boot. You should not rename this one.

vbmeta_system: This image is specific to the system partition. If you’re flashing a custom ROM or modifying the system, you’ll want to use this one. No need to rename it.

vbmeta_vendor: This image is related to the vendor partition. If you’re making changes to the vendor-specific components, use this image. Again, no renaming required.

In summary:

Use vbmeta for general boot integrity.

Use vbmeta_system for system modifications.

Use vbmeta_vendor for vendor-specific changes.
[General Questions and Answers] Teelads:
Ok thank you, I want to flash a boot.img which I have modified with magisk .

Will it be OK to use vbmeta_system, if yes, will the code look like this then:

fastboot --disable-verity --disable-verification flash vbmeta vbmeta_system.img
[General Questions and Answers] xXx yYy:
AFAIK when flashing a patched boot.img using Magisk, you don’t necessarily need to flash vbmeta.img beforehand.
[General Questions and Answers] Teelads:
The tutorials I watch about the flashing of my device flash vbmeta. I have done it I end up flashing all the system images. This are the code I use after asking Chatgpt. I flash all three

# Reboot into fastboot mode

adb reboot bootloader

# Flash vbmeta

fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img

# Flash vbmeta_system

fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img

# Flash vbmeta_vendor

fastboot --disable-verity --disable-verification flash vbmeta_vendor vbmeta_vendor.img

# Flash the modified boot image

fastboot flash boot boot.img

# Reboot the device

fastboot reboot
[General Questions and Answers] Teelads:
Thank you.