There is ROMs for all core prime versions (sm-g360h/hu etc...) but not for SM-G360F.
i wish it will be available to get soon...
thanks.
I've tried porting Touchwiz Marshmallow for this device. I'm getting an issue though with audio device not starting resulting in a crash(from audio policy).
I've also ported Lineage 14.1 but rild and cameraservice were crashing(didn't bother fixing them)
I cannot build because i don't have any time or a decent rig to compile ROMs and also don't wanna start working on device trees and stuff.
IDK which person to contact to give me any tips on that audio issue i have.
Damn, so we dont have any chance...
Related
Hello,
I don't understand, there's tons of people using custom roms on C6833 device.
There's toussands of hundreds people that has at least tried to record their voice, their landscape, their street, their home.
How couldn't anyone notice that the sound recorded is inaudible ?
Even shazam can't recognize a well known music.
My snapchat friends don't hear me on their android and iphone nor on windows phone.
I had to switch back to stock to have some "stock audio recording".
It's like something is blocking the microphone when a custom rom is installed based on any cyanogenmod, rc, stable, nightly, ver 10.2 , 11, 12.
I have even tried to report this issue for a stable version of cm on kit kat with a log on jira.cyanogenmod, but I couldn't run the test the good way, gave up, they closed my report.
Please, anyone that understands codes, sources, developpements stuff, ask users, ask (wait, I'm gonna create a poll)
So my question is: Do you have a decent volume recording while you are using your camera app on cyanogenmod 10.2 or 11 or 12 ?
Witht the camera app, with snapchat, with shazam, with voice recorder app ?
Do your friends hears you ?
Do shazam recognize something at a decent level of your computer/radio ?
Do you hear yoyrself as on a stock rom when recording with a memo voice ?
Moderators: if I post this in Q/A, nobody will react, this issue is not taken seriously, I think that nobody records anything, this happens since I own a custom rom except when I relock the bootloader and use my stock laggy rom.
Please, make it know cm devs, ask every krait-400 based devices owners if this is still happening.
Poll seems to not work:
Even if you are a z1 owner, do you noticed the non-record of your audio when using anything that needs sound source ?
Did you ever tried to record a video with your device before and after flashing ?
End (want to delete it moderators, then delete it, but I already tried everything, I'm pissed of switching back on stock just for the sound recording works perfectly and losing the beauty of lollipop) + I hate kit kat stock with preinstalled apps
To mention: I even were on cyanogenmod.forum to discuss about it and nobody seems to take care of that issue, it's like they deal with it like I will have to do and like I have always been
guys I looked in all Z5 series forums and none seem to have a fully functional AOSP roms (any thing thats not STOCK fw doesnt seem to be bug free)
and I know there are fully working but they all have these small bugs of laggy camera (focus colors everything) and some have distorted sound, some have not working wifi hotspot , some have blutooth issues and I need blutooth cuz i have BT headphones, can any one give me some thing good to go? thanks
Nope. Big issue with Sony Xperia series are camera and sometimes nfc. This will most likely not be solved until the Sony Dev teams releases the source and/or help developing the open source code. And that is very unlikely to happen.
The other issues beside camera and nfc are ROM specific. That is up to the ROM developer to solve.
I have installed different nougat roms on my redmi note 3 kenzo. One of the most dangerous and irritating bug is When You take screenshot, or click a picture with a camera. while listening to music in earphones/headphone. Then the sound of music start coming from the speaker also.
when I end a whatsapp call. then also the same thing happened.
But Exodus android, omnirom does not have his issue. all goes well on that but I prefer to use lineage os more.
Is there any fix for that??
I know we had this issue before, and I don't want to revive old hostilities. I'd like to make this clean and objective discussion.
As you probable know by now, some time ago Google have decided to make android phones play *any* sound to *any* connected BT device, no matter if those devices are capable of playing those sounds or not, and no matter if the users are using (wearing) those devices or not. And this results, for example, in missing text messages, when your head phone is still switched on but you're not wearing it. It also will interrupt your favourite song that you're listening to on your car's radio, with a loud and nasty sound over your car's speaker. And it will also keep you from hearing medical alarm signals if your head phone is in your pocket.
As far as I know, this change in BT behaviour was introduced somewhere between Android 7 and Android 8 (LOS 14 and LOS 15), and as far as my programming knowledge goes, it should be possible to reverse these changes, to make a phone play system sounds over the phone's speaker, while music and calls are still routed to a paired and active BT devices.
So, my questions are these:
What is the big advantage of the present BT behaviour compared to the old behaviour?
How much work or effort would it take for LOS developers to re-code the BT behaviour from LOS 14 back into LOS 17 and above?
If you need help: how can normal people like me with no big development skills help you with this? Would it be a question of money?
How much (in)stability would current and future LOS versions gain through the necessary changes?
Would making these changes be illegal in any way? Would Google sue LOS developers, or would Google send their Men In Black, if LOS developers dared to undo Googles decision?
Although I do not understand the cleverness behind Google's decision, and frankly, no one I talked to about this did understand it, I'd rather make this a discussion about the possibility to undo these BT changes. It would be very obliging to get some useful answers to these questions. Thanks in advance!
Google and LineageOS devs are aware of it and don't see it as an issue:
https://gitlab.com/LineageOS/issues/android/-/issues/950
https://issuetracker.google.com/issues/123758732
https://issuetracker.google.com/issues/125166459
https://issuetracker.google.com/issues/139884122
I can't for the life of me understand why anyone would want it this way. I, for one, see notifications and media audio as separate things that serve different purposes. I regularly pull out my bluetooth earbuds or turn off my bluetooth-linked hi-fi system without remembering to disconnect them at my phone. It's one thing if I go to youtube or play music and can't hear it because of this, but another thing entirely to miss a day's worth of notifications.
A lot of people have been really vocal about this -- just read some of the stories -- but these devs are so sure of themselves that they won't even offer a toggle setting for this. I'm tired of the arguing... LineageOS is free software and I'll patch and build it to suit my needs. But like you, I am not an Android developer, and I don't even know where to start to look for what controls this. I'm sure it's just a couple of lines tucked away in some file, but all I can do is ask, please, for someone out there with greater skills than me to show me what to change!
So I've been digging into the source but it's really above my head... seems like there must be a config file or set of constants somewhere. I'll keep digging and share if I find anything.
Another approach that seems possibly doable is an app that routes the notification sounds through the alarm stream. I have a calendar app that is configured to sound through the alarm stream and that sounds the way I want -- through both the device speakers and any bluetooth or wired headphones.
Sorry about the delay:
htsmi said:
Google and LineageOS devs are aware of it and don't see it as an issue:
https://gitlab.com/LineageOS/issues/android/-/issues/950
https://issuetracker.google.com/issues/123758732
https://issuetracker.google.com/issues/125166459
https://issuetracker.google.com/issues/139884122
Click to expand...
Click to collapse
The answers given by Google's team are living arrogance, a disgrace to themselves and an insult to the users!
Any (good) news on this subject?
Hello.
I've been using CrDroid on my Poco F1 for more than 8 months without problems when streaming media on my car's infotainment system.
Since an update in July (build of July 18th) media doesn't stream at all in the car's system but the phone itself seems connected and calls are working properly.
Yesterday I clean flashed another rom (Reloaded CAF latest version) but the result is the same. The last working rom is CrDroid from 11/07/2020 which I just switched back too.
I don't want to try other roms with clean flashes right now because I don't want to go through the fuss of setting up the phone each time without knowing if the issue is solved.
Does anybody have any insight on this?
Thank you in advance.
DanteGR said:
Hello.
I've been using CrDroid on my Poco F1 for more than 8 months without problems when streaming media on my car's infotainment system.
Since an update in July (build of July 18th) media doesn't stream at all in the car's system but the phone itself seems connected and calls are working properly.
Yesterday I clean flashed another rom (Reloaded CAF latest version) but the result is the same. The last working rom is CrDroid from 11/07/2020 which I just switched back too.
I don't want to try other roms with clean flashes right now because I don't want to go through the fuss of setting up the phone each time without knowing if the issue is solved.
Does anybody have any insight on this?
Thank you in advance.
Click to expand...
Click to collapse
If its any help, I was using Crdroid for a while until Android Auto stopped working sometime back in April. Since then, I'm on EvoX and both AA and Bluetooth streaming are working great...
BTW, on earlier versions of Crdroid, if I installed V4A and also audio compatibility patch and audio modification library from Magisk, I would get no sound through Bluetooth... Don't know which of the two mods was the exact culprit, though, but if you've got any of these installed, maybe disable them first and give it a try...
krilok said:
If its any help, I was using Crdroid for a while until Android Auto stopped working sometime back in April. Since then, I'm on EvoX and both AA and Bluetooth streaming are working great...
BTW, on earlier versions of Crdroid, if I installed V4A and also audio compatibility patch and audio modification library from Magisk, I would get no sound through Bluetooth... Don't know which of the two mods was the exact culprit, though, but if you've got any of these installed, maybe disable them first and give it a try...
Click to expand...
Click to collapse
Thanks for replying.
No mods installed so that shouldn't be it.
I've settled on CrDroid from 11/07 for now due to forthcoming vacation and no time for clean flashes.
Will test other roms later on.
Thanks again.