CoreCodec Community Forum • View topic

BetaBoy · Joined: 06 Feb 2007, 10:06 **Posts:** 2085

We have been asked if we plan to release a version of CorePlayer for Android. The short answer is yes (we have been researching/working in it for over a year now) but there are major hurdles in the current SDK and NDK.

- Native space
- Audio input (is really a hack atm in the SDK and not for production)
- Video rendering
- NDK (too many issues to list)

While Android works great for many apps.... its A/V system designed by PacketVideo is far from robust enough to add onto no less use. David Turner one of the lead Android Devs even noted last week that there are major changes coming this way with each SDK/NDK release as it relates to multimedia, quoting: "(and believe me the graphics and media frameworks are under extensive changes at the moment, and will keep doing so for quite a number of upcoming releases)".

Our goal is once the dev kits are ready to use for stable Audio input and a new method for Video rendering, is to basically replace the entire multimedia stack with CorePlayer. Naturally for us the diff is that we want to run in the 'native space' as much as possible, so we hope with the upcoming milestones it helps us and other developers to do what we need to make that happen.

In the meantime we have been working on the native Dalvik components (UI, system access, network access, installer) and will adapt those as each SDK/NDK milestone is released.

BetaBoy · Joined: 06 Feb 2007, 10:06 **Posts:** 2085

Nice, 4 PM's in 5 minutes after this was posted ;-)

So to clarify.... sure we can easily break off from the NDK/SDK NOW and create a one off solution to make CorePlayer 'just work' (technically it does work now in full native space), and there are plenty of third party hardware/multimedia providers doing that right now with Android (look at Creative's efforts with http://www.ziilabs.com/ ). But that's not the point of 'playing nice' and compliant with the SDK/NDK for mobile operators.

In the end we want CorePlayer to be 100% NDK/SDK compliant for two reasons:
- Consumer downloads that work against any device (Android Store) and for any mobile provider
- OEM expandability. In matching our consumer goal this will easily allow third parties to use CorePlayer as a compliant drop in solution without the need to one off a separate SDK.

BetaBoy · Joined: 06 Feb 2007, 10:06 **Posts:** 2085

I would also like to clarify further as I have received a few more emails about this.

We _ARE_ actively developing for Android RIGHT NOW. The issue is to what level we code and the work are doing will be a wash because the next/future releases of the NDK/SDK has changed. So we are mindful of this.

whatznext28 · **Posted:** 22 Sep 2009, 15:38

Android 1.6 SDK, Release 1 is available (http://developer.android.com/sdk/1.6_r1/index.html). Would this mean that we can expect CorePlayer for Android with the next update? I'm asking because the media playing function of Android currently doesn't handle any relevant media I have in my collection. If this is coming out soon, I'd be willing to pay immediately. Even if it had limited functions besides playback, I'd definitely purchase this now & wait for an update when it's available.

BetaBoy · Joined: 06 Feb 2007, 10:06 **Posts:** 2085

Pls no double posting.... its not just about the SDK but as stated the NDK as well. Without a new NDK being available at the same time we are limited to comment further.

pk_fms · **Posted:** 29 Sep 2009, 17:02

BetaBoy wrote:

Pls no double posting.... its not just about the SDK but as stated the NDK as well. Without a new NDK being available at the same time we are limited to comment further.

The android 1.6 donut NDK is now released!

I hope this helps you and that the Android version can now be finished. http://developer.android.com/sdk/ndk/1.6_r1/index.html

BetaBoy · Joined: 06 Feb 2007, 10:06 **Posts:** 2085

The 1.6 NDK is a good start but still lacks an 'open' OPENCORE. In other words its still closed from native space access to allow for Audio input or video rendering.

unfrostedpoptart · Joined: 19 Jun 2008, 16:39 **Posts:** 7

I'm a long-time PalmOS/CorePlayer (Palm Centro) user looking to move to Android (Moto Droid!).

I'd like to have CorePlayer, especially to support .flac files. You've said that Android isn't great for audio/video, but I've just read about some PMPs coming out that are Android based. How do they do it?

Creative Zii Egg: http://gizmodo.com/5326548/creative-zii ... s+on-debut

Archos 9 - http://www.archos.com/products/nb/archo ... dj&lang=en

I know the Droid/Sholes will be running Android 2.0. Does this new version give you the features you need to port CorePlayer?

Thanks,

David

BetaBoy · Joined: 06 Feb 2007, 10:06 **Posts:** 2085

The use proprietary code to make it work with the hardware. That's cake walk stuff since the code is open source.

unfrostedpoptart · Joined: 19 Jun 2008, 16:39 **Posts:** 7

BetaBoy wrote:

The use proprietary code to make it work with the hardware. That's cake walk stuff since the code open source.

Thanks for the quick reply! So, does anything in 2.0 help you guys?

BetaBoy · Joined: 06 Feb 2007, 10:06 **Posts:** 2085

Sure... each release of the NDK and SDK gets us closer... the Android team needs time to add native code support to run as 'native' as possible. Java and multimedia do not really mix well.... and hence why OpenCore sucks so bad. Its ok if you are looking to do the basics.... anything more then that and your SOL.

BetaBoy · Joined: 06 Feb 2007, 10:06 **Posts:** 2085

One thing I should note now is that in the latest Android Milestone has now added Alsa Audio input support! So check off one more thing that needed to be done... now the biggest obstacles seems to be the Video renderer and more NDK access features.

unfrostedpoptart · Joined: 19 Jun 2008, 16:39 **Posts:** 7

Thanks again for the info. I use your program almost totally for music, so if you're still blocked on video, I'd be happy with an audio-only beta

BetaBoy · Joined: 06 Feb 2007, 10:06 **Posts:** 2085

In 2.0 we have pushed for more of an Audio friendly UI.... the updated 'Now Playing' screen will reflect this... and by 2.1 we will have PictureFlow integrated.

Wishmaster89 · Joined: 14 Sep 2008, 02:38 **Posts:** 156 **Device:** i900

BetaBoy wrote:

In 2.0 we have pushed for more of an Audio friendly UI.... the updated 'Now Playing' screen will reflect this... and by 2.1 we will have PictureFlow integrated.

Will you modify PictureFlow to better suit your "vision" and your CoreUI 2.0 or will it be standard PictureFlow version?

Transitions, transparencies and reflections could be too demanding for CPU only processing so I think that adding openGL acceleration would be a good thing. All major platforms support openGL so it wouldn't mean rewriting for every platform.

BetaBoy · Joined: 06 Feb 2007, 10:06 **Posts:** 2085

PictureFlow is good... for example HTC uses it in their main WM UI for many of the UI elements. Its hard to say about performance yet.. as we might also be able to duplicate it in CoreLua as well.

Wishmaster89 · Joined: 14 Sep 2008, 02:38 **Posts:** 156 **Device:** i900

BetaBoy wrote:

PictureFlow is good... for example HTC uses it in their main WM UI for many of the UI elements. Its hard to say about performance yet.. as we might also be able to duplicate it in CoreLua as well.

I know that they're using it in the newest version of manilla for picture browsing and in CoverFlo style audio player and it is very smooth but it is probably using openGL acceleration cause on older devices like Touch HD it is not smooth.
That is why I'm worried that it may be too much for current devices using CPU only. Slide2Play is a free player resembling iPhone's ipod player and it is using PictureFlow too and without 3D acceleration it wasn't that smooth, only after the author added openGL support it became smooth.
Probably devices based on cortex CPU wouldn't have problem with it but not all devices are based on ARM cortex.

BetaBoy · Joined: 06 Feb 2007, 10:06 **Posts:** 2085

2.0 supports ARM Cortex / NEON.... the question is if QA is done in time for the initial 2.0 launch.

cmd · **Posted:** 26 Oct 2009, 19:16

Hi!

I am about to order a new phone and right now I am either going to buy the HTC HD2 or the SE X3, which I heard today should be released next month.

I must say that Coreplayer working on Android is a big deal, if it isnt going to happen in the near future I probably will go for WinMo 6.5 and use my currnet Coreplayer license on it.

So sorry if I am being an annoying customer but how is the plan going for CP on Android, are we talking weeks, months or maybe next year before I can buy it?

// Halling

640k · **Posted:** 10 Nov 2009, 11:43

BetaBoy wrote:

2.0 supports ARM Cortex / NEON.... the question is if QA is done in time for the initial 2.0 launch.

in for updates. willing to be guinea pig if needed (hint, hint, wink, wink).

cmd · **Posted:** 12 Nov 2009, 07:09

Yep I am in on the same track, I have pre-ordered a HTC HD2 now, also been reading good things on different sites where they are declaring the HD2 UI better then the Iphone one which I like to hear.

I was afraid of the size of the HD2 at first but reviews have agreed on that it isnt a problem since it's so thin, and really not bigger that HTC touch HD or Iphone if you count the whole phone.

Quotes from gsmarena:
"HD2 HTC are the first manufacturer to outdo almost everything you'd find on the Apple's device."
"..the HD2 is better, faster and stronger than the current golden standard of UI - the Apple iPhone."

BetaBoy · Joined: 06 Feb 2007, 10:06 **Posts:** 2085

All..... I wanted to post a follow-up to clear any confusion.

The key to what we feel will be our success is 'native' code compliance (ie compliant against both thr NDK and SDK). This will maximize our ability to work on as many devices as possible.

Writing 'one off' code is not the way to go... and we can do that with our eyes closed. What is happening is that with each Official Android NDK/SDK release now, is that you are seeing the abilities added that we have been asking for. This code changes are taking the required steps towards our longer term goal in keeping CorePlayer in as much of the native space as possible.

We are also taking the time now in CorePlayer 2.0 to add more hooks that will be needed for the port.

640k · **Posted:** 14 Nov 2009, 21:28

So what does that mean in terms of availability for current androids and 2.0?

iampedro · Joined: 15 May 2008, 04:37 **Posts:** 3

It is great to hear that you are developing for the Android since I have just switch from HTC 6800 to the Droid and I am liking the difference and stability. I currently own Core Player for Windows please make a upgrade discount for people switching to the Android OS from Windows Mobile.

http://developer.android.com/sdk/android-2.0.html

piro · **Posted:** 01 Dec 2009, 08:26

I thought the policy was that you had to buy it again if you changed platform?

I have no problem paying full price for CorePlayer on Android if it performs as I hope, just to register my interest