are there any modifications needed to Lox's Proprietary files to compile android source for the cdma hero?
Anybody know this?
Wish I could give you an answer -- never tried it myself though.
I keep getting errors on line 22 in a make file. I don't remember the exact error and am posting on my hero right now. If I figure this out ill post back.
Related
Hi Guys
I have tried to put together my own config files for the sapphire, these go in the vendor/htc/sapphire directory after you have extracted the source
by no means are they perfect but i hope they will start some fresh development.
http://www.cminion.com/wordpress/2009/08/11/rolling-your-own-android-rom-for-htc-magic-sapphire/
If something doesnt work, or anyone manages to perfect them let me know so I can repost.
please let me know how you get on
Nice work!
Did you try this for a 32A or 32B board?
Looks interesting... anyone tried this for 32A since 32B don't have this issue in the first place?
I have a 32b and someone is testing it with 32a but we are having trouble compiling today its been fine in the past
cminion said:
I have a 32b and someone is testing it with 32a but we are having trouble compiling today its been fine in the past
Click to expand...
Click to collapse
Well keep us updated if you get anything working for 32A since all of 32A users are stuck with the htc kerel... if you need someone else to test you can pm =D
I've been trying my best at building a kernel for 32A, but no matter what I do it doesn't boot at all.
Does anyone know how you can debug a kernel the kernel's boot process at all? I just get hangs or reboots from any of the kernels I build and I've no idea what is missing or where it's going wrong. If it gave some sort of output then I might be able to figure out what I'm doing wrong! (adb logcat doesn't kick in until AFTER it's booted unfortunately)
How have the 32b users gone with this? Anyone managed to boot one?
cminion said:
Hi Guys
I have tried to put together my own config files for the sapphire, these go in the vendor/htc/sapphire directory after you have extracted the source
by no means are they perfect but i hope they will start some fresh development.
http://www.cminion.com/wordpress/2009/08/11/rolling-your-own-android-rom-for-htc-magic-sapphire/
If something doesnt work, or anyone manages to perfect them let me know so I can repost.
please let me know how you get on
Click to expand...
Click to collapse
Hey, just saw your post and I'm taking a look. So far it's OK, but I think you're missing (at least) the keypad files. Also, a little legal note (in case you didn't know), you aren't legally able to pack the qualcomm libraries on the proprietary/ folder. Not that I really care about it, but I thought you should know since maybe you're going against xda rules by posting copyrighted files -not sure anyway-. Maybe it's better if you leave the propietary folder empty (or just with the minimal stuff like the keymaps, audioparametters and .ini files) and let the extract-files script do the job for whoever uses it to compile. After all, if someone uses this, he already has the libraries on the phone
Anyway, I'm going to compile, if I see something else missing, I'll modify accordingly and send you the changes made, ok?
Regards!
PS: Nice work
EDIT: Okay, I did some little changes on the board file definitions,renamed the folder to sapphire-open (to match dream-open added the keymaps, and a kernel & wlan.ko I had laying around (it's still compiling so maybe the kernel doesn't start, but it still needs an hour or so to end the build, but so far, it's not failing). I have packed it, you can get it here: http://rapidshare.com/files/266633357/sapphire_config.tar
If I see something else I'll repost
I hate to make a thread on this but would like to get started soon with learning how to root roms and add the kernel for multitouch and tethering. This is more for my personal use since I just want a stock rom with all the root benefits like jf use to and theses are the questions I have.
1. Will I have to take the update.zip file and extract everything and modify it then resign and I'm done?
2. I read some info on adding busybox and root which seem easy but when I run the chmod command and such everything will be through adb and the files will be on my pc so do I just make sure its all in the right directory and file path?
3. Where are the wallpapers stored in builds along with animations I will be looking into the framwork/framework-res.apk later but still curious
4. The modified kernel for tethering and multitouch is located where along with the market.db file?
5. What is meta.inf and how easy is it to make the cpu 528mhz standard also not sure what BFS and ASOP are haven't been keeping up.
P.S. I would really appreciate some help on this and I don't mind reading if this information is somewhere else so please provide a link and as always gotta show love to those who started this like JF, Hakuro, Cyanogen, Drizzy, and many more like daproy and kornub did a lot of helping.
I hate to make a thread on this
Click to expand...
Click to collapse
You mean you hate starting threads in the correct place?
Thats a fine line here. Although it is a question, it is specifically a development question. Its not a which rom do i choose?
Although android is "open source" these people dont give a **** about people trying to learn how to develop. They will pull the google line or something.
yeah me 2
Trying 2 learn
Im a noob, so I can only answer two of thosew questions
1. Anytime you modify your update.zip you will have to resign before trying to flash it onyour device.
5b. BFS: Brain **** (simple) Scheduler, something to do with the priority of running proccesses or something http://en.wikipedia.org/wiki/Brain_Fuck_Scheduler. AOSP stands for Android Open Software Project, which i believe is just googles standard rom really (but I may be wrong)
I recommend you try out this rom though, kind of like JF but for Donut http://forum.xda-developers.com/showthread.php?t=538456
Very Sorry, double post
Thanks! I'm actually using that rom and its what has me so interested in this cause I hate having to flash another update.zip to get the full root benefits when JF just made everything available in one nice package but looks like I will just have to go through trial an error unless I get some more feedback cause switching between cyan 4.1.11.1 and JF1..51 is killing me and taking up space on my card.
With my little to no knowledge, replacing the boot.img and some files in system/bin with the ones provided in theofficial expansion pack should give you all that you need. With no extra apps.
yeah me 2
Yeah me too
Can anyone provide me some reference or guide on how to compile the ROM for tf101 from Paulburton's ICS source.
rajkumard said:
Can anyone provide me some reference or guide on how to compile the ROM for tf101 from Paulburton's ICS source.
Click to expand...
Click to collapse
Check his website for repo information. Beyond that, its no different than compiling any rom from source.
You should know that you probably will not get anything different than what he has released thus far, that is, unless you have coded your own changes.
Thanks, I will check the link. I believe he has few bug fixes which I need, that's the reason why I wanted to compile it.
rajkumard said:
Thanks, I will check the link. I believe he has few bug fixes which I need, that's the reason why I wanted to compile it.
Click to expand...
Click to collapse
Understood. I do know that Paul is neck deep with finals, and other school stuff, so there is no harm in running a compile yourself. I just wanted to make sure you knew what to expect. His repo sync is a tad different from other instructions, i.e. CyanogenMod...but once you get it all pulled down, its essentially the same steps for the compile portion.
Actually I am new to this. All these days I have been only using the ROM's and never tried to compile one. This is my first time and I appreciate your help. The link really helper, I have started syncing the repo, looks like it's going to be a while. I will post if I run into any issues.
rajkumard said:
Actually I am new to this. All these days I have been only using the ROM's and never tried to compile one. This is my first time and I appreciate your help. The link really helper, I have started syncing the repo, looks like it's going to be a while. I will post if I run into any issues.
Click to expand...
Click to collapse
I will tell you this...use ccache, its a huge time saver when you need to rebuild after making changes. Also...dedicated build system really is recommended, and without question, the more juice its got, the better.
Here are a couple of links...including a kernel specific one from CyanogenMod's wiki. I use both when I am bored and just want to compile something
Yet Another Tutorial on Building Android from Sources
Building Kernel from Source
Compiling ICS from Source
Hope these help!
http://source.android.com/source/initializing.html
http://wiki.cyanogenmod.com/wiki/Building_from_source
You will probably need these... be sure to cross reference the CM website against the google one. There are a few differences.
Thank you for the links. I got a spare machine and am thinking it is about time I did something productive with it.
Thanks for all the links, I was using one of the links that you have provided. It had the with step by step instruction. I followed it, most of the things went fine and some issues I was able to resolve. Now when try to build the rom using the make command I get the following error. I am doing the sync again to see if it resolves. I will try it out tomorrow. Meanwhile if any of you have any suggestions please let me know. btw I have tried the solution provided in one of the xda thread (repo sync -f) already and it did not resolve.
ERROR:
cts/apps/CtsVerifier/lib/colorchecker/Android.mk:22: external/stlport/libstlport.mk: No such file or directory
make: *** No rule to make target `external/stlport/libstlport.mk'. Stop.
rajkumard said:
Thanks for all the links, I was using one of the links that you have provided. It had the with step by step instruction. I followed it, most of the things went fine and some issues I was able to resolve. Now when try to build the rom using the make command I get the following error. I am doing the sync again to see if it resolves. I will try it out tomorrow. Meanwhile if any of you have any suggestions please let me know. btw I have tried the solution provided in one of the xda thread (repo sync -f) already and it did not resolve.
ERROR:
cts/apps/CtsVerifier/lib/colorchecker/Android.mk:22: external/stlport/libstlport.mk: No such file or directory
make: *** No rule to make target `external/stlport/libstlport.mk'. Stop.
Click to expand...
Click to collapse
The obvious question would be does the folder/file exist?
Code:
$ ls external/stlport/libstlport.mk
external/stlport/libstlport.mk
If it is...type 'env' at your command prompt and see what environment variables are set to see if the external folder should be seen.
Re-run 'source ./build/envsetup.sh', then 'lunch' and choose the tf101-userdebug (or what ever Paul uses now) option listed after running lunch.
See if that helps.
I'm repo sync'ing now- gosh, it takes longer to sync than it does to build. I still have to clone the kernel. I think it's been downloading for 2 hours!
I've actually never flashed this ROM, but that won't stop me from building it
Thanks gVibeR. The external folder exist but the 'stlport' folder does not exist. And I also did not see any option with 'tf101' in it when I run 'lunch'. I tried re-syncing the repo but i ran into out of space error. I did not know where to delete all the earlier repo downloads. This was a brand new Ubuntu installed with 25gig disk space. I will keep looking and let know if I had any luck.
rajkumard said:
Thanks gVibeR. The external folder exist but the 'stlport' folder does not exist. And I also did not see any option with 'tf101' in it when I run 'lunch'. I tried re-syncing the repo but i ran into out of space error. I did not know where to delete all the earlier repo downloads. This was a brand new Ubuntu installed with 25gig disk space. I will keep looking and let know if I had any luck.
Click to expand...
Click to collapse
I think you'll need more space than that - once you start building, the directory will swell to over 20gb. For comparison, andromadus(ICS) for the vision is 21g and CM7 (GB) is 18gb.
I'm still downloading, but spark source is at least 11gb and that doesn't include the kernel or the out directory, which will fill up after building.
I think you will need at least 25gb for the build plus whatever for ubuntu. If you are hard up for space, you can install one of the server versions of ubuntu, which doesn't include the GUI (~1.5gb).
The repo files are stored in .repo, which will be hidden. Use ls -a to see it, although I think it manages and discards old commits.
Thanks gee one, I have more than enough space, just thought 25gig should be fine. I will install Ubuntu again with more space and give it a try. Let me know how it goes for you, please post if you got any issues and resolved it.
alright im trying to build aosp for the p505. i have a ubuntu 10.04 build environment set up, adb working, and some knowledge with repo and git. though nothing to brag about.
my problem is trying to get the prop files for lgp505 gingerbead. i dont know what files to pull from stock, or how to make the make files, let alone how to put them into the device folder correctly. then theres the manifest.xml that i dont quite understand.
if anyone would give me some pointers or point me towards a guide that would be greatly appreciated.
thanks.
savagephoenix said:
alright im trying to build aosp for the p505. i have a ubuntu 10.04 build environment set up, adb working, and some knowledge with repo and git. though nothing to brag about.
my problem is trying to get the prop files for lgp505 gingerbead. i dont know what files to pull from stock, or how to make the make files, let alone how to put them into the device folder correctly. then theres the manifest.xml that i dont quite understand.
if anyone would give me some pointers or point me towards a guide that would be greatly appreciated.
thanks.
Click to expand...
Click to collapse
With basic knowledge its gonna be hard to build aosp for your device. What ver of aosp? 2.3.7?
Remember it is required to have a x64 operating system for build aosp onward from froyo. Try compiling cm7 a couple times then move towards aosp. Cm7 will help a lot ! I know from experience
it is 64bit. yes 2.3.7, yes i plan to try cm7 also...
still need to get prop files for my device in the gingerbread branch.
thanks
111 views and not a one can atleast point me in a direction, or tell me im off my rocker.
a book , a guide... something that would help. please...
maybe this thread being moved will help... not holding my breath though...
My Nexus has problems connecting over bluetooth to my Car (BMW). I've found a lot of references to similair problems, and also a hint which suggests a change that could solve the problem. The hint can be found on the cyanogem forum in posting 77834, "bluetooth-connection-drops-kar-kit-bmw" (I cannot post links here).
I am running stock KitKat, and for the moment want to keep it that way. So, I decided to try the same patch on KitKat. I've managed to setup a development image in a VM, but keep running into problems compiling - my machine lacks resources (diskspace) to complete a complete build. I do not need a complete build; I need just 1 file, bluetooth.default.so, compiled. My development skills are VERY rusty, and I cannot find out how to build only this file.
I've applied the patch to external/bluetooth/bluedroid/bta/ag/bta_ag_sdp.c, run a make on the Makefile here etc - but, still no luck. The most frustrating bit is that I'm sure this is trivial, but it has been such a long time since I did any development work that I cannot seem to find a way to compile.
Can someone help me out here with hints on how to build the .so? I need bluetoot.default.so, build from the files in the external/.../ag directory, to be situated in system/lib/hw on the android system.
You put a Q in the title yet still posted in the wrong place. Please be more careful about where you post. General is not for questions. Q&A is for questions