First  Prev  72  73  74  75  76  77  78  79  80  81  82  83  84  85  86  87  88  Next  Last
Android
21432 cr points
Send Message: Send PM GB Post
20 / M / University of Tex...
Offline
Posted 2/11/13

alniau wrote:


PatrickAupperleUtexas wrote:

Please hide the soft keys during video playback. It isn't hard, and they really annoy me.
http://stackoverflow.com/questions/8469112/hide-ics-back-home-task-switcher-buttons


lights out mode huh.


Lights out mode isn't quite right. It leaves the bar across the bottom. What really needs to happen is the view needs the SYSTEM_UI_FLAG_HIDE_NAVIGATION flag.
13979 cr points
Send Message: Send PM GB Post
M / 20.0167° N, 155.6...
Online
Posted 2/11/13 , edited 2/11/13
like in the android 17 SDK packet (API)

you know where to find it in your current rom? I can write you a string to replace......
21432 cr points
Send Message: Send PM GB Post
20 / M / University of Tex...
Offline
Posted 2/11/13 , edited 2/11/13

alniau wrote:

like in the android 17 SDK packet (API)

you know where to find it in your current rom? I can write you a string to replace......



I'm using the stock Nexus 4 ROM fully updated.

No, I don't really know where to find it. I have to admit I've done much more development for Windows than Android. I've even done more WP7 development than Android.

Edit: After rereading your question, I believe I may have misunderstood it. Would you mind clarifying? Where to find what in my current rom?
67860 cr points
Send Message: Send PM GB Post
53 / M / Northeast Ohio, USA
Offline
Posted 2/13/13

PatrickAupperleUtexas wrote: Please hide the soft keys during video playback. It isn't hard, and they really annoy me.
http://stackoverflow.com/questions/8469112/hide-ics-back-home-task-switcher-buttons

I assume that wouldn't be any change in my Nook Color, which is Android 2.2 (though the more branches in the code used by some Android versions and not others, the more likely bugs are to creep into some of those branches).

But it seems like it would suck on my cheap chinese 7" tablet, which doesn't have hardware back and menu buttons and I am used to using the softkeys a lot more than my Nook Color which has a hardware "back" key or my 4.3" player, which has hardware "back" and "menu" keys
21432 cr points
Send Message: Send PM GB Post
20 / M / University of Tex...
Offline
Posted 2/13/13

agila61 wrote:


PatrickAupperleUtexas wrote: Please hide the soft keys during video playback. It isn't hard, and they really annoy me.
http://stackoverflow.com/questions/8469112/hide-ics-back-home-task-switcher-buttons

I assume that wouldn't be any change in my Nook Color, which is Android 2.2 (though the more branches in the code used by some Android versions and not others, the more likely bugs are to creep into some of those branches).

But it seems like it would suck on my cheap chinese 7" tablet, which doesn't have hardware back and menu buttons and I am used to using the softkeys a lot more than my Nook Color which has a hardware "back" key or my 4.3" player, which has hardware "back" and "menu" keys


It would be a very minor branch. Only ~5 lines of code need added.

It wouldn't suck on any device. It would work like the Youtube app. If you touch the screen, the soft keys reappear. It just frees up some of the screen when you aren't trying to push buttons. This would then allow my Nexus 4 (which doesn't have any hardware buttons other than power and volume) to display the videos in 720p (assuming the app supports that), something it can't do now because the soft keys take up some of the pixels from the edge of the screen (reducing the horizontal resolution to below 1280).
67860 cr points
Send Message: Send PM GB Post
53 / M / Northeast Ohio, USA
Offline
Posted 2/13/13

PatrickAupperleUtexas wrote: This would then allow my Nexus 4 (which doesn't have any hardware buttons other than power and volume) to display the videos in 720p (assuming the app supports that).

They've got 48 pixels to play with before it gets below 720 ... how many pixels high are the soft key icons on that device?

Right now the Android app is 360p, so its not leaving the softkey icons on that are preventing 720p.
21432 cr points
Send Message: Send PM GB Post
20 / M / University of Tex...
Offline
Posted 2/13/13 , edited 2/13/13

agila61 wrote:


PatrickAupperleUtexas wrote: This would then allow my Nexus 4 (which doesn't have any hardware buttons other than power and volume) to display the videos in 720p (assuming the app supports that).

They've got 48 pixels to play with before it gets below 720 ... how many pixels high are the soft key icons on that device?

Right now the Android app is 360p, so its not leaving the softkey icons on that are preventing 720p.


The screen on a nexus 4 is 1280×768. 720p is 1280x720. Clearly, the soft keys take pixels from the taller direction, reducing the 1280. This prevents 720p playback.

Somewhat disappointing to hear about the android app being limited, but I'd still like (mostly) full screen playback. Hopefully 720p will come around soon, as well. The two together would be great.
67860 cr points
Send Message: Send PM GB Post
53 / M / Northeast Ohio, USA
Offline
Posted 2/14/13 , edited 2/14/13

PatrickAupperleUtexas wrote: The screen on a nexus 4 is 1280×768. 720p is 1280x720. Clearly, the soft keys take pixels from the taller direction, reducing the 1280. This prevents 720p playback.

No, in landscape mode 1280 is side to side and 768 is top to bottom. The soft keys would take pixels from the 768.

Obviously 720p is likely to come for the iPad/iPhone first, since Android is such a fragmented mess to develop for.
21432 cr points
Send Message: Send PM GB Post
20 / M / University of Tex...
Offline
Posted 2/14/13

agila61 wrote:


PatrickAupperleUtexas wrote: The screen on a nexus 4 is 1280×768. 720p is 1280x720. Clearly, the soft keys take pixels from the taller direction, reducing the 1280. This prevents 720p playback.

No, in landscape mode 1280 is side to side and 768 is top to bottom. The soft keys would take pixels from the 768.

Obviously 720p is likely to come for the iPad/iPhone first, since Android is such a fragmented mess to develop for.


You sure about that?


Android isn't so bad to develop for. Admittedly, I haven't done anything worth anything for it, but you could just target 2.3 and throw in a few small things from 4.0 or 4.1 (like hiding the soft keys). Then it would work on most any android device.
67860 cr points
Send Message: Send PM GB Post
53 / M / Northeast Ohio, USA
Offline
Posted 2/15/13 , edited 2/15/13

PatrickAupperleUtexas wrote: You sure about that?

Your image doesn't show where the softkeys are located. If they are located at the side, there's a mistake in putting the device into landscape to show the video.


Android isn't so bad to develop for. Admittedly, I haven't done anything worth anything for it, but you could just target 2.3 and throw in a few small things from 4.0 or 4.1 (like hiding the soft keys). Then it would work on most any android device.

Doing that would of course lose more the 10% of the market which is Android 2.2. But the fragmented mess part is not in four different levels that must be supported to get 95% of the market so much as the differences the different implementations from the different device makers.

That's why there is the constant stream of unexpected problems that crop up with new CR app releases. If you have an iOS app that works on a collection of eight Apple devices, it likely works on all of them. If you have an Android app that works on a collection of eight Android devices, it all too often breaks on the ninth that you don't have..
21432 cr points
Send Message: Send PM GB Post
20 / M / University of Tex...
Offline
Posted 2/15/13 , edited 2/15/13

agila61 wrote:


PatrickAupperleUtexas wrote: You sure about that?

Your image doesn't show where the softkeys are located. If they are located at the side, there's a mistake in putting the device into landscape to show the video.


Those three dots on the right are the soft keys (crunchyroll did put it in lights out mode). If the buttons staying on the right is an error, it is a very common one (YouTube, Netflix and every app I've ever used on this phone leave the buttons on the right in landscape).





Android isn't so bad to develop for. Admittedly, I haven't done anything worth anything for it, but you could just target 2.3 and throw in a few small things from 4.0 or 4.1 (like hiding the soft keys). Then it would work on most any android device.

Doing that would of course lose more the 10% of the market which is Android 2.2. But the fragmented mess part is not in four different levels that must be supported to get 95% of the market so much as the differences the different implementations from the different device makers.

That's why there is the constant stream of unexpected problems that crop up with new CR app releases. If you have an iOS app that works on a collection of eight Apple devices, it likely works on all of them. If you have an Android app that works on a collection of eight Android devices, it all too often breaks on the ninth that you don't have..


target 2.1 or whatever it currently targets then. My point still stands.

As for apps not working on devices they weren't explicitly tested OK, I say BS. The majority of apps probably still haven't been thoroughly tested on the nexus 4, yet I've not found a single one that doesn't work perfectly.
67860 cr points
Send Message: Send PM GB Post
53 / M / Northeast Ohio, USA
Offline
Posted 2/15/13

PatrickAupperleUtexas wrote: Those three dots on the right are the soft keys (crunchyroll did put it in lights out mode). If the buttons staying on the right is an error, it is a very common one (YouTube, Netflix and every app I've ever used on this phone leave the buttons on the right ).


I know from my Android player and Nook Color that the notification and status bars move correctly in Android 2.2 and 2.3, and from my Cheap Chinese tablet that they move correctly in 4.0. If they no longer move correctly in 4.1, that's interesting. Though it could your settings, and not the system itself.


target 2.1 or whatever it currently targets then. My point still stands.

The earlier the version that you target, the more the API varies from the Android 4.x API, and the more branches you introduce in the code to support the Android 4.x features while still running on earlier versions. Every time you do an upgrade, you should exercise each branch of the source before release, and the more branches there are, the more likely there are combinations of branches that you are going to miss.


As for apps not working on devices they weren't explicitly tested OK, I say BS. The majority of apps probably still haven't been thoroughly tested on the nexus 4, yet I've not found a single one that doesn't work perfectly.


In other words, you are arguing that its not a fragmented landscape by saying that things work for you. But in a fragmented landscape, the fact that it works for you over in fragment A does not imply that it works for someone else over in fragment B. In a fragmented landscape, the experience using the Google-branded flagship devices that are Android showpieces is not the same as the experience using some other Android devices.

To take a more clearcut example than the glitches that sometimes show up in the Android help forum, the Funimation app does not successfully play video on the Nook Color. There's no telling whether that's an encoding problem or a software problem, and every other part of the app works ... except for the whole reason for having the app in the first place.
21432 cr points
Send Message: Send PM GB Post
20 / M / University of Tex...
Offline
Posted 2/15/13 , edited 2/15/13

agila61 wrote:

I know from my Android player and Nook Color that the notification and status bars move correctly in Android 2.2 and 2.3, and from my Cheap Chinese tablet that they move correctly in 4.0. If they no longer move correctly in 4.1, that's interesting. Though it could your settings, and not the system itself.


The status bar still moves correctly. The soft buttons just remain stationary (although the pictures do turn, https://skydrive.live.com/redir?resid=8261E8443106DA8E!38503&authkey=!AB1Y_CNN3M83PUY). It could be settings, I guess, but can't seem to find any way to change them. I think it is more likely a tablet vs phone difference.



The earlier the version that you target, the more the API varies from the Android 4.x API, and the more branches you introduce in the code to support the Android 4.x features while still running on earlier versions. Every time you do an upgrade, you should exercise each branch of the source before release, and the more branches there are, the more likely there are combinations of branches that you are going to miss.


There is some truth to this, but I solely target Android 2.3 in my (somewhat meager) development and have yet to have a problem. I don't access the 4.x features much, though. Only to change (hide or lights out mode) the soft keys. These code branches are extremely small and require very little testing.



In other words, you are arguing that its not a fragmented landscape by saying that things work for you. But in a fragmented landscape, the fact that it works for you over in fragment A does not imply that it works for someone else over in fragment B. In a fragmented landscape, the experience using the Google-branded flagship devices that are Android showpieces is not the same as the experience using some other Android devices.


My device working certainly isn't proof of anything, but still provides some evidence. I've also spoken to friends who have all manner of different phones and (as far as I know) have no problems with any app. I also have a Samsung Vibrant running a Jelly Bean ROM that almost never had any difficulties (it ran low on RAM in a couple of apps, but nothing else). A no name custom ROM running most everything perfectly on a 2 year old device certainly shows something.



To take a more clearcut example than the glitches that sometimes show up in the Android help forum, the Funimation app does not successfully play video on the Nook Color. There's no telling whether that's an encoding problem or a software problem, and every other part of the app works ... except for the whole reason for having the app in the first place.


To be fair, a Nook Color is about as far as you can get from Android and still call it Android. I also never said problems couldn't arise, only that they usually don't. How much Android development have you done? Have you personally experienced problems with the apps you wrote? I'd be interested to hear about the code that inexplicably didn't work on a device.
67860 cr points
Send Message: Send PM GB Post
53 / M / Northeast Ohio, USA
Offline
Posted 2/21/13 , edited 2/21/13

PatrickAupperleUtexas wrote: The status bar still moves correctly. The soft buttons just remain stationary (although the pictures do turn) ..

How bizarre. I looked at how my cheap chinese ICS tablet works, and it (1) swings ~ both the status bar and the softkeys ~ and then the video display expands to full width, so the Crunchyroll app doesn't prevent full screen in FroYo, Gingerbread or Ice Cream Sandwich. The FroYo is heavily customized (a rooted stock Nook Color), the Gingerbread and Ice Cream Sandwich are pretty generic.

Why it would not work in JellyBean, I have no idea.


PatrickAupperleUtexas wrote: To be fair, a Nook Color is about as far as you can get from Android and still call it Android. ...

Its just Android Frozen Yogurt with its own home app and a set of standard bundled apps. The lack of Google Play is a substantial usability issue, but it's not a fundamental system level issue.

Though the most likely problem would be Funimation's encoding rather than Android programming ~ that level of PowerVR (SGX 530) can only handle the Baseline profile of H.264. Of course, the Nook Color is not the only device to be built with an SGX 530 or below PowerVR graphics chip ~ for instance, the original Droid used the SGX530 core.
47325 cr points
Send Message: Send PM GB Post
27 / F
Offline
Posted 2/22/13
-has not read any recent posts so dont get mad-

I cannot play any of the premium only videos on either my nexus 7 or droid 4. i keep getting the message "we are preparing this show for your device. please check back later!"


i'm talking even the naruto epidoses, not shippuden but regular naruto. i use my phone and tablet to watch my anime primarily so to pay $100 a year(yearly subscription) and not be able to watch premium episodes on my devices kinda pisses me off. what is going on in order to fix this? i cant imagine that im the only one with this issue if its happening on both devices
First  Prev  72  73  74  75  76  77  78  79  80  81  82  83  84  85  86  87  88  Next  Last
You must be logged in to post.