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.
Related
EDIT: [email protected] has been added to nightly and bitrate has been set to 12mbps which is not that bad. Its hence not recommended to flash these anymore. If you want higher bitrate look in the thread for those. I think it was pastime who made them. Alternatively use root explorer to manually edit /etc/mediaprofiles.XML. again, read pastimes and related posts in the thread on that.
This will replace the Camera.apk from CM7 with a more tegra2 friendly version that enables [email protected] recording. There's also included an updated media_profiles.xml file that'll enable different bitrates. Choose wisely . To test the bitrate I recommend having it running for at a minute to make sure everything can keep up. Usually it starts out smooth and then starts stuttering as the ram gets filled up. I also upped the quality for still.
Videos (I'll add experimental stuff as well, such as ultra high bitrates and auto focus):
http://www.youtube.com/user/O2XdevVids
I would stay away with 64mb ram hacks for the time being. Maybe we can find some middle ground in the future .
Anyway, please give me feedback on how it works. Some beautiful videos would be nice. Weather is really depressing here.
Please don't use this for non-tegra 2 devices.
Also, I'm experimenting a lot. Expect a lot to be buggy. I do my best not to put something out that doesn't work, but a couple of runs is really the extend of my testing before it goes up (to be honest). The autofocus-mod is seriously buggy. The bitrate-mod should be pretty much as buggy as the std. cm7 Camera app.
And, of course, thx to all the great ppl who works on cm.
------------------------------------------------------------
Source code (just the 1080p mod):
https://github.com/LeJay/Camera
Versions & Changelog & TODO
--------------Autofocus1.1----------------- (Note this is horribly buggy)
Just adds auto focus (and 25/30fps if you're on nightly), no change to bitrate. Flash this AFTER you do the bitrate mods. Flashing with any of the bitrate mods will replace the Camera app and you'll lose autofocus.
----------------------------------------------
--------------FullHDmod 1.0---------------
->Video:
HD: [email protected]@20mbps
High: [email protected]@12mbps
----------------------------------------------
--------------FullHDmod_high 1.0---------- (works for some, requires fast sd card)
->Video:
HD: [email protected]@26mbps
High: [email protected]@12mbps
----------------------------------------------
--------------FullHDmod_mid 1.0---------- (Recommended)
->Video:
HD: [email protected]@17mbps
High: [email protected]@12mbps
----------------------------------------------
--------------FullHDmod_low 1.0----------
->Video:
HD: [email protected]@14mbps
High: [email protected]@12mbps
----------------------------------------------
--------------FullHDmod_LG 1.0---------- (It's the settings used as stock LG... except for 1080p being 30fps)
->Video:
HD: [email protected]@9mbps
High: [email protected]@4mbps
----------------------------------------------
----------BitrateMod(720p only)---------- (Does not replace Camera.apk. Works for 64mb ram hack, until we find other solution)
->Video:
HD: [email protected]@20mbps
High: [email protected]@10mbps
----------------------------------------------
All audio is 128 kbps and all stills are:
Super fine: 100
Fine: 90
Normal: 80
--------------------------------CHANGELOG----------------------------------------
1.0 Initial release.
---- Small bugfix of CM7s camera app + tegra 2 specific stuff.
1.1-pre-alpha
---- Enables autofocus prior to video capture. Cannot be turned off(I don't do UIs,lol). Need to restart app for each video.
Autofocus 1.1
---- No need to restart app.
Known issues:
Does no longer auto adjust for exposure while recording. In between recordings it will auto adjust again. (I have no idea why).
Cannot disable autofocus (have no idea how to do UI).
Rather buggy, lots of freezes. For best results, don't push it. Ie. don't start and stop recordings rapidly, stuff like that.
Don't switch quickly to video when opening app... I think that might be a cm7 issue.
---------------------------------------TODO----------------------------------------
Touch to focus.
continuous auto-focus.
FAQ
Q: Does this work for non-CM7 ROMS?
A: Probably not. Certainly not froyo. But feel free to try and let me know. On stock rom-based builds, please look at somemadcaaant's awesome work at http://forum.xda-developers.com/showthread.php?t=1090785.
Q: T-Mobile LG G2x support?
A: Yes.
Q: What are the disadvantages?
A: Larger filesize. Takes longer to save (give it time to save before doing anything else with the phone). Potential issues with playback on phone.
Q: Does this work with 64 mb ram hack?
A: No. You can still use a high bitrate 720p mod for that kernel, though.
Q: It stutters after a few secs of recording or freezes once in a while, why is this?
A: Your phone/sdcard is having issues trying to keep up. Try a lower bitrate mod. If there is no lower, ask for one. I'm experimenting a little myself, trying to find a stable bitrate.
Q: If I open the Camera app and very quickly change to video I get a black screen?
A: Don't do that. I get the same bug on std. cm7 Camera app.
Q: Isn't it overkill with an FAQ for a camera mod?
A: Yes. But people kept asking the same questions last time I made a thread.
THX so much I will test it and report.
i would also add "touch to re-focus during video capture"(like in htc's) to the to-do list
Tegra 2 is some impressive hardware.... bitrate goes up crazy high. I'll add some different versions, but do people have any thoughts on what kind of bit rates they'd like to see?
Damn, I think maybe my sdcard cant keep up with the ultra high bit rates I'm testing. Starts stuttering after 10 sec. Maybe someone out there with a class 10 card?
When switching on video mode, i get a black screen and FC afterwards.
ranrick said:
When switching on video mode, i get a black screen and FC afterwards.
Click to expand...
Click to collapse
I purposely made my tweaks so code is first running when you actually start recording... If it's a new problem it's because of the settings file.
Tried restarting the app?
Work great for me on Kang today buid !
gregman26 said:
Work great for me on Kang today buid !
Click to expand...
Click to collapse
Great news.
LeJay said:
I purposely made my tweaks so code is first running when you actually start recording... If it's a new problem it's because of the settings file.
Tried restarting the app?
Click to expand...
Click to collapse
I reinstalled. Thereafter i was able to start it. But Recording doesn't work so far.It starts at 720P but when ending the recodring, I get a FC. 1080p keeps black screen and no FC and no recording. Maybe because of the 64MB RAM hack in the vorkKernal.
Thanks LeJay
But i have a bug.... The video is lagging(I think my Sd Card is Class 2), so i think it is because of the high bitrate. And sometimes after shooting a video the camera just freezes and i have to pull the battery..
LG O2x, Latest Kang, stock kernel.
ranrick said:
I reinstalled. Thereafter i was able to start it. But Recording doesn't work so far.It starts at 720P but when ending the recodring, I get a FC. 1080p keeps black screen and no FC and no recording. Maybe because of the 64MB RAM hack in the vorkKernal.
Click to expand...
Click to collapse
Okay, so it officially doesn't work with the 64 mb ram hack. Not surprising. You can enable high bitrate 720p with some of my other mods.
TattooHtc said:
Thanks LeJay
But i have a bug.... The video is lagging(I think my Sd Card is Class 2), so i think it is because of the high bitrate. And sometimes after shooting a video the camera just freezes and i have to pull the battery..
LG O2x, Latest Kang, stock kernel.
Click to expand...
Click to collapse
Isnt that the case with cm7 nightlies and 1080p recording?
Can someone up a vid?
TattooHtc said:
Thanks LeJay
But i have a bug.... The video is lagging(I think my Sd Card is Class 2), so i think it is because of the high bitrate. And sometimes after shooting a video the camera just freezes and i have to pull the battery..
LG O2x, Latest Kang, stock kernel.
Click to expand...
Click to collapse
Hmm... I just recorded for 1 min straight with no issue. I do get similar issues on som2e of the higher bitrates I've been toying with(40mbps can make most sd cards cry). Does it start lagging as soon as you start recording?
I'm going to make higher and lower bitrate versions.
Works beautifully on the G2x as well. Thanks
@LeJay: you should contact arcee to include your mod in CM tree
TattooHtc said:
Thanks LeJay
But i have a bug.... The video is lagging(I think my Sd Card is Class 2), so i think it is because of the high bitrate. And sometimes after shooting a video the camera just freezes and i have to pull the battery..
LG O2x, Latest Kang, stock kernel.
Click to expand...
Click to collapse
Could you try the low bitrate mod?
Works grat! 40 sec of video went from 18mb to 99mb. Now that we need a fast memory isn't better to use the internal memory?
buch85 said:
@LeJay: you should contact arcee to include your mod in CM tree
Click to expand...
Click to collapse
Agreed.
LeJay, I also think that you should contact Ricardo (arcee) and see if he can merge you changes. He just changed from 1080 to 1088 the other day in the .xml file so we can record 1080p nativly. Kinda wierd that you have to set it to 1088?
The best thing would of course be if he could include all the different modes/profiles for us to freely choose:
"FPS: 15, 25, 30"
"Resolution: 1080p, 720p, ..."
"Bitrate: X, Y, Z"
"Sound: 44 Khz, ..."
etc... because I know my class 2 card can't keep up at the best options. Going to buy me a new one soon though.
Send him a message and see if he's interested. His todo list probably is long though....
Alright, as promised, the camera patch for all ROMs using the grouper blobs.
First of all, a very big thanks to @Adam77Root, cause without him, none of this would have been possible.
This patch allows the camera to use the old nvomx, which fixes the encoder issues. However, this breaks the hardware decoder of the stock gallery. And using software decoder, lags are inevitable. But, you can still play HD videos using MX player.
To revert this, either restore a system backup, re-flash your ROM or flash the "Cam_revert_patch.zip" from the Attachment.
@ROM devs, please don't include this patch into your ROMs, but rather link to this thread. Not being able to use the read hw decoder can cause confusion and false bug reports, which is why I want people to read this first, before using the patch
Good idea!
tested the patch, works wonderfully. thank you!
As above working flawlessly as it should good work you are one step to make everything fully working
Sent from my LG-P880 using Tapatalk
Can anyone test Skype videocall? Because for me it doesn't work, it gives me the same error as without the patch (green screen instead of the video). I can record videos though.
Also it works with the new omni buils (the ones reverted to old blobs) and all other official roms that use old blobs.
qr decoding/skype still doesn't work - this is just a fix for video recording
I would really like a revert patch, because I would like to install the patch when I want to take a video and simply uninstall it when I want to use the gallery.
I also add that this patch breaks Youtube app
Nagass said:
I also add that this patch breaks Youtube app
Click to expand...
Click to collapse
Confirmed, output when playing a video is only black screen
breaks also flashplayer...
Nagass said:
I also add that this patch breaks Youtube app
Click to expand...
Click to collapse
JustChris20 said:
breaks also flashplayer...
Click to expand...
Click to collapse
Of course, it breaks almost all video decoding stuff, especially YT. This is why don't want devs to include it into ROMs.
MX player is more-less the only exception
in addition the recorded Videos are really "not good". The framerate is not stable. One video I recorded has 13 fps, the next 22 fps. Stable 25fps seems not possible.
So I would really appreciate a revert patch, dont want to flash all the rom again
Climuff said:
in addition the recorded Videos are really "not good". The framerate is not stable. One video I recorded has 13 fps, the next 22 fps. Stable 25fps seems not possible.
So I would really appreciate a revert patch, dont want to flash all the rom again
Click to expand...
Click to collapse
you were watching this videos on gallery app ?? or mx player with s/w decoding chosen? or on your pc?
i didnt faced such problem.. only when u watch video you recorded on gallery it OFC will lag...
I watched the videos on my pc, I read the framerate out with standard windows and also with adobe premiere pro cs5.
Climuff said:
I watched the videos on my pc, I read the framerate out with standard windows and also with adobe premiere pro cs5.
Click to expand...
Click to collapse
What's your recorded resolution?
About the revert patch, I'm on it
I recorded in 1080p H.264 with LED on and USB connected. Video was saved on internal storage.
Climuff said:
I recorded in 1080p H.264 with LED on and USB connected. Video was saved on internal storage.
Click to expand...
Click to collapse
What's the bitrate of the recorded vid?
BTW, revert patch added to the OP
laufersteppenwolf said:
What's the bitrate of the recorded vid?
Click to expand...
Click to collapse
this one which ended up with 13 fps is 11.5 mbits and this one which has 22 fps is 10.3 mbits.
Climuff said:
this one which ended up with 13 fps is 11.5 mbits and this one which has 22 fps is 10.3 mbits.
Click to expand...
Click to collapse
Will do some troubleshooting tomorrow, gonna let you know if I find anything
Alright, as already mentioned HERE, we have a new way to switch between video playing and recording, a more "on the go" version
For details and how to use it, please take a look into the linked post
Now, some more explanation, the new patch "nameless_patchV2" is not only for nameless, but all ROMs built using p880-dev's android-4.4 branch, such as NamelessROM, Omni, Thinkingbridge, ...
Just flash the patch and you can switch blobs as explained.
The patch for CM11 (the cm-11.0 branch) is in the making
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.
FooxMagisk Alpha[ v0.2.2/SIZE]
×WHO:
FxM is aimed at Android users in search of an easy way to capture system or internal sounds (systemless-ly), and on Android versions past Lollipop. By installing my module users will no longer need to worry about background noise from their environment.
×WHAT:
FooView, an app by fvalpha, comes from the same dev behind ES File Explorer nearly a decade ago. Development is ongoing, but in essence, FV supplies the user with a range of controls outside of screen recording. Be sure to visit their thread.
×WHY:
Some time ago someone inquired about the possibility, which led us to trying other means before quitting. Recently I found FV and gave it a spin. Plus, others are frustrated by the absence of native recording on most devices. Whilst I've experimented with other techniques on Oreo & Pie, none come close.
×HOW:
The real reason you're here! First of all, in order use this module I strongly recommend Magisk 18+. It was used on 18, so can't guarantee the results on older versions. If there's demand, a test for 17 can be made.
×Prerequisites:
- Magisk 18+
- Grab fooView Play Store
- Download/Install FxM module from below
×Links
- All Releases
×Steps:
- Follow above
- Reboot after installing
- Check app info (foo can now be disabled, instead of uninstalled)
- Open foo -> Settings -> Advanced settings -> Dev Mode -> Enable "root for screenshots" -> Grant -> Enable "Record internal"
- Enable little MIC icon BEFORE recording
- Adjust media volume to < 40% (Volume bug on some devices)
×Credits:
- @fvalpha - Developer of fooView
- @topjohnwu - Magisk
- @ahrion - Unity Installer
- @Zackptg5 - Unity Installer
×Bugs
- Using high volume creates a tick sound on certain devices
- If Module is installed FIRST the app will crash constantly
×Revision History
v0.1a - Jan 18, 2019 - Initial Release (Unity v3.1 + 0.9.9.9)
v0.2.2a - Jan 21, 2019 - (Unity v3.2 + Perms fixed)
v0.2.3a - Jan 25, 2019 - (Removed unnecessary perms)
×Compatibility:
- LOS 15.1 (8.1)
- AICP 13 (8.1)
- AICP 14 (9.0)
×Devices:
- Le Pro 3
- Moto Z2
- Whyred
- Pocophone F1
Further testing is necessary to extend this list
×FAQ:
Q: Can I hear speaker audio whilst recording internal sounds?
A: No, not at this time. And likely never. It's a limitation in the API.
Q: Sound doesn't play when recording!
A: This is normal. Maybe simultaneous internal/external recording will be doable in Android Q.
Q: Fooview crashes!
A: This happens when Foo module is installed before the base app.
Q: Why is there no sound in my recording?
A: Turn on the microphone icon that's shown in fooview.
Q: Is root needed?
A: Yes!
Q: Watermark in videos?
A: This can be disabled in settings.
Still crashing unable to open setting I am using 9.0
Unable to here sound's..
hitesh748- said:
Still crashing unable to open setting I am using 9.0
Click to expand...
Click to collapse
Did you follow all the steps? In foo there's a permission section, first 3 need to be enabled when installing the app. After rebooting only floating window is needed really.
hitesh748- said:
Unable to here sound's..
Click to expand...
Click to collapse
Sound from the speaker stops whenever foo records. Make sure mic is enabled in the screen recorder, there's going to be a little mic icon. Like here:
http://imgur.com/a/f3ZQINs
Ace42 said:
Did you follow all the steps? In foo there's a permission section, first 3 need to be enabled when installing the app. After rebooting only floating window is needed really.
Sound from the speaker stops whenever foo records. Make sure mic is enabled in the screen recorder, there's going to be a little mic icon. Like here:
http://imgur.com/a/f3ZQINs
Click to expand...
Click to collapse
if we are not hearing voice.. Than why to use this?Is that any way possible to record internal voice and also able to hear?Because if this is going to possible than ?.. It's going on trending.. Because this is what people really want
hitesh748- said:
if we are not hearing voice.. Than why to use this?Is that any way possible to record internal voice and also able to hear?Because if this is going to possible than ?.. It's going on trending.. Because this is what people really want
Click to expand...
Click to collapse
No, because Android doesn't support system recording natively. You'd have to record your voice from another device and merge the waveforms. It's not possible to record MIC & system simultaneously, unless it's done on a Samsung or Xiaomi device.
This is meant for people that DON'T want sounds from their mic. Internal recording isn't possible without root after lollipop, and game audio from a microphone sounds awful.
Thanks! I am able to record internal audio, but unable to hear while recording:'(
My rom PE whyred
Is there any fix yet?
Thanks Dev
ItsOm said:
Thanks! I am able to record internal audio, but unable to hear while recording:'(
My rom PE whyred
Is there any fix yet?
Thanks Dev
Click to expand...
Click to collapse
It's a limitation of the the app at this time (fooview), not the module. I don't know if the Dev will add that functionality in the future. There's another Android app that can record internal sound, I'm trying to create a module for it too.
Ace42 said:
It's a limitation of the the app at this time (fooview), not the module. I don't know if the Dev will add that functionality in the future. There's another Android app that can record internal sound, I'm trying to create a module for it too.
Click to expand...
Click to collapse
Oh! good luck
You are our only hope literally!
One more question, Can Xiaomi devices record internal audio?
I have Whyred (RN5pro) with PE rom installed.
Thanks!
WORK
Thanks dude, work in POCOPHONE F1 android 9 pie.
Bgsbeb said:
Thanks dude, work in POCOPHONE F1 android 9 pie.
Click to expand...
Click to collapse
No problem! Happy to help.
ItsOm said:
Oh! good luck
You are our only hope literally!
One more question, Can Xiaomi devices record internal audio?
I have Whyred (RN5pro) with PE rom installed.
Thanks!
Click to expand...
Click to collapse
With school it'll take time for me to get around to it.
Only some Xiaomi phones feature it natively. I've heard of it being available on older devices like the Note 4.
Sorry to ask this basic question. Where is best use of this module. Can this be used alongside screen video recorder so that WhatsApp video calls can be recorded.
smohanv said:
Sorry to ask this basic question. Where is best use of this module. Can this be used alongside screen video recorder so that WhatsApp video calls can be recorded.
Click to expand...
Click to collapse
1. It's meant to record system audio. My buddy needs that for games. I guess there are other uses like recording calls, but I never considered it.
2. I've never tried this on WhatsApp, nor any app like it. I don't know if WA even allows recorders.
It only needs to be installed, nothing else it required.
excellent thread and mind blowing work, this is what i have been searching for since a long time, it works great but only problem is i can't hear anything while recording internal sound, but it records internal sound. well it works though !
vasu97 said:
excellent thread and mind blowing work, this is what i have been searching for since a long time, it works great but only problem is i can't hear anything while recording internal sound, but it records internal sound. well it works though !
Click to expand...
Click to collapse
There seems to be no way to achieve this on any Android version after LP (internal + MIC). Samsung, Xiaomi, and LG feature native recording in their skins so it's a different story. For example, my sister's Stylo can do both on Nougat.
For unknown reasons Google doesn't want apps to contain this functionality (also true of call recording apps). It's odd since Apple's position is the complete opposite...
Ace42 said:
There seems to be no way to achieve this on any Android version after LP (internal + MIC). Samsung, Xiaomi, and LG feature native recording in their skins so it's a different story. For example, my sister's Stylo can do both on Nougat.
For unknown reasons Google doesn't want apps to contain this functionality (also true of call recording apps). It's odd since Apple's position is the complete opposite...
Click to expand...
Click to collapse
I hate Google for that and even regret buying a Pixel
Man u said I should enable the mic thing for screen recording but I searched every where no such a thing
Device pocophone f1
No sound at all for screen recording is there any way to enable the internal mic ?
Thanks in advance
Antidote03 said:
Man u said I should enable the mic thing for screen recording but I searched every where no such a thing
Device pocophone f1
No sound at all for screen recording is there any way to enable the internal mic ?
Thanks in advance
Click to expand...
Click to collapse
https://m.imgur.com/gallery/f3ZQINs
The microphone is there. It's needed for internal audio, the speaker won't output any sound.
I prefer this one for its ability to alter FPS (25 - 60).
Edit: Link removed temporarily
Ace42 said:
https://m.imgur.com/gallery/f3ZQINs
The microphone is there. It's needed for internal audio, the speaker won't output any sound.
https://drive.google.com/file/d/1yiqCE8Szik59CGccrxLfjomwRDOTIhAN/view?usp=drivesdk
I prefer this one for its ability to alter FPS (25 - 60).
Click to expand...
Click to collapse
No picture please upload it again
Note:
- I am not responsible for anything that goes wrong with your device, bootloops, bricks, paperweights etc... Nothing should go wrong but hey i need to include this. If you need any help i will try my best to help you to fix it if you comment.
(Downloads at the bottom of this post in the attached files)
Should work with every Razer Phone 2
Installation:
Open Magisk Manager and head to the Modules page
Click on the plus(+) and select the file you want to install
To install more than one file, after one module has installed go back and redo the same process with the other file you downloaded
The Viewfinder Fix: Download Link If XDA Is Broken
It will replace your tuned camera file with the file that razer used in android OREO as that one has no issues with the viewfinderIssues: None that i know of so far, if you notice anything you can mention it in the comments but it is likely i cannot fix it
The EIS Fix: Download Link If XDA Is Broken
EIS (Electronic Image Stabilisation) helps your videos look more stable, by default this is only available at 30fps and only in some apps. However, with this fix EIS will be enabled in any app that asks for it and it will work at 1080p 60fps.Make sure to not use the stock camera app with this but instead a gcam with 60fps support for this phone (like BSGs)Issues: It will break 4k 60fps recording, it just won't work. Also it will break 1080p 60fps recording on the front camera.
And finally, yes of course these modules work together
Also if you need anything else or want to join the Razer Phone community join our group on Telegram!
thanks!
Why is this needed? Can you provide any context? Are these features broken on stock, or just in Gcam?
MishaalRahman said:
Why is this needed? Can you provide any context? Are these features broken on stock, or just in Gcam?
Click to expand...
Click to collapse
on stock the camera viewfinder is blurry and colours smudge, making 3rd party apps like Instagram very bad with recording videos and not being able to see well on on what you're taking a picture of.
This issue came around with the pie update for razer phone 2 so I managed to fix the viewfinder issue by using the razer libs from android OREO.
This is for every app, not just gcam.
The EIS fix allows for video stabilization at 1080p 60fps.
Usyless said:
on stock the camera viewfinder is blurry and colours smudge, making 3rd party apps like Instagram very bad with recording videos and not being able to see well on on what you're taking a picture of.
This issue came around with the pie update for razer phone 2 so I managed to fix the viewfinder issue by using the razer libs from android OREO.
This is for every app, not just gcam.
The EIS fix allows for video stabilization at 1080p 60fps.
Click to expand...
Click to collapse
Thanks for the explanation. Do you have any videos/photos to show the fix in action? Or can anyone else confirm this works? Cheers!
MishaalRahman said:
Thanks for the explanation. Do you have any videos/photos to show the fix in action? Or can anyone else confirm this works? Cheers!
Click to expand...
Click to collapse
I am outside right now but I will upload a comparison video later as I am recording some right now
MishaalRahman said:
Thanks for the explanation. Do you have any videos/photos to show the fix in action? Or can anyone else confirm this works? Cheers!
Click to expand...
Click to collapse
I have made a couple comparison videos and here they are: (read the description of each as it describes what to look for if it is not immediately visible)
1. Stock Camera Libs through the gcam viewfinder
2. My module through the gcam viewfinder
3. Stock Camera libs recording a video of snapchat (it just records the viewfinder)
4. My module recording the same video in snapchat
Even with the low youtube quality as of now (still processing probably) the changes are noticeable
MishaalRahman said:
Thanks for the explanation. Do you have any videos/photos to show the fix in action? Or can anyone else confirm this works? Cheers!
Click to expand...
Click to collapse
Using both of these and my gcam is much better. Viewfinder no longer has a ghosting effect, colors are better, and stabilization works.
Usyless said:
Note:
- I am not responsible for anything that goes wrong with your device, bootloops, bricks, paperweights etc... Nothing should go wrong but hey i need to include this. If you need any help i will try my best to help you to fix it if you comment.
(Downloads at the bottom of this post in the attached files)
Should work with every Razer Phone 2
Installation:
Open Magisk Manager and head to the Modules page
Click on the plus(+) and select the file you want to install
To install more than one file, after one module has installed go back and redo the same process with the other file you downloaded
The Viewfinder Fix: Download Link If XDA Is Broken
It will replace your tuned camera file with the file that razer used in android OREO as that one has no issues with the viewfinderIssues: None that i know of so far, if you notice anything you can mention it in the comments but it is likely i cannot fix it
The EIS Fix: Download Link If XDA Is Broken
EIS (Electronic Image Stabilisation) helps your videos look more stable, by default this is only available at 30fps and only in some apps. However, with this fix EIS will be enabled in any app that asks for it and it will work at 1080p 60fps.Make sure to not use the stock camera app with this but instead a gcam with 60fps support for this phone (like BSGs)Issues: It will break 4k 60fps recording, it just won't work. Also it will break 1080p 60fps recording on the front camera.
And finally, yes of course these modules work together
Also if you need anything else or want to join the Razer Phone community join our group on Telegram!
Click to expand...
Click to collapse
Which camera version are you using? The 7.4 version doesnt with when i want to use video and the 7.3 versions all crash instantly on startup same as 7.2.
Danishblunt said:
Which camera version are you using? The 7.4 version doesnt with when i want to use video and the 7.3 versions all crash instantly on startup same as 7.2.
Click to expand...
Click to collapse
Impossible, are you using BSGs cameras? also disable the EIS fix to check if it is that one.
Is it the EIS FIX of VF FIX doing it? and which gcams did you try (by which modder)
Usyless said:
Note:
- I am not responsible for anything that goes wrong with your device, bootloops, bricks, paperweights etc... Nothing should go wrong but hey i need to include this. If you need any help i will try my best to help you to fix it if you comment.
(Downloads at the bottom of this post in the attached files)
Should work with every Razer Phone 2
Installation:
Open Magisk Manager and head to the Modules page
Click on the plus(+) and select the file you want to install
To install more than one file, after one module has installed go back and redo the same process with the other file you downloaded
The Viewfinder Fix: Download Link If XDA Is Broken
It will replace your tuned camera file with the file that razer used in android OREO as that one has no issues with the viewfinderIssues: None that i know of so far, if you notice anything you can mention it in the comments but it is likely i cannot fix it
The EIS Fix: Download Link If XDA Is Broken
EIS (Electronic Image Stabilisation) helps your videos look more stable, by default this is only available at 30fps and only in some apps. However, with this fix EIS will be enabled in any app that asks for it and it will work at 1080p 60fps.Make sure to not use the stock camera app with this but instead a gcam with 60fps support for this phone (like BSGs)Issues: It will break 4k 60fps recording, it just won't work. Also it will break 1080p 60fps recording on the front camera.
And finally, yes of course these modules work together
Also if you need anything else or want to join the Razer Phone community join our group on Telegram!
Click to expand...
Click to collapse
Usyless said:
Impossible, are you using BSGs cameras? also disable the EIS fix to check if it is that one.
Is it the EIS FIX of VF FIX doing it? and which gcams did you try (by which modder)
Click to expand...
Click to collapse
Using BSG 7.4 latest release, only got the VF Fix as I would like to shoot 4k.
I'm using:
https://f.celsoazevedo.com/file/cfiles/gcm1/MGC_7.4.104_V0a.apk
Danishblunt said:
Using BSG 7.4 latest release, only got the VF Fix as I would like to shoot 4k.
I'm using:
https://f.celsoazevedo.com/file/cfiles/gcm1/MGC_7.4.104_V0a.apk
Click to expand...
Click to collapse
You on android 9 or 10? also try disable it and see if it works.
also try re downloading it as maybe it got corrupted
Usyless said:
You on android 9 or 10? also try disable it and see if it works.
also try re downloading it as maybe it got corrupted
Click to expand...
Click to collapse
Am on stock rom Pie and did redownload and try without ur mods.
Danishblunt said:
Am on stock rom Pie and did redownload and try without ur mods.
Click to expand...
Click to collapse
okay so,
1. does it work without the mods?
2. I've had testers and it all works on stock rom and android 10
3. does the redownloaded one work?
4. if you use a social media app like Instagram does it work?
Usyless said:
okay so,
1. does it work without the mods?
2. I've had testers and it all works on stock rom and android 10
3. does the redownloaded one work?
4. if you use a social media app like Instagram does it work?
Click to expand...
Click to collapse
1.) Camera works on stock camera app, instagram, facebook, gcam 6.1.
2.) Doesnt work with gcam 7.4 with or without mods
3.) redownloaded and reinstalled 3 times, clean install.
Danishblunt said:
1.) Camera works on stock camera app, instagram, facebook, gcam 6.1.
2.) Doesnt work with gcam 7.4 with or without mods
3.) redownloaded and reinstalled 3 times, clean install.
Click to expand...
Click to collapse
it seems more of like an issue with your phone or something as I've not heard of anybody having problems with the viewfinder fix.
about the 7.4 gcam, try BSGs latest version from celsoazevado, it should be labelled test
also you said the camera works in social medias, is that with or without the viewfinder fix
Usyless said:
it seems more of like an issue with your phone or something as I've not heard of anybody having problems with the viewfinder fix.
about the 7.4 gcam, try BSGs latest version from celsoazevado, it should be labelled test
also you said the camera works in social medias, is that with or without the viewfinder fix
Click to expand...
Click to collapse
I don't see the latest version being labelled as test. Maybe you're talking about one of those that are labelled as test?
Danishblunt said:
I don't see the latest version being labelled as test. Maybe you're talking about one of those that are labelled as test?
Click to expand...
Click to collapse
seems it got deleted then, join the telegram channel with the version available there, https://t.me/razer_phone
you can also get more help there