[Q] Compiling KA6 source succesfully but lib file is not working.. - Vibrant Q&A, Help & Troubleshooting

Hi, i need help from the developers who were able to compile a working rom from Samsung Froyo code for the Vibrant.
First of all i don't want a full working ROM, all i need is just to add the Arabic language support to the libwebcore.so. So before doing anychanges to the code I wanted to compile the original and replace the original libwebcore.so with mine to see if it works, then I will modify the code and add the language support.
So i got the source code (KA6) and i copied it over the android code (i used 2.2_r1 since Samsung told that it is what they used for the Vibrant)
For 'lunch' i selected "passion" which is for Nexus One since I don't know how I can add the Vibrant to the list or if it will make any difference in my case, since I don't need the whole ROM and I don't care about the drivers (correct me if i am wrong).
The compilation was successful, however when i swapped the libwebcore.so in my vibrant with the compiled one the browser window opens for a second or so and then closes (no Force close message)
The file size of the original libwebcore file is 5187072 but mine is 5187064 (also another user who compiled the source got the same size as mine)
I tried to use libwebcore.so files from a number of the leaked Samsung ROMs (JL5, KA6, KA7) and they all have the same size and they all work fine.
Am I missing something? or doing something wrong?
Kindly see the attached log file (I started logging just before opening the browser)

Moved of: Samsung Vibrant > Vibrant Android Development
To: Samsung Vibrant > Vibrant Q&A
Please put your questions to: Vibrant Q&A

Having this development related question under Q&A means it will never get answered by the developers
I think I will need to contact the vibrant developers and direct them to this thread.

Updates:
After asking for help from many developers and on IRC channels, I got a help from a #cyanogenmod-dev user <ius> who pointed me to the missing method HttpEquivhandle" which I found to be included in a pre-compiled file libsecwebcore.a (binary) without the source code. The files is already their with samsung code, and it get linked (or merged) to the libwebcore.so during compiling, but I am not sure why it is still complaining about not finding it.

Related

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.

samsung galaxy pocket gt-s5300 build from source

i own samsung galaxy pocket gt-s5300, its like galaxy Y little brother. And i'm trying to build from source.
i'm new in this stuff, so i can't elaborate enough to find solution myself.
i've downloaded the samsung source for this device from samsung website, when extracted it has 2 sources, platform and kernel.
im trying to build the platform and hopefully can build the stock rom successfully so i can proceed to modification.
already followed the instructions to get the gingerbread 2.3.6 from aosp, merge the folders from samsung to aosp, and execute build script (generic-user). seems fine, i got system.img,userdata.img,etc but no boot.img, still tried to flash anyway and figured that this device doesn't support fastboot but adb works. then i tried to make otapackage but got no rule error. perhaps caused by this generic-user lunch, but i dont know how to add this device to build, because there's only generic,emulator,crespo-4g, and crespo choices.
trying to find alternatives, and thinking about modify the stock rom with my build, so i also tried to open the odin flashable stock rom with winrar (xxx.tar.md5) which i cant, i dont know why since the other galaxy rom has no problem.
so many thing i'm not sure of doing it right, so i need help building for this samsung device from source.
bLusiLv said:
i own samsung galaxy pocket gt-s5300, its like galaxy Y little brother. And i'm trying to build from source.
i'm new in this stuff, so i can't elaborate enough to find solution myself.
i've downloaded the samsung source for this device from samsung website, when extracted it has 2 sources, platform and kernel.
im trying to build the platform and hopefully can build the stock rom successfully so i can proceed to modification.
already followed the instructions to get the gingerbread 2.3.6 from aosp, merge the folders from samsung to aosp, and execute build script (generic-user). seems fine, i got system.img,userdata.img,etc but no boot.img, still tried to flash anyway and figured that this device doesn't support fastboot but adb works. then i tried to make otapackage but got no rule error. perhaps caused by this generic-user lunch, but i dont know how to add this device to build, because there's only generic,emulator,crespo-4g, and crespo choices.
trying to find alternatives, and thinking about modify the stock rom with my build, so i also tried to open the odin flashable stock rom with winrar (xxx.tar.md5) which i cant, i dont know why since the other galaxy rom has no problem.
so many thing i'm not sure of doing it right, so i need help building for this samsung device from source.
Click to expand...
Click to collapse
I try to do it but i still make a lot of tweaks on my Rom I need to make good performance to my phone

[Q] GT-i9300 - Problems with building CM10.1

Hey,
first excuse me when this is the wrong section :-x
But since it might be a general problem which is not related to the Device, I thought I might should post it here.
Just a week ago I bought a new Laptop and moved all my (windows) stuff over there.
Since Im a programmer for C# and C++ for over 5 years now, I installed Ubuntu 12.10 on my Old Laptop and wanted to start messing with Android, CyanogenMod 10.1 to be specific.
But I came up with a few Problems and questions ...
I have a few questions regarding Building CM10.1 for the Samsung Galaxy S3 GT-I9300 (international) and some which might be general to building from Source.
Every time I close a Terminal window in Ubuntu 12.10 and open one again, I have to execute "envsetup.sh" all over again, to use the "croot" command or anything related to building. Is there a way to ( more or less ) integrate that into Ubuntu ?
Right now I got the CM10.1 Source tree located in the specified location the Wiki states. How do I cherry pick Changes from Gerrit effectively ? Sure, the easiest way would be to Copy&Paste the Code, but is there any way to keep the changes after "repo sync" and keep track of additional patch sets that have been added, which might be required ?
Like I said I have problems building CM10.1 for my (german) i9300. Booting is well, everything running like on the Nightlies, but the Radio is "missing", just like the IMEI and IMEI SV. Ive tried to google the issue but dont get anything clear, I also followed every point in their Wiki but dont get any further. How do I fix this ?
Whats the average time when you build CM10.1 ? Is about 1 1/2 Hours good ?
Again, Im sorry if this is the wrong section or anything I can find here, but I might searched for the wrong things and came up with Hundreds of Threads, none related to my issues ( related to building ).
Thank you in advance
v3n3 said:
Hey,
first excuse me when this is the wrong section :-x
But since it might be a general problem which is not related to the Device, I thought I might should post it here.
Just a week ago I bought a new Laptop and moved all my (windows) stuff over there.
Since Im a programmer for C# and C++ for over 5 years now, I installed Ubuntu 12.10 on my Old Laptop and wanted to start messing with Android, CyanogenMod 10.1 to be specific.
But I came up with a few Problems and questions ...
I have a few questions regarding Building CM10.1 for the Samsung Galaxy S3 GT-I9300 (international) and some which might be general to building from Source.
Every time I close a Terminal window in Ubuntu 12.10 and open one again, I have to execute "envsetup.sh" all over again, to use the "croot" command or anything related to building. Is there a way to ( more or less ) integrate that into Ubuntu ?
Right now I got the CM10.1 Source tree located in the specified location the Wiki states. How do I cherry pick Changes from Gerrit effectively ? Sure, the easiest way would be to Copy&Paste the Code, but is there any way to keep the changes after "repo sync" and keep track of additional patch sets that have been added, which might be required ?
Like I said I have problems building CM10.1 for my (german) i9300. Booting is well, everything running like on the Nightlies, but the Radio is "missing", just like the IMEI and IMEI SV. Ive tried to google the issue but dont get anything clear, I also followed every point in their Wiki but dont get any further. How do I fix this ?
Whats the average time when you build CM10.1 ? Is about 1 1/2 Hours good ?
Again, Im sorry if this is the wrong section or anything I can find here, but I might searched for the wrong things and came up with Hundreds of Threads, none related to my issues ( related to building ).
Thank you in advance
Click to expand...
Click to collapse
Answer's here
1)no you cant integrate that into ubuntu ..ps why do you need to integrate something which is just a line to type....
2)for cherry picking commits you can do git am or download the diff patch .. if you repo is frameworks base then copy that patch to frameworks/base cd into frameworks/base and type git patch -p1 and drag the dif patch on to the terminal and hit enter
3)u can use boardconfig flags to make use of stock radio, go through boardconfigs of different devices..
4)for me it takes 2hrs to build gb and 3-4 hours of ics..really i have a crap pc it depends on your processing power ..you could make use of make -j4 if you havent yet ..but it the build gets crashed reduce the number next to j like j3 or j2..

How do I develop an image for my Samsung Galaxy Note 3 from the Samsung Source Code?

I have a Samsung Galaxy Note 3 which I want to build an image for. I followed the procedures given by http://wiki.cyanogenmod.org/w/Build_for_hlte#Prepare_the_device-specific_code and I was able to compile it successfully. But I have an issue, and that is I need to patch the code to get additional functionality. The patch I need to apply is only available for Jelly Bean, and the Cyanogenmod procedures use Kitkat. I tried to manually apply the patch, and I had to remove a number of lines before the image compiled. But when I flash the phone with it, I get an error about NFC adapter. Basically the message says that NFC adapter is disabled. I think I know why it says that. The patch is for allowing extended functionality of NFC adapter, and well you know...It seems like either me or the patch broke the NFC adapter. Most likely it was me I tried to download the Jelly Bean version from Cyanogenmod repo, but the procedures explicitly say not to. And when I tried, I get a repo sync error and the whole thing does not download. So I am trying to do something different. I like to download the phone's source code from Samsung Source code. But that is just the kernel as I understand it. There is a lot of what Cyanogenmod people call "proprietary blob", which they provide a way to extract from the phone. So this is why I am where I am, and I am trying to mix the two together. Please tell me if there is a better way for me. And if not, then I like to know if it is possible for me to replace the Cyanogenmod source that I downloaded from Git repository with the Samsung Source and successfully compile it. I wish I could just download Cyanogenmod's version 10.5; I think they remove the previous version due to resource issues. I am not sure. I have to say Cyanogenmod rocks. My understanding is most developers there and here on this site are really busy. More power to you guys. You are really doing a big service for the open source community. Thank you all.
Thread moved to Q&A.

[Q] Deodexerant binary for 4.4.2

Good day fellow XDA citizens.
I'm in dire need of a usable deodexerant 4.4.2 binary for my device. I'm in the process of deodexing framework files but some files (namely core.odex, framework.odex, and framework2.odex) just refuse to deodex. Apparently my device has a non standard inline table (whatever that is) and some files will not deodex unless this non standard inline table has been extracted from my device using this deodexerant binary. I would like to give this a shot but with avaricious internet providers here it will take at least three weeks nonstop to download the full AOSP source. No kidding.
My phone is a MT6592 device running on Android 4.4.2. I hope someone will assist me regarding this matter, as the development for this specific device is just plain dry and I have to do the things I like to have in my phone all by myself.
If some sort of workaround is available or if there is someone I can PM to ask for assistance or if there is anything of help at all please feel free to reply in this thread.
P.S. Here is the README file I used as reference https://cells-source.cs.columbia.ed...759ef422e9f7cf4a08c80ac87f/deodexerant/README
Best regards
Ocenyx
After fooling around in Google for some more I found something peculiar and such is the case of my device. Classes.dex are already included in the apk and jar files I intended to deodex. It seems like the odex files present are duds.
As this dilemma seems to be not present in the first place, I'll leave this thread open as deodexerant binary might come in handy for future use.

Categories

Resources