Related
Hi,
I'm going to start building my own ROMs. I'd like to start from only official sources and drivers. Then add my own improvements and features. Here are a few questions before I can start:
1) I know there is a tool in AOSP to extract proprietary drivers. Can I extract Froyo drivers from G2x and use it with Gingerbread AOSP?
2) I see many users reporting that "XXX doesn't work" (XXX is things like radio, GPS, Wi-Fi) with custom ROMs. Are those issues caused by incompatibility between GB AOSP and Froyo drivers? Or caused by patches done by ROM makers?
3) Does Google provide official sources for Google Apps? Or official binaries to bundle with a ROM?
Thanks!
rhinology said:
Hi,
I'm going to start building my own ROMs. I'd like to start from only official sources and drivers. Then add my own improvements and features. Here are a few questions before I can start:
1) I know there is a tool in AOSP to extract proprietary drivers. Can I extract Froyo drivers from G2x and use it with Gingerbread AOSP?
2) I see many users reporting that "XXX doesn't work" (XXX is things like radio, GPS, Wi-Fi) with custom ROMs. Are those issues caused by incompatibility between GB AOSP and Froyo drivers? Or caused by patches done by ROM makers?
3) Does Google provide official sources for Google Apps? Or official binaries to bundle with a ROM?
Thanks!
Click to expand...
Click to collapse
First off this is a Q&A question, not a dev section issue...
1) Not really...
2) These are typically kernel issues...
3) yes they do, check the CM7 Nightly thread
rhinology said:
Hi,
I'm going to start building my own ROMs. I'd like to start from only official sources and drivers. Then add my own improvements and features. Here are a few questions before I can start:
1) I know there is a tool in AOSP to extract proprietary drivers. Can I extract Froyo drivers from G2x and use it with Gingerbread AOSP?
2) I see many users reporting that "XXX doesn't work" (XXX is things like radio, GPS, Wi-Fi) with custom ROMs. Are those issues caused by incompatibility between GB AOSP and Froyo drivers? Or caused by patches done by ROM makers?
3) Does Google provide official sources for Google Apps? Or official binaries to bundle with a ROM?
Thanks!
Click to expand...
Click to collapse
1. In general for Linux, there are 2 types of drivers, kernel space drivers and user space drivers. The Kernel space drivers are available via kernel source dump from manufacturers, however, the user space drivers are often proprietary so they are released as binary only. In case for G2x, the current official release from LG is Froyo, so often time, CM7 is hacked to work with Froyo user space drivers until an official GB version is released.
2. Because of #1, often times, CM7 team has to work around the limitations they have by writing new code. The new code is not tested as thoroughly as major manufacturers QA department (a whole team of professional testers) so CM team release their nightly builds to serve as open public beta to hammer out bugs for the newly released workarounds/patches. It's amazing what CM team has done without access to all the necessary files and sources.
3. Google Apps are proprietary Google software, so no source code will be available to them (until Google decides to open source their apps, which is 100% their right and decision). Because Google holds the rights to their software, they also have a say in the distribution of their software. CM originally bundled Google Apps with their CM releases, but Google decided not to allow a major independent team to bundle their software and sent CM a legal letter asking them to stop. Ever since, CM team decided to release just a bare AOSP portion without Google Apps. I have followed CM's example and also does NOT bundle Google Apps with my Hybrid AOSP ROM.
Thanks a lot!
Sounds like I'd better build a Froyo ROM first.
For #3, I learned that I can download Google Apps binaries provided by CM team. My question is: where did CM team get the binareis?
faux123 said:
1. In general for Linux, there are 2 types of drivers, kernel space drivers and user space drivers. The Kernel space drivers are available via kernel source dump from manufacturers, however, the user space drivers are often proprietary so they are released as binary only. In case for G2x, the current official release from LG is Froyo, so often time, CM7 is hacked to work with Froyo user space drivers until an official GB version is released.
2. Because of #1, often times, CM7 team has to work around the limitations they have by writing new code. The new code is not tested as thoroughly as major manufacturers QA department (a whole team of professional testers) so CM team release their nightly builds to serve as open public beta to hammer out bugs for the newly released workarounds/patches. It's amazing what CM team has done without access to all the necessary files and sources.
3. Google Apps are proprietary Google software, so no source code will be available to them (until Google decides to open source their apps, which is 100% their right and decision). Because Google holds the rights to their software, they also have a say in the distribution of their software. CM originally bundled Google Apps with their CM releases, but Google decided not to allow a major independent team to bundle their software and sent CM a legal letter asking them to stop. Ever since, CM team decided to release just a bare AOSP portion without Google Apps. I have followed CM's example and also does NOT bundle Google Apps with my Hybrid AOSP ROM.
Click to expand...
Click to collapse
rhinology said:
Hi,
I'm going to start building my own ROMs. I'd like to start from only official sources and drivers. Then add my own improvements and features. Here are a few questions before I can start:
1) I know there is a tool in AOSP to extract proprietary drivers. Can I extract Froyo drivers from G2x and use it with Gingerbread AOSP?
2) I see many users reporting that "XXX doesn't work" (XXX is things like radio, GPS, Wi-Fi) with custom ROMs. Are those issues caused by incompatibility between GB AOSP and Froyo drivers? Or caused by patches done by ROM makers?
3) Does Google provide official sources for Google Apps? Or official binaries to bundle with a ROM?
Thanks!
Click to expand...
Click to collapse
I've written a good guide for building cm7. (link in my signature)
Sent from my LG-P999 using XDA Premium App
I'm sorry if this has been answered somewhere else, but I have not been able to find this solution after a few days of searching.
I am building CM10 from source for Galaxy S II (I9100) with my own changes on a Linux system. It builds and runs fine using UserDebug signatures.
I wish to build the release version not the userdebug one, and I wish to use my own keys/certificates/Signatures (e.g. release.x509.pem)
After setting everything up, I build the ROM using the commands
. build/envsetup.sh
lunch 27
./build.sh i9100
Is there options or settings to trigger the Release build?
How do I get the build to use my own Signatures?
I understand how to re-sign an existing ROM, but wish to have my signatures be used for internal parts (media, platform, shared, etc.) plus use the builder to do everything automatically without any post processing.
I have not found or understood the Android nor Cyanogenmod documentation. I might be missing the key document.
Thank you for your time.
.
looking at make files and buildspec.mk.default
I'm still looking into solving this myself, but I'm not making much headway.
The search for android build_new_device gave me a links to look at and it is helping me understand the build a bit.
I am trying to understand how buildspec.mk.default is used. I've tried to find where TARGET_BUILD_VARIANT is set for the cm build of i9100 but apparently I am exceeding the limits of grep
Anyone have a suggestion or pointers for this?
Build a release version of cm10 for i9100 and use my own certificates/keys
(not userdebug or eng, but just user)
Thank you.
randombitsca said:
I'm sorry if this has been answered somewhere else, but I have not been able to find this solution after a few days of searching.
I am building CM10 from source for Galaxy S II (I9100) with my own changes on a Linux system. It builds and runs fine using UserDebug signatures.
I wish to build the release version not the userdebug one, and I wish to use my own keys/certificates/Signatures (e.g. release.x509.pem)
After setting everything up, I build the ROM using the commands
. build/envsetup.sh
lunch 27
./build.sh i9100
Is there options or settings to trigger the Release build?
How do I get the build to use my own Signatures?
I understand how to re-sign an existing ROM, but wish to have my signatures be used for internal parts (media, platform, shared, etc.) plus use the builder to do everything automatically without any post processing.
I have not found or understood the Android nor Cyanogenmod documentation. I might be missing the key document.
Thank you for your time.
.
Click to expand...
Click to collapse
Try posting this in your device forum
In the General section
That would give you more help I believe !
Sent from my MT11i using xda premium
What is OpenPDroid?
OpenPDroid is a set of modifications to the Android framework and libraries which allows fine-tuning of the data which applications are able to retrieve about your device, your account, your messages, and more. Specifically, it is a Privacy service provider (using the PDroid 1.51 interface) forked from CollegeDev's PDroid 2.0, which is itself an extension of Syvat's PDroid.
A word to the wise
I'm just adding this for those who are just looking at OpenPDroid, or are trying to work out how to get involved.
Mateor, wbedard and I are currently in the process of moving repositories etc to a github 'organisation' in order to make it much easier for users to know which are the latest patches, where to report issues, etc. I expect this will be done soon (in the next day or so), and I'll post more information then.
Thanks for your suggestions on ways of managing repositories, patches, etc.
What does it do?
When configured using either FFU5y's PDroid Manager or CollegeDev's PDroid 2.0 App (up to v1.52), OpenPDroid intervenes in API interactions by apps (e.g. when an app attempts to retrieve your location, phone number, or contacts) and provides either real data, empty data, fake data, or random data, depending on the user setting. Unlike apps which actually remove permissions, OpenPDroid does not actually modify the permissions that an app has and so is much less likely to cause the app to crash as a result of data access being denied.
Note that CollegeDev's PDroid 2.0 App does not officially support OpenPDroid, so please don't contact CollegeDev for support if you're having problems with PDroid 2.0 App with OpenPDroid. You can post here, and we may be able to help you.
PDroid Manager does officially support OpenPDroid.
The complete list of data and functions controlled by OpenPDroid can be found at the end of this post, in What (specifically) can I control with OpenPDroid?, but at present it is identical to that offered by PDroid 2.0
For a list of issues which have been identified, please see below the Known Issues.
What makes OpenPDroid different to CollegeDev's PDroid 2.0 or Syvat's PDroid
There are a few differentiators, some technical, and some are philosophical or pragmatic. Both are important
Technical
Two major security issues are fixed, which allow apps to bypass many or all PDroid or PDroid 2.0 settings. (We are in the process of notifying CollegeDev of these issues, and sample code will not be released for at least a week to give him a chance to fix the problems in PDroid 2.0. Fixes have been added to PDroid in auto-patcher, so if you are using PDroid please consider re-patching your ROM).
It is available for Android 4.2.1
Database access threading has been rewritten, as the implementation actually caused bottlenecks and didn't protect from simultaneous read-writes (which is generally the goal of this type of code)
A bug which was causing 'null pointer exceptions' to occur (but not a crash) is fixed.
Other code tidy-up or restructuring which doesn't change functionality
Non-technical
The intention of OpenPDroid is to have a PDroid version which is developed in the open, and which welcomes (although doesn't necessarily always adopt) user input - especially code. This means that the source for OpenPDroid versions in progress is on a public repository (Github at the moment), that changes are put into the Github as they are made, and that other people can contribute code to it. We also hope that by having engaging people more in the development process, there will be more eyes trying to understand the code, and so security-related issues will be identified and address more efficiently.
We also want to make the discussion/decision making processes for what is in and what is out transparent, so that users can understand why some things are included and others are not, and actually influence the decision-making process.
How do I install it?
There are two 'supported' ways to install OpenPDroid:
mateor's auto-patcher (available for OS X, Linux and Windows) is the recommended way if you are not familiar with building from source, and have a supported ROM (CM10, CM10.1, AOKP Jellybean 4.1.2, AOKP Jellybean 4.2.1, AOSP 4.1.2, and AOSP 4.2.1).
Patch and build a ROM from source (see How do I compile a ROM with OpenPDroid). Patches are provided for: CM10, CM10.1, AOKP jb, AOKP jb-mr1, AOSP 4.1.2, AOSP 4.2.1
If you are using a stock ROM, then someone may have implemented OpenPDroid into that ROM - and if they have, they deserve huge credit because it is a difficult and unpleasant job.
Currently we are not aware of any ROMs which include OpenPDroid: if you are aware of one, please notify us and we'll list it here.
There are several reasons your preferred ROM may not currently be supported. First, adding support for a ROM in auto-patcher requires building the ROM with the OpenPDroid patches. We are only able to do this if the source is available for the ROM. (Note: strictly speaking, it is possible to build patches for ROMs where source is not available, as for stock ROMs. However, for non-stock ROMs the rate of change makes this fairly unmaintainable).
Second, there are a great many ROMs out there and it is not possible for us to build for all these ROMs. However, if you are able to patch source and build, then you may be able to build a version of your preferred ROM with OpenPDroid support - and even better, contribute patches for your preferred ROM to auto-patcher. For more details about contributing patches to auto-patcher, please contact Mateor.
How do I get the source?
The source is available as patches, or in complete form, from the OpenPDroid repositories
The source-code patches from the OpenPDroidPatches repository: . Note that there are two branches: 4.2.1 and 4.1.2. These source patches presently work against numerous roms (including CM 10/10.1, AOKP 4.1.2/4.2.1, AOSP 4.1.2/4.2.1, and potentially others)
[*] Complete repositories for the modified sections of the system are likewise located in the [URL=https://github.com/OpenPDroid/]OpenPDroid github. There are several repositories and branches; see the section 'What are all these repos and branches?' for more details about the content of the github.
What is the licence?
PDroid was under under the GPL v3 licence (as shown on the Google Code page), and as a result all derivative works (e.g. OpenPDroid) are likewise under the GPL v3 (or later) licence. Thus, OpenPDroid is under the GPL v3 licence, with no additional special conditions. The only way a PDroid derivative can be under any other licence is if the author contacts Syvat, gets him to agree provide PDroid under another licence, and then the author extends it.
Who's work is it?
PDroid was original developed by Syvat (with contributions and ports from others such as Pastime1971 and Mateor), and then CollegeDev extended it to created PDroid 2.0 (previously called PDroid Addon, then PDroid Extension). PDroid 2.0 has been forked by FFU5y, Mateor and wbedard to create OpenPDroid. Thus, OpenPDroid is the product of the work of many.
The following list includes all the contributors I know of for any of these version of the core (in alphabetical order):
CollegeDev (PDroid 2.0)
FFU5y (OpenPDroid)
Mateor (Porting PDroid to 4.x, porting PDroid 2.0 to 4.1.2, OpenPDroid)
Pastime1971 (Porting PDroid to 4.x, porting PDroid 2.0 to 4.1.2)
Syvat (PDroid)
Wbedard (OpenPDroid)
How do I report issues?
The best way to report an issue is to lodge it in github, although you may want to also post in this thread to let others know that the issue exists (and has been lodged). Please ensure you provide details of the issue you are experiencing (i.e. under what circumstances does it happen, what do you observe, etc) and please include a logcat: see how to get a logcat.
If you don't have a Github account, you can post the issue here (and note that you haven't lodged it in Github) so one of the team can add the issue to Github.
I want to contribute
Great! The whole point of OpenPDroid is to encourage community contribution in the form of ideas, testing, code, etc.
Presently, there isn't really a lot (read: any) documentation about how OpenPDroid works. However, this will be forthcoming, as will an API specification for the Privacy service, which will allow you to write your own management application (like PDroid Manager or the PDroid 2.0 App) if you so desire.
Right now, these are the particular areas of the service which would benefit from developer/code contributions.
Transient caching of privacy settings read from the database, ideally with destruction of cache entries when they are too old or memory conditions are low
Refining the locking code to ensure that reads are not unduly held up by write locks (note: this isn't a problem *yet*, but will be with the inclusion of batch support. More details soon).
Other performance optimisations
Adding good quality code comments - mainly function descriptions, etc
Back-porting of OpenPDroid to pre-4.1.2, so users currently only able to use PDroid can move to OpenPDroid and get the new features.
There are many other things you can work on, including adding whole new options (i.e. security features). If you are planning on creating new security features, however, please lodge the enhancement in github first so it can be discussed. Not every feature which seems like a good idea will be a good fit for OpenPDroid, and it may save some time if a prospective feature can be refined before it is fully coded.
How do I compile a ROM with OpenPDroid
To build a ROM with OpenPDroid, you will need to patch the source code using the provided patches, and then build as you normally would.
To patch the source:
Download the most relevant of the source code patch packages attached to this post
Extract the patch files from the package
On the command line, go to the root of your Android source code: it will contain folders such as 'build', 'frameworks', 'vendor', etc.
Patch the source code with each patch file using the following command
Code:
patch -p1 < <patch_filename>
You can then build your ROM as you would normally.
If you have previously built the ROM in the folder you are using, or you have previously built PDroid 2.0, Syvat's original PDroid, etc it can be helpful to delete the following directories:
out/target/common/obj/JAVA_LIBRARIES/framework_intermediates
out/target/common/obj/JAVA_LIBRARIES/framework2_intermediates
out/target/common/obj/JAVA_LIBRARIES/telephony-common_intermediates
Not all of these directories will exist for all ROMs, so if you try to delete one and it is missing that is not cause for concern.
What (specifically) can I control with OpenPDroid?
Currently, access to the following data and functions can be controlled (note this list exactly matches PDroid 2.0):
Code:
[b]Data access:[/b]
Device ID (IMEI/MEID/ESN)
Phone/voicemail number
Sim Card Serial (ICCID)
Subscriber ID (IMSI)
Source number of incoming calls
Destination number of outgoing calls
Network location
GPS location
Authentication credentials
List of accounts, including identifiers (e.g. gmail e-mail address)
Contact list and details
Call log
Calendar
Read and send SMS
Read and send MMS
Record audio (not phone calls)
Camera
Browser bookmarks and history
System logs
Wifi Info, such as current access point, IP address
Network information (detailed network information such as connection state, IP address, etc)
Android ID (a unique installation ID for your Android installation)
SIM information (your phone operator and country)
Restrict access to iptables command
ICC Access (reading or writing SMS on the SIM or R-UIM)
[b]Actions:[/b]
Make phone calls
Start on Boot (or more accurately, get notified when the boot is complete)
Switch Wifi State (turn wifi on and off, change access points)
Switch network state (turn off or on mobile data)
[b]Other[/b]
Force online state (always tell the app that the device is online: only needed if denying Wifi info and/or Network info)
Known Issues
Thanks to those users who have posted bug details, we now have a list of known issues. I have tried to indicate which will be fixed in the next release, but it is tentative. These issues can also be found (and discussed) on the github issues list
Requests for tower location are always blocked (ETA unknown)
Device lags when GPS is active (ETA: next release; experimental fix in 'devel' branch of 4.2.1-based ROMs: same fix as the below camera lag issue)
Camera lags when OpenPDroid is installed (ETA: next release; experimental fix in 'devel' branch of 4.2.1-based ROMs)
What are all these repos and branches?
In the github account containing the OpenPDroid repositories, there are numerous repositories. Many of these are OpenPdroid related: but not quite all of them. In addition, not all of them are relevant to each ROM.
The main repositories to be aware of are:
platform_frameworks_base
This contains the framework/base/* code, which constitutes the most important guts of OpenPDroid in 4.1.2 and 4.2.1. Other projects sometimes use the name android_frameworks_base for this.
platform_frameworks_opt_telephony
This contains the framework/opt/telephony code, which was split out from framework/base/* in 4.2.1.
platform_build
This contains the build code, mostly makefiles, and is present in 4.1.2 and 4.2.1.
platform_libcore
This contains core operational code outside of the framework (e.g. executing shell tasks, etc).
platform_packages_apps_mms
This contains the code for the Mms app, for 4.1.2 and 4.2.1.
platform_packages_apps_mms
This contains the code for the Mms app, which is modified to affect the ability of apps to send and receive MMS.
platform_packages_apps_videoeditor
This contais the code for the VideoEditor app. The only change here is including 'framework2', which is only required for AOSP 4.1.2.
platform_system_core
This contais a range of important core code, and is modified only for AOSP 4.1.2 to include 'framework2.jar' in the paths included at boot time.
The branches used include two key naming components. First, the rom:
e.g.
cm-10.1* = CyanogenMod 10.1
cm-jellybean* = CyanogenMod 10, cutting edge
cm-jellybean-stable* = CyanogenMod 10, stable release
aokp-jb-mr1* = AOKP 4.2.1-based
aokp-jb* (without the mr1) = AOKP 4.1.2-based
jb-mr0* = AOSP 4.1.2
jb-mr1* = AOSP 4.2.1
pa-jellybean* = ParanoidAndroid (currently buggy)
then the OpenPDroid version:
-openpdroid = the current stable release of OpenPDroid
-openpdroid-devel = the current development line of OpenPDroid
For development, the jb-mr1-release-openpdroid-devel is where I do my initial development, and I think expand it to be on the other -devel branches once I've tested it a bit.
FAQ
How do I include PDroid Manager in the ROM I am building so it can update from Google Play: see here
How do I include PDroid Manager in the ROM I am building so it is compiled during build: see here: TamCore provided a fix for the problem he mentioned, and it has been merged.
How do I build using the bleeding-edge (devel) code: see here, although there is a bit more to it than that. I'll provide extra details when time permits, but the important stuff is in this thread.
I have a question or issue not covered in this post
We'll be adding more to this post in the next day or two. Please be patient =)
Note to mods
I wasn't sure if this belonged in this forum, or in 'Apps and Games' but since it is not trivial to install I figured this was a safer bet.
reserved
Thank you!!!! I'll test
Sent from my LG-P920 using xda app-developers app
Announcement: OpenPDroid build patches, as well as the entire history of the PDroid framework, have been rebuilt and restructured and pushed to our github page. There are build patches for all Android versions from 2.3 to current. You can also take a look at the commit history of the original PDroid framework by svyat, from initial commit to the point where he halted development, 1.32 for gingerbread.
Build patches are here.
PDroid project history is here.
OpenPdroid for Android 4.2.1/4.2.2
These are the current build patches for Android 4.2.1 and 4.2.2 and should generally reflect the current state of the jb-mr1-release-openpdroid branch. The latest commist are not always reflected in the build patches, bleeding-edge development is in the -devel branches.
We realize that the patch/branch situation is not perfect, it is work in progress.
These build patches should work for most roms. As of their creation (1/17/13) they applied cleanly to AOKP, AOSP, Cyanogenmod, ParanoidAndroid and others.
The current best advice as to how to apply/remove them is below. Some easier application methods are being discussed.
To Apply
Code:
cd ~/android/system/build; git checkout -b pdroid; patch -p1 < ~/openpdroid_4.2.1_build.patch
cd ~/android/system/libcore; git checkout -b pdroid; patch -p1 < openpdroid_4.2.1_libcore.patch
cd ~/android/system/packages/apps/Mms; git checkout -b pdroid; patch -p1 < openpdroid_4.2.1_Mms.patch
cd ~/android/system/frameworks/base; git checkout -b pdroid; patch -p1 < openpdroid_4.2.1_frameworks_base.patch
cd ~/android/system/frameworks/opt/telephony; git checkout -b pdroid; patch -p1 < ~/openpdroid_4.2.1_frameworks_opt_telephony.patch
cd ~/android/system; . build/envsetup.sh; brunch <DEVICE_TARGET>
To Remove
Code:
cd ~/android/system
rm -rf out/target/common/obj/JAVA_LIBRARIES/framework_intermediates \
out/host/common/obj/JAVA_LIBRARIES/layoutlib_intermediates \
out/target/common/obj/JAVA_LIBRARIES/telephony-common_intermediates \
out/target/common/obj/APPS/Mms_intermediates
[OR]
Code:
cd ~/android; make clobber
and to reset your source tree**
Code:
cd ~/android/system/build; git checkout . ; git clean -df
cd ~/android/system/libcore; git checkout . ; git clean -df
cd ~/android/system/frameworks/base; git checkout . ; git clean -df
cd ~/android/system/frameworks/opt/telephony; git checkout . ; git clean -df
cd ~/android/system/packages/apps/Mms; git checkout . ; git clean -df
cd ~/android/system; repo abandon pdroid
If OpenPDroid intrigues you, yet the thought of applying all these patches gives you pause, there is a tool that can attempt to patch the framework of an already compiled rom called The Auto-Patcher.
OpenPDroid is an open source fork of the PDroid framework, as written by Svyat and expanded by CollegeDev. We are always looking for contributors, come see us on XDA or submit a pull request.
I'm glad to see there's a more open PDroid project happening. I'm not sure what I'll be able to contribute, but I'll find something to help out with.
Looks like I'm going to have to spend some quality time with the CM10.1 codebase tonight.
Decimalman:
If you look in my github (http://github.com/wsot) you will find there are forks of all the modified parts of Android, and these include forks from cm-10.1 (branches called cm-10.1-openpdroid). You can pull directly from these repositories into your existing repositories if you would prefer to do that, rather than apply patches to the source.
For cm-10.1, the repositories you'll care about are:
* platform_frameworks_base
* platform_libcore
* platform_build
* platform_packages_apps_mms
* platform_opt_telephony_common
Each of these has a branch for cm-10.1-openpdroid with the changes included.
This is great work guys, thanks!
I will test it and if everything works, I will release the next extended CM10/FXP ROM with it.
Is there already a solution for including PDroid Manager and still being able to get updates from the market?
I have one question, did you fix this bug too?
Is there any plan to cooperate with CollegeDev?
It would be a pity if development for PDroid would be fragmented.
M66B said:
I will test it and if everything works, I will release the next extended CM10/FXP ROM with it.
Click to expand...
Click to collapse
Excellent!
M66B said:
Is there already a solution for including PDroid Manager and still being able to get updates from the market?
Click to expand...
Click to collapse
If you include PDroid Manager as-is from the PDroid Manager thread, then it has the same signature as the one in the market. Because of that, it should be able to update from the market.
M66B said:
I have one question, did you fix this bug too?
Click to expand...
Click to collapse
No, thanks for pointing that out. I've updated the source and pushed it to Github with that change. It'll be in the next release, which I don't imagine will be all that far away.
M66B said:
Is there any plan to cooperate with CollegeDev?
It would be a pity if development for PDroid would be fragmented.
Click to expand...
Click to collapse
We have not discussed with CollegeDev any kind of collaboration at this stage. Because both OpenPDroid and PDroid 2.0 core are GPL licensed, I imagine there will be code migration in both directions as things are fixed and improved.
The main reason that OpenPDroid has appeared (rather than us just making a 4.2.1 port of PDroid 2.0) is because long periods of development of PDroid 2.0 went on without the code being available, and so there was really no scope to collaborate.
The reason we are planning to produce an OpenPDroid API document is essentially so that there is a clear (and shared) idea of what can be expected from a minimal PDroid implementation, which both PDroid 2.0 and OpenPDroid cover at this stage. That way even if additional features are added (or someone creates a whole new PDroid implementation from scratch) there can be a shared interface to allow interoperability of management apps (like PDroid Manager).
I think there will be some 'fragmentation', but our hope is that there can be a common API between the versions that users will not have to suffer as a result, and can continue to use their preferred management app, and so forth.
Whether than will happen, I can't say yet.
Thank you! That's what I've been waiting for. I'll integrate this in OpenSensation2 asap
FFU5y said:
If you include PDroid Manager as-is from the PDroid Manager thread, then it has the same signature as the one in the market. Because of that, it should be able to update from the market.
Click to expand...
Click to collapse
Good! Could you make a 'latest' URL available somewhere (github?), so I can integrate it in my build process?
M66B said:
Good! Could you make a 'latest' URL available somewhere (github?), so I can integrate it in my build process?
Click to expand...
Click to collapse
Just added https://github.com/wsot/pdroid_manager_build - the sole purpose of which is now to have the latest PDroid Manager binary.
You will be able to get the file from: https://github.com/wsot/pdroid_manager_build/blob/master/PDroid_Manager_latest.apk?raw=true
FFU5y said:
Just added https://github.com/wsot/pdroid_manager_build - the sole purpose of which is now to have the latest PDroid Manager binary.
You will be able to get the file from: https://github.com/wsot/pdroid_manager_build/blob/master/PDroid_Manager_latest.apk?raw=true
Click to expand...
Click to collapse
Thanks, I will integrate this tonight in my build process and I will document here how I did that, so other developers can maybe do the same.
M66B said:
Thanks, I will integrate this tonight in my build process and I will document here how I did that, so other developers can maybe do the same.
Click to expand...
Click to collapse
That would be excellent! Let us know how it goes.
Thanks for improving pdroid!
Great work :good:
but the Problem I got is that I want to test it on my Nexus 4 with ParanoidAndroid...
when will it be possible ?
because i feel a little bit naked without pdroid and i don´t like to use LBE
seety said:
Thanks for improving pdroid!
Click to expand...
Click to collapse
Cheers. We're happy to be able to expand on the great work done by others.
seety said:
... I want to test it on my Nexus 4 with ParanoidAndroid...
when will it be possible ? ...
Click to expand...
Click to collapse
If you haven't already, I suggest you try to patch with auto_patcher: I believe that quite a lot of the unofficial PA builds will actually patch even though we haven't specifically compiled for them.
While we were preparing for release, the source for ParanoidAndroid was not available, which is why there are not specific patches for it. The source has since been made available, so I expect we will have specific patches for PA integrated into auto_patcher quite soon. Exactly how soon is a bit hard to say, but we are certainly working on it.
Hi
I tried to find PDroid Manager in Play Store but can't find it.
Did a Web install from Play Store & it says my device is not compatible with the app.
I'm on Samsung Galaxy S3 i9300.
Is it really incompatible? If no where can I get the app?
Thanks.
Edit: lol Found the app in OP
Ignore me
Thanks for the good work, I'm test compiling to my build now.
temasek said:
Hi
I tried to find PDroid Manager in Play Store but can't find it.
Did a Web install from Play Store & it says my device is not compatible with the app.
Click to expand...
Click to collapse
Actually, it is a really valid question. I haven't updated the PDroid Manager in Google Play to be marked as supporting 4.2.1 yet. This will be done within the next 24 hrs, and you'll then be able to update from Google Play as new releases come out.
temasek said:
Thanks for the good work, I'm test compiling to my build now.
Click to expand...
Click to collapse
I hope it all goes smoothly, but if not let us know.
FFU5y said:
Cheers. We're happy to be able to expand on the great work done by others.
If you haven't already, I suggest you try to patch with auto_patcher: I believe that quite a lot of the unofficial PA builds will actually patch even though we haven't specifically compiled for them.
While we were preparing for release, the source for ParanoidAndroid was not available, which is why there are not specific patches for it. The source has since been made available, so I expect we will have specific patches for PA integrated into auto_patcher quite soon. Exactly how soon is a bit hard to say, but we are certainly working on it.
Click to expand...
Click to collapse
Hey thanks for the quick answer!
I tired the auto_patcher several times sadly it doesn't work...
maybe these logs are interesting for you:
Try to patch with CM Patches / With AOSP Patches
Perhabs it work if you try to patch this rom, but i am not angry if you got no time for this.
thanks in advance
seety said:
Hey thanks for the quick answer!
I tired the auto_patcher several times sadly it doesn't work...
maybe these logs are interesting for you:
Try to patch with CM Patches / With AOSP Patches
Perhabs it work if you try to patch this rom, but i am not angry if you got no time for this.
thanks in advance
Click to expand...
Click to collapse
Thanks for the details. We will be prepping patches for PA as a high priority so don't worry, you shouldn't be waiting long
I've compiled successful OpenPDroid and booted up fine. So far so good.
I'm letting my users of CM10.1 i9300 Unofficial BUILD to try your wonderful work.
This is my changelog for my CM10.1 Unofficial build V34 for i9300
http://forum.xda-developers.com/showpost.php?p=36697391&postcount=6919
Again, thanks for your good work.
If you are a developer, and wish to have a device merged into Omni, here is the current "temporary" process to use. There are 2 ways to do this - make your tree available on github (or a similar service), or request a new git tree be created, and submit it to gerrit.
1) Get your device working. There's plenty of help available in #omnirom on Freenode if you need assistance. An AOSP device tree is probably the best place to get started.
2) Set up your device to use the OmniROM "custom" build type, rather than full/aosp. More information will follow on this step - check device/samsung/manta or device/lge/mako for an example.
3) Make your device tree available on github or a similar git service. Please retain authorship of an original tree (if you fork it from AOSP or another custom ROM)
4) Come to #omni on Freenode, and have a chat to one of the core developers (they are listed at the top of the user list) - they will be able to help you get your device merged
Please note, in order to add a new device, we will require a maintainer on an ongoing basis for it, to ensure someone is able to investigate bugs that users report on a device. Without this, we unfortunately cannot enable nightly builds for a device.
will a cm kernel tree work for the most part with just a few changes?
azoller1 said:
will a cm kernel tree work for the most part with just a few changes?
Click to expand...
Click to collapse
yes - of course it must be 10.2 (4.3)
most likly it will work even unchanged
pulser_g2 said:
3) Make your device tree available on github or a similar git service. Please retain authorship of an original tree (if you fork it from AOSP or another custom ROM)
Click to expand...
Click to collapse
Along these lines, do NOT remove copyright attributions of a changed file. You may ADD copyrights to a header, but do NOT remove anything.
maxwen said:
yes - of course it must be 10.2 (4.3)
most likly it will work even unchanged
Click to expand...
Click to collapse
Most likely kernel change will be that reverting out that MDP sync point mess used by CM's AOSP+CAF frankendisplay. Can't link to it from my current location.
I have everything device sided transformed to Omni (m7ul,m7-common,and msm8960) and have exactly this problem now. Builds fine but Stucks after a few secs booting and hard reboots. Already looked into kmsg with maxwen but now we need to find what's causing it...
Reverted some stuff (MDP) kernel sided but haven't succeeded so far. Would be appreciated if u point us there when u back on a pc
noNeedForAsig
TF300T
OK here goes..
For the Asus Transformer TF300T the kernel forked from the CyanogenMod github:
https://github.com/scanno/android_kernel_asus_tf300t/tree/android-4.3
And the device tree, modified to get OmniROM to finish the build and get a bootable result:
https://github.com/scanno/android_device_asus_tf300t/tree/android-4.3
Hopefully it will be added to the OmniROM github.
n3ocort3x said:
I have everything device sided transformed to Omni (m7ul,m7-common,and msm8960) and have exactly this problem now. Builds fine but Stucks after a few secs booting and hard reboots. Already looked into kmsg with maxwen but now we need to find what's causing it...
Reverted some stuff (MDP) kernel sided but haven't succeeded so far. Would be appreciated if u point us there when u back on a pc
noNeedForAsig
Click to expand...
Click to collapse
I'm thinking for m7ul it would be https://github.com/CyanogenMod/android_kernel_htc_m7/commit/f2efb02581110747711c8b17f31f38fc3ed5dd1a
Don't want to hijack the thread though, so we can probably discuss this elsewhere
@Grarak Maybe you should post your edited device tree for Omni Rom =)
Sent From my i9500 With ☆★Crash Rom★☆
AL_IRAQI said:
@Grarak Maybe you should post your edited device tree for Omni Rom =)
Sent From my i9500 With ☆★Crash Rom★☆
Click to expand...
Click to collapse
Already on my github
https://github.com/Grarak/android_device_samsung_i9500
kernel tree
https://github.com/Grarak/android_kernel_samsung_exynos5410
proprietary
https://github.com/Grarak/proprietary_vendor_samsung
exynos 5410 repos:
https://github.com/intervigilium/android_hardware_samsung_slsi_exynos5410
https://github.com/intervigilium/android_hardware_samsung_slsi_exynos
https://github.com/intervigilium/android_hardware_samsung_slsi_exynos5
https://github.com/intervigilium/android_hardware_samsung_slsi_exynos5-insignal
https://github.com/intervigilium/android_hardware_samsung_slsi_openmax
pretty much ^^
I'd like to maintain for l900 and i605 (Sprint and Verizon Galaxy Note 2).
device trees
https://github.com/omnirom-slickrick/android_device_samsung_l900 (sprint tree)
https://github.com/omnirom-slickrick/android_device_samsung_i605 (vzw tree)
https://github.com/omnirom-slickrick/android_device_samsung_t0lte (note 2 common tree)
https://github.com/omnirom-slickrick/android_device_samsung_smdk4412-common (same as tree on omnirom github but actually more updated and device settings added back)
kernel
https://github.com/omnirom-slickrick/android_kernel_samsung_smdk4412 (just have needed device settings commits added back in)
thracky said:
I'm thinking for m7ul it would be https://github.com/CyanogenMod/android_kernel_htc_m7/commit/f2efb02581110747711c8b17f31f38fc3ed5dd1a
Don't want to hijack the thread though, so we can probably discuss this elsewhere
Click to expand...
Click to collapse
we already making progress but it needs more work to be done.. at least we are now in system with working wifi, and display but modem doesent work.. something for tomorrow, and i dont want to hijack this thread too sorry if my question was in the wrong section but i thought i mention it because of the post above mine. nevermind i cann offer to maintain m7ul as already discussed with maxwen and oin IRC but a lot of work needs to be done:
here are my sources, device trees are usable but kernel needs more work as said above:
device trees:
https://github.com/n3ocort3x/android_device_htc_m7ul
https://github.com/n3ocort3x/android_device_htc_m7-common
https://github.com/n3ocort3x/android_device_htc_msm8960-common
kernel: its a modified one but its no problem to bring it back to stock features and will push as soon asap the modem stuff is sorted out
https://github.com/n3ocort3x/android_kernel_htc_m7
EDIT modem fixed, only BT left
@sykomaniac , look at first post and become a maintainer
pulser_g2 said:
If you are a developer, and wish to have a device merged into Omni, here is the current "temporary" process to use. There are 2 ways to do this - make your tree available on github (or a similar service), or request a new git tree be created, and submit it to gerrit.
1) Get your device working. There's plenty of help available in #omnirom on Freenode if you need assistance. An AOSP device tree is probably the best place to get started.
2) Set up your device to use the OmniROM "custom" build type, rather than full/aosp. More information will follow on this step - check device/samsung/manta or device/lge/mako for an example.
3) Make your device tree available on github or a similar git service. Please retain authorship of an original tree (if you fork it from AOSP or another custom ROM)
4) Post a link here to the device tree (and kernel repository) for review, and tell us what device it is (give model numbers and board names and as many details as possible )
Click to expand...
Click to collapse
We have quite a few things that aren't working like bluetooth, camera is buggy, H/W vsync, gps, and fm radio.
https://github.com/SeannyM/android_device_samsung_kylessopen
https://github.com/SeannyM/ba2x-kernel
gt-s7560m with quadband gsm and 850/1900/2100 WCDMA/UTMS
We have a MSM7227a cpu armv7 clocked at 1008mhz stock.
645mb of usable ram
4gb of storage with 1.7 usable
233 dpi 800x480 4inch screen
Adreno 200 enhanced
5mp camera 1.3 front facing
hopefully we can get something official
single sim
Gtab2 10.1 Wifi & 3G (p5110 & p5100)
There you have my device tree for omni
p5110 :
https://github.com/sevenup30/android_device_samsung_p5110
p5100:
https://github.com/sevenup30/android_device_samsung_p5100
omap4-common (had to edit it cuz of duplicate libion entry):
https://github.com/sevenup30/android_device_samsung_omap4-common
other dependencies required from CM & Themuppets
kernel :
https://github.com/CyanogenMod/android_kernel_samsung_espresso10
samsung proprietary:
https://github.com/TheMuppets/proprietary_vendor_samsung
samsung hardware:
https://github.com/CyanogenMod/android_hardware_samsung
apps samsung service:
https://github.com/CyanogenMod/android_packages_apps_SamsungServiceMode
Everything is working (sound / wifi / bluetooth / video playback) BUT!
I must edit build.prop by hand to get sound working until omni build process take care of "product_build_prop_overrides" into custom_XXXX.mk
see:
http://forum.xda-developers.com/showthread.php?t=2484747
Original Samsung Galaxy Note
Samsung n7000 initial bringup:
Modified CM n7000 device: https://github.com/chasmodo/android_device_samsung_n7000/tree/android-4.3
Modified CM galaxys2-common: https://github.com/chasmodo/android_device_samsung_galaxys2-common/tree/android-4.3
CM smdk4412 kernel: https://github.com/CyanogenMod/android_kernel_samsung_smdk4412/tree/cm-10.2
Samsung proprietary stuff: https://github.com/TheMuppets/proprietary_vendor_samsung/tree/cm-10.2
Samsung hardware tree untouched from OmniRom.
Device info:
Board platform - exynos4
SOC - exynos4210
Board name - smdk4210
Kernel specifics - unified kernel and recovery
It compiles fine using the repos listed above, but throws up a kernel assert error when flashing the Rom. Several compilers for different devices complained about it in the 'All the answers' thread. The way out of this is to flash a CM10.2 kernel immediately after the Rom flash aborts, then Omni boots up fine.
What works:
1. telephony
2. mms
3. WiFi
4. GPS
What doesn't work:
1. data
2. bluetooth turns off as soon as you turn it on
3. both sdcards are invisible from Android; all your stuff is there when you drop into recovery, though
4. Settings/Storage FC when tapped - see #3
5. Performance options also FC
6. Notification drawer cannot be pulled down
Camera cannot be tested because it shuts down as soon as you start it, saying: "No external storage available" - again, see #3
Galaxy Note II / N7100 (International)
Samsung Galaxy Note II / N7100 Bring up details.
I have a working build of the Omni rom for the N7100. Below are the details on what is working and not working. i have been using it for the last 2 days, so far not crashes or reboots all seems to be working fine. i cherry picked a few commits and included it into my build
Working :
WIFI
DATA -3G & 2G
Telephony & MMS & SMS
GPS
Sound
Camera (Both Front and Back)
SD card
Performance control
Notification drawer & Lights
Multi-Window
roadrunner
Not Working :
BT
Backlights(if i install a custom kernel then the lights work)
Device Tree for N7100 - https://github.com/tilaksidduram/device_samsung_n7100
Device smdk4412-common - https://github.com/tilaksidduram/android_device_samsung_smdk4412-common
smdk-4412 Kernel (3.0.100) - https://github.com/CyanogenMod/android_kernel_samsung_smdk4412
samsung hardware - https://github.com/CyanogenMod/android_hardware_samsung
DEVICE: GT-N7100
sources
https://www.github.com/UtkarshGupta/android_device_samsung_n7100
https://www.github.com/omnirom/android_device_samsung_smdk4412-common
https://www.github.com/omnirom/android_hardware_samsung
https://www.github.com/omnirom/android_kernel_samsung_smdk4412
https://www.github.com/TheMuppets/proprietary_vendor_samsung
Is anyone else working on d2att/d2can (Galaxy S3 I747)? I'm not overly familiar with ROM development, but I can compile CM10.2 for this device just fine, and I'm slowly working on getting Omni to compile for it as well. If someone more experienced than I is already working on it though, I'll probably just let them do it.
If I am the only one, expect some newb-ish questions in the near future.
dstruct2k said:
Is anyone else working on d2att/d2can (Galaxy S3 I747)? I'm not overly familiar with ROM development, but I can compile CM10.2 for this device just fine, and I'm slowly working on getting Omni to compile for it as well. If someone more experienced than I is already working on it though, I'll probably just let them do it.
If I am the only one, expect some newb-ish questions in the near future.
Click to expand...
Click to collapse
I think a few are... There has been chat of it in the IRC channels.
Device name: LG Optimus 4X HD
Codename: P880
Board name: X3
Chipset: Tegra 3 AP33
Everything works, except button backlight.
https://github.com/Adam77Root/android_device_lge_p880
https://github.com/Adam77Root/android_kernel_lge_x3
https://github.com/TheMuppets/proprietary_vendor_lge
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.0 (Lollipop), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include
/*
* 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
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo.
Device-specific source code for the Samsung Galaxy S2 Plus are available from https://github.com/luk1337/android_device_samsung_s2vep,
https://github.com/luk1337/android_device_samsung_s2ve and https://github.com/luk1337/android_kernel_samsung_galaxys2plus-common.
Compatibilitiy Patches: https://github.com/luk1337/build_tools/tree/cm12
(Please give credit if you use them in your ROM and if you fix something, please submit patches.)
Do not submit bug on CyanogenMod issue tracker
Downloads
ROM: https://s.basketbuild.com/devs/LuK1337/CM12
Google Apps: For now, find your own package
What works?
Wi-Fi
Bluetooth
RIL (Calls, SMS, Mobile Data)
Sensors (Accelerometer, Compass, Light, Proximity, etc.)
Camera (photo)
Video playback
Audio (playback & recording)
GPS
Everything else not listed under "known issues"
Known Issues
screenrecord does not work
FM Radio does not work
Sometimes wake up causes music stutter
Video recording does not work
.wav playback does not work (.mp3 works fine)
SELinux is in permissive mode
Wi-Fi HAL (i.e. Scanning MAC Address Randomization) not implemented
Sim Tool Kit (STK) not fully working
Video in YouTube app sometimes freeze
Bluetooth headset isn't working
Does not work on 4.1 stock ROM's bootloader, please upgrade to 4.2 before flashing
Installation
Make a backup!
If you were on CM 10.1 or a stock ROM prior to 4.2, upgrade to 4.2.
Install ClockworkMod recovery with SELinux support
Reboot into recovery
Wipe data if coming from stock or another non-CM ROM (You may get a "staus 7" error if you fail to wipe.)
Install the ROM
Optionally install the Google Apps Addon
To upgrade to a newer build, simply flash the zip. There's no need for data wipe or flashing Google Apps again.
Changelog
20141116: Initial release
FAQ
Can you include Feature X into your ROM?
No. This ROM will have CyanogenMod's feature set.
Can you include S-Note/S-Planner/MultiWindow/Insert Samsung App Here?
No. This is an AOSP ROM and cannot have TouchWiz applications.
Can you include call recording?
No. CyanogenMod does not include call recording to avoid potential legal issues.
Can you add Feature X to the stock ROM?
No. I don't work on stock ROMs.
What kernel does this ROM use?
A slightly modified version of the stock kernel, the source code is linked above.
I've heard that Broadcom doesn't release source, how can you make this ROM?
Contrary to the popular belief, userspace driver source code is not always required to make an AOSP-based ROM as long as the proprietary binaries shipped with the device does not modify the API too heavily (or is from a very different version of Android). Instead of modifying the source code of the drivers, the Android source code was adapted to be able to use the proprietary binaries.
Can I use your ROM as a base?
http://source.android.com/source/licenses.html
Most of Android/CyanogenMod is licensed under the Apache License with other small parts licensed under other open-source licenses. Which means that you may modify and redistribute without asking for permission as long as the proper credits is given and it is not misappropriated as being the official CyanogenMod. (In other words, you must say that it is based on pawitp's unofficial CyanogenMod, but is not related to CyanogenMod in any other way.)
Can contacts be saved to phone/SIM?
No. It is not supported in AOSP-based ROMs.
Can I send files over Wi-Fi Direct?
Yes, but you must use third-party applications. The implementation provided on Samsung ROMs is not an open standard. AOSP/CM does not provide a native way to send files over Wi-Fi Direct.
Can I mirror your ROM?
You're free to, but I will not list it in this post.
Is overclock (OC) available?
1.3 GHz OC is available in Settings -> Performance -> Processor (enable developer mode first). Higher frequencies are not enabled since benchmark does not show additional benefit.
Will feature X from a previous version of CM be implemented?
I don't know, probably will be, eventually. I don't really involve myself in the feature-set side of CM.
Will you add OTA support?
No.
I cannot add APNs
Make sure you set the correct MCC/MNC code, the APN will not appear otherwise. Also make sure to use menu -> save (back button means discard).
Reporting Bugs
You are allowed to report bugs only in this thread.
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. The following is a useful format to follow.
Code:
What is your--
Phone model (s2ve or s2vep):
Radio (baseband):
CM version:
CM Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
CMSettings/Performance settings (other than stock):
ART Runtime:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
Thanks
- The CyanogenMod team for providing a great ROM. Without all the compatibility work which went into it, this ROM would've been much harder to make
- CoolDevelopment, pawitp and other s2ve/p and i9082 devs
XDA:DevDB Information
[ROM][UNOFFICIAL][ALPHA][s2ve/p] Cyanogenmod 12.0, ROM for the Samsung Galaxy S II Plus
Contributors
LuK1337
ROM OS Version: 5.0.x Lollipop
ROM Kernel: Linux 3.0.x
Version Information
Status: Alpha
Created 2014-11-16
Last Updated 2014-11-16
NOTE: I'm still building s2ve, I'll upload it later.
Can't wait
can't wait for test! so excited
Awesome
PLease dont forget the Non NFC edition.. keep up the good work
essuraj said:
PLease dont forget the Non NFC edition.. keep up the good work
Click to expand...
Click to collapse
you can easily flash P-recovery and enjoy the dev's work
Hy, please upload today a download link for CM12, i really want to try it as faster as i can. :fingers-crossed::fingers-crossed::fingers-crossed:
Sheldd said:
Hy, please upload today a download link for CM12, i really want to try it as faster as i can. :fingers-crossed::fingers-crossed::fingers-crossed:
Click to expand...
Click to collapse
It will be uploaded today,just be patient!
Sheldd said:
Hy, please upload today a download link for CM12, i really want to try it as faster as i can. :fingers-crossed::fingers-crossed::fingers-crossed:
Click to expand...
Click to collapse
Buy me SSD or better PC then I would build it faster.
LuK1337 said:
Buy me SSD or better PC then I would build it faster.
Click to expand...
Click to collapse
Oh, sorry, i don't want to be ungrateful,but i'm really excited and i want to try it...:angel:
LuK1337 said:
Buy me SSD or better PC then I would build it faster.
Click to expand...
Click to collapse
First of all: thank you so much for this amazing work! I can't wait to try!
How long do you think will it take?
Because for me the day ends in 3-4 hours
So i can't add contacts to my phone or sim ?
About Gapps?
Thank you very much : LuK1337!
Does somebody know what Gapps we must use in this rom?
I think we can use this:
https://s.basketbuild.com/filedl/gapps?dl=gapps-lp-20141109-signed.zip
Newku said:
So i can't add contacts to my phone or sim ?
Click to expand...
Click to collapse
You can save contacts on Phone but not on sim.
NW2000 said:
I think we can use this:
https://s.basketbuild.com/filedl/gapps?dl=gapps-lp-20141109-signed.zip
Click to expand...
Click to collapse
Ok. Thank you!
LuK1337 said:
You can save contacts on Phone but not on sim.
Click to expand...
Click to collapse
thank you very much luk
Can We flash with normal cwm, exept 6.0.5.1?
it looks pretty good.
i tended to think that we wouldn't get that soon cm12, but luk is the best dev,also,grand duos devs.
we wait for ur build uploaded.
thank you man.
LuK1337 said:
[*]Install ClockworkMod recovery with SELinux support
[*]
Click to expand...
Click to collapse
Does it work with PhilzTouch by hacky?
I can't wait :victory: :victory: