THIS IS A THREAD FOR TENDERLOIN ROM DEVELOPERS TO DISCUSS ISSUES REGARDING BUILDING, CODING, CREATING, DEBUGGING AND STABILIZING A CM10.1/JELLYBEAN 4.2.x ROM FOR THE HP TOUCHPAD. IF YOU AREN'T WORKING ON THIS, MOVE ALONG... NOTHING TO SEE HERE
Seriously, folks. This is an information exchange thread for developers. You're welcome to watch and listen, but PLEASE, please, don't ask user questions here, don't ask for ETA's, don't give huzzahs, and "I want this" stuff. Post that in the relevant ROM threads, the General or the Q&A. Thanks.
Thanks for starting this thread, shumash. Here's what I have so far:
I have built a 10.1 rom for the hp tenderloin. I am not posting the actual rom because it has a way to go. It is far from a daily driver. Instead, I am posting a link so other developers can build their own roms and maybe we can get a fully working cm10.1 rom.
My device tree is on github:
https://github.com/drmarble/android_device_hp_tenderloin/tree/10.1-ugly
On the 10.1-ugly branch is a semi working device tree for hp tenderloin cm10.1.
Many more details for building are included in the README file.
If you aren't set up to build cyanogenmod roms for the tenderloin, this won't be any use to you. It truely is developer only.
It is a work in progress. Very, very much a WIP.
Camera doesn't work.
Bluetooth doesn't work.
Thanks to the efforts of James Sullins the SDCARD mounts and sound works from the speakers.
This is heavily reliant on the work of Arne Coucheron.
His invaluable patches include:
http://review.cyanogenmod.org/#/c/34375
http://review.cyanogenmod.org/#/c/34377/
http://review.cyanogenmod.org/#/c/34374/
and his highly useful google doc:
https://docs.google.com/document/d/1cGKMXx112gGls9a6ziDTpPgObnU6ZExPy5tByqqIyI4/edit?pli=1
Without his work, we would still have no display.
Of course, everything depends upon the work of the cyanogenmod hp developers Dalingren, FatTire, jcsullins, eyeballer, dorregaray and all the rest.
All my patches are in one big, ugly patch. I included various gerrit patches that my patch is dependent on. I'll work on neatening it up so the commits are separate and readable. I just wanted to get this out there so others could work on it and we can get cm10.1 working.
I think that this is everything.
Please, lets have lots of folks working on this. We can't use gerrit because this isn't cyanogenmod. Steve Kondik feels that since we are dependent upon the legacy qcom repositories it isn't really cm. This is just a kang. We can post patches here, or link to our githubs. Or use pull requests. I also started a thread on Rootzwiki. IRC on #cyanogenmod-touchpad on Freenode is a good place to chat. Jcsullins has already contributed two essential patches that got us SDCARD mounting and sound via irc.
We can get this done together.
drmarble said:
Thanks for starting this thread, shumash. Here's what I have so far:
I have built a 10.1 rom for the hp tenderloin. I am not posting the actual rom because it has a way to go. It is far from a daily driver. Instead, I am posting a link so other developers can build their own roms and maybe we can get a fully working cm10.1 rom.
--SNIP--
We can get this done together.
Click to expand...
Click to collapse
Thanks for that informative post. What are you using for a default manifest and kernel source?
most of the information needed to build is in the README file at my github. I use the regular cm manifest and build tools. The local manifest I use is:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="drmarble/android_device_hp_tenderloin" path="device/hp/tenderloin" remote="github" revision="10.1-ugly" />
<project name="CyanogenMod/hp-kernel-tenderloin" path="kernel/hp/tenderloin" remote="github" revision="ics" />
<project name="CyanogenMod/android_hardware_atheros_wlan" path="hardware/atheros/wlan" remote="github" revision="jellybean" />
<project name="arco/android_hardware_qcom_display-legacy" path="hardware/qcom/display-legacy" remote="github" revision="cm-10.1" />
<project name="arco/android_hardware_qcom_media-legacy" path="hardware/qcom/media-legacy" remote="github" revision="cm-10.1" />
</manifest>
I just use the regular cm kernel. The addional repos work together with a couple of flags in Boardconfig.mk. Those are set in my "big_ugly_patch" which should have been broken up into several different ones. Really, you just have to set up a cm build environment, put in my local_manifest.xml, repo sync, apply the various commits listed in the README file and "brunch tenderloin".
To those who want a downloadable ROM. There isn't one yet. I don't think this is ready for anybody but home brewers. jcsullins' and others cm10 builds are much more stable and useable. This is just more fun for build-it-yourself-ers because it is newer and shinier. It's not a better android experience yet.
It may be worth mentioning, for clarity, to make sure you have included vendor/hp/tenderloin.
<project name="TheMuppets/proprietary_vendor_hp" path="vendor/hp/tenderloin" remote="github" revision="jellybean" />
I've been working on including the latest Adreno drivers but have found they are dependent on the CAF varriant, and we are stuck using legacy. Which is exactly why Steve Kondik said "I do not want to create official builds for any device that needs to use this. If your device can't support the latest driver for whatever reason, it's going to be janky and slow and probably worse than stock on 10.1."
I am trying to take some inspiration from the HTC Sensation, aka Pyramid, because that device is also msm8660 and they are utilizing the legacy display variant in 4.2.2 as well - without any complaints about video playback.
You can also use unzip-files.sh or extract-files.sh from device/hp/tenderloin to get the proprietary files. You just have to use jcsullins' latest cm10 zip file or installed rom (20130304etc.zip). These may be even more current than TheMuppets. They haven't been updated for 6 months. I know that the proprietary-files.txt file has been modified since then. I think that he updated some of the proprietary files so that sound would work. He also added some adreno libs, though we should look into the latest 4.2.2 adreno libs.
I'm trying out the Evervolv manifest, which is mostly AOSP. If it works, we may be able to get a mashup of the CM and AOSP source trees that gives us some options. So far, however, I've had to comment out the audio.primary.tenderloin package and the Settings package overlay in the tenderloin device source to get it to continue the compilation. I'll report back tomorrow.
drmarble said:
You can also use unzip-files.sh or extract-files.sh from device/hp/tenderloin to get the proprietary files. You just have to use jcsullins' latest cm10 zip file or installed rom (20130304etc.zip). These may be even more current than TheMuppets. They haven't been updated for 6 months. I know that the proprietary-files.txt file has been modified since then. I think that he updated some of the proprietary files so that sound would work. He also added some adreno libs, though we should look into the latest 4.2.2 adreno libs.
Click to expand...
Click to collapse
Are you getting any video playback with your builds using extract-flies.sh? All I ever seem to get is an infinite "loading" screen. I once used CM9 Adreno drivers in building CM10, with the same "loading" effect.
shumash said:
I'm trying out the Evervolv manifest, which is mostly AOSP. If it works, we may be able to get a mashup of the CM and AOSP source trees that gives us some options. So far, however, I've had to comment out the audio.primary.tenderloin package and the Settings package overlay in the tenderloin device source to get it to continue the compilation. I'll report back tomorrow.
Click to expand...
Click to collapse
Ok, after much thrashing, I"ve got everything compiled and waiting in the OUT folder, it stops with this:
Code:
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
out/target/product/tenderloin/obj/PACKAGING/systemimage_intermediates/unsparse_system.img: 1376/51296 files (0.0% non-contiguous), 60991/204800 blocks
Install system fs image: out/target/product/tenderloin/system.img
out/target/product/tenderloin/system.img+ maxsize=856424448 blocksize=135168 total=237901004 reserve=8650752
[email protected]:~/android/skz$
I'm guessing it has something to do with the releasetools, but I get no error. Any ideas?
If you look at my release patch I modify the release tools which changed for 10.1. I really need to separate that patch into it's separate parts. That would make it clear what you need to change. I did that months ago and really don't recall the reasons for each step, I just know that it works. The zip file format changed, as I recall. Wish I could help more. I'll get to work on cleaning up that patch and will make a cleaner branch soon.
drmarble said:
If you look at my release patch I modify the release tools which changed for 10.1. I really need to separate that patch into it's separate parts. That would make it clear what you need to change. I did that months ago and really don't recall the reasons for each step, I just know that it works. The zip file format changed, as I recall. Wish I could help more. I'll get to work on cleaning up that patch and will make a cleaner branch soon.
Click to expand...
Click to collapse
I think I've got that covered. I modified the releasetools, too, and tried both the modified Evervolv and CM versions, but what I get is that stop. I'll check and make sure, though, and I'll compile with the "-v" switch to see if there's something I missed.
I'm not sure if you are familiar with it, but you could try an application called Meld; its a diff viewer. It always comes in handy when I'm comparing code.
If you want to see what's different from the release tools in Evervolv and drmarble's repositories, you can just side by side compare them from your source locally :thumbup:
Also:
To go with the sound patch I removed one commit from the build process: # 34375 # MemoryHeapBase: ifdef for gingerbread/froyo compatibility We aren't using froyo libs apparently, thanks to jcsullins' new sound patch. This means we can remove -DBINDER_COMPAT from Boardconfig.mk.
For anyone who is not watching both threads
Sent from my SAMSUNG-SGH-T989 using xda premium
-SGA- said:
I'm not sure if you are familiar with it, but you could try an application called Meld; its a diff viewer. It always comes in handy when I'm comparing code.
If you want to see what's different from the release tools in Evervolv and drmarble's repositories, you can just side by side compare them from your source locally :thumbup:
Also:
To go with the sound patch I removed one commit from the build process: # 34375 # MemoryHeapBase: ifdef for gingerbread/froyo compatibility We aren't using froyo libs apparently, thanks to jcsullins' new sound patch. This means we can remove -DBINDER_COMPAT from Boardconfig.mk.
For anyone who is not watching both threads
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
Chortle, I do need to watch everything, don't I? And I do use meld. It's a great tool. What I'd like to do is to run the "tenderloin_ota_from_target_files" python script from the command line. I can just see all those compiled files sitting there waiting to be zipped up!
I've tried utilizing drivers from the HTC sensation and jcsullins CM10 03/04 build with no further success in getting video playback to function.
Shumash, any luck with getting that to compile yet? Are you trying straight Evervolv source?
Sent from my SAMSUNG-SGH-T989 using xda premium
-SGA- said:
I've tried utilizing drivers from the HTC sensation and jcsullins CM10 03/04 build with no further success in getting video playback to function.
Shumash, any luck with getting that to compile yet? Are you trying straight Evervolv source?
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
I got a CM10.1 to compile, but it boots to the flashy screen. I'm in process of running a clean make to ensure I didn't leave something nasty around. The Evervolv source built to the point that it needs to be zipped into the OTA and release files, but I think there's something missing in the make files that connects with the releasetools. I ran a compile with the verbose switch set, and it acted like it just reached the end of the make files. I have also successfully built a ROM from PAC-man sources, but it also boots to the flashy screen.
Try flashing this after you flash your ROM. It's just a collection of Adreno drivers which I have been experimenting with, it might help get you booting!
-SGA- said:
Try flashing this after you flash your ROM. It's just a collection of Adreno drivers which I have been experimenting with, it might help get you booting!
Click to expand...
Click to collapse
Would you check out that zip file, _SGA_? It fails to flash; says error in zip file (I don"t have any md5 or zip file checking going on).
shumash said:
Would you check out that zip file, _SGA_? It fails to flash; says error in zip file (I don"t have any md5 or zip file checking going on).
Click to expand...
Click to collapse
Just downloaded and flashed now, did not run into any errors. Hmm... I've uploaded it again under a different name :good:
-SGA- said:
Try flashing this after you flash your ROM. It's just a collection of Adreno drivers which I have been experimenting with, it might help get you booting!
Click to expand...
Click to collapse
Would you check out that zip file, _SGA_? It fails to flash; says error in zip file (I don"t have any md5 or zip file checking going on).
EDIT: I found that all but two of the Adreno egl files are missing in the ROM zip. Copied the egl files and your other files manually, and it now boots . I guess is we're going to have to copy them as prebuilt until we have good source.
shumash said:
Would you check out that zip file, _SGA_? It fails to flash; says error in zip file (I don"t have any md5 or zip file checking going on).
EDIT: I found that all but two of the Adreno egl files are missing in the ROM zip. Copied the egl files and your other files manually, and it now boots . I guess is we're going to have to copy them as prebuilt until we have good source.
Click to expand...
Click to collapse
Don't know if the attached are the same as those posted by SGA, but these are official ones from QualComm that I have been using with some sucess. They are advertised as...
"This release contains the user-mode driver binaries for Qualcomm's Adreno 3xx and 2xx GPU on Google Android 4.2 Jelly Bean MR1. It has been tested with the CAF release A8064AAAAANLGD133402.1 and M8960AAAAANLGD230306.1. Supports any Adreno 2xx and 3xx GPU on Android 4.2 Jelly Bean MR1."
Related
This is a continuation of the "Compiling CM6 for Eris" thread - http://forum.xda-developers.com/showthread.php?t=856215. But since Team ADX has really come together on this, we are releasing it in it's new form.
Thanks to workshed for working to get the Eris on the Official CM list and merged into the main repo. And also, thanks to workshed for most of the v6 --> v7 changes to EasyDev!
This script will grab CM7 source and compile a CM7 ROM for you using the official vendor tree that is built-in to the CM source. You have the option of including Google Apps or not.
Uses:
CM source - https://github.com/CyanogenMod/android.git
Conap's CFS kernel that's built-in to CM source - https://github.com/Conap30/htc_kernel_desirec_cfs
Requirements
-------------
1) 64- bit Linux -tested on Debian, Ubuntu 10.04, Linux Mint (if you have a different flavor of linux and easydev worked for you, please let us know so we can update this list)
2) An existing Eris ROM that the script will pull the proprietary files from.
INSTRUCTIONS
1) Download the script
2) 'chmod a+x easydev-v9.sh'
3) copy it to the directory of your choice or leave it where it is
4) copy an existing ROM to the same directory (tested with GSB, but most should work)
5) run it ('sudo ./easydev-v9.sh')
Possilbe future features:
Done.
Changelog
v1 - initial release
v2 - added squisher, made 'make clean' optional, added installation of dependencies, cleaned up output
v3 - uses existing ROM to pull proprietary files, renamed to 'easydev' for case sensitive linux admins
v4 - fixed file missing from list in unzip-files.sh in vendor tree, fixed move/rename of existing ROM, change 'make clean' option to default to no instead of yes
v5 - added 'apt-get update' to refresh repo list (should install dependencies now), swapped order of extract-files and unzip-files to fix 'chmod akmd' issue, tried not to break anything else
v6 - moved questions to beginning of script, added check to only init repo the first time, added check for existing ROM, modded vendor tree to fix compile issues
v7 - removed CM6 stuff, removed kernel compilation code, removed vendor tree code, changed from CM6 to CM7, fixed path bug, added 32-bit libs to dep list
v8 - added ALL official CM devices (mostly untested), minor update to dependency installer code (4-21-11)
v9 - added an extra check for correct Java version, fixed .zip rename issue
Download links:
v7+ --> https://github.com/gnarlyc/EasyDev-Eris
NOTE: If you have issues with google setup or not being able to pass andy the android at the beginning of setup, please delete Provisions.apk for system/app you shouldn't have a problem, but just incase, this will remedy it. -workshed
I'm all over this sh*t
Oh damn, I'm excited for this. good thing I use ubuntu!
Sent from my ERIS using XDA App
this should be fun once i get my new laptop.
Nice! I will be trying this later.
This is awesome! Thanks alot. What does the 'make clean' option do?
Skrip037 said:
This is awesome! Thanks alot. What does the 'make clean' option do?
Click to expand...
Click to collapse
The make clean removes everything that has been compile so far leaving only the original source.
Skrip037 said:
This is awesome! Thanks alot. What does the 'make clean' option do?
Click to expand...
Click to collapse
It removes any previously built ROMs, etc. It's not needed every time, so I've made it optional in the next version. The problem was that sometimes the script would be broken in some way and wouldn't build a ROM. But, there's so much text displayed to the screen, it's not always easy to notice. So, I was actually flashing the same test ROM over and over instead of getting a new build...
Great work guys. Going to try it out on Arch Linux and if anyone's interested I'll give details about how to get it working there (or just modify the script to detect Arch as opposed to Ubuntu and work accordingly.
<gripe>One complaint: commands (including scripts) should *always* start with a lowercase letter </gripe>
good work gnarlyc & conap.
this sounds great and i will be trying this when i get home. I have just one question. Why would i want to run this instead of conap's rom? Both being pure CM. I see alot of the other cm6 roms have stuff themed, but conap's rom doesn't. I'm assuming this is complete pure cm without little tweaks done by devs of the respective roms. Thanks in advance.
ngc604 said:
this sounds great and i will be trying this when i get home. I have just one question. Why would i want to run this instead of conap's rom? Both being pure CM. I see alot of the other cm6 roms have stuff themed, but conap's rom doesn't. I'm assuming this is complete pure cm without little tweaks done by devs of the respective roms. Thanks in advance.
Click to expand...
Click to collapse
Some people just like to "roll their own", more or less. If you like having someone else make improvements and fix issues for you, then you'll probably want to stick with another ROM.
I would love to make my own fixes and tweaks but i dont have the knowledge nor the time to gain said knowledge. guess i will just stick with the devs roms. thanks
Very very exciting. I am installing Ubunto 10.4 now. So does EasyDev-v2 pull from the CM6 nightlies or the stable version and can we change where it pulls from for the CM6 source. This is great.
Will have to check this out later. Always wanted to understand the compile process, always to busy with other software projects. Thanks for building this resource for the rest of us.
morrisdan said:
Very very exciting. I am installing Ubunto 10.4 now. So does EasyDev-v2 pull from the CM6 nightlies or the stable version and can we change where it pulls from for the CM6 source. This is great.
Click to expand...
Click to collapse
Hmmm. Someone correct me if I'm wrong, but I'm pretty sure that this is currently grabbing 'stable'.
Code:
repo init -u git://github.com/CyanogenMod/android.git -b froyo
I'm thinking that to get the nightly, we'll have to change that to:
Code:
repo init -u git://github.com/CyanogenMod/android.git -b master
I'll try it as soon as I can. You got me to thinking that we could add that as an option, if I understand this correctly.
Nightly vs Stable
Yes, you answered my question regarding nightly and stable. I am having fun so far. I got all the necessary packages installed. That was pretty easy using the Ubunto package manager deal. So where do I find the proprietary.zip now? I am almost there to cook this sucker up.
morrisdan said:
Yes, you answered my question regarding nightly and stable. I am having fun so far. I got all the necessary packages installed. That was pretty easy using the Ubunto package manager deal. So where do I find the proprietary.zip now? I am almost there to cook this sucker up.
Click to expand...
Click to collapse
I was apparently wrong about the "-b master" switch, but I think I mostly got it right...
Right now, you'll have to grab the files listed in the OP and zip them up into a file called 'proprietary.zip'. Then place it in the same directory that you run the script from.
I'm working on a way that you can just place an existing ROM there, and it will extract the proprietary files for you. That should be in v3.
Proprietary.zip Files
Can I download CELB Froyo 3.8 and uncompress it and do searches for those files and pull them out and zip them up?
morrisdan said:
Can I download CELB Froyo 3.8 and uncompress it and do searches for those files and pull them out and zip them up?
Click to expand...
Click to collapse
Yes, that should work fine. Here's a list with the paths -
https://github.com/Conap30/android_device_htc_desirec/blob/master/extract-files.sh
this is not to rush the devs, just asking, are they gonna wait till ( i really hope it actually hapens) jb update comes to us to start developing? couse i think our phone haves a lot more to give to us than the stock rom can, again i am not rushing the devs, just asking your oppinion, and since im kinda new to theese forums hardly think any dev is going to bother to even answer this thread
so im pretty much.asking your oppinion
this is just a question , please dont kill me
sent from the gray stuff inside my skull
demonoid phenomenom said:
this is not to rush the devs, just asking, are they gonna wait till ( i really hope it actually hapens) jb update comes to us to start developing? couse i think our phone haves a lot more to give to us than the stock rom can, again i am not rushing the devs, just asking your oppinion, and since im kinda new to theese forums hardly think any dev is going to bother to even answer this thread
so im pretty much.asking your oppinion
this is just a question , please dont kill me
sent from the gray stuff inside my skull
Click to expand...
Click to collapse
If you mean Custom Roms... we can't do anything until we can pack / unpack the boot.img/or recovery.img to make a custom recovery.
jeah thats right, i was wondering because my expirience with atrix 2 , previous to the ics update, i was using supercharger rom series, but again i understand that they got a leak to work on, and a bootstrap to flash the restores they where creating, and that stock leaked rom was awesome
sent from the gray stuff inside my skull
mattlgroff said:
If you mean Custom Roms... we can't do anything until we can pack / unpack the boot.img/or recovery.img to make a custom recovery.
Click to expand...
Click to collapse
Only for my own curiosity: what's prevents that ? The x86 arch ? or something else ?
Le_Poilu said:
Only for my own curiosity: what's prevents that ? The x86 arch ? or something else ?
Click to expand...
Click to collapse
Would be nice to know for sure. The current methods cannot find 'Android Magic'.
I'm looking forward to seeing this forum get some custom ROMs too...
Looks like progress is getting on with it now
Any updates on custom ROM making for this device?
I've followed the README from <link to Motorola's sourceforge for razr i, deleted because I'm a new user> , got to the final step, but now I'm stumped. What make target should I choose? 'make full_x86-eng' and 'make generic_x86' have no make rules. A simple 'make' generates a framework build error.
What do I have to do in order to get a bootable image (built from source) for the Razr i?
I'd appreciate any kind of advice. Thanks in advance.
PS: Many thanks Matt, turl1 and the other developers that worked on this device.
tiberiu24 said:
Any updates on custom ROM making for this device?
I've followed the README from <link to Motorola's sourceforge for razr i, deleted because I'm a new user> , got to the final step, but now I'm stumped. What make target should I choose? 'make full_x86-eng' and 'make generic_x86' have no make rules. A simple 'make' generates a framework build error.
What do I have to do in order to get a bootable image (built from source) for the Razr i?
I'd appreciate any kind of advice. Thanks in advance.
PS: Many thanks Matt, turl1 and the other developers that worked on this device.
Click to expand...
Click to collapse
You won't be able to build a full android system from that source. The most you can do is
Code:
$ . build/envsetup.sh
$ lunch generic_x86-eng
$ make [I]target[/I]
Where target is something like out/target/product/generic/system/bin/bluetoothd or bluetoothd
I am working on a device tree. Writing it from scratch isn't easy because there is no device I can base this on. No other x86 tree out there. And I still dont have a device. I did make threads requesting for a device but they got closed down. So once I have something built I'll make a new thread.
Sent from my GT-I9300 using xda app-developers app
hiemanshu said:
I am working on a device tree. Writing it from scratch isn't easy because there is no device I can base this on. No other x86 tree out there. And I still dont have a device. I did make threads requesting for a device but they got closed down. So once I have something built I'll make a new thread.
Click to expand...
Click to collapse
There's at least 10 device trees on the android-x86 project. And AOSP itself has a generic one, to build the x86 emulator platform. And I made a basic one to build recovery already, with support to generate the newer x86 boot image format.
Just saying
PS: I don't own the phone either
turl1 said:
There's at least 10 device trees on the android-x86 project. And AOSP itself has a generic one, to build the x86 emulator platform. And I made a basic one to build recovery already, with support to generate the newer x86 boot image format.
Just saying
PS: I don't own the phone either
Click to expand...
Click to collapse
Generic x86 and the razr I are too far apart. Also the android x86 ones are too far apart too (I am working on a android x86 tablet). I have already written more than 450 lines of the device tree by hand, and there is a lot more to go right now. I have patched bionic for x86 builds, I need to patch the build folder next, and even busybox needs patching, etc. I am now working on making a perfect set of the 3 important files, BoardConfing.mk, device.mk and proprietary-files.txt. My android x86 tree is a total of 181 lines (which in itself is twice the size of the trees on android-x86). Its fun, but really time consuming. Also the AOSP ones are generic ones, they will work on any system if you have all the correct drivers installed or compiled via the kernel, but Razr I needs the files to be pulled from the stock build, and it needs a lot of them, including kernel drivers.
-H
hiemanshu said:
Generic x86 and the razr I are too far apart. Also the android x86 ones are too far apart too (I am working on a android x86 tablet). I have already written more than 450 lines of the device tree by hand, and there is a lot more to go right now. I have patched bionic for x86 builds, I need to patch the build folder next, and even busybox needs patching, etc. I am now working on making a perfect set of the 3 important files, BoardConfing.mk, device.mk and proprietary-files.txt. My android x86 tree is a total of 181 lines (which in itself is twice the size of the trees on android-x86). Its fun, but really time consuming. Also the AOSP ones are generic ones, they will work on any system if you have all the correct drivers installed or compiled via the kernel, but Razr I needs the files to be pulled from the stock build, and it needs a lot of them, including kernel drivers.
-H
Click to expand...
Click to collapse
I'm playing a bit with AOSP 4.2 as I got some free time. This is what I found out so far:
bionic needed no patches. I seriously doubt it needs any on 4.1 (CM) either as recovery built fine.
build needed no patches either on both cases.
dalvik needed a 4-liner to build on AOSP (makefile fixes), I haven't tried to build it on CM
there's no busybox on AOSP, I patched the one on 4.1 already to be able to build recovery, it's all on CM Gerrit as you'd expect from a CM developer like myself
my tree is already 120 lines, as soon as you add the media decoder config and audio routing config you'll go over 180 lines
having proper drivers isn't enough, you need proper HALs too. And I haven't really looked, but I'd be surprised if you had to pull kernel drivers from the stock rom
turl1 said:
I'm playing a bit with AOSP 4.2 as I got some free time. This is what I found out so far:
bionic needed no patches. I seriously doubt it needs any on 4.1 (CM) either as recovery built fine.
build needed no patches either on both cases.
dalvik needed a 4-liner to build on AOSP (makefile fixes), I haven't tried to build it on CM
there's no busybox on AOSP, I patched the one on 4.1 already to be able to build recovery, it's all on CM Gerrit as you'd expect from a CM developer like myself
my tree is already 120 lines, as soon as you add the media decoder config and audio routing config you'll go over 180 lines
having proper drivers isn't enough, you need proper HALs too. And I haven't really looked, but I'd be surprised if you had to pull kernel drivers from the stock rom
Click to expand...
Click to collapse
1) bionic needs patching, patch already submitted to CM gerrit libdvm basically
2) build needs patching for the boot.img
3) dalvik has been patched
4) Odd, didn't notice that
5) Probably wont required pulling in kernel drivers, but would required pulling in the correct drivers for the defconfig
I'd be happy if you wanted to work together to get this working. PM me
hiemanshu said:
1) bionic needs patching, patch already submitted to CM gerrit libdvm basically
2) build needs patching for the boot.img
3) dalvik has been patched
4) Odd, didn't notice that
5) Probably wont required pulling in kernel drivers, but would required pulling in the correct drivers for the defconfig
I'd be happy if you wanted to work together to get this working. PM me
Click to expand...
Click to collapse
Let's continue talking on PM then
re. 2, I actually did need to patch build on AOSP after all . CM on the other hand, has BOARD_CUSTOM_BOOTIMG_MK from the tf tablets.
Hey I posted a rom over at droidrzr.com for use till aosp is ready. This should be enough till we get a jb leak
Sent from my XT890 using Tapatalk 2
Hi Folks
While I don't own a RAZR I , I have been Jaffing around with building CM10.1 and AOSP for x86, I've been getting in going on my FX8120, just need to sort the OpenGLES MESA drivers out.
Anyways I've got CM10.1 built for x86 using the mr1-staging branch ( I think it's been merged to cm10.1 ) and an edited mini-x86 device tree .
Busybox was a B**stard to build though, although on one of the branches there is an .config-minimal-x86 .config-full-x86, still needed tweaking tho.
I submitted my patches http://review.cyanogenmod.org/#/c/27377/ and http://review.cyanogenmod.org/#/c/27373/, however It seems x86 isn't top of cm's agenda.... or I'm missing something about assigning reviewers.
Obviously a base x86 build is only part of the story for you guys as you'll face all the regular problems that emedded devices have, not checked the specs for the RazR but I'm sure there's some binary blobs in your future,
Hack On Folks! :good:
Thanks to mamenyaka's efforts, we now have a running version of Ubuntu Touch on the Xperia Tablet Z. I'm attempting to do some customization of this kernel (such as add btusb support), but I'm not all the familiar with the Cyanogen build process. So looking for a little help here.
I've been following these instructions:
http://wiki.cyanogenmod.org/w/Build_for_pollux_windy
Now, I think the process is as follows:
Setup environment according to the wiki, up through the "repo init" step.
Add the "local_manifest.xml" from https://github.com/mamenyaka/android/ to ~/android/system/.repo/local_manifests
Run a repo sync in ~/android/system.
and this is where I get a bit confused. I _think_ the next step is then to run source build/envsetup.sh and breakfast pollux_windy, and then proceed according to the instructions as usual, excepting extracting the blobs. I think those are already included.
However, can someone confirm this? Or is there a step/steps I'm leaving out?
Thanks.
PS - yes, this should probably be in the dev forum, but the post count rules are forcing me to post it here...
If you want to build Ubuntu Touch, you should follow the porting guide.
You can't mix the two. The CM repo init and ubuntu's phablet-dev-bootstrap (ubuntu's repo init) use very different manifest.xmls. And if you want to build CM (advised if you never built android from source), you don't need the repos from my github.
Next thing: breakfast. It is a good to use when you build CM, but it's not good for building Ubuntu Touch. Breakfast adds CM repos specific to your device in a file in .repo/local_manifest (roomservice.xml). For Ubuntu Touch you don't need all of the device specific repos and you also need to apply some modifications in these repos (which I already done), and to use them, you will need to add the repos manually (local_manifest/local_manifest.xml, similar to roomservice.xml, but I prefer this file, because roomservice.xml is related to breakfast), so no breakfast needed.
Then simply repo sync to get the new repos.
The extra blobs are included thanks to TheMuppets repos.
To start building, simply $ . build/envsetup.sh and $ brunch pollux_windy. But all of this can be found in the guide or on CM wiki.
For building Ubuntu Touch you need a few extra things mentioned in the guide, like the phablet tool, and you need to update the ubuntu/platform-api bzr repo (bzr pull) - this isn't done by repo sync because it isn't a git repo, it's ubuntu's bazaar.
mamenyaka said:
If you want to build Ubuntu Touch, you should follow the porting guide.
You can't mix the two. The CM repo init and ubuntu's phablet-dev-bootstrap (ubuntu's repo init) use very different manifest.xmls. And if you want to build CM (advised if you never built android from source), you don't need the repos from my github.
Next thing: breakfast. It is a good to use when you build CM, but it's not good for building Ubuntu Touch. Breakfast adds CM repos specific to your device in a file in .repo/local_manifest (roomservice.xml). For Ubuntu Touch you don't need all of the device specific repos and you also need to apply some modifications in these repos (which I already done), and to use them, you will need to add the repos manually (local_manifest/local_manifest.xml, similar to roomservice.xml, but I prefer this file, because roomservice.xml is related to breakfast), so no breakfast needed.
Then simply repo sync to get the new repos.
The extra blobs are included thanks to TheMuppets repos.
To start building, simply $ . build/envsetup.sh and $ brunch pollux_windy. But all of this can be found in the guide or on CM wiki.
For building Ubuntu Touch you need a few extra things mentioned in the guide, like the phablet tool, and you need to update the ubuntu/platform-api bzr repo (bzr pull) - this isn't done by repo sync because it isn't a git repo, it's ubuntu's bazaar.
Click to expand...
Click to collapse
Okay, thanks for pointing me in the right direction. Thought I had to use CM build instead to use your repos. That's why this thread is here. I'd like to get instructions out here that could decrease the learning curve on some of this.
Are you aware of the state of CM on pollux_windy? I notice that Ubuntu has breakfast in their official porting guide now. Would you expect that to work, or are there further changes in your repositories to enhance their work?
In other words, Ubuntu's guide suggests doing a "breakfast pollux_windy", "repo sync", some tweaks, and then a build, under the Automatic build section.
I think your repo would work with the process under the "Manual (deprecated)" section. Is there a reason to use one over the other? Have you already integrated the required modifications in your repos, for example?
Sorry if this is all a bit pedantic. Just trying to come up to speed on the build process for all of this. I've built many a linux kernel, but I'm not at all familiar with this build process.
Thanks again for your help.
themikem said:
Okay, thanks for pointing me in the right direction. Thought I had to use CM build instead to use your repos. That's why this thread is here. I'd like to get instructions out here that could decrease the learning curve on some of this.
Are you aware of the state of CM on pollux_windy? I notice that Ubuntu has breakfast in their official porting guide now. Would you expect that to work, or are there further changes in your repositories to enhance their work?
In other words, Ubuntu's guide suggests doing a "breakfast pollux_windy", "repo sync", some tweaks, and then a build, under the Automatic build section.
I think your repo would work with the process under the "Manual (deprecated)" section. Is there a reason to use one over the other? Have you already integrated the required modifications in your repos, for example?
Sorry if this is all a bit pedantic. Just trying to come up to speed on the build process for all of this. I've built many a linux kernel, but I'm not at all familiar with this build process.
Thanks again for your help.
Click to expand...
Click to collapse
Don't worry, I am here to answer your questions.
So, breakfast in Ubuntu Touch is good when you want to start off a brand new port.
The advantage of using my repos and using the manual method is that I already integrated the required modifications and, most importatnly, the image builds. Simply using the CM repos, you would get build errors, which are fixed in my repos; for example, removing the android parts.
Also, if you are interested, you could join this group.
mamenyaka said:
Don't worry, I am here to answer your questions.
So, breakfast in Ubuntu Touch is good when you want to start off a brand new port.
The advantage of using my repos and using the manual method is that I already integrated the required modifications and, most importatnly, the image builds. Simply using the CM repos, you would get build errors, which are fixed in my repos; for example, removing the android parts.
Also, if you are interested, you could join this group.
Click to expand...
Click to collapse
Thanks for the tip. It worked!
For the record, it turned out to be this simple:
(~/phablet is arbitrary)
mkdir ~/phablet && cd ~/phablet
phablet-dev-bootstrap ~/phablet
repo sync
Add ~/phablet/.repo/local_manifests/local_manifest.xml from: https://github.com/mamenyaka/android
repo sync
. build/envsetup.sh
brunch pollux_windy
...and then flash the files from $OUT (~/android/system/out/target/product/pollux_windy)
Also note that I had a terrible time making git work through my NAT. Tried both a hardware router (Cisco) and my standard Vyatta VM. Ultimately had to put my build machine directly on a publicly-routable IP to make it go. If you're having problems with Git on 13.04, it could be the same issue. I'm not aware of any other fix, other than finding some way to switch the build system to http:// instead of git://
Now off to reconfigure the kernel. This should be interesting...
One thing, without this you won't be able too boot.
You need to replace boot.img from the .zip with ubuntu-boot.img from $OUT and rename, of course, to boot.img.
ubuntu-boot.img should be bigger in size.
Hope this is the right place, but am I correct to assume that its possible to run Ubuntu Touch on the Xperia Z Tablet?
If so are there any tutorials on this?
Tel'X
telx85 said:
Hope this is the right place, but am I correct to assume that its possible to run Ubuntu Touch on the Xperia Z Tablet?
If so are there any tutorials on this?
Tel'X
Click to expand...
Click to collapse
You gotta be kidding, right?
http://forum.xda-developers.com/showthread.php?t=2336018
mamenyaka said:
You gotta be kidding, right?
http://forum.xda-developers.com/showthread.php?t=2336018
Click to expand...
Click to collapse
Nope, but thanks for that.
Looks very promising.
mamenyaka said:
Don't worry, I am here to answer your questions.
So, breakfast in Ubuntu Touch is good when you want to start off a brand new port.
The advantage of using my repos and using the manual method is that I already integrated the required modifications and, most importatnly, the image builds. Simply using the CM repos, you would get build errors, which are fixed in my repos; for example, removing the android parts.
Also, if you are interested, you could join this group.
Click to expand...
Click to collapse
I have some questions, for example I want to try build the ubuntu touch to a new port (actually not new port, just the progress of development of my phone is held on), I just refer to your local manifest.xml file? Sure I know need to change to device specific repo, I have it on other developer github.
Just the question is, how do I recognise which part is belong to android parts and remove them? Or which part should be remained?
Sent from my SGP311 using xda app-developers app
Trevor Chuah said:
I have some questions, for example I want to try build the ubuntu touch to a new port (actually not new port, just the progress of development of my phone is held on), I just refer to your local manifest.xml file? Sure I know need to change to device specific repo, I have it on other developer github.
Just the question is, how do I recognise which part is belong to android parts and remove them? Or which part should be remained?
Sent from my SGP311 using xda app-developers app
Click to expand...
Click to collapse
You have a cm.dependencies file in your device's repo which tells what other repos it needs (for example kernel).
You can instantly remove any android app related repo (like android_packages_apps_FMRadio).
But if you tell me what phone, I can give you some hints.
mamenyaka said:
You have a cm.dependencies file in your device's repo which tells what other repos it needs (for example kernel).
You can instantly remove any android app related repo (like android_packages_apps_FMRadio).
But if you tell me what phone, I can give you some hints.
Click to expand...
Click to collapse
The phone I'm using is Xperia S. The developer has his github name OpenSEMC.
Thank you.
Sent from my Xperia S using xda app-developers app
Trevor Chuah said:
The phone I'm using is Xperia S. The developer has his github name OpenSEMC.
Thank you.
Sent from my Xperia S using xda app-developers app
Click to expand...
Click to collapse
You could start over from scratch. Just fork the CM repos. The OpenSEMC repos are not really ubuntu touch oriented.
mamenyaka said:
You could start over from scratch. Just fork the CM repos. The OpenSEMC repos are not really ubuntu touch oriented.
Click to expand...
Click to collapse
Okay. So basically the post #5 is applicable to every phone right?
I just follow it and modify the
1) local manifest to correct repo
2) remove the android part
Right?
I will try it.
Thank you.
Sent from my Xperia S using xda app-developers app
May I ask?
If I use phablet-dev-bootstrap, it will follow the android.git in http://phablet.ubuntu.com/gitweb right?
I did it, and
I checked the default.xml inside the android repo, to roughly compare with the file synced into local.
I found that it has many thing missing, for example the following:
Code:
<project path="external/mockwebserver" name="CyanogenMod/android_external_mockwebserver" />
<project path="external/mp4parser" name="CyanogenMod/android_external_mp4parser" />
<project path="frameworks/opt/inputmethodcommon" name="CyanogenMod/android_frameworks_opt_inputmethodcommon" />
<project path="frameworks/opt/mailcommon" name="CyanogenMod/android_frameworks_opt_mailcommon" />
and many of them.
Is it ubuntu automatically not download these file since they are not important?
Trevor Chuah said:
May I ask?
If I use phablet-dev-bootstrap, it will follow the android.git in http://phablet.ubuntu.com/gitweb right?
I did it, and
I checked the default.xml inside the android repo, to roughly compare with the file synced into local.
I found that it has many thing missing, for example the following:
Code:
<project path="external/mockwebserver" name="CyanogenMod/android_external_mockwebserver" />
<project path="external/mp4parser" name="CyanogenMod/android_external_mp4parser" />
<project path="frameworks/opt/inputmethodcommon" name="CyanogenMod/android_frameworks_opt_inputmethodcommon" />
<project path="frameworks/opt/mailcommon" name="CyanogenMod/android_frameworks_opt_mailcommon" />
and many of them.
Is it ubuntu automatically not download these file since they are not important?
Click to expand...
Click to collapse
Be sure to check out the phablet-saucy branch of default.xml, that's what phablet-dev-bootstrap pulls.
---------- Post added at 11:40 AM ---------- Previous post was at 11:30 AM ----------
Trevor Chuah said:
Okay. So basically the post #5 is applicable to every phone right?
I just follow it and modify the
1) local manifest to correct repo
2) remove the android part
Right?
I will try it.
Thank you.
Sent from my Xperia S using xda app-developers app
Click to expand...
Click to collapse
Mostly right, but there is always something extra that needs to be done with every device.
Be sure to get the sony proprietary blobs from TheMuppets on github and post any questions, errors you need help with.
mamenyaka said:
Be sure to check out the phablet-saucy branch of default.xml, that's what phablet-dev-bootstrap pulls.
---------- Post added at 11:40 AM ---------- Previous post was at 11:30 AM ----------
Mostly right, but there is always something extra that needs to be done with every device.
Be sure to get the sony proprietary blobs from TheMuppets on github and post any questions, errors you need help with.
Click to expand...
Click to collapse
The following is my local_manifest.xml file
Code:
<project path="device/sony/common" name="OpenSEMC/android_device_sony_common" remote="github" revision="cm-10.1" />
<project path="device/sony/nozomi" name="OpenSEMC/android_device_sony_nozomi" remote="github" revision="cm-10.1" />
<project path="device/sony/fuji-common" name="OpenSEMC/android_device_sony_fuji-common" remote="github" revision="cm-10.1" />
<project path="device/sony/qcom-common" name="OpenSEMC/android_device_sony_qcom-common" remote="github" revision="cm-10.1-legacy" />
<project path="kernel/sony/msm8x60" name="OpenSEMC/android_kernel_sony_msm8x60" remote="github" revision="cm-10.1-legacy" />
<project path="vendor/sony" name="OpenSEMC/proprietary_vendor_sony" remote="github" revision="cm-10.1-lagacy" />
<project path="hardware/sony/DASH" name="OpenSEMC/android_hardware_sony_DASH" remote="github" revision="cm-10.1" />
<project path="hardware/qcom/media" name="OpenSEMC/android_hardware_qcom_media-legacy" remote="github" revision="cm-10.1-legacy" />
I referred to your local_minifest.xml and the original author xml file and conclude this.
I do not know is it correct or not.
May I ask, will the recovery automatically add into the compile device image? What will it use? CWM?
Trevor Chuah said:
The following is my local_manifest.xml file
I referred to your local_minifest.xml and the original author xml file and conclude this.
I do not know is it correct or not.
May I ask, will the recovery automatically add into the compile device image? What will it use? CWM?
Click to expand...
Click to collapse
I think you should go with CyanogenMod for all repos except vendor, and TheMuppets for the vendor/sony (revision=cm-10.1 for all) if you want to start clean. Then just follow the porting guide.
It will use CWM.
mamenyaka said:
I think you should go with CyanogenMod for all repos except vendor, and TheMuppets for the vendor/sony (revision=cm-10.1 for all) if you want to start clean. Then just follow the porting guide.
It will use CWM.
Click to expand...
Click to collapse
But CyanogenMod (FXP) did not publish CM10.1 for Xperia S, heard that they do not fix for the display.
Therefore I do not know whether if use the CM repo, what should I modify for the video to display.
Still newbie...
Trevor Chuah said:
But CyanogenMod (FXP) did not publish CM10.1 for Xperia S, heard that they do not fix for the display.
Therefore I do not know whether if use the CM repo, what should I modify for the video to display.
Still newbie...
Click to expand...
Click to collapse
I don't know much about nozomi. There exists the CM 10.1 repo for nozomi, but true, there is no cm-10.1 release.
You might have to experiment a little, stuff like common, qcom, DASH are available in CM, but if they have device specific fixes, than it may be the only route to use OpenSEMC repos.
Anyone else experienced this? I'm building for Mako and the build is successful although after flashing the screen is just black after the google logo.
Do I need to extract the N4 binaries for this or am I missing something else? Thanks!
Sent from my Nexus 4 using XDA Premium 4 mobile app
You don't have the proprietary blobs.
Put the following line into your /omni/.repo/local_manifests/whatever.xml, resync and do a clobber recompile.
Code:
<project name="TheMuppets/proprietary_vendor_lge.git" path="vendor/lge" remote="github" revision="cm-10.2" />
chasmodo said:
You don't have the proprietary blobs.
Put the following line into your /omni/.repo/local_manifests/whatever.xml, resync and do a clobber recompile.
Code:
<project name="TheMuppets/proprietary_vendor_lge.git" path="vendor/lge" remote="github" revision="cm-10.2" />
Click to expand...
Click to collapse
Warning: This isn't guaranteed for all devices, as for some we're probably going to be diverging from current blob repos over time.
That is admittedly a bit of a problem now - without nightlies or existing builds, extract-files isn't the most reliable, and right now the blob repos the developers are using are private until we can sort out how to handle them. (Blob repos are always a bit of a complex legal grey area, which is why none of the official CM documentation references the repos at TheMuppets anywhere.)
For nearly all devices where it's known that SOMEONE has it booting from the repos you're using, blank screen on boot usually means no blobs. (A good way to check is to see if your ZIP is much smaller than typical for builds for that device.)
@Entropy512
and as non dev its imbossible to get hands on your private blobs atm?
In the mako build it mentions getting the blob files from developers.google.com/android/nexus/drivers#makojwr66y and putting them in the correct vendor directory. Should this work or is it necessary that we use the muppets binaries still?
Never mind, I figured out what the problem was thanks to some help in the irc chat. I updated the wiki page for building mako too.
caspian154 said:
Never mind, I figured out what the problem was thanks to some help in the irc chat. I updated the wiki page for building mako too.
Click to expand...
Click to collapse
What was the problem? Cause I have the same problem when trying to build rom for HTC One S C2.
makkeonmies said:
@Entropy512
and as non dev its imbossible to get hands on your private blobs atm?
Click to expand...
Click to collapse
It's quite possible - Quite a few people found them within 5 minutes of the first push to those repos on github...
The repos are public, we just don't go out of our way to point to them for various reasons.
(blob handling has always been a mess and will always suck - keep in mind that blob handling was one of the primary contributors to JBQ's final burnout and departure from AOSP.)
Hi,
I synced the CM10.1 source last weekend. I mucked about with the kernel. I pointed it to Christopher83's custom toolchain. I built it. It works. I'm content.
However my plan was to revive 4.2.2 and actually ADD to it, otherwise you could just go and download the zip which the Andromadus team uploaded. Unfortunately I've discovered that I'm completely incompetent when it comes to firstly finding things to add, secondly finding the commit, and then thirdly trying to cherry pick and apply the commit so it works. I haven't really got to stage 3 yet.
So here's my suggestion: could someone please work with me or if syncing sources etc. is not possible, at least help me by being knowledgeable enough to know some good features, point me to the commits, and help me fix conflicts so that I can apply them successfully. Therefore I either want a team, the 4.2.2 revival team as it were, or someone or some people to help me if they can't directly interact with the sources. Don't worry if you can't build for whatever reason: if you can sync specific repos, e.g. settings, frameworks base, and modify them, and push them, so that I can build the ROM, that's fine. Anyone who helps at all will be deemed equally if not more important than myself, as I expect I'll ultimately just end up being the builder.
Thanks very much for your support.
I can help you with that. Tell me when you start your project and what errors did you get
Best Regards,
MarcoMarinho
RE: [DEV] CM10.1 builds | help needed adding features | "4.2.2 Revival Team"
_MarcoMarinho_ said:
I can help you with that. Tell me when you start your project and what errors did you get
Best Regards,
MarcoMarinho
Click to expand...
Click to collapse
Thanks firstly I thought a simple thing to do would be to add the recent app screen ram bar from SlimBean, but I can't find the commit anywhere in the SlimRoms github. Perhaps you know where it is or can find it for me, then I could cherrypick it and we could fix the conflicts together and we'd have our first unofficial CM10.1 ROM with additional features!
HTCDreamOn said:
Thanks firstly I thought a simple thing to do would be to add the recent app screen ram bar from SlimBean, but I can't find the commit anywhere in the SlimRoms github. Perhaps you know where it is or can find it for me, then I could cherrypick it and we could fix the conflicts together and we'd have our first unofficial CM10.1 ROM with additional features!
Click to expand...
Click to collapse
Sure
Here is the commit: https://github.com/SlimRoms/frameworks_base/commit/9c1c3c0955d51adc589ec6fbb667a0ae482de24e
You need this to: https://github.com/AOSB/android/commit/a512f16890af8c277c3d1a88c8bca36711b82328
RE: [DEV] CM10.1 builds | help needed adding features | "4.2.2 Revival Team"
_MarcoMarinho_ said:
Sure
Here is the commit: https://github.com/SlimRoms/frameworks_base/commit/9c1c3c0955d51adc589ec6fbb667a0ae482de24e
You need this to: https://github.com/AOSB/android/commit/a512f16890af8c277c3d1a88c8bca36711b82328
Click to expand...
Click to collapse
That looks interesting, but it's for KitKat... I'll try later once I'm confident. In the meantime, how can I get this to work: https://github.com/SlimRoms/packages_apps_Settings/commit/fb2ea42468bea20f09b99048c9e7535b6cde643f I'm OK apart from the very last bit in UserInterface.java, although I'm applying that code to SystemSettings.java anyway. Thanks
@demkantor @_MarcoMarinho_ I've synced the PA source, can you help me at all setting up the vision.adds file? Thanks
Sure thing, assume this is for 4.2 android right?
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
Sure thing, assume this is for 4.2 android right?
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yep, as you know I synced the CM10.1 source a while ago so I used repo init --reference to sync the PA jellybean-legacy sources. Thanks for helping
paste this in a folder and title it
local_manifests
then add it to your .repo folder in ROM directory
I commented out a few things you may need to add, and there is possibly more but i dont have time to look into it all right now. just start with this, repo sync, and then build and check for errors
best of luck!
damn.... giving me uknown file, had to zip it first, so unzip the contents!
demkantor said:
paste this in a folder and title it
local_manifests
then add it to your .repo folder in ROM directory
I commented out a few things you may need to add, and there is possibly more but i dont have time to look into it all right now. just start with this, repo sync, and then build and check for errors
best of luck!
damn.... giving me uknown file, had to zip it first, so unzip the contents!
Click to expand...
Click to collapse
Thanks, do I only need to add these to the vision.adds file then, or do I not need a vision.adds file at all now?
HTCDreamOn said:
Thanks, do I only need to add these to the vision.adds file then, or do I not need a vision.adds file at all now?
Click to expand...
Click to collapse
cant say I've ever used a vision.adds file in a source build, I just find the files i need in github, download source, create a local_manifest, sync, check errors for somethings to add to manifest, build, check for errors, google how to fix, fix, fix, fix ,fix, then bam, got a rom that works.
but I can look into this vision.adds business, I don't think it will be necessary as this will place need files in the proper directories in your source code for you, I assume that's what the vision.adds would do?
demkantor said:
cant say I've ever used a vision.adds file in a source build, I just find the files i need in github, download source, create a local_manifest, sync, check errors for somethings to add to manifest, build, check for errors, google how to fix, fix, fix, fix ,fix, then bam, got a rom that works.
but I can look into this vision.adds business, I don't think it will be necessary as this will place need files in the proper directories in your source code for you, I assume that's what the vision.adds would do?
Click to expand...
Click to collapse
Here's the bit from their guide: http://forum.xda-developers.com/showpost.php?p=30958881&postcount=2 I'm not sure what it does though. I'm completely clueless about that whole post actually. I think it just syncs stuff after a sync.. or something. I don't know why though, isn't that what a local manifests file is for?
hmm... it looks like there will be a bit more to make than just the local_manifests
but i would attempt this first and if it doesnt work than follow the direction in that post as there me be a special way needed to build for pa, which i never have tried to build
most of what they are after will get pulled from local_manifests folder and placed appropriately. but at the same time... never used ./rom-build.sh before so this may be specific to pa, as in you need to follow their steps....
eh, just give it a try, if it doesnt work ill help you create those json files and build it the way laid out in their guide!
HTCDreamOn said:
Here's the bit from their guide: http://forum.xda-developers.com/showpost.php?p=30958881&postcount=2 I'm not sure what it does though. I'm completely clueless about that whole post actually. I think it just syncs stuff after a sync.. or something. I don't know why though, isn't that what a local manifests file is for?
Click to expand...
Click to collapse
Isn't easy, you need to add more repos to configure it for our phone.
This is very diferent:
http://forum.xda-developers.com/showpost.php?p=45827346&postcount=3467
As I said before, you need extra repos than CM needs. You can talk to the dev that made the SlimBean for our phone, as it's based on AOSP he needed to configure it as well.