Remember to Disable HW Overlay and Force GPU rendering. Disable HW Overlay has to be set every time you reboot unless you modify build.prop. After setting Force GPU rendering the first time you probably (guess) have to reboot for it to take effect.
I'm having a problem with any new 4.2.1 and 4.2.2 roms on my Verizon Galaxy S3. Every video I attempt to record just results in a black video. I have tried the hardware overlay and for gpu rendering multiple times with no luck. I have also tried emailing the developer but I have gotten no response. I really rely on this app for many of my Youtube videos so this is important to me to get solved. My guess is it is something specific with the Galaxy S3 on the newest android builds like 4.2.1 and 4.2.2. If anybody knows anything that I can do to fix this bug it would be greatly appreciated. Also if anyone knows a different email I can contact the developer at that would be great because I would like to do anything I can to help fix this problem!! Thanks.
Do you see the touch pointer in the recording if you add one from the settings menu?
How do I request a refund? Since the purchased app did not work on my tablet. permanent 'waiting for service', also in the demo version. Please advice. Regards
Do you see the touch pointer in the recording if you add one from the settings menu?
I've been experiencing the same issues with colors, some of them appear inverted. I've tried many things and none of them work. Strangely, some other screencast apps seem to work fine. As a developer I'd hate to ask for a refund. Please, @mediasol, let us solve this.
My device is a Samsung i9300 running latest stable ROM Vanilla RootBox with Siyah kernel. I've tried this app with Omega ROM and the same kernel before and it worked fine. It was said before that this app is "deep-in-the-kernel-code intrusive". So if I changed the kernel would it help?
I've uploaded the screenshots for my settings on the Developer Options menu, the About Phone menu, my kernel settings via the STweaks app, the Screencast Recorder settings and benchmarck, and an example of how the movie actually looks after recorded. You can view it here: https://www.box.com/s/cf1mh80hhj12n3vrf1fx
Please, let us fix this ASAP.
My best guess is that the latest build is using incompatible drivers. Screencast needs framebuffer video drivers to work.So do you have any idea what the problem could be? Let me know if there is anything I can do to help you diagnose this bug. Thanks!
Okay, so do you think that it is a bug that can be fixed via ROM devs, or is it something that you will have to address in a future update? I think it may be related to Galaxy S 3's in specific because I have seen other phones able to record on 4.2 and I also was able to record on an early version of a custom 4.2 rom, but now it does not in later versions of the ROM. So if you can give me more details on how this framebuffer video drivers work, like if it can easily be added to the System, that would be helpful. Let me know what you think.My best guess is that the latest build is using incompatible drivers. Screencast needs framebuffer video drivers to work.
Okay, so do you think that it is a bug that can be fixed via ROM devs, or is it something that you will have to address in a future update? I think it may be related to Galaxy S 3's in specific because I have seen other phones able to record on 4.2 and I also was able to record on an early version of a custom 4.2 rom, but now it does not in later versions of the ROM. So if you can give me more details on how this framebuffer video drivers work, like if it can easily be added to the System, that would be helpful. Let me know what you think.
Thanks!
It has to be the display drivers in the S3 kernel, I will need to run kernel traces on an S3 to narrow it down.