Q&A for Guide on building Lollipop for the OnePlus One
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for Guide on building Lollipop for the OnePlus One. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
./extract-files.sh on CM11S
Does ./extract-files.sh will do the right thing if you are on CM11S ?
Because it is sait there : wiki.cyanogenmod.org/w/Build_for_bacon
That you need to have a build of the same branch running on your phone (which is obiously not the case here...)
Kppqju77 said:
Does ./extract-files.sh will do the right thing if you are on CM11S ?
Because it is sait there : wiki.cyanogenmod.org/w/Build_for_bacon
That you need to have a build of the same branch running on your phone (which is obiously not the case here...)
Click to expand...
Click to collapse
Yes, it will work if you're running CM11S on your phone as far as I know. You can try and report back.
me too. video play can't work . it will reboot when click to play video.
Any idea why do I get it? I followed a guide.
make[1]: Entering directory `/home/malwin/cm/kernel/oneplus/msm8974'
The present kernel configuration has modules disabled.
Type 'make config' and enable loadable module support.
Then build a kernel with module support enabled.
Edit : I've checked settings and "Enable loadable module support is checked.
It also bothers my why revision="cm-11.0" of connectivity project is used to build cm12?
lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 14.04.1 LTS
Release: 14.04
Codename: trusty
Related
Hi all,
#############################
My apologies. I posted this question in "General" first. Shame on me! I didn't find how to move or delete it there, so I decided to post here, in the correct section, again. If an Admin is reading this, I would be happy to delete the post in the "General" section if you tell me how to do it. Thanks!
#############################
I want to build Android from source and install it on a device. Simple build runs successfully so that I assume the environment is set up correctly. Question is: Is there a dependency between Android and the kernel version, i.e. do certain Android versions require certain kernel versions? Do I need to update the kernel on a device before installing a new Android version?
Thanks a lot!!
Mike
Q&A for [ROM][4.4.4] -PA - AK Kernel - F2FS- [OnePlus One]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][4.4.4] -PA - AK Kernel - F2FS- [OnePlus One]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
CallMeAldy said:
You missed out on adding @ak to your credits without him AK Kernel wouldnt be what it is
Click to expand...
Click to collapse
Is it required that he give full credit to ak when he did not include ak in his rom it is flashed separate. It would seem that any f2fs ready kernel should work assuming it had a compatible ramdisk. He is not redistributing the ak-kernel just linking to the official ak site with a kind recommendation to use his kernel.
Thanks for this rom. Finally a f2fs rom with working ART. Testing with the new avalon kernel and every thing is just fine. Just wanted to people to know that more than just ak kernel works with this rom and it seems to me that many f2fs kernels are working with this rom. The neo kernel is also working although I did not test for long enough with this rom but neo also has some interesting things going on in his kernel v27 had good battery life when i tested it on the previous f2fs rom I was using. So far every thing seems to be going great keep up the good work and thanks for bringing us another f2fs rom to play with.
Negen+1 said:
Is it required that he give full credit to ak when he did not include ak in his rom it is flashed separate. It would seem that any f2fs ready kernel should work assuming it had a compatible ramdisk. He is not redistributing the ak-kernel just linking to the official ak site with a kind recommendation to use his kernel.
Click to expand...
Click to collapse
It's fair enough to give credits to the kernel developers like people give credits to the rom developers. It's upto the OP i just gave a headsup
First off, I just want to say I don't mean to step on anyone's toes. Thanks for all the work so far from digitalhigh, bracketslash, santod040 and everyone who has posted information about or commits to the CM12 build tree. This is not my code, all I have done is disable enough stuff to get it to build and boot. A LOT OF STUFF IS BROKEN. This is intended for developers only right now. I will try to update the builds as I can but please don't expect true nightly builds.
DISCLAIMER: I am in no way responsible for malfunctioning or bricked devices if you run this software. If you do not agree to these terms, DO NOT DOWNLOAD. Again, this is seriously broken right now.
What doesn't work:
-Almost everything
What works:
-Wifi
-Touchscreen
-Sound
Changelog:
Merged (compare to build date)
Open (not in build yet)
Installation notes:
As I have yet to find a way to easily disable NFC for the builds, you will have to remove the /system/app/Nfc to stop those force closes. I just went to TWRP, mounted system, then ran "rm -rf /system/app/Nfc" to disable NFC for now.
Downloads:
2014-11-17: Download (Android File Host)
Edit: Please see bracketslash's thread for future downloads: http://forum.xda-developers.com/ver...ment/cm12-unofficial-unstable-builds-t2941198
bring it on bro
This saved me some time. Guess I'll see what I can do.
There was a new commit added to the open section that "adds dependency on device/qcom/sepolicy"
http://review.cyanogenmod.org/#/q/status:open+project:CyanogenMod/android_device_htc_m8,n,z
That was fast!
krazie1 said:
There was a new commit added to the open section that "adds dependency on device/qcom/sepolicy"
http://review.cyanogenmod.org/#/q/status:open+project:CyanogenMod/android_device_htc_m8,n,z
Click to expand...
Click to collapse
Thanks for info. I'll probably just wait on that one to get merged as so much is broken already. I doubt selinux will be the cause of frustration right now Also for anyone interested I made the following modifications to the cm12.0 branch to get this to build:
1) Created local_manifest.xml with muppeteers 12.0 branch
2) Commented out DotCase line in device/htc/m8/device.mk (has issues building)
3) Commented out ro.cwm.forbid_mount and ro.cwm.forbid_format lines in device/htc/m8/system.prop (too long)
4) Added missing overlay resources to main resources (copy the missing variables from build/overlay/frameworks/blah.xml to frameworks/blah.xml)
Ive been patiently waiting for cm12 on this beast
This should be in HTC one m8 original development not the Verizon section. If you want more attention and to help people out repose there
jake.99x3 said:
This should be in HTC one m8 original development not the Verizon section. If you want more attention and to help people out repose there
Click to expand...
Click to collapse
Given the intro post on the "original development" forums, I feel my topic is still more applicable in this section.
http://www.xda-developers.com/android/introducing-original-development-forums-for-more-devices/
djh816 said:
Given the intro post on the "original development" forums, I feel my topic is still more applicable in this section.
http://www.xda-developers.com/android/introducing-original-development-forums-for-more-devices/
Click to expand...
Click to collapse
Good point so then move it to android development. Cm is for all device variants not specifically verizon and won't get Much attention here.
jake.99x3 said:
Good point so then move it to android development. Cm is for all device variants not specifically verizon and won't get Much attention here.
Click to expand...
Click to collapse
While I agree it may not get as much attention, I still think this is the proper place. Android development (not m8 android development) is more for universal android projects or new code bases or ROMs for devices that don't have their own sub forum. That being said, this is a build of already existing code so it should go into a "development" section and given that I only plan to get this working on Verizon variant (as that's what I have) I avoided posting to the generic m8 sub forum. Mods can move as they feel fit but I think it belongs here Feel free to repost any info I have here though.
I'm trying to build and I'm getting stuck on the proprietary binaries.
Specifically this:
Code:
make: *** No rule to make target `vendor/htc/m8/proprietary/bin/adsprpcd', needed by `/home/build/cm12/out/target/product/m8/system/bin/adsprpcd'. Stop.
Any advice?
-xdadevelopers-user
xdadevelopers-user said:
I'm trying to build and I'm getting stuck on the proprietary binaries.
Specifically this:
Code:
make: *** No rule to make target `vendor/htc/m8/proprietary/bin/adsprpcd', needed by `/home/build/cm12/out/target/product/m8/system/bin/adsprpcd'. Stop.
Any advice?
-xdadevelopers-user
Click to expand...
Click to collapse
Hmm I didn't run into this. I just used the get-prebuilts command and didn't have any issue after. I followed these but modified for 12.0 branch:
http://forum.xda-developers.com/ver.../how-to-build-cm11-htc-one-m8-082714-t2860056
Just make sure your local_manifest.xml file has the 12.0 muppeteers branch as shown in example on page 6 of that thread.
djh816 said:
Hmm I didn't run into this. I just used the get-prebuilts command and didn't have any issue after. I followed these but modified for 12.0 branch:
http://forum.xda-developers.com/ver.../how-to-build-cm11-htc-one-m8-082714-t2860056
Just make sure your local_manifest.xml file has the 12.0 muppeteers branch as shown in example on page 6 of that thread.
Click to expand...
Click to collapse
@djh816
Hi compile ROM cm11 for a different device
Could you tell me which Java version are you using to build cm12, since you have just built cm12?
I tried to built cm12 yesterday and I got an error for Java so I installed OpenJDK7 and the it started building but I am getting a lot of non-device related error saying "internal compilation error"
I even tried removing all java version and re-installing OpenJDK7. Set alterantives too but no luck.
So please could you let me know which Java Version are you using for building cm12?
OpenJDK7 or Oracle/sun 7
Thanks
macs18max said:
@djh816
Hi compile ROM cm11 for a different device
Could you tell me which Java version are you using to build cm12, since you have just built cm12?
I tried to built cm12 yesterday and I got an error for Java so I installed OpenJDK7 and the it started building but I am getting a lot of non-device related error saying "internal compilation error"
I even tried removing all java version and re-installing OpenJDK7. Set alterantives too but no luck.
So please could you let me know which Java Version are you using for building cm12?
OpenJDK7 or Oracle/sun 7
Thanks
Click to expand...
Click to collapse
I started with clean ubuntu 14.04 lts x64 and added the packages from bracketslash's thread here. Then I just installed openjdk-7-jdk and openjdk-7-jre after that.
djh816 said:
While I agree it may not get as much attention, I still think this is the proper place. Android development (not m8 android development) is more for universal android projects or new code bases or ROMs for devices that don't have their own sub forum. That being said, this is a build of already existing code so it should go into a "development" section and given that I only plan to get this working on Verizon variant (as that's what I have) I avoided posting to the generic m8 sub forum. Mods can move as they feel fit but I think it belongs here Feel free to repost any info I have here though.
Click to expand...
Click to collapse
HTC One M7 has fully working CM12 build, and that is in ANDROID DEVELOPMENT SECTION The Op said that he has working CM12 rom for M8, you might ask him for advice, how to make your build more stable and with less bugs. That's my opinion anyways. You can check the build for M7 here http://forum.xda-developers.com/htc-one/development/5-0-lollipop-unofficial-cm12-android-5-0-t2943826 :good:
djh816 said:
Thanks for info. I'll probably just wait on that one to get merged as so much is broken already. I doubt selinux will be the cause of frustration right now Also for anyone interested I made the following modifications to the cm12.0 branch to get this to build:
1) Created local_manifest.xml with muppeteers 12.0 branch
2) Commented out DotCase line in device/htc/m8/device.mk (has issues building)
3) Commented out ro.cwm.forbid_mount and ro.cwm.forbid_format lines in device/htc/m8/system.prop (too long)
4) Added missing overlay resources to main resources (copy the missing variables from build/overlay/frameworks/blah.xml to frameworks/blah.xml)
Click to expand...
Click to collapse
You don't need to do all of that.
There's one commit and everything works just fine.... nothing's broken.
http://review.cyanogenmod.org/#/c/76760
...and you may just want to thank invisiblek in your original post. He's the only one that did all of the work to bring up the device.
Gunman84 said:
HTC One M7 has fully working CM12 build, and that is in ANDROID DEVELOPMENT SECTION The Op said that he has working CM12 rom for M8, you might ask him for advice, how to make your build more stable and with less bugs. That's my opinion anyways. You can check the build for M7 here http://forum.xda-developers.com/htc-one/development/5-0-lollipop-unofficial-cm12-android-5-0-t2943826 :good:
Click to expand...
Click to collapse
calling @santod040 for some cm love for m8vzw
munchy_cool said:
calling @santod040 for some cm love for m8vzw
Click to expand...
Click to collapse
if someone wants to make a donation to me, i will cherry pick a commit and brunch a completely working build (apart from universal cm issues).
ajrty33 said:
if someone wants to make a donation to me, i will cherry pick a commit and brunch a completely working build (apart from universal cm issues).
Click to expand...
Click to collapse
Welcome to XDA ..
Lollipop Red M8
Q&A for [ROM][DEV][WIP] Ubuntu-Touch port
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][DEV][WIP] Ubuntu-Touch port . If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
konnorrigby said:
I noticed that there is no current port going or started for ubuntu touch, so today i thought i would start that project.
the first thing i noticed was that ubuntu's documentation for porting is one of the worst things ive ever seen, so this will probably end up being kind of a guide until we get a working image or something.
first thing is you will absolutely need Linux. Im using ubuntu for ease of use, although I do build android on arch.
I set up a directory structure on my pc just for android development. i have ~/android/platforms/ in which i have cm11, ubuntu-touch carbon, etc.
so to summarize how i got this started:
Code:
$ mkdir ~/android/platforms/ubuntu-touch-phablet-4.2.2_r1
$ cd ~/android/platforms/ubuntu-touch-phablet-4.2.2_r1
$ repo init -u git://phablet.ubuntu.com/aosp/platform/manifest.git -b phablet-4.2.2_r1 && repo sync -j16
Now im really hoping that is the correct branch. I tried to follow the "porting guide" and its just full of out dated information that lead me to sync a few repos incorrectly. :silly:
after a few failed builds and some common error logs i finally figured i was on the wrong branch. This attempt shall be on 4.2.2_r1 as that appears to be the latest. (I hope)
anyway the rest is still in progress. My sources will be on github for people to help out.
Device
Kernel
also: im on irc on freenode at #oudhitsquad pressy4pie
[update]
i have a huge problem in the real world, so i will have virtually no time to get this updated for now. I am really sorry, hopefully i can get it going again soon
XDA:DevDB Information
Ubuntu Touch , ROM for the ONEPLUS ONE
Contributors
konnorrigby
Version Information
Status: Testing
Created 2014-09-24
Last Updated 2014-10-13
Click to expand...
Click to collapse
Hi ;
What is the current situation? Have developments ?
Thank You
IDK how to delete
...
Man? Are you alright? When you can start dev again?
The project is dead, isn't it?
For everybody here: I have bad news.
The project was stopped.
BUT you can carry it on if you want.
No, I can't programming this. I have only experience with HTML, CSS and a little bit PHP.
Gesendet von meinem A0001 mit Tapatalk
---------- Post added at 06:49 PM ---------- Previous post was at 06:09 PM ----------
But why was it stopped?
Gesendet von meinem A0001 mit Tapatalk
Ubuntu Touch on Oneplus One
Just adding my voice to the crowd of folks who want to see Ubuntu Touch ported to the OPO.
I don't think its over, I think some of the developers are waiting for the porting guide
Acording to one of the Ubuntu Q&A it should be done by the third of feburary (its about 53 mins in, would link by XDA is telling me I'm not allowed to ;-; )
Just a headsup to say that I would still really like a OnePlus One port of Ubuntu Touch! So if there's still anybody out there that is working on this; I send you all my energy!
Adding to the crowd. MultiROM on this would be amazing.
Sailfish, Ubuntu Touch.
New Porting Guide
So people who are still looking to port ubuntu to the oneplus one, you can grab the new porting guide here https://developer.ubuntu.com/en/start/ubuntu-for-devices/porting-new-device/
I hope it gets ported soon, I'm excited
Ubuntu Touch HAS BEEN PORTED!
Mariogrip as he's known on IRC has successfully ported Ubuntu Touch to the OPO!
Q&A for [TOOL] Honor 6 Kernel Toolbox
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [TOOL] Honor 6 Kernel Toolbox. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
For windows
codeworkx said:
update:
fixed some problems
added colored output
added unpack function
added support for l02, l04, l12
Click to expand...
Click to collapse
is there any way to run this on windows 7 ??
anim.tasleem said:
is there any way to run this on windows 7 ??
Click to expand...
Click to collapse
Don't think so.
Yes , with doubletap2wake and sweep2wake will be awesome .
insmod failed
Hello, @codeworkx , I downloaded the kernel source as you described on this post and use it to compile my kernel module, but when I tried to insmod it, it failed:
Code:
[email protected]_l04:/storage/sdcard1/work # insmod ./hello.ko
insmod: init_module './hello.ko' failed (Exec format error)
and here is my Makefile is:
Code:
obj-m := hello.o
ARCH = arm
CROSS_COMPILE = ~/Development/h60/toolchain/arm-eabi-4.7/bin/arm-eabi-
KDIR := ~/Development/h60/out/target/product/hi3630/obj/KERNEL_OBJ
PWD := $(shell pwd)
default:
make ARCH=$(ARCH) CROSS_COMPILE=$(CROSS_COMPILE) -C $(KDIR) M=$(PWD) modules
So what can I do to compile my kernel module and insmod it?
I compile the kernel for my honor 6, but can't boot my device
I used the kernel_tools by codeworkx, and compile the code smoothly.
After I get the boot.img and kernel zip, I reboot to fastboot mode and flash the boot.img to my device. But, the kernel can't boot my honor6.
I checked the kernel header, and found that the ramdisk size is different from the ramdisk of codeworkx's. The ramdisk compile by codeworkx is 0x000fa8d9, mine is 0x000fa126. The zImage size is also different. So, how to solve the preblem?
Sorry for my bad English. I am looking forward to replying.