Oreo 8.1 beta 1 doesn't seem to have Snapdragon Audio+. If it does, it's not skinned properly and doesn't sound quite right.
I am trying to build a Magisk module to bring SD Audio+ back to 8.1. I did a little experimenting and, unless libraries and such are also missing, I think I can do it. I have a proof-of-concept module that partially works already. It's a port for a different phone, so some things are broken. Hoping getting the apk for this phone would correct everything.
gk1984 said:
Oreo 8.1 beta 1 doesn't seem to have Snapdragon Audio+. If it does, it's not skinned properly and doesn't sound quite right.
I am trying to build a Magisk module to bring SD Audio+ back to 8.1. I did a little experimenting and, unless libraries and such are also missing, I think I can do it. I have a proof-of-concept module that partially works already. It's a port for a different phone, so some things are broken. Hoping getting the apk for this phone would correct everything.
Click to expand...
Click to collapse
https://forum.xda-developers.com/essential-phone/themes/app-snapdragon-audio-8-1-beta-1-t3750657
Related
Hi, apologies if this is in the wrong place,
Having managed to get sMiUI onto my RedMi Note 3 Pro, with SuperSU and a MiUI compatible Xposed framework by SolarWarez (based on v85), I wanted to get xMultiWindow or similar on here, given I last had a SGS3 and it didn't really have the hardware to be able to support it I wanted to try again.
I first installed the module and it did as described briefly in the title, it produced a half-sized app in most cases but it will not show 2 apps simultaneously, the previous app turns invisible.
I believe this is related to a bug from earlier versions of android (according to a thread about doing this on MIUI 6) that struggled with it but I would have thought that it would be fixed by now, evidently Samsung fixed it.
I did some reading from that same thread and elsewhere and found MultiWinowSideBar and a Xposed fix for the invisible apps, however I'm pretty sure it was made for MIUI 6, not 8.
Needless to say, it's not working.
The Xposed module 'fix' is called "FixVisibilityOfMultipleNonFullscreenActivities"
I've heard split screen will be coming to MiUI 8 anyway, but hey, I'm impatient
Thanks everyone
I'm currently searching for a port of A300FU Android M version, also working for a A300F.
Is there any such version?
Or a reason why there shouldn't be one?
There isn't one, as of yet, but I don't see why there couldn't be, aside of it being somewhat difficult to do it for TouchWiz ROMs.
Just asking because, I've till now, not come across a non-stock (CM or Lineage)version for the A3 (2015), where the encryption still seems works. And I guess since the A310-series uses no Qualcomm chip anymore, there would be some issues trying to use a port of these unless they are specifically modded to work with other hardware components and firmware :crying:
And I really want to have a version where the encryption works, otherwise I would probably buy next year just a new one and try my luck with some XPosed modules and root access instead and keep the Google integration for the better or worse >.<
Since the b12 beta, we seem to have a real camera2 implementation. My question to the devs is, will it be possible to use the leaked beta to get camera2 api working on your custom roms in the future. Or do you need the source code from the beta in order to do that?
As far as I know it works...
macmobile said:
As far as I know it works...
Click to expand...
Click to collapse
As far as I know, you didn't read the entire post.
^So your answer is?
way to ruin a thread @macmobile thanks!
ignoring the guy that can't be bothered to ready tough, @GodOfPsychos has a very good question.
Does this beta opens the possibility of having custom oreo roms without errors like dual sim, call bugs and also with camera2 api?
@Unjustified Dev can you please help us out with some information on this?
GodOfPsychos said:
Since the b12 beta, we seem to have a real camera2 implementation. My question to the devs is, will it be possible to use the leaked beta to get camera2 api working on your custom roms in the future. Or do you need the source code from the beta in order to do that?
Click to expand...
Click to collapse
aLexzkter said:
As far as I know, you didn't read the entire post.
Click to expand...
Click to collapse
rzarectha said:
way to ruin a thread @macmobile thanks!
ignoring the guy that can't be bothered to ready tough, @GodOfPsychos has a very good question.
Does this beta opens the possibility of having custom oreo roms without errors like dual sim, call bugs and also with camera2 api?
@Unjustified Dev can you please help us out with some information on this?
Click to expand...
Click to collapse
Actually yes. AEX and RR already have HDR+ working, and NFound made a zip that fixes HDR+ on B01. It basically takes camera.msm8996.so from B12 and puts it in the appropriate place on B01, and also changes build.prop somehow (i'm guessing that he adds the HAL3 prop, haven't checked).
NFound says that if someone decides to share the stock ROM's source code (That person being @OrdenKrieger) he could fix NFC on B01 too. But you know, NFound has beef with a bunch of devs, unsurprisingly...
I'm not sure about dual sim or call bug, but it fixes HAL3 and consequentially HDR+
oh, the "when I want to" guy. well, that's just bad luck then....
Choose an username... said:
(...)
NFound says that if someone decides to share the stock ROM's source code (That person being @OrdenKrieger) he could fix NFC on B01 too. But you know, NFound has beef with a bunch of devs, unsurprisingly...
(...)
Click to expand...
Click to collapse
Excuse my question, but what's the bug with NFC on B01?
Choose an username... said:
Actually yes. AEX and RR already have HDR+ working, and NFound made a zip that fixes HDR+ on B01. It basically takes camera.msm8996.so from B12 and puts it in the appropriate place on B01, and also changes build.prop somehow (i'm guessing that he adds the HAL3 prop, haven't checked).
NFound says that if someone decides to share the stock ROM's source code (That person being @OrdenKrieger) he could fix NFC on B01 too. But you know, NFound has beef with a bunch of devs, unsurprisingly...
I'm not sure about dual sim or call bug, but it fixes HAL3 and consequentially HDR+
Click to expand...
Click to collapse
So HDR+ is working then on latest AEX? Or should the patch from 01 be used to make it work? Because I'm on the latest AEX release and HDR+ still doesn't work.
Thanks in advance
It may be a silly question, but why are people trying to fix things on B01 when B12 is out, where those things are already fixed?
0Kajuna0 said:
It may be a silly question, but why are people trying to fix things on B01 when B12 is out, where those things are already fixed?
Click to expand...
Click to collapse
The main question we have here is not if we can "port" fixes from B01 to B12; ratherm we're interested to know if B01 and B12 can be used to bring fixes to the custom ROMs like, Lineage, AEX, RR etc. etc.
rzarectha said:
The main question we have here is not if we can "port" fixes from B01 to B12; ratherm we're interested to know if B01 and B12 can be used to bring fixes to the custom ROMs like, Lineage, AEX, RR etc. etc.
Click to expand...
Click to collapse
Or missing things like the camera2 api. Of course aex have gcam somewhat working (like choose an username said) but nougat does have pretty much the same as well (only minor differences, which make aex and rr to use gcam somehow) but they are all lacking full level 3 implementation. I really hope the devs like unjustified, ordenkrieger would give us some insight if it would be possible to use the b12 (or newer if available) beta to port the camera2 api over. Idk if this would work since I'm not familiar with rom development. Perhaps it won't be possible to port because we would need the source codes for oreo? Thats basically what i wanna know.
GodOfPsychos said:
Or missing things like the camera2 api. Of course aex have gcam somewhat working (like choose an username said) but nougat does have pretty much the same as well (only minor differences, which make aex and rr to use gcam somehow) but they are all lacking full level 3 implementation. I really hope the devs like unjustified, ordenkrieger would give us some insight if it would be possible to use the b12 (or newer if available) beta to port the camera2 api over. Idk if this would work since I'm not familiar with rom development. Perhaps it won't be possible to port because we would need the source codes for oreo? Thats basically what i wanna know.
Click to expand...
Click to collapse
You can't really"port" stuff reliably. There's a rumour that there are certain Devs who do have access to source but unable to release it yet as they are waiting for the official go ahead from zte. eg release of official Oreo or failing that, admitting the release will not happen.
Hopefully it is true and like with nougat we have lineage os again working well but i don't know.
Right now we make do with what we have, leaked beta releases and a few decent aosp Oreo roms with slightly janked HDR+ support.
Hello Guys :fingers-crossed:
What about our beloved device, Is there any developer who works on this project to bring us android pie for this device
And if there can we test it ?? :good:
Yes, and yes.
@lukasb06 is working on it, and TeamNexus (?). Go and give him thanks on his thread for the NexusOS
He hasn't been online in almost two weeks or so, though. Not sure how he'll feel about us being the ones to spread news about his ROM instead of letting him do that, but oh well.
https://stor.lukasberger.at/TeamNexus/.testing/Samsung/zero/9/2018-09-08/
Though be wary, there's not even a thread about it yet, so many bugs could be present.
Bit of advice:
1. Stock camera doesn't work - use the GCamera modded for the S7Exynos.
2. GPS in plain device mode doesn't work - use high accuracy.
GApps can be downloaded from the OpenGapps website just select ARM64, 9.0, pico, and flash them after flashing the ROM.
Nice Thank you :highfive:
What about RIL Is it working ??
Well, no one has reported it as a bug yet, as far as I'm aware, so yeah?
Though bluetooth call-audio, and VoLTE (like in Oreo ROMs) don't work.
Also, instead of the modded GCamera, you can try using Open Camera.
- black theme crashes
- can´t power off softkey lights
Calling is working, back camera is working in open camera, but front camera always FC.
That is what I tested for 30 min. (SM-G920F)
Question to the developers here. Anyone excited about this update? The G5+ and the A2 lite are basically the same device aside from the battery and camera. Possible 64bit pie port in the future?
JohnSmith8786 said:
Possible 64bit pie port in the future?
Click to expand...
Click to collapse
There has been 64 bit pie since android pie has been on our phone.
Hirorails said:
There has been 64 bit pie since android pie has been on our phone.
Click to expand...
Click to collapse
But most of the ported ROM's have VOLTE troubles and UI issues. NFC isn't working good too. If a port from a phone which has nearly the same hardware and near stock experience, I think his question is valid and probably devs should consider this.
All ROMs will need to implement proper Bluetooth, NFC or fingerprint blobs to work properly. This also requires to flash stock Oreo before flashing any of Pie ROM. Volte issue is basically issue because of Persist partition. I am not sure about any issues with UI. Anyway ArrowOS from built released on 26/11 has already solved all issues and NFC for example works fine. I am using for last two days and so far nothing is wrong with it. You can't say A2 is same if it hasn't different camera for example. it might have other components or chips which differs. For example Moto Z Play (Addidson) has same components as potter except camera and anyone trying to flash ROM from it was bricking G5+. Also because of that there was never a possiblity to release an official Lineage.
It will surely be beneficial to us. Someone already ported Dirac and audio libs from MI A2 to potter for better overall sound quality.