The AOSP ROMs are great but they lack due to the fact that they can't use the DAC. Is it possible for us to port over the DAC function over? Or is it exclusive to the terrible stock ROMs?
I didn't see a bounty thread. I have $30 for a developer to enable the DAC.
jameslapc2 said:
The AOSP ROMs are great but they lack due to the fact that they can't use the DAC. Is it possible for us to port over the DAC function over? Or is it exclusive to the terrible stock ROMs?
Click to expand...
Click to collapse
The kind of device V20, I wouldn't mess with its OS much. I would use it with stock.
I am pretty sure that the Sabre DAC does work and utilized in AOSP roms, there was a commit for it a couple times in Lineage OS and IIRC, the maintainer for LOS mentioned that the DAC is enabled on boot (LG Screen), then gets disabled by the kernel when the device finishes the boot (Enters the lockscreen/homescreen). The commit is meant to disable the behavior the kernel does after boot, so in theory the DAC should be enabled and being used. Proper testing with the right equipment is required to verify if this commit is working, testing the response from the headphone jack.
I believe any builds for AOSP roms for the V20 built after May should have the commit and the DAC should be working.
Notice that I said should, I believe no one has confirmed with tests to ensure these commits work or not.
FQuimson23 said:
I am pretty sure that the Sabre DAC does work and utilized in AOSP roms, there was a commit for it a couple times in Lineage OS and IIRC, the maintainer for LOS mentioned that the DAC is enabled on boot (LG Screen), then gets disabled by the kernel when the device finishes the boot (Enters the lockscreen/homescreen). The commit is meant to disable the behavior the kernel does after boot, so in theory the DAC should be enabled and being used. Proper testing with the right equipment is required to verify if this commit is working, testing the response from the headphone jack.
I believe any builds for AOSP roms for the V20 built after May should have the commit and the DAC should be working.
Notice that I said should, I believe no one has confirmed with tests to ensure these commits work or not.
Click to expand...
Click to collapse
If that's the case then I'll see what I can do in getting it to work. Looks like my new Ryzen CPU finally has a job fitting for it.
Related
First of all I have the HTC Inspire 4g and I know I should post this there. But the JellyTime is Here with the Inspire Mod.
Before I tryed Jellytime I had IceColdSandwitch witch the sound was one of the loudest I think I had.
Is a read the sound was lower on Jellytime but with different versions of the releases,
So what makes the sound lower on some builds of JellyTime then others?
I tryed the inspiremod, I always do a Backup and a Full wipe of everything. Before I flash anything.
I know all of the builds are beta and testing and bugs are going to be in everyone. Hint my UserName.
No One
No one?
I know its all trial and error, with Testing and Learning.
To sum it all up
Dose Changing one thing to make something work Brakes something else?
like with Bluetooth? Working in one release and the next release its not?
This is from having to hack together a working kernel. Without source for the kernel it will be trial and error for the devs
Sent from the Bat Cave
go back a build to 13 - volume works fine, albeit with the fix.
Ok, now I'm learning,
I'll try 13.
zelendel said:
This is from having to hack together a working kernel. Without source for the kernel it will be trial and error for the devs
Sent from the Bat Cave
Click to expand...
Click to collapse
Actually the "issue" was upstream qcom media/audio changes unrelated to kernel. I put issue in quotes because I found it to be a non-issue. The same day this happened was the same day CM qcom audio officially supported building 7x30 from source, so I switched that night to build audio from source, and in every nightly since that one, audio volume and quality has been fine. The 20% audio boost I put in kernel was after I fixed the audio in source. And only because all older custom kernels had a 20-30%% boost, and it put the volume back to what users had learned to expect on custom roms/kernels.
Just flashing a more recent KangBang kernel on top of a cooked ROM like this that hasn't been fixed in or updated for upstream source built audio will not give you the quality or volume you are expecting.
I should also note that I've stopped uploading non-test kernels due to the nightlies pulling from my kernel git and building during the build, so the kernel's fully up to date with whatever I've done every day.
I'd like to ask what would be the state of each of the next features on SGS5 (any of its models) when moving to an AOSP based rom (like CM, Omni, PA, ...) :
1. MHL/HDMI
2. Screen recording.
3. Calls recording
4. hovering with the fingers.
5. touching with gloves
6. sensors
7. IR
8. Any TW app (camera, keyboard, etc...)
By state, I mean, how well would it function, if at all.
Also, I'd like to ask (as I don't really own the device) : what would you miss the most in case you moved from stock-Samsung rom to AOSP-based rom?
Any feature I didn't mention ?
AndroidDeveloperLB said:
I'd like to ask what would be the state of each of the next features on SGS5 (any of its models) when moving to an AOSP based rom (like CM, Omni, PA, ...) :
1. MHL/HDMI
2. Screen recording.
3. Calls recording
4. hovering with the fingers.
5. touching with gloves
6. sensors
7. IR
8. Any TW app (camera, keyboard, etc...)
By state, I mean, how well would it function, if at all.
Also, I'd like to ask (as I don't really own the device) : what would you miss the most in case you moved from stock-Samsung rom to AOSP-based rom?
Any feature I didn't mention ?
Click to expand...
Click to collapse
Sadly, most of these functions have not been carried over to AOSP based roms. Most of these functions seem to arrive on Cyanogenmod first.
I do know that Cyanogenmod is currently supporting IR but it is not complete enough to run 100% daily driver. They're having GPU video/image rendering issues in some apps, camera isn't properly configured. It's all stuff being worked on but I am sure all of these functions are on Cyanogenmod's to-do to support all of the hardware features of most devices.
Glove sensitivity functions perfectly in cyanogenmod, most sensors work perfectly as well. The eye-tracking features are likely not ever going to be a part of AOSP roms. Hopefully Hover gets picked up by more manufactures and becomes a part of AOSP and the SDK for apps, it has great possibilities for better intuitive interfaces.
stevey500 said:
Sadly, most of these functions have not been carried over to AOSP based roms. Most of these functions seem to arrive on Cyanogenmod first.
I do know that Cyanogenmod is currently supporting IR but it is not complete enough to run 100% daily driver. They're having GPU video/image rendering issues in some apps, camera isn't properly configured. It's all stuff being worked on but I am sure all of these functions are on Cyanogenmod's to-do to support all of the hardware features of most devices.
Glove sensitivity functions perfectly in cyanogenmod, most sensors work perfectly as well. The eye-tracking features are likely not ever going to be a part of AOSP roms. Hopefully Hover gets picked up by more manufactures and becomes a part of AOSP and the SDK for apps, it has great possibilities for better intuitive interfaces.
Click to expand...
Click to collapse
I see. Not even screen recording?
Is this the situation with all of the variants of the device?
I wonder how well other devices (even of other manufacturers) are supported by CM (and other AOSP based roms).
I assume Nexus is one of the best ones that they support.
AndroidDeveloperLB said:
I see. Not even screen recording?
Is this the situation with all of the variants of the device?
I wonder how well other devices (even of other manufacturers) are supported by CM (and other AOSP based roms).
I assume Nexus is one of the best ones that they support.
Click to expand...
Click to collapse
Screen recording is in the works on Cyanogenmod and in the process of being built for compatibility on all devices. It's a lot of work to build software in compatibility will all hardware. Nexus devices to get the extra bit of love because those devices are arms wide open to the developer community. Samsung, LG, and HTC are getting hit hard by locked bootloaders on the two giant carriers verizon and AT&T... if those bootloaders were not locked, I am sure that the flagship devices from those companies would be getting a LOT more developer support, especially from Cyanogenmod team.
Such as, the Galaxy S3 (and a moment for the S4) were the last devices that were getting insta-written AOSP code and compatibility support for AOSP based roms while the majority of them were bootloader unlocked/unlockable. The Galaxy S5 is being developed for, just a bit slowly, sadly. AT&T and Verizon models are totally bootloader locked with no current workaround.
The nexus devices may seem to be better supported by the developers but the Nexus devices aren't as complex and have a more basic hardware layout lacking alot of the extras and premium features of the samsung, htc, and LG family- those devices require more attention.
stevey500 said:
Screen recording is in the works on Cyanogenmod and in the process of being built for compatibility on all devices. It's a lot of work to build software in compatibility will all hardware. Nexus devices to get the extra bit of love because those devices are arms wide open to the developer community. Samsung, LG, and HTC are getting hit hard by locked bootloaders on the two giant carriers verizon and AT&T... if those bootloaders were not locked, I am sure that the flagship devices from those companies would be getting a LOT more developer support, especially from Cyanogenmod team.
Such as, the Galaxy S3 (and a moment for the S4) were the last devices that were getting insta-written AOSP code and compatibility support for AOSP based roms while the majority of them were bootloader unlocked/unlockable. The Galaxy S5 is being developed for, just a bit slowly, sadly. AT&T and Verizon models are totally bootloader locked with no current workaround.
The nexus devices may seem to be better supported by the developers but the Nexus devices aren't as complex and have a more basic hardware layout lacking alot of the extras and premium features of the samsung, htc, and LG family- those devices require more attention.
Click to expand...
Click to collapse
I see. So it takes a lot of work.
Say, you mentioned the SGS3. I have this device. Do you think it will ever support screen recording on CM ? Currently it's very very slow. I've tried the special customized rom that's based on Note 2, and this feature worked fine there. I've left this rom because of some reasons I don't remember about (maybe stability).
All those features are available in samsung based custom roms. Why does it have to be AOSP based?
Sent from my SM-G900F using Tapatalk
Hello all,
I'm on the fence about moving back to using a custom ROM on my A2017U. The issue I have is that I had trouble on my last ROM using the Hi-Fi DAC, which really bothered me because part of the reason why I bought this phone was to take advantage of the better audio quality as compared to other phones at the time of its release. Presently, what's the easiest way to take advantage of the DAC on an 8.x AOSP ROM?
Thanks!
achillesphazd said:
Hello all,
I'm on the fence about moving back to using a custom ROM on my A2017U. The issue I have is that I had trouble on my last ROM using the Hi-Fi DAC, which really bothered me because part of the reason why I bought this phone was to take advantage of the better audio quality as compared to other phones at the time of its release. Presently, what's the easiest way to take advantage of the DAC on an 8.x AOSP ROM?
Thanks!
Click to expand...
Click to collapse
Also, I'd like to know if there is a way to fully use Dolby Atmos with the built-in speakers on a custom ROM.
achillesphazd said:
Also, I'd like to know if there is a way to fully use Dolby Atmos with the built-in speakers on a custom ROM.
Click to expand...
Click to collapse
Not sure about "fully use" but I have used Dolby Atmos on custom ROMs. Currently running the one from here...
http://forum.xda-developers.com/showthread.php?t=3740508
[PORT] [8.0+] Dolby Atmos™ for Oreo 20180220 [Standard/Unity]
ZTE Axon 7 A2017U, AospExtended v5.4 ROM, HellsGate Kernel, Multiboot, Tapatalk 4.9.3
marcdw said:
Not sure about "fully use" but I have used Dolby Atmos on custom ROMs. Currently running the one from here...
http://forum.xda-developers.com/showthread.php?t=3740508
[PORT] [8.0+] Dolby Atmos™ for Oreo 20180220 [Standard/Unity]
ZTE Axon 7 A2017U, AospExtended v5.4 ROM, HellsGate Kernel, Multiboot, Tapatalk 4.9.3
Click to expand...
Click to collapse
Thanks for the reply. How about using the AKG DAC?
https://www.extreamsd.com/index.php/hires-audio-driver
http://www.extreamsd.com/index.php/uapp-trial
aosp said:
https://www.extreamsd.com/index.php/hires-audio-driver
http://www.extreamsd.com/index.php/uapp-trial
Click to expand...
Click to collapse
Thanks so much! Have you personally tried this?
achillesphazd said:
Thanks so much! Have you personally tried this?
Click to expand...
Click to collapse
Yes I have and I'll be surprised if any other audio player will sound more Hi-Fi then UAPP besides the craptastic stock player
achillesphazd said:
Hello all,
I'm on the fence about moving back to using a custom ROM on my A2017U.....
I guess you partly answered your question yourself. First of all, the reason to root devices and install custom ROMs have reduced drastically. Rooting and Custom ROMs were the thing when Android was in its initial stages. Now, they have grown it leaps and bounds and there isn't simply anything that a developer could add which is not present in the stock. That being said, people still root it for various reasons and I am okay with it. I used to be root all my phones but have completely stopped it in the last two years. I don't much value in rooting anymore. But that's me.
Now coming to this specific device, which is renowned for its audio capabilities. Why would you buy a phone which comes with stellar sound through both speakers and audio jack and install a custom ROM?!? There are certain things best left to the makers of the phone. I would look to install a custom ROM to enhance performance/features of a device. But in this case, if you are going to install a custom ROM, you are certainly going to rob the device of its audio capabilities. This phone is best left untouched if music/sound is your thing. I wouldn't even root this device, for the fear of breaking something that might deteriorate the sound quality. I own a ZTE Axon 7 Mini. I bought it mainly for its audio capabilities. It is my secondary phone for SIM2 and a media device. After buying, I just updated it to Android 7.1.1, froze the apps that I won't use. I certainly will not even root it, even though I know how to root it.
Hope this helps.
Click to expand...
Click to collapse
prmbasheer said:
achillesphazd said:
Hello all,
I'm on the fence about moving back to using a custom ROM on my A2017U.....
I guess you partly answered your question yourself. First of all, the reason to root devices and install custom ROMs have reduced drastically. Rooting and Custom ROMs were the thing when Android was in its initial stages. Now, they have grown it leaps and bounds and there isn't simply anything that a developer could add which is not present in the stock. That being said, people still root it for various reasons and I am okay with it. I used to be root all my phones but have completely stopped it in the last two years. I don't much value in rooting anymore. But that's me.
Now coming to this specific device, which is renowned for its audio capabilities. Why would you buy a phone which comes with stellar sound through both speakers and audio jack and install a custom ROM?!? There are certain things best left to the makers of the phone. I would look to install a custom ROM to enhance performance/features of a device. But in this case, if you are going to install a custom ROM, you are certainly going to rob the device of its audio capabilities. This phone is best left untouched if music/sound is your thing. I wouldn't even root this device, for the fear of breaking something that might deteriorate the sound quality. I own a ZTE Axon 7 Mini. I bought it mainly for its audio capabilities. It is my secondary phone for SIM2 and a media device. After buying, I just updated it to Android 7.1.1, froze the apps that I won't use. I certainly will not even root it, even though I know how to root it.
Hope this helps.
Click to expand...
Click to collapse
Why would you "certainly" kill the audio? Why are you so damn sure that it's worse than stock?
---------- Post added at 03:36 AM ---------- Previous post was at 03:32 AM ----------
achillesphazd said:
Hello all,
I'm on the fence about moving back to using a custom ROM on my A2017U. The issue I have is that I had trouble on my last ROM using the Hi-Fi DAC, which really bothered me because part of the reason why I bought this phone was to take advantage of the better audio quality as compared to other phones at the time of its release. Presently, what's the easiest way to take advantage of the DAC on an 8.x AOSP ROM?
Thanks!
Click to expand...
Click to collapse
On Nougat AOSP you can get 192k no problem with Neutron. Literally ANY ROM from here uses the AK4490, because they are all patched now. Stock ROMs will use the AK4490 most of the time but not with the speakers (doesn't really matter) or with Dolby (Does matter) and sometimes it will even turn it off on Youtube for some reason.
I think you can't ger hi-fi in custom Oreo. But now you guys also have B01 and B12 which are stock Oreo and work just fine
Click to expand...
Click to collapse
Choose an username... said:
prmbasheer said:
Why would you "certainly" kill the audio? Why are you so damn sure that it's worse than stock?
---------- Post added at 03:36 AM ---------- Previous post was at 03:32 AM ----------
On Nougat AOSP you can get 192k no problem with Neutron. Literally ANY ROM from here uses the AK4490, because they are all patched now. Stock ROMs will use the AK4490 most of the time but not with the speakers (doesn't really matter) or with Dolby (Does matter) and sometimes it will even turn it off on Youtube for some reason.
I think you can't ger hi-fi in custom Oreo. But now you guys also have B01 and B12 which are stock Oreo and work just fine
Click to expand...
Click to collapse
Didn't nfound say dac works on aex if you use the b10+b32 bootsect?
Click to expand...
Click to collapse
Dodgexander said:
Choose an username... said:
Didn't nfound say dac works on aex if you use the b10+b32 bootsect?
Click to expand...
Click to collapse
It works. I'm on AEX oreo with Hellsgate Kernel and CAD driver for better control over the dac and it works flawlessly with direct pcm players like Neutron and UAPP.
Click to expand...
Click to collapse
Dodgexander said:
Choose an username... said:
Didn't nfound say dac works on aex if you use the b10+b32 bootsect?
Click to expand...
Click to collapse
yes, ergo, it works on all ROMs
---------- Post added at 04:43 PM ---------- Previous post was at 04:43 PM ----------
wannaskoo said:
Dodgexander said:
It works. I'm on AEX oreo with Hellsgate Kernel and CAD driver for better control over the dac and it works flawlessly with direct pcm players like Neutron and UAPP.
Click to expand...
Click to collapse
I'm actually pretty sure that AEX already has the CAD driver integrates
Click to expand...
Click to collapse
Click to expand...
Click to collapse
I'm confused, first you said you can't get it working in custom oreo but now you are saying you can?
As far as I'm aware the CAD driver was to make oreo roms work that didn't have support, aex always has with the b10+b32 bootstack.
I guess it also gives you more control..the cad settings that is.
Dodgexander said:
I'm confused, first you said you can't get it working in custom oreo but now you are saying you can?
As far as I'm aware the CAD driver was to make oreo roms work that didn't have support, aex always has with the b10+b32 bootstack.
I guess it also gives you more control..the cad settings that is.
Click to expand...
Click to collapse
You can't get hi-fi in Oreo, that's that. Now, the DAC, sure. Those are two different things. Apps can't get direct_pcm output for some reason. But the AK4490 processes stuff just fine, albeit @48KHz.
The CAD driver was to be able to change the DAC's filters, only that. i.e. super-slow and stuff. It may or may not have added support on ROMs.
aosp said:
Yes I have and I'll be surprised if any other audio player will sound more Hi-Fi then UAPP besides the craptastic stock player
Click to expand...
Click to collapse
I don't know what do you mean "more HIFI" because the stock player is quite good and precise in the term of sound quality.
I have tested it with the best soundcards A/B.
Functionality is another story.
I hope your tip will work anyway...
Androowner said:
I don't know what do you mean "more HIFI" because the stock player is quite good and precise in the term of sound quality.
I have tested it with the best soundcards A/B.
Functionality is another story.
I hope your tip will work anyway...
Click to expand...
Click to collapse
nice 6 month bump fam
Choose an username... said:
nice 6 month bump fam
Click to expand...
Click to collapse
And whats the problem with it ?
if my Axon7 guarantie goes over in december, I will thinking to go with AOSP or other custom rom. Sound is the most important for me. Now I have a little time to read again forums... And checking whats happened since than.
Also subscribed fans get this 6 mount bump letter also...
(also the stock player is real pain, would be great to use all the media through DAC)
Stock ROM is unable to do this, but can't move yet to custom ROM...
Androowner said:
And whats the problem with it ?
if my Axon7 guarantie goes over in december, I will thinking to go with AOSP or other custom rom. Sound is the most important for me. Now I have a little time to read again forums... And checking whats happened since than.
Also subscribed fans get this 6 mount bump letter also...
(also the stock player is real pain, would be great to use all the media through DAC)
Stock ROM is unable to do this, but can't move yet to custom ROM...
Click to expand...
Click to collapse
the problem is that you annoy everyone with a dead thread about something that seemingly was never really agreed upon. Honestly I'm about to make a thread explaining the facts if this keeps going (It'll get buried but whatever)
Point is, ALL SOUND GOES THROUGH THE DAC THAT IS SELECTED AT THE TIME (Unless you use Atmos, which will select the 4961 [crappy one])
If you want hifi off of another app, then use Poweramp or Neutron or that UAPP thing (i never tested it). They handle 192k just fine, proven.
Same story on custom ROMs since Nougat. GSIs are a bit more complex.
Poweramp's sound engine absolutely obliterates the stock app's sound.
Choose an username... said:
the problem is that you annoy everyone with a dead thread about something that seemingly was never really agreed upon. Honestly I'm about to make a thread explaining the facts if this keeps going (It'll get buried but whatever)
Point is, ALL SOUND GOES THROUGH THE DAC THAT IS SELECTED AT THE TIME (Unless you use Atmos, which will select the 4961 [crappy one])
If you want hifi off of another app, then use Poweramp or Neutron or that UAPP thing (i never tested it). They handle 192k just fine, proven.
Same story on custom ROMs since Nougat. GSIs are a bit more complex.
Poweramp's sound engine absolutely obliterates the stock app's sound.
Click to expand...
Click to collapse
Can any PIE rom play 192khz?
residento said:
Can any PIE rom play 192khz?
Click to expand...
Click to collapse
don't think so, but LOS 16 will probably be the only candidate as GSIs have hideous audio
I'm not Rooted and i'd like to be able to use Banking Apps, so 'Enforcing' is a must. .
Better still if the ROM has a Kernel that bypasses the Bootloader checks and passes Safetynet. I've just got my OP5 today so i'm playing catch-up. Resurrection Remix on the OP3T does all of the above out of the box, but not on this device, strangely.
TIA.
Try OmniROM
arvindgr said:
Try OmniROM
Click to expand...
Click to collapse
You're right, they do have selinux Enforcing. Nice one. The feature set is a bit sparse though. I might hold out in hope that the RR devs make a change in their build. It would be easier to communicate with the dead than successfully begin a dialogue with their team though.
DirkGently said:
You're right, they do have selinux Enforcing. Nice one. The feature set is a bit sparse though. I might hold out in hope that the RR devs make a change in their build. It would be easier to communicate with the dead than successfully begin a dialogue with their team though.
Click to expand...
Click to collapse
I am with some of the most developer friendly phones - Mido
I was using RR for years together. But there update frequency was not that great and overall ROM is definitely not that seem-less. Some or other thing would break somewhere every now and then. Also I got fed up doing clean flash and have Issues over previous app data. Not a major issue but its always like that in xda
Here in Omni - One master Gerrit which neatly tracks all changes for every device (Most ROMs isn't so transparent)
OTA updates in delta and it never breaks anything!
All features in ROM though are limited work so seem-less as a family.
Overall stability is always a priority
Initially I too felt features list is limited. But after sometime I got so used everything., In a way i have to ensure my next phone would support Omni... Thanks @maxwen
First of all I would like to thank all the great devs that keep supporting this phone.
But I miss a really bugless ROM. ROMs with 3.18 kernel were almost perfect, but they aren't developed anymore. 4.9 kernel is great too, but it has some annoying (for me at least) limitations. Miui camera doesn't work properly and it's a pity because it's the only app (as far as I know) that can use both sensors at the same time. Nhappyman's camera module isn't working (no smooth videos and no long exposure).
Mtp and vibration aren't working in TWRP custom recovery.
Is there any developer that can build an updated ROM based on 3.18 kernel? I bought a Mi A1 for dual-camera setup and I would like to use his full potential with MIUI camera AND GCam. At the moment it's possible only on 3.18 kernel so I'm wondering if there is any "brave" Dev who wants to go that way. I think that many other users like me are waiting for that. Am I wrong?
You're right, I agree with you. Of course it is quite an achievement for the development of this device, and I actually enjoy the new kernel and it's securities advancements, but it is not stable compared to the officially supported 3.18. For example, I have a Quick charger but can't use it properly because it's not working on kernel 4.9, at least right know.
Not being ungrateful btw, I totally support the continuous development of 4.9, and I hope someday it will be just as stable as 3.18.
sipollo said:
First of all I would like to thank all the great devs that keep supporting this phone.
But I miss a really bugless ROM. ROMs with 3.18 kernel were almost perfect, but they aren't developed anymore. 4.9 kernel is great too, but it has some annoying (for me at least) limitations. Miui camera doesn't work properly and it's a pity because it's the only app (as far as I know) that can use both sensors at the same time. Nhappyman's camera module isn't working (no smooth videos and no long exposure).
Mtp and vibration aren't working in TWRP custom recovery.
Is there any developer that can build an updated ROM based on 3.18 kernel? I bought a Mi A1 for dual-camera setup and I would like to use his full potential with MIUI camera AND GCam. At the moment it's possible only on 3.18 kernel so I'm wondering if there is any "brave" Dev who wants to go that way. I think that many other users like me are waiting for that. Am I wrong?
Click to expand...
Click to collapse
You can use LR v10.0.3 it's still based on 3.18 based kernel. Or go for Revenge OS, it's also 3.18 based
I'm not going to say anything about TWRP installer that was never supported officially by TeamWin or quick chargers that aren't even supported by our device, but I have a few things that I want to say specifically about MIUI Camera (and the reason why I'm always acting cocky when someone talks about it).
Supporting it was and always will be too much of a hassle for developers. It's not because "damn devs don't care about meme camera", but rather because whatever Xiaomi does for their camera features is very far from perfect, tends to break very often and also introduces random issues with third-party camera apps.
Recent switch to the open source camera HAL helped us to get a much more stable and reliable base (as well as fixing some very annoying issues we had before) but it also was the final nail in the coffin of MIUI Camera as it relies on undocumented proprietary features that we can't implement in any possible way.
I know that it can be hard for someone to cope with the lack of some well advertised marketing feature essential camera functionality, but we also have to go to concessions to make our support continuous and more future-proof.
flex1911 said:
I'm not going to say anything about TWRP installer that was never supported officially by TeamWin or quick chargers that aren't even supported by our device, but I have a few things that I want to say specifically about MIUI Camera (and the reason why I'm always acting cocky when someone talks about it).
Supporting it was and always will be too much of a hassle for developers. It's not because "damn devs don't care about meme camera", but rather because whatever Xiaomi does for their camera features is very far from perfect, tends to break very often and also introduces random issues with third-party camera apps.
Recent switch to the open source camera HAL helped us to get a much more stable and reliable base (as well as fixing some very annoying issues we had before) but it also was the final nail in the coffin of MIUI Camera as it relies on undocumented proprietary features that we can't implement in any possible way.
I know that it can be hard for someone to cope with the lack of some well advertised marketing feature essential camera functionality, but we also have to go to concessions to make our support continuous and more future-proof.
Click to expand...
Click to collapse
Totally understandable, it's not rocket science to know that exclusive "features", which is closed source, is really hard (mostly impossible) to port to custom development. Many devices suffers from this, like the implementation on Moto display on Motorola phones, for example. I'm not a developer myself, but I know a thing or two with my experience as android enthusiast, and for development to work it means you're gonna let some "goodies" go in favor of it.
Thanks for your work btw!
Shubham2509 said:
You can use LR v10.0.3 it's still based on 3.18 based kernel. Or go for Revenge OS, it's also 3.18 based
Click to expand...
Click to collapse
Revenge use 4.x now, so the only updated rom with 3.18.x is Lineage 15.1
Never_Sm1le said:
Revenge use 4.x now, so the only updated rom with 3.18.x is Lineage 15.1
Click to expand...
Click to collapse
In the next update ROS will be updated with 3.18
Shubham2509 said:
In the next update ROS will be updated with 3.18
Click to expand...
Click to collapse
Really? Nice, have been looking for an updated pie rom running 3.18
Now that Flex gave us the possibility to use miui camera on 4.9 kernel there's no need of 3.18 anymore (IMHO). To use MTP on TWRP we can boot it from PC and it will work.
Touch screen misbehaves with 4.x kernel
My mi a1 touch screen misbehaves with 4.9 kernel.
So i have to stick with the stock rom even i want to use a custom rom.
Am i the only person facing to this kind of problem?
Same problem here guys, anyone know how to fix this? :crying:
sujiththilakasiri said:
My mi a1 touch screen misbehaves with 4.9 kernel.
So i have to stick with the stock rom even i want to use a custom rom.
Am i the only person facing to this kind of problem?
Click to expand...
Click to collapse
Me too, in fact my screen doesn't work at all with 4.9 kernel. It was a cheap replacement from aliexpress. I was hoping to find some updated ROMs with 3.18 but I will have to just stick to stock. It's a shame.