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.
Hi all devs for P7510:
I'm following guides all over the place in my attempt to learn a thing or two by building AOSP ICS (specifically the 4.0.4_r1 branch) from source. I know that Google states building anything other than master on a version of Ubuntu higher than 11.10 is experimental and not really supported - seen many Google Groups threads indicating this. I've been able to patch and fix some of the errors that I'm seeing, but others that I'm searching for are answered with links back to the AOSP website where it's simply saying building anything other than the master branch on Ubuntu 12.xx is not officially supported.
I am getting ready to re-do my dev environment with Ubuntu 10.04 to see if that really does make a difference somehow, but had a couple of questions that I'm hoping someone can answer as I get ready to try again.
1) Has anyone out there built AOSP 4.0.4, from a branch other than master, successfully for the P7510 device?
2) If so, with what version of Ubuntu/Linux and were there many errors encountered when compiling that required fixes via manual code revision rather than simply applying a missing dependency or toolchain fix?
I've searched high and low and it's proving particularly difficult to find info on whether or not someone has been able to build a non-master branch of AOSP ICS 4.0.4 for this particular device. I know I could just abandon it and try to build JB or something instead but really want to see if I can pull this off. Hoping someone out there can help me out!
Update: I was able to complete a build today!! Please disregard the questions, self answered.
Sent from my GT-P7510 bleeding CM10 inverted awesome
Hello,
I want to develop an app for the Android OS but I am a total newbie and need some advice to get started.
What I want to do is study and add some extra features to the existing Android Open Source Project Contacts Manager (found in github: github.com/android/platform_packages_apps_contacts/tree/jb-release). I figured that reinventing the wheel is a bit stupid. I tried downloading the source code and creating a new android project from existing code in Eclipse. Unfortunately the code is full of references to classes that aren't there. I don't understand how this is possible when everything seems to be in order, the Google APIs are there including Android.jar.
Obviously I am doing something wrong or I have missed something, or maybe I am doing this totally wrong. Thanks in advance.
Okay so im trying to port over Firefox OS but im stuck at
Create a manifest for the new device
Now you need to add a manifest file for the new device. Refer to one of the existing manifests for a template. You can use the hamachi manifest a reference. Once done, you should add and commit your new manifest to your local b2g-manifest repository:
hamchi manifest -> https://github.com/mozilla-b2g/b2g-m...er/hamachi.xml
im not exactly sure what needs to be changed and what needs to be put in the areas that i do change the only other device ive did anything relative to this is ZTE Open C i also have a manifest for it several actually so im entirely ignorant but i am at a point of being dumbfounded on how to change this up so it can ./config.sh correctly
so my question is ... will someone help me create a proper manifest from the refrence manifest/point me to a manifest thats already created ive looked on google and havent found one so im asking you guys
thanks for all help its appreciated
Bump for Firefox goodness
Do you have android source for your device?
My understanding is that Firefox OS is basically built on top of an Android kernel with some of its libs and such so that device makers don't need to write new driver stacks. If you look at the hamachi manifest that you reference, it looks just like an android manifest and in fact refers to android's source repo as well as what looks like qualcomms android kernel source(codeaurora).
So start with a Android source tree for the LG G2 (that's your device right?).
Hello guys,
I hope I'm in the right forum.
I've studied several days, if it is possible to update my Smartbook S10 (smartbook.de/produktfeatures/72/technische-daten is the link from the manufacturer) from Android 4.4.2 to at least 7 (best case to the newest 9, that I'm trying atm).
It has got only 8GB of space, so I wanted to ask, if it's even possible with that low space and processor (RK3026)? Couldn't find clear information about this.
I've come that far, that I've created a new AOSP device tree and inserted all data I know/could find. But it fails now at the kernel.
I've tried to compile the common actual kernel 4.19 with Google's Android tools and getting this error:
Code:
/home/test/Android_Kernel/build/_setup_env.sh: line 28: /home/test/Android_Kernel/build.config: No such file or directory
My build repo lays at /home/test/Android_Pie. What am I missing or doing wrong?
Thanks in advance
Greetings
Andi448 said:
Hello guys,
I hope I'm in the right forum.
I've studied several days, if it is possible to update my Smartbook S10 (smartbook.de/produktfeatures/72/technische-daten is the link from the manufacturer) from Android 4.4.2 to at least 7 (best case to the newest 9, that I'm trying atm).
It has got only 8GB of space, so I wanted to ask, if it's even possible with that low space and processor (RK3026)? Couldn't find clear information about this.
I've come that far, that I've created a new AOSP device tree and inserted all data I know/could find. But it fails now at the kernel.
I've tried to compile the common actual kernel 4.19 with Google's Android tools and getting this error:
Code:
/home/test/Android_Kernel/build/_setup_env.sh: line 28: /home/test/Android_Kernel/build.config: No such file or directory
My build repo lays at /home/test/Android_Pie. What am I missing or doing wrong?
Thanks in advance
Greetings
Click to expand...
Click to collapse
Hello Andi,
I've got a similar question about the device, although I'm not at all an expert as you seem to be. Just want to run it with an COS (lineage, etc). So I am looking for a COS for this device.
Did you manage to solve your problem?
Do you have any idea what COS would run on a smartbook S10?
Thanks for your answer
Hi Willi,
I'm sorry to disappoint you, but I gave up this project after a few days, because I couldn't find any further information and I'm no dev at all. This was my very first attempt to compile a new kernel for an (additionally pretty unknown) Android device. The thing, which helped me the most was watching YouTube videos from https://www.youtube.com/channel/UCnGqG_jyyXmTzdamBpKfeHA (AlaskaLinuxUser AKLU).
Maybe some more experienced users can help you here.
Greetings