Recherche avancée

Sur d’autres sites (5780)

• 4 Ways to Embed User Privacy & Data Security in Your Business

  15 juillet 2022, par Erin — Privacy

  Customer analytics undeniably plays a vital role for businesses. Product improvements, interface personalisation, content improvements, and creative advertising thrive on data. 

  Yet, there’s a fine line between being a customer-centred company and a privacy-violating one. 

  Due to ubiquitous online tracking, 62% of Americans now believe that it’s impossible to go about their daily lives without companies collecting data about them. Still, despite the importance of privacy in business for consumers, companies are reluctant to act. Privacy initiatives often stay on the back burner due to perceived complexity. That’s true to some extent.

  Privacy in business does assume complex technical changes to your data management. But to be a privacy-centred organisation, you also need to re-think your processes, practices, and culture. 

  Here are four ways to start your journey to better user privacy and data security. 

  1. Revise Your Data Collection Process to Gain Consumer Trust 

  The public is wary of sharing data with businesses because they are suspicious of its subsequent usage. 

  However, not all data collection is bad or wrong. In many cases, you need specific data for service delivery, compliance, or good-natured personalisation. 

  That’s exactly what consumers expect. Almost half of US consumers say they’d trust a company that limits the amount of personal information requested and only asks for data relevant to its products/services. 

  By limiting data collection and offering transparent data usage terms, you can : 

  • Reassure reluctant users to try your product or service — hence, boost conversions and sales. 
  • Retain existing audiences by gaining their trust, which leads to loyalty and higher customer lifetime value (CLV). 

  To gain consumers’ trust, implement proper consent and opt-out mechanisms. Then create educational materials about how you are collecting and using their data.

  2. Perform Data Mapping to Determine Where Sensitive Data Rests 

  Businesses are already pressed with an expanded cyber-security radar, courtesy of remote work, digital payment processing, IoT device adoption, etc. Yet, 41% of the executives don’t think their security initiatives have kept up with the digital transformations.

  Loopholes in security eventually result in a data breach. The average cost of a data breach looms at $4.24 million globally. The sum includes regulatory fines and containment costs, plus indirect losses in the form of reduced brand equity and market share. 

  Lax data protection in business also undermines consumer trust : 87% of consumers wouldn’t transact with a company if they had qualms with its security practices. 

  To improve your security posture, analyse where you are storing sensitive consumer data, who has access to it (internally and externally), and how you are protecting it. Then work with cybersecurity specialists on implementing stronger consumer security mechanisms (e.g. auto-log offs, secure password policy, etc) and extra internal security policies (if needed). 

  At the same time, start practising data minimisation. Ensure that all collected data is : 

  • Adequate – sufficient to meet your stated objectives 
  • Relevant – is rationally linked to the objectives 
  • Limited – no unnecessary data is collected or stored
  • Timely – data is periodically reviewed and removed when unnecessary 

  

  These principles prevent data hoarding. Also, they help improve your security posture and regulatory compliance by reducing the volume of information you need to safeguard.

  3. Do an Inventory of Your Business Tools

  Data leaks and consumer privacy breaches often occur through third parties. Because Google Analytics was deemed in breach of European GDPR in France, Austria and Italy, businesses using it are vulnerable to lawsuits (which are already happening). 

  Investigate your corporate toolkit to determine “weak links” – tools with controversial privacy policies, murky data collection practices, and poor security. 

  Treat it as a journey and pick your battles. By relying on Big Tech products for years, you might have overlooked better alternatives. 

  For example :

  • Matomo is a privacy-centred Google Analytics alternative. Our web analytics is compliant with GDPR, CCPA, and other global privacy laws. Unlike Google Analytics, we don’t exploit any data you collect and provide full transparency into how and where it’s stored. Or if you want a simple analytics solution, Fathom is another great privacy-friendly option.

  

  • For online data storage, you can choose Proton Drive or Nextcloud (open-source). Or host your corporate data with a local cloud hosting provider to avoid cross-border data transfers.

  

  Aim to progressively replace Google products with more privacy-centred alternatives. 

  4. Cultivate a Privacy-Centred Corporate Culture 

  To make privacy a competitive advantage, you need every team member (at every level) to respect its importance. 

  This is a continuous process of inspiring and educating your people. Find “privacy ambassadors” who are willing to lead the conversations, educate others, and provide resources for leading the change. 

  On an operational level, incorporate privacy principles around data minimisation, bounded collection, and usage into your Code of Conduct, standard operating procedures (SOPs), and other policies. 

  Creating a privacy-centric culture takes effort, but it pays off well. Cisco estimates that for each dollar spent on privacy, an average organisation gets $2.70 in associated benefits. Almost half (47%) of organisations gain 2X returns on their privacy initiatives.

  Moving Forward with a Data Privacy Programme 

  Privacy has become a strong differentiator for brands. Consumers crave transparency and ethical data usage. Regulators mandate limited data collection and proper security mechanisms.

  But sweeping changes are hard to implement. So start small and go one step at a time. Understand which first-party data your company collects and how it is stored.

  Then look into the tools and technologies you are using for data collection. Do these provide sufficient privacy controls ? How are they using data collected on your behalf ? Finally, move to wider transformations, pertaining to data management, cybersecurity, and cultural practices. 

  Be consistent with your effort — and eventually, all the pieces will fall into place. 

• Matomo Celebrates 15 Years of Building an Open-Source & Transparent Web Analytics Solution

  30 juin 2022, par Matthieu Aubry — About, Community
  &lt;script type=&quot;text/javascript&quot;&gt;<br />
       if ('function' === typeof window.playMatomoVideo){<br />
       window.playMatomoVideo(&quot;brand&quot;, &quot;#brand&quot;)<br />
       } else {<br />
       document.addEventListener(&quot;DOMContentLoaded&quot;, function() { window.playMatomoVideo(&quot;brand&quot;, &quot;#brand&quot;); });<br />
       }<br />
  &lt;/script&gt;

  Fifteen years ago, I realised that people (myself included) were increasingly integrating the internet into their everyday lives, and it was clear that it would only expand in the future. It was an exciting new world, but the amount of personal data shared online, level of tracking and lack of security was a growing concern. Google Analytics was just launched then and was already gaining huge traction – so data from millions of websites started flowing into Google’s database, creating what was then the biggest centralised database about people worldwide and their actions online.

  So as a young engineering student, I decided we needed to build an open source and transparent solution that could help make the internet more secure and private while still providing organisations with powerful insights. I aimed to create a win-win solution for businesses and their digital consumers.

  And in 2007, I started developing Matomo with the help from Scott Switzer and Jennifer Langdon (who offered me an internship and support).   

  All thanks to the Matomo Community

  We have reached significant milestones and made major changes over the last 15 years, but we wouldn’t be where we are today without the Matomo Community.

  So I would like to celebrate and thank the hundreds of volunteer developers who have donated their time to develop Matomo, the thousands of contributors who provided feedback to improve Matomo, the countless supportive forum members, our passionate team of 40 at Matomo, the numerous translators who have translated Matomo and the 1.5 million websites that choose Matomo as their analytics platform.

  

  Matomo has been a community effort built on the shoulders of many, and we will continue to work for you. 

  So let’s look at some milestones we have achieved over the last 15 years.

  Looking back on milestones in our timeline

  2007

  • Birth of Matomo
  • First alpha version released

  2008

  • Release first public 0.1.0 version

  2009

  • 50,000 websites use Matomo

  2010

  • Matomo first stable 1.0.0 released
  • Mobile app launched

  2011

  • Released Ecommerce Analytics, Custom Variables, First Party Cookies

  • Released Privacy control features (first of many privacy features to come !)

  2012

  • Released Log Analytics feature
  • 1 Million Downloads !
  • 300,000 websites worldwide use Matomo

  2013

  • Matomo is now available in 50 languages !
  • Matomo brand redesign

  2016

  • Released Roll-Up Reporting Premium Feature, Users Flow Premium Feature, White Label Premium Feature, A/B Testing Premium Feature, Media Analytics Premium Feature, Funnels Premium Feature and Activity Log Premium Feature 
  • On-Premise Premium Plugins now available on the Marketplace

  2017

  • Launched Matomo Cloud service 
  • Released Multi Channel Conversion Attribution Premium Feature, Custom Reports Premium Feature, Login Saml Premium Feature, WooCommerceAnalytics Premium Feature and Heatmap & Session Recording Premium Feature 

  2018

  • Piwik renamed to Matomo
  • New Matomo logo and Matomo.org website re-launch
  • Launch of Matomo Tag Manager
  • 10,000 stars on Github
  • GDPR comes into effect, and Matomo released new product features and published several new guides
  • 17 Matomo features videos published online
  • Reached thousands of paying customers, making the project sustainable and financially independent

  2019

  • 700,000 websites worldwide use Matomo
  • Google Analytics importer released

  2020

  • Matomo For WordPress goes live on the WP Marketplace !
  • Released Paid Advertising Performance Premium feature
  • 100 million On-Premise Plugins downloads on the marketplace (since the beginning)

  2021

  • 1,000,000 websites worldwide use Matomo
  • including 30,000 active Matomo for WordPress installations
  • Released SEO Web Vitals, Advertising Conversion Export and Tracking Spam Prevention feature

  2022

  • Released WP Statistics to Matomo importer

  Our efforts continue

  While we’ve seen incredible growth over the years, our work doesn’t stop there. In fact, we’re only just getting started.

  Today over 55% of the internet continues to use privacy-threatening web analytics solutions, while 1.5% uses Matomo. So there are still great strides to be made to create a more private internet, and joining the Matomo Community is one way to support this movement.

  There are many ways to get involved too, such as :

  • Submitting feature requests
  • Developing for Matomo 
  • Leaving Matomo a review on sites like Capterra, TrustRadius, G2 Crowd, alternativeTo, SaaSworthy, Siftery, Open Hub
  • Translating Matomo
  • Joining our Security Bug Bounty Programme
  • Sharing Matomo with your peers
  • Talking about Matomo on social platforms

  So what comes next for Matomo ?

  The future of Matomo is approachable, powerful and flexible. We’re strengthening the customers’ voice, expanding our resources internally (we’re continuously hiring !) and conducting rigorous customer research to craft a tool that balances usability and functionality.

  I look forward to the next 15 years and seeing what the future holds for Matomo and our community.

• Android FFMPEG video editing operation failed

  30 mai 2022, par Bipin Vayalu

  I am using FFMPEG in my Android app for video cropping and trimming but when I execute the following command on a specific video. FFMPEG command execution failed and the app crashed.

  


  Command :

  


  ffmpeg -y -i "/storage/emulated/0/DCIM/Camera/Test-Video.mp4" -crf 19 -color_primaries 1 -color_trc 1 -colorspace 1 -vcodec h264 -acodec aac -ss 00:00:00 -t 00:00:15 -async 1 -vf "crop=540:539:0:0:exact=0 , scale='if(gt(iw,ih),min(640,iw),-2)':'if(gt(iw,ih),-2,min(640,ih))'" "/data/user/0/com.bipin.myapp/cache/Test-Video_16535454525974982000318197164476.mp4"


  


  Failure logs :

  


  2022-05-26 11:40:52.605 5308-9484/com.bipin.myapp D/[RxCachedThreadScheduler-11;FFmpegUtil#performVideoOperation:151]: Debug - performVideoOperation - Source File: Test-Video.mp4, size: 9.697972297668457 MBs
2022-05-26 11:40:52.605 5308-9484/com.bipin.myapp D/[RxCachedThreadScheduler-11;FFmpegUtil#performVideoOperation:159]: Debug - performVideoOperation - Command: -y -i "/storage/emulated/0/DCIM/Camera/Test-Video.mp4" -crf 19 -color_primaries 1 -color_trc 1 -colorspace 1 -vcodec h264 -acodec aac -ss 00:00:00 -t 00:00:15 -async 1 -vf "crop=540:539:0:0:exact=0 , scale='if(gt(iw,ih),min(640,iw),-2)':'if(gt(iw,ih),-2,min(640,ih))'" "/data/user/0/com.bipin.myapp/cache/Test-Video_16535454525974982000318197164476.mp4"
2022-05-26 11:40:52.607 5308-9484/com.bipin.myapp I/mobile-ffmpeg: Loading mobile-ffmpeg.
2022-05-26 11:40:52.617 5308-9484/com.bipin.myapp I/mobile-ffmpeg: Loaded mobile-ffmpeg-min-gpl-arm64-v8a-4.4-lts-20200724.
2022-05-26 11:40:52.619 5308-9485/com.bipin.myapp D/mobile-ffmpeg: Callback thread started.
2022-05-26 11:40:52.620 5308-9485/com.bipin.myapp I/mobile-ffmpeg: ffmpeg version v4.4-dev-416
2022-05-26 11:40:52.620 5308-9485/com.bipin.myapp I/mobile-ffmpeg:  Copyright (c) 2000-2020 the FFmpeg developers
2022-05-26 11:40:52.620 5308-9485/com.bipin.myapp I/mobile-ffmpeg: 
2022-05-26 11:40:52.620 5308-9485/com.bipin.myapp I/mobile-ffmpeg:   built with Android (6454773 based on r365631c2) clang version 9.0.8 (https://android.googlesource.com/toolchain/llvm-project 98c855489587874b2a325e7a516b99d838599c6f) (based on LLVM 9.0.8svn)
2022-05-26 11:40:52.620 5308-9485/com.bipin.myapp I/mobile-ffmpeg:   configuration: --cross-prefix=aarch64-linux-android- --sysroot=/files/android-sdk/ndk/21.3.6528147/toolchains/llvm/prebuilt/linux-x86_64/sysroot --prefix=/home/taner/Projects/mobile-ffmpeg/prebuilt/android-arm64/ffmpeg --pkg-config=/usr/bin/pkg-config --enable-version3 --arch=aarch64 --cpu=armv8-a --cc=aarch64-linux-android21-clang --cxx=aarch64-linux-android21-clang++ --extra-libs='-L/home/taner/Projects/mobile-ffmpeg/prebuilt/android-arm64/cpu-features/lib -lndk_compat' --target-os=android --enable-neon --enable-asm --enable-inline-asm --enable-cross-compile --enable-pic --enable-jni --enable-optimizations --enable-swscale --enable-shared --enable-v4l2-m2m --disable-outdev=fbdev --disable-indev=fbdev --enable-small --disable-openssl --disable-xmm-clobber-test --disable-debug --enable-lto --disable-neon-clobber-test --disable-programs --disable-postproc --disable-doc --disable-htmlpages --disable-manpages --disable-podpages --disable-txtpages --disable-static --disable-sndio --disable-schannel --disable-securetransport --disable-xlib --disable-cuda --disable-cuvid --disable-nvenc --disable-vaapi --disable-vdpau --disable-videotoolbox --disable-audiotoolbox --disable-appkit --disable-alsa --disable-cuda --disable-cuvid --disable-nvenc --disable-vaapi --disable-vdpau --enable-libx264 --enable-gpl --enable-libxvid --enable-gpl --enable-libx265 --enable-gpl --enable-libvidstab --enable-gpl --disable-sdl2 --enable-zlib --enable-mediacodec
2022-05-26 11:40:52.621 5308-9485/com.bipin.myapp I/mobile-ffmpeg:   libavutil      56. 55.100 / 56. 55.100
2022-05-26 11:40:52.621 5308-9485/com.bipin.myapp I/mobile-ffmpeg:   libavcodec     58. 96.100 / 58. 96.100
2022-05-26 11:40:52.621 5308-9485/com.bipin.myapp I/mobile-ffmpeg:   libavformat    58. 48.100 / 58. 48.100
2022-05-26 11:40:52.622 5308-9485/com.bipin.myapp I/mobile-ffmpeg:   libavdevice    58. 11.101 / 58. 11.101
2022-05-26 11:40:52.622 5308-9485/com.bipin.myapp I/mobile-ffmpeg:   libavfilter     7. 87.100 /  7. 87.100
2022-05-26 11:40:52.622 5308-9485/com.bipin.myapp I/mobile-ffmpeg:   libswscale      5.  8.100 /  5.  8.100
2022-05-26 11:40:52.622 5308-9485/com.bipin.myapp I/mobile-ffmpeg:   libswresample   3.  8.100 /  3.  8.100
2022-05-26 11:40:52.638 5308-5308/com.bipin.myapp D/InputMethodManager: startInputInner - Id : 0
2022-05-26 11:40:52.638 5308-5308/com.bipin.myapp I/InputMethodManager: startInputInner - mService.startInputOrWindowGainedFocus
2022-05-26 11:40:52.645 5308-9485/com.bipin.myapp I/mobile-ffmpeg: Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '/storage/emulated/0/DCIM/Camera/Test-Video.mp4':
2022-05-26 11:40:52.645 5308-9485/com.bipin.myapp I/mobile-ffmpeg:   Metadata:
2022-05-26 11:40:52.645 5308-9485/com.bipin.myapp I/mobile-ffmpeg:     major_brand     : 
2022-05-26 11:40:52.646 5308-9485/com.bipin.myapp I/mobile-ffmpeg: mp42
2022-05-26 11:40:52.646 5308-9485/com.bipin.myapp I/mobile-ffmpeg: 
2022-05-26 11:40:52.646 5308-9485/com.bipin.myapp I/mobile-ffmpeg:     minor_version   : 
2022-05-26 11:40:52.646 5308-9485/com.bipin.myapp I/mobile-ffmpeg: 1
2022-05-26 11:40:52.646 5308-9485/com.bipin.myapp I/mobile-ffmpeg: 
2022-05-26 11:40:52.646 5308-9485/com.bipin.myapp I/mobile-ffmpeg:     compatible_brands: 
2022-05-26 11:40:52.646 5308-9485/com.bipin.myapp I/mobile-ffmpeg: isommp41mp42
2022-05-26 11:40:52.646 5308-9485/com.bipin.myapp I/mobile-ffmpeg: 
2022-05-26 11:40:52.646 5308-9485/com.bipin.myapp I/mobile-ffmpeg:     creation_time   : 
2022-05-26 11:40:52.646 5308-9485/com.bipin.myapp I/mobile-ffmpeg: 2022-04-05T14:20:18.000000Z
2022-05-26 11:40:52.647 5308-9485/com.bipin.myapp I/mobile-ffmpeg: 
2022-05-26 11:40:52.647 5308-9485/com.bipin.myapp I/mobile-ffmpeg:   Duration: 
2022-05-26 11:40:52.647 5308-9485/com.bipin.myapp I/mobile-ffmpeg: 00:00:15.48
2022-05-26 11:40:52.647 5308-9485/com.bipin.myapp I/mobile-ffmpeg: , start: 
2022-05-26 11:40:52.647 5308-9485/com.bipin.myapp I/mobile-ffmpeg: 0.000000
2022-05-26 11:40:52.647 5308-9485/com.bipin.myapp I/mobile-ffmpeg: , bitrate: 
2022-05-26 11:40:52.647 5308-9485/com.bipin.myapp I/mobile-ffmpeg: 5255 kb/s
2022-05-26 11:40:52.647 5308-9485/com.bipin.myapp I/mobile-ffmpeg: 
2022-05-26 11:40:52.647 5308-9485/com.bipin.myapp I/mobile-ffmpeg:     Stream #0:0
2022-05-26 11:40:52.647 5308-9485/com.bipin.myapp I/mobile-ffmpeg: (und)
2022-05-26 11:40:52.647 5308-9485/com.bipin.myapp I/mobile-ffmpeg: : Video: h264 (avc1 / 0x31637661), yuv420p(tv, bt709), 540x960, 5251 kb/s
2022-05-26 11:40:52.647 5308-9485/com.bipin.myapp I/mobile-ffmpeg: , 
2022-05-26 11:40:52.647 5308-9485/com.bipin.myapp I/mobile-ffmpeg: 30.04 fps, 
2022-05-26 11:40:52.647 5308-9485/com.bipin.myapp I/mobile-ffmpeg: 30 tbr, 
2022-05-26 11:40:52.647 5308-9485/com.bipin.myapp I/mobile-ffmpeg: 600 tbn, 
2022-05-26 11:40:52.647 5308-9485/com.bipin.myapp I/mobile-ffmpeg: 1200 tbc
2022-05-26 11:40:52.647 5308-9485/com.bipin.myapp I/mobile-ffmpeg:  (default)
2022-05-26 11:40:52.648 5308-9485/com.bipin.myapp I/mobile-ffmpeg: 
2022-05-26 11:40:52.648 5308-9485/com.bipin.myapp I/mobile-ffmpeg:     Metadata:
2022-05-26 11:40:52.648 5308-9485/com.bipin.myapp I/mobile-ffmpeg:       creation_time   : 
2022-05-26 11:40:52.648 5308-9485/com.bipin.myapp I/mobile-ffmpeg: 2022-04-05T14:20:18.000000Z
2022-05-26 11:40:52.648 5308-9485/com.bipin.myapp I/mobile-ffmpeg: 
2022-05-26 11:40:52.648 5308-9485/com.bipin.myapp I/mobile-ffmpeg:       handler_name    : 
2022-05-26 11:40:52.648 5308-9485/com.bipin.myapp I/mobile-ffmpeg: Core Media Video
2022-05-26 11:40:52.648 5308-9485/com.bipin.myapp I/mobile-ffmpeg: 
2022-05-26 11:40:52.648 5308-9485/com.bipin.myapp I/mobile-ffmpeg: Stream mapping:
2022-05-26 11:40:52.648 5308-9485/com.bipin.myapp I/mobile-ffmpeg:   Stream #0:0 -> #0:0
2022-05-26 11:40:52.648 5308-9485/com.bipin.myapp I/mobile-ffmpeg:  (h264 (native) -> h264 (libx264))
2022-05-26 11:40:52.648 5308-9485/com.bipin.myapp I/mobile-ffmpeg: 
2022-05-26 11:40:52.648 5308-9485/com.bipin.myapp I/mobile-ffmpeg: Press [q] to stop, [?] for help
2022-05-26 11:40:52.673 5308-9485/com.bipin.myapp W/mobile-ffmpeg: [graph 0 input from stream 0:0 @ 0xb400007bf58e0ed0] sws_param option is deprecated and ignored
2022-05-26 11:40:52.674 5308-9485/com.bipin.myapp I/mobile-ffmpeg: [libx264 @ 0xb400007c65974720] using cpu capabilities: ARMv8 NEON
2022-05-26 11:40:52.678 5308-9485/com.bipin.myapp I/mobile-ffmpeg: [libx264 @ 0xb400007c65974720] profile High, level 3.0, 4:2:0, 8-bit
2022-05-26 11:40:52.678 5308-9485/com.bipin.myapp I/mobile-ffmpeg: [libx264 @ 0xb400007c65974720] 264 - core 160 - H.264/MPEG-4 AVC codec - Copyleft 2003-2020 - http://www.videolan.org/x264.html - options: cabac=1 ref=3 deblock=1:0:0 analyse=0x3:0x113 me=hex subme=7 psy=1 psy_rd=1.00:0.00 mixed_ref=1 me_range=16 chroma_me=1 trellis=1 8x8dct=1 cqm=0 deadzone=21,11 fast_pskip=1 chroma_qp_offset=-2 threads=12 lookahead_threads=2 sliced_threads=0 nr=0 decimate=1 interlaced=0 bluray_compat=0 constrained_intra=0 bframes=3 b_pyramid=2 b_adapt=1 b_bias=0 direct=1 weightb=1 open_gop=0 weightp=2 keyint=250 keyint_min=25 scenecut=40 intra_refresh=0 rc_lookahead=40 rc=crf mbtree=1 crf=19.0 qcomp=0.60 qpmin=0 qpmax=69 qpstep=4 ip_ratio=1.40 aq=1:1.00
2022-05-26 11:40:52.678 5308-9485/com.bipin.myapp I/mobile-ffmpeg: Output #0, mp4, to '/data/user/0/com.bipin.myapp/cache/Test-Video_16535454525974982000318197164476.mp4':
2022-05-26 11:40:52.678 5308-9485/com.bipin.myapp I/mobile-ffmpeg:   Metadata:
2022-05-26 11:40:52.678 5308-9485/com.bipin.myapp I/mobile-ffmpeg:     major_brand     : 
2022-05-26 11:40:52.678 5308-9485/com.bipin.myapp I/mobile-ffmpeg: mp42
2022-05-26 11:40:52.678 5308-9485/com.bipin.myapp I/mobile-ffmpeg: 
2022-05-26 11:40:52.678 5308-9485/com.bipin.myapp I/mobile-ffmpeg:     minor_version   : 
2022-05-26 11:40:52.678 5308-9485/com.bipin.myapp I/mobile-ffmpeg: 1
2022-05-26 11:40:52.679 5308-9485/com.bipin.myapp I/mobile-ffmpeg: 
2022-05-26 11:40:52.679 5308-9485/com.bipin.myapp I/mobile-ffmpeg:     compatible_brands: 
2022-05-26 11:40:52.679 5308-9485/com.bipin.myapp I/mobile-ffmpeg: isommp41mp42
2022-05-26 11:40:52.679 5308-9485/com.bipin.myapp I/mobile-ffmpeg: 
2022-05-26 11:40:52.679 5308-9485/com.bipin.myapp I/mobile-ffmpeg:     encoder         : 
2022-05-26 11:40:52.679 5308-9485/com.bipin.myapp I/mobile-ffmpeg: Lavf58.48.100
2022-05-26 11:40:52.679 5308-9485/com.bipin.myapp I/mobile-ffmpeg: 
2022-05-26 11:40:52.679 5308-9485/com.bipin.myapp I/mobile-ffmpeg:     Stream #0:0
2022-05-26 11:40:52.679 5308-9485/com.bipin.myapp I/mobile-ffmpeg: (und)
2022-05-26 11:40:52.679 5308-9485/com.bipin.myapp I/mobile-ffmpeg: : Video: h264 (libx264) (avc1 / 0x31637661), yuv420p(bt709), 540x538, q=-1--1
2022-05-26 11:40:52.679 5308-9485/com.bipin.myapp I/mobile-ffmpeg: , 
2022-05-26 11:40:52.680 5308-9485/com.bipin.myapp I/mobile-ffmpeg: 30 fps, 
2022-05-26 11:40:52.680 5308-9485/com.bipin.myapp I/mobile-ffmpeg: 15360 tbn, 
2022-05-26 11:40:52.680 5308-9485/com.bipin.myapp I/mobile-ffmpeg: 30 tbc
2022-05-26 11:40:52.680 5308-9485/com.bipin.myapp I/mobile-ffmpeg:  (default)
2022-05-26 11:40:52.680 5308-9485/com.bipin.myapp I/mobile-ffmpeg: 
2022-05-26 11:40:52.680 5308-9485/com.bipin.myapp I/mobile-ffmpeg:     Metadata:
2022-05-26 11:40:52.680 5308-9485/com.bipin.myapp I/mobile-ffmpeg:       creation_time   : 
2022-05-26 11:40:52.680 5308-9485/com.bipin.myapp I/mobile-ffmpeg: 2022-04-05T14:20:18.000000Z
2022-05-26 11:40:52.680 5308-9485/com.bipin.myapp I/mobile-ffmpeg: 
2022-05-26 11:40:52.680 5308-9485/com.bipin.myapp I/mobile-ffmpeg:       handler_name    : 
2022-05-26 11:40:52.680 5308-9485/com.bipin.myapp I/mobile-ffmpeg: Core Media Video
2022-05-26 11:40:52.680 5308-9485/com.bipin.myapp I/mobile-ffmpeg: 
2022-05-26 11:40:52.680 5308-9485/com.bipin.myapp I/mobile-ffmpeg:       encoder         : 
2022-05-26 11:40:52.680 5308-9485/com.bipin.myapp I/mobile-ffmpeg: Lavc58.96.100 libx264
2022-05-26 11:40:52.681 5308-9485/com.bipin.myapp I/mobile-ffmpeg: 
2022-05-26 11:40:52.681 5308-9485/com.bipin.myapp I/mobile-ffmpeg:     Side data:
2022-05-26 11:40:52.681 5308-9485/com.bipin.myapp I/mobile-ffmpeg:       
2022-05-26 11:40:52.681 5308-9485/com.bipin.myapp I/mobile-ffmpeg: cpb: 
2022-05-26 11:40:52.682 5308-9485/com.bipin.myapp I/mobile-ffmpeg: bitrate max/min/avg: 0/0/0 buffer size: 0 
2022-05-26 11:40:52.684 5308-9485/com.bipin.myapp I/mobile-ffmpeg: vbv_delay: N/A
2022-05-26 11:40:52.684 5308-9485/com.bipin.myapp I/mobile-ffmpeg: 
2022-05-26 11:40:52.797 5308-5308/com.bipin.myapp D/[main;BaseDaggerFragment#onDestroyView:90]: Debug - PostMediaTabFragment onDestroyView called
2022-05-26 11:40:52.798 5308-5308/com.bipin.myapp D/[main;ViewBindingBaseFragment#onDestroyView:32]: Debug - PostMediaTabFragment onDestroyView called
2022-05-26 11:40:52.895 5308-9521/com.bipin.myapp A/libc: Fatal signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 0xb400007a53e6d000 in tid 9521 (RxCachedThreadS), pid 5308 (com.bipin.myapp)
2022-05-26 11:40:54.302 9524-9524/? A/DEBUG: Cmdline: com.bipin.myapp
2022-05-26 11:40:54.302 9524-9524/? A/DEBUG: pid: 5308, tid: 9521, name: RxCachedThreadS  >>> com.bipin.myapp <<<
2022-05-26 11:40:54.302 9524-9524/? A/DEBUG:       #00 pc 000000000058b8d0  /data/app/~~QE7_ItG7A3ZSxt4PIZf-2w==/com.bipin.myapp-o6_afbhi9zItP6DEnUAd6w==/base.apk!libavcodec.so
2022-05-26 11:40:54.398 1189-1447/? W/ActivityManager: Missing app error report, app = com.bipin.myapp crashing = true notResponding = false
2022-05-26 11:40:54.407 1189-9530/? W/ActivityManager: crash : com.bipin.myapp,10342