Related
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.
I did a Google search and found the github that jackpotclavin seems to have put his CM9 port on, and I mashed it into my local copy of the CM9 repo. I have tested my setup by building a rom for my HP touchpad, which works, but the GP 5.0 ROM fails to build.
In case you are wondering why I want to recompile the ROM, I found a "generic V4L2 camera HAL" that I was going to try to get working on the GP 5.0. I know there are six V4L2 device nodes available under his ROM (video0, video1, video2, video14, video21, and video22). I just need to be able to make a test build of the ROM with all the patches applied, because the patches appear to change more than just the "camera.v4l.so" they produce.
Search Google for "Android generic V4L2 camera HAL" and you'll see a kernel mailing list post from Guennadi Liakhovetski. This links to the patches.
Hi all,
I create this thread for annotate my progress in debugging @FXP's CM10 @munjeni CM11 and for create a guide to new developers. So.. Let's start
Quick start:
Get all necessay software in order to compile CyanogenMod's source code: here there is a very good guide by @elia222, I have no more to add.
Get CyanogenMod 's source code as described here but use this device tree.
Debugging using catlog, dmesg and brain.
Goals:
Some of this bugs are already fixed by other users, all credits to relative developers (if you are one of this and I have not mentioned you, or I make a mistake about credits please send me a PM).
Fix Bluetooth ✓
Fix Wi-Fi ✓
Fix Wi-Fi Tethering ✓
Fix Wi-Fi Direct ✓
Fix Camcorder ✓
Fix LED bar ✓
Fix FM radio
Fix main camera upside-down (Fixed here by @Na'onak ):
This fix consist in use right camera file as FreeXperia use the Xperia GO version. The right file can be downloaded from here.
After have substituted the file in relative CyanogenMod's build folder, recompile and flash.
Fix ambient sensor light (Fixed here + this post by @munjeni + @95A31):
This fix consist in adjust ambient sensor light driver. In detail Android Jelly Bean require als_lx parameter that is not in standatd driver source code. This parameter and relative functions were added by @munjeni in the safest possible way: return a fixed value. The fix consist in implement this new functions exploiting the already present functions. The original version can be dowloaded here and the newest is attacched at bottom of this post. After have substituted the file in relative CyanogenMod's build folder, recompile and flash.
good thread, try this, to run the front camera
https://app.box.com/s/xswdumrr4uqgbj5dczo9
Original thread : http://forum.xda-developers.com/showthread.php?t=2448962
remove FM radio ,its impossible without sources and sources = not possible because ST-Ericsson is no more
loren82 said:
good thread, try this, to run the front camera
https://app.box.com/s/xswdumrr4uqgbj5dczo9
Original thread : http://forum.xda-developers.com/showthread.php?t=2448962
Click to expand...
Click to collapse
Thank you but I have already a fix for front camera. He has published the patch before me so the credits go to him. I want give you a little spoiler: in order to fix from camera is necessary modify only 2 files .
Anyway i currently working on Wi-Fi direct, more suggests about this are well accepted .
percy_g2 said:
remove FM radio ,its impossible without sources and sources = not possible because ST-Ericsson is no more
Click to expand...
Click to collapse
I want investigate on these commits:
https://github.com/CyanogenMod/android_device_sony_montblanc-common/commit/52cedeea40957113358f92780d7f927414fcc73a
https://github.com/CyanogenMod/android_device_sony_montblanc-common/commit/0f86f877f07c7e9d9de7939012d0a19aa9ae2175
https://github.com/CyanogenMod/android_device_sony_montblanc-common/commit/61c4290fd4e7cadde9ff42c6fdf0161f6723f2e1
https://github.com/CyanogenMod/android_device_sony_montblanc-common/commit/8541f5b88cd05789b05ee1bf3034e17cb1c45b70
https://github.com/CyanogenMod/android_device_sony_montblanc-common/commit/59a6f62c4b4c65ba90a6bbac43c04010b1262d14
and maybe continue to develop this:
https://github.com/freexperia/android_packages_apps_FMRadio
hopefully reusing some code from MIUI FM Radio.
loren82 said:
good thread, try this, to run the front camera
https://app.box.com/s/xswdumrr4uqgbj5dczo9
Original thread : http://forum.xda-developers.com/showthread.php?t=2448962
Click to expand...
Click to collapse
While everyone is waiting for camera fix this one above works perfectly and fixes orientation or back camera, also led turns of after this flash when you have used the LED bar fix
@95A31 I guess you forgot to add the link to my guide in the op
Neurom707 said:
While everyone is waiting for camera fix this one above works perfectly and fixes orientation or back camera, also led turns of after this flash when you have used the LED bar fix
Click to expand...
Click to collapse
Front camera fix is coming in couple of days .
elia222 said:
@95A31 I guess you forgot to add the link to my guide in the op
Click to expand...
Click to collapse
Wops, fixed :good:.
95A31 said:
I want investigate on these commits:
https://github.com/CyanogenMod/andr...mmit/52cedeea40957113358f92780d7f927414fcc73a
https://github.com/CyanogenMod/andr...mmit/0f86f877f07c7e9d9de7939012d0a19aa9ae2175
https://github.com/CyanogenMod/andr...mmit/61c4290fd4e7cadde9ff42c6fdf0161f6723f2e1
https://github.com/CyanogenMod/andr...mmit/8541f5b88cd05789b05ee1bf3034e17cb1c45b70
https://github.com/CyanogenMod/andr...mmit/59a6f62c4b4c65ba90a6bbac43c04010b1262d14
and maybe continue to develop this:
https://github.com/freexperia/android_packages_apps_FMRadio
hopefully reusing some code from MIUI FM Radio.
Click to expand...
Click to collapse
If you can get FM audio enabled, there should be enough open source code out there for an open source FM app. The closed source libfmradio.cg2900.so would be needed, but should still work.
An ambitious person might even be able to get FM transmit working on some Euro phones. I was able to enable it with my app, but couldn't figure out how to enable FM transmit audio with some quick attempts.
mikereidis said:
If you can get FM audio enabled, there should be enough open source code out there for an open source FM app. The closed source libfmradio.cg2900.so would be needed, but should still work.
An ambitious person might even be able to get FM transmit working on some Euro phones. I was able to enable it with my app, but couldn't figure out how to enable FM transmit audio with some quick attempts.
Click to expand...
Click to collapse
When I will start to work on the FM radio, I would be happy to collaborate with you .
Fix front camera (Fixed here by @xx214718247):
Also this fix consist in use right camera files as FreeXperia use the Xperia GO version. The right files can be downloaded from here and here. The first one is necessary in order to make able the system to recognize front camera, the second allow to use it. After have substituted the files in relative CyanogenMod's build folders, recompile and flash.
Good to see ambitious devs like you creating xperia u's future!
SIGNATURE OUTDATED. I now use honami moonwalker 4.2
In this period I am looking Team Canjica's camcorder fix:
In this post @DevSwift1 suggest to use android_vendor_sony by Team Canjica for fix camcorder.
It work, but it broke bluethoot. This small issue can be fixed reverting this commit.
The two main differences between Team Canjica's version and TheMuppets' version are:
Different organization of common and device specific libs.
Team Canjica version require that some media and camera libs shoud be compiled from source.
If kumquat-vendor-blobs.mk is modified in order to require that the media and camera libs must be compiled frome source we obtain a lenght 0:00 video and logcat report an error of OMX node allocation about h264enc.
TODO: Search which other differents files are involved in recording/encoding process in order to make TheMuppets' version work.
Currently I am also investigate on Wi-Fi tethering/direct:
For fix these issues I follow this guide by Texas Instruments. The firts issue that I have found is broken Wi-Fi. This can be simply fixed setting the right permissions to files and directories involved in Wi-Fi as described here. The second problem is of corse tethering. The first issue is in hostapd.conf: when Hostapd try to change the owner of the control interface as described in line 8 give a operation not permitted error. The (naive) solution is eliminate line 8 so Hostapd can run without problem. The second and critical issue concern how softAP is used by the system. Below the interesting logcat's part:
Code:
...
E/hostapd ( 2731): Configuration file: /data/misc/wifi/hostapd.conf
...
E/hostapd ( 2731): Using interface wlan0 with hwaddr 01:23:45:67:89:AB and ssid 'AndroidAP'
D/hostapd ( 2731): Deriving WPA PSK based on passphrase
D/SoftapControllerTI( 1484): hostapd started OK
D/SoftapControllerTI( 1484): hostapd set - Ok
E/NetdConnector( 1967): NDC Command {14 softap set wlan0 wl0.1 AndroidAP wpa2-psk trolololol} took too long (1823ms)
D/hostapd ( 2731): random: Got 20/20 bytes from /dev/random
D/hostapd ( 2731): WPA: Delay group state machine start until Beacon frames have been configured
E/hostapd ( 2731): Failed to setup control interface
E/hostapd ( 2731): wlan0: Unable to setup interface.
...
TODO: Search documentation about SoftAP in order to make tethering work.
About Wi-Fi direct the issues start to be hard to fix. From ICS to JB is changed more about Wi-Fi direct managing, in detail JB require a network device called p2p0 in order to get working Wi-Fi direct. AFAIK this device is created and managed only in recents verions of wpa_supplicant and not all drivers can handle this kind of device.
TODO: Porting CM10.2 version of wpa_supplicant in order to make Wi-Fi direct work.
mmm
++++
Hi guys,
here I created a git repository with all fixes that I analized. In order to exploit it just simply download it as zip archive and extract the content over the CyanogenMod's build folder.
I hope in a tethering fix.
Thx for the repo.
Inviato dal mio Xperia U con Tapatalk
For led bar u can use dis..
http://forum.xda-developers.com/showthread.php?t=2429318
marce78 said:
I hope in a tethering fix.
Thx for the repo.
Inviato dal mio Xperia U con Tapatalk
Click to expand...
Click to collapse
I'm working on
ajain3982 said:
For led bar u can use dis..
http://forum.xda-developers.com/showthread.php?t=2429318
Click to expand...
Click to collapse
Thank you :good:
Hi guys, tethering fix is not so easy as I image. I think that @munjeni in this porting have the same problem. Probably is enought a good configuration but without documentation is very hard. I ask you provide to me this files:
init.st-ericsson.rc form Stock Jelly Bean Xperia GO
A logcat from Stock Jelly Bean Xperia GO when Wi-Fi tethering is turn on
Daily report:
Camcorder: For fix this, I decide to use TeamCanjica's android_vendor_sony because it is updated and I prefer his "old" organization of common and device specific files. It already contain the back camera fix, so is useless keep it as different fix. A side effect is broken bluetooth, that as I previous say can be fixed reverting this commit. I fond also iw broken so I used the ICS version.
Wi-Fi thetering: I keep working on this but I dont see the end (for now ). In detail the jellybean Android Network Deamon not has full support for SoftAP used by FreeXperia. The support was reintroduced in this commit. The TeamCanjica has ported this fix in the own Android Network Deamon so I use this last one. I try several configuration of hostapd.conf but none seams work.
@95A31, appreciate doing this and sorry for intruding but it seems that you're the only one looking at real problems right now. Anyway, to the point.
There seems to be everlasting problem of extreme call dialer lag in jb roms, at least in ones that I've tried. During the answering of call phone just freezes and hangs for a period of time during which call gets established but you can't hear or be heard. Lots of people are not using jb especially because of this. However, I haven't tried cm10 in a while 'cause fxp stopped updating it and I don't have enough knowledge to build it, so I can't say if it's present there. So if you think you might be able to fix the dialer please try it. And also if you're already building cm10 with fixes feel free to upload it somewhere, I'm sure people would flash it. That way you could get some more logcats. Of course, I'm just suggesting stuff, there's no pressure and it all depends on if you have free time.
Thanks
Dialer lag affects me only after 3 months of jb. Thereafter, i change roms and wipe data amd to its not there
Sent from my LT22i using xda premium
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.
I'm trying to compile Android 4.2.2 for the Lenovo A2109A. AOSP 4.1.2 mostly worked out fine, except that panorama mode for the camera didn't work. In AOSP 4.2.2 the camera HAL didn't seem to connect to the camera, so I switched to CM-10.1. Camera HAL loads fine, but it doesn't take pictures. The problem seems to be that the stock camera HAL is linked to a version of libjpeg with proprietary additions from nvidia and I can't figure out what they are. Someone else was able to successfully compile CM-10.1 with a working camera by using libjpeg-turbo for compilation (see here), but it also needs a patch for skia that I can't find.
So right now I'm basically stuck and I'm looking for different ways forward. I could really use your advice. Should it be possible to use the camera hal from a related device instead? I know that the nexus 7 is also a tegra3 device, and very close to A2109. It does use different camera devices, but these can be configured in nvcamera.conf. I used strings to find whether any proprietary lib referenced the specific cameras and I found only one, libnvodm_imager.so. The most important differences appear to be in the kernel source, in the following files:
drivers/media/video/tegra/tegra_camera.c
drivers/media/video/tegra/tegra_dtv.c
My question--to what extent should it be possible to just use the grouper tegra camera files for the kernel and then use the grouper camera HAL? Or do you have a different suggestion for me to proceed? I'm asking because I can hardly code. I am, however, getting better and better with git and patches, and I did manage to fix two compile issues in the lenovo kernel source.
My kernel source is over here. My device tree is over here (defaults to aosp 4.2.2 branch, cm-10.1 is a different branch). Grouper kernel sources are over here.
P.S., I have a development thread over at androidtablets.net, which also contains various details.
Answering my own post...
I tried using grouper HAL, gives error message. But using tf700 camera HAL worked, when used with tf700 libnvcamerahdr.so, both taken from stock 4.2.
So--problem solved