Database Users

[Q] Question about the Professional Audio Framework on SM-G870A

Good Morning XDA,
Based on the research I have been doing, it would appear that the Samsung SM-G870A (AT&T Galaxy S5 Active) does not have the Professional Audio Framework, but that also being said, I haven't found anything that says it doesn't. I have read a lot about the Galaxy S5 (Standard) does have it, but only after upgrading to Lollipop.
Does anyone know if the SM-G870A does or will support the framework?
Thanks in advance,
Jodan20xx

I'm wondering the same thing. I tried to download IK Multimedia Amplitube LE and it says my device isn't compatible, even after a Lollipop upgrade. Help!

There just aren't any resources out there. The hardware from what I can tell will fully support the framework, it just doesn't appear to be implemented.
I wonder if there is an XDA guy that can hack the SDK into the active lol

New S5 G900FD: Camera not working with CM12/CM13

Is the camera in a S5 G900FD working for anyone with CM13 snapshot/nighty or CM12 snapshot?
I just got this new toy, put twrp-2.8.7.0-klte.img and cm-13.0-20160412-NIGHTLY-klteduos on it. Neither the LED Flashlight thing nor the Camera app is working.
The output from 'adb logcat' suggests that something is wrong with the "preview stream". Does it have any prereq, like google apps or something?
Is it supposed to work, are there perhaps drivers missing? Right now its kind of an expensive brick..

olh said:
Is the camera in a S5 G900FD working for anyone with CM13 snapshot/nighty or CM12 snapshot?
Click to expand...
Click to collapse
After installing twrp-3.0.2-0-klteduos.img I wiped that data and system partition, now I think its a clean new system.
Then I installed cm-13.0-20160413-NIGHTLY-klteduos.zip. Still, neither flashlight not camera is working.
I found variours threads with users who most likely have a G900FD, so I wonder if its just me or if the Camera is just not supported. If thats the case, their wiki should be updated to state that fact.

I have G900FD with CM 13, too, and I have no probs with camera. Works as it should.

Thanks for your reply. I have created bug CYAN-7613 in Jira.

Samsung Galaxy A9 (2018) Google Camera Port or Custom ROMS

So, I've tried so many Pixel Camera ports for my latest Samsung Galaxy A9, but none of it seems to work. I've literally installed and tried more than 30-40 ports but none of them worked. They install properly but force close as soon as I open the app. I really want to see if using the Pixel Camera app will increase the picture quality.
Details about device:
OS: Android 8.0
Processor: SD660
RAM: 8GB
Any more needed information I'm happy to share

WedBull007 said:
So, I've tried so many Pixel Camera ports for my latest Samsung Galaxy A9, but none of it seems to work. I've literally installed and tried more than 30-40 ports but none of them worked. They install properly but force close as soon as I open the app. I really want to see if using the Pixel Camera app will increase the picture quality.
Details about device:
OS: Android 8.0
Processor: SD660
RAM: 8GB
Any more needed information I'm happy to share
Click to expand...
Click to collapse
Even i am using the samsung galaxy A9 (quad camera )and no google camera port is working ,but it seems that we need to root the devise and run prop editor to enable manual camera settings ,so that google camera port works on our devise

No apk file working for samsung a9 google camera installation
Hey Guys!!!!
Was anyone able to find .apk file for Samsung A9 google camera. Would be very thankful if anyone could help with any trick to make it work on the set .

I'm not finding any GCAM apk that works on Samsung A9 (quad camera).
Does anyone knows anything about it?

edit
uppp

and I'm very interested

danger2u said:
edit
uppp
Click to expand...
Click to collapse
Sir What to edit please tell us the complete procedure

You need to enable api2 on build.prop to make it work

How do I enable api2 on build.prop to make it work?

O2d4 said:
How do I enable api2 on build.prop to make it work?
Click to expand...
Click to collapse
First you need root access to edit build.prop
Then add this line to file:
persist.camera.HAL3.enabled=1
(Maybe the line is there but with =0, just replace 0 for 1)
Then save and reboot.

Is the first Samsung from mew models witch i hear that needs root....?

Seems like we won't be able to make GCam work until we won't get Android 10 update, I tried many many many many ways of getting GCam work, I changed build.prop, tried over 50+ camera's, executed many commands on ADB, none of it works for us now. So... Let's wait for Andoird 10.

I don't think you can either or you have found something that works for us (I think buying this device has been the worst and expensive investment)

Galaxy S10+ SM-G975F Galaxy Watch pairing issue with Magisk

Hello,
I am curious to see if anyone else had or still has this issue and if there is a fix for it.
Devices involved:
Phone - Samsung Galaxy S10 Plus (SM-G975F) Android Version: 10.0 Build Number G975FXXU4CTC9
Watch - Samsung Galaxy Watch 46mm (NO LTE)
Before rooting with Magisk I was able to pair the watch to the phone using the Galaxy Wearable App and use the watch with no problems. (And it still connects with my unrooted Xiaomi mi 9T)
After rooting my s10+ with Magisk (latest stable and also previous version) I was no longer able to pair the watch. It would start out fine by showing a matching passkey on both devices. I accept the code and they would begin to pair. Once the watch displays "Use phone to complete setup" is when the problems presented.
The Galaxy Wearable app will say its pairing the devices but shows nothing and keeps sending a notification saying it sees the watch and asks to connect or cancel. I tap connect and I get a white screen with a spinning circle. After 3-5 seconds the white screen goes away and 3-5 seconds later I am asked to connect the watch again.
If I go to Settings>Connections>Bluetooth (on the phone) I can see the watch is paired but the app will not complete setup. (I can pair to my car Bluetooth and JBL Xtreme speaker with no problems)
I am using Magisk Hide on the Galaxy Watch Plugin, Galaxy Wearable App, and Samsung Accessory Service but that hasn't helped. Nor does uninstalling and reinstalling Galaxy Wearable App.
Any thoughts?
Please help me, im messing around with this crap since 4 days. (I restored the phone about 20 times with odin an retryed again and again)

Could it be related to tripping knox through rooting (i.e. then some of the Samsung apps will not work e.g. Samsung Health)? I am unable to register S.Health and Wearable (on my rooted S7 edge) will not work.
However, working fine on non-rooted S10+.

Does this help?
https://forum.xda-developers.com/galaxy-s10/how-to/guide-samsung-health-knox-0x1non-root-t4075853

Boot into TWRP and flash @ianmacd's multidisabler

I have the same issue with not rooted s10+ and gear s3

Xenenon said:
Hello,
Exactly Same problem!!!!!
Stuck badly!!!
Any solution!!!!
Ahmed
Click to expand...
Click to collapse

xBrownieCodez said:
Boot into TWRP and flash @ianmacd's multidisabler
Click to expand...
Click to collapse
I did but the problem remains the same!!!

My Galaxy S3 Frontier works fine on Stock rooted + Lineage OS 17.1 .
there is a mgaisk module you can try called "Bluetooth Libary Patcher". Find it in Magisk -- Downloads -- and search for it there (just type bluetooth in search panel on top)
as i said, my watch works as it should.
and for Samsung helath: if youre rooted you just have to add one line in build.prop: ro.config.tima=1

lladwein said:
My Galaxy S3 Frontier works fine on Stock rooted + Lineage OS 17.1 .
there is a mgaisk module you can try called "Bluetooth Libary Patcher". Find it in Magisk -- Downloads -- and search for it there (just type bluetooth in search panel on top)
as i said, my watch works as it should.
and for Samsung helath: if youre rooted you just have to add one line in build.prop: ro.config.tima=1
Click to expand...
Click to collapse
oops! It did not work on mine S10+
Getting frustrated day by day!

I think the era of Rooted Devices is over!!!!!

Xenenon said:
Hello,
I am curious to see if anyone else had or still has this issue and if there is a fix for it.
Devices involved:
Phone - Samsung Galaxy S10 Plus (SM-G975F) Android Version: 10.0 Build Number G975FXXU4CTC9
Watch - Samsung Galaxy Watch 46mm (NO LTE)
Before rooting with Magisk I was able to pair the watch to the phone using the Galaxy Wearable App and use the watch with no problems. (And it still connects with my unrooted Xiaomi mi 9T)
After rooting my s10+ with Magisk (latest stable and also previous version) I was no longer able to pair the watch. It would start out fine by showing a matching passkey on both devices. I accept the code and they would begin to pair. Once the watch displays "Use phone to complete setup" is when the problems presented.
The Galaxy Wearable app will say its pairing the devices but shows nothing and keeps sending a notification saying it sees the watch and asks to connect or cancel. I tap connect and I get a white screen with a spinning circle. After 3-5 seconds the white screen goes away and 3-5 seconds later I am asked to connect the watch again.
If I go to Settings>Connections>Bluetooth (on the phone) I can see the watch is paired but the app will not complete setup. (I can pair to my car Bluetooth and JBL Xtreme speaker with no problems)
I am using Magisk Hide on the Galaxy Watch Plugin, Galaxy Wearable App, and Samsung Accessory Service but that hasn't helped. Nor does uninstalling and reinstalling Galaxy Wearable App.
Any thoughts?
Please help me, im messing around with this crap since 4 days. (I restored the phone about 20 times with odin an retryed again and again)
Click to expand...
Click to collapse
Anything you figure out!
Please do share with me!!!!

I flashed Beyonde Rom 6.7 it comes based on the latest April Patch.
This fixed all my problems
No Bugs yet with this rom
https://forum.xda-developers.com/ga...pment-exynos/rom-beyondrom-v6-0-t4017921/amp/
Flash with TWRP
Health works
Bcs of magisk all my banking works fine (Sparkasse germany)
I LOVE IT

GeekSiddiqi said:
Anything you figure out!
Please do share with me!!!!
Click to expand...
Click to collapse
Beyone Rom 6.7
If you have questions better go to reddit and ask for help
XDA is dead

any update on this issue ?

Xenenon said:
Beyone Rom 6.7
If you have questions better go to reddit and ask for help
XDA is dead
Click to expand...
Click to collapse
But do you lose the Samsung stock camera with this Rom? I have the same exact problem as you. When I was running the Evolution X custom Rom I could connect. But I wasn't happy with the camera that Rom provided. The stock camera on this phone is so amazing and one of the main reasons I bought the phone. I feel cheated when I have to give that up

nasheednashy said:
any update on this issue ?
Click to expand...
Click to collapse
I was having the exact same issue. I just activated magisk hide. And also installed the magisk module, Bluetooth library patcher. Now mine paired up first try. Not sure which helped or if it was a combination of both. But I'm paired up now.

Having same issue too. Tried changing props, tried multi disabler. Tried editing rules.
Now the app can enter but watch not connected

synite said:
Having same issue too. Tried changing props, tried multi disabler. Tried editing rules.
Now the app can enter but watch not connected
Click to expand...
Click to collapse
Did you found a way to connect them?
Inviato dal mio Pixel 3 utilizzando Tapatalk

Hi! Given a Samsung Galaxy Watch Active 2 (LTE) watch and a rooted Galaxy S10 (Android Q). Bluetooth pairing starts but does not end. Two Magisk modules id have been installed but I can't pair them. Is there anything you can bring together? So much for all the stupidity to read, but no answer or stupidity throughout. I can't install Viper4android on the same phone under Android 10. Magisk 21.4, but the 2.7 Viper doesn’t go up. It is installed by plugin, but not among applications. Can these be solved somehow? There was no problem under Android 9. Unfortunately, for the latest Android Q version, XEH version November 27, 2020, TWRP is not trable either. I download the right version, with Magisk, I boot into the AP with Odin, then start button, and odin closes immediately. Nothing goes on this ****ty Android Q. I am waiting for help together or separately! Thanks!

Any update on this issue?
I have problem pairing my Galaxy S21 Ultra and Galaxy Watch Active 2.
No pairing issues before rooting (stock firmware). After rooting using both stable Magisk V22 and Canary 22005, it stuck on Finalizing Pairing screen. I also noticed that the Bluetooth and Samsung accessory icons briefly shown on the notification bar (appear part of the screen) and then disappear.
I hope someone has solution to this.

NFC & Camera issues on Galaxy S6 edge+ SM 928F w. Havoc 3.12-20210125-zenlte

Der Folks,
I upgraded my SM928F with German Telekom Branding- specification attached, from SDK24 Nougat to Havoc's custom ROM, because my diabetic App LibreFreestyle2 needed it who regarded a higher SDK version as 24 like e.g. SDK 26. This App uses NFC to read the data and Bluetooth to send back alarm notifications to the phone. As in instructions discribed I did a rooting with TWRP-3.1.1-0-zenlte and first with Nougat_Root_SuperSU_No_kernel_included.zip and later on with Magisk-v22.0.zi before installing the custom ROM Havoc 3.12-20210125-zenlte. The Installation worked in both cases fine after deleting in updater-script file the assert line. The ROOT Checker App confirmed the rooting success. But unluckily I couldn't use NFC afterwards no matter what I did. The ui symbol of NFC showed it's on but there was no reacting on any NFC Card or my diabetic sensor. With Nougat NFC worked NFC well e.g with credit cards and their App's so on . Only because of NFC using diabetic App LibreFreestyle2 from sensor manufacture Abott I need a higher SDK as 24 (Nougat). A minor issue is the freezing camera App in video mode with custom ROM. Is there any chance to fix NFC or do I have to buy another modern phone. Any advice is highly appreciated. Regards Droidbud

Droidbud said:
Der Folks,
I upgraded my SM928F with German Telekom Branding- specification attached, from SDK24 Nougat to Havoc's custom ROM, because my diabetic App LibreFreestyle2 needed it who regarded a higher SDK version as 24 like e.g. SDK 26. This App uses NFC to read the data and Bluetooth to send back alarm notifications to the phone. As in instructions discribed I did a rooting with TWRP-3.1.1-0-zenlte and first with Nougat_Root_SuperSU_No_kernel_included.zip and later on with Magisk-v22.0.zi before installing the custom ROM Havoc 3.12-20210125-zenlte. The Installation worked in both cases fine after deleting in updater-script file the assert line. The ROOT Checker App confirmed the rooting success. But unluckily I couldn't use NFC afterwards no matter what I did. The ui symbol of NFC showed it's on but there was no reacting on any NFC Card or my diabetic sensor. With Nougat NFC worked NFC well e.g with credit cards and their App's so on . Only because of NFC using diabetic App LibreFreestyle2 from sensor manufacture Abott I need a higher SDK as 24 (Nougat). A minor issue is the freezing camera App in video mode with custom ROM. Is there any chance to fix NFC or do I have to buy another modern phone. Any advice is highly appreciated. Regards Droidbud
Click to expand...
Click to collapse
Sorry to say ... I recommend to look for a new (more recent) device which fulfills all your needs right from the start.
S6 edge development seems to be (nearly) dead