Database Info

Open source softwares on Android platform?

Hi everybody!
It's my first post here, I'm quite a noob at all these Android things, but I got my HTC Hero last year and have been using it quite a lot since then.
I'm also fond of FLOSS (Free/Libre/Open Source Software), and I always try to find an open source equivalent to what I'm using. That's how I switched to Ubuntu Linux 6 years ago and never came back to Windows
I've been looking on the Web, reading Android news websites, and I realized they never talk about open source software being developed for Android phones. At most, they will talk about free (as in beer) softwares, but most of the time these are ad-supported or quickly become ad-supported if they're popular.
For instance, I looked for a music player (cause the one offered by HTC is quite slow and poorly reads OGG music -- yes I'm also in open formats!), and I could only find ad-supported free-ish softwares (MixZing player for instance)... but no open source choice!
On Linux, there are dozens of music players, and of course they're all open source, so you just choose the one you like the best, and even if it doesn't suit you perfectly, you can modify it or develop a plugin for it!
I was wondering if all that was because of the Android Market. Could it be possible to push an open source application on the Android Market? Would it be accepted?
Anyways, to summarize: Is there an open source community on Android?
Thanks in advance!

I'd say yes, you can find many oss in android market, but generally the source is in devs personal page. For instance my apps are open-source, the rom hackers generally give out their source, and more. However i don't know if there are oss apps for all categories...

Hi!
Thanks for your answer! (and congrats for the supertux port )
I'm pretty concerned about the multimedia part... So far:
MixZing Player ==> Ad supported, closed sources
Tune Wiki ==> Ad supported, closed sources
Astro Player ==> Commercial software, closed sources
Cubed ==> Closed sources
etc.
The only one I see was Rock On, which used to be closed sources until the project was discontinued (now the sources are available on github I guess).
As for the other softwares, a lot of them are created by people who think they're going to be rich by selling 0.99 USD softwares... therefore all these softwares are (obviously) closed-sources!

not to be a smart ass but, as long as it works, does it really matter if the source is available?
Yes FOSS is great but if there's a closed source app that does the job I'll use it, there's nothing wrong with closed source vs open when it comes to functionality

Of course, it's mainly a philosophical/ethical topic.
But to give you an example, MixZing recently decided to add an ad-supported system. In the initial release after this system was applied, ads were displayed every 10 seconds, it became almost unusable!
Of course, because a lot of people complained, the MixZin developers changed that. Yet, it's still heavily invaded with ads everywhere...
Another thing is that if you like a software but think it lacks a functionality, with open source you can add it. Of course, it requires technical skills, but the most important thing is that it is possible. With closed source, the only thing you can do is to send a feedback to the developers, then cross your fingers and hope that your request will be implemented in the next version.
A last thing: if the software is discontinued (e.g. the main developers lack of time to keep maintaining the software), the source is available for anybody to maintain it. With closed sources, well... use your software until the next Android update tells you it's too old to run on your system!
By the way, I should twist my fingers 7 times before typing anything: the main developer of RockOn created a project called ^3 (Cubed) which is open source as well, and which has evolved a lot since the last time I checked it! It might become my music player of choice!

I personally use Music Mod. I'm not sure if it's open or not, it's based on the stock music player.
As for open source vs not, I use the best tool for the job. I've used Linux for 11 years and Unix for years before that but I'm no source code tree hugging hippy..
There are many open source software.. I'd have to guess most on code.google.com are open..

arcMedia is based off ffmpeg and so should be OSS
(appbrain playing up today so link here)
http://www.androidzoom.com/android_applications/multimedia/arcmedia_jpez.html

【ROM 4.3.1【UN-OFFICIAL PURE AOSP】InsomniaAOSP【10/22/13 v.1.0】

【ROM 4.3.1【UN-OFFICIAL PURE AOSP】InsomniaAOSP【10/22/13 v.1.0】
{
"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"
}
Open Source
What is the Android Open Source Project?
We use the phrase "Android Open Source Project" or "AOSP" to refer to the people, the processes, and the source code that make up Android.
The people oversee the project and develop the actual source code. The processes refer to the tools and procedures we use to manage the development of the software. The net result is the source code that you can use to build cell phone and other devices.
Why did we open the Android source code?
Google started the Android project in response to our own experiences launching mobile apps. We wanted to make sure that there would always be an open platform available for carriers, OEMs, and developers to use to make their innovative ideas a reality. We also wanted to make sure that there was no central point of failure, so that no single industry player could restrict or control the innovations of any other. The single most important goal of the Android Open-Source Project (AOSP) is to make sure that the open-source Android software is implemented as widely and compatibly as possible, to everyone's benefit.
You can find more information on this topic at our Project Philosophy page.
What kind of open-source project is Android?
Google oversees the development of the core Android open-source platform, and works to create robust developer and user communities. For the most part the Android source code is licensed under the permissive Apache Software License 2.0, rather than a "copyleft" license. The main reason for this is because our most important goal is widespread adoption of the software, and we believe that the ASL2.0 license best achieves that goal.
You can find more information on this topic at our Project Philosophy and Licensing pages.
Why is Google in charge of Android?
Launching a software platform is complex. Openness is vital to the long-term success of a platform, since openness is required to attract investment from developers and ensure a level playing field. However, the platform itself must also be a compelling product to end users.
That's why Google has committed the professional engineering resources necessary to ensure that Android is a fully competitive software platform. Google treats the Android project as a full-scale product development operation, and strikes the business deals necessary to make sure that great devices running Android actually make it to market.
By making sure that Android is a success with end users, we help ensure the vitality of Android as a platform, and as an open-source project. After all, who wants the source code to an unsuccessful product?
Google's goal is to ensure a successful ecosystem around Android, but no one is required to participate, of course. We opened the Android source code so anyone can modify and distribute the software to meet their own needs.
What is Google's overall strategy for Android product development?
We focus on releasing great devices into a competitive marketplace, and then incorporate the innovations and enhancements we made into the core platform, as the next version.
In practice, this means that the Android engineering team typically focuses on a small number of "flagship" devices, and develops the next version of the Android software to support those product launches. These flagship devices absorb much of the product risk and blaze a trail for the broad OEM community, who follow up with many more devices that take advantage of the new features. In this way, we make sure that the Android platform evolves according to the actual needs of real-world devices.
How is the Android software developed?
Each platform version of Android (such as 1.5, 1.6, and so on) has a corresponding branch in the open-source tree. At any given moment, the most recent such branch will be considered the "current stable" branch version. This current stable branch is the one that manufacturers port to their devices. This branch is kept suitable for release at all times.
Simultaneously, there is also a "current experimental" branch, which is where speculative contributions, such as large next-generation features, are developed. Bug fixes and other contributions can be included in the current stable branch from the experimental branch as appropriate.
Finally, Google works on the next version of the Android platform in tandem with developing a flagship device. This branch pulls in changes from the experimental and stable branches as appropriate.
You can find more information on this topic at our Branches and Releases.
Why are parts of Android developed in private?
It typically takes over a year to bring a device to market, but of course device manufacturers want to ship the latest software they can. Developers, meanwhile, don't want to have to constantly track new versions of the platform when writing apps. Both groups experience a tension between shipping products, and not wanting to fall behind.
To address this, some parts of the next version of Android including the core platform APIs are developed in a private branch. These APIs constitute the next version of Android. Our aim is to focus attention on the current stable version of the Android source code, while we create the next version of the platform as driven by flagship Android devices. This allows developers and OEMs to focus on a single version without having to track unfinished future work just to keep up. Other parts of the Android system that aren't related to application compatibility are developed in the open, however. It's our intention to move more of these parts to open development over time.
When are source code releases made?
When they are ready. Some parts of Android are developed in the open, so that source code is always available. Other parts are developed first in a private tree, and that source code is released when the next platform version is ready.
In some releases, core platform APIs will be ready far enough in advance that we can push the source code out for an early look in advance of the device's release; however in others, this isn't possible. In all cases, we release the platform source when we feel the version has stabilized enough, and when the development process permits. Releasing the source code is a fairly complex 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.
How does the AOSP relate to the Android Compatibility Program?
The Android Open-Source Project maintains the Android software, and develops new versions. Since it's open-source, this software can be used for any purpose, including to ship devices that are not compatible with other devices based on the same source.
The function of the Android Compatibility Program is to define a baseline implementation of Android that is compatible with third-party apps written by developers. Devices that are "Android compatible" may participate in the Android ecosystem, including Google Play; devices that don't meet the compatibility requirements exist outside that ecosystem.
In other words, the Android Compatibility Program is how we separate "Android compatible devices" from devices that merely run derivatives of the source code. We welcome all uses of the Android source code, but only Android compatible devices -- as defined and tested by the Android Compatibility Program -- may participate in the Android ecosystem.
How can I contribute to Android?
There are a number of ways you can contribute to Android. You can report bugs, write apps for Android, or contribute source code to the Android Open-Source Project.
There are some limits on the kinds of code contributions we are willing or able to accept. For instance, someone might want to contribute an alternative application API, such as a full C++-based environment. We would decline that contribution, since Android is focused on applications that run in the Dalvik VM. Alternatively, we won't accept contributions such as GPL or LGPL libraries that are incompatible with our licensing goals.
We encourage those interested in contributing source code to contact us via the AOSP Community page prior to beginning any work. You can find more information on this topic at the Getting Involved page.
How do I become an Android committer?
The Android Open Source Project doesn't really have a notion of a "committer". All contributions -- including those authored by Google employees -- go through a web-based system known as "gerrit" that's part of the Android engineering process. This system works in tandem with the git source code management system to cleanly manage source code contributions.
Once submitted, changes need to be accepted by a designated Approver. Approvers are typically Google employees, but the same approvers are responsible for all submissions, regardless of origin.
You can find more information on this topic at the Submitting Patches page.
Compatibility
What does "compatibility" mean?
We define an "Android compatible" device as one that can run any application written by third-party developers using the Android SDK and NDK. We use this as a filter to separate devices that can participate in the Android app ecosystem, and those that cannot. Devices that are properly compatible can seek approval to use the Android trademark. Devices that are not compatible are merely derived from the Android source code and may not use the Android trademark.
In other words, compatibility is a prerequisite to participate in the Android apps ecosystem. Anyone is welcome to use the Android source code, but if the device isn't compatible, it's not considered part of the Android ecosystem.
What is the role of Google Play in compatibility?
Devices that are Android compatible may seek to license the Google Play client software. This allows them to become part of the Android app ecosystem, by allowing users to download developers' apps from a catalog shared by all compatible devices. This option isn't available to devices that aren't compatible.
What kinds of devices can be Android compatible?
The Android software can be ported to a lot of different kinds of devices, including some on which third-party apps won't run properly. The Android Compatibility Definition Document (CDD) spells out the specific device configurations that will be considered compatible.
For example, though the Android source code could be ported to run on a phone that doesn't have a camera, the CDD requires that in order to be compatible, all phones must have a camera. This allows developers to rely on a consistent set of capabilities when writing their apps.
The CDD will evolve over time to reflect market realities. For instance, the 1.6 CDD only allows cell phones, but the 2.1 CDD allows devices to omit telephony hardware, allowing for non-phone devices such as tablet-style music players to be compatible. As we make these changes, we will also augment Google Play to allow developers to retain control over where their apps are available. To continue the telephony example, an app that manages SMS text messages would not be useful on a media player, so Google Play allows the developer to restrict that app exclusively to phone devices.
If my device is compatible, does it automatically have access to Google Play and branding?
Google Play is a service operated by Google. Achieving compatibility is a prerequisite for obtaining access to the Google Play software and branding. Device manufacturers should contact Google to obtain access to Google Play.
If I am not a manufacturer, how can I get Google Play?
Google Play is only licensed to handset manufacturers shipping devices. For questions about specific cases, contact [email protected].
How can I get access to the Google apps for Android, such as Maps?
The Google apps for Android, such as YouTube, Google Maps and Navigation, Gmail, and so on are Google properties that are not part of Android, and are licensed separately. Contact [email protected] for inquiries related to those apps.
Is compatibility mandatory?
No. The Android Compatibility Program is optional. Since the Android source code is open, anyone can use it to build any kind of device. However, if a manufacturer wishes to use the Android name with their product, or wants access to Google Play, they must first demonstrate that the device is compatible.
How much does compatibility certification cost?
There is no cost to obtain Android compatibility for a device. The Compatibility Test Suite is open-source and available to anyone to use to test a device.
How long does compatibility take?
The process is automated. The Compatibility Test Suite generates a report that can be provided to Google to verify compatibility. Eventually we intend to provide self-service tools to upload these reports to a public database.
Who determines what will be part of the compatibility definition?
Since Google is responsible for the overall direction of Android as a platform and product, Google maintains the Compatibility Definition Document for each release. We draft the CDD for a new Android version in consultation with a number of OEMs, who provide input on its contents.
How long will each Android version be supported for new devices?
Since Android's code is open-source, we can't prevent someone from using an old version to launch a device. Instead, Google chooses not to license the Google Play client software for use on versions that are considered obsolete. This allows anyone to continue to ship old versions of Android, but those devices won't use the Android name and will exist outside the Android apps ecosystem, just as if they were non-compatible.
Can a device have a different user interface and still be compatible?
The Android Compatibility Program focuses on whether a device can run third-party applications. The user interface components shipped with a device (such as home screen, dialer, color scheme, and so on) does not generally have much effect on third-party apps. As such, device builders are free to customize the user interface as much as they like. The Compatibility Definition Document does restrict the degree to which OEMs may alter the system user interface for areas that do impact third-party apps.
When are compatibility definitions released for new Android versions?
Our goal is to release new versions of Android Compatibility Definition Documents (CDDs) once the corresponding Android platform version has converged enough to permit it. While we can't release a final draft of a CDD for an Android software version before the first flagship device ships with that software, final CDDs will always be released after the first device. However, wherever practical we will make draft versions of CDDs available.
How are device manufacturers' compatibility claims validated?
There is no validation process for Android device compatibility. However, if the device is to include Google Play, Google will typically validate the device for compatibility before agreeing to license the Google Play client software.
What happens if a device that claims compatibility is later found to have compatibility problems?
Typically, Google's relationships with Google Play licensees allow us to ask them to release updated system images that fix the problems.
Compatibility Test Suite
What is the purpose of the CTS?
The Compatibility Test Suite is a tool used by device manufacturers to help ensure their devices are compatible, and to report test results for validations. The CTS is intended to be run frequently by OEMs throughout the engineering process to catch compatibility issues early.
What kinds of things does the CTS test?
The CTS currently tests that all of the supported Android strong-typed APIs are present and behave correctly. It also tests other non-API system behaviors such as application lifecycle and performance. We plan to add support in future CTS versions to test "soft" APIs such as Intents as well.
Will the CTS reports be made public?
Yes. While not currently implemented, Google intends to provide web-based self-service tools for OEMs to publish CTS reports so that they can be viewed by anyone. CTS reports can be shared as widely as manufacturers prefer.
How is the CTS licensed?
The CTS is licensed under the same Apache Software License 2.0 that the bulk of Android uses.
Does the CTS accept contributions?
Yes please! The Android Open-Source Project accepts contributions to improve the CTS in the same way as for any other component. In fact, improving the coverage and quality of the CTS test cases is one of the best ways to help out Android.
Can anyone use the CTS on existing devices?
The Compatibility Definition Document requires that compatible devices implement the 'adb' debugging utility. This means that any compatible device -- including ones available at retail -- must be able to run the CTS tests.
Click to expand...
Click to collapse
SOURCE
Click to expand...
Click to collapse
INITIAL RELEASE 10/22/2013 @ 5:54 am
Click to expand...
Click to collapse
InsomniaAOSP v1.0
Click to expand...
Click to collapse
Standard Core gapps
Click to expand...
Click to collapse
WORK IN PROGRESS ALL MAINTAINERS COLLABORATE IN GIVING CREDITS
Click to expand...
Click to collapse
Android Open Source Project
CodeKill13
Ubuntu
Linux Mint
Github
Flar
Peter Poelman
itsme
Stericson
JesusFreke
CyanogenMOD
AOKP
PacROM
Rootbox
Evervolv
ParanoidAndroid
slimroms
Team-Hydra -Device Trees-Kernel
Team Horizon
The mikmik
AndroidSpin
Android Police
VanirAOSP
CodefireXexperiment
albinoman887
TheMuppets
Htc
Samsung
TheBr0ken
snuzzo
T-Macgnolia
ljjehl
Saif Kotwal
pr0xy man1Ac
Djwuh
ammikam
!I am not responsible for anything that happens to you or your device as a result of flashing this rom. If you decide to install this rom then you've taken responsibility for any risks involved !!

reserrrrved

Nice to see another 4.3.1 rom for our sensation
Keep the good work, will flash it tommorow
Sent from my HTC Sensation using XDA Premium 4 mobile app

Looks good shall test in the morning , thanks
Sent from my HTCSensation using Tapatalk

Tried it already from DK's thread on other forum.
There are issues with languages, not everything is translated to russian for instance.
Also there are plenty of CM ringtones, why is that?
WiFi hotspot is not working, cannot even detect an access point.
Launcher has weird wallpaper alingment, that doesn't fit at very left or right...
All these are minor issues to polish in the future.
Oh, why there's a theme engine, is it a part of AOSP now or a bonus from CM?
I'm glad see another pure (or maybe not so much) AOSP ROM.
Since there's no new SuperXE ROMs we welcome the new effort with a big smile on our never well shaved faces.

Noobel said:
Tried it already from DK's thread on other forum.
There are issues with languages, not everything is translated to russian for instance.
Also there are plenty of CM ringtones, why is that?
WiFi hotspot is not working, cannot even detect an access point.
Launcher has weird wallpaper alingment, that doesn't fit at very left or right...
All these are minor issues to polish in the future.
Oh, why there's a theme engine, is it a part of AOSP now or a bonus from CM?
I'm glad see another pure (or maybe not so much) AOSP ROM.
Since there's no new SuperXE ROMs we welcome the new effort with a big smile on our never well shaved faces.
Click to expand...
Click to collapse
hahahah..I agree with this " our never well shaved faces".. New ROM to play with....Good job

Nice to see it's playing again. Don't let our Senny dead.

oooo another AOSP for my Sensation! Bring it on! Thank you!!
---------- Post added at 04:35 AM ---------- Previous post was at 04:34 AM ----------
Any listing of what is working and what is not?

Good work, i'll try it

anyone got any feedback on this one?

Sage said:
anyone got any feedback on this one?
Click to expand...
Click to collapse
Yes, +1, feedback is important for the rom cooker
Is this really pure AOSP without any mods?
I mean "stock" android 4.3.1 ?

Just for the record that I am not running this rom anymore and the bugs I noticed and know of are:
Quit hours not working
Clock Widget settings gives a FC
Setting the navigation bar in Insomnia setting will FC the system UI and can't be recovered and need a factory reset
Browser and the Mail-App have a screen glitches.
I saw this InsomniaAOSP purity test!

Announcement of Jafier Roms

Calling up and all the moderators at XDA we have started our project and those who are interested opportunities
The name of the ROM is JafierRoms and we have intentions to make it available for vast number of devices including those omap4xxx devices as well as those device which have safetrap and locked device which can run 2initd recoveries as well
Our source is based on CyanogenMod 11 and as soon as the source get finalized and cleaning up is done we would start a build for the nexus series as the latest once even the tabs too ,lg g2 ,etc.
As soon as the cleaning up is done u ppl will be able too see builds on JFtexx and all the JFs
s3 variant and tabs will followed too
To james carter I request if we can have a space in custom ROM centrals and can be displayed at the portal so we get intiallized and funded
we will only have the beta versions for this month.
Followed by weeklies and all things done and up 2 months from now ppl can see nigtlies as well
Members and core team
Mohhamad Rehan Madhar (founder)
Raj P (initializing the source forks)
Akshay Chordiya (Developer of apps such as jafier, active notifications and Automaton)
Jishnu Sur (feature porting and camera enhancement)
Adarsh or Audio God ( developer of Sensonic HD Roms and Our community maintainer would not maintain any devices)
Mao Chenxi (fixes here and there)
Napstar (for Xperia devices)
Planned members to include:-
Mohhamad Abid (developer of switcher)
RSen ( developer of Open mic+)
And philz if he agrees can't contact him though
Features:-
1)Stock cm features
2)active display replaced by active notifications and enhancement to make it more like MotoX. As the app by Akshay was made open source
3) full automation on Locking and unlocking the devices and hand and wave gesture there won't be a app but code for this which would be placed in framework and SystemUi, even the gesture would work in gallery
4) Power shell Replaces Superuser
5) a feature in security would be placed which will be like whenever a wrong pin or password is detected at the keygaurd a photo and location of the device would be sent to ur email address
6) A launcher which would never have the skin like the aosp or trebuchet launcher but will be based on Aosp launcher
7) stock icons will be replaced by something new
Planned features :-
1) active notifications and touchless control like feature may get integrated in the nightlies (yes toucless control is possible with pocket sphinx)
2)our very own gapps with Aroma installer where selecting the Google now launcher would be optional
3)delta update app can be created if we get funded and able to get Jenkins server I am bankrupt
4) Our touch less control gets integrated with Google Now that's why there may not be a need of the Gel Launcher
5) don't get over excited we won't have every feature of Moto X or any other phone
And finally nothing from omni and any other Roms only small and tiny fixes to dalvik bionic and art would get cherry-picked
And speaking of cherry-picks we will have gerrit code rewiev by March 10 for sure
Our source is located at
https://github.com/JafierRoms
Sent from my Nexus 5 using XDA Premium 4 mobile app

Regardless of how you call them, placeholder threads are not allowed on XDA. Please feel free to open this thread again for supported devices, in the correct areas, once the ROM is ready. Thread closed.

[PORT][MOD] Xperia Z5 UI AND APPS PORT

Introduction:-
Hello Samsung Galaxy Grand 2 Community,
Here I present the Latest Sony Xperia Z5 Port which is based on Lollipop 5.1 for our Cyanogen Mod 12.1, Xperia is well known and famous for customizing their User Interface, Being on default User Interface of CyanogenMod is boring, So use this port and Enjoy the new refreshed looks on your Device.... ​
POST 1:- Introduction and Features
POST 2:- Screenshots
POST 3:- Downloads
POST 3:- Instructions and Simple Guide
POST 3:- Changelogs
Features:-
• Xperia Z5 SystemUi
• Xperia Z5 Home
• Xperia Z5 Setup Wizard
• Xperia Z5 Album
• Xperia Z5 Music
• Xperia Z5 Videos
• Xperia Z5 Clockwidgets
• Xperia Z5 SemcClock
• Xperia Z5 Calender
• Xperia Z5 KeyBoard
• Xperia Z5 Backup and Restore
• Xperia Z5 Clock
• Xperia Z5 Photo Editor
• Xperia Z5 Weather App
• Xperia Z5 Care
• Xperia Z5 Media Sounds
• Xperia Z5 Live Wallpaper
• Xperia Z5 Calculator
• Xperia Z5 World Clock Widget
• Xperia Z5 Top Contacts Widget
• Xperia Z5 Wallpaper
• Xperia MovieCreator
• Xperia What's New​Credits:-
• @STRYDER~007 for Superuser mod and Z5 UI port
• @serajr for no OSB Home
• @mukulsoni for Cm12.1
• @gamzekal for Z5 deodexed system dump
• @alone_in_dark for Xperia Blue Bootanimation
• Sony for beautiful UI
• Samsung for our Device
NOTE- DO NOT USE OR SHARE ANY PART OF MY WORK IN ANY ROM OR ANY MOD WITHOUT MY PERMISSION!!
Know Bugs
Same as CM12.1
Second SIM Voice
Off mode charging
Click to expand...
Click to collapse
Dont Forget to HIT Thanks Button :good: :good: :laugh:

ScreenShots:- I am sure you are gonna love this mod
• Z5 Xperia Sytem UI with Particle effect
• Xperia Z5 Album
• Xperia Z5 Home Launcher
• Xperia Z5 Startup Guide
• Xperia Z5 Music and Videos
• Xperia Z5 Movie creator backup and restore clock widget
• Xperia Z5 Whats new app+ Weather + Clock
• Xperia Z5 Keyboard and My Settings

Downloads:-
Samsung Drivers
Download ApeXPreia Mod
Download CM 12.1
Download ODIN V3.9
CWM-6.0.5.1-mukul
Disclaimer:-
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,thermonuclear war, or you getting fired because the alarm app failed!!
*Please make nandroid backup before flashing this as a precaution!
*Try this ROM at your own risk!
Click to expand...
Click to collapse

Alright Guyz, I will explain you in detail how to Install cm12.1 and ApexPeria Mod on our Grand 2
Installing recovery:-
•First of all Download the required tools from POST 3(Samsung Drives, ODIN, CWM Recovery, CM12.1 AOI.ZIP and ApeXperia MOD) on your PC for tasting the Z5 Looks.
•Install the Samsung Drivers on the Computer.
•Place Cm12.1, Gapps AOI.ZIP and ApeXPeria mod on SD card of your Phone.
•Extract the ODIN using Winzip or Winrar.
•Run the ODIN from the Extractedfolder.
•Uncheck the opton RE-PARTITION(important) and select AP/PDA, select the downloaded recovery.
•Turn off the phone and press the key combination “”Volume Down+ Home + Power””, This will boot the device in download mode.
•ODIN will detect your Phone as COM[x] and click on start and wait till you get the PASS message.
•Disconnect the phone and press the key combination “”Volume up+ Home + Power”” to boot the phone in Recovery mode,
•Finally you have a working recovery on your device which is required for flashing.
Installing CyanogenMOD and ApexPeria Z5 Mod:-
•Once you are booted in Recovery Select Mount and Storage and format Data, Cache, Dalvik,System and Boot.
•Use the Volume keys and power button to navigate.
•Install the Cm12.1, Gapps.
Now u have two options for cyanogemod
• If u want single Sim then flash AOI.zip immediately after flashing Gapps AND install ApeXPeria mod.
Done you have Z5 looks on ur device

Reserved for ChangeLog

This looks fresh great work man

Nice work....something new..good
Sent from my SM-G7102 using Tapatalk

Thanks brother..

Yes, sonething new and latest in the Market

This is perhaps a stupid question, but is this legal? I mean, is any Sony code or other property used? If so, is it properly licensed to be used like this?
I don't want to kill the enthusiasm, but it's in everybody's interest to not get the xda developers community into trouble by violating copyrights.

I do appreciate you concern towards xda community!! For your kind information Android is open source and Sony do believe in open source.
That is the reason they release their sources and allow the developers to develop further. They also allow us to unlock bootloaders for installing custom softwares.
Everything is open source in Xda and Android

do you think rooting is legal?

It's good to hear that Sony releases the source code (perhaps in honor of GPL). However, does this also include the Sony and Xperia brand names and graphics? Compare for example to the relation between Red Hat Enterprise Linux and Fedora Linux (which as you may know is the Red Hat sponsored, community driven sibling to RHEL). Fedora is not allowed to include any Red Hat brand name or logos even though Red Hat contributes a lot of code to Fedora.
I think it is important to distinguish between the following completely separate issues:
1. Sony releasing their software under open source (maybe a requirement from their products being based on GPL software, also increases their goodwill and brand name).
2. Allowing their customers to unlock bootloaders (increases the value of their products and can also be considered fair use since you own the device, potentially increasing sales).
3. Allowing the use of their brands and graphic identities on other devices (hard to argue that it has a positive impact on the Sony brand value or sales of their product).
Unless you can provide some kind of proof that they really allow (3) above I seriously doubt that it is allowed.
I am not a Sony lawyer or anything, just a Cyanogenmod fan who enjoys unlocking bootloaders and flashing custom roms as much as everybody else in this community.

Bro, can I install your Mod over blisspop ROM?

mhult said:
It's good to hear that Sony releases the source code (perhaps in honor of GPL). However, does this also include the Sony and Xperia brand names and graphics? Compare for example to the relation between Red Hat Enterprise Linux and Fedora Linux (which as you may know is the Red Hat sponsored, community driven sibling to RHEL). Fedora is not allowed to include any Red Hat brand name or logos even though Red Hat contributes a lot of code to Fedora.
I think it is important to distinguish between the following completely separate issues:
1. Sony releasing their software under open source (maybe a requirement from their products being based on GPL software, also increases their goodwill and brand name).
2. Allowing their customers to unlock bootloaders (increases the value of their products and can also be considered fair use since you own the device, potentially increasing sales).
3. Allowing the use of their brands and graphic identities on other devices (hard to argue that it has a positive impact on the Sony brand value or sales of their product).
Unless you can provide some kind of proof that they really allow (3) above I seriously doubt that it is allowed.
I am not a Sony lawyer or anything, just a Cyanogenmod fan who enjoys unlocking bootloaders and flashing custom roms as much as everybody else in this community.
Click to expand...
Click to collapse
you guys can relax and enjoy this port
even though i dont own this device
rooting is not illegal nor is porting
people and myself have been doing it for years
so appreciate the dev and enjoy

Rooting is certainly not illegal.
Porting open source software is certainly not illegal.
Copying logotypes, graphics and brands is definitely illegal unless you have permission from the owner of the intellectual property. I am not saying this port is illegal, but it could be, unless Sony has explicitly allowed the use of their brand names and graphics when they released the source code of their software.

mhult said:
Rooting is certainly not illegal.
Porting open source software is certainly not illegal.
Copying logotypes, graphics and brands is definitely illegal unless you have permission from the owner of the intellectual property. I am not saying this port is illegal, but it could be, unless Sony has explicitly allowed the use of their brand names and graphics when they released the source code of their software.
Click to expand...
Click to collapse
search over xda,you will get tons of port apps from z5,z4,note 5 and other flagship devices.
---------- Post added at 12:16 AM ---------- Previous post was at 12:08 AM ----------
aswe77 said:
Bro, can I install your Mod over blisspop ROM?
Click to expand...
Click to collapse
you can give it a try..make a nandroid backup before and flash..it will help others blisspop users too.
---------- Post added at 12:19 AM ---------- Previous post was at 12:16 AM ----------
shau_rj said:
do you think rooting is legal?
Click to expand...
Click to collapse
it is legal but your warranty gets void...android is open source, you can do whatever you want to do with your device but at the end of the day,if something happens to your device then you will have to pay its fees in hospital(i mean service centre)because you lost your warranty.

as said by @neonkat , there are tons of xperia , htc, samsung, etc ports.
so i suggest u njoy the mod and appreciate the dev.
i also suggest that if u still have unsolved queries, u can start a thread on xda general and u will get much decorated ans. to your questions.
installing the mod, will report after usage. boot screen is cool.
also when on topic, nope rooting is not purely legal, its jus neglected under the name of risk....if it was then the companies wouldn't have a problem with rooting and would not void the warranty,
EDIT.....facing bootloop on cm12.1 AIO 1 rom.

I don't think rooting is illegal. Voiding warranty has nothing to do with it being legal. I guess some manufacturers would like rooting to be illegal, because it would give them greater control over their devices, but in many countries it is not legal for manufacturers to restrict what consumers can do with hardware they have paid for and are rightful owners of.
The reason why rooting voids warranties is because the manufacturers don't want to be responsible for the functioning of their products if they have been modified without the manufacturer approving the modification. It is exactly the same with cars, refrigerators and lots of other products.

Stuck on 'Android starting apps' and then xperia boot screen is shown n again 'android is starting apps'... waited for like 20mins.

[Completed] What is the difference between Stock Android and Cyanogenmod?

I'm pretty much a noob when it comes to android development, so please bear with me:silly:. As I understand, stock android is a generic firmware released by Google Inc. and not specific to any particular device. Similarly, CyanogenMod is also a generic firmware. Then what's the difference between the two?

prahladyeri said:
I'm pretty much a noob when it comes to android development, so please bear with me:silly:. As I understand, stock android is a generic firmware released by Google Inc. and not specific to any particular device. Similarly, CyanogenMod is also a generic firmware. Then what's the difference between the two?
Click to expand...
Click to collapse
Hi prahladyeri. This is from the Cyanogenmod Wiki
So what is the difference between Android and CyanogenMod?
About 1-2 times a year, the vanilla Android operating system (known as AOSP, or the Android Open Source Project) is internally developed, then released to the public, by Google. They provide the source code to anyone who wants to download it. The CyanogenMod community, comprised mostly of unpaid volunteers and enthusiasts from around the world, takes this newest Android code and "ports" it to dozens of new and older (aka "legacy") devices. At the same time, other CyanogenMod developers start adding features, fixes, and improvements that Google didn't include to the CyanogenMod code, which benefits all the devices. The CyanogenMod community has a whole infrastructure for people to build and test experimental versions, report bugs, and contribute back to the source code.
Sometimes features that started in CyanogenMod have appeared in newer version of "official" Android. And every time Android does a new "code dump" of their latest version, CyanogenMod benefits from Google's changes.
In this way, CyanogenMod is one (but not the only) community distribution of what started as vanilla AOSP. The Android community is vibrant, with numerous "modders" and "themers" and "performance enhancers" taking the source code and doing incredible things to it. Generally, there is a spirit of sharing knowledge and empowering people to experiment with controlling their devices, often giving old phones new life, and hopefully having fun in the process.
What does it all mean to me?
CyanogenMod is an alternative operating system intended to replace the one pre-installed on your smart phones and tablets. If you've got an older device that isn't getting updates anymore, or if your device seems unusually slow, or maybe you're sick of spyware, adware, and other unwanted garbage on your phone that you can't remove... Maybe your device is missing features or has been otherwise artificially limited in functionality. Perhaps you just could use a boost in performance. Or maybe you'd like to be more confident that your operating system has included some of the latest bug fixes.
If so, CyanogenMod might be for you.
Click to expand...
Click to collapse