Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[SEINE] [pdx-201] AudioFlinger no output device is set #792

Open
KingProNoob2 opened this issue Oct 31, 2022 · 15 comments
Open

[SEINE] [pdx-201] AudioFlinger no output device is set #792

KingProNoob2 opened this issue Oct 31, 2022 · 15 comments
Labels

Comments

@KingProNoob2
Copy link

Platform: seine
Device pdx-201
Kernel version: 4.19
Android version: 10, 11, 12, 12.1
Software binaries version: Newest

Previously working on
Never

Description
Sorry for making a second issue, but there is no sound coming out of the device or Bluetooth devices (Could be related: https://forum.sailfishos.org/t/no-sound-no-microphone/6423 since they use the software binaries too.)
Oh, and it didnt detect my SIM card too (I also saw that in the logcat)

How to reproduce
Build and run AOSP

Additional context: part of a logcat with sound in the attachment.
10 30 17 16 11 889 734.txt

@KingProNoob2
Copy link
Author

@jerpelea I am sorry for pinging you and wasting your time, but have you got any idea why this could be happening? I am again sorry for pinging you.

@jerpelea
Copy link
Collaborator

jerpelea commented Nov 2, 2022

sorry no ! we are busy bringing nagara to SODP

@jerpelea
Copy link
Collaborator

jerpelea commented Nov 2, 2022

can you check on stock which output device is selected for this usecase?

@MarijnS95
Copy link
Contributor

The logs indicate that the audio service is falling completely flat on its face, followed by a whole bunch of unrelated chatter/fallout when it restarts, which is completely useless after knowing it crashed initially. Make sure you attach a log from boot (look up how to increase permanently the log buffer if necessary). Fwiw this all used to work fine before so it must have been recent change or otherwise? 🤢

@KingProNoob2
Copy link
Author

All right, i will build it again (bcs i broke my system which i first built it on) and post the logcat. (This will take like a day or 2)

@MarijnS95
Copy link
Contributor

All the time of the world, no worries ;)

@KingProNoob2
Copy link
Author

The os was Arch btw (sorry, i had to...)

@MarijnS95
Copy link
Contributor

Me as well, but what's this BTW version you're talking about?

😏

@MarijnS95
Copy link
Contributor

Switch to SteamOS 3.0 :)

@KingProNoob2
Copy link
Author

I did actually try steam os (Holo iso) but there was something wrong with it, i don't remember what though.

@KingProNoob2
Copy link
Author

Wait, i actually have a logcat from the whole boot process, but it was from android 13 which doesn't fully boot. From what I could tell it was because it for some reason didn't build some apks (like ims.apk)
logcat.txt

@MarijnS95
Copy link
Contributor

Audio got left in a pretty miserable state when this project was "upgraded" to Android 13, and I've yet to have a proper look into what happened (I was on holiday 😢).

It is however surprising that you're observing these failures on older Android versions as well..

@KingProNoob2
Copy link
Author

And about that sailfish os article, they do use the SODP project to build it, i saw the source myself, but the interesting thing is that the article was a year after sailfish os got ported to seine, which means the audio has probably worked before...

@KingProNoob2
Copy link
Author

Ok, i have the built images and now i will flash them.

@KingProNoob2
Copy link
Author

logcat-12.1.txt

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants