I am trying to build GB aosp from source on ubuntu for my phone samsung conquer 4G. I already have the source and in it there is a platform and in the text for it it says to put those files in the folders in the source than build. I am wondering if I would only replace files and not put in new ones? Or if I would even do this. If I shouldnt, how would I even port after its built and does anyone know what poison I should choose? Thanks a bunch
Any reason why GB? ICS or JB would be better wouldn't it? I'm not the best person to try to answer your question, but you will have to supply a little more info, I will help if I can.
onlychevys said:
Any reason why GB? ICS or JB would be better wouldn't it? I'm not the best person to try to answer your question, but you will have to supply a little more info, I will help if I can.
Click to expand...
Click to collapse
Thanks, i am building gb because my phone does not have any official roms like cm,aosp,etc. I am the only person with the device that is capable of building from source i have already built a kernel. Also i am doing gb because my phones version is 2.3.6 and it should be easier to port than ics or jb. If you need any more info i will be glad to give you it.
bump
itzdarockz said:
I am trying to build GB aosp from source on ubuntu for my phone samsung conquer 4G. I already have the source and in it there is a platform and in the text for it it says to put those files in the folders in the source than build. I am wondering if I would only replace files and not put in new ones? Or if I would even do this. If I shouldnt, how would I even port after its built and does anyone know what poison I should choose? Thanks a bunch
Click to expand...
Click to collapse
Could use some clarification
When you refer to the source are you talking aosp? Or your device source?
If your referring to the device source that goes in working/device/manufacturer/devicename/
Could you provide a screenshot of the device source? Wanna make sure it looks like a proper device tree
As for poison...you just add your device to the lunch menu and build it...create a file in your device tree called vendorsetup.sh (just right click and go to create new document and name it that) then open it with a text editor (gedit) and type this and save it :
Code:
add_lunch_combo full_devicename-eng
(replace "devicename" with your device
Then in the root of your working folder type
Code:
. build/envsetup.sh
lunch
Choose your device then type
Code:
make otapackage
or to fully utilize your CPU
Code:
make -j# otapackage
replacing "#" with the number of CPU cores your computer has plus 1 or 2...so for dual core I usually do male -j4 otapackage
Sent from my HTC PH39100 using Tapatalk 2
mg2195 said:
Could use some clarification
When you refer to the source are you talking aosp? Or your device source?
If your referring to the device source that goes in working/device/manufacturer/devicename/
Could you provide a screenshot of the device source? Wanna make sure it looks like a proper device tree
As for poison...you just add your device to the lunch menu and build it...create a file in your device tree called vendorsetup.sh (just right click and go to create new document and name it that) then open it with a text editor (gedit) and type this and save it :
Code:
add_lunch_combo full_devicename-eng
(replace "devicename" with your device
Then in the root of your working folder type
Code:
. build/envsetup.sh
lunch
Choose your device then type
Code:
make otapackage
or to fully utilize your CPU
Code:
make -j# otapackage
replacing "#" with the number of CPU cores your computer has plus 1 or 2...so for dual core I usually do male -j4 otapackage
Sent from my HTC PH39100 using Tapatalk 2
Click to expand...
Click to collapse
When i mean the source I meant my phones. It has two zips, kernel and platform. It has txt files on how to build the kernel and the update. And thanks man. The screen is attatched. The folders are build, extension, external, libcore, and vendor.
i was afraid of that...doesnt look like a device tree...and unfortunatly i have no expiernece creating a device tree from scratch/from manufacturer source...
anyways heres an example of two device tree i use...
mg2195 said:
i was afraid of that...doesnt look like a device tree...and unfortunatly i have no expiernece creating a device tree from scratch/from manufacturer source...
anyways heres an example of two device tree i use...
Click to expand...
Click to collapse
Thats why it says in a txt to replace files in the aosp source with the ones in the folder.
itzdarockz said:
Thats why it says in a txt to replace files in the aosp source with the ones in the folder.
Click to expand...
Click to collapse
Well do what it says then...it has .mk files and looks like that when placed in aosp?
Sent from my HTC PH39100 using Tapatalk 2
mg2195 said:
Well do what it says then...it has .mk files and looks like that when placed in aosp?
Sent from my HTC PH39100 using Tapatalk 2
Click to expand...
Click to collapse
Actually I think we do have a non manufacturer source does this look good? https://github.com/utkanos/android_device_samsung_SPHD600
itzdarockz said:
Actually I think we do have a non manufacturer source does this look good? https://github.com/utkanos/android_device_samsung_SPHD600
Click to expand...
Click to collapse
Yeah...looks small...but that's a device tree
Sent from my HTC PH39100 using Tapatalk 2
mg2195 said:
Yeah...looks small...but that's a device tree
Sent from my HTC PH39100 using Tapatalk 2
Click to expand...
Click to collapse
Doesn't building, I made the tree like you said with these files no luck.. I went to the Crespo 4gs and it has two folders.. But mine has 1. Also do u think I should port over some of the files i dont have from the crespo 4gs folder
itzdarockz said:
Doesn't building, I made the tree like you said with these files no luck.. I went to the Crespo 4gs and it has two folders.. But mine has 1. Also do u think I should port over some of the files i dont have from the crespo 4gs folder
Click to expand...
Click to collapse
Wouldnt hurt to try
Sent from my HTC PH39100 using Tapatalk 2
Related
I've tried porting several roms to my devices and every time I try to flash I always get status 0 or some type of error! I can't logcat from recovery because some things do not work completely with clockworkmod I have. I even manually tried porting the same method that android kitchen does and still run into the same problem. I have no idea what I should try next? This is really making me made. I get no help at all after searching and searching every where!
android kitchen
http://forum.xda-developers.com/showthread.php?t=633246
all in one guide
http://forum.xda-developers.com/showthread.php?t=1273718
And some other methods and still no luck!!
You are right. There is no guide. It's trial and error. Logcat helps and if you know what certain files do that helps too.
It's simple:
grab the sources from github, add your device and vendor folder, add the device to the list in the mk files, lunch, and build.
openetna is a repository with many bugfixes, as you will have them.
Easy ****!
mDroidd said:
It's simple:
grab the sources from github, add your device and vendor folder, add the device to the list in the mk files, lunch, and build.
openetna is a repository with many bugfixes, as you will have them.
Easy ****!
Click to expand...
Click to collapse
Thats great if building from source
but i think he is talking about porting roms that are not AOSP.
The problem with a porting tutorial is that all devices and roms are a bit different so there will never will be a tutorial to get this done 100%. They are great guides to give you a start but it can take a lot more to get things ported.
if the device architecture is similar
Ex... Evo 4g to Incredible
than porting is fairly easy
being able to logcat is very necessary when porting roms
getting that working is your first step.
I always gave up on porting just because i dont have the patients to do it.
Exactly. I've ported several roms from the E3D and Sensation to the Rezound, and they are easy because the processor is the same. All you really need to get it booting is the kernel in most cases.
mDroidd said:
It's simple:
grab the sources from github, add your device and vendor folder, add the device to the list in the mk files, lunch, and build.
openetna is a repository with many bugfixes, as you will have them.
Easy ****!
Click to expand...
Click to collapse
Not that simple if you have to make a device tree from scratch like I'm doing
I've a question!!
I have an HTC Explorer (based on Qualcomm MSM7227) and I'd like to build a rom (AOSP or Cyano)...
I've downloaded Kernel Source Code but after hours of researches I haven't found a guide for merge a rom with a kernel..
can you help me?
thank you!
Can we port a rom from HTC desire to Motorola defy....is it easy??
HIT THANKS IF IVE HELPED
extremists said:
Can we port a rom from HTC desire to Motorola defy....is it easy??
HIT THANKS IF IVE HELPED
Click to expand...
Click to collapse
That's about as hard as it gets.
Unless building from source its not as difficult.
Sent from my PG86100 using Tapatalk
wes342 said:
That's about as hard as it gets.
Unless building from source its not as difficult.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
Do u know how to port??
HIT THANKS IF IVE HELPED
The thing is there's also no real guide on how to make your own public repo for devices who don't have one .
E.g. Galaxy R
Herpderp Defy.
So I found out how to build from cm7 sources and it is a no go... I do not know how in the world you guys can port any roms. How do you get your files up on git hub any way? There is more to it then just compiling from cm sources..
Here's a slightly outdated one
EmoBoiix3 said:
The thing is there's also no real guide on how to make your own public repo for devices who don't have one .
E.g. Galaxy R
Herpderp Defy.
Click to expand...
Click to collapse
Just so its clear... this (slightly outdated) guide would be (the best I've found) for building a device tree (that you may elect to throw up on github) that can be used to build AOSP.. the same device tree probably could build CyanogenMod or MIUI fairly easily (minimal editing) but you are correct... no exact guide bc its not an exact science (lots of different devices out there with lots of different device configurations; even kernels different some are ti omap, some are qualcomm msm, etc.). Basically you build a tree to define your hardware.. AOSP, CM or MIUI will build themselves based on this definition (device) tree.
http://www.kandroid.org/online-pdk/guide/build_new_device.html
Now after you follow this guide, google the various build errors you get (one at a time) and perfect your tree until you get basic bring up... then perfect it some more until you get all your modules working (will take some aosp kernel cooking as well)... then perfect it some more... in a few months you should have something pretty decent (and learn tree building a bit more; we all learn by doing ) Best advice I have for you; going through the same thing myself.
Also wouldn't be a bad idea to download Hardware Info apk (Sleek Apps) and email yourself the info it spits out. That way you at least have a list of some of the hardware you are trying to define.
Rob
mDroidd said:
It's simple:
grab the sources from github, add your device and vendor folder, add the device to the list in the mk files, lunch, and build.
openetna is a repository with many bugfixes, as you will have them.
Easy ****!
Click to expand...
Click to collapse
How exactly do you do this? How do you build it completely specifically for your device?
Sorry, I'm a complete noob on building from scratch and Linux. Could anyone shed some some light?
Thanks you guys
I need help upgrading a device tree to a Jelly Bean device tree. Please pm me for more details. Thanks
Read this thread: http://forum.xda-developers.com/showthread.php?t=1762641
onlychevys said:
Read this thread: http://forum.xda-developers.com/showthread.php?t=1762641
Click to expand...
Click to collapse
Thanks for your response, I already looked at that forum and its about compiling Jelly Bean from source. I didn't see anything about updating a device tree to Jelly Bean. Thanks
He you tried building with your ICS device tree and seeing what doesn't work?
jd3107 said:
I need help upgrading a device tree to a Jelly Bean device tree. Please pm me for more details. Thanks
Click to expand...
Click to collapse
Look in your manifest.xml and change from ics to jellybean, then repo sync and you should be synced to JB. If you are wanting to build CM10 it will be your local_manifest.xml located in your .repo file. You will have to type ctrl h to show hidden files to see your .repo file
onlychevys said:
Look in your manifest.xml and change from ics to jellybean, then repo sync and you should be synced to JB. If you are wanting to build CM10 it will be your local_manifest.xml located in your .repo file. You will have to type ctrl h to show hidden files to see your .repo file
Click to expand...
Click to collapse
No that's pulling down Jellybean sources, not making sure your device tree is Jellybean compatible. Still correct and a required step, just not exactly what the OP was looking for.
Sent from my SCH-R760 using Tapatalk 2
thewadegeek said:
He you tried building with your ICS device tree and seeing what doesn't work?
Click to expand...
Click to collapse
Thanks, the problem I am having is the only device tree I have found for my device is gingerbread 2.3.7. I'm not sure if I build one for jellybean before ICS. Thanks for all your help.
onlychevys said:
Look in your manifest.xml and change from ics to jellybean, then repo sync and you should be synced to JB. If you are wanting to build CM10 it will be your local_manifest.xml located in your .repo file. You will have to type ctrl h to show hidden files to see your .repo file
Click to expand...
Click to collapse
Thanks, I will try this. Does this work for changing a 2.3.7 device tree to jellybean as well? Thanks for all your help.
jd3107 said:
I need help upgrading a device tree to a Jelly Bean device tree. Please pm me for more details. Thanks
Click to expand...
Click to collapse
Just changing the device tree to comparable with jellybean isn't going to enable you to build jellybean. There are still many kernel changes, framework edits, and system library changes. For the most part, you can get jellybean to build for just about any device. Its once the device tree is updated and have a working build that's the hard part, because now you have to fix it all.
If you want guidance on how a device tree is updated from versions. Check out a device that had gingerbread as well. Look at the tree changes to build ICS, then look at the changes from ICS to jellybean. You can also do a diff from gingerbread to jellybean on said device. See what changed and attempt those changes keeping in mind your own device specific elements.
Sorry if this isnt the answer you were looking for. Its better then the real answer of you need to figure it out by trial and error like everyone else. All devices are different.
Sent from my Galaxy Nexus using xda premium
lithid-cm said:
Just changing the device tree to comparable with jellybean isn't going to enable you to build jellybean. There are still many kernel changes, framework edits, and system library changes. For the most part, you can get jellybean to build for just about any device. Its once the device tree is updated and have a working build that's the hard part, because now you have to fix it all.
If you want guidance on how a device tree is updated from versions. Check out a device that had gingerbread as well. Look at the tree changes to build ICS, then look at the changes from ICS to jellybean. You can also do a diff from gingerbread to jellybean on said device. See what changed and attempt those changes keeping in mind your own device specific elements.
Sorry if this isnt the answer you were looking for. Its better then the real answer of you need to figure it out by trial and error like everyone else. All devices are different.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Lithid,
Thanks for your reply. I am going to do what you said and do a comparison of gingerbread, ICS and Jellybean. Hopefully I can get the tree built and go from there. Any place you know of where I can get info on the kernel changes I will need? Or do I have to trial and eror that as well? Thanks
jd3107 said:
Lithid,
Thanks for your reply. I am going to do what you said and do a comparison of gingerbread, ICS and Jellybean. Hopefully I can get the tree built and go from there. Any place you know of where I can get info on the kernel changes I will need? Or do I have to trial and eror that as well? Thanks
Click to expand...
Click to collapse
You would need to find a phone with a similar architecture type. You could sift through those commits. Most should be spot on but nothing is absolute.
lithid-cm said:
You would need to find a phone with a similar architecture type. You could sift through those commits. Most should be spot on but nothing is absolute.
Click to expand...
Click to collapse
OK thanks I appreciate all your help. I will give it a shot! Thanks guys
lithid-cm said:
You would need to find a phone with a similar architecture type. You could sift through those commits. Most should be spot on but nothing is absolute.
Click to expand...
Click to collapse
I know I'm lacking in understanding some of the term's used, but some of the comments made in this thread have made me consider options I hadn't thought of before. The tablet I use mentioned in my signature, might be the focus of my previous efforts for upgrading to Android 4.1, (which it would appear that the manufacturer has no intention of doing), but my focus is now directed toward other models of this brand that have, or will, receive an update. Once I find the likely candidate to focus my attention on, I'll get the old (Android 4.0) ROM and the new (Android 4.1) ROM and compare my 4.0 to see what the differences are.
I know it will be far more than the device tree that needs changes, but it's a step in the right direction. Which would at least indicate some movement. It seems like I started my quest for JB so lonmg ago, but it's only been a few weeks of pouring over page after page of mostly disappointing search results. Maybe theres light at the end of the tunnel after all. Perhaps a bright light. Maybe I'll walk into it...
k.
Hey all, since a lot of folks are wondering about custom roms for the DX, I decided to start this thread to document my exploits in trying to compile CM9.
Basically, I'm new to Android (had an iPhone 3GS for about 2 years) so I'm going to need a lot of help and this is really going to start of very basic. But since I had my Desire X and been on this forum, I have met more and more cool people that are actively trying to help development for our phone, like stereo8,maartenxda and yasir, so I'm sure we'll be alright. None of this would be even possible if not for LLior that made the CWM recovery for us. :good:
OK, so to build CM9 you need a build environment set up specifically for the job, there's many guides out there on how to do this, but I found this one (props to mbroeders, OP of the tut) pretty good :
http://forum.xda-developers.com/showthread.php?t=1566224
Basically, building CM9 is done in linux, Ubuntu being the most popular version, and I'll be using the latest Ubuntu 12. If you don't use Ubuntu as main OS, you can still try this, but you'll need to set up a good (!) portion of your harddrive to install it in a virtual environment, like VMWare Player (free). Mind you, we'll be downloading the CM9 source, which ended up being around 10 gig on my pc, and we'll be needing at least another 16 gig to actually build CM9. To be on the safe, I set aside 50 gig on my drive for the virtual Ubuntu-pc in VMWare.
The guide I'm using will show you how to set up a general build environment, but since we are talking about the Desire X, which is brand new and without official CM support (yet?), we are going to have to adapt it to make CM9 for our phone. Several people have already worked on this, mainly Lloir, so I got his permission to use the stuff he's already done. A big thanks btw, from one and all
And this is basically the first time I'm going to need help. To adapt the build system specifically for the DX, we'll need to make a local_manifest file that points it to device and vendor trees LLoir has made. The local_manifest is supposed to go in the .repo folder of your CM9 source.
How do I do this ?
Goto cm9 wiki and install all prerequisites. Then do a repo init of the main build tree(cm9) and then add the device trees to manifest.xml found in .repo. after that , you sync via repo sync and then you setup environment through envsetup.sh and then you build for protou by brunch protou. Debug the errors you encounter. That's about it. If it doesn't boot after successful build, then the device/hardware/vendor/kernel trees need some sorting out .
Regards.
Sent from my HTC Desire X using xda app-developers app
help for local_manifest - Llior ?
Morning, googled some more, and found a template for a local_manifest.xml file I'm adapting for the DX.`I prefer to go as much by the book as possible for now, apparently putting these in manifest.xml can mess up your source.
So far, I have :
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="Lloir/protou" path="device/htc/protou" remote="github" revision="ics"/>
<project name="LLior/XXXXXXXXXXXXX" path="device/htc/msmXXXX-common" remote="github" revision="ics"/>
<project name="Lloir/android_vendor_htc_protou" path="vendor/htc/protou" remote="github" revision="ics"/>
<project name="Llior/XXXXXXXXXXXXX" path="kernel/htc/msmXXXX" remote="github" revision="XXXXXXXXXXXX"/>
</manifest>
The XXXX need editing, not sure which repositories though
manifest
Here you go, you can see it for your reference...
Attachment
CM9 - first build - result
Yasir Javed Ansari said:
Here you go, you can see it for your reference...
Attachment
Click to expand...
Click to collapse
OK, using your manifest, I managed to set up the system to build with Lloir's device and vendor trees.
I had to edit the msm7x30.mk file in /device/htc/msm7x30-common though so the first section of it would point to /frameworks/base rather than /frameworks/native as in the original for it to build.
It then compiled to the end, I ended up with a boot.img, recovery.img, system.img and userdata.img, which I turned into a .zip file to flash in CWM.
It installs, but gets stuck on the HTC-logo screen, but I can't take a logcat -same as with stereo's paranoidandroid : logcat.txt says logcat cant be found in /sbin/sh- even when I create a sbin/sh folder with logcat.
Anyone know what I'm doing wrong ? I would really like to see what's going on during boot.
infernal77 said:
OK, using your manifest, I managed to set up the system to build with Lloir's device and vendor trees.
I had to edit the msm7x30.mk file in /device/htc/msm7x30-common though so the first section of it would point to /frameworks/base rather than /frameworks/native as in the original for it to build.
It then compiled to the end, I ended up with a boot.img, recovery.img, system.img and userdata.img, which I turned into a .zip file to flash in CWM.
It installs, but gets stuck on the HTC-logo screen, but I can't take a logcat -same as with stereo's paranoidandroid : logcat.txt says logcat cant be found in /sbin/sh- even when I create a sbin/sh folder with logcat.
Anyone know what I'm doing wrong ? I would really like to see what's going on during boot.
Click to expand...
Click to collapse
Stock Rom showed our device shares common config from msm7k and not msm7x30. I'll try another build with some modified things to see if it boots . One thing you can do is to compare lloir device tree with other trees of similar devices to verify whether we are missing something critical. Also did you use pre.built kernel ?
AND framework native is used in jelly bean , not ics. You're syncing jelly bean cm source and device tree is currently for ics. Recheck please.
Sent from my HTC Desire X using xda app-developers app
Yasir Javed Ansari said:
Stock Rom showed our device shares common config from msm7k and not msm7x30. I'll try another build with some modified things to see if it boots . One thing you can do is to compare lloir device tree with other trees of similar devices to verify whether we are missing something critical. Also did you use pre.built kernel ?
AND framework native is used in jelly bean , not ics. You're syncing jelly bean cm source and device tree is currently for ics. Recheck please.
Sent from my HTC Desire X using xda app-developers app
Click to expand...
Click to collapse
Hm, thanks for the input, Yasir. I was wondering about it, I just synced using the default.xml in the last post. I guess that means I was using the prebuilt kernel as well. Don't worry about the source code I synced, it's definitely cm-ics. As far as I can see, there aren't files relating to msm7k in Lloir's github. I'll see if I can find out about a device that uses the msm7k.
cheers :good:
EDIT : Yasir and me are working together on trying to get a CM9 to the Desire X, anyone that wants to help (preferably with experience) is welcome Use this thread to keep things organised. Thanks
update on CM9 - wip - all help welcome !
OK, update on what's happening :
Because our phone has a new Qualcomm processor there's no CyanogenMods out yet for any device that uses it, let alone by HTC, that we can compare it to. This could help us out a lot to get the device specific information and sources the build system needs to make us a CM9. This info and these files are contained in and referred to by the so-called device and vendor trees. Lloir has done the most work for the Desire X up to now in making these device and vendor trees, but since first test builds aren't booting, Yasir and me are going over them again.
By the way, if anyone knows more about why logcat doesn't work, that would be extremely helpful. All response I get is that logcat isn't in /sbin/sh. I tried adding it to a separate /sbin/sh folder in my test build, but no dice
Good news is I found out the MSM8225 chipset was designed to be fully backward compatible, both hardware and software, with the MSM7225A and MSM7227A phones, of which Qualcomm sold about a 100 million. So, I've begun studying the device and vendor trees for the HTC Explorer (Pico), which is a MSM7225A model. Important because it has the compatible 7225A chipset and uses the ARMv7 cpu instruction set - which is the same as the Desire X.
We'll keep you guys posted, also when we need testers. :good:
Ours is cortex a5, that's why it is compatible with msm7227. But the not booting issue is probably due to some thing missing or wrong in device.mk. the board config is ok. And kernel source is also available on htcdev and git simonsimons23. The device tree and vendor mk files need correction. At least that's my thinking.
Sent from my HTC Desire X using xda app-developers app
Yasir Javed Ansari said:
Ours is cortex a5, that's why it is compatible with msm7227. But the not booting issue is probably due to some thing missing or wrong in device.mk. the board config is ok. And kernel source is also available on htcdev and git simonsimons23. The device tree and vendor mk files need correction. At least that's my thinking.
Sent from my HTC Desire X using xda app-developers app
Click to expand...
Click to collapse
OK, I'll leave the boardconfig for now (am checking the files alphabetically) and move on to device.mk If I see anything I don't get or differs from the pico source (has official CM9), I'll let you know here or through pm. I was thinking the same about the device and vendor trees, it's our starting point and we're stuck here already lol. I know about the githubs, I'll check the changes (if any) simonsimons made.
I was thinking though : don't we need the 1.18 kernel to do this ? I already flashed the updated kernel with the 1.18 ruu. I checked on htcdev and it only lists the 1.14 kernel source. Or is there a way to get it from a running phone ?
missing logcat....
Hi Guys,
I don't know why logcat is missing, but to obtain kernel messages you could run the "dmesg" command instead.
I would like to participate in DX porting. I got intermediate knowlegde in android, but I'm really good in linux and kernel stuff.
Are you guys hanging around in IRC somewhere so we cant talk directly?
currently I am compiling lloirs tree. It is running for some time already...
hang loose
maze
atmel-touchscreen.kl is not in any git
Hi Guys,
I still try building the stuff, but atmel-touchscreen seems to be missing so I decided to remove it from
htc/protou/device_protou.mk. Now it continues compiling ....
( device/htc/protou/prebuilt/usr/keylayout/atmel-touchscreen.kl:system/usr/keylayout/atmel-touchscreen.kl)
Any progress OP??? I did a recent build with some mods on weekend but it failed to boot. I'm highly suspicious that its a kernel issue although i cant say for sure. If any one manages to boot it, even if its till the boot animation, DO POST AND SHARE, coz then its easier going forward.
Regards
neXus PRIME said:
Any progress OP??? I did a recent build with some mods on weekend but it failed to boot. I'm highly suspicious that its a kernel issue although i cant say for sure. If any one manages to boot it, even if its till the boot animation, DO POST AND SHARE, coz then its easier going forward.
Regards
Click to expand...
Click to collapse
got a logcat? or even a kmsg? you can get the kmsg by rebooting into TWRP mount system and open the file manager in advanced and going into /proc grab last_kmsg from in there, you can also find me on IRC Most days, (except tonight i'm working )
-Lloir
I'm sorry guys, haven't been able to do much for this project anymore...no time (holidays and starting training to become system administrator), not to mention I spilled coke all over my Macbook Pro
Lloir said:
got a logcat? or even a kmsg? you can get the kmsg by rebooting into TWRP mount system and open the file manager in advanced and going into /proc grab last_kmsg from in there, you can also find me on IRC Most days, (except tonight i'm working )
-Lloir
Click to expand...
Click to collapse
Doesnt even get past the splash screen (the one with HTC red letter sentence about private build). I used the prebuilt kernel which i have used in recovery. I'll try getting kmsg though.
Regards
neXus PRIME said:
Doesnt even get past the splash screen (the one with HTC red letter sentence about private build). I used the prebuilt kernel which i have used in recovery. I'll try getting kmsg though.
Regards
Click to expand...
Click to collapse
You can still logcat on that screen if adb sees it
Sent from my HTC One X+ using Tapatalk 2
nopes. I have QtADB running in background with logcat ON all the time. Thats how i can never miss if it gets to boot. But i didnt check kmsg though.
My laptop is in a mess right now and i have jellybean source synced by mistake over night. Now i gotta go back to ICS and it will again take a day to sync as the net is crappy here.
I got a ramdisk hack for you when I get home to enable very early adb. If I had the DX I would do it for you guys, but I'll help where I can. Don't be afraid to pm me if you need to.
Sent from my HTC One X+ using Tapatalk 2
Lloir said:
I got a ramdisk hack for you when I get home to enable very early adb. If I had the DX I would do it for you guys, but I'll help where I can. Don't be afraid to pm me if you need to.
Sent from my HTC One X+ using Tapatalk 2
Click to expand...
Click to collapse
Tell me, should I use pre built kernel or use HTC provided sources?
Hello !
In Tutorial about compile AOSP GB i see one think. When I write in terminal lunch i have list devices which i can compile. So I am in trouble becouse i don't know how can i add My device. I Download Source GB to my device but I have external folder, bionic and probably hardware (and kernel) So My Question is - How can I Add My phone to compile list, to compile flashable zip work?:fingers-crossed:
cheqolada said:
Hello !
In Tutorial about compile AOSP GB i see one think. When I write in terminal lunch i have list devices which i can compile. So I am in trouble becouse i don't know how can i add My device. I Download Source GB to my device but I have external folder, bionic and probably hardware (and kernel) So My Question is - How can I Add My phone to compile list, to compile flashable zip work?:fingers-crossed:
Click to expand...
Click to collapse
What is your device?
Sent from my GT-I9100 using xda app-developers app
xSkArx said:
What is your device?
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Alcatel Ot - 908 / T-Mobile Move.
Im trying using latest cm10.1 source to compile the latest cm10.1 for my old phone...i use this tutorial http://forum.xda-developers.com/showthread.php?t=1971645 and an old dev device tree that haves some bugs but at least it compiled for him properly...
First of all when i type
Code:
$ gedit ~/paranoid/.repo/local_manifest.xml
im getting after a while an error with term.apk and it stops..i can't do anything so i keep up... and i type
Code:
$ brunch u8800pro(my device)
after 10-15 minutes im getting this
Code:
make: * [/home/pikachukaki/cm10.1/out/target/product/u8800pro/obj/SHARED_LIBRARIES/libOmxVdec_intermediates/src/omx_vdec.o] Error 1
always this error!!
and it stops completly...i sync the repo again...nothing....i delete the out folder and try again...nothing...im not very experianced with developing..this is my 1st test complety rom compile...anyone can help thanks!!
fatal: remove-project element specifies non-existent project: CyanogenMod/hardware/qcom/display
at least to this??anyone?
u might have a bigger error then that
mostly it says it above
post 8/15 lines of above the error her also
Sent from my S500 using xda app-developers app
SpaceCaker said:
u might have a bigger error then that
mostly it says it above
post 8/15 lines of above the error her also
Sent from my S500 using xda app-developers app
Click to expand...
Click to collapse
At least an answer...i manage to pass the 2nd post error by fixing local_manifest.xml
but im still getting the error 1 now...in another cpp..i repo sync again...i will post entire log after getting the error again!!!
Whats the difference between git://github.com/CyanogenMod/android.git -b cm-10.1 and git://github.com/CyanogenMod/android.git -b jellybean???
pikachukaki said:
Whats the difference between git://github.com/CyanogenMod/android.git -b cm-10.1 and git://github.com/CyanogenMod/android.git -b jellybean???
Click to expand...
Click to collapse
jellybean is JB 4.1.2 and cm10.1 is cm10.1 4.2.2
Sent from my S500 using xda app-developers app
SpaceCaker said:
jellybean is JB 4.1.2 and cm10.1 is cm10.1 4.2.2
Sent from my S500 using xda app-developers app
Click to expand...
Click to collapse
Thanks i found another tutorial that uses first this command
lunch cm_devicename-userdebug
and then
make otapackage
That seems to make it through my errors...i dont know the difference between this and brunch...but it seems it work....
As you can think i dont have enought knowlage over coding and programming...i study only about the hardware...i wanna ask something if you don't mind...where the compile procedure find the kernel (boot.img) i dont see the kernel source inside my device tree...only a raw file called kernel!!!
pikachukaki said:
Thanks i found another tutorial that uses first this command
lunch cm_devicename-userdebug
and then
make otapackage
That seems to make it through my errors...i dont know the difference between this and brunch...but it seems it work....
As you can think i dont have enought knowlage over coding and programming...i study only about the hardware...i wanna ask something if you don't mind...where the compile procedure find the kernel (boot.img) i dont see the kernel source inside my device tree...only a raw file called kernel!!!
Click to expand...
Click to collapse
if u do this
. build/envsetup.sh
then it loads all devices
and then do
lunch
then u can see a list of wich devices are available
type the numbe of ur device and it selects it
thwn do make -j6 bacon
thata how i do build
as for kernel
it can be a prebuilt kernel
wich will be using some parts of system/core
Sent from my S500 using xda app-developers app
SpaceCaker said:
if u do this
. build/envsetup.sh
then it loads all devices
and then do
lunch
then u can see a list of wich devices are available
type the numbe of ur device and it selects it
thwn do make -j6 bacon
thata how i do build
as for kernel
it can be a prebuilt kernel
wich will be using some parts of system/core
Sent from my S500 using xda app-developers app
Click to expand...
Click to collapse
The point is that it compiling all this time...its slow as hell too many cpp's but what can you do...
About the kernel so maybe the rom isn't bootable after this...maybe i have to replace it with a working 4.2.2 boot.img after this!!!
pikachukaki said:
The point is that it compiling all this time...its slow as hell too many cpp's but what can you do...
About the kernel so maybe the rom isn't bootable after this...maybe i have to replace it with a working 4.2.2 boot.img after this!!!
Click to expand...
Click to collapse
jup
also it can take sometimes up to 24 hour to a complete build
i so happen to use VMware soi can pause stop mine always
Sent from my S500 using xda app-developers app
SpaceCaker said:
jup
also it can take sometimes up to 24 hour to a complete build
i so happen to use VMware soi can pause stop mine always
Sent from my S500 using xda app-developers app
Click to expand...
Click to collapse
No vmware was extremly slow to do other things too so i install ubuntu on a 2nd hard drive...24hours...omg!!
for nightlies i have to do the same again??
Code:
. build/envsetup.sh
lunch cm_devicename-userdebug
make otapackage
pikachukaki said:
No vmware was extremly slow to do other things too so i install ubuntu on a 2nd hard drive...24hours...omg!!
for nightlies i have to do the same again??
Code:
. build/envsetup.sh
lunch cm_devicename-userdebug
make otapackage
Click to expand...
Click to collapse
yeah sure
my total compile time is 8 hours
i use linux mint + gnome classic no effects
also the time depends on how much ram and cpu u have + if u have installed ccache
Sent from my S500 using xda app-developers app
SpaceCaker said:
yeah sure
my total compile time is 8 hours
i use linux mint + gnome classic no effects
also the time depends on how much ram and cpu u have + if u have installed ccache
Sent from my S500 using xda app-developers app
Click to expand...
Click to collapse
Nop i don't run the ccache command...phenom x4 with 4GB ram...its ok..my point was to learn now i found a proper device tree...its ok if it takes time..and also to help the community of my olderst phone that have no dev support at all!!!