yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S24 Ultra] MasonJames1988:
Yes. I have a triple fan adapter on the back of my PS5 and it lights up blue, if I take a photo of that, It looks horrible.. I'll post a pic later
[Samsung Galaxy S24 Ultra] Msrag:
So it is issue with the camera , i don't know is it physical or software , we need to report it to Samsung !
[Samsung Galaxy S24 Ultra] cpufrost:
Can confirm this. Blue particularly in the 450nm range has always been a sore spot for capture. Its becoming increasingly more apparent now with the advent of LED lighting with its narrower spectrum point sources. I have some 445nm class IV laser projector cannons and they absolutely overload the sensor into clipping hell! Like taking a FLIR image of a magma conduit with 400C max metering!
[Samsung Galaxy S24 Ultra] ajarosz:
But this is I would say completely normal behavior of the camera sensor. Here is an example of a shot from Sony A7III from a wedding (100% crop):

View attachment 6080210Mind you, here I had white overcasting light, which was helping with that blue one. Blue/purple colors are ones that cameras, even much better than ones from the smartphone, struggle the most. If you shoot with RAW, you can save it a bit, but with JPGs, it is what it is.
[Samsung Galaxy S24 Ultra] Msrag:
So in conclusions you say that nothing to do from Samsung side ! , the thing is , when i was at the aquarium i had a friend with me having iphone 15 , and captured the blue perfectly fine , in video and photos !!! So i guess something is wrong with our devices !

I wish i could share the video but it is too long and big size , the video is a disaster ! It shows it as i don'tknow how to explain , but too much blue , too much saturated and exposed !!

I wanted to escalate the prob , but Samsung members advised to reset factory the device !! And try!
[Samsung Galaxy S24 Ultra] ajarosz:
Yeah, it can be handled better, but it is hit or miss. My GF has an iPhone 14 PRO, and in such cases sometimes it is better on my device, sometimes on hers. But I do not use default Samsung camera apps, only GCAM.

And to show you that it is not that device dependant, here is shot from iPhone 14 PRO from London:View attachment 6080544

and next to it, shot from OnePlus 7T PRO with GCAM:

View attachment 6080545
[Samsung Galaxy S24 Ultra] Msrag:
Aha , well can you suggest link for a working version of gcam on s24 ultra ?
[Samsung Galaxy S24 Ultra] ajarosz:
https://xdaforums.com/t/gcam.4652876/ Take a look at this thread. I am using config from JavaSabre, and I think it is the best that has ever happened to my device.

But please remember that:

- GCAM is not good for videos

- Samsung does not provide API for higher resolution than 12Mpix (but details from GCAM are far superior than in 12Mpix from the Samsung app).

But again in such light conditions, there is no single device that will always perform well. As in my example in prev post, even the Sony A7 III with I would say quite a good lens (Sigma 35/1.4 A) will produce some artifacts.
[Samsung Galaxy S24 Ultra] Msrag:
Thx bro
[Android Software/Hacking General [Developers Only]] PatrolMan1An:
Hi guys, anyone here kind enough to help me with my problem?

I recently tried flashing XSG Rom on my S22 Ultra running Hongkong Variant (TGY) since ive heard that UAE variants are esim capable, but while flashing through patched Odin3 v3.14.1_3B i encountered the problem below, though im used to flashing custom and stock firmwares from Pixel phone which by the way are the easiest to flash but samsung devices are different and this is my first time flashing samsung. What seemed to be the problem here?

My current firmware:​

SAMSUNG GALAXY S22 ULTRA (SM-S9080) - TGY - S9080ZHS5DXB1​

Firmware i tried to flash:​

SAMSUNG GALAXY S22 ULTRA (SM-S908E) - XSG - S908EXXS7DXB8​

​

<ID:0/005> Added!!

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/005> Odin engine v(ID:3.1401)..

<ID:0/005> File analysis..

<ID:0/005> Total Binary size: 11248 M

<ID:0/005> SetupConnection..

<ID:0/005> Initialzation..

<ID:0/005> Set PIT file..

<ID:0/005> DO NOT TURN OFF TARGET!!

<ID:0/005>

<ID:0/005> Re-Partition operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)

If the firmware is the problem can you suggest the right firmware for me?
[ASUS ROG Phone 5 / 5s] luqmanhaqim77:
Does anyone have the unpacked version of .210 firmware? Mine accidentally updated to .242 after system format and the air trigger is not working.
[ASUS ROG Phone 5 / 5s] Lovesilently94:
Bạn có thể tải xuống chương trình hạ cấp chính thức của nhà phát triển. Bạn đặt nó vào bộ nhớ trong. Sau đó hạ cấp như bình thường. Nó có tên tương tự "UL-ASUS_I005_1-ASUS-99.0840.2201.226"
[Moto G6 Questions & Answers] ibnaadam:
I got a Moto G6 with Verizon and I want to unlock the bootloader. I tried the normal process of getting Device ID and putting it in the Motorola website and it emails you the unlock code after it checks that can your device be unlocked or not. When I tried pasting my Device ID it says "Your device does not qualify for bootloader unlocking." I checked the format, removed spaces/line breaks etc etc but it didn't work. Then I found this post, according to which "There are certain restrictions such as carrier exclusive models (ex. Verizon, AT&T, Tracfone)". And mine was just that, a carrier exclusive Motorola/Verizon phone. 🙁

When I tried unlocking without code it just outputs, "(bootloader) fastboot oem unlock [ unlock code ]". Which got me thinking, can it still be unlocked with a unlock code even when the website says my device is not eligible? From what i have seen on the internet, Motorola bootloader unlock codes are generally in this form:

ZZXEJRQ6P2TANPWKWF32

A3YDR2YU5UTKYSAJOOOB

TUYTVOIZCNWQVQ6XWEHT

A 20 character string consisting mostly of capital letters and some numbers. When I try wrong codes, it just gives this error, "(bootloader) Code validation failure with status 7". It doesn't block me for trying again and again. So my question is that is it still possible to unlock a carrier exclusive phone? Or no the bootloader is just not unlockable at all, because it just wasn't designed to be unlocked. To understand what I mean, let's just say, theoretically, that we try to brute force this code with length 20. Will it work? I am not asking about brute force method but guessing the code again and again in fastboot until, if the code hash exists somewhere inside the phone, it unlocks. And if yes, it is possible, then how can it be unlocked? Bruteforcing this code would be trying out 1.34×10³¹ possible codes, which is not possible on a simple desktop. Sunshine exploit doesn't work because it's too old. So what are other methods to unlock it?
[Moto G6 Questions & Answers] WoKoschekk:
it's not possible
[Moto G6 Questions & Answers] milesius:
it has been tried. somebody even attempted a key generator app at one time. all failed. I too would like to unlock my AMZ G6.

I have a second G6 that is retail and it uses exactly the same rom but the bootloader is locked. I attempted to flash using the LMSA rescue tool from lenovo/motorola but it was also a no go. I do think that is the best path if we can figure out how to mod the rom files.

Basically we would need to trick the tool to flash what it thinks is the carrier files but are actually retail. The tool does bypass the unlock. Maybe after that exploit we could attempt root and unlock.
[Moto G6 Questions & Answers] milesius:
As a curiosity I tried flashing the just bootloader from the retail version (crossflash) onto a carrier locked (amz) version phone and it worked! flash was successful and the phone boots fine...

Is there an exploit possible ?
[Moto G6 Questions & Answers] milesius:
And I was also able to change the Fastboot version from AMZ to retail by doing fastboot flash dsp adspso.bin

so now my phone thinks its a retail version.
[Moto G6 Questions & Answers] milesius:
Flashing Recovery and Boot images fail due to verification. Seems like Lenovo/Motorola could send out a simple update to unlock these devices OTA by patching following partitions:

VENDOR_PATCH_LEVEL: vendor partition

BOOT_PATCH_LEVEL: boot partition
[Android Software Development] PatrolMan1An:
Hi guys, anyone here kind enough to help me with my problem?

I recently tried flashing XSG Rom on my S22 Ultra running Hongkong Variant (TGY) since ive heard that UAE variants are esim capable, but while flashing through patched Odin3 v3.14.1_3B i encountered the problem below, though im used to flashing custom and stock firmwares from Pixel phone which by the way are the easiest to flash but samsung devices are different and this is my first time flashing samsung. What seemed to be the problem here?

My current firmware:​

SAMSUNG GALAXY S22 ULTRA (SM-S9080) - TGY - S9080ZHS5DXB1​

Firmware i tried to flash:​

SAMSUNG GALAXY S22 ULTRA (SM-S908E) - XSG - S908EXXS7DXB8​

<ID:0/005> Added!!

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/005> Odin engine v(ID:3.1401)..

<ID:0/005> File analysis..

<ID:0/005> Total Binary size: 11248 M

<ID:0/005> SetupConnection..

<ID:0/005> Initialzation..

<ID:0/005> Set PIT file..

<ID:0/005> DO NOT TURN OFF TARGET!!

<ID:0/005>

<ID:0/005> Re-Partition operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)

If the firmware is the problem can you suggest the right firmware for me?
[Android Software Development] Oswald Boelcke:
[ATTN] : Read before posting - Any questions posted here will be MOVED or CLOSED

Please read the below before posting. Any questions not development related will be moved or closed. Forum Searching | Posting | The Basics: (Make sure you've read them before starting a new thread) Forum Rules Forum Search Google Forum...

xdaforums.com

Hello and good morning, @PatrolMan1An

Second time that I've closed a thread. Prior to your next posting please read all the moderator guidances and announcements that are stuck at the top of every forum like the one I've quoted above.

Regards

Oswald Boelcke

Senior Moderator
[Android Q&A, Help & Troubleshooting] Scott Walker:
Hello

I'm looking to hire an android developer that can delete the directory address name for the in built cameras and replace them with a OTG HDMI to USB C capture card.

I have this idea working on a phone with the app cameraFI live. It allows you to live stream from a HDMI capture card to YouTube, Facebook and others.

I need the same functionally with Zoom, Google meet, Skype. The issue is these apps only see the front and back camera. I'm thinking if we could delete these cameras in the directory and only have an address for the HDMI capture card these apps would pick it as a camera. I have no codeing experience so please excuse me if I haven't explained this correctly.
[Touch Diamond, MDA Compact IV Themes and Apps] abovelegit:
I see this theme here, http://mobileshell.ppc-theme.com/page 12.html, for SPB mobile shell, but it only has the today theme up for download, not the whole thing. If anyone may know where to find it please help.

Thanks,

Happy New Years!
[Touch Diamond, MDA Compact IV Themes and Apps] mrassol:
they said : make a donation and we'll send you the theme ... for such a good work you can give a few money ....
[Touch Diamond, MDA Compact IV Themes and Apps] Usper:
What? No. Its there to be downloaded are you absolutely blind, dumb or lazy to find it and click it?? Oh boy, here it is (the link IS THERE on THAT PAGE):

http://mobileshell.ppc-theme.com/natures_beauty/natures%20beauty.rar

If you want it as a TF3D theme you have to make a request thread for a theme.
[Touch Diamond, MDA Compact IV Themes and Apps] abovelegit:
Thats the .tsk for the today, I want the whole theme, I don't see where it says donate for full theme, I mean I will donate but I want to know im getting the theme.

and for SPB, not TF3D.
[Touch Diamond, MDA Compact IV Themes and Apps] abovelegit:
Nvm, donated, waiting for an email from him. :)
[Samsung Galaxy S10 Questions & Answers] MarkMRL:
I'm talking about rom version G973FXXSHHWI1 from Telcel Mexico, including the september 2023 security patches.

Can this firmware be installed to any SM-G970F using Odin or whatever? Any side effects of installing it on a phone from Europe?
[Samsung Galaxy S10 Questions & Answers] MrBricker:
i would like to know also but dare not try it🥵
[Android Head-Units] AlgoryThm1st:
This is the official Custom Rom Development thread for the Joying 2023 Qualcomm Snapdragon 665 Headunits.

What we know so far:

* They have disabled the accessibility menu and options in the settings

* They made their custom settings app, the shortcut to the default system settings app has been removed

* Custom notifications (status) bar, no luck so far trying to modify using Lsposed modules or other apps

* Various locks here and there

* Custom recovery which boots to USB flash disk update screen instead of the original system recovery

* The bootloader is unlocked

I have tried to port TWRP using Hovatek TWRP porter tool and replace the stock recovery.img with patched TWRP recovery with no luck.

Here is the HW Device Info PDF file with detailed hardware info: Joying Snapdragon 665 Headunit HW Device Info

Link to the stock recovery.img, boot.img and (unsuccessfully) patched TWRP recovery image: Here

Link to COMPLETE ROM DUMP: Here

Joying is unwilling to help in any case and prefers to replace the device with an older one than give any info on how to unlock it.

Any help from experienced developers in order to make a custom rom for these devices is absolutely needed and much appreciated. Please spread the word, so we can all benefit from this effort.

PCB picture:

View attachment 6079963
[Android Head-Units] Anton TNT:
Device snapshot ?
[Android Head-Units] AlgoryThm1st:
I'll try to take an online snapshot using Titanium Backup or Migrate tool, upload it and post it here. Offline snapshot is almost impossible since we don't have access to any kind of recovery and fastboot is disabled.

@Anton TNT Please ignore my previous message. It seems we DO have SU adb access so it was piece of cake to make a whole ROM dump. It's in the same folder I posted above.

Thanks for the interest and quick reply!
[Android Head-Units] AlgoryThm1st:
The latest news is I have successfully managed to get access at least to the custom bootloader screen, after I reflashed the Hovatek patched TWRP image. The problem is the 8 inch device I own, doesn't have any hardware or soft buttons. And touch doesn't work, so stuck again I guess...Does anyone know how to enable touch on that custom screen?

View attachment 6079982
[Android Head-Units] PrinceLc:
Better development on HCT MCU device with Snapdragon 665. Eonon or Xtrons.
[Android Head-Units] AlgoryThm1st:
I know, but there's also us who are stuck with these devices, so we have to find a solution in order to unlock them. The platform you're referring to is not suitable for the latest Joying devices. It still needs porting.
[Android Head-Units] PrinceLc:
I know I know what I know bootloader is unlocked, real Android 13 on it Bluetooth is a bit costom but you can pair many devices. The base of this unit is the Smartphone Doro
[Android Head-Units] nFiniti:
In for the Win! I am currently packaging my 2024 device now to send back to Joying. I'll get another one when development has been improved. But I'm gonna stick around for all of it. I wouldn't be of any use besides a tester.

Have you tried to use a USB Keyboard/Mouse?

Also a way to get to the Android System Settings, you can use shortcut apps. The normal methods that used to work no longer do. But certain shortcut apps still work. I used Shortcut Widget, then clicked Mobile Data, then clicked the small back button and it brings you to the System Settings.

Real Android 13? Proven via ADB or Terminal? Aida64 and CPU-Z are not accurate. CPU Info will tell you, Root Checker, and inix on a terminal will tell you if its real or fake android. These Snapdragon Joying units are all running Android 10 spoofed to Android 12.
[Android Head-Units] PrinceLc:
Yes real Android 13 comes with Android 12 OTA update to A13 checked with fake device test checked build.prop.
[Android Head-Units] nFiniti:
Run CPU Info from the Play Store, Run Root Checker, or install Termux and Type pkg install inxi -y then Press ENTER

Type inxi then Press ENTER

Read the info displayed.

Fake Device Check, CPUZ, Aida64 can all be spoofed.

CPU Info (open-source) - Apps on Google Play

CPU Info provides information about device hardware and software.

play.google.com

root checker - Android Apps on Google Play

Enjoy millions of the latest Android apps, games, music, movies, TV, books, magazines & more. Anytime, anywhere, across your devices.

play.google.com

Termux - Apps on Google Play

Terminal emulator and Linux environment.

play.google.com
[Android Head-Units] PrinceLc:
I know with Aida64 had an Ossuret with Fake A13 and also fake device test said pass contacted the dev of fake device test app to check his app, after an update it was seen as fake. But when you want I can check with the apps provided by you
[Android Head-Units] nFiniti:
On your own convenience. I personally don't care about the fake or real. Android 10 is better at the current time for development anyway with all the restrictions with newer versions of android. All the aftermarket roms you see here on XDA are based on new versions of Android but are not.
[Android Head-Units] PrinceLc:
Had a PX6 MTCD MCU with root after an Junsun MT8259 with A9 fake A12 than Ossuret QF001 UIS7862S A10 Fake A12 now Eonon Snappy 665 A13 HCT MCU and I am 100% sure now that the version is real. But ok check again. And yes for development A10 is better for now
[Android Head-Units] AlgoryThm1st:
I wish you the best my friend! For now, you're probably making the right move.

Yeah I tried both keyboard and mouse, both USB ports nothing. I have contacted Hovatek but the guy is busier than the president of the US...Meanwhile I'm trying to find how to enable support for my screen for that bootloader screen.
[Android Head-Units] nFiniti:
This actually got a tad off topic for this specific post. But if the development is there on similar devices, reach out to known Developers to see if they would be interested in tackling this. The Only dev I know of is only working on the typical FYT UIS 7862 Joying units because he owns one. I don't think he would be interested in trying without owning the device himself.
[Android Head-Units] PrinceLc:
Here a picture of the status notification bar

Yes I know FYT based units but hey it's crap too. Now I found the best Unit for my Passat B7 Eonon VWA12S all works OBD connection BT call all works how it should work ADB Shell works also in need future I put Magisk root and ready
[Android Head-Units] AlgoryThm1st:
Guys, please stay on topic. This thread is only for the development of the devices the title says. No more other devices discussion please, unless they have something to do with the progress concerning custom rom dev for the joying devices.
[Android Head-Units] nFiniti:
I still want this unit. So I will be around maybe to toss some thoughts around. I really don't want to ship this thing off. I was really hoping Joying would cave and tell me something like "Here's a free reverse camera for your patience, if you give us a little bit of time we will for sure fix the known issues and release an update shortly". I'm hesitant on giving up soo soon. The Bluetooth thing just really screwed it for me. And its not even something that I need. Its hard to explain. I want to HAVE games on the device and be able to connect my Bluetooth Xbox Gaming Controller to it to play them. Tho it is not something I do often. I also run HPTuners and OBX Pro VT for my LS V8 Swap that I want to use still. I could just hold off and keep it with fingers crossed that someone gets a legit root going and we can fix the bluetooth and other known issues. I was about to look into other brands but non seem to compare.

The buttons on the motherboard don't act like any sort of up or down and select buttons when in a recovery? You said you got TWRP working but touch screen isn't working?
[Android Head-Units] AlgoryThm1st:
I tried those buttons just in case but no response. I'm not in TWRP yet. I've installed custom recovery which includes that custom first menu screen I posted above. Where it says "START" I have to select "Recovery" to get into TWRP but no response so far...
[Android Head-Units] nFiniti:
There is an extra plug on the Mainboard. I swear that is an external button plug. The one right next to the SD Card. Its empty. Joying Devs gotta be able to do this stuff as well.
[Android Head-Units] AlgoryThm1st:
Yeah, I thought about it too, but with no schematics I don't risk it to short any of those pins...
[Android Head-Units] AlgoryThm1st:
I just tried to connect different bluetooth devices, Keyboard with touchpad, third company OBD, they work fine. Bluetooth is unlocked, so removing that issue from the initial list.

I guess if we could swap SystemUI with a clean one, we don't need a fully custom ROM anymore...But how could we do that? Any guides?
[Android Head-Units] nFiniti:
How did you get BT to work with other devices? The only thing I can get working is my phone. It sees my Xbox Gaming Controller but does not connect no matter how I do it. It doesn't see my Logitech Bluetooth Mouse and it wont connect to my OBDX Pro VT.

Modding SystemUI isn't difficult. I used to do it on the Samsung Galaxy Tab S 8.4. Which is what I wanted to do with this unit. But you need to have true root ability in the System Partition. Magisk is only a Systemless Root Module. Its like spoofing some things to give root privileges. So if you can actually get into even the basic Android Recovery and are able to ADB into the Device as SU and mount the System Partition, you can then unpack the SystemUI.apk. From here you'll have the entire package unzipped and it is soo awesome on how to mod things. Its images and XML files. XML files are like HTML code but more a map stating where an image is on the screen, its size, its file location and what it does when you touch it etc. I feel if you have a decent understanding of the Android system, you can mod the SystemUI no problem. After mods, you just need to re pack the SystemUI.apk and push it back into the SU Mounted System Partition. Hope you make a backup every time and hope you didn't mess something up in the code but with the backup you're good and can easilly go back into it and fix anything. I loved doing it. And that was exactly what I was planning on doing to this device.

This is why I originally brought up the Systemless root on the other post. I want to mod the SystemUI. But the issue with the Bluetooth was the last straw. And its not even that big of a deal really. Just bugs to have a Nice Snapdragon Device that is soo limited.