Samsung Amps Up Its Multi-Window Android Upgrade
DeviceGuru writes "New multiwindow, multitasking features in Samsung's recent Jellybean update to the Galaxy Note 10.1 have pushed the user interface of Android tablets into new territory, adding MS Windows-like capabilities that are sure to delight many users — and aggravate others. Although some observers have warned of the dangers of forking Android, Samsung's efforts to extend Android and its ecosystem can be defended as being consistent with Google's master plan for the Android system, most of which is released under ASLv2. And remember: unlike Apple, Android device makers, and the wireless carriers who offer Android smartphones to their customers, need ways to differentiate their products."
First, I find out last night that Attack of the Show was just Leo Laporte's bad dream all along, and now this. But I do love the delightful irony* of desktop OS maker Microsoft moving AWAY from the windows, building a more tablet/phone-oriented OS for desktops with Windows 8--at the same time as tablet/phone maker Samsung is moving TOWARDS the windows, building a more desktop-oriented OS for its tablets and phones with this. You can't make this shit up.
* And before any of you grammar Nazi's start soiling your panties, yes, I am damned well familiar with the *classic* definition of "irony." So the first one of you pretentious pedagogues who feels the need to show everyone how big your intellectual dick is by pointing out that classic irony is more akin to what we generally call "sarcasm" today is going to get a visit from me tonight. And I've got diarrhea and a strong desire to leave a double-decker in every toilet in your house.
What political party do you join when you don't like Bible-thumpers *or* hippies?
This is much needed if Android ever wants to branch into the market for people you actually like to DO things, rather than just CONSUME things. I approve, but I wouldn't like to see this on every device - only larger and more powerful devices where it makes sense, of course.
Do I rather to see the 4 inch by 4 inch box on my weather temperature app that shows "-25 C"?
Awesome. More shit that can cause your app work on one Android tablet and not on another. Because there wasn't enough of that already.
This ia an Android thread, not iOs
it's turning into Windows. Fork that!
Please do not read this sig. Thank you.
You've got to love how having multi-window capability is being "MS Windows-like", according to the submitter. I guess we have a bit of computer history to rewrite again...
I, for one, welcome our new Android fragmentation overlords.
I would love for this to be added in to the base Android OS. It is such a dream and is fluid as hell.
It reminds me of tiling window managers, which are so handy if you hate messing around with window placement and Actually Want To Get Stuff Done.
But it also has classic window management too.
Come on Samsung and Android devs, work together to bring this to everyone.
Yes, take your time if it means getting more people to get your tablet over others, but allowing everyone to work with this would be great.
Obviously some things won't across to some systems easily, such as pen interaction with the secondary button.
This feature actually makes Android feel more like an actual OS instead of some baby OS that forces fullscreen on you.
Shame on devs who don't make scalable apps anyway, you and your app sucks, get good.
Not to mention those that force a certain orientation on you, holy hell that annoys me. Toolbars can be made to scroll if they are too small, even forced in to a menu if it gets small enough (but that won't happen, that is just over-optimization)
I've already used a pretty decent VNC app that does the above, but it still has an odd bug where it moves the mouse down when it loses focus and comes back in to focus again. A screen-rotate fixes it. Will need to message the developer for that and see if he can figure it out.
Android device makers, and the wireless carriers who offer Android smartphones to their customers, need ways to differentiate their products.
You do that mainly with hardware and with customer service.
Then you can place own custom wallpaper and custom icons, but stupid way to do is to bake them to Android framework so user can not remove them.
The correct (and smart) way would be to do a own launcher and own icon theme for it and make it available only for your hardware.
OEM could make custom look, custom functions but should always allow easily the user to swap to vanilla Android look and functionality.
Be a good OEM, support Android and give a customer change to actually like your product and use it as they want. OEM is hardware manufacturer what should focus for hardware first and then to user experience.
Not windows 8.
Well really there are three Androids now:
1) Amazon
2) Samsung
3) Everyone else
Samsung by grabbing so much market share of Android sales, now how the power to drive Android in a direction it wants to go.
Its not a bad or a good thing; it's just what is. If I were doing Android development supporting Samsung extensions would seem to be a pretty good idea.
"There is more worth loving than we have strength to love." - Brian Jay Stanley
They're free to fork it if they want. If google doesn't like it then tough. They can think back to the time they pissed off oracle and the Linux kernel people. Besides that's what happens when you flood the market with a bunch of nearly identical cheap phones. Hardware people will need to stand out in some way and unlike the iPhone most of them have shit margins and won't have a problem doing what they think they can do to protect their position
Slashdot seems to have some severe issues with Android being forked by various hardware manufacturers...and yet...every time a post about some new "I hate GNOME 3" Ubuntu spin-off gets posted here people latch onto it like the second coming. It's almost as if the hivemind is divided on this subject, is forking a project a good idea or not? Maybe it's not all as clear as a black and white, one line question?
Never mind, this is Slashdot. No one thinks in any other color but black and white here.
While the window does have its uses, I find most of the time I want a single app operating full screen. Additional apps are sometimes useful and I tend to fit them on a second window,but on the whole I find switching between apps using the taskbar is a lot more useful.
I'm clearly not the only person who feels this way to some degree. There's a reason that firefox gained market share, and much as I wish it was, it probably wasn't because of standards compliance. It was because it didn't clutter the workspace with windows.
So it will
*blue screen
*get malware
*gum up registry
*hog your hardware
*dial back to Redmond
*overwrite the bootloader regardless of other OSes
*600 page EULA
*super sikrit code keys asked at every turn
*activation bullshit
hmm.. no thx
Lemme ask: has this guy ever used a computer or just M$ Winders?
Android does windows! When will Google update my phone to that? Man I can't wait.
I'm kidding I know it's a forked version but I wonder if Google will now how to add it.
I really don't see how this functionality fragments Android.
It doesn't exactly fragment in the traditional way, but I believe you can code in some ways that enhance your apps use in the multi-window mode - but because Samsung is such a large component of the Android market and also most of the higher end of it, if I were making an Android app I'd specifically add whatever support made sense for that even though it is Android specific.
"There is more worth loving than we have strength to love." - Brian Jay Stanley
Nobody uses the term "Android" when pitching to consumers, but Samsung is particularly aggressive about differentiating their software. If all the distributions competed only on hardware it would be a boring market.
I applaud Sammy on making Android more useable in a hybrid/convertible setup, however, I wish they'd make it less ugly. Windows 8 has ugliness in ex-Metro, but at least the desktop environment looks great.
In my experience when carriers try to 'differentiate' their phones, they install shitware, cripple the device, and sometimes even modify it to cost you more money.
Years ago when phones which could surf the web were new, a friend spent an entire weekend trying to reconcile his charged bandwidth with what he believed it should have been -- in the end, the way the carrier had injected themselves into the process ended up sending twice as much data. It could have been innocent, or it could have been a cash grab. The end result was the same, a slower more costly data plan.
In my experience, the carrier specific stuff installed on a phone makes it worse. On my current Android phone, I disabled everything specific to the carrier and ended up with a *far* better phone, because they want to stick themselves into everything or sell you ring tones and other shit.
Carriers usually aren't qualified to do a good job of this, and they're only looking out for their own profits.
Lost at C:>. Found at C.
I'll let the "forking android" conversation run its course. From the point of a casual tablet user, this is progress. There are lots of times it's a hassle to have some info in one app, and some in another, and only be permitted to have one open at a time. This may be confusing or cause the world to stop spinning or whatever, but to me it's useful.
If this were Usenet, I'd killfile the lot of you.
Hasn't Samsung learned its lesson when it copied Apple and got fined a billion dollars for doing so?
Forking android is fine, as long as you give Google some pull-request love. If the changes are not integrated back in, Google will come up with their own different implementation of it next year.
Samsung has zero credibility on putting out quality software. There is a bug on their Android software (not on Google's base code), that causes applications to crash when they use the clipboard. Has been this way for months, and ever after various software updates, Samsung has failed to acknowledge the error even exists, so there is also very low chances that they will go through the trouble of putting out a fix, as simple as it may be (users with root access can just periodically delete a file and everything works perfectly fine).
What a joke.
https://code.google.com/p/android/issues/detail?id=35732
http://developer.samsung.com/forum/board/thread/view.do?boardName=GeneralB&messageId=213645
The N4/N7/N10 are pretty much flying off the shelves as fast as they can make them.
It's funny that the Samsung/Android is adding "MS Windows" functionality at the same time MS Windows is loosing that functionality.
OK, Samsung is the biggest player in Android right now, but seeing as how so many iOS and Andoid devs seem to have so much trouble making their apps scale to different resolutions, I wonder how many 'windowing' apps we will ultimately see.
I don't know anything about developing for those platforms; can anyone here say how hard or trivial it is?
(Like, why did I get an update for virtually all my iPhone and iPad apps when the iPhone 5 came out, although they seemed to be just to cater for the different screen resolution of the iPhone 5, which i was clearly not using. Have not noticed this with my Andoid devices..)
Also, how hard for Google to just stick this feature back into 'base' Andoid? Real multi-tasking and windowing, that would really stick it to iOS, eh? The hardware seems beefy enough now...
Actually, if Google doesn't like it, Samsung will be forbidden to call it Android. This already happened once with Acer. What makes you think Google won't spank Samsung too if necessary?
Have a Virgin Mobile USA smartphone? Give VMRoms.com a try!
Needing multiple windows on a tablet or phone means you are using it wrong, or really want to be using a laptop.
I haven't thought of anything clever to put here, but then again most of you haven't either.
It's great that Samsung is making multiple windows possible, now how about making it work as a phone? The only time my phone has ever crashed was when I was making a call. It's a PHONE. Making a call is it's PRIMARY PURPOSE. If it screws up when sending a text or an e-mail, or while playing a game, that is understandable, but if it is making a call, there is no excuse for that ever failing. My 20 year old bag phone never rebooted when trying to make a call. Neither did my Motorola brick, flip phone, or any of my several Nokia's. But suddenly I get an S2 and it reboots during calls. This morning, I tried 5 times to call into a conference number. Whenever it connected, the screen completely freezes. I am unable to push any button or get back to the number pad screen to put in my code for the conference. Then after about 5 seconds, it reboots. After 5 attempts, I called from my house phone. Surprise! The house phone didn't reboot. It just made the call, just like a cell phone is primarily supposed to do.
I don't care about all the whizbang apps, web surfing, texting, e-mailing, alarm clocks, calendars, phonebooks, etc. If it can't fulfill it's primary purpose of making phone calls, then it is a crap product and should not have been released.
If you are not allowed to question your government then the government has answered your question.
If you don't like the user interface that the handset manufactuer cooked up and puked on your Android phone, just install ADW Launcher on it, and you get a functional as well as speedy.
I did that on my Sony Ericsson Xperia Arc to get rid of Sony's TimeScape.
2bits.com, Inc: Drupal, WordPress, and LAMP performance tuning.
MS-hating aside, multiple window viewing and management on a physically small device like a tablet or phablet is just a bad UI idea, even if the screen resolution is high. Flipping the whole screen sideways between whole-window apps is a better idea.
This gives me the impression of having come from the creative minds of people who think that managing windows on screen is synonymous with using a computer. That is a sadly narrow view, reflecting too much time spent in front of beige boxes.
In the west, demographics suggests that font sizes on both stop signs and computer screens should be getting bigger, not smaller. And all you youngsters out there. Don't gloat. Staring cross-eyed at endless streams of life-alteringly important texts and sexts on phablets will blur your vision sooner than you think.
Where are we going and why are we in a handbasket?
I am seriously starting to dislike Android. When it runs, it is fine BUT if you want to upgrade (coming from a DOS, Unix, Linux and Windows background) FORGET about it. It is gigantic fucking mess where you are totally at the mercy of the manufacturer as to whether your model gets an upgrade. Cyanogenmod isn't an answer either, it is FAR from a generic Android that just "works". If Android was Linux you would have distro's that ONLY ran on ONE model of Dell and then had 1 year after release small niggling bugs like the monitor not yet working...
Now I grew up with Unix, Dos, Windows and Linux. I am no stranger to having to hunt for drivers and have to deal with weird configurations and installing stuff in just the right order. But with ALL the above, you at least have the OPTION to do so.
With Android? No drivers, no configs, no nothing. Either you spend ages learning how to cook a release to tweak it or you just don't. The debug options to are shockingly bad even compared to Windows. It would be a LOT better if there was just a default install you could do and install drivers that Google required each company to make available for install if they want to use Android.
But they didn't and you suddenly realize just how fucking open the Windows platform is by comparison, just how complete Linux is.
I am either going to stick with Nexus devices in the future or hope an alternative emerges because I am NOT going to be stuck with a device that is not going to be updated by Samsung ever again.
You don't have to differentiate with screen/case etc. JUST FUCKING UPDATE YOUR FUCKING DEVICE! That will make you fucking unique in Android land. The first company that manages to release a device that can ALWAYS run the latest Android version will leave ALL the other companies in the dust.
MMO Quests are like orgasms:
You may solo them, I prefer them in a group.
So... customers care more about price then minor feature differences but are willing to pay a premium for Apple products that have minor feature differences...
That makes sense.
Oh and smartphones are hardly a budget market at the moment, if you want a budget phone, you get one for 50 dollars or less without a contract. 500-600 dollars for a smartphone is high-end. And they sell like hotcakes.
MMO Quests are like orgasms:
You may solo them, I prefer them in a group.
Curse my hasty posting, didn't hit preview.
"There is more worth loving than we have strength to love." - Brian Jay Stanley
Is there any potential for them to prevent other android companies from making similar changes to android? My worry here is they patent the modifications and prevent them from showing up in the main branch of android code if someone later on wants to add their own version of the same features to main android.
http://interserver.net/
And remember: unlike Apple, Android device makers, and the wireless carriers who offer Android smartphones to their customers, need ways to differentiate their products.
Actually, what you should be aware of is that Samsung is it. They are the only Android manufacturer making money. The others may want to differentiate, or emulate; but whatever it is isn't working.
It appears the difference is that Cornerstone allows the user to decide which app would be windowed, however MultiWindow requires the developers of the application to support it. Googles complain appears to be arround users mistaking an application that does not support Cornerstone for a crappy application. Which is kind-off fair
Cornerstone - Make it application opt-in.
Wow, I should not post when knackered.
And remember: unlike Apple, Android device makers, and the wireless carriers who offer Android smartphones to their customers, need ways to differentiate their products.
No they fucking well do not.
Only in the USA would this be regarded as a virtue or a requirement. I don't want to have to choose between crippled-version-of-Android-1, crippled-version-of-Android-2, crippled-version-of-Android-3, etc when what I want is a decent device knowing that the system will be the same no matter which device I choose.
The last thing on earth we need is wireless carriers and telcos who bugger around with the OS because they think their ghastly sucky software is sooooo terribly important.
Oh, wait, we already have them...
What if Android would get something so powerful for GUI apps as what pipe is for Unix shell?
I think that's what the "share" button on each application's action bar is for. (Pre-Android 4.0 applications don't have an action bar; instead, they have only an overflow menu.)
It is so funny that sometimes I am watching random Star Trek TNG episodes and they don't ever do any backups.
That you can see. Some operating systems can be configured to back up certain folders automatically in the background, and I'd bet LCARS on their PADDs is configured the same way.
I don't even know can you share content between Modern apps in Windows 8
To "share" in Windows Store applications, you need to open the Charms bar, which is essentially a system-wide auto-hidden toolbar. It's magically delicious!
Does Google Navigation describe your current location as "Hell"?
Only near Pinckney.
The feature is nevertheless something that Android sorely needs if it wants to expand from plain tablets to Win8-style convertibles and laptops.
Unless Google is trying to intentionally segment the market: convertibles and laptops run Chrome OS, and plain tablets run Android.
Am I missing something or isn't this just using Fragments? Possible with ActivityGroups in prior versions as well.
Don't complain about syntax, grammar, or spelling. There is no.hell like input on android.
multiwindow fundamentally breaks the Android CTS
How so? I tried Google multi-window android compatibility test suite and found this article that claims that the only reason CyanogenMod with Cornerstone doesn't pass the CTS is that CyanogenMod isn't bundled with a device.
There are several toolkits for developing Linux apps, and popular ones such as Qt and GTK+ are just an apt-get away. If Android were ported, it could be used as such a toolkit. Let me know when I can sudo apt-get install a toolkit to run Android apps on a major desktop Linux distribution.
While the window does have its uses, I find most of the time I want a single app operating full screen. Additional apps are sometimes useful and I tend to fit them on a second window,but on the whole I find switching between apps using the taskbar is a lot more useful.
Would you want to have to always switch between full-screen windows showing a program's source code and the compiler's error messages, or the source code and the program's output? I don't know about you, but I prefer seeing them side by side.
Needing multiple windows on a tablet or phone means you are using it wrong, or really want to be using a laptop.
I do want to be using a laptop, but they don't make 10" laptops anymore. Only tablets remain in that size range according to a Slashdot story from a month ago.
Agreed, new functionality is progress. If someone doesn't like a particular variant of Android, just don't buy the device that has it.
What's more, multiple windows on Android tablets are absolutely essential. What is this, 1980 again? Google's position is ludicrous for 2013.
What's more, Google's attitude towards Android modifications is especially worrying. Is Android open source or isn't it? If it is then "freedom to modify" is one of the core freedoms, and Google can go screw themselves if they don't like it. Perhaps they should choose a proprietary license ... let's see how far that will get them.
As things stand, they want to have their cake and eat it too. Well that won't fly, Google, sorry. Get with the programme. It's extremely good for the Android ecosystem to see a lot of evolution by 3rd parties, and you're being utterly blinkered.
keeping it simple is the hard part.
A 10" tablet *is* a laptop in a modern form factor. Google's problem is that it's living in the past and wants us to do our work through the keyhole of a single window. Their total preoccupation with app store growth is turning them technically myopic.
It's as if we still lived in pre-X11 times and only had VT consoles, one screen at a time. It's beyond retarded, a total Google fail.
Listen to me carefully. This is important.
A phone is a phone
A PC is a PC
A phone is not a PC
A PC is not a phone
Got it?
Good.
Actually the main usage scenario I see for these multi-window things is fixing the recent tvdpi mess for stone age apps that are more or less designed for fixed resolutions & don't scale properly.
Since those apps expect tiny resolutions, why don't we give them just that? Nexus 7 has enough screen real estate for running 4 of them older apps, all visible concurrently.
I thought by MS-Windows like, they meant it crashed or hung a lot.
the SDK includes an emulator.
The rule of thumb is that emulation uses roughly ten times the CPU power (and thus battery power) compared to native code. I was under the impression that the emulator included with the Android SDK ran Android apps slowly and/or used excessive electric power. This is fine for development on a desktop machine but may be unusably slow or result in an unusably short battery life for production use on, say, a laptop or convertible tablet PC. I was hoping for something that would sit side-by-side with GTK+ and run Dalvik-only and x86-recompiled apps natively, more like Wine.
I prefer seeing them side by side.
No. I'd prefer this to be tiled.
That's what I meant: the side-by-side view that results from the Snap feature in Windows 7 and several Linux window managers or from clicking one taskbar entry, Ctrl+right clicking another, and choosing Tile Vertically in Windows XP. Even on a netbook with a 10" 1024x600 pixel display, I can have an 80-column editor window and an 80-column output window open at once.
Switching between them isn't actually as bad as you seem to think.
I've tried doing various thoughtful tasks with the input on one full-screen application and the output on another full-screen application, or by comparing two documents in two different full-screen applications, and the act of switching between them caused me to lose my train of thought in much the same way as doorway amnesia, as I've mentioned before. It'd be like having a desk that's big enough for only one book, and whenever you want to look at a different book, you need to put away one book and open the other one. If maximization-induced doorway amnesia is a disability, then the use of tiled windows or overlapping windows as needed has been an assistive technology. Consider that in some Star Trek spinoffs, characters were seen using multiple PADD tablets to study multiple documents. Eventually we can look forward to tablets being that cheap, but until then, splitting is probably the best way to handle it.
This was how I worked with Watcom C++.
And I worked differently. I seem to remember that in RHIDE, an old DOS-based IDE for GCC inspired by Borland Turbo C, I could reserve the top two-thirds of the 80x50-character screen for a source code file and the bottom third for compiler diagnostics that I'd tackle one at a time.
You can have a custom API for applications to opt in to your experience (for example a meta-data tag in their manifest), but they must explicitly opt in to any such changes in behavior
So there is enough hope for tiled windows on Android to change my standard netbook vs. tablet spiel. The first step is bugging Google or Douche to create a "flexible screen size" feature that developers can enable through metadata; the second is bugging developers to enable it.
Andy Dodd wrote:
This is what Samsung did - except instead of by using a custom API for apps to opt-in, Samsung hardcoded a whitelist into the framework.
So how does Samsung expect developers to request addition of their applications to the tiled window whitelist?