Faea Release Full Source Code for Mediatek - Android General

{
"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"
}
Faea is just new Android phone brand from China, and only a few model on sale now. Their Faea F1 is the world’s cheapest NFC phone, and Faea F2s own better FHD screen and faster MediaTek quad-core processor. Faea decide to release full source code to all developers as Thanksgiving Day gifts.
Faea has plan to compile CyanogenMod ROM with official team, the team leader Jef Oliver (Head of Developer Relations & Legacy, CyanogenMod) has a little difficult to port the official ROM, so Faea decide to release all source code to all developers who want to help them. As we known, CyanogenMod is the most popular unofficial ROM on Android operating system, but there is no ROM on MediaTek processor yet, although there is tons of China phone used this company processor. Faea F2s hope to be first, but still in processing after 2 months effort.
Faea has released the source code on their official site, all developers may download it now if you are interested in the original MediaTek source code.
Source Link : http://www.faeamobile.com/opensource
News Source : http://www.gizmochina.com/2013/11/27/faea-f2s-first-full-open-source-on-mediatek-processor/#comment-3054
Hopefully this can help developers to develop a Custom Rom for other MTK devices as well..

Problem here
Well i guess it wont that open source as the source is for private distribution only and will only be distributed to the trusted people and not anyone else as also seen in their forum
Hope they will keep it public and real open source
The real villan is MediaTek. I have a mtk6575 device and now I really hate the company now, not only me the developers hate it too
I hate the company too much and i somebody allows me then i'll ban the company. Why the heck in the world would violate open gpl v2 law and not release the source? I really believe google should file a case against mediatek. I dont know why it dont allow anyone to release their source code.

Related

[Q] Honeycomb question - don't shoot me

This isn't a request about getting the Honeycomb on the G-Tab, so lighten up, Francis.
My question is more about the source code for Android 3.0 and how Google goes about releasing that to the public. I don't really understand their processes in developing a new OS and releasing it for the world to use.
Do they typically only provide it to hardware developers like Motorola, then after a period of time give it to anyone else that wants it?
When they post it, it will be available to anyone to download...
http://source.android.com/index.html
Sooo, my question was more about the processes they go through to get to that point. I know it'll be on the source code page "when it's ready"...but I'm looking for maybe an overview of what it is that they're doing from a business perspective to get it to the masses.
anyone call me francis, and I'll kill ya...
gingerberry said:
anyone call me francis, and I'll kill ya...
Click to expand...
Click to collapse
LOL. Any of you guys touch my stuff...and I'll kill ya.
gingerberry said:
anyone call me francis, and I'll kill ya...
Click to expand...
Click to collapse
How about Ginger?
{
"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"
}
I just want you guys to know, when Honeycomb development starts, I'll be right behind you every step of the way.
On a more serious note, here's their explanation of their release process:
"What is involved in releasing the source code for a new Android version?
Releasing the source code for a new version of the Android platform is a significant process. First, the software gets built into a system image for a device, and put through various forms of certification, including government regulatory certification for the regions the phones will be deployed. It also goes through operator testing. This is an important phase of the process, since it helps shake out a lot of software bugs.
Once the release is approved by the regulators and operators, the manufacturer begins mass producing devices, and we turn to releasing the source code.
Simultaneous to mass production the Google team kicks off several efforts to prepare the open source release. These efforts include final API changes and documentation (to reflect any changes that were made during qualification testing, for example), preparing an SDK for the new version, and launching the platform compatibility information.
Also included is a final legal sign-off to release the code into open source. Just as open source contributors are required to sign a Contributors License Agreement attesting to their IP ownership of their contribution, Google too must verify that it is clear to make contributions.
Starting at the time mass production begins, the software release process usually takes around a month, which often roughly places source code releases around the same time that the devices reach users."
http://source.android.com/faqs.html
So it sounds like they go through the regulatory and operator process, then release it to the manufacturers while at the same time going through their own preparations. But it's a different process, which is why manufacturers can end up releasing their products before the source code is made available to the public.
Too Funny!
[email protected] pic of "Francis Sawyer" aka Phsyco!
Too Funny!!
Closing thread to avoid inevitable flaming war due to post being about Honeycomb. Good overall question though.

[EMU] ResidualVM

Found this on another site (SOURCE - droidgamers) and thought would share. No onscreen controls as uses hardware keys (early port's). have not got time to test at mo but if the Xperia Play Keys dont work straight off you can remap unworking buttons with Gamekeyboard.
{
"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"
}
ResidualVM is another emulator that is a cross-platform 3D interpreter which allows you to play LucasArts' Lua-based 3D adventures games and has had a team working on it for awhile now. As with all things relating to emulators, the inevitable question arises about an Android version. Well it seems some users over on the ResidualVM forums have taken it upon themselves to unofficially port the emulator over in the hopes that the ResidualVM team picks it up and makes an official version from it. However, the unofficial version works very well and you can grab it and play a little Grim Fandango on your Android device if you're up for it.
Of course this is still a work in progress and there happens to be no overlay with on-screen controls that you can use to play the game. The solution to this is to either use a physical controller or an application like Game Keyboard to have a custom overlay that you can use to play the game. You will also need a fairly high-end Android device to run everything as full speed. Our tipster has it running nice and smooth on a Samsung Galaxy S II so you don't need a bleeding edge Android device to run it well, just a decent high-end one at least.
If the current coder of the unofficial Android version decided to merge his port with the code base of the ResidualVM team's version, we could see an official version of ResidualVM not too long from now. Until that happens though, we have an unofficial version to toy around with. Of course if you aren't technically inclined when it comes to emulators, especially those that are a work in progress, you might want to wait on grabbing this one. If you're up for mucking around with this unofficial version, and playing a little Grim Fandango, hit up the official forums below and on page 4 and 5 of the thread there are links to the different ports.
Click to expand...
Click to collapse
Link to the original - http://forums.residualvm.org
Have attached the Apks below incase the Dropbox link on original forum go's down
Thanks for the share!

Next Version of Android is ‘KitKat’ – Android 4.4 (Its Official)

{
"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"
}
Android KitKat ​
Google has just announced that the next version of Android will be called KitKat and not Key Lime Pie, as rumoured earlier. Also, the next Android version number is 4.4 not 5.0, indicating that KitKat is not going to be a huge jump but a smaller upgrade.
​
The search giant has also placed the KitKat Android version statue along with previous versions in the Mountain View. Android boss Sundar Pichai posted a photo of the same on his Twitter account today.
In this tweet and on his Google+ account, Pichai revealed that Android has now crossed 1 billion device activations. This is up from 900 million activations figure shared at Google I/O 2013 earlier this year.
“… All this Android innovation is driving tremendous ecosystem momentum and I’m excited to share that together we’ve now passed 1 Billion Android device activations. Huge thanks to the entire Android community from the hardware manufacturers, chip makers and carriers to the developers and content creators to all of you – our Android users around the world – for making this possible,” Sundar wrote on Google+.
Android KitKat
Let see how Sony give update to Android 4.4 KitKat
I don't think getting our mobile officially this version...
I thought Google would release 5.0 but they troll me xD I hope Sony will give the list of device's that are updating to 4.4 and hope there will be XL.
Stop dreaming guys.We're lucky if will get android 4.3 official.And since the development doesn't seems too bright,I'm considering selling my XL...I'll just wait for a little longer to see what's going on.Peace!
And about 5.0 troll,Android might run out of ideas...hope next version won't be 4.5,etc ...
This dream is a beautiful thing . I believe that it will get Android 4.3 and 4.4 on our Xperia L.

3Minit battery mod (compatibility)

Those that have been around Android for a while know that in the days prior to Lollipop, we could use custom batteries. This was one of the things that we enjoyed and made our devices stand out.
In Lollipop, Google took that away and while we still have a few custom batteries (circle, dotted, landscape, etc) we don't have as many.
Cue the 3Minit battery mod which promised to fill this void and does it well.
{
"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"
}
The problem with it was not the app nor the code behind it but the maintainers behind it. Some decided to play God with it and hold it over people's head. Things like "I'm not providing support for this ROM" were said for no real reason but because they didn't like an individual involved with the ROM.
I and many members of the open source community saw this as petty BS. If you're going to provide a mod then is either all or nothing. If you don't want to provide support then take your toys and keep it to yourself.
Well long story short, this is no longer something we have to deal with. Thanks to the help of my friend and fellow developer @bigrushdog and the actual 3Minit developer @gharrington , open source developers can now add the necessary code to make the app work flawlessly in their custom ROM.
No begging some random user to add support or petty games of favoritism.
All you (the custom ROM developer) would have to do is cherry pick these two commits and that's it!
https://github.com/AICP/frameworks_base/commit/91cf8b844a6eff038f5411d9a58883979942cc07
https://github.com/AICP/frameworks_base/commit/b9872b97d104f7a9c07e8fa92cfb55fb37c83735
Direct your users to the support thread for general app support and/or links to the app
http://forum.xda-developers.com/showthread.php?t=2799958
Out of courtesy for the great work that @gharrington has done, maybe throw a thanks in your thread for him
Enjoy and long live open source!!
Mazda said:
Those that have been around Android for a while know that in the days prior to Lollipop, we could use custom batteries. This was one of the things that we enjoyed and made our devices stand out.
)
Click to expand...
Click to collapse
Is this still applicable for nougat ?
When I try to cherry-pick the commits I get 'fatal: bad object " error.

Petition for vivo to release sourcecode

https://www.change.org/p/vivo-obtai...m_medium=copylink&utm_campaign=share_petition
Above is the link for a petition asking vivo to release sourcecode. They are stubborn about not releasing sourcecode, let's push them to provide us sourcecode, we don't want to use their crappy stock rom. Let's everyone sign above petition in large number!
vvvvv5 said:
https://www.change.org/p/vivo-obtai...m_medium=copylink&utm_campaign=share_petition
Above is the link for a petition asking vivo to release sourcecode. They are stubborn about not releasing sourcecode, let's push them to provide us sourcecode, we don't want to use their crappy stock rom. Let's everyone sign above petition in large number!
Click to expand...
Click to collapse
Great effort. Just now signed it.
Do keep us updated regarding any progress in this matter.
Signed. Hope vivo notices this petition.
signed!
signed
Signed!
Signed
I don't have the device but I have signed.
Holding out for a win so I can finally buy this device with that android freshness
Signed!
Signed! Fingers crossed we get it. Got my global version coming in during the next week or so
Signed!
Don't own the device but I still signed it. A phone like this deserves every bit of freshness and as a lover of bezel less phones I'd consider buying this one as long as there's an active development going on.
Also you might want to consider sharing the petition on social media such as Twitter. Don't think it'll be too difficult finding the people who already own a nex.
Sent from my Xiaomi MI MIX using XDA Labs
Signed
191...!!
Lets keep going share the link on all social media platforms . Tagg vivo everywhere as possible
Pman said:
I don't have the device but I have signed.
Holding out for a win so I can finally buy this device with that android freshness
Click to expand...
Click to collapse
This is aimed at all of vivo's source code. I've been chatting with their support on facebook (however, i dont know how official their support is) and showing them the petition progress.
[email protected]
[email protected]
I email these addresses nearly daily. I suggest everyone else add to the bombardment.
Answer from Vivo's devs ...
{
"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"
}
Signed, fingers crossed
Guys I am user of vivo y51l they didnt release our kernel sources yet signed many petitions sended many mails but they are not releasing source they are not upgrading the android versions of our device we (vivo y51 users) still stuck on lollipop. I ha e signed the petition
Signed it too.
If they refuse to release the source code, would there ever be a way for us to install a custom rom? Is it a matter of too much work or simply impossible?

Categories

Resources