Netflix lets you see player stats which includes bitrate. On a computer press Ctrl+Alt+Shift+D. I'm not sure what the combinations are for other platforms.
To add to the great advice you got by davelnewton already, you should consider a few more things.
It's obvious that you're at the point of frustration, and you're taking it personal. It's either affecting your style of communication, or your style of communication is combative as a whole.
Speaking of personal, your resume is very personal, where it should be professional. Reading your resume should be a succinct representation on your professional skills. Your personal style and hobbies are something that co-workers learn during interviews and after you start your job. As other people have said, less is more in this aspect.
Hiring managers find objectives in a resume mostly useless. Even if you insist on including an objective, the current one is weak. It's about as generic as the label you'd find on white bread. It should be a summary of who you are (professionally). For example: "A Software Engineer with over 10 years worth of experience with a track record of delivering exceptional quality on time with a focus on electrical engineering"
Your resume should sell, and you are the product. With that in mind, you should write it in a manner that describes the value you bring, not a laundry list of things you've done at your previous positions. It's great that you wrote driver software, but what impact did it have?
Everything on the resume that adds no value can be removed, that includes all of these 1-2 month long internship (it's ok to combine it into 1 "job" with multiple bullet points demonstrating value). It also includes everything that's extracurricular, hobbies, interests, languages, GPA, etc. (Use judgement here, if the job requires multi-lingual proficiency than you'd want to keep that)
References should not be on your resume. If someone wants a reference, they will ask for it.
You should list major roles and describe you VALUE and not day to day tasks. 3-4 bullet points each one a paragraph elaborating on how your contribution was valuable. Small roles can be combined, but the same rule applies - the place/title doesn't matter only the value.
Is your goal building an Android application or learning a new language?
Instead of asking "Should I use Kotlin or Java to create an Android application?" ask yourself "Do I want to create an Android application using Kotlin or Java?"
You're going to get mixed answers from external forces because this is a mostly subjective question. People who used Java for 10 years will obviously recommend one over the other, while early Kotlin adopters will praise their own choice.
The biggest concern when choosing a language should be "Can I achieve the same results?" in this case is a yes, because you can always use both in the same project if you need to dive deep into some Android API.
Put 10-15 minutes into a simple Hello World in each one, and see which one is more fun and engaging for you to learn.
I needed a small for my C# MAME frontend IV/Play, it didn't matter if it was relational on not. I picked this over SQLite because it's a single native DLL with no dependencies. It also supports POCO mappings (think serialization) which usually requires some ORM type package.
SQLite in .NET is still a little messy - there are several versions in various state of support, and they all depend on multiple packages.