Develop Bugs

Tab S 10.5 + Lollipop 5.02 + USB DACs

after working perfectly with 4.4 - my Fiio E17 DAC no longer works with my Tab S
from reading forums this seems quite a common complaint across Samsung users - including some Note 4 users (although bizarely some seem to have no issue)
I am not sure if it is a combination of the Tab S Exynos chipset + 5.02 + my specific DAC that has an issue - so has anyone with a Tab S and Lollipop got any USB DAC to work please ? I find the Headphone out rather poor (nowhere near as god sounding with my headphones as my Note 3) - but the screen class leading - so the combination of the Tab S + USB DAC was absolutely superb
I have read of one user using a E17 with a Sony device and Lollipop 5.02 - although can't verify it
I think Samsung had their own USB audio implementation before on 4.4 - which worked flawlessly for me - have they moved across to generic Android 5.02 implementation - and therefore could that be the issue (but doesn't explain why some non Samsung devices working ok) - OR has Samsung disabled their own USB audio but hasn't somehow implemented the 5.02 audio correctly?
hence I was wondering if anyone has managed to get USB Audio out of their Tab S please
USB audio works fine in USB Audio Pro tool - but you can only play local music content, 99.9% of my Tab S usage is with Spotify, Netflix, Amazon Instant Video etc etc
thanks for any help
LOVING Lollipop on Tab S otherwise so would be a shame to have to go back to 4.4 just for USB Audio

Bought an Oppo HA-2 and am having the same issues.
Sounds totally distorted using Player Pro, Poweramp, Samsung native music player, Spotify.
On Poweramp. the sound is distorted and the speed is super slow ie it gives the low demonic voice, like when slowing down a LP.
I don't want to have to load the Tab S with audio files and that only to use UAPP.

Fiio E18 here, works flawlessly with my Sony Z3 Compact.
On Tab S 10.5 LTE just gives slowmo playback and massive distortion..

I'm in the same boat. I used to use DACs with my Tab S 10.5 fine on the stock OS (4.4 I think), but when I upgraded to Lollipop it just hisses at me when I plug one in now. This is esspecialy annoying as I've just bought the Oppo HA-2 as well. I find this very odd since Lollipop is supposed to bring generic support for this to devices and yet it has stopped it working here. My wife has a Elephone P7000 (running Lollipop) and that works fine. I have a Samsung Galaxy Note 2 and a Galaxy Alpha (both running 4.4) and they work fine, butt if the Alpha (my main phone) gets an upgrade to Lillipop I will have to leave it now, as I need these two devices to work (they look so damn pretty together!).
Have you complained to Samsung about this? If so have you got a response? I think I will mention it to them now...

Im having problems as well...ive recently got a tab s 8.4...i upgraded to lollipop right out of the box...damn!
Anyway....my device is SMSL X-USB (XMOS based usb receiver). Works great with UAPP but not natively....no sound. On my Note 4 with lollipop 5.1.1 UAPP and native works great with it.
I want native to use RDIO, TUNEIN RADIO ETC....and then use UAPP for my hidef 96/24 flacs.
Im thinking of trying some custom roms but there are so many! Has anyone had any success with any of the custom roms?

Ok, I decided to change my entire Car Tablet install. Eliminate my Bluetooth head unit for a DAC and a DSP only to find issues. Both my Tab S 8.4 and S6 Edge will NOT WORK without using UAPP. But that's a music player. So no Android app sounds go through it. No YouTube, videos etc. Total fail with Samsung. I can test a HTC M8 just to try. Nexus 7 fresh from the 5.1.1 update doesn't work but I don't trust using my current DAC, since it's a 5.1 Surround Asus Xonar U5.
I've been trying to find DACs that work but haven't found much. I joined HeadFi and found some people that ditched the awesome Tab S for the downgraded Tab S2 because their USB SPDIF only DAC worked on the Tab S2.
I wouldn't mind downgrading to 4.4 to make DACs work, but will not get rid of my lovely screen, size, and install to go to a different tablet I dislike.
Like I stated I can't trust the Xonar, it's not a typical DAC. Unless someone can confirm it works with the Tab S on 4.4.
I know I'm not a 10.2 user but virtually the same devices, including the Tab Pro. So no need to make a new thread.
Sent from my SM-T700 using Tapatalk

So, Cheap USB DAC's are working fine on Samsungs with Android 5+. But the ones I've tried out that are capable of digital audio output don't work unless using UAAP. This is not Ok. Time to look for a CM10 Rom to install on my Tab S. This is a huge failure on Android 5. I don't think its just samsung because my Nexus 7 on 5.1.1 OEM (Maybe CyanogenMod 12 as I have not tried it yet) also does not work, as well as my HTC M9. Everything works if using UAAP, but thats just a Music Player, does not work with any other audio. I personally might end up trying a decent priced DAC with only Analog output. Since I can't hear the difference in quality in my car.

USB audio out and DACs
I had same problems with usab audio out on lollipop on tab s, nexus 7 and LG G3.
I eventually got Tab S T805 USB audio out to work after I flashed the AICP 5.1.1 rom. Worked perfectly.
Last week I flashed the AOSP Marshmallow ROM and USB audio out and this works perfectly too.
I am sending to an Audio GD DAC via an OTG adaptor.
Eventually got the G3 to work on lollipop by using a powered hub but this did not work for Tab S.
Buckster76 said:
after working perfectly with 4.4 - my Fiio E17 DAC no longer works with my Tab S
from reading forums this seems quite a common complaint across Samsung users - including some Note 4 users (although bizarely some seem to have no issue)
I am not sure if it is a combination of the Tab S Exynos chipset + 5.02 + my specific DAC that has an issue - so has anyone with a Tab S and Lollipop got any USB DAC to work please ? I find the Headphone out rather poor (nowhere near as god sounding with my headphones as my Note 3) - but the screen class leading - so the combination of the Tab S + USB DAC was absolutely superb
I have read of one user using a E17 with a Sony device and Lollipop 5.02 - although can't verify it
I think Samsung had their own USB audio implementation before on 4.4 - which worked flawlessly for me - have they moved across to generic Android 5.02 implementation - and therefore could that be the issue (but doesn't explain why some non Samsung devices working ok) - OR has Samsung disabled their own USB audio but hasn't somehow implemented the 5.02 audio correctly?
hence I was wondering if anyone has managed to get USB Audio out of their Tab S please
USB audio works fine in USB Audio Pro tool - but you can only play local music content, 99.9% of my Tab S usage is with Spotify, Netflix, Amazon Instant Video etc etc
thanks for any help
LOVING Lollipop on Tab S otherwise so would be a shame to have to go back to 4.4 just for USB Audio
Click to expand...
Click to collapse

interestingly I get proper sound out of Neutron with their new "direct to USB" option
except then my Note 3 crashes

Neutron?
Sent from my SM-G925T using Tapatalk

It's a music player
Whilst talking about USB DACs - someone on another thread posted a work around for Note 3 and USB DACs and woks perfectly on my Note 3 but no go on Tab S

If you just want to play Music, try UApp. I'm completely against settling for JUST a music player. I want to play a movie and YouTube and everything.
Sent from my SM-G925T using Tapatalk

I totally agree as most of my usage is the likes of Spotify etc
The workaround for my Note 3 although adds a few steps allows you to use DAC for all apps but doesn't work for Tab S
Annoying as the headphone out from my Note 3 is very very good anyway but the output from my Tab S I find rather poor and the main reason I bought the DAC in the first place !

Yes. I'm hoping there is a fix on 6.0 because I am not ok with just music. My tablet is built into my car, with a optical DAC, and a Helix DSP.
Sent from my SM-G925T using Tapatalk

I can't comment on the fiio as I've only got the amp only E11k but I can say my turtle beach earforce 450 DAC seems to work fine on my tab s. No surround, obviously, but I do get sound.
Sent from my LG-D855 using Tapatalk

All analog DACs seem to work. It's the DACs that have an optical out that are having issues.
Might join in on the Android 6 pages to see if they can fix the Native drivers. Doubt Samsung really cares enough. Typical DACs are working, that's good enough for them.
Sent from my SM-G925T using Tapatalk

Well, guess the "Native" USB DAC 'crap' Google has implemented doesn't work worth a damn on 6.0 either. Soo odd how it works almost flawless across soo many platforms before Android 5, then they release "Native" drivers that cripple all worthwile DACs. It's like they are purposely preventing us from using better DACs than that was installed internally so we'd be forced to use the Wolfson.
And Apple devices have Optical built in. Lol
Anyway I'm on 6.0 now testing out my Asus Xonar. Same issues as before. Using UApp it works but since UApp is 'only' a music player it leaves all other audio routed through the tablet. Noticing one issue that's new, there is a click sound every couple seconds of music playback that wasn't there on 5.1.1.
Need to find me a pre 5.0 CyanogenMod Rom to run.
Sent from my SM-G925T using Tapatalk

kernel
what about trying your stock 5.0.2rom with another kernel? like ironkernel or skyhigh kernel.
i do(or want to) belive dac suport is a kernel issue
if already are on lollipop 5.0.2 i would try this before anything else
i am currently on 4.4.2 and was just about to update to 5.0.2, had read it has native dac suport lol.
just tought i would check if there was any issues first
becouse i do have some issues of my own with my cheepo 5$ ebay pcm2704 dac with optical out (everytime i coldstart my xenons or i bump my cable it gets disconnected/connected in an instant and then sound gets wierd kinda like an echo of sorts, and i have to close music player remove cable wait a bit plug in and all is fine. quite annoing and dangerus now in the wintertime when there are frequent xenon cold starts) was hoping 5.0.2 would solve this.
im in the same boat as many others, dac suport inside player does nothing for me, as im using the tab as gps/mediasenter
so from what im reading im gonna live with it or atleast until someone have tryed 5.0.2 with another kernel
Cmon be a guinnipig, your device doesnt work anyway nothing yo lose ;p

Name the kernel and Rom, I've been on them all. I'm a vivid tester. It's not a kernel issue. This "native" support, technically just removed drivers for some dedicated DACs. Leaving the others that have been tested and proved working for years... Yes years before "native", I know I've been using DACs in all my tablet car installs from cheapo eBay 1 dollar pos dacs to high end, removed. The app UApp has this specific driver built into the app itself.
However what your describing sounds like a wiring issue.
I even jumped on the Android 6 bandwagon. It's not working on OEM Samsung Android 6 that was just released in beta form.
The hifi forum has 790 pages of info. And page one a collab of info on what dacs work and how they work.
Sent from my SM-G925T using Tapatalk

indeed i had wirering issues, nothing was sheilded, resoldered otg with sheilded cables and grounded dac chassie to cable (at the same time made a y on the otg cable for simulcharge with 88kohm resistor) and behold all is as should. ( all but a clicking sound left so i guess my dsp needs the same treatment) thanks
no build with a fix thats just wierd, there are so many clever rom/kernel builders in here
guess we cant do nothing but hope for a fix then
thanks for testing and letting us know

Connecting MIDI keyboard to Note 8.0

Hi!
I have a couple of older (5-pin) MIDI keyboards and a USB-to-MIDI "cable/dongle". I'm fairly (99%) this is class compliant, since it works perfectly on my Mac and my iPad without any drivers. I have, however, not confirmed this. But I'm actually very sure that iPad required class compliant hardware to work at all.
Anyway. When I connect this cable to my Note 8.0, my software (Synthesia, full unlocked version) does NOT recognize the keyboard(s) at all. The same software and hardware works perfectly well with my Sony Xperia Z Ultra however, so it should not be Android-related.
Question is, has Samsung disabled SO MUCH of the Android functionality on their devices that they've "accidentally" also disabled this? (Since they HAVE disable using USB-to-Ethernet devices, even class compliant ones.)
Each device is running with latest official ROM, but I'm willing to flash a custom ROM if that does away with the problem. I highly suspect that it will.
I have given up trying to contact Samsung themselves about ANYTHING, since their attitude towards tablet-customers is pretty much "hugemiddlefinger.jpg"
ps. I have ordered a USB-to-SamsungTablet cable and when it arrives I'll try with my P1000 and P6800 tablets and will let you know if these work.

V30 Quad DAC Root Bybass fix

Ive been playing about with this phone now and making a rom and in my expericance so far and from somthing @ChazzMatt said that I realized something was not quite right and it happened after i flashed a new 10c kdz and did the normal thing twrp + Magisk + Viper that i found the Quad DAC to not be switching on. Volume at 50 is nowhere near what i should be with it on compared to off. Ive found something in the build prop but im not sure if its just a coincence or this is actually doing something but 2 things might be the cause of the DAC not switching on.
1. Persist.audio.dmb_hifidac = true
2.Persist.audio.hifi_dac = off
Ive found that playing with these options and rebooting causes the DAC to switch on again. Maybe someone else can confirm exactly which of these keeps it working.

In custom CM/LOS ROMs with the 2016 ZTE Axon 7, which also has a quad DAC, devs could not use the quad DAC for audio processing. They had to use the Qualcomm Snapdragon audio processor -- as ZTE would not release proprietary source code for their award-winning quad DAC.
I believe stock based custom ROMs still had access -- as those were just debloated, tweaked ZTE firmware.
(Last time I checked was a few months ago, so if devs overcame that hurdle, then good for them. I only know the situation last time I looked.)
I do not know about the LG V20 custom ROMs, either stock-based or CM/LOS. LG V20 of course also has quad DAC. I've not researched. Maybe someone coming from V20 can tell us, either a dev or a user?
It's just the quad DAC on this phone is one of the main selling points, so you want to make sure it's being used if possible... Your ROM is stock based, but LG does have limits in place. For instance, it checks for impedance. And there's things you don't want to break.
Sent from my carrier unlocked LG V30+ US998

Can confirm. After last twrp session updating to magisk 15 killed the quaddac.
Setting the values as follows and rebooting brought it back.
persist.audio.dmb_hifidac
true
persist.audio.hifi_dac
ON

donky kong 017 said:
Can confirm. After last twrp session updating to magisk 15 killed the quaddac.
Setting the values as follows and rebooting brought it back.
persist.audio.dmb_hifidac
true
persist.audio.hifi_dac
ON
Click to expand...
Click to collapse
Ok that's strange as I had it working on different settings.
Having just replaced my v30 twice. USB port broke on 1st phone then a vertical line was on the 2nd one I got. I'm now on my 3rd phone with your settings but nothing happened till I switched on viper master power and rebooted. There's some weird impedance thing going on with it.

Whiskeyomega said:
Ok that's strange as I had it working on different settings.
Having just replaced my v30 twice. USB port broke on 1st phone then a vertical line was on the 2nd one I got. I'm now on my 3rd phone with your settings but nothing happened till I switched on viper master power and rebooted. There's some weird impedance thing going on with it.
Click to expand...
Click to collapse
Yeah it's strange. Everything worked last time with old magisk (I had to go back to stock and reflash twrp after updating to magisk 15 got me a bootloop)
It seems odd that rooting changes such things in build.prop

I woke up this morning and plugged my phone into my speakers and then later in my headphones I noticed the dac not coming on despite not rebooting since the last time it worked. So I actually switched off the dac and kept plugging in the headphones until I noticed a difference in the sound and then the dac just came on. No reboot needed again.

Whiskeyomega said:
I woke up this morning and plugged my phone into my speakers and then later in my headphones I noticed the dac not coming on despite not rebooting since the last time it worked. So I actually switched off the dac and kept plugging in the headphones until I noticed a difference in the sound and then the dac just came on. No reboot needed again.
Click to expand...
Click to collapse
It's very strange. I noticed a short lag in sound when I tried to switch on/off dac and settings. As if it was about to change something but very delayed. Seemed like something was trying to do something but got stuck and never turned on settings or dac.
That was before I changed build.prop. After that all worked well. Like said before.
Could be that when i played around little more it would have switched on without changing build.prop. But did not have time to test because i was commuting.
Sent from my SM-G935F using Tapatalk

donky kong 017 said:
It's very strange. I noticed a short lag in sound when I tried to switch on/off dac and settings. As if it was about to change something but very delayed. Seemed like something was trying to do something but got stuck and never turned on settings or dac.
That was before I changed build.prop. After that all worked well. Like said before.
Could be that when i played around little more it would have switched on without changing build.prop. But did not have time to test because i was commuting.
Sent from my SM-G935F using Tapatalk
Click to expand...
Click to collapse
What headphones do you have? I think it is to do with this. I just bought the Sennheiser HD630VB's which are only 23ohms. I also have the Momentum 2.0 over ears and the HD650s but ive only tried with the 630s and i suspect it needs 50ohms to really switch on DAC which in turn having Viper on would cause the checker to trick itself into thinking im running a higher impedance set of headphones so i need the dac on.

Whiskeyomega said:
What headphones do you have? I think it is to do with this. I just bought the Sennheiser HD630VB's which are only 23ohms. I also have the Momentum 2.0 over ears and the HD650s but ive only tried with the 630s and i suspect it needs 50ohms to really switch on DAC which in turn having Viper on would cause the checker to trick itself into thinking im running a higher impedance set of headphones so i need the dac on.
Click to expand...
Click to collapse
Atm im on vacation. I will look into it when I have the time. FYI I have ath m50x and teufel move inear
Sent from my SM-G935F using Tapatalk

so i've looked into it. my HP have 32 and 16 Ohm impedance.
they trigger the dac on when i connect them (after i changed the build.prop. it never stopped working for me again)
judging from this thread connecting higher impedance HP will trigger higher power output modes, but the dac is always on in the same way

If somebody was thinking battery test on youtube video streaming, i did that and got 8h 2min sot. Full brightness and volume.

can someone help me? have the feeling that my dac does not run since I use viper4android

with me the dac does not run with viper4android

Sony92 said:
with me the dac does not run with viper4android
Click to expand...
Click to collapse
Don't use that then. Instead use this:
Whiskeyomega's V30 Sound Mods
https://forum.xda-developers.com/lg-v30/themes/whiskeyomegas-v30-sound-mods-t3757115
What LG has done as made a bad job of the mixer_paths_tavil.xml which includes references a ES9018 which was never put in the phone or any phone AFAIK.
But what I have just noticed is if you are using a set of low impedance headphones, It goes through to the low power sound device chip but keeps the HIFI DAC switch working so the EQ can still work. Unless you make it think you are running a different type of headset which it calls "Advanced" which is high impedance then it runs to the decent DAC and there are no problems.
I have also noticed in all the mixer_paths_tavil.xml from around the world markets that there are differences in settings which should be the same. Which is what could account for some people saying Low Impedance still runs through the same decent DAC and some people saying it doesnt. Either way mixer_paths_tavil.xml is a maze of old and incorrect information.
So with that in mind. I'd Like to share the results of my work with more always coming.
Click to expand...
Click to collapse
Besides these standalone mods, some of this is implemented in at least two stock-based ROMs.

I do not want to use only the DAC, but also viper4android

Sony92 said:
I do not want to use only the DAC, but also viper4android
Click to expand...
Click to collapse
Those mods improve the DAC so you don't need viper4android.

Ok, I have to try it. but there is no way to use both?
because in the first posts was that someone has used it together with viper

Sony92 said:
Ok, I have to try it. but there is no way to use both?
because in the first posts was that someone has used it together with viper
Click to expand...
Click to collapse
You will have to ask them.
Sent via open market LG US998 V30/V30+

can it be because I installed a Costum Rom because the DAC is not running?

have the deep_buffer file restored. Now the DAC is running with Viper4Arise. I did not have to change any settings in Build.prop.

Question A52s 5G - Common issues?

Hey all,
So looking at getting a different phone for my GF as she is not enjoyong hers due to some hardware and software issues which have not been fixed by recent updates - she has a Xiaomi Redmi Note 10 Pro currently.
Considering the Samsung A52s 5G as the specs seem decent, I see it has a virtual proximity sensor - how well does this work on the Samsung as I know it does not work very well on the Xiaomi devices.
I also see there seems to be a fairly common issue with the A52s 5G and the screen and possibly 2G network - however it seems that the issue is resolved after Samsung replace the screen (if it occurs).
Are there any other glitches, issues or frustrations with this phone or does it work pretty much how it should?
She won't need to root it and won't be using custom ROMs.
Feedback and advice will be greatly appreciated!

Proximity is not working somethimes but it's ok most of the time.Working better than Xiaomi models i had before.Screen is excellent and I dont't have any problems with it.Only con for me is slow charging(about 2hrs fully charged)so I charge the phone every night.Phone is very good midrange phone-fast enough with good cameras and display and very good battery life.I'm satisfied with it.

Gaga Kanasta said:
Proximity is not working somethimes but it's ok most of the time.Working better than Xiaomi models i had before.Screen is excellent and I dont't have any problems with it.Only con for me is slow charging(about 2hrs fully charged)so I charge the phone every night.Phone is very good midrange phone-fast enough with good cameras and display and very good battery life.I'm satisfied with it.
Click to expand...
Click to collapse
Thanks, I appreciate the feedback.
Unfortunately it seems as if a lot of phones are going the Virtual Proximity Sensor route and I am wondering if we will end up with no phones having physical IR proximity sensors.
Hopefully Samsung optimize their proximity sensor software going forward.
I assume loud speaker and mic when the phone is on loud speaker or plugged in via a 3.5mm cable works 100%?
This is an issue with the Redmi Note 10 Pro which is an issue for my girlfriend as she often has her phone connected to the car via 3.5mm and when she takes phone calls the mic on the Xiaomi does not work properly and sometimes people cannot hear her clearly - was never an issue with her previous phone or when I use my phone.
Slow charging is not the end of the world, 25W apparently charges to 50% in 30 minutes which is fine for a quick power boost if need be.

Hi, i have problem with my Samsung A52s 5G. Its a wifi issue, i can't connect to a wifi with the quotes " in the name of wifi network. I connect just fine on wifi without quotes in the name of a wifi network. Pleas help! Thanks!

Gaga Kanasta said:
Proximity is not working somethimes but it's ok most of the time.Working better than Xiaomi models i had before.Screen is excellent and I dont't have any problems with it.Only con for me is slow charging(about 2hrs fully charged)so I charge the phone every night.Phone is very good midrange phone-fast enough with good cameras and display and very good battery life.I'm satisfied with it.
Click to expand...
Click to collapse
You can enable fast charging in Settings - Battery - More Baterry settings.

PsyCLown89 said:
Hey all,
So looking at getting a different phone for my GF as she is not enjoyong hers due to some hardware and software issues which have not been fixed by recent updates - she has a Xiaomi Redmi Note 10 Pro currently.
Considering the Samsung A52s 5G as the specs seem decent, I see it has a virtual proximity sensor - how well does this work on the Samsung as I know it does not work very well on the Xiaomi devices.
I also see there seems to be a fairly common issue with the A52s 5G and the screen and possibly 2G network - however it seems that the issue is resolved after Samsung replace the screen (if it occurs).
Are there any other glitches, issues or frustrations with this phone or does it work pretty much how it should?
She won't need to root it and won't be using custom ROMs.
Feedback and advice will be greatly appreciated!
Click to expand...
Click to collapse

Samsung galaxy A52s is a great phone I got my self one a week ago and I'm telling you it's a great phone loving it, I've had know problems with it since I got it it's a good buy

I got one for my GF, she is enjoying it but the battery does not last as long as her Redmi Note 10 Pro and she complains about the slow charging.
Samsung only include a 15W charger in the box, WTF!?
Otherwise it is working well and she enjoys it.

Yeah I've noticed the battery on the Samsung galaxy A52s don't last long

I have problems with VoLTE, doesn't work at all with any sim (italian carriers), I'm on android 12 one ui 4

Question S22 does not detect ssd nvme samsung 970 evo plus with external case asus rog strix arion

hi, as the title suggests, I've been trying to read my nvme ssd with an external case asus rog strix arion for days but an intermittent notification comes out that says usb device not recognized (I tried to change the file system cable but nothing) I tried the same ssd with the same case on Galaxy S7 and Galaxy A71 and it works there so I don't understand why my s22 doesn't want to read it (the power supplied by s22 is sufficient). attached a youtube video that shows the problem (as already mentioned, not present on other samsung devices):

What is the error? The video isn't clear enough to see what is said.

gernerttl said:
What is the error? The video isn't clear enough to see what is said.
Click to expand...
Click to collapse
and there is another one that says powered usb device but in each section of android there is no trace of the connection to the ssd so it was inaccessible.

How old is the SSD? Or the enclosure?

gernerttl said:
What is the error?
Click to expand...
Click to collapse
The SSD seems to keep connecting and disconnecting. in fact, the popup of the default application that manages the disk and the notification "usb device not known" appear intermittently. There is also another notification that says that the usb device is powered by USB. But for all sections of android the ssd is not detected and accessible

gernerttl said:
How old is the SSD? Or the enclosure?
Click to expand...
Click to collapse
the ssd is from 2020 produced in 2019 but it doesn't even have a 1TBW and the asus rog strix arion i bought it less than a week ago. but on other devices they work quietly even with different formatting

After a little research, I've found articles saying that the S22 series have problems recognizing older external SSD and flash drives.
I've run into a similar problem with my USB-C to 3.5mm adapter that came with my Tab S5e. It worked on my Note 10+, but neither my S22 Ultra, Tab S7, nor my daughter's S22 would recognize it.
The A71 and S7 are older devices (3 years and 7 years respectively).

gernerttl said:
After a little research, I've found articles saying that the S22 series have problems recognizing older external SSD and flash drives.
I've run into a similar problem with my USB-C to 3.5mm adapter that came with my Tab S5e. It worked on my Note 10+, but neither my S22 Ultra, Tab S7, nor my daughter's S22 would recognize it.
The A71 and S7 are older devices (3 years and 7 years respectively).
Click to expand...
Click to collapse
so it's a software problem with s22 that i can't fix except waiting for an update that will probably never come?

Run it on a (powered) hub, it probably doesn't have enough power.

Renate said:
Run it on a (powered) hub, it probably doesn't have enough power.
Click to expand...
Click to collapse
thanks for the answer but I don't think it's a power problem since my A51 doesn't support it, giving me a specific notification and turning off the case LEDs. Instead S22 does not turn off the ssd but simply cannot read it with the OS

Saverio04 said:
so it's a software problem with s22 that i can't fix except waiting for an update that will probably never come?
Click to expand...
Click to collapse
Could be. What version of Android is your A71 running?

.

gernerttl said:
Could be. What version of Android is your A71 running?
Click to expand...
Click to collapse
my a71 has one ui 5.1 with android 13 as s22

In that case it could be hardware.
Saverio04 said:
my a71 has one ui 5.1 with android 13 as s22
Click to expand...
Click to collapse
Then I doubt it is software related, or at least not completely. It is also possible that it is hardware. The reason I suspect hardware is because of the issue I ran into that I previously mentioned. There is also the possibility that it is the SSD. Have you run a check disk or error scan on the SSD to ensure there isn't a problem with it? SSDs do have a shorter life span than platter drives. Depending on how may times and how much data had been written and re-written.
Unfortunately, I can't test it using my Samsung 1TB EVO T5 portable SSD because it is:
a) new, and
b) formatted for NTFS and Bitlockered.
I don't have anything older than a three years old to try.

I used samsung magician and it has just over 300gb written, i.e. it is practically new and has no logical errors... moreover, this is very strange because the other devices read it and my s22 for example also reads an 870qvo ssd with an external case without problems paid 10 euros even when I format it in xbox format in fact it tells me to format it in a compatible format which does not happen with this ssd.

Ok. Can you check and update the firmware to the SSD? Also, is it possible to try it using a different S22?
I am still of the opinion that it is because the S22 series phones don't like older devices; even though it is practically new. Practically new is a relative term. You may have gotten only a few years ago, but in the technology realm, that is a long time.
I am not saying to go and buy a new one. I'm not sure it will ever work with your S22.

gernerttl said:
Ok. Can you check and update the firmware to the SSD? Also, is it possible to try it using a different S22?
I am still of the opinion that it is because the S22 series phones don't like older devices; even though it is practically new. Practically new is a relative term. You may have gotten only a few years ago, but in the technology realm, that is a long time.
I am not saying to go and buy a new one. I'm not sure it will ever work with your S22.
Click to expand...
Click to collapse
I understand, I will try to update the firmware and test it with a friend's S21 (since I don't have any other S22). I also sent a report to samsung in the hope that they can do something since these are two samsung products... Thanks a lot for the tip!