Hi,
I have an HTC Vivid running albinoman887's CM11 4/24/14 nightly, and the 4/26a PA GApps. Everything seems to run smoothly except for the fact that the latest Google Camera update force closes, so I cannot use that app at all to take pictures or shoot video. I haven't yet found a way to revert to the older version so on a side note if someone can point me to that APK I'd be greatly appreciative.
At any rate, other camera apps like A Better Camera and CameraMX do a great job of taking still photos, but neither one will invoke the video recording function. I have updated to the latest nightly of both CM11 and PA GApps, and the reason why I'm on the older versions is because the newer builds caused problems, so I clean flashed back to the older ones.
I downloaded a couple of diagnostic apps and neither one seems to indicate the presence of video recording function. I don't know if that's normal for those apps or if there's some damaged hardware involved. I don't want to go all the way back to stock to test that theory, so if anyone has had any similar problems or has some insight to offer, I'd really appreciate it. The lack of video recording is not a backbreaker for me, but it's one of those minor annoyances that I absolutely hate - kind of like a wart. TIA for any help you can offer.
falcon7204 said:
Hi,
I have an HTC Vivid running albinoman887's CM11 4/24/14 nightly, and the 4/26a PA GApps. Everything seems to run smoothly except for the fact that the latest Google Camera update force closes, so I cannot use that app at all to take pictures or shoot video. I haven't yet found a way to revert to the older version so on a side note if someone can point me to that APK I'd be greatly appreciative.
At any rate, other camera apps like A Better Camera and CameraMX do a great job of taking still photos, but neither one will invoke the video recording function. I have updated to the latest nightly of both CM11 and PA GApps, and the reason why I'm on the older versions is because the newer builds caused problems, so I clean flashed back to the older ones.
I downloaded a couple of diagnostic apps and neither one seems to indicate the presence of video recording function. I don't know if that's normal for those apps or if there's some damaged hardware involved. I don't want to go all the way back to stock to test that theory, so if anyone has had any similar problems or has some insight to offer, I'd really appreciate it. The lack of video recording is not a backbreaker for me, but it's one of those minor annoyances that I absolutely hate - kind of like a wart. TIA for any help you can offer.
Click to expand...
Click to collapse
Yeah, I had the same problem with video on the older nightlies. I am now on 5/7 build and video works great using any of several different cameras.
So this is our main problem.
Logcat says only: bufferitemconsumer: [stagefright-camerasource] failed to release buffer: unknown error -1
It's only related to google and aosp camera. every other cam working without this logcat message.
According to google we got this info:
http://forum.xda-developers.com/attachment.php?attachmentid=3887247&stc=1&d=1474924978
http://forum.xda-developers.com/attachment.php?attachmentid=3887250&stc=1&d=1474925299
Pass metadata in video buffers(HAL1 only). If HAL1 stores metadata instead of real YUV frame data in video buffers, the HAL must not store anything that is invalid across process boundaries, including native handles. If HAL passes native handles in the metadata in video buffers, you must update it to use kMetadataBufferTypeNativeHandleSource as the metadata buffer type and pass VideoNativeHandleMetadata in video buffers.
With VideoNativeHandleMetadata, camera and media frameworks are able to pass the video buffers between processes by serializing and deserializing the native handles properly. If HAL chooses to continue using kMetadataBufferTypeCameraSource as the metadata buffer type, the metadata must be able to be passed between processes as plain values.
Buffer handle address does not always store same buffer (HAL3 only). For each capture request, HAL3 gets addresses of buffer handles. HAL cannot use the addresses to identify buffers because the addresses may store another buffer handle after HAL returns the buffer. You must update the HAL to use buffer handles to identify the buffers. For example: HAL receives a buffer handle address A, which stores buffer handle A. After HAL returns buffer handle A, buffer handle address A may store buffer handle B next time the HAL receives it.
Click to expand...
Click to collapse
What do you think about this?
With media.stagefright.codecremote=false prop the glitch is gone and all working fine on aosp camera (but logcat message still persist). But in google camera still persist a green flickering on video record.
Edit:
So. Preview state is fine, Recording state is fine too. It seems the main problem will be stagefright/omx/encoder.
On marsmallow camera related stuff and codecs was in the same process/mediaserver/. Now on nougat camera service is out from mediaserver and it looks like in the code, all the codecs / video encoder and etc / are gone too to a separate codec process.
kamarush said:
So this is our main problem.
Logcat says only: bufferitemconsumer: [stagefright-camerasource] failed to release buffer: unknown error -1
It's only related to google and aosp camera. every other cam working without this logcat message.
According to google we got this info:
http://forum.xda-developers.com/attachment.php?attachmentid=3887247&stc=1&d=1474924978
http://forum.xda-developers.com/attachment.php?attachmentid=3887250&stc=1&d=1474925299
Pass metadata in video buffers(HAL1 only). If HAL1 stores metadata instead of real YUV frame data in video buffers, the HAL must not store anything that is invalid across process boundaries, including native handles. If HAL passes native handles in the metadata in video buffers, you must update it to use kMetadataBufferTypeNativeHandleSource as the metadata buffer type and pass VideoNativeHandleMetadata in video buffers.
With VideoNativeHandleMetadata, camera and media frameworks are able to pass the video buffers between processes by serializing and deserializing the native handles properly. If HAL chooses to continue using kMetadataBufferTypeCameraSource as the metadata buffer type, the metadata must be able to be passed between processes as plain values.
Buffer handle address does not always store same buffer (HAL3 only). For each capture request, HAL3 gets addresses of buffer handles. HAL cannot use the addresses to identify buffers because the addresses may store another buffer handle after HAL returns the buffer. You must update the HAL to use buffer handles to identify the buffers. For example: HAL receives a buffer handle address A, which stores buffer handle A. After HAL returns buffer handle A, buffer handle address A may store buffer handle B next time the HAL receives it.
What do you think about this?
With media.stagefright.codecremote=false prop the glitch is gone and all working fine on aosp camera (but logcat message still persist). But in google camera still persist a green flickering on video record.
Edit:
So. Preview state is fine, Recording state is fine too. It seems the main problem will be stagefright/omx/encoder.
On marsmallow camera related stuff and codecs was in the same process/mediaserver/. Now on nougat camera service is out from mediaserver and it looks like in the code, all the codecs / video encoder and etc / are gone too to a separate codec process.
Click to expand...
Click to collapse
Have you contacted any of the developers working on Nougat? Maybe they could adress this issue. It's kind of the only issue on our Rom's right now.
There is already some work ongoing around this in CM14.
See current merges: http://review.cyanogenmod.org/#/c/165009/ http://review.cyanogenmod.org/#/c/165008/ http://review.cyanogenmod.org/#/c/165140/
Video recording works with this, however, the camera crashes while saving the video with a "Can't connect to camera" error and the recorded video seems broken (meaning it's very sluggish and some frames seem duplicated).
It will eventually be fixed, as all devices pre-n use HAL1, we just need to be patient.
On the bright side, other applications seem to be working, so whoever needs video, can use those.
morphvale said:
There is already some work ongoing around this in CM14.
See current merges: http://review.cyanogenmod.org/#/c/165009/ http://review.cyanogenmod.org/#/c/165008/ http://review.cyanogenmod.org/#/c/165140/
Video recording works with this, however, the camera crashes while saving the video with a "Can't connect to camera" error and the recorded video seems broken (meaning it's very sluggish and some frames seem duplicated).
It will eventually be fixed, as all devices pre-n use HAL1, we just need to be patient.
On the bright side, other applications seem to be working, so whoever needs video, can use those.
Click to expand...
Click to collapse
Yes i know this.
But just for understand the problem. Google Camera now uses Camera API version 2 (at MM used Camera API version 1), so we need to update the HAL's buffer handle to be able to pass and release buffers between separate processes.
AOSP Camera and CM's Snap uses Camera API version 1, which is fine with our HAL with media.stagefright.codecremote=false prop. It's completely working.
So if @Santhosh M put the prop in the build, CM will be complete.
kamarush said:
Yes i know this.
But just for understand the problem. Google Camera now uses Camera API version 2 (at MM used Camera API version 1), so we need to update the HAL's buffer handle to be able to pass and release buffers between separate processes.
AOSP Camera and CM's Snap uses Camera API version 1, which is fine with our HAL with media.stagefright.codecremote=false prop. It's completely working.
So if @Santhosh M put the prop in the build, CM will be complete.
Click to expand...
Click to collapse
Will do the same
With some kernel related changes/patches now we can use all the camera apps without disabling the remote codecs. Except Google Camera....
Still don't know what causing that green flashes, but this is again one step forward.
@Santhosh M @yashade2001 @ganachoco @Mr.MEX
So guys i was completely wrong
With my last changes to dev-tree/QCamera2 and kernel Aosp Camera2 worked fine without disabling mediacodecs, but was still problem with Google Camera. So my fault was i always tried with GoogleCamera 3.X which was released with N dev preview. But the last N5 officially supported GoogleCamera is 2.7.008, and with that its working completely fine (HDR+ too) :good: No green flashes no glitches, so it's working fully. No need mediaserver and other hacks!
Feel free use it on your builds guys!
Cheers
kamarush said:
@Santhosh M @yashade2001 @ganachoco @Mr.MEX
So guys i was completely wrong
With my last changes to dev-tree/QCamera2 and kernel Aosp Camera2 worked fine without disabling mediacodecs, but was still problem with Google Camera. So my fault was i always tried with GoogleCamera 3.X which was released with N dev preview. But the last N5 officially supported GoogleCamera is 2.7.008, and with that its working completely fine (HDR+ too) :good: No green flashes no glitches, so it's working fully. No need mediaserver and other hacks!
Feel free use it on your builds guys!
Cheers
Click to expand...
Click to collapse
I knew 2.7 worked since long, just that i was figuring out for latest versions
kamarush said:
@Santhosh M @yashade2001 @ganachoco @Mr.MEX
So guys i was completely wrong
With my last changes to dev-tree/QCamera2 and kernel Aosp Camera2 worked fine without disabling mediacodecs, but was still problem with Google Camera. So my fault was i always tried with GoogleCamera 3.X which was released with N dev preview. But the last N5 officially supported GoogleCamera is 2.7.008, and with that its working completely fine (HDR+ too) :good: No green flashes no glitches, so it's working fully. No need mediaserver and other hacks!
Feel free use it on your builds guys!
Cheers
Click to expand...
Click to collapse
This is weird. In Android MM with custom roms like Dirty Unicorns or even in Stock MM provided by Google the Google Camera was working fine and let me to update it on Play Store. That brings a new UI where you can just swipe left and right to switch between photo and video mode.
I just tested the Google Camera that you provided (http://www.apkmirror.com/apk/google...-2130300-30-m-preview-3-android-apk-download/) and it works fine, but the UI is the old one.
Also you get the notification in the Play Store to update it, which brings the new UI and brokes video recording, so I think something is still wrong.
Sadly I can't install MM back to check what google camera version I had since I need to attend important stuff this days with phone. I'm getting a new phone someday next week(in like 1 to 3 days) and I will be able to gladly help you guys to test stuff.
Jaizu said:
This is weird. In Android MM with custom roms like Dirty Unicorns or even in Stock MM provided by Google the Google Camera was working fine and let me to update it on Play Store. That brings a new UI where you can just swipe left and right to switch between photo and video mode.
I just tested the Google Camera that you provided (http://www.apkmirror.com/apk/google...-2130300-30-m-preview-3-android-apk-download/) and it works fine, but the UI is the old one.
Also you get the notification in the Play Store to update it, which brings the new UI and brokes video recording, so I think something is still wrong.
Sadly I can't install MM back to check what google camera version I had since I need to attend important stuff this days with phone. I'm getting a new phone someday next week(in like 1 to 3 days) and I will be able to gladly help you guys to test stuff.
Click to expand...
Click to collapse
It's because from v3 GoogleCamera uses API2. On marshmallow this was fine. Android 7.x's camera framework hardening prevents us from using it without HAL changes or framework hacks.
To sum up google camera version that I use on Nougat
- 2.7.008 hdr+ ok. Video rec ok
- 3.2.045 hdr+ ok. Video rec not ok ( this version is the last for N5 on MM with no issues in video rec)
- 4.1.006 hdr+ not ok. Video recording not ok
Hdr+ not ok meaning no processing done. No difference of output between non hdr+ and hdr+ photos
amnher said:
To sum up google camera version that I use on Nougat
- 2.7.008 hdr+ ok. Video rec ok
- 3.2.045 hdr+ ok. Video rec not ok ( this version is the last for N5 on MM with no issues in video rec)
- 4.1.006 hdr+ not ok. Video recording not ok
Hdr+ not ok meaning no processing done. No difference of output between non hdr+ and hdr+ photos
Click to expand...
Click to collapse
With my latest patches we can go up to 3.1.x.
After a lot of debug, now i'm relatively sure what causing the problem, but i needed to stop development. Because my phone is accidentally dropped into water and now it's dead
Sorry guys
@kamarush
too bad you're one hell of developer like the old days when I was still on xperia mini(Smultron) well hope someone can continue your work
kamarush said:
With my latest patches we can go up to 3.1.x.
After a lot of debug, now i'm relatively sure what causing the problem, but i needed to stop development. Because my phone is accidentally dropped into water and now it's dead
Sorry guys
Click to expand...
Click to collapse
Willing to share? Thanks in advance.
JulianXhokaxhiu said:
Willing to share? Thanks in advance.
Click to expand...
Click to collapse
Just check his github
First of all, we need to port this commit. this would have been my next step.
https://android.googlesource.com/platform/hardware/qcom/camera/+/ecc5ece9eff7c7855faf676881d0aba59c1bd1db%5E!/
Then we can check things further.
It's fixed in Dark's 7.1 CM14.1 ROM. Using 4.2 without issue. Haven't confirmed for sure if HDR+ is working properly, but from the extra delay after taking a shot I'd guess it is.
snives said:
It's fixed in Dark's 7.1 CM14.1 ROM. Using 4.2 without issue. Haven't confirmed for sure if HDR+ is working properly, but from the extra delay after taking a shot I'd guess it is.
Click to expand...
Click to collapse
No it's not. That's only a workaround (hack) for mediaserver and cameraserver.
We can deal with the real problem, as we have the complete source for camera and media/display. Just need a real developer who understand bufferqueue, native_ and buffer_handle_t functions and gralloc. To continue my work.
So, workarounds are not real fixes imo.
kamarush said:
No it's not. That's only a workaround (hack) for mediaserver and cameraserver.
We can deal with the real problem, as we have the complete source for camera and media/display. Just need a real developer who understand bufferqueue, native_ and buffer_handle_t functions and gralloc. To continue my work.
So, workarounds are not real fixes imo.
Click to expand...
Click to collapse
why do u need that?
the latest camera with the latest hal is working!
Sent from my Nexus 5 CAF using Tapatalk
santi1993 said:
why do u need that?
the latest camera with the latest hal is working!
Sent from my Nexus 5 CAF using Tapatalk
Click to expand...
Click to collapse
The point is, we have the whole source. Hal3 can be fixed without "dirty" patches on fw to stay clear the source.
These workarounds completely disables a huge size of the security measures introduced by Google in N.
These only for devices which don't have access to Camera HAL or encoder sources, or has old blobs.
Btw for temporary solution is good, but need to patch up correctly the HAL.
Hello,
Are there any Pie based roms for Redmi 4X which do not have problems with Facebook app? It stutters like crazy while scrolling. Some stutter may be seen in Playstore also. No such thing happens on Oreo based roms.
Turn off auto video play, reduce image quality to medium. Its none of rom or kenel's fault. Its a app which isnt optimised for smooth scrolling.
Amit_mishra said:
Turn off auto video play, reduce image quality to medium. Its none of rom or kenel's fault. Its a app which isnt optimised for smooth scrolling.
Click to expand...
Click to collapse
I always turn off auto play. How does it happen that this app is "not optimised" for smooth scrolling while on Oreo based roms it works great?
Try CAF roms, they are already faster and smoother...
Where are the CAF roms listed please ?
ryback64 said:
Where are the CAF roms listed please ?
Click to expand...
Click to collapse
Search in the telegram r4x community. I prefer up to date Roms..
DoctorRzepa said:
Hello,
Are there any Pie based roms for Redmi 4X which do not have problems with Facebook app? It stutters like crazy while scrolling. Some stutter may be seen in Playstore also. No such thing happens on Oreo based roms.
Click to expand...
Click to collapse
I will answer myself: LineageOS 16, new builds. Facebook app somehow becomes "optimised" on those ROMs like someone said. <sarcasm> Of course it can't be rom or kernel fault </sarcasm>.
I am experiencing serious problem with scrolling performance on instagram whatsapp and stock contacts app is it only me experiencing this? Before also with some updates it was happening but later they were fixing but it is so awkward after all this updates i am still not happy about performance
Erofs game turbo etc i think they were a big marketing hoax
Game turbo does work on some games that are optimized for it (like Minecraft and fortnite for example). I mainly saw that the heat is decreased, not very significantly.
If you have scrolling lag, stop using battery saving option. It is useless as it kills features for just +10 minutes of battery life (from my own experience)
ahmetgox said:
I am experiencing serious problem with scrolling performance on instagram whatsapp and stock contacts app is it only me experiencing this? Before also with some updates it was happening but later they were fixing but it is so awkward after all this updates i am still not happy about performance
Erofs game turbo etc i think they were a big marketing hoax
Click to expand...
Click to collapse
What resolution are you using? Make sure smart is turned off and it's on FHD not HD, this bugs out recording videos too. I'm on 370 and WhatsApp is fine, although I using WhatsApp plus
i'm using Samsung s5 , i've tried many custom roms like lineage os and hovac os based on android 9 and android 10 and i've been seeking for a rom that contain some features like low audio latency ( bcz i'm using my phone as guitar pedal ) multi window resizable support , and good gaming experience , and i noticed that with every rom one of these features is missing , lineage os 16 gives a pretty low audio latency but when it comes to gaming it's a little bit laggy and it have a problem supporting resizable windows , and 17 is still with a lot of bugs , hovac os 3.4 comes with an amazing gaming experience except the audio latency is very high and it crushes every time u try to use resizable windows.
about the audio latency i've done many researches on the internet and the only solution that may be can work is to change the audio buffering size , but i really didn't find how to do it on android , can anyone help me with that ? also how i can record audio from two apps in the same time ? i was using another phone model ( condor p6 pro lte running android 7 ) and i could record from two apps in the same time with low latency