Yes using googles tester(can't remember what it was called)
checked right now: 12 video and 15 audio codecs supported. I need more concrete information and less empty words
Idk about your setup and I haven't tried to build for DX but try . build/envsetup.sh && brunch (idk if you need to say shadow or cm_shadow or the local_manifest or what but usually its the device codename)I am attempting to build this unoffical CM11 for Droid-X but am stuck at the lunch step. cm_shadow-userdebug doesn't seem to be available. When I specify "lunch cm_shadow-userdebug" on the commandline it says "Trying dependencies-only mode on a non-existing device tree?"
I followed the "Getting Started" steps in github.com/MotoDX-CM11/android to obtain the source code, then looked for build instructions. I have gone through the pages on building CM for Droid-X, but they really target CM-7.
I am building on Ubuntu 12.04, and have apt-get installed the required features from build instruction pages on wiki.cyanogenmod.org and source.android.com. However, I wasn't able to install phablet-tools.
A little further guidance on getting started building this would be very much appreciated.
This may be irrelevant here but just trying to help...why are you trying to build cm11? Why not just flash m.ksy's build? Or are you attempting a kang?
I then run the m command, which runs for a while (albeit with some warnings) but finally outputsTrying dependencies-only mode on a non-existing device tree?
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.4.4
CM_VERSION=11-20141007-UNOFFICIAL-shadow
TARGET_PRODUCT=cm_shadow
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a-neon
TARGET_CPU_VARIANT=cortex-a8
HOST_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-3.13.0-36-generic-x86_64-with-Ubuntu-12.04-precise
HOST_BUILD_TYPE=release
BUILD_ID=KTU84Q
OUT_DIR=/home/chrisr/cyanogenmod/out
============================================
I assume that being hated by Koush is undesirable, but the @hide is already in the frameworks/base/core/java/android/provider/Settings.java file where VOLUME_xx are declared. I have searched for solutions, but no one seems to be having this issue.Checking API: checkapi-current
/home/chrisr/cyanogenmod/out/target/common/obj/PACKAGING/public_api.txt:21299: error 5: Added public field android.provider.Settings.System.VOLUME_07
/home/chrisr/cyanogenmod/out/target/common/obj/PACKAGING/public_api.txt:21300: error 5: Added public field android.provider.Settings.System.VOLUME_08
/home/chrisr/cyanogenmod/out/target/common/obj/PACKAGING/public_api.txt:21301: error 5: Added public field android.provider.Settings.System.VOLUME_09
/home/chrisr/cyanogenmod/out/target/common/obj/PACKAGING/public_api.txt:21304: error 5: Added public field android.provider.Settings.System.VOLUME_FM
******************************
You have tried to change the API from what has been previously approved.
To make these errors go away, you have two choices:
1) You can add "@hide" javadoc comments to the methods, etc. listed in the
errors above.
2) You can update current.txt by executing the following command:
make update-api
^^^^^^^^^^^^^^^^^^
NO. NO. STOP BEING LAZY. SERIOUSLY.
DO NOT DO THIS in CM. THIS IS A LIE. IF YOU DO THIS I WILL HATE YOU.
USE OPTION #1.
-Koush
To submit the revised current.txt to the main Android repository,
you will need approval.
******************************
make: *** [/home/chrisr/cyanogenmod/out/target/common/obj/PACKAGING/checkapi-current-timestamp] Error 38
Try brunch....also run ccache -M 0 before the build. Mine didn't get errors like yours did but I'm not entirely sure mine built right because in /out I don't have any apks just libs and recovery and something else.I'm still working to build CM11 for Droid-X as described in github.com:MotoDX-CM11/android, but as a newbie I'm struggling.
After I repo sync the tree, I copy mb526_cm10.1_defconfig to shadow_cm11_defconfig in shadow-kernel/arch/arm/configs
In vendor/cm I do ./get-prebuilts
I then run lunch cm_shadow-userdebug which outputs:
I then run the m command, which runs for a while (albeit with some warnings) but finally outputs
I assume that being hated by Koush is undesirable, but the @hide is already in the frameworks/base/core/java/android/provider/Settings.java file where VOLUME_xx are declared. I have searched for solutions, but no one seems to be having this issue.
Suggestions?
Thanks in advance.
When I do "brunch cm_shadow-userdebug", I get "make: *** No rule to make target `bacon'. Stop."
<project path="build" name="CyanogenMod/android_build" groups="pdk" >
<copyfile src="core/root.mk" dest="Makefile" />
</project>
When I do "brunch cm_shadow-userdebug", I get "make: *** No rule to make target `bacon'. Stop."
I've searched for a solution to that, but the closest thing I found was a statement after they'd resolved it that it was an internal or local configuration thing. Nothing about what it actually was.
---------- Post added at 02:48 PM ---------- Previous post was at 02:34 PM ----------
I don't have a Makefile in the top directory, so that's probably the immediate reason I get the error, but why wouldn't there be a Makefile?
Is your build environment correct? Try building for hammerhead. If it won't build for a nexus.....more than likely your system isn't setup correctly. Is this on a VM or dual-boot?I copied build/core/root.mk to Makefile because .repo/manifest.xml has the entry
It's now building (with a gazillion warnings), but I'm not sure what the result will be...Code:<project path="build" name="CyanogenMod/android_build" groups="pdk" > <copyfile src="core/root.mk" dest="Makefile" /> </project>
Is that where the Makefile should have come from? Is that the right approach?
It's a VM, running Ubuntu 12.04 LTS. It actually completed a build and generated cm-11-20141008-UNOFFICIAL-shadow.zip, and it seems to run on the Droid-X.
Congrats on finally getting it to build! Here's the link to the prebuilt VM I use based off of Ubuntu 14, if you're interested. It builds and runs good. Has a swap already set up and the guy debloated the system and installed a few extra packages. Guake is my favorite and really the only thing it needs extra IMO is Chrome-Dev but that's just me lol. If you'd prefer a legit full Ubuntu to build on he has a guide to setup Ubuntu 14.04. I tried using that, but the prebuilt VM was much faster for me.It's a VM, running Ubuntu 12.04 LTS. It actually completed a build and generated cm-11-20141008-UNOFFICIAL-shadow.zip, and it seems to run on the Droid-X.
It's a VM, running Ubuntu 12.04 LTS. It actually completed a build and generated cm-11-20141008-UNOFFICIAL-shadow.zip, and it seems to run on the Droid-X.
Sigh! It doesn't work well yet. Camera app can't connect to the camera and videos don't playback yet.
You need a ROM specifically built for your device. This ROM isn't compatible with your device because it's built for the droid x. Look for one for your device on xda.I followed the steps to install CM11 Android 4.4.4 on a Droid X and it worked. However, I also have an HTC Incredible, and was wondering if the same method would work on it.
Based on the video link below, CM11 Android 4.4.2 was installed on HTC Incredible. Not sure if there would be a compatibility issue by moving up to 4.4.4. Thanks.
(Since I'm a noob, I can't post a link... but the youtube video is titled "HTC Droid Incredible CM11 rom install KIT KAT 4.4.2" by rootjunky)
Lol I always dirty flash everything (except cross-rom flashing) but if u experience bugs and can't troubleshoot out of it a clean install is advised.So far, I've been really happy with CM11 on my phone as a daily driver, even with the daily reboots.
Today, I flashed the latest 20140930 version and the only thing I've found so far is the swipe typing on the built-in keyboard has disappeared. Poke typing works fine. I loaded up the Google keyboard from the Play store which works as expected. The built-in keyboard is preferable, obviously.
I tried rebooting a couple of times with no change. I have played with Privacy Guard a bunch lately, but I thought that wouldn't do that.
Am I the only one to experience this? Now, I was somewhat lazy and didn't wipe anything in TWRP when reflashing, but that worked fine last time.
Lol....is this your first ROM flash? When flashing ROMs it wipes all user data. Cm11 is stable only real bugs would be it random reboots sometimes. If you can't live with that @sd_shadow has a droidx bible with all ROMs and how-tos lolI have a Droid X and I flashed the CM11 ROM on this thread.
http://xdaforums.com/showthread.php?t=2670547
But my data and settings are wiped on reboot. The thread is almost 300 pages long, so it would take a long time to hunt down the final, stable download. Can someone help me out? I really want Kitkat on my DX.
Thanks
Do not use the droid x bootstrap from play store, it was designed for froyo not gingerbread. If you would like to buy one pick droid 2 or 3, but the modified one in the op is best.Howdy
I've begun researching the possibility of taking my clunky old Verizon DroidX that's been disconnected from a phone# and applying a custom Rom in the hopes of improving its performance.
After receiving considerable help from @sd_shadow with getting OtterX working beautifully on my KF, I'm feeling brave enough to try something similar now.
The 1st step I've taken was to use "Android Device Drivers Install" - https://www.youtube.com/watch?v=j_KPGUMzrjU (VERY informative) youtube video by Rootjunky.com
I successfully used "How to Root Droid X & Droid 2 on Android V2.3.4" - https://www.youtube.com/watch?v=w543XNIExWo to get it rooted - YAY.
Next is getting a nandroid backup done. I was just about to purchase "Droid X Recovery Bootstrap" - https://play.google.com/store/apps/details?id=com.koushikdutta.droidx.bootstrap from the Play Store for $3 but then I noticed a wise man said "if Droid X bootstrap works for you great, but don't be surprised if it causes a bootloop"
I know that the next logical step is to be able to restore the device before going any further. I'm thinking CWM is a good way to go.
I need advice as far as which specific goal I should be shooting for as far as the best recommended final ROM based on your successes with my configuration. I really do like CM11/4.4.4 a whole lot.
Any Suggestions please?
System version = 45.621.10.MB810.Verizon.en.US
Android version = 2.3.4
Kernel Version - 2.6.32.9-g3e80c7a
Build number = 4.5.1_57_DX9-10
ERI = 5
PRL = 52826
Thanks in advance for reading this and possibly even considering to point me in the right direction.
use camera button to select options, you used power button right?
just press power once more, to see options again, then press camera button