I don't know where to post/report this exactly... So I'm posting it here for now.
I've discovered that all the AOSP based ROM's for our OPO are missing some files, that causes an bug:
Some media/video streams on internet are not working, and causes an black frozen screen, after 1/2 minute(s) that you did try to start the video-stream... (You have to force reboot your device with the hardware buttons when you're experiencing this bug)
The Stock CM11S ROM doesn't have this bug, only ALL the AOSP ROM's.
So I've compared all the files differences between those 2 ROM's (latest 30O Stock ROM & latest CM11 nightly), and I discovered that the CM11 nightly (and all the other OPO AOSP based ROM's) are missing some files in the /system/vendor folder that are causing this bug...
I see that those files are included with CM11 niglties for other devices, but not with the CM11 nightlies for our OnePlus
And no, those files are also not included in ANY GAPPS package!!
Thus I've tried adding those files to the latest CM11 nightly that I have installed on my OPO... and guess what it did fix this problem, and video streams are now working properly (and not getting the black screen of dead anymore!)
The missing files that I'm talking about are the following ones:
/system/vendor/lib/mediadrm/libwvdrmengine.so
/system/vendor/lib/libwvdrm_L3.so
/system/vendor/lib/libwvm.so
/system/vendor/lib/libWVStreamControlAPI_L3.so
So I've made an flashable fix for this if you're also experiencing this bug.
You can use it on any AOSP based ROM.
The source of those files are the latest 30O CM11S Stock ROM.
Download for the AOSP Streaming FIX:
(NOT needed when you're on CM11S Stock based ROM's!!)
DOWNLOAD
If anyone knows where I can report this bug to Cyanogenmod then let me know pls.
You can report bugs to cm here: https://jira.cyanogenmod.org/secure/Dashboard.jspa
Can you be more specific on how this problem is triggered? I've always ran CM nightlies and never had any trouble with streaming.
They have integrated the files/fix in nightly 20-8
See those links:
https://jira.cyanogenmod.org/browse/CYAN-5071
http://review.cyanogenmod.org/#/c/70794/
I can confirm the widevine files are present now. DRM media should work now.
A temporary Xposed fix for part of Lollipop 5.0.x memory leak issues has just been released by tonyp.
It might be interesting for those of you running Lollipop ROMs and being annoyed by this issue.
According to tonyp, the Android 5.1 fix has already been implemented in CM12 for two weeks, so for those running CM12 nightlies there is no need to use this fix. The fix should therefore also be present in new versions of Lollipop CM12-based ROMs, but until then it could be a relief.
So feel free to test it and tell us if it shows improvements!
So some newer devices have been shipped with different components from the older ones and while everything works fine on recent miui versions, most custom roms have issues. So I'm creating this thread to document all the issues caused by these new components and any solutions to them in one thread. Please reply if you have any other issues caused by the new hardware or any solutions to them.
Fingerprint
Description:
Option to add fingerprints doesn't appear even after setting pin, pattern or password on non miui based roms.
/data folder contains goodix folder with contents on miui.
Cause:
Some devices have a new fingerprint sensor manufactured by Goodix which is not yet supported by non miui based roms.
Solutions:
miui and any miui based roms such as xiaomi.eu should still work fine.
The newest build of Santosh's CM has a fingerprint patch available that will fix it.
Wait for CM to add support for the new hardware to its source code.
Battery
Description:
Battery is stuck at either -2% or 50%.
TWRP does not show battery percentage at all or constantly shows 50%.
Cause:
Possibly new battery controller hardware, by the looks of it the issue is related to the kernel, older CM kernel builds seem fine and so do newer miui builds however any rom using a new CM kernel build or based off it has the issue.
Solutions:
Fix was added to CM source code so the problem should be solved on all newer roms and kernels based on it now.
Flashing Radon 1.9 or above will fix it on any CM source based roms.
miui and other miui based roms such as xiaomi.eu should be fine.
Santosh's CM13 plust the camera fix works.
Mokee works fine.
Unofficial Ressurrection Remix works fine up until the 06/08 build.
This is the patch applied to Radon to fix the bug.
If you know of any other issues caused by newer hardware or solutions please tell me so that I can add it to this thread.[/QUOTE]
If possible, Can you also provide information about how to identify different components without changing roms?
Thank you.
dmemon said:
If possible, Can you also provide information about how to identify different components without changing roms?
Thank you.
Click to expand...
Click to collapse
Added for the fingerprint sensor, using TWRP is still probably the easiest way to check for the battery bug.
dmemon said:
If possible, Can you also provide information about how to identify different components without changing roms?
Thank you.
Click to expand...
Click to collapse
The sensor of fingerprints with aida64, it is possible to identify.
The battery only if flash the TWRP, for the present.
Santhosh's CM13 battery bug is gone if you flash his camera fix.
razr96 said:
Santhosh's CM13 battery bug is gone if you flash his camera fix.
Click to expand...
Click to collapse
Ok cool I'll add it to the post and test it out if I get a chance.
I hear of that Mokee is using Xiaomi device tree, I guess that is why it don't has the "-2% or 50%" issue...
NTRNSTR said:
Description:
Battery is stuck at either -2% or 50%.
TWRP does not show battery percentage at all or constantly shows 50%.
Cause:
Possibly new battery controller hardware, by the looks of it the issue is related to the kernel, older CM kernel builds seem fine and so do newer miui builds however any rom using a new CM kernel build or based off it has the issue.
Solutions:
Santosh's CM13 plust the camera fix should fix it.
Click to expand...
Click to collapse
The camera fix works only with Santosh's CM13, not with other CM/AOSP roms
the new kernel Radon V1.8 by Umang96 does not fix the battery problem
EkiFox said:
The camera fix works only with Santosh's CM13, not with other CM/AOSP roms
the new kernel Radon V1.8 by Umang96 does not fix the battery problem
Click to expand...
Click to collapse
I would expect it to work on all Santosh based roms, the camera fix must have modified something that flashing a new kernel overwrites, if we can figure out what the camera fix changes we might be able to get a fix for all roms.
---------- Post added at 02:11 PM ---------- Previous post was at 02:10 PM ----------
dna1982 said:
I hear of that Mokee is using Xiaomi device tree, I guess that is why it don't has the "-2% or 50%" issue...
Click to expand...
Click to collapse
Well that would explain it, but at least we have roms without the bugs, that should help figure out the problem.
any working custom kernels for -2% or 50% battery bug?
mega-samu said:
The sensor of fingerprints with aida64, it is possible to identify.
The battery only if flash the TWRP, for the present.
Click to expand...
Click to collapse
as far as i know AIDA64 is not a good way to see your fingerprint sensor it shows fpc102x for me but i have a goodix sensor, in fact i think the other ones with fpc sensors have a fpc 1035 not a 102x. i think a good was would be checking kernel log you should see the module name or checking data partition ( if you have root) or system/etc/firmware if you dont (i'm not sure about the second one but i can see some goodixfp data there)
just saying maybe it saves someone from lots and lots of confusion as i had when i bought my device
The new Radon kernel doesn't have the -2%/50% battery bug!
For the cm13 based roms : http://forum.xda-developers.com/showthread.php?p=68012485 and few posts under there is a test version for MIUI rom
Reno_kun said:
The new Radon kernel doesn't has the -2%/50% battery bug!
For the cm13 based rom : http://forum.xda-developers.com/showthread.php?p=68012485 and few posts under there is a test version for MIUI rom
Click to expand...
Click to collapse
:victory: Now we can use any Official-CM based rom. Definitely adding this to the top of the list.
Reno_kun said:
The new Radon kernel doesn't has the -2%/50% battery bug!
For the cm13 based rom : http://forum.xda-developers.com/showthread.php?p=68012485 and few posts under there is a test version for MIUI rom
Click to expand...
Click to collapse
Yep just flashed official RR with this kernel and no battery bug!
Yes, there is just the lack of the support ou goodix fp and it will be perfect !
KaciPL said:
any working custom kernels for -2% or 50% battery bug?
Click to expand...
Click to collapse
Now there are, just updated the post.
Radon V1.9 Kernel does not cause the battery bug .......
Radon V1.9 Kernel does not cause the battery bug on "MIUI 8 by Xiaomi.eu 6.7.28 | Beta".
I got a test version from @Umang96 and successfully got below 50% battery level.
Any custom kernel working with goodfix fp ??
Sent from my Redmi Note 3 using Tapatalk
I lose data connection on any cm custom rom. It goes away for 50-60sec then it gets back
And if i flash radio zip, then security options crash
LiRi2000 said:
Any custom kernel working with goodfix fp ??
Sent from my Redmi Note 3 using Tapatalk
Click to expand...
Click to collapse
I don't think so, still a work in progress getting it to work.
Please fix this problem on los/rr and other roms.
On G530H/FZ XCU models
@Has.007
@RioFebrian
I tryed cm camera fix and changing libs but doesnt work//lh3.googleusercontent.com/NggOrMno4UzBT2XbU1TQvcRIknkFseiC83OPop9UXU_2c6Ea7uKJXfs8VUk3AmXgLXtvPg=s85
no there is problem with that rom
Video recording doesn't work.
Neither stock nor installed camera apps...
I am using rr. There are no such problem.
fix this problem
ilhamisayev said:
Please fix this problem on los/rr and other roms.
On G530H/FZ XCU models
@Has.007
@RioFebrian
I tryed cm camera fix and changing libs but doesnt work//lh3.googleusercontent.com/NggOrMno4UzBT2XbU1TQvcRIknkFseiC83OPop9UXU_2c6Ea7uKJXfs8VUk3AmXgLXtvPg=s85
Click to expand...
Click to collapse
my friend just pull the battery out when the device is running and then put it back and turn the device on againe this problem happened to me and I searched for solution for very long time and finally I find the solution by Coincidence hhhhh
I'm having the same problem with RR since about 4 months. Can't use my rear camera. It is being detected but can't be used (tried any camera app). When I installed RR, it worked. I have this error since changing my display.
Try to Google it, there are some unofficial fixes out there but I'm not sure if they're really working. I would regard an official fix, but this will have to wait I think.
Such bug has already been fixed with each ROMs' respective latest builds.
Mine too I got a distorted camera but whenever I capture it captures normally, I haven't tried using other camera apps
I've got the same problem
im using footej camera now and it's ok
What is the status on proximity sensor issue in AOSP ROMs? Here in xda and telegram groups people are trying to tell Me that it is fixed but I am sure that there is no permanent solution for this hardware issue. I have tried about half of ROMs here on xda and all after a while have issues whit proximity sensor. I have tried workarounds, calibrated it but still - nothing fixes it. Maybe because I use latest EEA ROM is the issue and I need to flash Global ROM?
You can try adding
"ro.lge.proximity.delay=150
mot.proximity.delay=150"
to your build.prop file in root/system. It fixed the issue on a few roms for me.