Database Develop

[Q] Device tree help

Hey all,
I'm trying to compile my own ROM of ParanoidAndroid from source following a guide on their official site. Anyway, I need to find device specific trees, can anyone please help me out?
The guy gave an example for his S3:
<!-- Add i9300 device tree -->
<project name="CyanogenMod/android_device_samsung_i9300" path="device/samsung/i9300" remote="github" revision="jellybean" />
<!-- Add Samsung Kernel SMDK4412 -->
<project name="CyanogenMod/android_kernel_samsung_smdk4412" path="kernel/samsung/smdk4412" remote="github" revision="jellybean" />
<!-- Add samsung hardware source tree -->
<project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" remote="github" revision="jellybean" />
<!-- Add Samsung Proprietary Vendor Files -->
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="jellybean" />
Click to expand...
Click to collapse
Thanks

miniura said:
Hey all,
I'm trying to compile my own ROM of ParanoidAndroid from source following a guide on their official site. Anyway, I need to find device specific trees, can anyone please help me out?
The guy gave an example for his S3:
Thanks
Click to expand...
Click to collapse
Wait,do u have galaxy s3 i9300(quad core,4.8 screen) or galaxy s1(single core,4 inch screen)?

ClockWorkMod 6.0.3.2 ADB flashable

Hi everyone. Not sure if this has been posted,but I wanted to just share with newest CMW 6.0.3.2 Touch version,the installation procedure is usual. Tested on my L7 P700 CM10
1) Connect phone to PC ins USB Debugging mode(You can enable it in developer tools)
2) Download this https://www.dropbox.com/s/89u7kui5u7jtqua/Flash+boot_cwm.rar and extract it to folder and I suggest locating folder for example in C:/new folder.
3)The launch flash_bootloader.bat and wait for phone to restart.
4)Then Flash_Recovery.bat,wait for it to restart and you're done.
CMW Flashable 6.0.3.2 Touch - http://www.sendspace.com/file/i3see9

For L7 or L5/L3??
Sent from my LG-P700 using xda premium

ubuntuh said:
For L7 or L5/L3??
Sent from my LG-P700 using xda premium
Click to expand...
Click to collapse
Tested on my L7 ,not sure about other devices.

Lukijs said:
2) Download this ... and extract it to folder and I suggest locating folder
Click to expand...
Click to collapse
The link doesn't work, could you upload it again ?

Dead link, refresh it.

Will it work on lg Optimus l7 710?

Upgrade I must doing as a install??
regards
cr3pt

Someone tested it in L5?
Sent from my LG-E610 using xda app-developers app

If anybody is interested in CWM 6.0.4.0 Advanced Edition / PhilZ Touch 5.16.6, please forward this message to PhilZ thread, since I'm some posts short to post in dev section.
Please add support for LG Optimus L7 (cm_p700) (should fit p705 too).
Android.mk:
#LG Optimus L7 (p700/p705)
else ifeq ($(TARGET_PRODUCT), cm_p700)
TARGET_COMMON_NAME := lge_p700
BOARD_USE_NTFS_3G := false
BOARD_USE_EXFAT_FUSE := false
LOCAL_CFLAGS += -DTARGET_DEVICE_P700
Official device files on CyanogenMod have only "jellybean" branch, so I used TeamHackLG repo.
On cm-10.1:
<project path="device/lge/e610" name="TeamHackLG/android_device_lge_e610" remote="github" revision="cm-10.1" />
<project path="device/lge/msm7x27a-common" name="TeamHackLG/android_device_lge_msm7x27a-common" remote="github" revision="cm-10.1" />
<project path="device/lge/p700" name="TeamHackLG/android_device_lge_p700" remote="github" revision="cm-10.1" />
<project path="kernel/lge/msm7x27a-common" name="TeamHackLG/lge-kernel-lproj" remote="github" revision="android-msm-3.4-jb42" />
<remove-project name="CyanogenMod/android_bootable_recovery" />
<project path="bootable/recovery" name="PhilZ-cwm6/philz_touch_cwm6" remote="github" revision="cm-10.1" />
On cm-10.2:
<project path="device/lge/e610" name="TeamHackLG/android_device_lge_e610" remote="github" revision="cm-10.2" />
<project path="device/lge/msm7x27a-common" name="TeamHackLG/android_device_lge_msm7x27a-common" remote="github" revision="cm-10.2" />
<project path="device/lge/p700" name="TeamHackLG/android_device_lge_p700" remote="github" revision="cm-10.2" />
<project path="kernel/lge/msm7x27a-common" name="TeamHackLG/lge-kernel-lproj" remote="github" revision="android-msm-3.4-jb4.3" />
<remove-project name="CyanogenMod/android_bootable_recovery" />
<project path="bootable/recovery" name="PhilZ-cwm6/philz_touch_cwm6" remote="github" revision="cm-10.2" />
Builds without errors, flashes and works.
Recovery and boot images from stock p700 v20e (P70020e-EUR-XX, Android 4.1.2, kernel 3.4.0)
P.S. Aroma File Manager has picture rotated by 180 deg, while touch areas are correctly oriented,
Seems this is due ro.sf.hwrotation=180 for p700.

ADambi said:
If anybody is interested in CWM 6.0.4.0 Advanced Edition / PhilZ Touch 5.16.6, please forward this message to PhilZ thread, since I'm some posts short to post in dev section.
Please add support for LG Optimus L7 (cm_p700) (should fit p705 too).
Android.mk:
#LG Optimus L7 (p700/p705)
else ifeq ($(TARGET_PRODUCT), cm_p700)
TARGET_COMMON_NAME := lge_p700
BOARD_USE_NTFS_3G := false
BOARD_USE_EXFAT_FUSE := false
LOCAL_CFLAGS += -DTARGET_DEVICE_P700
Official device files on CyanogenMod have only "jellybean" branch, so I used TeamHackLG repo.
On cm-10.1:
<project path="device/lge/e610" name="TeamHackLG/android_device_lge_e610" remote="github" revision="cm-10.1" />
<project path="device/lge/msm7x27a-common" name="TeamHackLG/android_device_lge_msm7x27a-common" remote="github" revision="cm-10.1" />
<project path="device/lge/p700" name="TeamHackLG/android_device_lge_p700" remote="github" revision="cm-10.1" />
<project path="kernel/lge/msm7x27a-common" name="TeamHackLG/lge-kernel-lproj" remote="github" revision="android-msm-3.4-jb42" />
<remove-project name="CyanogenMod/android_bootable_recovery" />
<project path="bootable/recovery" name="PhilZ-cwm6/philz_touch_cwm6" remote="github" revision="cm-10.1" />
On cm-10.2:
<project path="device/lge/e610" name="TeamHackLG/android_device_lge_e610" remote="github" revision="cm-10.2" />
<project path="device/lge/msm7x27a-common" name="TeamHackLG/android_device_lge_msm7x27a-common" remote="github" revision="cm-10.2" />
<project path="device/lge/p700" name="TeamHackLG/android_device_lge_p700" remote="github" revision="cm-10.2" />
<project path="kernel/lge/msm7x27a-common" name="TeamHackLG/lge-kernel-lproj" remote="github" revision="android-msm-3.4-jb4.3" />
<remove-project name="CyanogenMod/android_bootable_recovery" />
<project path="bootable/recovery" name="PhilZ-cwm6/philz_touch_cwm6" remote="github" revision="cm-10.2" />
Builds without errors, flashes and works.
Recovery and boot images from stock p700 v20e (P70020e-EUR-XX, Android 4.1.2, kernel 3.4.0)
P.S. Aroma File Manager has picture rotated by 180 deg, while touch areas are correctly oriented,
Seems this is due ro.sf.hwrotation=180 for p700.
Click to expand...
Click to collapse
Anybody tried this?
from LG-P705G w/ Vanir Rom Weeklies

Here's safe CMW 6.0.3.2 Touch flashable http://www.sendspace.com/file/i3see9

bootloader link is dead

dead link bro

Error:Syncing sources

Fetching projects: 99% (407/411) Fetching project platform/developers/docs
error: Cannot fetch androidarmv6/android_kernel_goldfish
warn: --force-broken, continuing to sync
Fetching projects: 100% (411/411), done.
Syncing work tree: 69% (284/411) error: revision cm-10.1_2.6.29 in androidarmv6/android_kernel_goldfish not found
[email protected]:~/armv6$
How to solve this error?
Edit: I have seen in androidarmv6 github, there is no android_kernel_goldfish project...but my roomservice.xml points to that project....if i remove it, then there are lots of errors....how to get past that error @androidarmv6, @A_U anna... @erikcas, @yajnab
This is my roomservice.xml:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="androidarmv6/android_kernel_goldfish" path="kernel/goldfish" remote="github" revision="cm-10.1_2.6.29" />
<project name="androidarmv6/android_device_samsung_tass" path="device/samsung/tass" remote="github" />
<project name="androidarmv6/android_kernel_samsung_msm" path="kernel/samsung/msm" remote="github" revision="jb_chocolate-samsung" />
<project name="androidarmv6/android_kernel_samsung_msm7x27" path="kernel/samsung/msm7x27" remote="github" />
<project name="androidarmv6/android_device_qcom_msm7x27" path="device/qcom/msm7x27" remote="github" />
<project name="androidarmv6/android_device_samsung_msm7x27-common" path="device/samsung/msm7x27-common" remote="github" />
<project name="androidarmv6/android_vendor_samsung" path="vendor/samsung" remote="github" />
<project name="androidarmv6/android_vendor_qcom_msm7x27" path="vendor/qcom/msm7x27" remote="github" />
<project name="androidarmv6/android_hardware_atheros_ath6kl-compat" path="hardware/atheros/ath6kl-compat" remote="github" />
<project name="androidarmv6/android_hardware_atheros_wifi_libs" path="hardware/atheros/wifi/libs" remote="github" />
<project name="androidarmv6/android_hardware_broadcom_fmradio" path="hardware/broadcom/fmradio" remote="github" />
</manifest>

Venkatesh said:
Fetching projects: 99% (407/411) Fetching project platform/developers/docs
error: Cannot fetch androidarmv6/android_kernel_goldfish
warn: --force-broken, continuing to sync
Fetching projects: 100% (411/411), done.
Syncing work tree: 69% (284/411) error: revision cm-10.1_2.6.29 in androidarmv6/android_kernel_goldfish not found
[email protected]:~/armv6$
How to solve this error?
Edit: I have seen in androidarmv6 github, there is no android_kernel_goldfish project...but my roomservice.xml points to that project....if i remove it, then there are lots of errors....how to get past that error @androidarmv6, @A_U anna... @erikcas, @yajnab
This is my roomservice.xml:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="androidarmv6/android_kernel_goldfish" path="kernel/goldfish" remote="github" revision="cm-10.1_2.6.29" />
<project name="androidarmv6/android_device_samsung_tass" path="device/samsung/tass" remote="github" />
<project name="androidarmv6/android_kernel_samsung_msm" path="kernel/samsung/msm" remote="github" revision="jb_chocolate-samsung" />
<project name="androidarmv6/android_kernel_samsung_msm7x27" path="kernel/samsung/msm7x27" remote="github" />
<project name="androidarmv6/android_device_qcom_msm7x27" path="device/qcom/msm7x27" remote="github" />
<project name="androidarmv6/android_device_samsung_msm7x27-common" path="device/samsung/msm7x27-common" remote="github" />
<project name="androidarmv6/android_vendor_samsung" path="vendor/samsung" remote="github" />
<project name="androidarmv6/android_vendor_qcom_msm7x27" path="vendor/qcom/msm7x27" remote="github" />
<project name="androidarmv6/android_hardware_atheros_ath6kl-compat" path="hardware/atheros/ath6kl-compat" remote="github" />
<project name="androidarmv6/android_hardware_atheros_wifi_libs" path="hardware/atheros/wifi/libs" remote="github" />
<project name="androidarmv6/android_hardware_broadcom_fmradio" path="hardware/broadcom/fmradio" remote="github" />
</manifest>
Click to expand...
Click to collapse
Remove the roomservice.xml and resync

yajnab said:
Remove the roomservice.xml and resync
Click to expand...
Click to collapse
Thanks yajnab...but i din't fix..produced more errors....nevermind fixed it already...what i did is created another directory and referencing previous directory intialized repo in newly created directory and did repo sync....already compiled a build for my mini also....everything working except camera.... din't applied camera force close hack...

yajnab said:
Remove the roomservice.xml and resync
Click to expand...
Click to collapse
this is what happened after removing roomservice.xml
Syncing work tree: 99% (396/400) Traceback (most recent call last):
File "/home/venkatesh/armv6/.repo/repo/main.py", line 418, in <module>
_Main(sys.argv[1:])
File "/home/venkatesh/armv6/.repo/repo/main.py", line 394, in _Main
result = repo._Run(argv) or 0
File "/home/venkatesh/armv6/.repo/repo/main.py", line 142, in _Run
result = cmd.Execute(copts, cargs)
File "/home/venkatesh/armv6/.repo/repo/subcmds/sync.py", line 657, in Execute
project.Sync_LocalHalf(syncbuf)
File "/home/venkatesh/armv6/.repo/repo/project.py", line 1106, in Sync_LocalHalf
lost = self._revlist(not_rev(revid), HEAD)
File "/home/venkatesh/armv6/.repo/repo/project.py", line 2074, in _revlist
return self.work_git.rev_list(*a, **kw)
File "/home/venkatesh/armv6/.repo/repo/project.py", line 2227, in rev_list
p.stderr))
error.GitError: CyanogenMod/android_vendor_qcom_opensource_v8 rev-list ('^ed6baff3b8971fe968a30c0c7dc631be1f31fd5c', 'HEAD', '--'): fatal: bad object HEAD

[Q] Need help with local_manifest.xml for Paranoid Android

Hi everybody,
I've found a thread about [GUIDE][AOSPA:v3.+] How to Compile AOSPA from Source : + Support and Maintenance . So with help from @Kevinjoa im start building ubuntu 13.10 machine for compiling.
Now i've problem with local_manifest.xml which last night attempt i got Error : fetch from source.
My local_manifest.xml :
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="Kevindeving/android_device_samsung_golden" path="device/samsung/golden" />
<project name="Kevindeving/android_kernel_samsung_golden" path="kernel/samsung/golden" />
<project name="OliverG96/android_vendor_samsung_golden" path="vendor/samsung/golden" />
</manifest>
Click to expand...
Click to collapse
From the tutorial it shows like this :
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="ParanoidAndroid/android_device_samsung_i9300" path="device/samsung/i9300" remote="github" revision="cm-10.2" />
<project name="CyanogenMod/android_kernel_samsung_smdk4412" path="kernel/samsung/smdk4412" remote="github" revision="cm-10.2" />
<project name="ParanoidAndroid/android_device_samsung_smdk4412-common" path="device/samsung/smdk4412-common" remote="github" revision="cm-10.2" />
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="cm-10.2" />
<project name="CyanogenMod/android_packages_apps_SamsungServiceMode" path="packages/apps/SamsungServiceMode" remote="github" revision="cm-10.2" />
<project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" remote="github" revision="cm-10.2" />
</manifest>
Click to expand...
Click to collapse
My question is, what should i replace in :
<project name="ParanoidAndroid/android_device_samsung_i9300" path="device/samsung/i9300" remote="github" revision="cm-10.2" />
<project name="ParanoidAndroid/android_device_samsung_smdk4412-common" path="device/samsung/smdk4412-common" remote="github" revision="cm-10.2" />
Click to expand...
Click to collapse
Thanks in advance!

[GUIDE][DEV]Compiling CyanogenMod 12.1 NEO builds for Xperia T, TX, V

Maybe this will help someone..
I'll be visiting this thread occasionally in case someone needs help. But I'd be glad if people and future devs also helped each other. :good:
If you compile a running build with these instructions, feel free to share it with people in this thread. Maybe development for these phones is not over yet! :fingers-crossed:
Soo.. Let's start!
What you need:
- Basic coding skills
- A GitHub account and some skills on how to use git.
- A computer with decent specs. (using an i5-4670k and 8gb ram here)
- LOTS of free storage. I recommend at least 100-200GB. The more, the better.
- A linux VM with all neccesary tools to build android. I recommend BBQLinux.
Initial Steps:
1. Grab the CM12.1 source by typing the following in your VM's Terminal:
Code:
mkdir cm12
cd cm12
repo init -u git://github.com/CyanogenMod/android.git -b cm-12.1
repo sync
This will take some hours. Just wait.
2. Create a file called roomservice.xml in /home/yourusername/cm12/.repo/local_manifests directory, containing the following:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remove-project name="CyanogenMod/android_bootable_recovery" />
<remove-project name="CyanogenMod/android_build" />
<remove-project name="CyanogenMod/android_external_bluetooth_bluedroid" />
<remove-project name="CyanogenMod/android_frameworks_av" />
<remove-project name="CyanogenMod/android_frameworks_base" />
<remove-project name="CyanogenMod/android_hardware_qcom_display" />
<remove-project name="CyanogenMod/android_libcore" />
<remove-project name="platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.8" />
<remove-project name="platform/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.8" />
<project name="ArchiDroid/Toolchain" path="prebuilts/gcc/linux-x86/arm/arm-eabi-4.8" remote="github" revision="architoolchain-4.9-arm-linux-gnueabihf-cortex_a9_neon" />
<project name="ArchiDroid/Toolchain" path="prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.8" remote="github" revision="sabermod-4.9-arm-linux-androideabi" />
<project name="CyanogenMod/android_device_sony_common" path="device/sony/common" remote="github" />
<project name="CyanogenMod/android_device_qcom_common" path="device/qcom/common" remote="github" />
<project name="CyanogenMod/android_hardware_sony_DASH" path="hardware/sony/DASH" remote="github" revision="cm-12.1" />
<project name="CyanogenMod/android_kernel_sony_msm8x60" path="kernel/sony/msm8x60" remote="github" />
<project name="WhiteNeo-/android_bootable_recovery" path="bootable/recovery" remote="github" revision="android-5.1" />
<project name="WhiteNeo-/android_build" path="build" remote="github" revision="cm-12.1" />
<project name="WhiteNeo-/android_external_bluetooth_bluedroid" path="external/bluetooth/bluedroid" remote="github" revision="cm-12.1" />
<project name="WhiteNeo-/android_frameworks_av" path="frameworks/av" remote="github" revision="cm-12.1" />
<project name="WhiteNeo-/android_frameworks_base" path="frameworks/base" remote="github" revision="cm-12.1" />
<project name="WhiteNeo-/android_hardware_qcom_display" path="hardware/qcom/display-caf/msm8960" remote="github" revision="cm-12.1-caf-8960" />
<project name="WhiteNeo-/android_libcore" path="libcore" remote="github" revision="cm-12.1" />
<project name="WhiteNeo-/android_device_sony_blue-common" path="device/sony/blue-common" remote="github" revision="cm-12.1" />
<project name="WhiteNeo-/android_device_sony_mint" path="device/sony/mint" remote="github" revision="cm-12.1" />
<project name="WhiteNeo-/android_device_sony_hayabusa" path="device/sony/hayabusa" remote="github" revision="cm-12.1" />
<project name="WhiteNeo-/android_device_sony_msm8960-common" path="device/sony/msm8960-common" remote="github" revision="cm-12.1" />
<project name="WhiteNeo-/android_device_sony_tsubasa" path="device/sony/tsubasa" remote="github" revision="cm-12.1" />
<project name="WhiteNeo-/kernel-msm" path="kernel/sony/msm8960" remote="github" revision="master" />
<project name="WhiteNeo-/proprietary_vendor_sony" path="vendor/sony" remote="github" revision="cm-12.1" />
</manifest>
3. Find all the lines containing "WhiteNeo-", fork those repositories at GitHub and replace "WhiteNeo-" with your GitHub name. (Important!)
Then copy the related repositories to your local drive with the "git clone" command.
4. Some sources are still old and need to be updated before we start to compile. These are:
android_bootable_recovery
android_build
android_external_bluetooth_bluedroid
android_frameworks_av
android_frameworks_base
android_hardware_qcom_display
android_libcore
These sources have to be updated like the example below.
Just remember that not all branches are named cm-12.1, so replace "cm-12.1" with the revision from roomservice.xml (look above)
Code:
cd android_build
git pull https://github.com/CyanogenMod/android_build.git cm-12.1
git push https://github.com/WhiteNeo-/android_build.git cm-12.1
The recovery sources are updated differently:
Code:
cd android_bootable_recovery
git pull https://github.com/omnirom/android_bootable_recovery.git android-5.1
git push https://github.com/WhiteNeo-/android_bootable_recovery.git android-5.1
5. Once more do a repo sync in your cm12 directory, to synchronize our updated repositories with the ones in CM12 directory.
6. Start the build with the following terminal commands:
Code:
cd cm12
. build/envsetup.sh
brunch yourdevicename
(Replace "yourdevicename" with your phone's manufacturer name: tsubasa = Xperia V // mint = Xperia T // hayabusa = Xperia TX)
If there are no issues, you'll find the finished ROM zip in cm12/out/target/product/yourdevicename directory.
Copy the META-INF folder from my latest NEO build over to the new zip and flash. Done.
Future builds:
Just repeat steps 4 to 6.
Troubleshooting:
If you run into toolchain errors, grab the libraries from the following link and install them in your virtual machine.
http://sabermod.com/Prebuilt-libs (DEV ONLY)/ROM-Kernel/

Hey, I need some help with a kernel build. Ive got a zimage and I cant compile it into a boot.img and doomkernerls tutorial is only for jelly bean

Can it be done with ScriBt?