Database Users

Poll--Better Cornerstone build

Just wanted your opinions on which dev has the best Onskreen Cornerstone build right now. I have installed both CM9 and Eos i personally prefer Eos' build they are doing a great job with the dev so far. Great job on both roms though. And are there any other roms with OSCS built in these are the only two im aware of.
I can deal with the minor bugs I really couldn't see my TF without OSCS now im spoiled

I'd personally love a completely stock with cornerstone and stock buttons. I like the Asus quick panel and soundset
Sent from my Nexus S 4G using xda premium

I like the Team EOS better.
After using Cornerstone for a day, you cannot imagine life without it. I know the feeling.

jinsoku3g said:
I'd personally love a completely stock with cornerstone and stock buttons. I like the Asus quick panel and soundset
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
This is pretty much what I'm holding out for, a nice stock rom with cornerstone.

st0nedpenguin said:
This is pretty much what I'm holding out for, a nice stock rom with cornerstone.
Click to expand...
Click to collapse
Which can't happen right now because we ain't got no source code yet.

i flashed back to ARHD to many bugs for me to use as daily (especially now with the dock) waiting for a good solid CS build screen swapping would be cool if they release the source for that (not likely soon)

Here is some important information from the CEO of Onskreen directly to Diane Hackborn of Google, I've not read this on this site, I was directed here after an email with consumer relations with Onskreen while asking if the window-swappng option was going to be re-implemented..their reply was basically "no, and here is why; read this comment" so here is what they said..
(my emphasis)
hansmeet sethi - I am the CEO of Onskreen and felt it was about time we weighed in on the public discussion. To start off with, we have been impressed by the level of discussion on this thread on the topic of compatibility. We take it very seriously and are glad that the rest of the community do as well.
+Dianne Hackborn - Thanks for sharing specific concerns and we can appreciate their gravity and the need for a dialogue. However, outside of the implementation details perhaps some background will help. Onskreen saw an obvious need in the UX of Android on larger screen devices (that is our business after all), and we worked to address that with Cornerstone. During the process, we have invested heavily to respect Android's intentions and compatibility of the Frameworks you helped build. When you get a chance to review the code, you will see that we went out of our way to not introduce app requirements, leverage the patterns already used, and treat running Applications in a way that they are oblivious to the Cornerstone experience. We rejected many features along the way to optimize for compatibility. The result is a product that we are proud of, respects the Android project, that the user and mod communities are excited about, and OEMs love. And frankly, once you use a tablet with multi-tasking there is no going back. We are the first to admit the product is not perfect, but was at a point where we felt comfortable sharing with the community to use, help improve and polish. We see the goal of this conversation as a way to come to an agreement on some of the aspects of Compatibility and deliver multi-tasking on Android.
Now - a few of your concerns:
- Orientation - Good points, and we spent a ton of time thinking through the UX here. Cornerstone adheres to the desired orientation of the Application running in the Main Panel (and rotation of the device). Cornerstone restricts the user from opening an app that won't support all orientations in the Cornerstone panel, so there is not a case where an app running there is forced into an orientation the app developer did not intend to run in (try opening Angry Birds in the Cornerstone and you will see this). There is more here but I will leave it at that for the time being.
- Screen size changes - You point out the complexity of a changing screen size on an app. We agree and this is the reason that swapping panels (applications moving from the main area to the cornerstone or vice versa) was removed from the product. Apps at this point just aren't enforced to consider this, so Cornerstone imposing it on them would be incompatible and we don't (although we all sorely miss the feature). One area we are still considering is the Config of the main app. Logically this should change when the user minimizes/maximizes the Cornerstone, however the implementation is not doing that because of compatibility issues it would introduce. To be fully compliant we are aware that we will may have to remove the ability to minimize/maximize the Cornerstone (we will miss that feature too). Perhaps you have some suggestions here?
- ProcessRecord/ActivityThread Configurations - As you mentioned, while the ActivityStack was refactored out during your exploration, other inherent dependencies on a static Configuration do still exist. Some interesting features could be enabled by expanding this, but we didn't make these changes so that the Cornerstone codebase could more easily be used in customized Android trees of OEMs and others, as well as perhaps in upcoming Android releases.
- CDD Compliance - We take this one very seriously and you bring up good points. However, our intention is that each area (the main panel and cornerstone panels) be designed as CDD compliant sizes. That is not fully the case in the .85 release that was open sourced. As we made the switch to v4.0.3_r1 and the 1280x800 reference device (Xoom), we haven't made all these changes yet. It may require that some of the panels in certain orientations run in a pseudo compatibility mode similar to how the Android OS supports legacy apps already so that their config is CDD compliant and the UX is optimized.
- CTS - One test in CTS calls for any Activity that doesn't have the focus to be moved to the paused state. This is obviously not the case in Cornerstone as Activities do stay resumed when not having the focus and still are visible on the screen. Google could ding Cornerstone for that and in truth they would be technically correct. However this would be silly considering the nature of the test when applied to a real multi-tasked environment. That is not our call however.
In short, we think about the same problems you do and we believe in the product as well as maintaining the integrity of Android applications and devices. You of all people can appreciate the complexity in working with the Android framework in the way we have to get Cornerstone built, and to call it a fork is doing the design and engineering effort that went into it a disservice. We see the point of AOSP and contributions like Cornerstone to create a dialogue, come to agreement and add great features to the platform. To that end, we are more than happy to continue this conversation. Some of us are in the bay area and happy to drop by Google if you prefer.
hansmeet.
Click to expand...
Click to collapse

thats pretty cool but i will miss having the features im sure the community will implement our own twist on it though. to bad for the screen swapping though .
on a different note CM9 with cornerstone is moving along quite well a lot more stable ROM can i vote again lol

Cornerstone is just a placeholder for me until Windows 8 is released for tablets.
Definitely switching to Windows 8 unless Google adds to Android a comparable multitasking capability.

Just stock, I like stock ICS on TF101 (after reboot and pc connection issue removed...) and don't see any pro's in any other ROM for me...

Pretty much all of the concessions that they have or are discussing making to cornerstone are quickly removing the reason for having it at all. There are plenty of apps that already are not compatible with many devices and resolutions. Crippling a feature because you "can't" create new app requirements is silly. This is the area where google(and cornerstone) have the potential to destroy apple. As these devices get faster and bigger, you can't stick with the one app at a time paradigm.
I understand google is trying to remove the "fragmentation" but your OS can't evolve if that outweighs everything else.

gottahavit said:
Pretty much all of the concessions that they have or are discussing making to cornerstone are quickly removing the reason for having it at all. There are plenty of apps that already are not compatible with many devices and resolutions. Crippling a feature because you "can't" create new app requirements is silly. This is the area where google(and cornerstone) have the potential to destroy apple. As these devices get faster and bigger, you can't stick with the one app at a time paradigm.
I understand google is trying to remove the "fragmentation" but your OS can't evolve if that outweighs everything else.
Click to expand...
Click to collapse
Google will add better multitasking to Android. They have to or they will lose to Windows 8.
Cornerstone is just not Google's answer to multitasking on Android. I bet Google has something better.

horndroid said:
Google will add better multitasking to Android. They have to or they will lose to Windows 8.
Cornerstone is just not Google's answer to multitasking on Android. I bet Google has something better.
Click to expand...
Click to collapse
The problem with windows 8 is that a windows tablet will always cost 100 dollars more than the same android tablet. Add to that the fact that you'll have to re-buy all your apps for ARM or Metro and they have a tough battle ahead in the consumer market.
Personally I Find Metro totally annoying on my 17" laptop, I think Microsoft is having an identity crisis with windows 8. The last thing I want on my laptop is forced full screen apps. Honestly Metro is a little to Android(ish) for what I would want on a tablet once they get a little more powerful and have better rez.
EDIT: I should qualify this with the fact that I am a die hard windows fan, I LOVE windows 7, prefer coding for windows over any other OS EVER, and absolutely hate MAC OS.

gottahavit said:
The problem with windows 8 is that a windows tablet will always cost 100 dollars more than the same android tablet. Add to that the fact that you'll have to re-buy all your apps for ARM or Metro and they have a tough battle ahead in the consumer market.
Personally I Find Metro totally annoying on my 17" laptop, I think Microsoft is having an identity crisis with windows 8. The last thing I want on my laptop is forced full screen apps. Honestly Metro is a little to Android(ish) for what I would want on a tablet once they get a little more powerful and have better rez.
EDIT: I should qualify this with the fact that I am a die hard windows fan, I LOVE windows 7, prefer coding for windows over any other OS EVER, and absolutely hate MAC OS.
Click to expand...
Click to collapse
I don't care. All that matters is that Windows 8 will motivate Google to add some real multitasking capability to its Android OS. We all know how competitive Google is. They will do it, and it won't be Cornerstone. It will be something better.

horndroid said:
I don't care. All that matters is that Windows 8 will motivate Google to add some real multitasking capability to its Android OS. We all know how competitive Google is. They will do it, and it won't be Cornerstone. It will be something better.
Click to expand...
Click to collapse
Kinda, my point. have you used Windows 8 Multitasking? it looks too much like Honeycomb except they keep apps actually running. This is of course Metro, native apps are still good old windows. This isn't Microsoft putting out something for google to steal or envy, it's Microsoft going "OHHH everybody love android and IOS, they must all want "one app at a time" style OS.

Android 5.0 Key Lime Pie Release Date, News And Rumours

Android 5.0 release date
Google has announced that its next developer conference - Google IO - will take place from May 15 to May 17 2013, a month earlier than 2012's June dates. Given that Google announced Android 4.1 Jelly Bean at 2012's IO conference, it's not unreasonable to expect to see Android 5.0 at this year's event On 31 January, a Google IO showing of Android 5.0 looked more likely when screengrabs of a Qualcomm roadmap were leaked, showing Android 5.0 as breaking cover between April and June 2013.
Android 5.0 phones
Rumours of a new Nexus handset started trickling in during the third quarter of 2012, as we reported on 1 October 2012. There was speculation that this phone would be sporting Key Lime Pie, but sources who spoke to AndroidAndMe correctly claimed that the handset, which turned out to be the Google Nexus 4 would be running Android Jelly Bean.
While the Nexus 4 didn't appear with a helping of Key Lime Pie, speculation that we reported on 21 January 2013 suggests that the Motorola X Phone is the Android 5.0-toting handset that will be revealed at Google IO. According to a post on the DroidForums website, the phone will also feature a virtually bezel-free, edge-to-edge, 5-inch display.
The same leaked Qualcomm documents cited above also made mention of a two new Snapdragon devices, one of which will be, unsurprisingly, a new Nexus phone.
Android 5.0 features
For 24 hours, it seemed as though the first kinda, sorta confirmed feature for Android 5.0 was a Google Now widget, which briefly appeared in a screenshot on the company's support forum before being taken down. As it was so hurriedly pulled, many people assumed it was slated for the big five-o and accidentally revealed early.
As it happened, the following day, on 13 February 2013, the Google Now widget rolled out to Jelly Bean.
So while we wait on Key Lime Pie features to be revealed and scour the web for more Android 5.0 news, TechRadar writer Gary Cutlack has been thinking about what we want to see in Android 5.0 Key Lime Pie. Hopefully the new mobile OS will feature some of these things...
Performance Profiles
It's bit of a fuss managing your mobile before bed time. Switching off the sound, turning off data, activating airplane mode and so on, so what Android 5.0 really needs is a simple way of managing performance, and therefore power use, automatically.
We've been given a taste of this with Blocking Mode in Samsung's Jelly Bean update on the Samsung Galaxy S3 and the Note 2 but we'd like to see the functionality expanded.
Something like a Gaming mode for max power delivery, an Overnight low-power state for slumbering on minimal power and maybe a Reading mode for no bothersome data connections and a super-low backlight.
Some hardware makers put their own little automated tools in, such as the excellent Smart Actions found within Motorola's RAZR interface, but it'd be great to see Google give us a simple way to manage states.
Another little power strip style widget for phone performance profiles would be an easy way to do it.
Better multiple device support
Google already does quite a good job of supporting serious Android nerds who own several phones and tablets, but there are some holes in its coverage that are rather frustrating.
Take the Videos app which manages your film downloads through the Play Store. Start watching a film on one Android device and you're limited to resuming your film session on that same unit, making it impossible to switch from phone to tablet mid-film.
You can switch between phone and web site players to resume watching, but surely Google ought to understand its fans often have a couple of phones and tabs on the go and fix this for Android Key Lime Pie?
Enhanced social network support
Android doesn't really do much for social network users out of the box, with most of the fancy social widgets and features coming from the hardware makers through their own custom skins.
Sony integrates Facebook brilliantly in its phones, and even LG makes a great social network aggregator widget that incorporates Facebook and Twitter - so why are there no cool aggregator apps as part of the standard Android setup?
Yes, Google does a great job of pushing Google+, but, no offence, there are many other more widely used networks that ought to be a little better "baked in" to Android.
Line-drawing keyboard options
Another area where the manufacturers have taken a big leap ahead of Google is in integrating clever alternate text entry options in their keyboards. HTC and Sony both offer their own takes on the Swype style of line-drawing text input, which is a nice option to have for getting your words onto a telephone. Get it into Android 5.0 and give us the choice.
A video chat app
How odd is it that Google's put a front-facing camera on the Nexus 7 and most hardware manufacturers do the same on their phones and tablets, yet most ship without any form of common video chat app?
You have to download Skype and hope it works, or find some other downloadable app solution. Why isn't there a Google Live See My Face Chat app of some sort as part of Android? Is it because we're too ugly? Is that what you're saying, Google?
Multi-select in the contacts
The Android contacts section is pretty useful, but it could be managed a little better. What if you have the idea of emailing or texting a handful of your friends? The way that's currently done is by emailing one, then adding the rest individually. Some sort of checkbox system that let users scroll through names and create a mailing list on the fly through the contacts listing in Android Key Lime Pie would make this much easier.
Cross-device SMS sync
If you're a constant SIM swapper with more than one phone on the go, chances are you've lost track of your text messages at some point. Google stores these on the phone rather than the SIM card, so it'd be nice if our texts could be either backed up to the SIM, the SD card, or beamed up to the magical invisible cloud of data, for easy and consistent access across multiple devices.
A "Never Update" option
This would annoy developers so is unlikely to happen, but it'd be nice if we could refuse app updates permanently in Android 5.0, just in case we'd rather stick with a current version of a tool than be forced to upgrade.
Sure, you can set apps to manual update and then just ignore the update prompt forever, but it'd be nice to know we can keep a favoured version of an app without accidentally updating it. Some of us are still using the beta Times app, for example, which has given free access for a year.
App preview/freebie codes
Something Apple's been doing for ages and ages is using a promo code system to distribute free or review versions of apps. It even makes doing little competitions to drum up publicity for apps much easier, so why's there no similar scheme for Android?
It might encourage developers to stop going down the ad-covered/freemium route if they could charge for an app but still give it away to friends and fans through a promo code system.
Final whinges and requests...
It's be nice to be able to sort the Settings screen by alphabetical order, too, or by most commonly used or personal preference, as Android's so packed with a huge list of options these days it's a big old list to scroll through and pick out what you need.
Plus could we have a percentage count for the battery in the Notifications bar for Android 5.0? Just so we know a bit more info than the vague emptying battery icon.
(Source)

Okay I wanted to drop this in about video chat. You say that Google doesn't have one right? Of I remember correctly Google talk has video.
Sent from my PC36100 using xda app-developers app

jlmancuso said:
Okay I wanted to drop this in about video chat. You say that Google doesn't have one right? Of I remember correctly Google talk has video.
Sent from my PC36100 using xda app-developers app
Click to expand...
Click to collapse
This one is built in,you dont have to look for it and install it from 3rd party.

Diablo67 said:
This one is built in,you dont have to look for it and install it from 3rd party.
Click to expand...
Click to collapse
Google talk has built in video chat, you don't have to install anything its preloaded on every android phone for as long as I can remember.
I like to break stuff!

-EViL-KoNCEPTz- said:
Google talk has built in video chat, you don't have to install anything its preloaded on every android phone for as long as I can remember.
I like to break stuff!
Click to expand...
Click to collapse
Most of the gapps i ever installed didnt,but yes on a sense rom you can find it and maybe an official ICS or JB that is meant for a certain phone.So i should have reworded that.You are correct though.

Ability to remove skin soon to be unveiled from Google?

Hello
An interesting article I read today with regards to the skins OEM put on android devices (touchwiz) that leads to fragmentation.
Interesting quote from the article,
"I believe this Android update underscores Google’s new vision for OEMs has hardware producers only! Android 4.4 is a trojan horse of unification - it will give Google the tools it needs to completely wipe a skin from a device with a simple download from the Play Store."
If this turns out to be true it can have a major impact on the Galaxy Note products due to it being so reliant on touchwiz. Also I do not know how deeply integrated touchwiz is on Android so I guess time will tell.
http://techtainian.com/news/2013/10...l-reclaim-android-and-unify-holo-with-kennedy

Great article. Thanks for posting the link. I hate touchwizz and love simple vanilla android which you get on the nexus devices. Android needs to be simple to use and I find using touchwizz requires a another learning curve and it just irritates me. I think manufactures should use stock android and then install custom launchers and apps. Commercially google wants to retain the rains of android which will also be a business decision. I can see the advantages for Joe public who could just pick up any android device and know it works like any other device. I want the choice to pick either without having to root a device and install custom firmware.

andyzarins said:
Great article. Thanks for posting the link. I hate touchwizz and love simple vanilla android which you get on the nexus devices. Android needs to be simple to use and I find using touchwizz requires a another learning curve and it just irritates me.
Click to expand...
Click to collapse
Vanilla is good but then you don't get S Pen and multi window. And nexus devices come without SD Support.

ddavtian said:
Vanilla is good but then you don't get S Pen and multi window. And nexus devices come without SD Support.
Click to expand...
Click to collapse
These two things do not apply to one another whatsoever. Samsung could put S-Pen, SD, and multi-window support on their devices without the UI overhaul. The two are not in any way connected.

It makes perfect sense for them to put stock android in their tablets and make the S-Note, multi window etc available via the playstore.
Honestly, I don't know about Samsung's and Google relationship as it stands today but if Google does makes an app that allows the user to remove OEM skins than it might be the start of the downfall between the two companies.
On a side note there are rumours that the new Nexus 10 is Asus built not Samsung.

Not a rumour. Asus is building the new nexus 10. One the fence about buying the new 10.1 or waiting for the new nexus.

Android Wear in AOSP/OpenSource?

Hello,
I just wanted to know if the Android Wear Project is also getting open source, cause we have so many Smartwatches that are allready based on Android (Gear, Moto Actv,...) so porting Android Wear over to them is not the hardest thing.
If you find something, please let me know!
Regards

Yes, IMO a VERY important question that hasn't been answered yet.
I would be concerned that Google felt it was TOO open with Android proper and tried to restrict Wear even more.
If the current preview emulator is a good indication, then Wear is just another variant of Android. Many normal apps can run on it right now, though with issues. I tested my own app and it more or less worked, with a squished UI.
So I think a LOT of the Wear code is effectively already IN AOSP already.
But will Google release enough Wear specific code for custom ROMs to be built ? I very much hope so.

i
That will be gr8
custom launchers
like wht devs did on galaxy gear (they installed nova launcher on it)
or using custom keyboard like minuum beside voice input.
system dump;
source

Praying for a port of Android Wear for Galaxy Gear!!!!

traxxasislife said:
Praying for a port of Android Wear for Galaxy Gear!!!!
Click to expand...
Click to collapse
Prayer is the only remote hope you have, I think.
There are reasons Gears are going cheap now.
You really think Samsung won't take every opportunity to sell you new wearables, EVERY year at least ?
EVERY few months, new, "in fashion" designs.
Every year, moar cores, LOL.
We'll be overclocking on both wrists to keep our hands warm in winter...

mikereidis said:
We'll be overclocking on both wrists to keep our hands warm in winter...
Click to expand...
Click to collapse
That's genius! Perfect winter accessory:silly:

Android wear without wear
Couldn't we just built a custom android wear version which is based on one of the regular open source android versions? Like e.g. android kitkat with a special launcher and a way to display notifications similar to android wear

Finkes said:
Couldn't we just built a custom android wear version which is based on one of the regular open source android versions? Like e.g. android kitkat with a special launcher and a way to display notifications similar to android wear
Click to expand...
Click to collapse
IMO they're going to need to for it to be usable by the pro-android anti-google crowd.
I have the LG G Watch and I have it unlocked with TWRP and a custom ROM on it. However it still can't connect to my phone unless I have a Google account on it, so I can use the Play Store to download the Android Wear app and connect it via Bluetooth.
So I figured "fine whatever, I'll just put it in airplane mode and use it as a regular watch until someone comes up with an Open Source solution" right?
Wrong, turns out I CAN'T EVEN CHANGE THE TIME! It updates that from the phone which updates from the time servers on the net. Good thing I have an older phone that I can stick Google on to work with it I guess.
All I want is my texts on my watch without having to get spied upon by the almighty Google.
Also, they should call it AWOSP because it sounds awesome.

[Question] Multi Window status?

As per the title, has development ceased on that style of multi-window? Is the 'Floating Window' similar? With the Nexus 6 rumored to have a 5.9" screen I was hoping that a custom ROM would have something similar to the LG G3 Dual Windows which is great.

parker09 said:
As per the title, has development ceased on that style of multi-window? Is the 'Floating Window' similar? With the Nexus 6 rumored to have a 5.9" screen I was hoping that a custom ROM would have something similar to the LG G3 Dual Windows which is great.
Click to expand...
Click to collapse
It's been on hold for quite some time. It was about 90% working, but had some final issues that needed work. After further review, xplodwild actually wants to completely rewrite the feature again after reading up on some interesting infrastructure in Android we didn't know about before. (I don't have the link on this machine).
At this point it might not get finalized until L - since L is going to change a LOT of different things.

Entropy512 said:
It's been on hold for quite some time. It was about 90% working, but had some final issues that needed work. After further review, xplodwild actually wants to completely rewrite the feature again after reading up on some interesting infrastructure in Android we didn't know about before. (I don't have the link on this machine).
At this point it might not get finalized until L - since L is going to change a LOT of different things.
Click to expand...
Click to collapse
Thanks for the fast response, glad it didn't get abandoned.

parker09 said:
Thanks for the fast response, glad it didn't get abandoned.
Click to expand...
Click to collapse
Yeah it's something I've wanted to finish up but didn't have time. The last issues with the patch proved significantly more difficult/time-consuming to solve than expected. Namely:
1) Layout in some apps is totally broken. G+ is the most obvious example of this. As a result we're probably going to have to implement a whitelist similar to Samsung's multiwindow. (Apps won't work unless whitelisted by the frameworks or the app declares itself as compatible in the manifest. We'll likely use the same manifest declarations Samsung does, e.g. assume any app compatible with Samsung's multiwindow should be compatible with ours.
2) Re-layout of apps after a rotation was really flaky. This is the #1 reason plodey wants to do a rewrite. He's been buried in a special project for a while, he was supposed to be wrapping up in September but that schedule seems to have slipped.