yashsingh1/xdaforums huggingface dataset:
[General Topics] Hendrix7:
I often see people in Internet comments falsely assuming that MicroSD is obsolete now that smartphones have high internal storage capacity.

While I am glad that we have moved past the days where 32 GB of internal storage was considered normal (remember the Galaxy S7 with its tiny 32 GB in 2016?), many people don't seem to understand that the main benefit of MicroSD is not storage capacity anymore, but durability and control over your data.

Any data in internal storage it is at the mercy of the operating system of the device. As history has shown, it can be broken by bogus updates or at worst be remotely disabled:

The internal storage is also more vulnerable to physical damage. If your USB port breaks or you drop your phone and it breaks (you should use a protective case anyway) or the water protection fails, you can no longer access its internal storage. Then you are at the mercy of the repair shop.

However, you can immediately retrieve a MicroSD card from the device and read it from another device or a computer. If you hold the power button and the screen stays black, you can rest assured that your data is still there.

Facilitated backups​

Creating backups is easier thanks to MicroSD. Using a file archiving utility (ZIP64, 7z, TAR, RAR, or whatever is supported by existing apps), you can dump the entire content of the internal storage on the MicroSD card. It is much faster than cloud storage and requires no internet connection.

Some people might also be uncomfortable with uploading their entire internal storage to a cloud service for privacy reasons. A memory card can't spy on you (obviously).

Without the MicroSD card, you would have to create the archive file on the internal storage itself, which wears down the irreplaceable internal flash memory and also requires that less than half of the internal storage is in use. (USB OTG may be another option, but it is uncomfortable to use and has no traditional mount point since Android 7 but uses some strange interface by Google, but rooted users can bypass this.)

You can simply insert a MicroSD card into the computer and bypass the slow and buggy MTP (Media Transfer Protocol) or even slower cloud syncing.

Memory cards also give you control over your data. If you have a music library on your MicroSD card, you can bring that music library to a new phone within one minute by switching cards. You don't have to bother with hour-long file transfers. It's with you in an instant, everywhere, even in locations where no Internet connection is available.

I hereby release this text under the Creative Commons 4.0 Attribution Share-Alike International license. Attribute this text with an URL to this post or with "Hendrix7 from the XDA Forums".

Edit 2024-06-14: clarified benefit for backups; added Creative Commons license.
[General Topics] Ultramanoid:
Indeed. People pay more attention to devices than to their data. And guess what, it's only the data that really matters, funny and sad how most don't recognize this.

Devices are replaced, broken, stolen, they fail, and you move on, as long as your data is safe ( AND backed up ), who cares. If the photos are lost, now, that's a loss. Or the music, or the legal documents, or whatever it is that cannot be replaced. You can buy a new device but you cannot buy the memories or valuable data lost forever. Still people attach data to devices as if they were one and the same, when their data does not have to die with the hardware at all.

Keep data independent and safe.

Never mind if you're a developer working with multiple OSes and devices. You don't want anything stuck on a piece of hardware and inaccessible to the rest.
[General Topics] blackhawk:
Meh, 1tb V-30 rated SanDisk Extreme is down to $89. One reason I still run N10+'s and not an S24U, etc.

Get a name brand card that's V-30 from a known good vendor only.

Format in phone and then leave it there.

NEVER encrypt or password protect a data drive!!!

Never clone a data drive; copy/paste.

Protect from ESD when handling and storing.

Avoid temperature extremes during use and storage. Do not touch the contacts.

Do not share it with other non Android devices ie cams etc. Best to not remove it at all.

Redundantly and regularly back up the SD card to at least 2 other drives that are physically and electronically isolated from each other and the PC! Protect all drives from near lightning strikes ie a Faraday cage.

All critical data goes on the SD card ie the data drive. Everything you need to do a complete restore should be stored there. Put some thought into this and organize it well.

There can only be one folder on the phone with "dcim" in its name! So rename any copies you make without it.

One if the Beasts, a 1.25tb dual drive.

View attachment 6094499
[G1 Android Development] Brutal-Force:
I have been following the Threads since I got my G1 for about 3 weeks now. Two days after receiving it I got the OTA update from T-Mobile before I knew it I was on RC30. After DREAMIMG.nbh and very careful reading I was able to downgrade to RC29, Root - Telnetd, and install RC30 Mod JFv1.2 then JFv1.3. Finally I installed Bootloader and got the skateboarding androids.

After a couple days of reading, I took the plunge. Let me be the first to say that as a Windows XP user, alot of this information is very confusing as I am used to a Dos type system, and all of these commands made it seem a bit more confusing than it really is.

Now that I have root and bootloader I would like to start to change the boot screen and try my hand at some Linux based stuff?

Being that I use Windows XP, it is my understanding that I can run Linux using Slax? I am very computer literate, but haven't tried my hand at programming since the days of Dos and Paschal. Are their any online tutorials that somone would recommend as a starter or is the Android Software so different that it may be better to start from scratch?

Willing to learn any pointers would be appreciated.
[G1 Android Development] Datruesurfer:
I may be misunderstanding you but if your looking to make any modifications to the operating system itself (which is definitely needed), I would suggest having a look at the Android source code at http://android.git.kernel.org. The back-end of the platform (kernel, etc) is all written in C. The userland stuff is written in Google's implementation of Java called Dalvik. Now that you have the dev bootloader, all you really have to do is clone the official android repository, make your changes, build and flash to the device using fastboot.
[G1 Android Development] Brutal-Force:
Thanx Datruesurfer

After all the reading it seemed alot of work was being done in Linux but I don't know anything about that so, I could be completely off base.

At your suggestion I looked at android.git.kernal and it seems they do a good job at explaining some things, but it still makes many references to Linux and Unix.

Would programming of Git be done in linux. I see that Git is gotten using .tar files which is Linux compressed files? So is it best to try to do programming using slax or ubuntu?

Also, are things like the boot screen modified using Linux based .png or can that be done in Windows?

Let me say sorry in advanced, as I am doing this for the first time, please say stop if I am being too n00bish.
[G1 Android Development] Brutal-Force:
Also...I noticed ....

that the commands given in the Git User's Manual look very familiar like the commands that were given while I was reverting my RC30 back to RC29 using the Pterminal/Telnet. Can this programming with Git be done off of the G1 Phone itself?
[G1 Android Development] dirr:
You're in over your head dude. If you haven't programmed in these object oriented based programming methods and you know nothing of linux, then recompiling the android source like the above poster suggested is too much.

I don't mean to dissapoint or negatively comment, but really save yourself the trouble.

If you really want to though, figure out the basics of C and java programming and start reading the source.
[G1 Android Development] Datruesurfer:
A Few things...

1. Android and Git are two completely different products. Git is the revision control system used by Android. Whenever one of the developers at Google makes a change to the source code they will upload it to the repository. Then people can go revision by revision to see where modifications have been made and suggest their own if they wish.

2. The part where a Linux box would be handy is actually downloading all of the files in the repository and compiling your own build. As dirr said, you probably should hold off on this until you have a better understanding of the platform itself.

3 As far as the boot image goes, the bootloader will only accept files that have been formatted specifically for it. Once you have the image formatted, you can flash it in the SPL via fastboot (the screen with the skating androids) I believe this can all be done via windows now.

4. I think I better understand where your coming from as far as modification. You should look at http://code.google.com/android to learn about how to code in Dalvik, as that will help you out much more then learning C. Once you have a good understanding of that, you can try to build from source

Hope that helps...
[G1 Android Development] Brutal-Force:
Thanx for the advice.

After reading about the above suggestions, it does seem that to do something simple would only be simple for someone who has all the background programming information of different platforms. This is probably why most tutorials/procedures are written so vaguely here. I appreciate the input and I will hold off and just read up on things other "more experienced" people write about here. I have a basic understanding of what is happening, but the "language" is so complex. Maybe in baby steps I will learn, since it appears that on this forum "Android" is fairly new. And while I am watching what is happening here, I will get java for dummies or bone up on Dalvik and start reading and practicing. Thanx for the help guys, and thans JF, Koush and all the other senior members for the RC30 Mod. At least I have the skateboarding Androis :D
[POCO M4 Pro 5G, Redmi Note 11S (Opal), 11T (India)] 3AHYD4:
After installing any custom rom i am facing same issue. When i insert two sim cards at the same time rom doesn't want to identify imei, but when i use only one sim card it works fine. Currently I'm using derpfest cos is has gpay in power menu. Any solution?

Device Poco M4 Pro 5G aka evergreen. 6/128
[General Questions and Answers] IsHacker:
Starting from android 13, if some app is not responding, it will keep displaying the popup if you tap on "Wait". It keeps appearing until you tap on "Close App". Does anyone know a fix for this?
[General Questions and Answers] xXx yYy:
You're right, there have been reports of an issue with the "App isn't responding" popup in Android 13. It's either a bug in Android or an incompatibility with certain apps. AFAIK there's no official fix yet.
[General Questions and Answers] IsHacker:
Bumping this thread, as it's been a while since I posted it. Has anybody found any solution? It's really annoying!
[FYT Android Head Units] gonzo99:
Recently got an Ekiy T7 Unit - a 7862(s?) with 8GB-128GB, upgrading from an earlier PX5 unit, and it's (mostly) a large improvement.

However, one issue I've run into is that I cannot get it to connect to my vLinker FD OBD dongle.

It sees it, but linking always fails before it asks for the pin.

I tested a cheapo OBD dongle, and that gave me a pop up for the pin and worked first time. However, as its a cheap and nasty unit, it causes canbus/signal errors if I leave it in, hence wanting to use the more expensive unit.

Attached is the pic of the point it gets to. With the cheap unit I get a pop up asking for the pin, but this doesn't happen with this unit - it just says linking failed.

I tried setting the pin of the unit to the same as the pin of the OBD, which is what was required on my previous PX5 unit, but same results.

As I understand it, these units have a separate inbuilt bluetooth chip too - so I tried connecting via that (using one of the apps to see the default bluetooth settings) - however, that lists everything with "noName" as description - so it's impossible to tell which if any of these it is - and trial and error didn't seem to work.

Since my phone connects fine, as does the cheap OBD, it doesn't seem like the chip is faulty - any other suggestions for things to try?

I can connect to the dongle fine with my phone, so the dongle isn't faulty.

Is this an MCU software thing, or would trying one of the modded kernels, or PeaceOS - make this more likely to work?
[FYT Android Head Units] marchnz:
Vlinker is another cheap Chinese clone.

Tested on MTCD and FYT platforms, OBDLink LX (BT) and OBDLink SX (USB) work without issue.

USB is best. BT will always be slower and have times of intermittent connectivity on these kanged platforms.

Is T7 an FYT platform? Post Screenshots of Android System information including MCU version.
[FYT Android Head Units] gonzo99:
Thanks for the reply - yes T7 is definitely FYT - I'll get a screenshot tomorrow, but the MCU version is: 2023.03.22 15:39:47 YUNC_53_L6315_N32P48F64_E60_V:1.0

The Bluetooth Version is: BLINK_2161_RELEASE/2023:11:15:14:20:47

Build Number: Qp1A.190711.020 release-keys

System Info: APP 1280x720 2023-07-22 17:39:36

I got the vLinker because its one that definitely works with Forscan, which allows better access to Fords systems than Torque or any of the competitors.

What confused me was that the ultra cheap one connected with no problems... I do have another semi cheap one somewhere that I will try - the obdlink LX is a bit too expensive to justify for the use case though I think.
[FYT Android Head Units] Moldeb:
Likely because the official BT on your unit only allows Ekiy distributed BT dongles and they sell something like the cheap dongle while the vLinker has a totally different MAC.

I had a similar issue on my Joying and solved it like this:

- In your first screenshot (or from sticker/label) note the MAC address of the target device.

- Enable secondary BT chip and make it visible in standard settings (e.g. using FET app released by @surfer63), I understand you've done this.

- Rescan using secondary BT chip as you've done in your second screenshot. Do this in an empty environment so that not too many noNames occur - three like in your screenshot is comfortable.

- Click on each of the noNames and on the next screen you'll see their respective MAC. Compare MAC to the one of your vLinker and pair that one.

- Once paired, change name of device from noName to vLinker FD in settings.

Actually I had an OBDlink MX for years and it caused the same issue when I moved from PX5 to FYT (crippled Joying). When it died after years of use, I replaced it with a vLinker MX and that's actually more capable and also receives FW updates etc. So yes it's Chinese but not just another cheap clone, does many protocols and supports accelerated transfer modes... The FD is just more tailored to Ford if I remember correctly. These are not junk devices.
[FYT Android Head Units] gonzo99:
Thank you - that sounds promising - I'll give it a try today and see if it works.
[FYT Android Head Units] gonzo99:
I tried that today and got further, but not quite there.

The secondary chip sees the device and must at some level "connect", because the device appears in 'previously connected devices' and lets me change the name.

However, it never seems to stay connected for any length of time to allow torque to see it.

I tried the same with a phone and it also connected, but then immediately disconnected - so it seems to possibly be a firmware issue on my device with the secondary chip.

I will at some point be installing one of the modded kernels, so I'll see if that helps.

In the meantime, I found a usb dongle I bought for a previous car and that seems to work perfectly with torque, so I will probably go with that as the option for now.

Hopefully your advice assists anyone else with the same issue though.
[FYT Android Head Units] j0hn83:
Add these 2 lines to your current config.txt and then reflash the unit.

Try pair your OBD via the Android Bluetooth Settings menu that just appeared in your settings.

Leave your sys.fyt.bluetooth_type= how it was before (usually 1 or 7, but not 0).
[FYT Android Head Units] Moldeb:
Further to @j0hn83's comment (you might already find the lines in config.txt if you used FET for the second step of my previous post): It's quite normal that the OBD dongle is not connected to the radio, because it is the app that connects it on demand. I don't use Torque anymore but in the settings of all these apps you typically select the dongle from the list of paired devices. Now it might be the case also that Torque doesn't show you the Bluetooth 2 list. You might want to try another app, eg Car scanner https://play.google.com/store/apps/details?id=com.ovz.carscanner which works on mine.

Or the vLinker app and if that doesn't see it, use it on the smartphone and check/update the dongle's firmware, this should be done anyway.
[FYT Android Head Units] gonzo99:
You were correct - carscanner connects and works fine!

So clearly the issue was that Torque doesn't show the Bluetooth 2 list.

Carscanner looks fairly comprehensive too, so I'll use that going forward.

Many thanks for the help!
[FYT Android Head Units] Moldeb:
Or Forscan etc, if you have a Ford
[Samsung Galaxy A54 5G] tommyzc1705:
#####################################

#••••••••••••••••••••LICH ROM•••••••••••••••••••#

#------------《S23 FE port for A54》--------------#

#####################################

LICH ROM V1

• Initial Build

• OneUI 6.1 from S23 FE

• Base S711BXXS2CXD1

• April Security Patch

• Samsung Call settings are fixed

• Some AI features fixed

• Self-generation with AI in photos worked in the gallery

• AI keyboard functions now work

• Keyboard translation also works

• SmartManager CN is added

• The "Interpret" function now works

Bugs:

• The audio is not so good, the second speaker will only sound if the volume is above 50%.

• Portrait does not seem to work in the back camera

• If you find any other bug report it

Install:

• Install Twrp [twrp in AP- vbmeta in USERDATA]

• Reboot recovery

• Wipe>Advanced wipe>formad data>yes

• Reboot>Reboot Fastboot

• On the pc open a CMD where you have the system.img [download .zip an unzip] saved.

• Type the command in cmd: fastboot flash system system.img

• When the process is finished, you can reboot system in TWRP

Download: Update

TWRP and Vbmeta used: Gdrive

kernel source here

Credits:

@testamic2 for guide install system.img in xda

@TOM_a54 (Me) for test xd

@BlackMesa123 for UN1CA as I guided a little with his work
[Samsung Galaxy A54 5G] A54Usery:
there aint no way... i just installed a one ui 6 un1ca roms and there is a new one??? boutta switch every day lmao
[Samsung Galaxy A54 5G] sakeyo:
Does NOT work with model SM-A546E
[Samsung Galaxy A54 5G] tommyzc1705:
I have the A546E model and it works.
[Samsung Galaxy A54 5G] sakeyo:
That means I failed miserably trying. I had problems with it and an error appeared when trying to install TWRP and vbmetaView attachment 6094253
[Samsung Galaxy A54 5G] cacciaviti:
Is the 4k60 working? How much is the zoom in photo mode? What are the camera bugs other than portrait?
[Samsung Galaxy A54 5G] catprrmeow:
I get an error on fastboot: Invalid sparse file format at header Magic

I redownloaded the file 4 times
[Samsung Galaxy A54 5G] cacciaviti:
It's taking more than 15 minutes for the first boot on a546b, thinking that it's not working. Anyone got it working on a546b?
[Samsung Galaxy A54 5G] gloxmy:
does it work on M546B?
[Samsung Galaxy A54 5G] tommyzc1705:
You have the recording modes of the A54, the zoom works, only the portrait mode fails.
[Samsung Galaxy A54 5G] tommyzc1705:
Try this ADB: https://dl.google.com/android/repository/platform-tools-latest-windows.zip?hl=es-419
[Samsung Galaxy A54 5G] SprechenderTV:
boot loop
[Samsung Galaxy A54 5G] TestaMic:
Explain the installation process, something you may did wrong, or the image you downloaded is corrupted
[Samsung Galaxy A54 5G] SprechenderTV:
Installed the TWRP provided with Odin in AP slot.

Then installed with the fastboot command
[Samsung Galaxy A54 5G] TestaMic:
Check if the file is corrupted. Also what version (security patch) of stock firmware you were on before installing?
[Samsung Galaxy A54 5G] SprechenderTV:
Newest
[Samsung Galaxy A54 5G] DarkGandoYT:
I don't know the reason but when I flash both the recovery and the vbmeta it tells me fail for vbmeta. Does anyone already know how to fix it?
[Samsung Galaxy A54 5G] sakeyo:
The same happens to me
[Samsung Galaxy A54 5G] TestaMic:
Send screenshot of Odin, also what security patch of stock firmware are you on?
[Samsung Galaxy A54 5G] A developer 2005:
Hi there! I tried the rom last night installation process was fairly easy and straight forward

Everything was great and I hope you keep on improving it also I have some suggestions for you! Make a telegram support group/channel for better user feedback also I encountered a bug in settings it crashes when I go to storage section of Instagram and Telegram and would you make knox work please it packes some important features 🤍
[Samsung Galaxy A54 5G] TestaMic:
A telegram group already exists but you need to talk to him as how you get in
[Samsung Galaxy A54 5G] sakeyo:
After installing TWRP and vbmeta, how did you restart in recovery mode?
[Samsung Galaxy A54 5G] V0latyle:
Hello @tommyzc1705

ROMs and kernels shared on XDA must have a published kernel source, in accordance with the XDA GPL Policy.

You have 5 days to correct this. If you do not publish the kernel source, this project will be taken down.

Please respond to this message when you have published your kernel source.

Thank you.
[Samsung Galaxy A54 5G] tommyzc1705:
If you use kernel stock which source should you place?
[Samsung Galaxy A54 5G] V0latyle:
The Samsung stock kernel source.

If you built this from someone else's source, you can publish theirs.
[Samsung Galaxy A54 5G] x3n1:
i think the download link broke
[Samsung Galaxy A54 5G] x3n1:
the post got updated with the kernel source
[Samsung Galaxy A54 5G] x3n1:
both lich rom and un1ca were bootlooping for me, I fixed by updating to latest fw which is sw rev 7, so I had to use this vbmeta https://github.com/Vaz15k/proprietary_vendor_samsung_a54x/releases instead of lich rom's, after that it took ~3 minutes and it booted