Stuck while building - Android Q&A, Help & Troubleshooting

Ok. I know this is nooby but I don't have anyone else to ask. I am trying to build Android 4.4 Kit Kat for the HTC Flyer. I followed a guide. I installed all the packages, installed the repo downloaded the source code but after that it said that i need to clone my device tree from github. I googled HTC flyer github but i only found a branch of a kernel from doomlord and i don't think that's what I am looking for. Now I am stuck and don't know what to do. So basicly I don't what to after downloading the source code using repo sync.
Any sort of help would be appretiated. I am just trying to bring my device back from the dead. Thank you and again sorry for the nooby question.

Related

[Q] AOSP Build. I need help. Yes I am a complete noob.

Okay, so I am a complete noob when it comes to this. I understand what it means, I have downloaded the source code for my device as well as the source provided by google.
My device is the Epic 4G Touch, and I was wondering where I would start in order to build android from source with my device.
I set up my working directory and performed the repo sync to have the google source up to date, I then downloaded the samsung source for my device (SPH-D710) which came with both kernel and platform files, however I am at a loss as to what comes next. I
assume I need some sort of programming language but I am not sure. Am I over ambitious? did I miss an obvious step?

Forking and porting CM7 to an unsupported device? (Gio GT-S5660M)

Hello,
So far, I have:
A working Android build environment (Ubuntu 11.10 x64).
Managed to build, install and boot AOSP on my Nexus S. (I have downloaded but not attempted to build CM7 yet.)
Created a Github account.
Samsung's open source files for my target device, the Galaxy Gio GT-S5660M.
I've read some documentation and forum posts about Github, but I remain unsure as to what I should do to fork in a way that:
I'll be able to keep on syncing the remainder of the code.
My new device directories and modifications could be brought back (pulled?) to the main CM7 code base.
Will avoid needless frustrating re-downloads of the source code.
Thanks in advance,
Darkshado
After some further reading, I'm beginning to grasp some git basics...
I've forked two CM7 repos so far, added them as remotes in the appropriate installations. (Instead of forking and cloning, since I already had repo sync'ed the whole CM7 source. My commits show up on Github like they should, and I should be able to merge in commits to the origin remotes.)
I'm not going to do any pull requests until I've managed to build and boot.
By the way, yesterday I attempted to build AOSP with a bunch of files overwritten by the Samsung sources (that's how they tell you to do it!!) and this failed, as I expected.
Goodbye,
Darkshado
Update: I'm currently trying to port CM7 to the Gio 5660M. Still attempting a first successful build as I'm writing these lines.
My main issue so far has to do with the camera. I get the following error message:
make: *** No rule to make target « out/target/product/gio5660M/obj/lib/libcamera.so », needed by « out/target/product/gio5660M/obj/SHARED_LIBRARIES/libcameraservice_intermediates/LINKED/libcameraservice.so ». Stop.
After toggling off the camera by using the stub, I hit the same error further into the build with this:
make: *** No rule to make target « vendor/samsung/gio5660M/proprietary/wifi/ath6k/AR6003/hw2.0/athtcmd_ram.bin », needed by « out/target/product/gio5660M/system/wifi/ath6k/AR6003/hw2.0/athtcmd_ram.bin ». Stop.
I know this has to do with makefiles, but that's about it...
Thanks in advance for any help,
Darkshado
hi i'm interested too.
hi I found your github because I also interested poriting cyanogemod to galaxy gio korea(SHW-M290K). the device hardware is different from s5660. so I need some modification.
and your libcamera problem is that there is some reason that the make system can't find libcamera.so, so they cannot compile libcamera service. it should be in ./vendor/samsung/gio/proprietary according to your extract-files.sh .
have one cuorisity. I searched gio android device make file. and none of them are relreased source code. how did you make them?
I found this information. it may help you.
http://processors.wiki.ti.com/index.php/TI-Android-GingerBread-2.3.4-DevKit-2.1_PortingGuides
I'll have to update my Github, hadn't been in a rush due to lack of progress, but now my problem lies with libaudio instead.
I got the Samsung sources for the 5660M on their open source website, although I mostly worked with the CM7 ports for similar devices like Tass and Cooper as well as a Gio source provided by Phiexz but it didn't build either.
Thanks for the link, I'll check it out.
proprietary does not help
do you have any progress since last time?
well, I admit that proprietary files does not help.
does your s5660m hardware identical to s5660v?
becasuse galaxy gio in Korea(shw-m290k,shw-m290s) does different hardware.
well in this case, like me, you need to hack into not only android pdk, but also android kenel.
I have seen that phiexz has released kernel with latest cyanogenmod kenel in his github and I am modifing it to shw-m290k. there are some hardware differences i have to apply to.
I suggest you to compare phiexz's kernel and samsung original kernel from samsung opensource homepage.
My problem right now is that I don't have that much spare time to put into this, and that I'm very much learning as I go, so progress is not always that quick. Also, I'd like to get my Touchwiz based ROM updated and working properly before trying to build AOSP or CM again.
Another thing I want to try is building the kernel (probably based on Phiexz's) that will support ext4, and compare performance of the Touchwiz ROM on ext4 versus RFS.
As far as we can tell, GT-S5660 (Europe/Asia) GT-S5660M, L and V are identical except for the radio firmware. People with the 5660M initially encountered issues after flashing 5660 ROMs because they also contained the AMSS image.
my cyanogen kernel is based on samsung open source kernel
because cm-kernel on cyanogenmod github dont support our device, if we wnt use that kernel we must add some hardware pofile & board for galaxy gio
so alternative is make samsung's open source kernel compatible with cyanogenmod
Wouldn't it be much better from a code maintainability standpoint to make the CM kernel work on the Gio? (Also if you ever hope to get official CM team support, that's a given.)
The way I understand repo and git, you could create a github repo for your device and board configs and add those to your repo manifest so the whole CM7 source and your modifications all sync properly.
I've forked the CM7 manifest files off github, added my gio files and removed all those extra devices I didn't need, so my repo syncs are much faster too. (The idea comes from http://slightlymorethanworthless.blogspot.com/2011/05/remove-unwanted-devices-from.html)
hey a quick question...
just starting out here..
i'm on win7 32 bit, going to run ubuntu on virtualbox.
shud i choose ubuntu 32 bit or 64?
sorry for OT.
doesn't really matter
roofrider said:
hey a quick question...
just starting out here..
i'm on win7 32 bit, going to run ubuntu on virtualbox.
shud u choose ubuntu 32 bit or 64?
sorry for OT.
Click to expand...
Click to collapse
doesn't really matter. but compiling process needs much cpu power. so 64x would be better.
Well, im not a dev or a user of gt5660m, but good luck to you, hope u can finally port it
Sent from the GUN in my pants
darkshado, if you have same problem untill now.
http://strazzere.com/blog/?p=220
look this page. and check out koush's proprietary page. especially for samsung cooper(galaxy ace). because many of kernel procedure are same for gio.
https://github.com/coolya/android_device_samsung_cooper.git
https://github.com/koush/proprietary_vendor_samsung
i've upload galaxy gio source + proprietary files for galaxy gio
please see & help to fix some problem
github.com/phiexz
Darkshado said:
Hello,
So far, I have:
A working Android build environment (Ubuntu 11.10 x64).
Managed to build, install and boot AOSP on my Nexus S. (I have downloaded but not attempted to build CM7 yet.)
Created a Github account.
Samsung's open source files for my target device, the Galaxy Gio GT-S5660M.
I've read some documentation and forum posts about Github, but I remain unsure as to what I should do to fork in a way that:
I'll be able to keep on syncing the remainder of the code.
My new device directories and modifications could be brought back (pulled?) to the main CM7 code base.
Will avoid needless frustrating re-downloads of the source code.
Thanks in advance,
Darkshado
Click to expand...
Click to collapse
Really the best kernel for your phone is here:
http://forum.xda-developers.com/showthread.php?t=1991020
BLN enabled, optimized&stable kernel, jelly bean look
Whoa! Zombie thread!
Dude: the ROM you linked was published over a year after my original post in this thread. I'm pretty sure there was NO CM7 build available for the Gio back then. That's what I was trying to work on, but got beat to the punch by Maclaw and a couple others. (Hard-bricking my Gio and having a sluggish laptop to build on didn't help.)
Besides, I got rid of my Gio a long time ago. I enjoy my Note 2 and keep my Nexus S as backup.

[Q] Building CM11

I'm trying to build CM11 for LG L9 P760.
I tried following some of the tutorials and reached the point where I synced the CM11 repo.
I've also pulled the device tree to vendor/lge/p760 from a git and used extract_files.sh to get the files from device.
But I don't know where to go from here. I tried brunch p760 and got the following output.
http://paste.ubuntu.com/6626112/
There is an error towards the end.
I am also confused whether to add the kernel source, and if i have to, where and how i have to add it.
It'd be really great if you guys could help.
thanks.
Thanks
Thanks Master

[ROM][Porting] guide to cm11

Hello everybody. i serached the net a bit and found this guide on how to port CM11 to our devices
http://wiki.cyanogenmod.org/w/Doc:_porting_intro
my phone is still on service (two weeks now )
but i thought before i get it back if someone wanted to try to make it happen.
i wouldnt say im that much of a developer so i think theres people out there that can make this happen faster than me.
anyway i thought to start this thread so people can try it out and talk about what we have to do and help people out with the progression.
Help appreciate
invaderjohn said:
guide on how to port CM11 to our devices
http://wiki.cyanogenmod.org/w/Doc:_porting_intro
if someone wanted to try to make it happen.
i wouldnt say im that much of a developer
Click to expand...
Click to collapse
Any help is greatly appreciated!
I have set up a ubuntu box and got the cm sources.
I followed the instructions to build the device files from boot.img
Tweaked the BoardConfig.mk and can build recoverys from source now using the stock kernel.
Only problem with this is the 'dtb' part of the recovery.img.
I use Android Image Kitchen to copy the original recovery dtb to the ones i have build.
[Q]Can anyone tell me how to build dtb in the recovery at build time?
I have downloaded the android and kernel source from LG for D620.
Source from LG
[Q] Can anyone tell me how to merge them with the CM source?
In general i need some help to build the kernel from source, the instructions in the LG source don't work for me.
Zaaap
Zaaap72 said:
Any help is greatly appreciated!
I have set up a ubuntu box and got the cm sources.
I followed the instructions to build the device files from boot.img
Tweaked the BoardConfig.mk and can build recoverys from source now using the stock kernel.
Only problem with this is the 'dtb' part of the recovery.img.
I use Android Image Kitchen to copy the original recovery dtb to the ones i have build.
[Q]Can anyone tell me how to build dtb in the recovery at build time?
I have downloaded the android and kernel source from LG for D620.
https://www.lg.com/global/support/opensource/opensourceList?types=NAME&search=d620
[Q] Can anyone tell me how to merge them with the CM source?
In general i need some help to build the kernel from source, the instructions in the LG source don't work for me.
Zaaap
Click to expand...
Click to collapse
is this any help for you?
http://forum.xda-developers.com/showthread.php?t=1748297
and perhaps you can find a solution on the dtb here?
http://forum.xda-developers.com/showthread.php?t=2428117
Hi guys,
I bought this device a week ago, highly impressed with it.I'm not interested in tweeking it yet as I'm trying to get my lg o3d also a working cm11.I do follow this forum all the time and also leading as I mess around with my old phone, but if I know something I would try to help. To add sources to cm try this guide, its most recent and very helpful.
http://forum.xda-developers.com/showthread.php?t=2814763
:thumbup:
Sent from my GT-i8190 using XDA Free mobile app

[help]getting device tree for new devices for cyanogenmod builds

Hello Everyone!
I had started building Cyanogenmod-11.0:angel: from source.I had sucessfully completed the repo sync and now searching for getting device tree but my device haven't had any builds at so finally I've found this Cyanogenmod porting guide.
Code:
https://wiki.cyanogenmod.org/w/Doc:_porting_intro[/URL]
I'am trying this guide to get device tree out my device.
Now, I've been trying Method-1 you can see image of method I'am using from attachments.
But I get errors can anyone help me.
https://wiki.cyanogenmod.org/w/Doc:_porting_intro

Categories

Resources