FORUMS

Voices Of XDA: Orbiting The Earth With Android

Editor’s note: This week’s feature has been written by forum … more

CloudPlayer: DIY HiFi Music Streaming Solution

In our Helpful Guide to Music Streaming Services, we mentioned several different services … more

Optimize Battery Life with This Useful App

Battery life is an important aspect of your smartphone, especially if you use it for more … more

The OnePlus 2 & The Year of Smartphone Compromises

We are very close to entering the last third of 2015, and we have now seen many of … more

[Q] JellyBean for T320

4 posts
Thanks Meter: 0
 
By einmed, Junior Member on 14th April 2014, 12:11 PM
Post Reply Subscribe to Thread Email Thread
17th April 2014, 11:48 AM |#11  
conan1600's Avatar
Senior Member
Thanks Meter: 208
 
Donate to Me
More
Quote:
Originally Posted by roustabout

I'm going to at least empathize with the OP here. The biggest downside of the 8.4 to me is that it turns out that a lot of the web stuff I do is expecting flash to run. And please don't tell me flash is dead and html 5 rUleZ - yes, I know, but a lot of web devs haven't gotten the memo yet.

I would love it if there was interest in the CM community in making n-1 releases available for devices, as they are so good at getting the current OS and the N+1 releases available.

Google hacked version of flash player for Kit Kat. With dolphin browser you can enable flash content with this.
 
 
17th April 2014, 11:50 PM |#12  
Senior Member
Thanks Meter: 207
 
More
Quote:
Originally Posted by conan1600

Google hacked version of flash player for Kit Kat. With dolphin browser you can enable flash content with this.

But not in Flipboard, which embeds a lot of video into articles. I can break out of Flipboard and into dolphin, then load the file that way but it's a much better experience on my 4.2 device which can simply load the video.

The experience is similar with other apps that embed links.

Oh, and of course I'd forgotten - the magazine UI is basically flipboard, so it must spend a lot of time *trying* to show video and being unable to, because so much video out in the world won't work with Kitkat, or barely wll at best.

Quote:
Originally Posted by crpalmer

New hardware often requires new software. The tab pro 8.4 is a dual dsi device that is on the bleeding edge of what is supported.

Pardon my ignorance, but what is dual DSI?

I understand that the n-1 support is difficult, especially given how long folks often have to lobby to get source code. I still empathize with the OP, though - if I want to run an older linux on newer hardware, I very often can. I may sacrifice a feature or three, but it would be nice if Android supported doing that as well.

Quote:

I will be shocked if anyone tries

There's the thing - as far as I know, folks with build tools and knowhow aren't that interested in trying.

My impression is that it's ultimately down to the difficulty of getting source for hardware drivers, to support building without dependencies on newer system features. A lot of times, though, it's expressed along the lines of "what idiot would want to do that?" - and the transition to Kitkat is starting to highlight some areas where the newer OS seems incremental at best, and for many, purely lateral.
Last edited by roustabout; 17th April 2014 at 11:55 PM.
18th April 2014, 12:49 AM |#13  
Senior Member
Thanks Meter: 4,315
 
Donate to Me
More
Quote:

[quote name="crpalmer" post=51964976]New hardware often requires new software. The tab pro 8.4 is a dual dsi device that is on the bleeding edge of what is supported.

<br />
<br />
Pardon my ignorance, but what is dual DSI? <br />
<br />
I understand that the n-1 support is difficult, especially given how long folks often have to lobby to get source code. I still empathize with the OP, though - if I want to run an older linux on newer hardware, I very often can. I may sacrifice a feature or three, but it would be nice if Android supported doing that as well.<br />
<br />
[/QUOTE]

Dual dsi means that your big lovely pixel rich screen is actually two screens that are so carefully aligned that you can't tell and android is splitting the display between the two screens.

This is very new (for the CM 11 build I had to pull in fixes that were newer than what CM was currently supporting) and whether or not people want to try to port and older android, I would be shocked if someone did so successfully.
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes