Compiling Roms Thread: Build errors, bootloops, ... - G2 Developer Discussion [Developers Only]

Hi everybody!
Finally, our LG G2 got an Developer Discussion area. So I decided to create this thread:
This thread is set up for people who want to compile roms for our great device. Perhaps you compiled already
a rom sucessfull but the rom isn't booting? Post it here! Errors during the compile process? Again, write it in this
section here. Apps are crashing on your compiled rom? In here again!
This thread should be kept clean, no offtopic, this means no questions when a rom will be published.
This area should only be for devs or for people who want to get one.
Thank you and happy compiling!!!

Flo0008 said:
Hi everybody!
I need help from devs please:
So, I built Slim LP for the D802 but my problem is I am stuck in a bootloop (at the LG logo) after a clean installation.
I use the GCC 4.8 toolchain to compile the rom and the kernel.
Perhaps a dev can take a look on my local_manifest.xml if there are missing any needed repos.
Slim LP: https://github.com/Flo0008/android_scripts/blob/lp5.0/.repo/local_manifests/local_manifest.xml
Device tree:
https://github.com/Flo0008/android_device_lge_d802
https://github.com/Flo0008/android_device_lge_g2-common
I ran . build/envsetup.sh, then lunch slim_d802-userdebug and then make -j8 otapackage.
Do I have to run another command?
Thanks in advance!
Perhaps @arcardinal, have you an idea what causes the bootloop?
Sent from my LG-D802 using XDA Free mobile app
Click to expand...
Click to collapse
How far do you get? Do you see Slim's boot logo? Also when you open the created zip, does everything look to be there? Like boot.img and such? Can you think of any more info?

RenderBroken said:
How far do you get? Do you see Slim's boot logo? Also when you open the created zip, does everything look to be there? Like boot.img and such? Can you think of any more info?
Click to expand...
Click to collapse
Thanks firstly for your help!
I get until the LG bootlogo, not further. I didn't see the bootlogo of Slimrom.
I have the same problem with AOSP, I don't get further than the LG logo.
SlimLP: After some time (at the LG logo) the phone starts vibrating but not more.
I flashed the roms via TWRP recovery and my phone is running the latest KK version 20h.
The boot.img is there and seems ok with a size of about 5.7Mb in the .zip file, the system folder seems to be complete and the META folder is also there.
In the thread of another device I read something about a problem with com.qualcomm.location in system/app or anything but I can't find this file there.
There were no errors during the flash-process on my device too. A problem I recogniced on AOSP LP was when I rebooted the device after flashing the rom with TWRP, that I got on a screen where on the top left is written:
[650] Fastboot mode started
[700] udc_start()
For both roms I used the kernel source of lg-dev's repo. One weird thing I recognized on AOSP was that the .zip file has only about 166Mb, SlimLP has a .zip size of aroung 195Mb.
I was thinking about that I am perhaps missing any device specific repo here on my local_manifest: https://github.com/Flo0008/android_scripts/blob/aosp_g2/.repo/local_manifests/local_manifest.xml
or I asked myself if I have to run any file like extract-files.sh in the device repo here: https://github.com/Flo0008/android_device_lge_d802/tree/aosp5.0.
One more thing I tried was to replace the boot.img of both roms with that one from CM's. Nevertheless nothing changed, the rom didn't boot up.
If you need more information please tell me.
Thank you very much!!!

Flo0008 said:
Thanks firstly for your help!
I get until the LG bootlogo, not further. I didn't see the bootlogo of Slimrom.
I have the same problem with AOSP, I don't get further than the LG logo.
SlimLP: After some time (at the LG logo) the phone starts vibrating but not more.
I flashed the roms via TWRP recovery and my phone is running the latest KK version 20h.
The boot.img is there and seems ok with a size of about 5.7Mb in the .zip file, the system folder seems to be complete and the META folder is also there.
In the thread of another device I read something about a problem with com.qualcomm.location in system/app or anything but I can't find this file there.
There were no errors during the flash-process on my device too. A problem I recogniced on AOSP LP was when I rebooted the device after flashing the rom with TWRP, that I got on a screen where on the top left is written:
[650] Fastboot mode started
[700] udc_start()
For both roms I used the kernel source of lg-dev's repo. One weird thing I recognized on AOSP was that the .zip file has only about 166Mb, SlimLP has a .zip size of aroung 195Mb.
I was thinking about that I am perhaps missing any device specific repo here on my local_manifest: https://github.com/Flo0008/android_scripts/blob/aosp_g2/.repo/local_manifests/local_manifest.xml
or I asked myself if I have to run any file like extract-files.sh in the device repo here: https://github.com/Flo0008/android_device_lge_d802/tree/aosp5.0.
One more thing I tried was to replace the boot.img of both roms with that one from CM's. Nevertheless nothing changed, the rom didn't boot up.
If you need more information please tell me.
Thank you very much!!!
Click to expand...
Click to collapse
Did I understand right that you are on a KK Bootloader? You need to be on a JB Bootloader for all of the current LP Source out right now. Try that and see if you get any further.

Wow..finally someone tryin to port slimlp..hope u get it Working??

Thanks again. Yes I am on KK bootloader but I dont understand why Cyanogenmod 12 is working. But thanks for the information, I will try it.
Sent from my LG-D802 using XDA Free mobile app

So, what I did now: I flashed the JB baseband on my device via TWRP, rebooted to recovery and flashed SlimLP, but I still get a bootloop.
Or should I flash the .kdz of a JellybeanRom?
And do you know how to fix this error? I get it when I try to build AOSP LP.
/bin/sh: 1: cd: can't cd to out/target/product/d802/obj/KERNEL_OBJ
make[1]: Entering directory `/home/fabio/rasta/kernel/lge/msm8974'
Makefile:121: *** output directory "out/target/product/d802/obj/KERNEL_OBJ" does not exist. Stop.
make[1]: Leaving directory `/home/fabio/rasta/kernel/lge/msm8974'
make: *** [out/target/product/d802/obj/KERNEL_OBJ/.config] Error 2
make: *** Waiting for unfinished jobs....
Sent from my LG-D802 using XDA Free mobile app

First:
In root directory of rom: make clean -> this should fix build error.
My proposition:
1. repo init -u https://github.com/SlimRoms/platform_manifest -b lp5.0-caf
2. roomservice.xml need to looks like:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
# Device Specific part
<project path="device/lge/d802" name="Flo0008/android_device_lge_d802" revision="lp5.0" remote="github" />
<project path="device/lge/g2-common" name="Flo0008/android_device_lge_g2-common" revision="lp5.0" remote="github" />
<project path="kernel/lge/msm8974" name="Flo0008/android_kernel_lge_msm8974" revision="cm-12.0" remote="github" />
<project path="vendor/lge" name="Flo0008/proprietary_vendor_lge" revision="cm-12.0" remote="github" />
</manifest>
Click to expand...
Click to collapse
3. repo sync.
4.
. build/envsetup.sh
brunch d802
Try this if you want.
---------- Post added at 11:34 AM ---------- Previous post was at 11:24 AM ----------
When finish building of DU will try SlimLP
---------- Post added at 11:36 AM ---------- Previous post was at 11:34 AM ----------
SlimLP has a .zip size of aroung 195Mb.
Click to expand...
Click to collapse
Size of compiled CM12 is about 240 MB -> something is missing in your build...
---------- Post added at 11:44 AM ---------- Previous post was at 11:36 AM ----------
look here:
https://github.com/TheMuppets/proprietary_vendor_lge/blob/cm-12.0/d802/d802-vendor-blobs.mk
See how much blobs is there...
insteed of using your blobs try TheMuppets's blobs:
https://github.com/TheMuppets/proprietary_vendor_lge
add this to roomservice.xml
---------- Post added at 11:50 AM ---------- Previous post was at 11:44 AM ----------
My last proposition is to try using cm device tree and kernel...
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
# Device Specific part
<project path="device/lge/d802" name="CyanogenMod/android_device_lge_d802" revision="cm-12.0" remote="github" />
<project path="device/lge/g2-common" name="CyanogenMod/android_device_lge_g2-common" revision="cm-12.0" remote="github" />
<project path="kernel/lge/msm8974" name="CyanogenMod/android_kernel_lge_msm8974" revision="cm-12.0" remote="github" />
<project path="vendor/lge" name="TheMuppets/proprietary_vendor_lge" revision="cm-12.0" remote="github" />
</manifest>
Click to expand...
Click to collapse
Then make some changes in device/lge/d802 .

Thanks for your answer. I use already CM device repos (from lg-devs), all device specific folders are picked from them and I modified only some things for SlimLP.
I have to use the caf branch of Slim?
Sent from my LG-D802 using XDA Free mobile app

Flo0008 said:
Thanks for your answer. I use already CM device repos (from lg-devs), all device specific folders are picked from them and I modified only some things for SlimLP.
I have to use the caf branch of Slim?
Sent from my LG-D802 using XDA Free mobile app
Click to expand...
Click to collapse
I think this is problem with blobs... Try using TheMuppets and will see
---------- Post added at 12:21 PM ---------- Previous post was at 12:18 PM ----------
Yes, need CAF branch

Is Rashed using the caf branch for CM too?
Sent from my LG-D802 using XDA Free mobile app

Flo0008 said:
Is Rashed using the caf branch for CM too?
Sent from my LG-D802 using XDA Free mobile app
Click to expand...
Click to collapse
I'm building my own CM12 daylies and using standard CM sources.
EDIT:
Building and not sharing, only for my personal use.

@RenderBroken
Can you or anybody else help me with this build error on AOSP Lollipop?
Target boot image: /data1/Flo0008/aosp_g2/out/target/product/d802/boot.img
usage: mkbootimg
--kernel <filename>
--ramdisk <filename>
[ --second <2ndbootloader-filename> ]
[ --cmdline <kernel-commandline> ]
[ --board <boardname> ]
[ --base <address> ]
[ --pagesize <pagesize> ]
-o|--output <filename>
device/lge/g2-common/releasetools/mkbootimg.mk:47: recipe for target '/data1/Flo0008/aosp_g2/out/target/product/d802/boot.img' failed
make: *** [/data1/Flo0008/aosp_g2/out/target/product/d802/boot.img] Error 1
make: *** Waiting for unfinished jobs....
Thanks in advance.

Wished i had knowledge i would help.
If u need any tester for d802 u can Holla at me..
Maybe ASK @varund7726 Compiler of resurection remix he did Good job on the Rom...maybe he can give u advice..since he is a Good dev who also helps others.
Good luck my friend..

Flo0008 said:
@RenderBroken
Can you or anybody else help me with this build error on AOSP Lollipop?
Target boot image: /data1/Flo0008/aosp_g2/out/target/product/d802/boot.img
usage: mkbootimg
--kernel <filename>
--ramdisk <filename>
[ --second <2ndbootloader-filename> ]
[ --cmdline <kernel-commandline> ]
[ --board <boardname> ]
[ --base <address> ]
[ --pagesize <pagesize> ]
-o|--output <filename>
device/lge/g2-common/releasetools/mkbootimg.mk:47: recipe for target '/data1/Flo0008/aosp_g2/out/target/product/d802/boot.img' failed
make: *** [/data1/Flo0008/aosp_g2/out/target/product/d802/boot.img] Error 1
make: *** Waiting for unfinished jobs....
Thanks in advance.
Click to expand...
Click to collapse
This error means that the mkbootimg tool you have is not the correct one. Apparently there are more than one out there and the other supports different flags. Use the one here:
https://github.com/RenderBroken/mkbootimg_tools
Also CAF (to me) doesnt seem to be ready as a Daily Driver. Are you just wanting to mess around or get out a fully functioning build? I do know that LG-Devs CAF branch is still being worked on. Not sure about TheMuppets but they are always solid. Still LP CAF is not stable yet.
---------- Post added at 02:19 PM ---------- Previous post was at 02:17 PM ----------
reaper61616 said:
First:
In root directory of rom: make clean -> this should fix build error.
My proposition:
1. repo init -u https://github.com/SlimRoms/platform_manifest -b lp5.0-caf
2. roomservice.xml need to looks like:
3. repo sync.
4.
. build/envsetup.sh
brunch d802
Try this if you want.
---------- Post added at 11:34 AM ---------- Previous post was at 11:24 AM ----------
When finish building of DU will try SlimLP
---------- Post added at 11:36 AM ---------- Previous post was at 11:34 AM ----------
Size of compiled CM12 is about 240 MB -> something is missing in your build...
---------- Post added at 11:44 AM ---------- Previous post was at 11:36 AM ----------
look here:
https://github.com/TheMuppets/proprietary_vendor_lge/blob/cm-12.0/d802/d802-vendor-blobs.mk
See how much blobs is there...
insteed of using your blobs try TheMuppets's blobs:
https://github.com/TheMuppets/proprietary_vendor_lge
add this to roomservice.xml
---------- Post added at 11:50 AM ---------- Previous post was at 11:44 AM ----------
My last proposition is to try using cm device tree and kernel...
Then make some changes in device/lge/d802 .
Click to expand...
Click to collapse
Great Info! Thanks for chiming in.

Syncing repo of SlimLP

Ok, keep me up to date

Flo0008 said:
Ok, keep me up to date
Click to expand...
Click to collapse
Have no good news...
After build zip is 190 MB... :/
Give it up today. Tomorrow will check what is wrong.

@RenderBroken
I built AOSP LP again today, build size seems ok with around 200Mb but when I tried to flash the rom I gout stuck in TWRP. A kind of a flashloop (instead of bootloop) - anyway, the device didn't get bricked althought I shut down the phone after that. This means the .zip file didn't flash. Any ideas?
And where can I paste your mkbootimg_tools repo to build the boot.img with it?
And one more thing: In lollipop (Cyanogenmod 12) all the system files and so on get compressed into a .dat file, right? I have the problem, for me there isn't such a file in my .zip file ... Do you know what to do against this problem?
I hope I don't bother you too much ...

reaper61616 said:
Have no good news...
After build zip is 190 MB... :/
Give it up today. Tomorrow will check what is wrong.
Click to expand...
Click to collapse
But the size shouldn't be that problem ... Did the build boot up?

Related

CM10.1 based ROM #8 - [4.2.2] Broken: radio, batt indicator, GPS

Below you'll find a whole rom for p999 based on the jellybean sources from CM repo compiled earlier in the week, using the modified defconfig with minor tweaks from cyanogenmod_p990_defconfig and a bootloader patch from wkpark (http://forum.xda-developers.com/showpost.php?p=33993473&postcount=636) applied. One day I noticed this patch on one of my sdcards and decided to apply it to my build, that patch actually has pushed me to a point where there was a black screen with operational adb, all the builds before that were useless, then I rolled a whole cm10 around it.
The black screen was due to missing ICS vendor blobs, and after throwing in the vendor_blobs from p990, the whole thing just magically booted up with almost everything functional (sdcard issues were due to a typo, and wifi due to wifi module getting overwritten by prebuilt one), but the cell radio and the battery meter. There was no other code-voodoo needed to get anything going up to this point. Naberus's patches were for brightness inclusion (P999 was missing in the ifdefs), and storage fix and gpio (if I recall correctly). The latest is being built from the plain CM10 kernel with addition of wkpark's patch. Yes, it is buttery smooth out of the box.
I'm trying to roll CM10.1 for the #7, so please be patient.
UPDATE: I got CM10.1 (4.2.2) built.
If anyone feels adventurous, and knows what to do with these things below, please let me know. If you'll see some obvious mistakes in any of the things below, don't be a stranger and post your findings in the thread
Oh, and one last thing, please "no (log)cat fights girls"!
Please use the user-thread for non-development related discussions (http://forum.xda-developers.com/showthread.php?t=2039501)
Github repos:
https://github.com/apolkosnik/lge-kernel-star
https://github.com/apolkosnik/device_p999
https://github.com/apolkosnik/android_device_lge_star-common
# 8
CM10.1 (4.2.2) - Just updated to 4.2.2, and tried some spi master/slave magic in the kernel. Based on CM10.1 sources.
cm-10.1-20130221-UNOFFICIAL-p999.zip - 154.37 MB
#7
CM10.1 (4.2.1) - some things are still broken. Based on CM10.1 sources,
cm-10.1-20121215-UNOFFICIAL-p999.zip - 150.80 MB
#6
Added some extra blobs from p999, and kineto. You can disable kineto manually if it starts crashing on you.
build.,prop adjusted to point to librilswitch.so. Some patches from Naberus merged, and also his MDM6600 changes.
cm-10-20121209-UNOFFICIAL-p999_v6.zip.md5sum - 69 bytes
cm-10-20121209-UNOFFICIAL-p999_v6.zip - 151.83 MB
#5:
fixed wifi, and sdcard, so that you can take pictures and stuff. Netflix works :laugh: Cell radio and battery indicator are still not working.
cm-10-20121209-UNOFFICIAL-p999.zip.md5sum - 69 bytes
cm-10-20121209-UNOFFICIAL-p999.zip - 149.05 MB
#4:
cm-10-20121208-UNOFFICIAL-p999.zip.md5sum - 69 bytes
cm-10-20121208-UNOFFICIAL-p999.zip - 149.05 MB
#3:
cyanogenmod_p999_defconfig - 82.61 KB
star_kernel.diff - 33.77 KB
cm-10-20121205-UNOFFICIAL-p999.zip.md5sum - 69 bytes
cm-10-20121205-UNOFFICIAL-p999.zip - 141.60 MB
logcat.txt.gz - 60.38 KB
dmesg.txt.gz - 17.81 KB
If you'd like t o roll your own, you can follow the directions outlined here:
http://forum.xda-developers.com/showthread.php?t=1971645
http://forum.xda-developers.com/showthread.php?t=2024590
Contents of my .repo/local_manifest.xml
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_lge_p990" path="device/lge/p990" remote="github" revision="jellybean" />
<project name="apolkosnik/android_device_lge_star-common" path="device/lge/star-common" remote="github" revision="jellybean" />
<project name="apolkosnik/lge-kernel-star" path="kernel/lge/star" remote="github" revision="jellybean" />
<project name="apolkosnik/device_p999" path="device/lge/p999" remote="github" revision="jellybean" />
<project name="TheMuppets/proprietary_vendor_lge.git" path="vendor/lge" remote="github" revision="jellybean" />
</manifest>
This would not happen without the CM kernel by RC and wkpark's patch, and the people who made comments in this thread.
delete
so if weebles wobble...why don't they fall down?
@OP So where is the download link and can u explain more about the tweaks you implemented. Also is it kernel 2.6.36.x or not?
Link?
Sent from my LG-P999 using xda premium
Sadly he removed his original post and did a bad copy paste into this thread. Once he gets back online he will provide the link.
links fixed
donezo.... kernel 2.6.39.4
Well then lets do this!!
adampk said:
Below you'll find a kernel for p999 based on the jellybean (cm10) lge-kernel-star repo compiled earlier today, using the star_p999_defconfig with minor tweaks. I've started tweaking the p999 as a target for the ROM build, but I don't have the time to do it today. If anyone feels adventurous, and knows what to do with these things below, please let me know.
kernel - 3.49 MB
wireless.ko - 2.43 MB
lge-kernel-star.diff - 2.12 KB
config - 85.73 KB
Click to expand...
Click to collapse
Can anyone create an img file out of this?
Sent from my LG-P999 using Tapatalk 2
Rafase282 said:
Well then lets do this!!
Click to expand...
Click to collapse
Agreed! Nice Adam!!!!!!
Sent from my LG-P999 using xda premium
Rafase282 said:
Well then lets do this!!
Click to expand...
Click to collapse
Rafase what do u think? Since Tony has ported the su660 stock to p990. Is it possible if we work on that port to move that to p999? I have seen many people porting g2x roms for p990 ... devs like Tony and kashamalaga has worked on both devices simultaneously. Also if someone has missed it earlier there is another test stock ics kernel for p999 posted in p990 thread... by one of the Dev around the time when the first p990 stock ics kernel was released from the source.... I think we should gather as much resources we have....
One last thing I should need to ask Adam. Did u extract it out of the cm10 p990? Or the original sources?
Sent from my LG-P999 using Tapatalk 2
n30wav3 said:
Rafase what do u think? Since Tony has ported the su660 stock to p990. Is it possible if we work on that port to move that to p999? I have seen many people porting g2x roms for p990 ... devs like Tony and kashamalaga has worked on both devices simultaneously. Also if someone has missed it earlier there is another test stock ics kernel for p999 posted in p990 thread... by one of the Dev around the time when the first p990 stock ics kernel was released from the source.... I think we should gather as much resources we have....
One last thing I should need to ask Adam. Did u extract it out of the cm10 p990? Or the original sources?
Sent from my LG-P999 using Tapatalk 2
Click to expand...
Click to collapse
I'm currently porting. I have one test zip and working on two more in different ways to see which one works. First time porting from p990 to p999 so im not sure what to do so I'm trying three different ideas so see which one works.
Edit: I hope I still manage to finish my professional essays for the week.
---------- Post added at 05:20 AM ---------- Previous post was at 05:14 AM ----------
http://rootzwiki.com/topic/13194-dev-how-to-port-o2x-miui-to-g2x-instructions/ I'm missing the zip for step 5. Does anyone has it?
Hopefully you get it working !!!!!!!
g2x mokee os
kepapas said:
Hopefully you get it working !!!!!!!
g2x mokee os
Click to expand...
Click to collapse
Well I'm doing this assuming that the kernel file is actually a boot.img so if that is wrong and it needs to be compiled converted then so fart the first 3 build I have will fail. Currently waiting to see if it boots.
n30wav3 said:
One last thing I should need to ask Adam. Did u extract it out of the cm10 p990? Or the original sources?
Click to expand...
Click to collapse
https://github.com/CyanogenMod/lge-kernel-star/blob/jellybean/arch/arm/configs/star_p999_defconfig
You could do it!!! You could do it all night long lol jk
g2x mokee os
kernel = zImage
adampk said:
https://github.com/CyanogenMod/lge-kernel-star/blob/jellybean/arch/arm/configs/star_p999_defconfig
Click to expand...
Click to collapse
so the "kernel" file can be ranmed to boot.img or not? I dont have the pc configured to build from source so I would have to do it tomorrow or most likely after Friday when im done with work and college work.
Edit: nvm you answered while I was writing this.
Edit: erased
adampk said:
https://github.com/CyanogenMod/lge-kernel-star/blob/jellybean/arch/arm/configs/star_p999_defconfig
Click to expand...
Click to collapse
Wait a sec... isn't this the same defconfig from the sources? M missing a trick here ... I know all kernel comes from stock sources even cm ones but which rom should exactly work on this one? The stock or the cm10 .... as this defconfig seems the same as was in the stock kernel sources ...
Also rafase, dun push it ... clear out ur personal work first so u can concentrate... we need to understand it clearly then make a .move..... I have seen some kitchens here that can create boot.img from zlmage ... so that's also on the cards..... also m gonna be posting that kernel I mentioned above.... Adam do u think u can compare it?
Sent from my LG-P999 using Tapatalk 2
---------- Post added at 02:08 AM ---------- Previous post was at 02:05 AM ----------
Rafase282 said:
I'm currently porting. I have one test zip and working on two more in different ways to see which one works. First time porting from p990 to p999 so im not sure what to do so I'm trying three different ideas so see which one works.
Edit: I hope I still manage to finish my professional essays for the week.
---------- Post added at 05:20 AM ---------- Previous post was at 05:14 AM ----------
http://rootzwiki.com/topic/13194-dev-how-to-port-o2x-miui-to-g2x-instructions/ I'm missing the zip for step 5. Does anyone has it?
Click to expand...
Click to collapse
Hey step 5 is optional... its only for miui ... what it does basically is set the workspace layout... we can use that XML file from cm10 hackfest
Sent from my LG-P999 using Tapatalk 2

[Q] Looking for some building help

First off not sure if this is in the proper location, so if it is wrong, mods I apologize. Basically I am looking for a bit of help with building from several different sources to make my own custom version of a ROM. I want to (more or less) build Carbon from source with PA Prefs and possibly some additions from CM10 and AOKP. I can find plenty of info on how to build AOSP from source for a Nexus, but very little on cherry-picking commits and such from git. Here is what I have so far:
-Build Environment ready (Ubuntu 13.04)
-Complete JB 4.2.2 AOSP source
-Scott's Infuse device tree (I think)
-Carbon's Infuse source files
Let me say that I have NO intentions of releasing this as a download, I only want it for my personal use. The main things i need help with is making sure i have the proper and complete device tree, things I need to replace, and how to cherry-pick and add the PA and other commits. I'm new to building (this will be my first actual attempt), but I'm a quick study and follow directions well. Any and all help is GREATLY appreciated. Once I learn this, I may be able to build up a new ROM for everyone to try out
check out scott's beanstalk thread...post #3..i think
qkster said:
check out scott's beanstalk thread...post #3..i think
Click to expand...
Click to collapse
thanks, there was some very helpful information there. turns out i didnt have all the device files lol. now to find out how to merge code and try to build this thing.
InsaneDDay69 said:
thanks, there was some very helpful information there. turns out i didnt have all the device files lol. now to find out how to merge code and try to build this thing.
Click to expand...
Click to collapse
If you ever have any questions or errors you can't seem to get past shoot me a pm. I was in your shoes once and know how confusing everything can be at first. :thumbup:
Sent from my SGH-I997 using xda premium
FauxAffliction said:
If you ever have any questions or errors you can't seem to get past shoot me a pm. I was in your shoes once and know how confusing everything can be at first. :thumbup:
Sent from my SGH-I997 using xda premium
Click to expand...
Click to collapse
I'll keep that in mind. Think I'm finally figuring out how to pick, though I need to wait on my carbon source sync to try it.
Sent from my Carbon-ized Infuse
I want to see how this turns out.I'm still learning too man
Sent from my SGH-I997 using Tapatalk 2
this is what i'm getting. all the files are in the proper places, so i have no clue what i'm missing. carbon git sync bombed, so i'm trying a CM10 test run and then will work on adding tweaks and stuff. tried breakfast command and got the same result too.
[email protected]:~/cm10$ . build/envsetup.sh && brunch "infuse4g"
including device/generic/armv7-a-neon/vendorsetup.sh
including device/generic/armv7-a/vendorsetup.sh
including device/generic/mips/vendorsetup.sh
including device/generic/x86/vendorsetup.sh
including device/ti/panda/vendorsetup.sh
including vendor/cm/vendorsetup.sh
including sdk/bash_completion/adb.bash
including vendor/cm/vendorsetup.sh
build/core/config.mk:160: *** TARGET_ARCH not defined by board config: device/samsung/infuse4g/BoardConfig.mk. Stop.
Device infuse4g not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Repository for infuse4g not found in the CyanogenMod Github repository list. If this is in error, you may need to manually add it to your local_manifests/roomservice.xml.
build/core/config.mk:160: *** TARGET_ARCH not defined by board config: device/samsung/infuse4g/BoardConfig.mk. Stop.
** Don't have a product spec for: 'cm_infuse4g'
** Do you have the right repo manifest?
No such item in brunch menu. Try 'breakfast'
Click to expand...
Click to collapse
still getting the same error. it appears to think i have placed the files in the wrong location. i assumed the device files (not kernel or proprietary vendor files) went into the device directory of the source. i have mine placed like this
cm10 (source code folder name)-->
device-->
samsung-->
infuse4g
when i run the lunch command i get a list of different devices to build, but none are the infuse. i could build for the I9000 and port it over, but i don't want to do it that way. this was synced from scott's cm git, and i added the following in my manifest.xml to make sure i got it right.
<!-- Add infuse4g device tree -->
<project name="scotthartbti/android_device_samsung_infuse4g" path="device/samsung_infuse4g" remote="github" revision="jellybean" />
<!-- Add Samsung Kernel -->
<project name="scotthartbti/cm_samsung_kernel_dempsey" path="kernel/samsung_kernel_dempsey" remote="github" revision="jellybean" />
<!-- Add Samsung Proprietary Vendor Files -->
<project name="scotthartbti/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="jellybean" />
Click to expand...
Click to collapse
ANY help at this point would be great. i want to finally learn how to give back to the community that has made my android owning a true joy.
Anyone have any ideas?
My Infuse is Stalking Beans

[N9005][Beta][Unofficial] - CyanogenMod 11 - Test Build 2014-01-13

Update 2014-01-15
Well, the wait has an end! Official nightlies are out! That means I'm off the hook for building!
I'd like to thank everybody who participated by flashing, and posting in this thread. I really had a great time building CM11 for this device! Obviously, the CM team deserves the credit, they were the ones who gave us this awesome ROM!
Official CM11 nightlies can be downloaded here:
N9005
http://download.cyanogenmod.org/?device=hltexx
To flash the 2014-01-15 nightly on the N9005, you must first remove a device check for hltexx in the update script. You can do this by opening up the .zip, editing the updater-script located under /META-INF/com/google/android/, and removing the assert(...) line at the top.
Other Versions:
http://download.cyanogenmod.org/?device=hltetmo (t-mobile)
http://download.cyanogenmod.org/?device=hltespr (sprint)
http://download.cyanogenmod.org/?device=hltevzw (verizon)
Happy Flashing!!
Last Build: 2014-01-13:
The File:
http://d-h.st/J92
md5: a4bddcec13c97db0ec484f40efccc9d0
mirror: https://mega.co.nz/#!V9xzUBgZ!QGPoHBqWxKcDOuMGwpSVcTjZ2VsxsJw9EXO7tLOthWE
Disclaimer:
You flash at your own risk! I take no responsibility for your device!
Warning/Compatibility:
I have tested this on my N9005 only. I removed the assert line in the update script so it can be flashed directly w/o editing.
Changes:
Check review.cyanogenmod.org for more information.
2014-01-13:
- Anything merged by 6:30PM CET
2014-01-12:
- Anything merged by 5:00PM CET
- Battery drain issues seem to be resolved. Will give it a few days before taking it off the list.
2014-01-11:
- Anything merged by 8:30AM CET
2014-01-09:
- Anything merged by 7:00PM CET
2014-01-08:
- Anything merged by 6:30PM CET
2014-01-07:
- Anything merged by 6:30AM CET
2014-01-05:
- Stylus gestures now supported (via settings -> language & input)
- Stylus hovering icon can now be enabled (via settings -> language & input)
2014-01-03:
- http://review.cyanogenmod.org/#/c/56805/
- Updated the two others (56727 and 56730) which are not yet merged to latest patch sets.
- Touch screen issue is fixed (no more touches registered when screen is off).
- Hopefully battery drain is fixed too.
2014-01-02:
http://review.cyanogenmod.org/#/c/56727/
http://review.cyanogenmod.org/#/c/56728/
http://review.cyanogenmod.org/#/c/56730/
Confirmed Working:
- Sound
- Camera (picture & video)
- Calls/SMS
- Data 2g/3g/4g/wifi
- External SD
- GPS
- BT
- NFC
- USB OTG
- IR
- MHL
- ART
- Proximity sensor
- Light sensor
- Humidity sensor
- Thermometer
- Barometer
Known Issues:
- Touches are registered while in-call even when the screen is off
- Mic does not work in hands-free mode
- Battery drain (probably fixed)
- Compass not functioning in some apps
Installation:
1. Download .zip to external SD.
2. Flash via recovery. (I use chenglu cwm)
- In theory you can dirty flash these updates, I usually do the wipes though.
- Coming from TW you must wipe.
- If you're having issues others are not, wipe!
Gapps:
I personally use an aroma installer found here. You can select which ones you want to install. Alternatively you can find packages at cyanogenmod.org.
Enjoy!
Previous Versions:
2014-01-12: file md5: c2186c357f9c503bd8cfa941834bebfa
2014-01-11: file md5: 88395918a155ff80fe94b5c732bf950a
2014-01-09: file md5: e35b69fbcd5c2711a8595ea078152d5f
2014-01-08: file md5: adc7183daf010285e1f3b3623fe4a62b
2014-01-07: file md5: 45919a2e84e6d6afa69a820ea5449cd1
2014-01-05: file md5: ace79a7843e80f304ef5e23c71d7786f
2014-01-03: file md5: 6a2bbec972bc03623cf907c3aedbac21
2014-01-02: file md5: 9b1140bb1242e62ce78af2165d1c199e
2014-01-01: file md5: 346487b8e9f6e1fdc3b005a604f58c0e
2013-12-31: file md5: db9d51d087f032527371575958d5fad2
2013-12-29: file md5: 1e0c8e160703dabb2fb6b475af26ea55
2013-12-29: file md5: ce5cb1c86077ab1fb9074b7f278eb5c0
2013-12-28: file md5: 3511e57d57b91109329932365501f686
-----------------------------------------------------------------
Original post, 2013-12-31:
Update 2013-12-31:
Just uploaded a new build!
Noticeably, calling now works (both making/receiving)! No word on bt calling, that has yet to be confirmed.
So now it's time to list things that are *not* working rather than things that are working!
NFC --> Could anyone make a statement on that?
The File:
http://d-h.st/Qq4
md5: db9d51d087f032527371575958d5fad2
Enjoy it guys!
A big thank you to the CM team for working out all the major bugs within a few days really, and of course everyone who has contributed by commiting patches, testing, discussing, etc!
I'm not sure I'll do more builds today, as I have a few errands to run before the new years celebration! A celebration it will be indeed with CM on our notes!
-----------------------------------------------------------------
Original post, 2013-12-29 #2:
Update 2013-12-29 #2:
Just uploaded a new build! I have to go out for a few hrs, but wanted to share it quickly.
- External SD is now working
- Audio seems to be working better now (it's not near-muted this time.)
I haven't tested other things though.
The File:
http://d-h.st/ShX
md5: 1e0c8e160703dabb2fb6b475af26ea55
-----------------------------------------------------------------
Original post, 2013-12-29 #1:
Update 2013-12-29:
Just uploaded a new build! It's running better than the first one. Noticeably, the following things have changed:
- Camera works now (FC before)
- Gallery works (FC before)
- Data (3g/4g) works
- Audio works (speakers and headphones, but very quiet.)
- Calls are not working. You can call the phone, but it wont ring on the receiving side.
- External SD is not mounting. (This issue has been reported by the tmo guys already)
The File:
http://d-h.st/QaT
md5: ce5cb1c86077ab1fb9074b7f278eb5c0
Disclaimer:
You flash at your own risk! I take no responsibility for your device!
-----------------------------------------------------------------
Original post, 2013-12-28:
Good news!
I got it built, and it boots to launcher (confirmed on my n9005)! I'm only sharing this for the many flash happy out there waiting to see what cm11 feels like. The build is not a daily driver.
Sources
This is based on the official cm repos:
Code:
<manifest>
<project name="CyanogenMod/android_device_samsung_hltexx" path="device/samsung/hltexx" remote="github" />
<project name="CyanogenMod/android_device_samsung_qcom-common" path="device/samsung/qcom-common" remote="github" />
<project name="CyanogenMod/android_device_samsung_msm8960-common" path="device/samsung/msm8960-common" remote="github" />
<project name="CyanogenMod/android_device_samsung_hlte-common" path="device/samsung/hlte-common" remote="github" />
<project name="CyanogenMod/android_kernel_samsung_hlte" path="kernel/samsung/hlte" remote="github" />
<project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" remote="github" revision="cm-11.0" />
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="cm-11.0" />
</manifest>
Issues:
- Camera FC
- Gallery FC
- No Data / GSM
- Probably alot more
- Model no shows up as n9000 (I flashed on n9005)
Installation:
1. Download the zip
2. Wipe and flash via recovery, (I used chenglu cwm)
The first two boots took forever (10 minutes?) now it boots relatively quickly.
Disclaimer:
You flash at your own risk! I take no responsibility for your device!
The File:
http://d-h.st/JUs
md5: 3511e57d57b91109329932365501f686
The Future
I'm on leave for a couple of days, so if testers want to attach logcats ill take a look at what i can fix.
I guess I'll sync and build daily for the next couple of days, or until a more experienced developer comes along and builds CM11
Great work, It's nice to see I would test, however im having to use my phone as a connection point..so with no data connection it could mean im stuck until I get to another connection
Goodluck and look forward to seeing more from you
SM-N9000? You have the N9005 right?
Did you apply the patch noobnl posted on the tmo thread?
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
CalcProgrammer1 said:
SM-N9000? You have the N9005 right?
Did you apply the patch noobnl posted on the tmo thread?
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Click to expand...
Click to collapse
Yes, I have the N9005. I was breakfasting and brunching hltexx. Is hltexx not the 9005?
Did not see that patch, thanks for that! I'll apply it and rebuild tomorrow. Its 2AM now, I'm done for today.
PS: camera likes to hog CPU time on this build. Can kill it via terminal emu or delete the apk from system/app.
LTE working just spiffy here. I didn't need to patch or pull any files. Added muppets repo and it built smoothly.
sturmavik said:
LTE working just spiffy here. I didn't need to patch or pull any files. Added muppets repo and it built smoothly.
Click to expand...
Click to collapse
Very nice! You got the right model number too Can you post your roomservice.xml?
That patch you speak of has been merged:
http://review.cyanogenmod.org/#/c/56103/
How are camera and audio doing in your build? Were you brunching cm_hltexx-eng ? I'm gonna try that now
ponglenis said:
Very nice! You got the right model number too Can you post your roomservice.xml?
Click to expand...
Click to collapse
I just followed the instructions and copied the roomservice.xml from http://forum.xda-developers.com/showthread.php?t=2485033
ponglenis said:
How are camera and audio doing in your build? Were you brunching cm_hltexx-eng ? I'm gonna try that now
Click to expand...
Click to collapse
Yeah. Brunched cm_hltexx-eng. Had to patch updater_script as explained in the thread in order to flash my zip. Audio worked but was pretty quiet. Camera was borked in a big way. I actually nandroided back to TW because in my excitement I forgot to offload my gallery pictures and backup my sms.
But damn that was a wonderful few minutes of CM glory!
Does external sdcard work in your build? It doesn't detect properly on hltetmo and it looks like it's an issue with the hlte common repo that affects all variants.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
sturmavik said:
Yeah. Brunched cm_hltexx-eng. Had to patch updater_script as explained in the thread in order to flash my zip. Audio worked but was pretty quiet. Camera was borked in a big way. I actually nandroided back to TW because in my excitement I forgot to offload my gallery pictures and backup my sms.
Click to expand...
Click to collapse
Good, i have the same repos (except hltexx instead of hltetmo). I'm building atm, synced at around 09:15 CET. Let's see how it goes
sturmavik said:
But damn that was a wonderful few minutes of CM glory!
Click to expand...
Click to collapse
Oh yes, it's very snappy! Need to get a daily driver asap!
CalcProgrammer1 said:
Does external sdcard work in your build? It doesn't detect properly on hltetmo and it looks like it's an issue with the hlte common repo that affects all variants.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Click to expand...
Click to collapse
Can confirm its not working on yesterdays build. Will report back if anything is fixed in the new build!
Psss.
Nice to see any progress.
G00D JOB.
I cant wait for a stable release.
I need the DATA & GALLERY & CAMERA and all other working ..
But it's great news - I had a Xiaomi MI2A and NOTE I and i changed to NOTE III , cant wait for 4.4.2 or CM from any kind.
Managed to get it up and running on my n9005, although it thinks its a n9000. Camera and gallery seem to be working OK, still no external storage and unable to hang up from calls....
https://plus.google.com/105753056745777397846/posts/ihc4BcfKq4z
Sent from my SM-N9000 using XDA Premium 4 mobile app
choppiii said:
Managed to get it up and running on my n9005, although it thinks its a n9000. Camera and gallery seem to be working OK, still no external storage and unable to hang up from calls....
https://plus.google.com/105753056745777397846/posts/ihc4BcfKq4z
Sent from my SM-N9000 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Oh boy, thats more good news! At this pace we'll have a daily driver before 2014!
My build showed up as N9000 too. But my build.prop was a mess. I was brunching hltexx. Now trying cm_hltexx-eng. I'ts almost done.
Anything special you did while building? I'm guessing you're using the same repos as posted here, or?
ponglenis said:
Oh boy, thats more good news! At this pace we'll have a daily driver before 2014!
My build showed up as N9000 too. But my build.prop was a mess. I was brunching hltexx. Now trying cm_hltexx-eng. I'ts almost done.
Anything special you did while building? I'm guessing you're using the same repos as posted here, or?
Click to expand...
Click to collapse
Yeah I brunched hltexx to then couldn't get it to flash so I had to change the update script from hltexx to htle in the .zip
Sent from my SM-N9000 using XDA Premium 4 mobile app
---------- Post added at 08:06 PM ---------- Previous post was at 07:59 PM ----------
Issues aside how nice does it feel to have CyanogenMod running on our phones.... Its going to kill me going back to crap wiz tomorrow when I have to go to work... ?
Sent from my SM-N9000 using XDA Premium 4 mobile app
Well the build from this morning is no good. Stuck on Samsung logo on boot.
Going to clean, sync and try again!
Just finished another build but couldn't get it to flash, I get a status 7 error, this package is for "htlexx" device; this is a "htle" which is the same as before so without changing the update script which I'm not going to do now as I have to be up for work 5 hours it won't flash....
And yes I'm using the same repos posted here to answer your question from earlier...
My first build sat on the Samsung logo for what felt like few minutes before it booted so give it time if it happens again.
Sent from my GT-N7100 using XDA Premium 4 mobile app
ponglenis said:
Good news!
I got it built, and it boots to launcher (confirmed on my n9005)! I'm only sharing this for the many flash happy out there waiting to see what cm11 feels like. The build is not a daily driver.
Sources
This is based on the official cm repos:
Code:
<manifest>
<project name="CyanogenMod/android_device_samsung_hltexx" path="device/samsung/hltexx" remote="github" />
<project name="CyanogenMod/android_device_samsung_qcom-common" path="device/samsung/qcom-common" remote="github" />
<project name="CyanogenMod/android_device_samsung_msm8960-common" path="device/samsung/msm8960-common" remote="github" />
<project name="CyanogenMod/android_device_samsung_hlte-common" path="device/samsung/hlte-common" remote="github" />
<project name="CyanogenMod/android_kernel_samsung_hlte" path="kernel/samsung/hlte" remote="github" />
<project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" remote="github" revision="cm-11.0" />
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="cm-11.0" />
</manifest>
Issues:
- Camera FC
- Gallery FC
- No Data / GSM
- Probably alot more
- Model no shows up as n9000 (I flashed on n9005)
Installation:
1. Download the zip
2. Wipe and flash via recovery, (I used chenglu cwm)
The first two boots took forever (10 minutes?) now it boots relatively quickly.
Disclaimer:
You flash at your own risk! I take no responsibility for your device!
The File:
http://d-h.st/JUs
md5: 3511e57d57b91109329932365501f686
The Future
I'm on leave for a couple of days, so if testers want to attach logcats ill take a look at what i can fix.
I guess I'll sync and build daily for the next couple of days, or until a more experienced developer comes along and builds CM11
Click to expand...
Click to collapse
I think you have either patched something wrong or used some wrong source, because if you have a look in carrier settings, it gives CDMA options in the settings.
wilfredlams said:
I think you have either patched something wrong or used some wrong source, because if you have a look in carrier settings, it gives CDMA options in the settings.
Click to expand...
Click to collapse
Something was borked. Did not patch anything myself, not sure what it was. Uploading a new build now, it's running better. Camera, data (3G/4G) and sound (can't testify on in call sound yet) are working now, but its experiencing a similar issue others have reported regarding hanging up a call.
ponglenis said:
Something was borked. Did not patch anything myself, not sure what it was. Uploading a new build now, it's running better. Camera, data (3G/4G) and sound (can't testify on in call sound yet) are working now, but its experiencing a similar issue others have reported regarding hanging up a call.
Click to expand...
Click to collapse
That's cool, I will test it again when you provide the link.
wilfredlams said:
That's cool, I will test it again when you provide the link.
Click to expand...
Click to collapse
Thanks! Thats perfect! Feel free to attach logcats of bugs in action. A link to the new build can be found in the first post now! I'll be updating that when i upload new builds.
I saw a few more merges on http://review.cyanogenmod.org/ for our device, I'm starting a new build now! Hoping for sd card fixes

[SOURCE] Cyanogenmod Source Highly Compressed

Content moved. Go here: http://forum.xda-developers.com/showthread.php?t=3231109
Thank you
thank you for sharing this
md5= 550a231310527ce322f6c0e3c0c0596c
thanks for this post, urm can you do jelly bean 4.2.2 for me :good:
are you sure this is full source? because i think full source comes around 15 or 20 gb. This is merely 3.2 gb.
falconnoob said:
are you sure this is full source? because i think full source comes around 15 or 20 gb. This is merely 3.2 gb.
Click to expand...
Click to collapse
Yaa bro... this is the full cm12 source... Highly compressed... I have my friends who have been using this... I myself am using this bro! If u extract the file... U get around 15GB...
kirito9 said:
thanks for this post, urm can you do jelly bean 4.2.2 for me :good:
Click to expand...
Click to collapse
4.2.2? Yaa sure... I had my friend uploaded it before... Here you go:
http://www.androidfilehost.com/?fid=23060877490004404
Link updated @kirito9 bro! Please copy-paste in browser...
This is the cm10.1 source.. (Android 4.2.2)
Born to be a coder said:
thank you for sharing this
Click to expand...
Click to collapse
Anytime Aman!
Please Dont Post on the Q/A thread.. I wont look at it... Post here and press the thanks button!
Awsome
You are really awsome can u do a favour to me
can you provide me the llvm and stlport folder compressed of cm11 source present in cm11/external/....
Please
Thanks again @regalstreak :laugh:
---------- Post added at 10:52 AM ---------- Previous post was at 10:48 AM ----------
4.2.2? Yaa sure... I had my friend uploaded it before... Here you go:
Download
This is the cm10.1 source.. (Android 4.2.2)
WORKING NOW THANKS :good: :laugh:
regalstreak said:
Yaa bro... this is the full cm12 source... Highly compressed... I have my friends who have been using this... I myself am using this bro! If u extract the file... U get around 15GB...
Click to expand...
Click to collapse
can you upload the compressed .repo folder too so that we can update it?i mean repo synced later on? and also is it cm12.1 or cm12?
falconnoob said:
can you upload the compressed .repo folder too so that we can update it?i mean repo synced later on? and also is it cm12.1 or cm12?
Click to expand...
Click to collapse
It is cm12... Not 12.1 as it is still in development stages and unstable. Of the .repo folder... Ill see... Ill compress it and see.. If size is less than 5gb.. Ill upload it... Ill update u guys on this till thursday..
P.S. Im happy dad bought me a new laptop! Lenovo z50-70.. The i7 model...
Help
Brother i need serious help im trying to get my proprietary files via .sh and it says cannot create directory permission denied and says adbd cannot run tried adbd insecure (it disables usb debugging in my case)
HOW TO FIX
the ss of error is attached plz help
sandeep.sethi said:
Brother i need serious help im trying to get my proprietary files via .sh and it says cannot create directory permission denied and says adbd cannot run tried adbd insecure (it disables usb debugging in my case)
HOW TO FIX
the ss of error is attached plz help
Click to expand...
Click to collapse
try
Code:
cd (your directory before the cm12 source)
chmod -R 777 cm12
chmod -R a+x cm12
No success
regalstreak said:
try
Code:
cd (your directory before the cm12 source)
chmod -R 777 cm12
chmod -R a+x cm12
Click to expand...
Click to collapse
It is showing same error.
Actually you can update to cm12.1 using a cm12 repo. Repo is basically a collection of git object, uploading this would serve no purpose, .repo folder is needed.
Sent from my Moto G using XDA Free mobile app
i have fixed propreitory files but now it shows this error
http://pastebin.com/Ux2Fia5h
got error.. need assistance.
regalstreak said:
Hey Guys! I have found many people like me with low bandwidth are not able to sync the cyanogenmod source. So here I present to you. Cyanogenmod 12 Source (Android 5.0.2) as of 29/03/2015! The original source size including the .repo folder is 29 GB. In the .repo folder, there are temporary files. So I have not included the .repo folder as you dont need it to compile. The size of source without .repo folder is 14 GB. And it is highly compressed to only 3.2 GB! This has purely done by me. So. Here you go:
You Cannot Update the sources as they do not have the .repo folder!
Cyanogenmod 12
DOWNLOAD
FAQ
Q1> Is this really Cyanogenmod 12 source?
Ans: Yeah! I have compressed it! and it is real Cyanogenmod 12 source.
Q2> How To Extract Source?
Ans:
Open Terminal
Download 7zip if not done before (sudo apt-get install p7z-full)
Now cd to the drive where you have downloaded the sources
7z x *.7z
Now you have extracted the source
Q3> Will you upload the .repo folder?
Ans:Sorry Guys. I cannot. The highly compressed size ofthe .repo folder is 10GB which makes it worthless to upload as you would not download because of low bandwidth. I also cant upload because of low bandwidth. More over, you cannot update to cm12.1 with the repo folder. You can just update the minor changes committed by the cyanogenmod maintainers. So, In short, Im not uploading. Sorry forthe inconvenience.
You cannot extract source with GUI on the Archive Extractor. So, Try the method I mentioned
Q3> The size is 2 GB or 3.2 GB? I saw the size 2 GB on Androidfilehost!
Ans: The size is 3.2 GB. I had kept the laptop whole night for uploading. So maybe it did not show the correct size there!
Please press the "Thanks Button" if I helped you and quote me if you have a problem!
Click to expand...
Click to collapse
got this error when ran make -j4 otatools.
Checking build tools versions...
************************************************************
You are attempting to build with the incorrect version
of java.
Your version is: Picked up JAVA_TOOL_OPTIONS: -javaagent:/usr/share/java/jayatanaag.jar java version "1.7.0_79" OpenJDK Runtime Environment (IcedTea 2.5.6) (7u79-2.5.6-0ubuntu1.15.04.1) OpenJDK 64-Bit Server VM (build 24.79-b02, mixed mode).
The required version is: "1.7.x"
Please follow the machine setup instructions at
https://source.android.com/source/initializing.html
************************************************************
build/core/main.mk:171: *** stop. Stop.
need help...
thanks..
I was trying to build for s duos 2
butt this error came after 3 hours
almamun512 said:
I was trying to build for s duos 2
butt this error came after 3 hours
Click to expand...
Click to collapse
Please reattach the picture.
jackey31 said:
got this error when ran make -j4 otatools.
Checking build tools versions...
************************************************************
You are attempting to build with the incorrect version
of java.
Your version is: Picked up JAVA_TOOL_OPTIONS: -javaagent:/usr/share/java/jayatanaag.jar java version "1.7.0_79" OpenJDK Runtime Environment (IcedTea 2.5.6) (7u79-2.5.6-0ubuntu1.15.04.1) OpenJDK 64-Bit Server VM (build 24.79-b02, mixed mode).
The required version is: "1.7.x"
Please follow the machine setup instructions at
https://source.android.com/source/initializing.html
************************************************************
build/core/main.mk:171: *** stop. Stop.
Install the correct java version bro...
need help...
thanks..
Click to expand...
Click to collapse
regalstreak said:
Please reattach the picture.
Click to expand...
Click to collapse
These are the screenshots ........................
bro can u upload cm11 sources ?? i have it but when i try to generate boot.img recovery files .. it alwasy gave me error of .. "unpackbootimg is not found"
i have tryd make -j4 otatools but still error occured ..
i will be very thankfull to you if u find me a fix for it else upload cm11 source as highly compressed as u did with cm12
almamun512 said:
These are the screenshots ........................
Click to expand...
Click to collapse
your build tree has problems... correct it... source is correct

[WIP]CyanogenMod 12.1 for Xiaomi Mi 4i

SOURCES
I've worked on this in the last 4-5 days... Unfortunately, i've no too much spare time, so I've published my sources, because I'm stucked on several areas...
I'm asking every Developer to collaborate.
This source is very experimental. I'm not responsible if you transform your phone into a brick!
kernel: https://github.com/dh-harald/android_kernel_xiaomi_ferrari
device: https://github.com/dh-harald/android_device_xiaomi_ferrari
optional:
vendor: https://github.com/dh-harald/android_vendor_xiaomi_ferrari
so your local_manifest must be something like this:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project path="kernel/xiaomi/ferrari" name="dh-harald/android_kernel_xiaomi_ferrari" />
<project path="device/xiaomi/ferrari" name="dh-harald/android_device_xiaomi_ferrari" />
<project path="vendor/xiaomi/ferrari" name="dh-harald/android_vendor_xiaomi_ferrari" />
<project path="device/qcom/common" name="CyanogenMod/android_device_qcom_common" />
<project path="external/mm-dash" name="CyanogenMod/android_external_mm-dash" />
<project path="hardware/qcom/fm" name="CyanogenMod/android_hardware_qcom_fm" />
</manifest>
Quick compile guide:
Code:
cd <your source>
. build/envsetup.sh
brunch cm_ferrari-userdebug
This topic is strictly for developers, so it will be enough for help
IMPORTANT
The binary base of my rom is 5.6.11.
If you have unexcepted behaviours, try to install developer edition 5.6.11, before you install CM
Latest alpha builds:
From: @dh.harald
cm-12.1-20151015-UNOFFICIAL-ferrari.zip - 348.13 MB
Sensor patch:
patch-sensors.zip - 204.43 KB (only libsensorservice.so needs)
I'm currently testing this build as a daily driver
From: @smoki3
Sensors patch already applied:
cm-12.1-20150722-UNOFFICIAL-ferrari.zip
WORKING
2D acceleration
Touchscreen
HW/SW buttons
RIL/multisim
+ mobile data (big thanks for @smoki3 & @k2wl)
Wifi
Bluetooth
internal SD
MTP
vibrate
gps
camera ( @smoki3)
audio (with proprietary drivers)
fm radio @k2wl
notification lights (see limitations: http://forum.xda-developers.com/showpost.php?p=61954224&postcount=434)
ant +
+ you tell me
NOT WORKING
sensors (use this patch: http://d-h.st/S5m)
+ everything else...
CHANGELOG
+ doze (limited)
If you want buy us a beer, here are the donation links:
dh.harald
smoki3
k2wl
can you add a list of working/non working parts?
have you tried
AUDIO_FEATURE_LOW_LATENCY_PRIMARY := true
on boardconfig?
smoki3 said:
have you tried
AUDIO_FEATURE_LOW_LATENCY_PRIMARY := true
on boardconfig?
Click to expand...
Click to collapse
Nope
Please fork it, and if your modification is working, make a pull request
Maybe I'll try it in the evening... we will see
Thanks!
Wow.. You are the man.
Thank you so much
Sent from my Mi 4i using XDA Free mobile app
dh.harald said:
Nope
Please fork it, and if your modification is working, make a pull request
Maybe I'll try it in the evening... we will see
Thanks!
Click to expand...
Click to collapse
have forked already. building now
dh.harald said:
Nope
Please fork it, and if your modification is working, make a pull request
Maybe I'll try it in the evening... we will see
Thanks!
Click to expand...
Click to collapse
can you do the following:
1. install this app: https://play.google.com/store/apps/details?id=com.tortel.syslog&hl=de
2. reboot
3. start and stop camera app
3. run the app from 1. and upload the generated zip file here
vibration is working for me on your build. it only is weak
Thank you very much for your work dh.harald! Give this man some beer for his work
You didn't define msm8916 audio files in your device.mk like inhttps://github.com/CyanogenMod/android_device_cyanogen_msm8939-common/blob/cm-12.1/msm8939.mk
k2wl said:
You didn't define msm8916 audio files in your device.mk like inhttps://github.com/CyanogenMod/android_device_cyanogen_msm8939-common/blob/cm-12.1/msm8939.mk
Click to expand...
Click to collapse
You mean, like here?
https://github.com/dh-harald/android_device_xiaomi_ferrari/blob/cm-12.1/full_ferrari.mk#L52
Bitti09 said:
can you do the following:
1. install this app: https://play.google.com/store/apps/details?id=com.tortel.syslog&hl=de
2. reboot
3. start and stop camera app
3. run the app from 1. and upload the generated zip file here
Click to expand...
Click to collapse
camera is not built in until now
smoki3 said:
camera is not built in until now
Click to expand...
Click to collapse
can you upload a zip of the logfiles directly after booting the mi4i ?
dh.harald said:
You mean, like here?
https://github.com/dh-harald/android_device_xiaomi_ferrari/blob/cm-12.1/full_ferrari.mk#L52
Click to expand...
Click to collapse
yes those...but why you put them in full.mk insetad of device.mk
are those building during compilation...check that too..
you must be missing something in your blobs...
and if those are building fine then just put
/system/vendor/lib/hw/sound_trigger.primary.msm8916.so
/system/vendor/lib/libhwdaphal.so
/system/vendor/lib64/libhwdaphal.so
in your vendor tree.
these are vendor files and are not open source files...like
https://github.com/AICP/device_htc_...c21f098ea9e883e156/proprietary-files.txt#L182
https://github.com/AICP/device_htc_...c21f098ea9e883e156/proprietary-files.txt#L400
https://github.com/AICP/device_htc_...c21f098ea9e883e156/proprietary-files.txt#L715
build everything else as open source like audio.primary.msm8916
Bitti09 said:
can you upload a zip of the logfiles directly after booting the mi4i ?
Click to expand...
Click to collapse
Here
dh.harald said:
Here
Click to expand...
Click to collapse
add DATA is not working.
No mobile data and no LTE option
smoki3 said:
add DATA is not working.
No mobile data and no LTE option
Click to expand...
Click to collapse
Thanks... I try to check it, but my mobile provider is not too healthy nowadays... (and I have no LTE subscription)
That's pretty sure, that the following proprietary files are missing for mobile data:
bin/netmgrd
lib/libcnefeatureconfig.so
lib64/libcnefeatureconfig.so
dh.harald said:
Thanks... I try to check it, but my mobile provider is not too healthy nowadays... (and I have no LTE subscription)
Click to expand...
Click to collapse
there is no lte option in settings until now. only 2g 3g there. but not working
---------- Post added at 08:18 PM ---------- Previous post was at 07:58 PM ----------
dh.harald said:
Thanks... I try to check it, but my mobile provider is not too healthy nowadays... (and I have no LTE subscription)
That's pretty sure, that the following proprietary files are missing for mobile data:
bin/netmgrd
lib/libcnefeatureconfig.so
lib64/libcnefeatureconfig.so
Click to expand...
Click to collapse
Have you tried to add them? does it work?
smoki3 said:
there is no lte option in settings until now. only 2g 3g there. but not working
---------- Post added at 08:18 PM ---------- Previous post was at 07:58 PM ----------
Have you tried to add them? does it work?
Click to expand...
Click to collapse
Not for me Maybe it's Vectone, but unfortunately, maybe something more is missing

Categories

Resources