[Discussion] Project CM12.1 for LG G4. Absolutly Alpha!! Dont ask for ETA Or Download

Search This thread

MetaIIica

Senior Member
Aug 30, 2012
1,568
2,620
Saarbrücken
after a small look i have found CM12.1 Repos for our H815 and i think we start now Tests to get workable Builds... Think, the first way are dirty but who cares :D

https://github.com/lg-devs

i have nothing to do with this and this is not my three so the credits and thanks are given to LG-Devs

think this are the Devicetree what we need:

https://github.com/lg-devs/proprietary_vendor_lge
https://github.com/lg-devs/android_device_lge_g4-common
https://github.com/lg-devs/android_device_lge_h815
https://github.com/lg-devs/android_kernel_lge_msm8994

lets get start united :D
 
Last edited:

xadet

Member
Dec 9, 2009
11
10
I've had this building since Friday but unfortunately it gets stuck at the LG screen. I'm going to play around again this afternoon and see where I can get to.

Although the Github description for the msm8994 kernel says "G4", the H815 needs the msm8992 kernel. Also the partition sizes in g4-common aren't correct for the H815, they need to be

Code:
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 4341104640
BOARD_USERDATAIMAGE_PARTITION_SIZE := 24897388544

This is the local manifest I've been using

Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
  <project name="CyanogenMod/android_device_qcom_common" path="device/qcom_common" remote="github" revision="cm-12.1" />
  <project name="lg-devs/android_device_lge_g4-common" path="device/lge/g4-common" remote="github" revision="cm-12.1" />
  <project name="lg-devs/android_device_lge_h815" path="device/lge/h815" remote="github" revision="cm-12.1" />
  <project name="lg-devs/android_kernel_lge_msm8992" path="kernel/lge/msm8992" remote="github" revision="cm-12.1" />
  <project name="CyanogenMod/android_hardware_qcom_audio" path="hardware/qcom/audio-caf/msm8992" remote="github" revision="cm-12.1-caf-8994" />
  <project name="CyanogenMod/android_hardware_qcom_display" path="hardware/qcom/display-caf/msm8992" remote="github" revision="cm-12.1-caf-8994" />
  <project name="CyanogenMod/android_hardware_qcom_media" path="hardware/qcom/media-caf/msm8992" remote="github" revision="cm-12.1-caf-8994" />
  <project name="lg-devs/proprietary_vendor_lge" path="vendor/lge" remote="github" revision="cm-12.1-caf" />
</manifest>
 

sardroid

Senior Member
Apr 21, 2009
2,405
2,798
Poland
www.androidnow.pl
Although the Github description for the msm8994 kernel says "G4", the H815 needs the msm8992 kernel. Also the partition sizes in g4-common aren't correct for the H815, they need to be

In github is description for the msm8992 kernel:
 

Attachments

  • 2015-07-05_165801.png
    2015-07-05_165801.png
    6.4 KB · Views: 2,529

janjan

Recognized Developer
May 20, 2007
3,209
3,447
Aalborg
tweaksyourandroid.weebly.com
I successfully build ROM + kernel but fails to flash. Some thing to do with............" failed to mount /dev/blocl/bootdevice/by-name/system......"I also tried to flash the kernel over the stock ROM and it seems to boot fine.

update: Ummm it seems to be fine with twrp-2.8.7.0-h815.img. I can see the CM boot animation..keep fingers crossing.
 
Last edited:

janjan

Recognized Developer
May 20, 2007
3,209
3,447
Aalborg
tweaksyourandroid.weebly.com
Acutally you can use the one from the #1.... It should work..

Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
  <project name="CyanogenMod/android_device_qcom_common" path="device/qcom_common" remote="github" revision="cm-12.1" />
  <project name="lg-devs/android_device_lge_g4-common" path="device/lge/g4-common" remote="github" revision="cm-12.1" />
  <project name="lg-devs/android_device_lge_h815" path="device/lge/h815" remote="github" revision="cm-12.1" />
  <project name="lg-devs/android_kernel_lge_msm8992" path="kernel/lge/msm8992" remote="github" revision="cm-12.1" />
  <project name="CyanogenMod/android_hardware_qcom_audio" path="hardware/qcom/audio-caf/msm8992" remote="github" revision="cm-12.1-caf-8994" />
  <project name="CyanogenMod/android_hardware_qcom_display" path="hardware/qcom/display-caf/msm8992" remote="github" revision="cm-12.1-caf-8994" />
  <project name="CyanogenMod/android_hardware_qcom_media" path="hardware/qcom/media-caf/msm8992" remote="github" revision="cm-12.1-caf-8994" />
  <project name="lg-devs/proprietary_vendor_lge" path="vendor/lge" remote="github" revision="cm-12.1-caf" />
</manifest>
[/QUOTE]
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 25
    I successfully build ROM + kernel but fails to flash. Some thing to do with............" failed to mount /dev/blocl/bootdevice/by-name/system......"I also tried to flash the kernel over the stock ROM and it seems to boot fine.

    update: Ummm it seems to be fine with twrp-2.8.7.0-h815.img. I can see the CM boot animation..keep fingers crossing.
    19
    CM12.1 on LG G4 H811

    I just got CM12.1 to boot on my H811!!!:D
    17
    H815:

    Wifi is fixed!

    Sent from my XT1039 using XDA Free mobile app
    15
    after a small look i have found CM12.1 Repos for our H815 and i think we start now Tests to get workable Builds... Think, the first way are dirty but who cares :D

    https://github.com/lg-devs

    i have nothing to do with this and this is not my three so the credits and thanks are given to LG-Devs

    think this are the Devicetree what we need:

    https://github.com/lg-devs/proprietary_vendor_lge
    https://github.com/lg-devs/android_device_lge_g4-common
    https://github.com/lg-devs/android_device_lge_h815
    https://github.com/lg-devs/android_kernel_lge_msm8994

    lets get start united :D
    15
    Calling for Help

    Hello users,

    Things have come to light and we found out some unfortunate news. I wish not to disclose that news because it was a huge misunderstanding and we would really just like to take matters into our own hands.

    Our main developer @genesixxbf3) who has been putting in LOADS of effort (producing over 25 builds this week alone for testing between H811, and H815) has been doing all this work thanks to many of our testers and our other joint developers.

    We have made significant progress within the last week. We gathered our own circle of developers actively working around the clock attempting to bring CM 12.1 to our device in full functionality. Great success has been made.

    @graig79 was the first one who managed to get the H811 booting on his own device pulling from multiple different sources and device trees in order to get the RAMDISK to even start and allow you into the device, providing our first look at CM12.1 on the LG H811.

    @bart452 has made significant improvements on @graig79 's work. Bringing GPS, WiFi, and preliminary bluetooth support to our device.

    @mythos234 and @genesixxbf3 : the powerhouses behind this ROM. @mythos234 has been doing kernel work while @genesixxbf3 has been helping him understand and make changes that ultimately solved our thermal issues (as the build would heat up the device and cause constant reboots)

    @graig79, @bart452, and @genesixxbf3 have been pouring builds into our test channels for both devices overtime in hopes of fixing RIL, Camera, and Bluetooth, which pretty much sums up the remaining problems...


    I apologize to anyone I haven't given credit to, and possibly mixed up the stories/credits, and will fix when/if needed, but as the voice that has brought all the testers together to assist in bringing the G4 CM 12.1 as quick as possible I hope to succeed in providing one last thing...

    Now... I ask of you, XDA Community, to help pitch in, every little bit helps.
    Our buddy @genesixxbf3 needs a device that he can continue to maintain and help solve the problems on his own, because once school comes for him, he will be forced to do it on his own time and we may be without a maintainer. So let's secure it while we still can.
    Within the H811 test group alone we have accumulated about $100. Looking on Swappa now I have found a H815 device for $440. If we can get $360 donated to @genesixxbf3 with his provided Paypal account (just be sure it's to genesixxbf3@gmail.com) He may be able to purchase the device and have it shipped to him and start working on it more effectively on his own terms soon.

    If this is not allowed, Please, just PM me and I will removed the post, But I really don't want to see Erwan's best efforts go to waste because he can't maintain on a device he doesn't own. Let's be the ones to make it happen.


    Thank you community, I hope we can get what we need and soon. :)