my1stSmartPhone
Member
The video takes up a tiny fraction of the screen. In that sense, it is step backward from my 1st generation iPod Touch. Is there a way there a way to make the video full screen without installing extra apps?
-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
CyanogenMod 12's native youtube viewer so small
- Thread starter my1stSmartPhone
- Start date
There should be 2 diagonal arrows in the bottom right corner of the video which allow you to expand it to fill the entire screen.
funkylogik
share the love peeps ;)
Or just turn the phone on its side
my1stSmartPhone
Member
funkylogiik: Surprisingly, turning the phone on its side does not increase the picture size.
El Presidente: Yes! That's it! But you have the tap the video screen before you see the double arrow.
Err...how does one make it not full screen again? The double arrow is not visible in landscape orientation. In portrait orientation, it is, but it doesn't switch back to non-full-screen. I can click the little cyanogenmod square at the bottom right of the smartphone's display to get out of the browser, then select to switch back to the browser, but hopefully there is a more direct way to get out of full-screen?
El Presidente: Yes! That's it! But you have the tap the video screen before you see the double arrow.
Err...how does one make it not full screen again? The double arrow is not visible in landscape orientation. In portrait orientation, it is, but it doesn't switch back to non-full-screen. I can click the little cyanogenmod square at the bottom right of the smartphone's display to get out of the browser, then select to switch back to the browser, but hopefully there is a more direct way to get out of full-screen?
Are you using a browser of the dedicated youtube app?
https://play.google.com/store/apps/details?id=com.google.android.youtube
https://play.google.com/store/apps/details?id=com.google.android.youtube
my1stSmartPhone
Member
I'm using the native browser. I'm trying to avoid apps because the permissions of apps takes a lot of work and guess-work to vet. That, and the whole business of signing in to get apps, is not an area that I fully understand at this point. One of the things driving my preoccupation with this is the importance that I place on privacy.
Fair enough. 
Don't you want to install anything, or if you could install apps without signing in to a gmail account, would that work for you?
If you're looking for a great explanation of permissions, take a look here: http://androidforums.com/threads/an...ned-security-tips-and-avoiding-malware.36936/
Don't you want to install anything, or if you could install apps without signing in to a gmail account, would that work for you?
If you're looking for a great explanation of permissions, take a look here: http://androidforums.com/threads/an...ned-security-tips-and-avoiding-malware.36936/
my1stSmartPhone
Member
Thanks, Presidente. I'm working through your permissions post. Nice explanations.
From what I've read online, it seems that liberal permissions is the norm, which makes apps installation a real...project. So much time and work needed just to obtain basic functions. Things never use to be like this. We relied on the product manufacturer for good functionality. These days, the smartphone is merely a platform, and you are exposed to a new vendor for each and every incremental piece of functionality (i.e., app). Furthermore, since the smartphone is a platform, the paradigm is that there is no need for the vendor to get the functionality just right, since there are hoardes of developers (vendors) ready to fill the many gaps. You end up with really whacky design details in the virgin system, like microfonts used for the text editor, lockscreens that don't permit removal of time display, text selection that sort of works, etc. This basically forces you to look beyond the stock system to (in essence) create your own system by exposing yourself to a great number of vendors. The stock system is just scaffolding.
Smartphone makers that make turnkey systems ....well, I'm not sure if they would even eliminate the need for an apps market place. For one thing, the new generation demands diversity in apps, so a phone maker needs to ensure that the ecosystem is cultivated. No apps market place equals no market for the phone. Secondly, with the Carrier IQ issue years ago, phone vendor ROMs are not trustworth, so open source (e.g., CyanogenMod) seems to be the most sensible way to go. Ergo, back to the scaffolding and need to turn to the apps market.
You asked if I'd be good with signing on to Google to download apps. I don't know enough about the implications yet. Google already gets all my email and calendar items. They already know all the things that I post about because I archive each original post as email containing the link, regardless of the forum. Even though I've read about signing in to Google for apps as a concern, I'm not so sure that it is for someone whose identities are comletely transparent to Google already. I should read a bit more about the details of the concern before dispensing with it.
From what I've read online, it seems that liberal permissions is the norm, which makes apps installation a real...project. So much time and work needed just to obtain basic functions. Things never use to be like this. We relied on the product manufacturer for good functionality. These days, the smartphone is merely a platform, and you are exposed to a new vendor for each and every incremental piece of functionality (i.e., app). Furthermore, since the smartphone is a platform, the paradigm is that there is no need for the vendor to get the functionality just right, since there are hoardes of developers (vendors) ready to fill the many gaps. You end up with really whacky design details in the virgin system, like microfonts used for the text editor, lockscreens that don't permit removal of time display, text selection that sort of works, etc. This basically forces you to look beyond the stock system to (in essence) create your own system by exposing yourself to a great number of vendors. The stock system is just scaffolding.
Smartphone makers that make turnkey systems ....well, I'm not sure if they would even eliminate the need for an apps market place. For one thing, the new generation demands diversity in apps, so a phone maker needs to ensure that the ecosystem is cultivated. No apps market place equals no market for the phone. Secondly, with the Carrier IQ issue years ago, phone vendor ROMs are not trustworth, so open source (e.g., CyanogenMod) seems to be the most sensible way to go. Ergo, back to the scaffolding and need to turn to the apps market.
You asked if I'd be good with signing on to Google to download apps. I don't know enough about the implications yet. Google already gets all my email and calendar items. They already know all the things that I post about because I archive each original post as email containing the link, regardless of the forum. Even though I've read about signing in to Google for apps as a concern, I'm not so sure that it is for someone whose identities are comletely transparent to Google already. I should read a bit more about the details of the concern before dispensing with it.
http://www.apkmirror.com/apk/google-inc/youtube/youtube-10-09-56-android-apk-download/
Try installing the Youtube app from there, I'm not sure if it will allow you to not sign in once it's installed, but give it a go anyway.
I kinda felt the same about the Google integration, but as I've used a gmail account as my primary email account since it was in early beta, I'm relatively sure they know all they want to know about me anyway.
You're kinda limiting yourself by not using your google account, but if you've privacy concerns, it is entirely possible to use Android without one.
If you do want to start experimenting with apps, would using the Amazon app store be an option?
Try installing the Youtube app from there, I'm not sure if it will allow you to not sign in once it's installed, but give it a go anyway.
I kinda felt the same about the Google integration, but as I've used a gmail account as my primary email account since it was in early beta, I'm relatively sure they know all they want to know about me anyway.
You're kinda limiting yourself by not using your google account, but if you've privacy concerns, it is entirely possible to use Android without one.
If you do want to start experimenting with apps, would using the Amazon app store be an option?
my1stSmartPhone
Member
I don't normally explore much in the way of apps for either the laptop or the 1st generation iPod Touch. In my world, they're basically tools to get stuff done rather than objects of entertainment or amusement (with exceptions). I didn't expect myself needing to explore apps so early just for basic functionality due to the rough-n-ready state of the OS -- this may be just because of the decision to go with an open source OS (I consider vendor ROMs to be opaque even though the may be derived from open source) . nor did I expect that in the apps ecosystem, loose permissions would be so pervasive, thus complicating the process of rounding out the OS.
As for APIs from other sources, I need to mull that one. It depends on what signin is needed and whether the source is more trustworthy than Google. The permissions tutorial that you referenced listed a few sites that were generally considered good. My personal bar might be a bit higher, e.g., I didn't go with a Moto G tool for installing a recovery, nor did I follow forum links to online repositories for carrier ROMs. For the latter, I currently would only get such images from the carrier's domain, if they provide them (mime did not). I've also pondered decision of getting APKs directly from the vendor. Need to assess vendor reputation and consider the possibility that the APK might not necessarily be exactly identical to the installation package from Google Play.
As I griped, things never use to be this involved. Then again, the market for identity info was probably never as thriving as today (I mean for potential customers, not necessarily identity theft). The immaturity of the platform, and the wild-west nature of the app ecosystem doesn't help. This can be contrasted with the situation for laptops, where OSs are well rounded and best practices are well known, as are the identities of reliable software.
As for APIs from other sources, I need to mull that one. It depends on what signin is needed and whether the source is more trustworthy than Google. The permissions tutorial that you referenced listed a few sites that were generally considered good. My personal bar might be a bit higher, e.g., I didn't go with a Moto G tool for installing a recovery, nor did I follow forum links to online repositories for carrier ROMs. For the latter, I currently would only get such images from the carrier's domain, if they provide them (mime did not). I've also pondered decision of getting APKs directly from the vendor. Need to assess vendor reputation and consider the possibility that the APK might not necessarily be exactly identical to the installation package from Google Play.
As I griped, things never use to be this involved. Then again, the market for identity info was probably never as thriving as today (I mean for potential customers, not necessarily identity theft). The immaturity of the platform, and the wild-west nature of the app ecosystem doesn't help. This can be contrasted with the situation for laptops, where OSs are well rounded and best practices are well known, as are the identities of reliable software.