Database Info

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

[ROM][4.3][CM 10.2][31/07/13] elicik's Unofficial CM 10.2 builds

Hey, I realized that there aren't many CM 10.2 ROMs out there yet, so I made one of my own. This is my first published ROM, so expect a buggy, unsupported experience. I am using fat-tire's repos for the time being. For now, I recommend the GAPPS posted here. I will attempt to post a new build everyday, but no promises.
I don't do support, but I will try to answer questions, and I would appreciate bug reports. Note that CM 10.2 is very much in development right now.
Download/ Changelog
07/31/13 (mirror) - Just a new sync, there should be no real changes.
07/30/13 (mirror) - Initial build, uses fat-tire's repos for device and kernel
For detailed changes see the gerrit page.
Bugs
Focal doesn't work
Two Clock apps, one from Google, one from Android.

Sweet. Been waiting for this. Thanks

the only reason that there are two clocks is because there is one in the cm10.2 zip and the 4.3 gapps.

Can I get a mirror, please? The download always fails at 144MB for me.

Why not use CMs repo? Just edit the manifests default.xml to include the cm10.2 tag, and enter the proper lines to grab the device and vendor file(s) for Grouper?

MBQ_ said:
Why not use CMs repo? Just edit the manifests default.xml to include the cm10.2 tag, and enter the proper lines to grab the device and vendor file(s) for Grouper?
Click to expand...
Click to collapse
I would, but grouper's device and kernel don't as of yet have 10.2 branches. I use fattire's because I believe they are the best I can do until we have official.
fattire said:
* The /device tree is basically 10.1's device plus a bunch of cherry-picked stuff from AOSP 4.3, plus newer SELinux rules, plus my own minor changes.
* The /kernel tree is currently AOSP 4.3 stock with a cyanogenmod_android_defconfig added. None of the customization from 10.1 are here yet.
Click to expand...
Click to collapse

sgt. meow said:
Can I get a mirror, please? The download always fails at 144MB for me.
Click to expand...
Click to collapse
Done

[Build Guide][Flo/Deb] - Pure AOSP 6.0.0_r1

This is a PURE AOSP ROM build guide. I have opted not to post an actual AOSP ROM based on 6.0.0 due to the fact I just dont care for it much. The instructions are up to date as of 10/21/2015
Deprecated-> This thread is about learning to build your own ROM following the instructions in post #2. The ROM posted in this thread is for example output. Feel free to download and use the ROMS @GROGG88 and I build! Feel free to try and build your own. We will try to help!
Quick Change Log
10/21 - Updated guide to reflect Android version 6.0.0_r1. No ROM for download (at this time).
1/17 - Updated build with official 5.0.2 Binaries. Fixed Browser "Settings" crash.
12/19 - Updated my Flo builds to Android 5.0.2_r1
12/9 - Updated my Flo build. Will not be doing a Deb Build any more.
12/2 @GROGG88 has updated his builds. I have not! I will update tomorrow. I did however get thefactory stock rooted ROM up HERE!
11/18 - @GROGG88 and I have joined forces to create two ROMS! I will be creating PURE AOSP ROMS and he will be creating Modified ROMS with many useful features! Each ROM can als be user built because all commits are shared in post #2!!!
11/15 - B8 - Updated the 5.0.0_r6. Deb is only using preview binaries due to lack of final binary files.
11/14 - B7 - Updated the 5.0.0_r5. Deb is only using preview binaries due to lack of final binary files.
11/10 - B6 - File system install instead of block install, Added Google Location Services to framework, Fixed a root issue that couple DEB users were having
11/9 - B5 - Changed wallpaper again. Fixed stock recovery at source level (Thanks to @Gnome and @GROGG88)
11/8 - B4 - Changed wallpaper to android 5 Wallpaper, fixed reverting to stock recovery (No need for save-recovery.zip), pre-rooted boot.img (No need for extra boot.img!)
11/7 - B3 - Removed it. Bad files. Reverted back to Build 2.
11/5 - B2 -- Fixed MTP bug that google has left in every version of AOSP, made ROM recovery flashable and added 2 zips to the OP
11/4 - B1 - Update to 5.0.0_r2. PC install via fastboot
Additional Downloads
Root by @Chainfire HERE!
Gapps for Lollipop HERE! There may be others so shop around!
Stericson's Busybox in flashable zip format is attached! Thanks to @Stericson for the binaries!
@GROGG88's Special Builds are HERE!
MOD EDIT: Link removed as domain has expired. Thread closed until new links can be installed
Please hit Thanks! It just as easy as hitting Download! ​
Click to expand...
Click to collapse
Click to expand...
Click to collapse

Ubuntu 14.04 Set up and Build Guide
Updated 11/05/2014
Feel free to ask any questions about the build process. Do not ask questions about Ubuntu!
This guide assumes the following
Have Ubuntu 14.04 setup, fully operation, and up to date. Hard Machine or Virtual, makes no difference. Must meet the minimum specs for compiling. Info from Google HERE
Understand terminal command line entry as this is all command line processors.
You are not here to ask for help with Linux, only the Android build process!
Add Java
Code:
sudo apt-get install openjdk-7-jdk
Add Build tools (Adds the required packages at the time of this posting)
Code:
sudo apt-get install git gnupg flex bison gperf build-essential \
zip curl libc6-dev libncurses5-dev:i386 x11proto-core-dev \
libx11-dev:i386 libreadline6-dev:i386 libgl1-mesa-glx:i386 \
libgl1-mesa-dev g++-multilib mingw32 tofrodos \
python-markdown libxml2-utils xsltproc zlib1g-dev:i386
Add Repo command (Syncs Google Repository with your local machine)
Code:
mkdir ~/bin && curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo && chmod a+x ~/bin/repo
Add bin folder to path for repo command (After you do this close Terminal and re-open to institute changes (easy way))
Code:
sudo gedit .bashrc
export PATH=~/bin:$PATH <-(add to end of bashrc)
Identify Yourself to the Repo (One day you may make commits so think about that when choosing your info!)
Code:
git config --global user.email "[email protected]"
git config --global user.name "yourpreferredusername"
Synch Repo (Download source... Sit back and grab a pop and a sandwich...)
Code:
mkdir ~/AOSP
cd ~/AOSP
repo init -u https://android.googlesource.com/platform/manifest -b android-6.0.0_r1
repo sync
Note: I use AOSP as my directory name. You can use what you want. You could use "aosp" or "Source" or "android" or "whateveryoulike"
Install proprietary binaries (Needed for things like GPS and Bluetooth, they are not Open Source like android) (Install proprietary binaries from here in the root of AOSP folder (or whatever you called yours))
Code:
[url]https://developers.google.com/android/nexus/drivers[/url]
Run envsetup.sh
Code:
source build/envsetup.sh
Choose Device
Code:
lunch
Build it!
Code:
make -j8 otapackage
See Build Notes and ramblings from me in post #3!

Notes
The ROM build will be a PURE AOSP ROM with no Gapps at all. See links in post #1 to PA Gapps for a good set of Google Apps!
The ROM will also have terminal level SU. So becareful! In other words its fully rooted and could be open to vulnerabilities. Flash your favorite Superuser Package if you need it. I dont. I recommend SuperSU by @Chainfire HERE. Download the flashable zip and flash after you flash ROM.
make -j8 is the number of worker threads that the make command will use to build. To me 8 is a safe number for an i7 processors. For an i5 Processor I would use -j4. I have experimented with a multitude of different values and it seems to me that the number of logical cores is also the best number to use with the make command.
Google recommends between -j24 and -j32 (to me that is excessive and causes my machine to error out every once in a while). Keep in mind the higher you push the more load the CPU will undertake. If your O/C'ing real hard you better have some nice cooling! I had to cut back OC on my 4770k from 4.65 to 4.4 with a Corsair H60 cooler just so it wouldn't over heat. When in doubt start low.
My i7 machine clocked at 4.4 and 16 gigs of RAM on a Samsung 840 Pro 256 Gig SSD take about 38 minutes to build the entire ROM.
With a 50 Meg download link it took maybe 30 to 45 minutes to sync the repo.
Changes from Source
Check out @GROGG88 patches HERE!
Click to expand...
Click to collapse
Click to expand...
Click to collapse

Mindrocket said:
Right on Scott! Can't wait to give it a spin.
---------- Post added at 07:37 PM ---------- Previous post was at 07:15 PM ----------
Security settings crashes says"unfortunately settings has stopped" .
Click to expand...
Click to collapse
I think its the same error some other folks are facing. Rascarlo and a few others would release their AOSP builds but it appears this blocks them from releasing. Read this over on a few pages on a few ROMs in this neighborhood.

whoamanwtf said:
I have faith in you making it work
Click to expand...
Click to collapse
Can anyone post a snippet of logcat during the crash? Particular the actually error itself.
Place it in the
Code:
box if you can.
If not I get out of work in a few hours and can look then...

mjwhirly said:
Nice to see you venturing into new projects. Most people start with CM since its not to hard to compile, but you did it the opposite way which will make all the difference in the end
Sent from my LG-D800 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
IMHO: If you dont start with the basics you will end in a mess

got to try this as your clean rom works well iam sure this one will be great also
keep up the great work to you and who helps you.
Where would i start to try baking my own cake .. i use archlinux what programs needed to do a build

rocksyjj said:
got to try this as your clean rom works well iam sure this one will be great also
keep up the great work to you and who helps you.
Where would i start to try baking my own cake .. i use archlinux what programs needed to do a build
Click to expand...
Click to collapse
Never used archlinux but I used Ubunutu 13.04
Here is where I started: http://forum.xda-developers.com/showthread.php?t=2224142
(I hate nano so used gedit of course. )
But at the last two shell commands i didint use the AOKP tree I used the AOSP base so you want to look here for that: http://source.android.com/source/downloading.html
Then follow the instructions from that page on forward until you have yourself a ROM :highfive:
Also pay attention to the blurb about proprietary binaries
Obtaining proprietary binaries
The Android Open-Source Project can't be used from pure source code only, and requires additional hardware-related proprietary libraries to run, specifically for hardware graphics acceleration.
Official binaries for the supported devices can be downloaded from Google's Nexus driver page, which add access to additional hardware capabilities with non-Open-Source code.
When building the master branch for a device, the binaries for the most recent numbered release or with the most recent date are the ones that should be used.
Click to expand...
Click to collapse
There is a link for the Nexus binaries in that blurb. Make sure you install them before building and you are good.

Alright then...
Build 20131008.010041 up!
Changes
Re-synced repo for 2013/10/08
Fixed Settings -> Security F/C
Changed SU to SuperSU
Also can I have some people rate the thread 5 stars... The Nexus 7 FHD troll is at it again. He is going around rating my threads, and others, 1 star.
Any help with that would be appreciated. Damn trolls, lol!

scrosler said:
Alright then...
Build 20131008.010041 up!
Changes
Re-synced repo for 2013/10/08
Fixed Settings -> Security F/C
Changed SU to SuperSU
Also can I have some people rate the thread 5 stars... The Nexus 7 FHD troll is at it again. He is going around rating my threads, and others, 1 star.
Any help with that would be appreciated. Damn trolls, lol!
Click to expand...
Click to collapse
You fixed the security settings fc! Mind sharing how you managed to fix that?
Sent from my Nexus 7 using Tapatalk 4

scrosler said:
Also pay attention to the blurb about proprietary binaries
There is a link for the Nexus binaries in that blurb. Make sure you install them before building and you are good.
Click to expand...
Click to collapse
Where is the link to download the Nexus binaries btw? I didn't see a proprietary binaries blurb in the above 2 links.
Thanks.

vibranze said:
Where is the link to download the Nexus binaries btw? I didn't see a proprietary binaries blurb in the above 2 links.
Thanks.
Click to expand...
Click to collapse
Its under the actual "Building for devices" page...
http://source.android.com/source/building-devices.html
Wich leads to...
https://developers.google.com/android/nexus/drivers

scrosler said:
Alright then...
Build 20131008.010041 up!
Changes
Re-synced repo for 2013/10/08
Fixed Settings -> Security F/C
Changed SU to SuperSU
Also can I have some people rate the thread 5 stars... The Nexus 7 FHD troll is at it again. He is going around rating my threads, and others, 1 star.
Any help with that would be appreciated. Damn trolls, lol!
Click to expand...
Click to collapse
Hi Scott. Where is the download link for this one? I think a few folks would love to know the fix for the security fc since last I read it was blocking their update as well. Definitely want to try the aosp one.
Sent from my Nexus 7 using XDA Premium 4 mobile app

scrosler said:
Its under the actual "Building for devices" page...
http://source.android.com/source/building-devices.html
Wich leads to...
https://developers.google.com/android/nexus/drivers
Click to expand...
Click to collapse
hi scott,
could you please share the sources you build from? and specifically how you fixed the Security settings FC?
thanks.

vibranze said:
Thanks Scotts, appreciated your fast response. :good:
Click to expand...
Click to collapse
Your welcome!
mpmilestogo said:
Hi Scott. Where is the download link for this one? I think a few folks would love to know the fix for the security fc since last I read it was blocking their update as well. Definitely want to try the aosp one.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Its in the OP. Post 1. I just changed the link. Happy downloading!

TheDarkDefender said:
hi scott,
could you please share the sources you build from? and specifically how you fixed the Security settings FC?
thanks.
Click to expand...
Click to collapse
The source is the AOSP tree and it can be found here: http://source.android.com/source/downloading.html (thats all I am using).
Fixing the Settings F/C was creative... had to Google to get the answer, lol
Here is what I found...
CM 10.2 initially had this issue as its based from AOSP like this rom (SOURCE). They did not explain a fix... Also, note this is a less than one week old issue. So I continued on with Google... (Google is a son of a ***** when you need it )
Then found this thread on XDA from the Nexus 4 about an update to 4.2.2 HERE! This started to make sense as they posted a fix for the N4. HOWEVER that fix was not applicable to our N7.2 because we did not have the keymaster files on the vendor partition!!!
So test flashed the Google stock ROM /system/vendor/firmware/keymaster/* files into this AOSP ROM. VIOLA! It worked and solved the problem.
Now I will admit I am not sure why these files are not in the AOSP source tree as I am still learning... If you can shed more light then please do! But I do know that it fixed the issue. Was not seemingly prevalent before October 2nd (or maybe it was but thats when it was reported on CM10.2) and moving those files into the ROM base resolved (granted they are not in the same spot as the N4).
Please feel free to share anything you know in this thread.

scrosler said:
Your welcome!
Its in the OP. Post 1. I just changed the link. Happy downloading!
Click to expand...
Click to collapse
Thanks Scott. I think I found something rather strange with my tablet with just about any of the AOSP builds. I found this on another as well. It seems whenever I enable locations in chrome or chrome beta the tablet soft resets immediately. If I turn off location reporting, nothing happens but I get no location updates. I decided to restore things using the factory images. For the umpteen thousandth time, thanks to the Android team for providing the safety net!
Gonna try again later today and see if this issue persists after resetting the device to the factory image and reflashing the AOSP build.

mpmilestogo said:
Thanks Scott. I think I found something rather strange with my tablet with just about any of the AOSP builds. I found this on another as well. It seems whenever I enable locations in chrome or chrome beta the tablet soft resets immediately. If I turn off location reporting, nothing happens but I get no location updates. I decided to restore things using the factory images. For the umpteen thousandth time, thanks to the Android team for providing the safety net!
Gonna try again later today and see if this issue persists after resetting the device to the factory image and reflashing the AOSP build.
Click to expand...
Click to collapse
No this very possible depending on the GAPPS used. I think this is more a GAPPS issue then a ROM issue. I cant say for sure but I might have time to look later.
If someone else knows then do tell.
However I dont much care for Chrome on mobile (love it on PC) so I use AOSP and it runs well. But have not tested location.
Im sure a fix can be found with enough effort.

scrosler said:
No this very possible depending on the GAPPS used. I think this is more a GAPPS issue then a ROM issue. I cant say for sure but I might have time to look later.
If someone else knows then do tell.
However I dont much care for Chrome on mobile (love it on PC) so I use AOSP and it runs well. But have not tested location.
Im sure a fix can be found with enough effort.
Click to expand...
Click to collapse
Interesting. I've tried the BANKS minimal GAPPS core and photosphere as well as the goo.im gapps in clean flashes of other aosp based ROMs but still had the same issue. Perhaps I'll try the PA gapps next since they seem to have everything in them. Gonna give the whole thing a try a bit later today as well. I'm lucky enough to have two Nexus 7 tablets so one has your latest CleanROM on it which I love! The other seems to have descended into flashing heaven or the other place .
Any help appreciate on the issue though. I'd love to run AOSP on the second tablet since one of them is destined for my daughter when she realizes she wants one.

scrosler said:
The source is the AOSP tree and it can be found here: http://source.android.com/source/downloading.html (thats all I am using).
Fixing the Settings F/C was creative... had to Google to get the answer, lol
Here is what I found...
CM 10.2 initially had this issue as its based from AOSP like this rom (SOURCE). They did not explain a fix... Also, note this is a less than one week old issue. So I continued on with Google... (Google is a son of a ***** when you need it )
Then found this thread on XDA from the Nexus 4 about an update to 4.2.2 HERE! This started to make sense as they posted a fix for the N4. HOWEVER that fix was not applicable to our N7.2 because we did not have the keymaster files on the vendor partition!!!
So test flashed the Google stock ROM /system/vendor/firmware/keymaster/* files into this AOSP ROM. VIOLA! It worked and solved the problem.
Now I will admit I am not sure why these files are not in the AOSP source tree as I am still learning... If you can shed more light then please do! But I do know that it fixed the issue. Was not seemingly prevalent before October 2nd (or maybe it was but thats when it was reported on CM10.2) and moving those files into the ROM base resolved (granted they are not in the same spot as the N4).
Please feel free to share anything you know in this thread.
Click to expand...
Click to collapse
Thank you very much. Did you figure out the commit in the CM repo that actually solved this issue?
Also, what do you mean by So test flashed the Google stock ROM /system/vendor/firmware/keymaster/* files into this AOSP ROM ? Could you elaborate please?
I'd be happy to share anything I get to know about this. Been researching about this too. Thanks.

[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