Database Info

(DEV-WIP) Updated Device Tree for JB 4.2.2

Hi guys first sorry for post in this forum, i no have permission for write in the dev forum.
recently i get this terminal and i know it have a omap4430 and sgx540, so this hardware its similar to the galaxy nexus but jellybean 4.1.2 and 4.2.2 for my works horrible lag and unresponsive, and also something related to a fps issue that make the ui super slow.
so im working and trying to make a updated and revamped device tree for the lge p920 for jb 4.2.2, that include updated powervrsgx 540 modules and propietary drivers update to the lasted 4AJ.2.5, hwc, gralloc, libionpower, domx, libion, bltsville, etc etc. from omapzoom
at this moment i manage to get the updates for the omap44x from omapzoom, and also update the boardconfig for the new sources, its fully buildeable but at this time its not booteable and for my side adb no works for debug it.
so i have propose to all devs here for work together and try to make this work, im not a kernel dev, and my pc its so slow take 5 hours to compile the source. so for all devs here want to help and compile it for trying
this its de device tree:
github.com/samuaz/android_device_lge_p920
and also you need the updated propietary vendor:
github.com/samuaz/proprietary_vendor_lge
it can be buildable with cm10.1, aokp, pacman or whatever 4.2.2 rom
this week i try to rebuild it with a other pvrsources and boardconfig for try to make it booteable
and sorry for my english im spanish
thanks to all

it would be much easier to help you if you would fork a repo and then update the files with a new commit per file
so we can see what you've changed to what

eduzvargas said:
Hi guys first sorry for post in this forum, i no have permission for write in the dev forum.
recently i get this terminal and i know it have a omap4430 and sgx540, so this hardware its similar to the galaxy nexus but jellybean 4.1.2 and 4.2.2 for my works horrible lag and unresponsive, and also something related to a fps issue that make the ui super slow.
so im working and trying to make a updated and revamped device tree for the lge p920 for jb 4.2.2, that include updated powervrsgx 540 modules and propietary drivers update to the lasted 4AJ.2.5, hwc, gralloc, libionpower, domx, libion, bltsville, etc etc. from omapzoom
at this moment i manage to get the updates for the omap44x from omapzoom, and also update the boardconfig for the new sources, its fully buildeable but at this time its not booteable and for my side adb no works for debug it.
so i have propose to all devs here for work together and try to make this work, im not a kernel dev, and my pc its so slow take 5 hours to compile the source. so for all devs here want to help and compile it for trying
this its de device tree:
github.com/samuaz/android_device_lge_p920
and also you need the updated propietary vendor:
github.com/samuaz/proprietary_vendor_lge
it can be buildable with cm10.1, aokp, pacman or whatever 4.2.2 rom
this week i try to rebuild it with a other pvrsources and boardconfig for try to make it booteable
and sorry for my english im spanish
thanks to all
Click to expand...
Click to collapse
how far did you get with this.
in relation to hwc the ics kernel will not cut it there stuff missing i attempted to merge P920 with 3.0.31 kernel from P760
https://mega.co.nz/#!VQQw3BDS!OaeDOEaGSNE36-2ZylQVexGKqIEyrVXMSOBzH7JO2Is
need to fix errors
changes need to happen in
kernel/sound/soc/omap/omap-mcbsp.c
kernel/sound/soc/omap/omap-abe.c
kernel/include/linux/muic/muic.h
kernel/include/linux/fuel_gauge_max17043.h
kernel/include/linux/i2c/twl.h
kernel/include/linux/input/lge_touch_core.h
kernel/include/linux/i2c.h
kernel/include/linux/input.h
kernel/include/linux/cosmo/cosmo_muic.h
kernel/include/video/dsscomp.h
kernel/include/video/omapdss.h
kernel/include/net/ip6_fib.h
kernel/include/config/auto.conf
kernel/include/generated/mach-types.h
kernel/include/generated/autoconf.h
kernel/arch/arm/mach-omap2/hsmmc.c
kernel/arch/arm/mach-omap2/include/mach/lpddr2-elpida.h
kernel/arch/arm/mach-omap2/remoteproc.c
kernel/arch/arm/mach-omap2/prm44xx.c
kernel/arch/arm/mach-omap2/omap4_ion.c
kernel/arch/arm/mach-omap2/gpio.c
kernel/arch/arm/mach-omap2/lpddr2_elpida_data.c
kernel/arch/arm/mach-omap2/omap4_ion.h
kernel/arch/arm/mach-omap2/omap4-reboot-reason.c
kernel/arch/arm/mach-omap2/pm44xx.c
kernel/arch/arm/mach-omap2/lge/include/lge/board/cosmo.h
kernel/arch/arm/mach-omap2/lge/include/lge/board.h
kernel/arch/arm/mach-omap2/lge/Makefile.board
kernel/arch/arm/mach-omap2/lge/lge-common.c
kernel/arch/arm/mach-omap2/lge/cosmo/cosmo_i2c.c
kernel/arch/arm/mach-omap2/lge/cosmo/cosmo_keypad.c
kernel/arch/arm/mach-omap2/lge/cosmo/cosmo_cmdline.c
kernel/arch/arm/mach-omap2/lge/cosmo/cosmo_pdev.c
kernel/arch/arm/mach-omap2/lge/cosmo/cosmo_display.c
kernel/arch/arm/mach-omap2/lge/cosmo/cosmo_mmc.c
kernel/arch/arm/mach-omap2/lge/cosmo/cosmo.c
kernel/arch/arm/configs/cyanogenmod_p920_defconfig
kernel/arch/arm/configs/cosmo_su760_defconfig
kernel/arch/arm/configs/cosmo_p920_defconfig
kernel/arch/arm/plat-omap/Makefile
kernel/fs/proc/base.c
kernel/kernel/timer.c
kernel/drivers/omap_hsi/hsi_driver.h
kernel/drivers/omap_hsi/xmd-tty.c
kernel/drivers/omap_hsi/xmd-hsi-ll.c
kernel/drivers/omap_hsi/hsi_driver_int.c
kernel/drivers/omap_hsi/xmd-hsi-ll-cfg.h
kernel/drivers/omap_hsi/Makefile
kernel/drivers/omap_hsi/xmd-ch.h
kernel/drivers/omap_hsi/hsi_driver.c
kernel/drivers/mmc/core/sd.c
kernel/drivers/video/omap2/displays/panel-lh430wv4-sd02.c
kernel/drivers/video/omap2/displays/panel-lh430wv2-sd01.c
kernel/drivers/video/omap2/dsscomp/dsscomp_adapt.c
kernel/drivers/video/omap2/dsscomp/gralloc.c
kernel/drivers/video/omap2/dsscomp/queue.c
kernel/drivers/video/omap2/dsscomp/device.c
kernel/drivers/video/omap2/vram.c
kernel/drivers/video/omap2/dss/dispc.c
kernel/drivers/video/omap2/dss/hdmi.c
kernel/drivers/video/omap2/dss/hdmi_panel.c
kernel/drivers/video/omap2/dss/gammatable.h
kernel/drivers/video/omap2/dss/core.c
kernel/drivers/input/touchscreen/lge_touch_core.c
kernel/drivers/input/touchscreen/touch_synaptics.c
kernel/drivers/input/touchscreen/lghdk_tm1709_ts.c
kernel/drivers/input/misc/twl6030-pwrbutton.c
kernel/drivers/input/keyboard/omap4-keypad.c
kernel/drivers/usb/gadget/f_mass_storage.c
kernel/drivers/rpmsg/rpmsg_omx.c
kernel/drivers/power/twl6030_bci_battery_ap_fuel.c
kernel/drivers/lge/subpmic/Makefile
kernel/drivers/lge/misc/Makefile
kernel/drivers/lge/Makefile
kernel/drivers/gpu/ion/omap/omap_tiler_heap.c
kernel/.config
kernel/.config.old
Click to expand...
Click to collapse
https://github.com/Pesach85/lge-kernel-omap4/search?p=1&q=CONFIG_MACH_LGE_COSMO&source=cc
i dunno if it would be easier to backport dsscomp to 3.0.21

[DEV] Porting kernel 3.10.x to d2 for Lollipop

As we know, Android Lollipop is being released soon, and it requires a kernel that is 3.10.y, which is not available for our device. I'm not great with kernels and would in no way consider myself a kernel developer, but I have applied the neccessary patches to get the kernel version up to 3.10.0, which can be found here https://github.com/frap129/android_kernel_samsung_d2. Because I'm not a kernel developer, I am looking for some help in at least getting this kernel somewhat ready before the release of 5.0, so we can all get the latest update ASAP. Any and all help is apreciated!

Does your kernel compile and boot on cm11? If it does, there shouldn't be much problems in getting it working on L.

Any news? Does it compile?

frap129 said:
As we know, Android Lollipop is being released soon, and it requires a kernel that is 3.10.y, which is not available for our device. I'm not great with kernels and would in no way consider myself a kernel developer, but I have applied the neccessary patches to get the kernel version up to 3.10.0, which can be found here https://github.com/frap129/android_kernel_samsung_d2. Because I'm not a kernel developer, I am looking for some help in at least getting this kernel somewhat ready before the release of 5.0, so we can all get the latest update ASAP. Any and all help is apreciated!
Click to expand...
Click to collapse
nope android 5.0 doesnt require new kernel, you could build it on 3.0.y like i am doing on my Note 2 oh and as far as i know new nexus devices are still on 3.4.y

Ivan_Meler said:
nope android 5.0 doesnt require new kernel, you could build it on 3.0.y like i am doing on my Note 2 oh and as far as i know new nexus devices are still on 3.4.y
Click to expand...
Click to collapse
yes, but the new Samsung tablets (at least) are being shipped with the 3.10.x kernels.. 'course they're still running kitkat at the moment, but definitely cannot wait to see if/when they get kit kat.
I'll have to report back later after I take pictures of the 'about phone' page lol [if you want proof anyway]

frap129 said:
As we know, Android Lollipop is being released soon, and it requires a kernel that is 3.10.y, which is not available for our device. I'm not great with kernels and would in no way consider myself a kernel developer, but I have applied the neccessary patches to get the kernel version up to 3.10.0, which can be found here https://github.com/frap129/android_kernel_samsung_d2. Because I'm not a kernel developer, I am looking for some help in at least getting this kernel somewhat ready before the release of 5.0, so we can all get the latest update ASAP. Any and all help is apreciated!
Click to expand...
Click to collapse
ztotherad said:
yes, but the new Samsung tablets (at least) are being shipped with the 3.10.x kernels.. 'course they're still running kitkat at the moment, but definitely cannot wait to see if/when they get kit kat.
I'll have to report back later after I take pictures of the 'about phone' page lol [if you want proof anyway]
Click to expand...
Click to collapse
I know samsung does things like that (i have few other devices from them) but hey thats samsung and they are lazy so they dont want to update kernel version after device is relesed so they do this not to feel outdated on softwere side

Whoops! I read somewhere that the newly expanded SELinux permissions had some dependency on the 3.10.y kernel. Oh well, I guess Ill just test it anyways so I can brag that I have a newer kernel than anyone else if it works

frap129 said:
Whoops! I read somewhere that the newly expanded SELinux permissions had some dependency on the 3.10.y kernel. Oh well, I guess Ill just test it anyways so I can brag that I have a newer kernel than anyone else if it works
Click to expand...
Click to collapse
That would definitely be awesome! Be sure to report back your results. I'm not an experienced ROM or kernel developer, but I'll be attempting on bringing a pure AOSP 5.0.0_r2 to my GS3. I'm not sure how successful I'll be, but my first step involved me planning on copying over our vendor repo from CM's M11 or M12 release (whenever that gets out) and trying to build Lollipop against it.

polarEskimo said:
That would definitely be awesome! Be sure to report back your results. I'm not an experienced ROM or kernel developer, but I'll be attempting on bringing a pure AOSP 5.0.0_r2 to my GS3. I'm not sure how successful I'll be, but my first step involved me planning on copying over our vendor repo from CM's M11 or M12 release (whenever that gets out) and trying to build Lollipop against it.
Click to expand...
Click to collapse
I was planning on working on that as well over the weekend.

polarEskimo said:
That would definitely be awesome! Be sure to report back your results. I'm not an experienced ROM or kernel developer, but I'll be attempting on bringing a pure AOSP 5.0.0_r2 to my GS3. I'm not sure how successful I'll be, but my first step involved me planning on copying over our vendor repo from CM's M11 or M12 release (whenever that gets out) and trying to build Lollipop against it.
Click to expand...
Click to collapse
You will need to change many things in device tree to get it compile oh and dont forget to disable cm overlays

Ivan_Meler said:
You will need to change many things in device tree to get it compile oh and dont forget to disable cm overlays
Click to expand...
Click to collapse
I'm very new to the AOSP build process and didn't have much luck last night getting the CM device sources to play nicely with AOSP. I'm finding it difficult to find any relevant guides on porting over the CM device trees to pure AOSP. If you or anyone else can help by explaining the process or pointing to a guide that I may have missed, I'd be grateful. Plus the more people we have collaborating on his, the better our chances of getting Lollipop on our devices.

I'm working on porting 5.0 to our phone, tweaked the device tree and got the build running but (as expected) i'm running into SEpolicy hell. The new selinux implementation in lollipop is proving to be trouble. I've just made a few more edits and the build is moving along, I'll post results shortly.
If anyone cares to help I'll walk you through what I've done so far. One thing to note is you need to adjust vendorsetup.sh to say full_d2lte-eng instead of cm_d2lte-eng and create AndroidProducts.mk that points at full_d2lte.mk (you can use the hammerhead device tree as a reference to do this)
That will get your device tree to regester properly. If you don't do the above you'll get a "no config makefile found" error when you try to select d2lte with lunch.
As far as the actual tree, you're gonna wanna grab device/samsung/d2lte, device/samsung/msm8960-common, vendor/samsung/d2lte, vendor/samsung/msm8960-common, vendor/cm, vendor/cyngn, and kernel/d2.
You'll also need a couple things from /hardware, namely hardware/samsung. There's a couple things you'll need to remove from msm8960-common in /device, I can't remember the specific file name but the error message will tell you.
Follow those instructions and you'll get where I'm at, with the build crapping out on SEpolicy

Restl3ss said:
I'm working on porting 5.0 to our phone, tweaked the device tree and got the build running but (as expected) i'm running into SEpolicy hell. The new selinux implementation in lollipop is proving to be trouble. I've just made a few more edits and the build is moving along, I'll post results shortly.
If anyone cares to help I'll walk you through what I've done so far. One thing to note is you need to adjust vendorsetup.sh to say full_d2lte-eng instead of cm_d2lte-eng and create AndroidProducts.mk that points at full_d2lte.mk (you can use the hammerhead device tree as a reference to do this)
That will get your device tree to regester properly. If you don't do the above you'll get a "no config makefile found" error when you try to select d2lte with lunch.
As far as the actual tree, you're gonna wanna grab device/samsung/d2lte, device/samsung/msm8960-common, vendor/samsung/d2lte, vendor/samsung/msm8960-common, vendor/cm, vendor/cyngn, and kernel/d2.
You'll also need a couple things from /hardware, namely hardware/samsung. There's a couple things you'll need to remove from msm8960-common in /device, I can't remember the specific file name but the error message will tell you.
Follow those instructions and you'll get where I'm at, with the build crapping out on SEpolicy
Click to expand...
Click to collapse
Wow, this is awesome. It sounds like you've gotten the furthest than any of us. I appreciate the instructions, but is there any chance you could push your repos to GitHub? And do you think the SELinux stuff you're running into has anything to do with our device being on the 3.4 kernel instead of 3.10?

polarEskimo said:
Wow, this is awesome. It sounds like you've gotten the furthest than any of us. I appreciate the instructions, but is there any chance you could push your repos to GitHub? And do you think the SELinux stuff you're running into has anything to do with our device being on the 3.4 kernel instead of 3.10?
Click to expand...
Click to collapse
It's not a kernel thing so much as a device tree thing. (Kitkat vs lollipop) the policy.conf (along with a few other things) in the device tree is designed for kitkat and isn't playing very nice with the 5.0 source. I'm trying to bang it out a bit by swapping a few C and header files in the build core.
As for my last build, my tweaks got me past where I was but now I'm hanging on a new set of SElinux errors.
I've been at this for less than 12 hours so given that timeframe this looks promising.
I'm trying to think of what the best way to go about this is. I could either try to adapt the tree for the new source or I could try to adapt the source for the old tree (use KitKat SElinux implementation on lollipop). The latter would have more success with root but the former is the correct way to do it (and would get us cyanogenmod 12 faster once they start nightlies, as I can push the changes to gerrit)

Restl3ss said:
It's not a kernel thing so much as a device tree thing. (Kitkat vs lollipop) the policy.conf (along with a few other things) in the device tree is designed for kitkat and isn't playing very nice with the 5.0 source. I'm trying to bang it out a bit by swapping a few C and header files in the build core.
As for my last build, my tweaks got me past where I was but now I'm hanging on a new set of SElinux errors.
I've been at this for less than 12 hours so given that timeframe this looks promising.
I'm trying to think of what the best way to go about this is. I could either try to adapt the tree for the new source or I could try to adapt the source for the old tree (use KitKat SElinux implementation on lollipop). The latter would have more success with root but the former is the correct way to do it (and would get us cyanogenmod 12 faster once they start nightlies, as I can push the changes to gerrit)
Click to expand...
Click to collapse
Again, any chance you can post your source? You don't have to try and work on it on your own. The more people that look at the progressions you made, the better our chances are at success.

polarEskimo said:
Again, any chance you can post your source? You don't have to try and work on it on your own. The more people that look at the progressions you made, the better our chances are at success.
Click to expand...
Click to collapse
I'll push what I've got to github after this experiment

Cyanogen is updating sources to lolipop right now and omni has semi working source so it will be easier to port 5.0 since we wont need to edit device tree that much

Ivan_Meler said:
Cyanogen is updating sources to lolipop right now and omni has semi working source so it will be easier to port 5.0 since we wont need to edit device tree that much
Click to expand...
Click to collapse
Yes but, they have a tentative deadline of dec. 1st to start pushing out the first nightlies. We likely won't be in the first wave either, since d2 is now 3 generations out of date.
I'd much rather just port aosp and have it in 2 weeks rather than wait 3 weeks to even begin work.
Side note. If/when I get this working I'm calling it PotatOS

Managed to work past my problem with SElinux for now, the build has now moved on to... another set of errors!
Build currently hangs at this:
Code:
host C++: libutils_32 <= system/core/libutils/StopWatch.cpp
host C++: libutils_32 <= system/core/libutils/String8.cpp
host C++: libutils_32 <= system/core/libutils/String16.cpp
host C++: libutils_32 <= system/core/libutils/SystemClock.cpp
host C++: libutils_32 <= system/core/libutils/Threads.cpp
host C++: libutils_32 <= system/core/libutils/Timers.cpp
system/core/libutils/Timers.cpp: In function 'nsecs_t systemTime(int)':
system/core/libutils/Timers.cpp:43:13: error: 'CLOCK_BOOTTIME' was not declared in this scope
build/core/binary.mk:618: recipe for target 'out/host/linux-x86/obj32/STATIC_LIBRARIES/libutils_intermediates/Timers.o' failed
make: *** [out/host/linux-x86/obj32/STATIC_LIBRARIES/libutils_intermediates/Timers.o] Error 1
#### make failed to build some targets (01:19 (mm:ss)) ####
Going to bed, will get back at it in the morning. Source should be up on github by tomorrow night

Restl3ss said:
Yes but, they have a tentative deadline of dec. 1st to start pushing out the first nightlies. We likely won't be in the first wave either, since d2 is now 3 generations out of date.
I'd much rather just port aosp and have it in 2 weeks rather than wait 3 weeks to even begin work.
Side note. If/when I get this working I'm calling it PotatOS
Click to expand...
Click to collapse
I'm with you on that, I'd rather have pure AOSP than buggy CM nightlies. Also interesting choice of ROM name lol. Thanks for your hard work and I'm looking forward to pulling down your repos so I can take a stab at these compile-time issues.

[ROM][11-17-2014][5.0] Unofficial CM12 Builds

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

WIP* ( port) Linage OS LG Stylo 2 plus

Development is dead. Please delete..

Rmontoya83 said:
Good news I have a working Linage OS 13 build for the lg stylo 2 Plus GSM. Thought it was bug free still has some issues though . My PC took a dump I have the sources saved on my hard drive I will have a new PC on Feb 6 and will release the Rom For Free probably with in a few days from then. As I'm almost done porting a working lineage OS 14 for the device.
I will update the device tree on Github So I can get help from other devs to trouble shoot these issues better and collaborate works. I will also include a working recovery with the Rom for free . I am doing this in my free time so please be patient .
I will keep you posted ?
Any people interested in helping let me know.
Click to expand...
Click to collapse
I am interested in helping, I have the metropcs variant.
Latest up to date software. Due to that I have no root
LG Stylo 2 PLUS
TWRP no ROOT

cragains said:
I am interested in helping, I have the metropcs variant.
Latest up to date software. Due to that I have no root
LG Stylo 2 PLUS
TWRP no ROOT
Click to expand...
Click to collapse
You can downgrade your firmware .

Nice work let me know when the source is up at github , i may be able to help

I'm so anxious I can't wait to get my new PC! I will be compiling a lot faster. You guys are going to like this lineage OS port. Hang in there

Any screenshots?
I'm interested in this also

Pelegius22 said:
Any screenshots?
I'm interested in this also
Click to expand...
Click to collapse
Not at the moment I had the backlight on my display burn out . had to flash the stock rom back for warranty purposes and for some reason every time I try and back up via twrp the data gets corrupted.
So the only place I have a working Rom is stored on a hard drive and I get my PC back on the 6th this month so it will be up soon.

Twrp link

Rmontoya83 said:
You can downgrade your firmware .
Click to expand...
Click to collapse
No PC right now, I moved across the state, and left my PC.
Can't down grade
LG Stylo 2 PLUS
TWRP no ROOT

Got the new laptop up and running building starts tommorrow.

All souces are downloaded . I will start building the device tree tonight hopefully by end of week myself and @messi2050 will have a working lineage OS build for the ph2n. I stood up all night working on the list of proprietary files need for the build.
Now comes the hard work of adding all the required blobs to get it all functional please be patient. As we are doing this in out free time. Once the device tree is all setup it will be a lot easier to port other roms to this device such as omni aokp DU and so much more. I chose a 13 build as I'm new to this and its a lot easier to port a Rom that has many components that are stable with the version.
If you appreciate our work buy us a cup of coffee. Or hit the thanks button for the Devs working on this build .
Thanks to all the xda community.

We should work on a changelog concerning drivers for cheaper models like my tmousa k550.

(((Poll )))) custom kernel with more governors and overclock or stock kernel?

Rmontoya83 said:
(((Poll )))) custom kernel with more governors and overclock or stock kernel?
Click to expand...
Click to collapse
Custom kernel with more governors and overclock! Let me know if you need me to test, I have MetroPCS variant. Thank you also for your time and development for this amazing device!

Rmontoya83 said:
(((Poll )))) custom kernel with more governors and overclock or stock kernel?
Click to expand...
Click to collapse
Custom all the way.
I am sending this to you in hopes of curing my boredom...

Montoya, how are you getting the blobs? I have root when want it, I just don't right now. I have teamoctos synced, I have all the source code for our device. I'm not much of a programmer, but let me know I can help. I have Ubuntu with all the packages for compiling.

we need all the help we can get
Giminji said:
Montoya, how are you getting the blobs? I have root when want it, I just don't right now. I have teamoctos synced, I have all the source code for our device. I'm not much of a programmer, but let me know I can help. I have Ubuntu with all the packages for compiling.
Click to expand...
Click to collapse
@messi2050
has one repository done for device /device
i have the other kernel/
i am working on the blobs using @JackpotClavin utility tool to pull all the blobs needed for the build. once we have a stable tree we can work on building other roms.

Good news we have the the last branch to the tree built so builds will start this week sometime. We have a lot of work ahead still so be patient.
Tree source and blobs are on github.
https://github.com/RichieRich83
@messi2050
You rock brother.

Rmontoya83 said:
Good news we have the the last branch to the tree built so builds will start this week sometime. We have a lot of work ahead still so be patient.
Tree source and blobs are on github.
URL deleted I am too new.
@messi2050
You rock brother.
Click to expand...
Click to collapse
Both you and Messi are doing amazing things. When this is done, both of you are getting a cup of java (I couldn't resist Java instead of Joe or Coffee). I downloaded the jackpotcalvindonkey thing yesterday, did the make on it, but didn't get it out.
Btw, your github shows no public repos.

Well that was quick

How to port rom from HTC sensation?

I have an One s with S3 processer(villeC2).
Its specs are similar to sensation(with same cpu and screen resolution),but sensation has Android 7.1 ROM and one s only 4.4......
I would like to port a ROM for it from sensation.
Does anyone know how to do that?
Or if it is possible ?
(sorry for my bad english)
(my first post)

Some info !
Hi,
Actually I'm new in building roms and kernels, too. But i can share some info with you.
For starting this tutorial may be helpful: [Guide] Compile 4.2 & 4.3 & 4.4 Roms for villec2
As you can see, you will need "device", "vendor" and "kernel" source to build a rom.
Usually you can find source code of roms and kernels in xda threads and can start from those.
For example for Android 7.1 you can use RROS vendor and VilleC2 device and kernel sources. (Note: i don't know are these examples compatible or not?!)
And for kernel, maybe you has to upstream the kernel source to be compatible with new version of android that you want to build.
Good luck.
-----------------------------------
Edit:
After Compiling for myself, i figured out Vendor files for choosed rom (Lineage, RR, ..) will be included by their manifest files automatically. so for "Vendor" part in "local_manifest.xml" (or newer "local_manifests/roomservice.xml") we need to assign "proprietary_vendor" files related to our devices. "proprietary_vendor" files can be extracted manully if there isn't any online source.
one more useful guide: [GUIDE]Building any ROM from source for HTC One S aka ville!