Database Users

Calling HTC Linux Geeks + Android Fans: MSM7200 Compatible Kernel Released!

Ok, there is plenty of speculation on Android and can we run it on our HTC devices, etc. I have started this new thread dedicated to the MSM7K Kernel release, and what it will take to get this running on our phones.
I would like this thread to become a resource, rather than just general theorizing. For example: "I know we need driver X to run Y on HTC device Foo." What I am not looking for: "Android is so l33t, plez tell me how to run on my Zaurus kthx". The difference is that the first example is constructive, and adds to the discussion.
The signal to noise ratio on the Android gGroup is terrible, and mostly consists of wild theorizing, self-promotion, and arguing. I have a feeling it will improve, but for now I'd like to discuss this subject away from all the SuperKoolNewAndroidForum.com forums.
My Goals for this Thread:
Establish what is known to work, and what the kernel is sorely lacking.
a) I know we have booted Linux on HTC devices, has it been done on the most current devices? (please link to thread/proof)
b) What are the main major roadblocks preventing Linux from being run on more HTC devices? (Obscure hardware design, bricking phone)
Compile a list of needed and helpful software for loading Android: bootloaders, useful Linux tools, filesystem images
Provide continual updates with photos/logs as we (hopefully) make progress
My bet is that the current 'gPhone' in the videos is an HTC device not unlike yours or mine. [link to my blog] IMHO, the hype over 'When will the first gPhone be released' is irrelevant, as Google has been working closely with HTC and Qualcomm for a long time -- and the specs for Android are so low, Google clearly expects to be able to run Android on existing hardware, without needing new hardware technology.
Of course, the tools and software we need are all in existence already, someone at Google is doing a good job of keeping their mouth shut. Therefore this is not an impossible task, just difficult, but I know you xda-hackers like a challenge! So, Let's go!!
Charles
FYI: I am aware XDA was founded with the Xanadux project, so this should be the perfect place to hack us a gPhone. I've also browsed threads, read the Wiki, studied up on the Hermes Linux project -- but things seem to have died since Feb 07, I'm hoping this latest development with Android will spark interest again, and we will be able to run Linux on our current, most powerful devices. I could make educated guesses about the state of the Xanadux project, but I'd rather hear it from XDA devs themselves who are most familiar.

Reserved for knowledge & files
Ok, I'll start:
Android.com *Now redirects (finally) to OpenHandsetAlliance.com
Download Android SDK
Official Android Dev gGroup
Here's what I know:
Announcement of the Kernel on the ARM Linux Mailing List
GIT Repository
gGroup for MSM7K Kernel Issues
[credit to Brian Swetland, Linux Kernel Lead, Android Project]
gGroups thread: Compiling C Binaries for Android
Filesystem dump from Android running on SDK Emulator: gGroups thread discussion | Benno's blog post with files

reserved for Android installation instructions
[ reserved ] Hopefully we will get this far

polyrhythmic said:
I've also browsed threads, read the Wiki, studied up on the Hermes Linux project -- but things seem to have died since Feb 07
Click to expand...
Click to collapse
If you are interested in the facts, and not some google-related hype, please
check this one
http://www.handhelds.org/moin/moin.cgi/UniversalStatus

My Android News blog (now on Russian language)
English version cooming soon.
http://android.my1.ru
Now it is under construction

Much thanks cr2!
n00bs are everywhere I'm trying not to be one of them.
I have been doing a lot of reading, things have been quiet on the Kaiser front but that soon will change. I just read the #htc-linux logs from the past few days, see you there after work!
Charles
(sent from das Kaiser)

WoW!
Is this going to be like getting Linux OS on my Trinity? I like the browser but a lot of the apps in teh demo vid rely too much on 3G. Data rates in the UK are prohibitive at the moment so I stick with WIFI

welcome to join AndroidPort group
hello:
you are welcome to join the AndroidPort group, where the
idea is to make Linux and Android work on a real or virtual
hardware phone platform.
looks like you are quite advanced in this area. we would
welcome your presence and expert knowledge.
have a look at our website. you will find a lot of
information for this subject in 1 place.
AndroidPort
http://groups.google.com/group/androidport
Aaron

Cool initiative, will write about it in my next News collection.

polyrhythmic said:
Ok, there is plenty of speculation on Android and can we run it on our HTC devices, etc. I have started this new thread dedicated to the MSM7K Kernel release, and what it will take to get this running on our phones.
I would like this thread to become a resource, rather than just general theorizing. For example: "I know we need driver X to run Y on HTC device Foo." What I am not looking for: "Android is so l33t, plez tell me how to run on my Zaurus kthx". The difference is that the first example is constructive, and adds to the discussion.
The signal to noise ratio on the Android gGroup is terrible, and mostly consists of wild theorizing, self-promotion, and arguing. I have a feeling it will improve, but for now I'd like to discuss this subject away from all the SuperKoolNewAndroidForum.com forums.
My Goals for this Thread:
Establish what is known to work, and what the kernel is sorely lacking.
a) I know we have booted Linux on HTC devices, has it been done on the most current devices? (please link to thread/proof)
b) What are the main major roadblocks preventing Linux from being run on more HTC devices? (Obscure hardware design, bricking phone)
Compile a list of needed and helpful software for loading Android: bootloaders, useful Linux tools, filesystem images
Provide continual updates with photos/logs as we (hopefully) make progress
My bet is that the current 'gPhone' in the videos is an HTC device not unlike yours or mine. [link to my blog] IMHO, the hype over 'When will the first gPhone be released' is irrelevant, as Google has been working closely with HTC and Qualcomm for a long time -- and the specs for Android are so low, Google clearly expects to be able to run Android on existing hardware, without needing new hardware technology.
Of course, the tools and software we need are all in existence already, someone at Google is doing a good job of keeping their mouth shut. Therefore this is not an impossible task, just difficult, but I know you xda-hackers like a challenge! So, Let's go!!
Charles
FYI: I am aware XDA was founded with the Xanadux project, so this should be the perfect place to hack us a gPhone. I've also browsed threads, read the Wiki, studied up on the Hermes Linux project -- but things seem to have died since Feb 07, I'm hoping this latest development with Android will spark interest again, and we will be able to run Linux on our current, most powerful devices. I could make educated guesses about the state of the Xanadux project, but I'd rather hear it from XDA devs themselves who are most familiar.
Click to expand...
Click to collapse
where is the video?

anheuer said:
where is the video?
Click to expand...
Click to collapse
YouTube Your best friend , along with google obviously

Push Samsung to release Exynos Source Code! [Update 25.11.13]

EDIT 25.11.13
The experimental Build with the new exynos sources works fine on the S3 and improves on graphics related stuff. There are some things that are broken but I hope those issues can be ironed out.
XpLoDWilD said:
In collaboration with geecko, here's a test build with the updated graphics stuff.
======== Don't expect it to be working 100% correctly that's not the goal. This build is exclusively to get your feedback on graphics and overall performance of the ROM. It is known that Camera and video playback might be both broken partially in this build.
Click to expand...
Click to collapse
GeeckoDev said:
It basically enables us to use hardware overlays, which means that the GPU has less work to do because all the compositing work is managed by fimd. Better performance (butter), lower power consumption. :good:
Click to expand...
Click to collapse
If someone wants to try it out, it can be downloaded here (FOR S3 I9300 ONLY):
http://dl.omnirom.org/omni-4.4-20131119-i9300-EXPERIMENTAL-GRAPHICS.zip
EDIT 19.11.13
Samsung dropped an insignal Update for the Exynos 4412 devices which can be used with AOSP. It's hard to implement but thanks to the brilliant developers at XDA there is hope. Check this out from the Omni Thread:
Scarface1991 said:
I found those 2 interesting commits:
https://gerrit.omnirom.org/#/c/2431/
https://gerrit.omnirom.org/#/c/2436/
What's with the insignal exynos4 update? Does it actually do any good? (I would be very surprised if Samsung would actually do something positive for the developer community ^^)
And also will the second commit when implemented enable tv-out on the I9100? Will this be usable on other Exynos devices especially the I9300?
Click to expand...
Click to collapse
Entropy512 said:
I have been too busy with other stuff to mess with them. In theory - actual working hwcomposer and maybe TV-out. More than 6 months after when they promised, Insignal finally dropped an update, but it proved extremely difficult to integrate at that time plus none of the "old" crew had much motivation to mess with it. Clement seems to have gained motivation and has done some great stuff so far.
The initial Insignal drop was actually for Exynos 4412 devices. 4412 and 4210 are nearly identical, main differences are regarding JPEG compression and the camera interfaces.
Click to expand...
Click to collapse
GeeckoDev:
Ok, so now hwcomposer isn't complaining anymore. Screen is completely black now because fences are timing out (surfaces are ready to be displayed when the fence is firing). dmesg is full of derp, looks like Mali driver is complaining. That's another progress... getting closer
EDIT: sent a mail to three samsung developers.. who knows
EDIT2: xplodwild should release a test build for i9300 users tomorrow.
Click to expand...
Click to collapse
The Test build is going to be for the I9300 but since the S2 has an almost identical SoC it's not far behind if everything works out for the I9300. It's great news and that's what we need
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Before 2013:
EDIT
Until now there was a lot of talk from Samsung but everything they released so far is useless for AOSP. They promised full availability of Exynos Source Code by the end of 2012. Let`s see if this time they can keep their promise or if it will be just talk like in the past with the eMMC Super-Brick issue.
25/10/2012 Samsung Exynos Tweets:
Yes, we are opening up HAL source code for the platform, which includes HWC, camera, gralloc, audio and light.
Click to expand...
Click to collapse
Developers: Expect full availability of integrated source code for #Exynos 4 family of processors on OrigenBoard by the end of 2012!
Click to expand...
Click to collapse
https://twitter.com/SamsungExynos/status/261482746101235712
Git server access will also be available to the public in Nov. 2012
Click to expand...
Click to collapse
https://twitter.com/SamsungExynos/status/261483932925689856
Now let`s hope they really mean it and that they don`t open up something useless...
Nevertheless I`m glad that we accomplished something.
Samsung presentation at the Big Android BBQ:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
chainfire tweets:
It seems Samsung is saying there will be sourcecode for the needed Exynos parts... I'm not sure it's everything TeamHacksung needs, ...
Click to expand...
Click to collapse
... but I'm sure they'll let us know. It all sounds very promising though. First stuff should be seen in weeks, complete before 2013.
Click to expand...
Click to collapse
Complete Samsung Developers Session:
This thread is the equivalent to the one in the SIII Forums and not my idea. AntonLiv92 started the thread to inform people where they can write personal concerns to Samsung, so they will release the source code and proper documentation for Exynos based devices and as you probably all know our SII is based on Samsung`s Exynos 4210 processor.
This thread will inform you people where to contact Samsung, so that we get their attention or as codeworkx said:
Originally Posted by codeworkx
If they don't know that there are a lot of users out who are pissed because of the bad exynos support, then they'll not change anything.
If 10 users are crying -> just 10 users, ignore them.
If 1000 users are crying -> ok, let's think a few minutes about it.
If 100.000 users are crying -> holy ****, we have to do something
If you stop crying, they'll stop paying attention and you've achieved nothing like in the past.
Click to expand...
Click to collapse
So our goal is to get Samsung`s attention by writing as many concerns as possible of missing source code to Samsung. Of course it`s also important what you write, so it`s not just a big noob campaign asking for the Source Code. Codeworkx made a list of what is needed:
Originally Posted by codeworkx
- git repos
- commit history
- release patches if ready as single commits and not as big messed up tarballs
- up2date reference code for their video interfaces
- up2date reference camera hal to work with these interfaces
- up2date reference audio hal
- up2date reference hardwarecomposer
- patches needed for android framework (platform support)
- gralloc if possible
- maybe hdmi?
- maybe fmradio?
Click to expand...
Click to collapse
You can find a done letter that you can copy and paste more down below.
Main Petition thread in the SIII Forums created by AntonLiv92:
[MISSION] Let's get some Exynos sources! - xda-developers
There is also a thread in the Galaxy Note N7000 section as well now created by androidindian:
[IMPORTANT] Make Samsung release "Exynos" sources! - xda-developers
Galaxy Note II:
http://forum.xda-developers.com/showthread.php?p=32684117#post32684117
And the AT&T Samsung Galaxy S II SGH-I777 section as well:
Samsung Exynos Movement(POLL ADDED) - xda-developers
German Thread regarding this issue:
http://www.android-hilfe.de/samsung...moegliche-freigabe-der-exynos-quellcodes.html
Thread on Androidforums:
http://androidforums.com/samsung-ga...1098-push-samsung-release-exynos-sources.html
Facebook group "Polite request to Samsung to release Exynos source code":
https://www.facebook.com/ExynosSourceCode
So yes we are serious about this!
HOW TO CONTACT SAMSUNG?
Via Twitter: https://twitter.com/SamsungExynos
https://twitter.com/samsungmobile
Via Facebook: https://www.facebook.com/SamsungMobile
Via Google+: https://plus.google.com/+SamsungMobile
You can write a personal letter regarding the release of the source code to:
http://opensource.samsung.com/reception/receptionSub.do?method=inquiry
If you don`t have time for writing a big letter, this is a already written one that you can copy and paste:
Requester: Enter your name.
ID (E-mail): Enter your email address.
Country: Select your country.
Inquiry Type: Select "Request for Source Codes".
Model: Enter "Samsung I9100 Galaxy S II".
Message: Copy & Paste the following...
Dear Samsung,
without a doubt you build the best phones on the market and I really enjoy using the Galaxy SII I9100 but there is a problem. A lot of people like to use mods like the popular CyanogenMod on your flagship
devices. Without the source code and proper documentation great developers like codeworkx who is a device maintainer for Samsung phones at XDA-Developers.com start to turn their back on Samsung
phones like the Galaxy SIII because they are based on the Exynos processor due to the fact that there is a lack of source code and proper documentation. Since developers are the lifeblood of Android it`s
not a good sign to see them leave to other companies who provide proper source code and documentation. Qualcomm and Texas Instruments understand that and they released their source code and
developers are using it to do great things.
With this letter I ask you to release Source code and proper documentation for the Exynos 4210 and the Exynos 4412 and in the best case it should include the following:
- git repos
- commit history
- release patches if ready as single commits and not as big messed up tarballs
- up2date reference code for their video interfaces
- up2date reference camera hal to work with these interfaces
- up2date reference audio hal
- up2date reference hardwarecomposer
- patches needed for android framework (platform support)
- gralloc if possible
- maybe hdmi?
- maybe fmradio?
Thank you for your great phones and I really hope that you will release the above stated things.
Click to expand...
Click to collapse
Responses from Twitter @samsungExynos
There are other signs that this might go somewhere, since this concern is reported now on several popular Android-blogs like Androidcentral and sites like XDA Developers, which will lead to even bigger popularity on this issue.
They also contacted the CM team:
codeworkx said:
Seems you got korea's attention because of the "flooding" the community is currently doing via opensource.samsung.com. twitter, facebook and so on. They contacted us and we told them again what the community wants to have.
You know that bad press for samsung is our most effective weapon to make things changing.
So if you want to make samsung to continue paying attention, you know what to do...
Fight till you got what you want to have.
Click to expand...
Click to collapse
XDA:
Samsung Aware of Exynos Documentation Issue – xda-developers
Androidcentral:
Samsung 'hears' Exynos community documentation concerns | Android Central
Sammobile:
Samsung Listens To Developer Concerns Over Missing Exynos Docs | SamMobile
Androidauthority:
Samsung acknowledges lack of documentation for Exynos SoC
Androidpit:
Exynos-Affäre: Entwickler setzen Samsung unter Druck - AndroidPIT
Sammyhub:
Samsung Investigating Exynos Documentation Issue - Sammy Hub
Tech-Gadget:
Samsung ‘hears’ Exynos community documentation concerns | Tech Gadget
Other links in the SIII thread.
Here is also a great video that summarizes this whole mess about Samsung and Exynos:
It is also recommended to tip popular news-blogs like Engadget or the Verge, so maybe they write about us and what we try to accomplish.
I thought that this thread might be a good idea, since we have one of the biggest userbases on the Android-platform.
Now you guys know what to do
Big thanks to AntonLiv92 for letting me use the contact links in my thread

Post this on the development section as well because I think it's the most visited one
Sent from my GT-I9100 using xda app-developers app

GalaxyGusta said:
Post this on the development section as well because I think it's the most visited one
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
That goes totally against forum rules
Sent from my GT-I9100 using xda app-developers app

GalaxyGusta said:
Post this on the development section as well because I think it's the most visited one
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
I think that this is not such a good idea because this thread has nothing to do with development directly, that`s why I posted it in the general section, which is also visited quite well I would say because of the CM10 thread etc.

How about you guys propose this as news for xda and spread the news on android news sites? And tech sites...
Sent from my GT-I9100 using xda premium

karendar said:
How about you guys propose this as news for xda and spread the news on android news sites? And tech sites...
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Just did it on Engadget.com. Let`s see, maybe it`s worth a news for them.

okay I'm crying now and I hope samsung hear it and release source code ASAP. My butt getting hot waiting for it.

Samsung is responding to the SIII campaign. Lets get the SII some attention too.
http://www.talkandroid.com/135667-s...oidForums (Android News, Rumours, and Updates)
Sent from my GT-I9300 using xda app-developers app

Warren.D said:
Samsung is responding to the SIII campaign. Lets get the SII some attention too.
http://www.talkandroid.com/135667-s...oidForums (Android News, Rumours, and Updates)
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Old news
Sent from my SGS2

Actually that's what I'm afraid of, that they release the source code only for the SIII Exynos and not for the SII. But until now they haven't released anything of course but let's see, maybe if enough people cry then they hopefully will release something.
Sent from my GT-I9100 using xda app-developers app

Scarface1991 said:
Actually that's what I'm afraid of, that they release the source code only for the SIII Exynos and not for the SII. But until now they haven't released anything of course but let's see, maybe if enough people cry then they hopefully will release something.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
both the s3 and s2 use exynos 4.. so it should be fine i guess with the documentation. but let them say a yes.. they usually just keeps the hopes high and say no later. need to push them more!!

From Entropy's post in the CM10 thread they changed too many things between S3 Exynos and the S2 for it to be useful. Let's hope they release source code for both. Scarface you should make a thread in the I777 and N7000 general sections since they use the same chips and will be affected by this news or eventual developments, I'm a I777 user and only use my own ported i9100 ROMS

the audio maybe is the problem, s3 and s2 have totally differente chip...

good idea :good:
maybe we will reach it also when we ask about the camera firmware?

Just send this letter to: http://opensource.samsung.com/reception/receptionSub.do?method=inquiry
Dear Samsung,
without a doubt you build the best phones on the market and I really enjoy using the Galaxy SII I9100 but there is a problem. A lot of people like to use mods like the popular CyanogenMod on your flagship
devices. Without the source code and proper documentation great developers like codeworkx who is a device maintainer for Samsung phones at XDA-Developers.com start to turn their back on Samsung
phones like the Galaxy SIII because they are based on the Exynos processor due to the fact that there is a lack of source code and proper documentation. Since developers are the lifeblood of Android it`s
not a good sign to see them leave to other companies who provide proper source code and documentation. Qualcomm and Texas Instruments understand that and they released their source code and
developers are using it to do great things.
With this letter I ask you to release Source code and proper documentation for the Exynos 4210 and the Exynos 4412 and in the best case it should include the following:
- git repos
- commit history
- release patches if ready as single commits and not as big messed up tarballs
- up2date reference code for their video interfaces
- up2date reference camera hal to work with these interfaces
- up2date reference audio hal
- up2date reference hardwarecomposer
- patches needed for android framework (platform support)
- gralloc if possible
- maybe hdmi?
- maybe fmradio?
Thank you for your great phones and I really hope that you will release the above stated things.
Click to expand...
Click to collapse

robertogl said:
the audio maybe is the problem, s3 and s2 have totally differente chip...
Click to expand...
Click to collapse
For that we should spam yamaha
Sent from my GT-I9100 using Tapatalk 2

asasione said:
From Entropy's post in the CM10 thread they changed too many things between S3 Exynos and the S2 for it to be useful. Let's hope they release source code for both. Scarface you should make a thread in the I777 and N7000 general sections since they use the same chips and will be affected by this news or eventual developments, I'm a I777 user and only use my own ported i9100 ROMS
Click to expand...
Click to collapse
Already done by other members
I777:
http://forum.xda-developers.com/showthread.php?t=1929357
Note N7000:
http://forum.xda-developers.com/showthread.php?p=32622901#post32622901

Scarface1991 said:
Already done by other members
I777:
http://forum.xda-developers.com/showthread.php?t=1929357
Note N7000:
http://forum.xda-developers.com/showthread.php?p=32622901#post32622901
Click to expand...
Click to collapse
Bro I've written to some major blogs like engadget verge gsmarena.. Would be lovely if you would recommend tip them as well..The more we write to them they will do a feature writeup on this.. If the major blogs write about this the impact would be larger..
Sent from my GT-N7000 using xda premium

androidindian said:
Bro I've written to some major blogs like engadget verge gsmarena.. Would be lovely if you would recommend tip them as well..The more we write to them they will do a feature writeup on this.. If the major blogs write about this the impact would be larger..
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Yeah I`ve wrote Engadget already about that. Will do as well on other popular blogs. Thanks

where do i sign?

[IMPORTANT] Make Samsung release "Exynos" sources!

This thread is the equivalent on the SIII and SII Forums and not my idea. AntonLiv92 and scarface1991 started the thread to inform people where they can write personal concerns to Samsung, so they will release the source code and proper documentation for Exynos based devices and as you probably all know our Note is based on Samsung`s Exynos 4210 processor.
So as you know the Galaxy Note contains the Exynos 4 chip, which Samsung doesn't provide any up2date documentation of. What they release is kernel source, and a few parts of the platform source that aren't actually modified or really critical. In short, everything in the Platform tarball is stuff that is already in AOSP, and the AOSP version works fine. So our goal is to convince Samsung to release the documentation and sources for the Exynos chip that the developers need so much.
* You are welcome to join the "Polite request to Samsung to release Exynos source code" FB page:
https://www.facebook.com/ExynosSourceCode
Write a request to Samsung asking them to provide proper documentation for the Exynos SoC:
https://twitter.com/SamsungExynos
https://twitter.com/samsungmobile
https://www.facebook.com/SamsungMobile
https://plus.google.com/+SamsungMobile
It is also highly recommended to create inquiry in the OSRC:
http://opensource.samsung.com/reception/receptionSub.do?method=inquiry
Hope it works! :fingers-crossed:
The Thread in the Forums will inform you people where to contact Samsung, so that we get their attention or as codeworkx said:
Originally Posted by codeworkx
If they don't know that there are a lot of users out who are pissed because of the bad exynos support, then they'll not change anything.
If 10 users are crying -> just 10 users, ignore them.
If 1000 users are crying -> ok, let's think a few minutes about it.
If 100.000 users are crying -> holy ****, we have to do something
If you stop crying, they'll stop paying attention and you've achieved nothing like in the past.
Click to expand...
Click to collapse
So our goal is to get Samsung`s attention by writing as many concerns as possible of missing source code to Samsung. Of course it`s also important what you write, so it`s not just a big noob campaign asking for the Source Code. Codeworkx made a list of what is needed:
Originally Posted by codeworkx
- git repos
- commit history
- release patches if ready as single commits and not as big messed up tarballs
- up2date reference code for their video interfaces
- up2date reference camera hal to work with these interfaces
- up2date reference audio hal
- up2date reference hardwarecomposer
- patches needed for android framework (platform support)
- gralloc if possible
- maybe hdmi?
- maybe fmradio?
Click to expand...
Click to collapse
and Entropy512 tweeted to Samsung exynos about:
@Entropy512
@SamsungExynos You have been discussing this for over a year with no results... TI and Qualcomm are setting the standard, you are failing.
@Entropy512
@SamsungExynos For more specifics on my last tweet: TI has omapzoom, Qualcomm has CodeAurora, you have nothing.
Click to expand...
Click to collapse
Responses from Twitter @SamsungExynos
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
There are other signs that this might go somewhere, since this concern is reported now on several popular Android-blogs like Androidcentral and sites like XDA Developers, which will lead to even bigger popularity on this issue.
They also contacted the CM team:
Originally Posted by codeworkx
Seems you got korea's attention because of the "flooding" the community is currently doing via opensource.samsung.com. twitter, facebook and so on. They contacted us and we told them again what the community wants to have.
You know that bad press for samsung is our most effective weapon to make things changing.
So if you want to make samsung to continue paying attention, you know what to do...
Fight till you got what you want to have.
Click to expand...
Click to collapse
In the Media:
On xda-developers.com
On pocketnow.com
On androidcentral.com
On androidnext.de (Translated vesrion here)
I thought that this thread might me a good idea, since we have one of the biggest userbases on the Android-platform.
Now you guys know what to do

Nice. Tomorrow I'll hit them with everything I've got.
Sent from my GT-N7000 using xda app-developers app

Beretta93 said:
Nice. Tomorrow I'll hit them with everything I've got.
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Awesome.. Let's do it! The more we do the better.. Btw samsungexynos is really getting it from the community via twitter and facebook.
And @Entropy512 has written lots of strong tweets to them.. Let's support our devs more!
Sent from my GT-N7000 using xda premium

Good initiative
I am in

This thread deserves a little bump.
C'mon people, take part in this, it is of vital importance.:good:

Great work
Sent from my GT-N7000 using xda premium

chasmodo said:
This thread deserves a little bump.
C'mon people, take part in this, it is of vital importance.:good:
Click to expand...
Click to collapse
Totally! Lets do this! If we want future builds of android , aosp and cm support.. lets get together..

Stand your ground and fight!

Did yesterday and today, let's keep'em on fire.

Great! :good:
Thread in the SII section: http://forum.xda-developers.com/showthread.php?t=1929188
Thread in the SIII section: http://forum.xda-developers.com/showthread.php?t=1925709
I really like how popular this thing gets. Let`s do this people, let`s make this as popular as we can. Great developers like codeworkx and Entropy512 tried it more than once to ask politely for this and Samsung did nothing. They wouldn`t even listen about the serious hard brick kernel bug and they still bringing out unsafe kernels. Now it`s our turn to make them to listen.
Edit
Just send this letter to: http://opensource.samsung.com/reception/receptionSub.do?method=inquiry
Dear Samsung,
without a doubt you build the best phones on the market and I really enjoy using the Galaxy SII I9100 but there is a problem. A lot of people like to use mods like the popular CyanogenMod on your flagship
devices. Without the source code and proper documentation great developers like codeworkx who is a device maintainer for Samsung phones at XDA-Developers.com start to turn their back on Samsung
phones like the Galaxy SIII because they are based on the Exynos processor due to the fact that there is a lack of source code and proper documentation. Since developers are the lifeblood of Android it`s
not a good sign to see them leave to other companies who provide proper source code and documentation. Qualcomm and Texas Instruments understand that and they released their source code and
developers are using it to do great things.
With this letter I ask you to release Source code and proper documentation for the Exynos 4210 and the Exynos 4412 and in the best case it should include the following:
- git repos
- commit history
- release patches if ready as single commits and not as big messed up tarballs
- up2date reference code for their video interfaces
- up2date reference camera hal to work with these interfaces
- up2date reference audio hal
- up2date reference hardwarecomposer
- patches needed for android framework (platform support)
- gralloc if possible
- maybe hdmi?
- maybe fmradio?
Thank you for your great phones and I really hope that you will release the above stated things.
Click to expand...
Click to collapse

ahalford said:
Did yesterday and today, let's keep'em on fire.
Click to expand...
Click to collapse
Awesome!
Sent from my GT-N7000 using xda premium

I'm in ,let the games begin.....

Of course I'm in. But do they really care about a handful (thousands) of geeks, flashing custom ROMs, compared to millions of sales ?
I hope they'll do.
Cheers, Markus

Sent from my GT-N7000 using Tapatalk 2

trell959 said:
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Thanks mate!
Yes that is there automated response. Community members are messaging them on that site, and twitter constantly..

Done.
Come on ppl. Be a sport.

Dear Samsung,
This is another request for the release of the source code and proper documentation for the Exynos processors that are currently powering your high end devices. As many of your clients, I choose my smartphones on the basis of their popularity among the developers community, as they have been able to provide high end support for a long time and keep them running smoothly with
the most up-to-date software.
This support does not cost you anything, as you are not paying high skilled programmers to work countless hours on fine tuning and further improving your products. I personally think you are getting a great deal, for little effort on your side.
In order for this to be able to continue and further improve, I would kindly request (as many have already done) if you could speed up your promises and finally release:
Originally Posted by codeworkx:
- git repos
- commit history
- release patches if ready as single commits and not as big messed up tarballs
- up2date reference code for their video interfaces
- up2date reference camera hal to work with these interfaces
- up2date reference audio hal
- up2date reference hardwarecomposer
- patches needed for android framework (platform support)
- gralloc if possible
- maybe hdmi?
- maybe fmradio?
I hope you will not make the same mistake as other manufacturers, that turned their back on the developers community and their sales results suffered as a result of doing that. And as a currently satisfied customer of a Galaxy Note (GT-N7000) I am looking forward to the JB (Android 4.1) update .
Click to expand...
Click to collapse
This is my post on their Facebook page, lets hope they'll do something about it .
Thank you for letting me know about this initiative.

Johev, well said--> quote: "I hope you will not make the same mistake as other manufacturers, that turned their back on the developers community and their sales results suffered as a result of doing that."
They do not want sales suffered as HTC, so maybe we will success.

Great Idea!
Did my bit!

Also made a twitter account just to tweet to them
Will do this again tommorow
GG...
Also wrote on their fb wall
Hope theyll listen? *fingers crossed*
Hi androidindian, do you mind if i copy your thread to Note 2 forum? ill give you credit fully...
I just want to spread the wprd but im not very good with my words
Hope you wont mind
Sent from my GT-N7000 using xda premium

[IMPORTANT] Make Samsung release their source codes!

Like the threads started in S II, S III, and Note N7000 forums, im starting a thread here.
It was originally the idea of AntonLiv92 and scarface1991, carried forward by androidindian to inform people that they can make Samsung release their source codes for Exynos-devices...
i am just carrying the message forward, you can spread the idea in other forums
How can you help?
By joining the "Polite request to Samsung to release Exynos Source Codes".
Here:
* FB page:https://www.facebook.com/ExynosSourceCode
Or by writing to their twitter account:
https://twitter.com/samsungexynos
You can also create an inquiry in the OSRC, which is highly recommended
http://opensource.samsung.com/reception/receptionSub.do?method=inquiry
You are highly recommended to spread this word im other forums, so that wordpower increases
As said by codeworkx
Originally Posted by codeworkx:
If they don't know that there are a lot of users out who are pissed because of the bad exynos support, then they'll not change anything.If 10 users are crying -> just 10 users, ignore them.If 1000 users are crying -> ok, let's think a few minutes about it.If 100.000 users are crying -> holy ****, we have to do somethingIf you stop crying, they'll stop paying attention and you've achieved nothing like in the past.
Click to expand...
Click to collapse
It is also inportant to know what we are asking Samsung, so it's not just a big noob campaign with no wind.
Codeworkx has highlighted the specifics so you can get them:
Originally Posted by codeworkx
- git repos
- commit history
- release patches if ready as single commits and not as big messed up tarballs
- up2date reference code for their video interfaces
- up2date reference camera hal to work with these interfaces
- up2date reference audio hal
- up2date reference hardwarecomposer
- patches needed for android framework (platform support)
- gralloc if possible
- maybe hdmi?
- maybe fmradio?
Click to expand...
Click to collapse
We can confirm to you that its not just a fruitless campaign.
Entropy tweeted this to SamsungExynos:
@Entropy512
@SamsungExynos You have been discussing this for over a year with no results... TI and Qualcomm are setting the standard, you are failing.
@Entropy512
@SamsungExynos For more specifics on my last tweet: TI has omapzoom, Qualcomm has CodeAurora, you have nothing.
Click to expand...
Click to collapse
This is reply Entropy512 got:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This may actually go somewhere be sure to give your support so you can have better custom ROMs and much better mobile phones overall...
They also contacted the CM team:
Originally Posted by codeworkx
Seems you got korea's attention because of the "flooding" the community is currently doing via opensource.samsung.com. twitter, facebook and so on. They contacted us and we told them again what the community wants to have.You know that bad press for samsung is our most effective weapon to make things changing.So if you want to make samsung to continue paying attention, you know what to do...Fight till you got what you want to have.
Click to expand...
Click to collapse
IN THE MEDIA:
on xda-developers
on pocketnow.com
on androidcentral.com
on androidnext.de --->translated version here

This thread in S III section: http://forum.xda-developers.com/showthread.php?t=1929188
This thread in S II section: http://forum.xda-developers.com/showthread.php?t=1929188
This thread in Note I section: http://forum.xda-developers.com/showthread.php?t=1929307
For convenience, Scarface1991 made a letter:
Just sent this to http://opensource.samsung.com/reception/receptionSub.do?method=inquiry
Dear Samsung,
without a doubt you build the best phones on the market and I really enjoy using the Galaxy SII I9100 but there is a problem. A lot of people like to use mods like the popular CyanogenMod on your flagship*devices. Without the source code and proper documentation great developers like codeworkx who is a device maintainer for Samsung phones at XDA-Developers.com start to turn their back on Samsung*phones like the Galaxy SIII because they are based on the Exynos processor due to the fact that there is a lack of source code and proper documentation. Since developers are the lifeblood of Android it`s*not a good sign to see them leave to other companies who provide proper source code and documentation. Qualcomm and Texas Instruments understand that and they released their source code and*developers are using it to do great things.
With this letter I ask you to release Source code and proper documentation for the Exynos 4210 and the Exynos 4412 and in the best case it should include the following:
- git repos
- commit history
- release patches if ready as single commits and not as big messed up tarballs
- up2date reference code for their video interfaces
- up2date reference camera hal to work with these interfaces
- up2date reference audio hal
- up2date reference hardwarecomposer
- patches needed for android framework (platform support)
- gralloc if possible
- maybe hdmi?
- maybe fmradio?
Thank you for your great phones and I really hope that you will release the above stated things.
Click to expand...
Click to collapse

Android blogs and samsung blogs now posting this more and more..
http://bit.ly/SNy5jU (sammyhub)
http://allaboutsamsung.de/2012/10/sa...os-quellcodes/ (allaboutsamsung)
http://www.sammobile.com/2012/10/10/...g-exynos-docs/ (sammobile)
http://rootzwiki.com/news/_/articles...pr-stunt-r1176 (rootzwiki)
http://www.androidauthority.com/sams...issues-121487/ (android authority)
(Courtesy androidindian)
:good good:
Things are getting very exciting *rubs hands and fingers crossed*

also mate, do post their twitter account https://twitter.com/samsungexynos on the op. anyone who has twitter should write to them

androidindian said:
also mate, do post their twitter account https://twitter.com/samsungexynos on the op. anyone who has twitter should write to them
Click to expand...
Click to collapse
Adding

androidindian said:
also mate, do post their twitter account https://twitter.com/samsungexynos on the op. anyone who has twitter should write to them
Click to expand...
Click to collapse
thanks for the link, i don't have facebook, but i have sent them a tweet now. everyone should do so!

I have a question. I clearly don't have full idea how it works in terms of open source license.
Is this a requirement from Samsung (or any other vendor) that they release information regarding Exynos chip? They are supposed to release kernel sources, does the license also state that all hardware/driver related information also have to be released. Because, if this is not something mandatory, no amount of petition is going to change anything.

I doubt it will help much, but I did the facebook, twitter, and OSRC bit. I highly doubt anything comes of this though...except more frustration.

hot_spare said:
I have a question. I clearly don't have full idea how it works in terms of open source license.
Is this a requirement from Samsung (or any other vendor) that they release information regarding Exynos chip? They are supposed to release kernel sources, does the license also state that all hardware/driver related information also have to be released. Because, if this is not something mandatory, no amount of petition is going to change anything.
Click to expand...
Click to collapse
No, Samsung doesn`t have to release anything of what we ask if they don`t want to (like they did in the past) but it would hurt their reputation when it comes to developers. Of course people who have no idea about Root and CyanogenMod will still buy their phones but people like Codeworkx and other great developers will eventually start to move on to other developer-friendly devices and as a reaction to that other people will do that too. I know for myself that I won`t buy another Exynos powered device if Samsung doesn`t change it`s attitude soon.

Sent.
@SamsungExynos Please release Source code and proper documentation for the Exynos 4210 and the Exynos 4412 (and future 5xxx when available)
Here's hoping they'll listen...

tstack77 said:
Sent.
@SamsungExynos Please release Source code and proper documentation for the Exynos 4210 and the Exynos 4412 (and future 5xxx when available)
Here's hoping they'll listen...
Click to expand...
Click to collapse
great thanks!

tstack77 said:
Sent.
@SamsungExynos Please release Source code and proper documentation for the Exynos 4210 and the Exynos 4412 (and future 5xxx when available)
Here's hoping they'll listen...
Click to expand...
Click to collapse
Sent pretty much the same as well

Sent today too made a twittrr account just to tweet

Looks like Note 2 will never be getting support from CM. Step 1 to frustration.
Sent from my GT-N7000 using xda app-developers app

Been looking and getting ready to buy the note 2 but i guess i have to hold off and look for some other good alternatives maybe the next nexus or pad phone 2 or an HTC. No cyanogenmod or aosp support,no exynos device for me a gs2 owner
Sent from my Nexus 7 using Xparent SkyBlue Tapatalk 2

just commenting so more people know about the petition

the most relevant samsung twitter account for us
https://twitter.com/samsung_dev

https://twitter.com/AntonLiv92/status/269749477856903168
Note II owners, are you with us?

I was going to start a thread like this myself, but then I saw yours
I soooo want Samsung to release the kernel source code .
Corey
Sent from my Nexus 7 using Tapatalk 2

i have tweeted and send request for taking part in this. Thanks.

Mock Up Appstore for Ubuntu Phone (Work in Progress)

Hi,
I have done some mock-ups of a software store on Ubuntu Phone OS.
Hope you like the screenshots
The only feature that works though is software update button and it just runs a apt-get upgrade.
I was wondering whether there were any development groups for Ubuntu on this forum that I could be a part of?
Anyway... let me know what you think of my work-in-progress software center
Available Software
my-cloudspace.co.uk/36jrgfjAcjY17y4/Available%20Software.png
Installed Software
my-cloudspace.co.uk/Aq1O822UT3ExE7s/Installed%20Software.png
Update Software
my-cloudspace.co.uk/NT2n5v3Ebp849NT/screenshot.png
I havent done ten posts so you'll have to manually view the images...

I have brought a domain called elbuntu projects (elbuntu is my display name on Skype) I will put my projects there over the next week.

Looks real good.

Thanks for the feedback.

Of course it need search, categorises and things but this is a good start.
If your want to show Canonical your work and help with the development
of the real software center you should submit this on the official mailing list.

I am planning to do this when I have perfected the designs... I am implementing the search as we speak and also want to have a app description page with reviews etc... Then I am going to submit the first designs to the mailing list.

Nice. Have a thank!
Sent from my Samsung Galaxy Note II LTE GT-N7105 using XDA Premium HD

elgunvo,
I strongly urge you to subscribe the Ubuntu-Touch mailing list and contact the core app development team if you have not already done so. Volunteering to help with the development of the "Ubuntu-Touch Software-Centre" will quickly get you the contacts who are running those efforts. https://launchpad.net/~ubuntu-phone and scroll down to "Mailing List"
Also: https://wiki.edubuntu.org/Touch/Contribute
To see what happened with a developer, who was started to creating their own Music app, follow this thread from the mailing list. It ended up as a good news situation for all involved.
https://lists.launchpad.net/ubuntu-phone/msg00744.html
In general there are issues with "perfecting" your design in relative isolation. The Core Developers are encouraged all devs to post your interface designs on line so that your product is both consistent with the Ubuntu-Touch interface and takes full advantage of it.
The best way to do remote, collaborative UX Design:
http://www.balsamiq.com/products/mockups/mybalsamiq
Examples: https://ubuntu.mybalsamiq.com/proje...sessionid=492036AAA24CBDF5C84D8CC364C67588-n2
From the UDS (Ubuntu Developers Sessions) "Ubuntu Touch Core Apps Project":
http://summit.ubuntu.com/uds-1303/meeting/21616/appdev-1303-coreapps/
At ~38:00 is an important design process review by one of the core app development team.
At ~46:30 Wire-frames creation tools used by the core app developers
2) The state of the Ubuntu-Touch Software-Centre is very much in flux. It has not actually been decided as of this week's UDS if debs alone will be used for installations, file system location for app installs (likely /opts) and how Ubuntu-Touch apps will integrate with the Ubuntu's current desktop Software-Centre. It was mentioned a number of times, by the SDK lead, that he felt debs had unnecessary overhead for the installation of apps on devices with limited CPU and power consumption concerns. Within their tight time frames debs maybe their only option.
3) Heavily stressed in the UDS SDK sessions were:
a) Due to the current dynamic nature of the Ubuntu-Touch APIs stick with pure QML as much as possible to reduce the amount of rework you would need to do.
b) At this time cross-compiling C++ apps are problematic with the current SDK
UDS: Ubuntu SDK Tools (this whole video is worth watching as you gain a lot of incite into the current state and direction of Ubuntu-Touch development)
http://summit.ubuntu.com/uds-1303/meeting/21625/appdev-1303-ubuntu-sdk-tools/
I hope you find this information helpful.
Doug

Looks very simple and clean, but at the same time it still retains the theme of Ubuntu touch, I love it,

This looks like something that should already exist
Great work, but please share it with Ubuntu community so your proposition could be taken into account for creating complete app market look

Available Software
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Installed Software
Update Software
Posted the images for the OP
PHONE SLOW CLICK ME?
_____________________________________
"Waiting 4 s4......"- TingTingin"​

You may find this relevant.
Extend interoperability between Ubuntu devices further by making the "app store" on Ubuntu phones simply a mobile Software Center:
"As much as the Ubuntu team wants to make Unity work on ALL devices and make all apps conform to the same pattern, using different app stores for different devices is only going to hurt the Ubuntu team in the long run. If there's one OS for all, then there must be one app store for all.
The Ubuntu Software Center is the perfect app store in itself. So let's embrace it no matter what the form factor."
https://blueprints.launchpad.net/ubuntu/+spec/ubuntuphone-s-mobile-software-center-form-factor

3DSammy said:
You may find this relevant.
Extend interoperability between Ubuntu devices further by making the "app store" on Ubuntu phones simply a mobile Software Center:
"As much as the Ubuntu team wants to make Unity work on ALL devices and make all apps conform to the same pattern, using different app stores for different devices is only going to hurt the Ubuntu team in the long run. If there's one OS for all, then there must be one app store for all.
The Ubuntu Software Center is the perfect app store in itself. So let's embrace it no matter what the form factor."
https://blueprints.launchpad.net/ubuntu/+spec/ubuntuphone-s-mobile-software-center-form-factor
Click to expand...
Click to collapse
Thats what I want to do. There are no plans on creating a QML front end on the phone at the moment so I wanted to start it off. No doubt they would have been doing this sooner or later. I am just trying to push it along.
The other thing is that my software will actually use the same methods used in the Ubuntu Software Centre to install apps and to remove them, The software update section on the software centre I made would combine the Software Update app with The Ubuntu Software Centre app thus getting rid of the need for two apps
BTW, I submitted my idea to the mailing list a while back with new designs but still haven't got a response back. I hope at least i am on the team when they decide to do one

elgunvo,
I also made a post on the mailing and in the IRC #ubuntu-touch channel and did not received a response.
I have been reviewing the majority of videos from last week's UDS (Ubuntu Developer Summit) and have gleamed some information you may find relevant.
1) The number of challenges just to complete designs, implement, integrate and have a half decent "production" version for the "phone" form factor release of Oct 2013 (v13.10) is mind boggling.
2) They are desperate for the developer community to add apps and take charge. You may even be allowed to lead an effort if you heavily coordinate with the core-app-team which is currently focused on other priorities. I suspect to a certain extent due to bullet point #3 below.
See: https://wiki.ubuntu.com/Touch/Contribute for contribute advise.
3) The state of distributions for device images and even the application file system layout is still in flux. So application installation will be problematic (shift sands) for at least the next several months. Likely no earlier than May 2013 which coincides with the "alpha" or as it is also called the 13.05 release of Ubuntu-Touch.
4) During the UDS session it was mentioned that ALL the Ubuntu-Touch sub-projects are tracked through on-line blueprints on Launchpad which are accessible by the public.
You may be interested in the following information from UDS:
"App Development Community Growth":
http://summit.ubuntu.com/uds-1303/meeting/21615/appdev-1303-app-development-community-growth/
Check around the 27:00 mark for the mention of an app contest
Check around the 27:50 mark for the mention of an App developer week for app devs to learn about writing apps and the platform
Also "Ubuntu SDK Days is an online event on Thursday, 14th March and Friday, 15th March where a number of app developers and Ubuntu SDK creators will get you started writing apps for Ubuntu on multiple devices. ":
https://wiki.ubuntu.com/UbuntuSDKDays
If you cannot watch the videos live they will be available for viewing after the event just as the UDS sessions are on YouTube.

3DSammy said:
elgunvo,
I also made a post on the mailing and in the IRC #ubuntu-touch channel and did not received a response.
I have been reviewing the majority of videos from last week's UDS (Ubuntu Developer Summit) and have gleamed some information you may find relevant.
1) The number of challenges just to complete designs, implement, integrate and have a half decent "production" version for the "phone" form factor release of Oct 2013 (v13.10) is mind boggling.
2) They are desperate for the developer community to add apps and take charge. You may even be allowed to lead an effort if you heavily coordinate with the core-app-team which is currently focused on other priorities. I suspect to a certain extent due to bullet point #3 below.
See: https://wiki.ubuntu.com/Touch/Contribute for contribute advise.
3) The state of distributions for device images and even the application file system layout is still in flux. So application installation will be problematic (shift sands) for at least the next several months. Likely no earlier than May 2013 which coincides with the "alpha" or as it is also called the 13.05 release of Ubuntu-Touch.
4) During the UDS session it was mentioned that ALL the Ubuntu-Touch sub-projects are tracked through on-line blueprints on Launchpad which are accessible by the public.
You may be interested in the following information from UDS:
"App Development Community Growth":
http://summit.ubuntu.com/uds-1303/meeting/21615/appdev-1303-app-development-community-growth/
Check around the 27:00 mark for the mention of an app contest
Check around the 27:50 mark for the mention of an App developer week for app devs to learn about writing apps and the platform
Also "Ubuntu SDK Days is an online event on Thursday, 14th March and Friday, 15th March where a number of app developers and Ubuntu SDK creators will get you started writing apps for Ubuntu on multiple devices. ":
https://wiki.ubuntu.com/UbuntuSDKDays
If you cannot watch the videos live they will be available for viewing after the event just as the UDS sessions are on YouTube.
Click to expand...
Click to collapse
Thanks for this info. I will check the videos out tonight and hopefully start a small, organized community of developers who will help me to add the extra apps to Ubuntu Phone.

Your install button look like it's already pressed btw, nice design, like it !

New UI
Hi All,
I have done a better ui for the App Store.
Youtube Video of the UI can be found here:
http://www.youtube.com/watch?v=MqzlF8qPTy8
Hope you like it and feel free to give suggestions

elgunvo,
Watched the video and really like the direction you are taking. I am also glad you are coordinating with the Canonical developers.

This looks great.

This looks awesome!
Sent from my Nexus 7 using xda app-developers app