Related
So I've been trying to build a kernel module for LIRC using the Gen8 source, but I keep getting issues when trying to compile the module. Since the setup scripts from LIRC keep going to my host Ubuntu source rather then the Gen8 stuff.
Has anyone had experience cross compiling LIRC or any modules for that matter and can help me out or knows where to go? Google hasn't been good to me in this regard.
TIA
Moved to general as not andorid development
Mr. Clown said:
Moved to general as not andorid development
Click to expand...
Click to collapse
Erm, yeah it is... Developing a kernel module for android....
Have you read that howto? [HOWTO] Build custom kernel, libraries and applications on your own
If you have any issues compiling kernel stuff, feel free to PM me or post it in your topic here and I'll try to help you.
I'll take a look at your guide and try it out over the next day or so
Hi,
I've started to download all the listed tools from AOSP and from Chulri's XDA post but wanted to start the discussion on what steps would be needed to create a gingerbread rom for our Gen8 devices.
My initial questions:
1- Would the driver's source from Archos that are currently written for 2.2 be compatible with 2.3? Can they reasonably be updated?
2- Aren't there two approaches we could use? Update the kernel to be compatible with 2.3 or back port 2.3 to be compatible with our existing kernels?
I apologize for probably sounding ignorant but this is all learning for me and any help is greatly appreciated. If nothing else, this thread would be a great place to discus the steps it would take to develop a Gingerbread rom from a high level stand point.
Mr. Clown - I'd appreciate leaving this in the devel forum since it is specific to devel for 2.3 and gen8 and not just an "is it possible" thread.
Thanks!!
-Nate
double post
sry
do you have kernel dev experience for linux/unix?
if yes concentrate on cm a lot of development has been done.
there are phones who have almost identical components ( well the usb attached screen is a problem)
the recovery will be hell of a problem too..
if you never worked with that stuff (at least i hope you are a c crack otherwise look for other stuff to learn c .kernel development is one of the hardest stuff you can pick in softwaredev.) look for another project where somebody could guide you and teach you stuff the first project will be learning the second could be a very specific project like this where you have to work on your own
Sent from my GT-I9000 using Tapatalk
gbohm said:
do you have kernel dev experience for linux/unix?
if yes concentrate on cm a lot of development has been done.
there are phones who have almost identical components ( well the usb attached screen is a problem)
the recovery will be hell of a problem too..
if you never worked with that stuff (at least i hope you are a c crack otherwise look for other stuff to learn c .kernel development is one of the hardest stuff you can pick in softwaredev.) look for another project where somebody could guide you and teach you stuff the first project will be learning the second could be a very specific project like this where you have to work on your own
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
Hi, thanks for the reply. I've been reading just about all of Chulri's posts in his thread and I know $aur0n would answer specific questions if I asked. Other than that, I took a few C++ classes a few years ago but never took the OS/Hardware level classes. I stopped at advanced/e intermediate algorithms and data structures. Either way, I was hoping to start a discussion with this thread about steps that would be needed to happen to build a gingerbread ROM.
But if anyone wants to read along with me about kernel devel then you can start here with me - http://forum.xda-developers.com/showthread.php?p=11261995
Archos's git - http://gitorious.org/archos/
Chulri's How to - http://forum.xda-developers.com/showthread.php?t=891056
Chulri's tool and fantastic following discussion (still trying to comprehend all of it) - http://forum.xda-developers.com/showthread.php?p=10033305#post10033305
Really Thank you for start this thread!
And when you've developed a gingerbread rom, i think the best would be if you work together with $aur0n Do think like i do?
And:
If you need a tester or somebody to do some little things, i'll do it
(At the moment i report some bugs at solune/sauron and test the bootscreens)
I want to help you with that cool project
xnatex21 said:
Hi, thanks for the reply. I've been reading just about all of Chulri's posts in his thread and I know $aur0n would answer specific questions if I asked. Other than that, I took a few C++ classes a few years ago but never took the OS/Hardware level classes. I stopped at advanced/e intermediate algorithms and data structures. Either way, I was hoping to start a discussion with this thread about steps that would be needed to happen to build a gingerbread ROM.
But if anyone wants to read along with me about kernel devel then you can start here with me - http://forum.xda-developers.com/showthread.php?p=11261995
Archos's git - http://gitorious.org/archos/
Chulri's How to - http://forum.xda-developers.com/showthread.php?t=891056
Chulri's tool and fantastic following discussion (still trying to comprehend all of it) - http://forum.xda-developers.com/showthread.php?p=10033305#post10033305
Click to expand...
Click to collapse
i am sorry but you will not be able to develop a kernel with some classes you took i am a dev so i am quite avit with it i come from a completly different backgroud (windows software) but i have a unbelievable hard time to find a starting point with cm7 for sgs although there other developers around
Sent from my GT-I9000 using Tapatalk
That's understandable. If development is going to be tough or near impossible, I'd hope to try before I give up. Right now I'm learning about kernel development but would love it if someone could help me focus.
Is the touch display driver the hardest part to upgrade? What changed in 2.3 that makes updating the driver so difficult? Or would it be better to "back port" 2.3 to be compatible with archos's driver?
Sent from my GSBv1.4-ERIS using XDA App
xnatex21 said:
1)Is the touch display driver the hardest part to upgrade?
2)What changed in 2.3 that makes updating the driver so difficult?
3)Would it be better to "back port" 2.3 to be compatible with archos's driver?
Click to expand...
Click to collapse
1) I would say one of the hardest parts
2) I think the archos drivers aren't compatible, so ...
3) ... this would be better because then you've better drivers support (for each hardware)
Again:
I think this project is assomeI'd love to be a helper/tester.
Found post about VegaComb being released for Adam on TabletRoms.com. Due to the similarities and the fact that there exists ROMs for G-Tab based on Adam. Do we know if there is an effort to port this ROM to G-Tab? Any info would be appreciated as this looks to be THE ROM, with the possibility of fixing camera and hardware acceleration.
A kernel is being worked on ; on the slatedroid forum. The hardware is different so a kernel has to be made for it to work
[email protected]: Posted Today, 09:31 AM
Unfortunately the Vega is not a hardware match for our beloved g-tab, they are very similar however they are not the same hardware exactly, little things like the wireless controller and the camera are different. They also have a different mainboard in their system. I'm pretty sure that the rom that works on theirs is not going to work on ours until we have a working kernel to work from. They have worked very hard on rewriting the drivers to get their tablet to work as well as it is in 3.2 and they don't seem to be slowing down now that it is working. I know that the group that is working on the kernel is working very hard to get it running as quickly as we can, I don't think that most of us have much experience in kernel coding and so it is taking some time to even get it to boot. However I can tell you that we are working diligently to get through the problems and get a kernel out to the community so that we can join the ranks of the Vega in making Google cry by hacking our way to victory. On a side note I want to say how impressed I am by the level of assistance that everyone in this community has for the new members and old members alike. I don't know of another rom that has this level of support from it's users out there. Thanks to all of you that are helping people overcome their issues and enjoy this fantastic rom.
Click to expand...
Click to collapse
.
[email protected] Posted 14 August 2011 - 09:01 PM
Hello all, Ch3vr0n5 here
The GTab Kernel Dev Team would like to chronicle our kernel development process for everyone to enjoy. The Gtablet 2.6.36 kernel project is based on the work done by Eduardo/RaYmAn on the Adam kernel. The biggest thanks goes out to them and anyone else who works on that project because it has made our work possible.
The Dev team is currently: Myself, Icewyng, Mayday_Jay, WayneMasta, Treznorx
[8/25/2011]
We know that we are hanging on init.rc and have a few ideas one how to proceed. Mayday_Jay (Give him and Icewyng a big thank you because they have made this project viable) is working on getting all the developers a proper update.zip that will help those with out a usb to serial converter get some useful debug information.
Don't fret when it takes a couple days for us to update. If you want bleeding edge news, join us on the kernel dev irc channel which is found further on in the thread. We are still working! =)
[8/23/2011]
Linux (BT5) will boot without Touchscreen working. Work is progressing slowly to get this working with Android. Mayday_Jay, with the use of USB -> serial converter has been able to get some useful dmesg output as well as some other debug information that is giving us new ideas on how to proceed.
[8/19/2011]
Starting to modify the adam files to mach the correct values for our device. Our current config gets us passed the birds and to the second boot image and the usb device registers. Trying to get it connected to adb to get some dmesg output.
[8/14/2011]
The resulting kernel did not boot and this is more than likely due to the fact that there are quite a few new config options that need to be set. I have run a diff to find differences between Pershoot's and Rayman's kernel and will be trying a new config either tonight or tomorrow hopefully. Gotta sift through new and deprecated options as well as any they both have but are set differently (and why)
Part 2
The kernel compiled with the additions from rayman's config in pershoots got it past the birds to the "Android 3.0" screen. Tomorrow I will be able to hookup adb and see where it is crashing from there.
[8/15/2011]
Still running through different configurations. Need to ask pershoot what modifications he made to make the .32 kernel boot on the 1.2 bootloader. IE Which files use the NEWBL config option and what the changes are.
[8/16/2011]
I received the source for the Vega kernel from rebel1. I may not update for a few days as I try out different configs and such but I will still be here.
[8/17/2011]
Decided to go with the Adam kernel because of hardware compatibility. Put up the github repo.
GitHub.com Repo
git://github.com/ch3vr0n5/android-tegra-2.6.36-gtablet.git
-----------------------
All thoughts, idea, comments and criticisms are welcome (Please be kind). Just remember, most of us are not programmers or software engineers by trade. I got my degree in network security so I generally play with routers, firewalls and the like and do this as a hobby. If you find anything wrong with what I or any of the Dev team have written please tell me... just don't point and laugh. LOL
Cheers
Click to expand...
Click to collapse
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&A for [SOURCES][DEVONLY] CyanogenMod 12.1
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [SOURCES][DEVONLY] CyanogenMod 12.1. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Embedded Developer want to help.
Hi everyone. I want to get in and help.
Hi,
if you want to help get the sources and build a ROM. You can find the instructions for the device here:
https://git.cryptomilk.org/projects/android/android_device_samsung_slte.git/tree/README?h=cm-12.1
Then look at the TODO list and start to fix issues. Let me know which one you want to work on and I can give you some hints what you need to do.
compiling
can anyone compile the source code for me or can anyone tell me what to do?
sorry
i've found the read me now
It looks like, the instructions are for cm 11, but the title says it's 12.1 How can i compile cm 12.1? (sorry if im wrong, I am a noob at CyanogenMod)
Download
People saying that the CM 12.1 is not out. But why can i donwload it from the here:
https://git.cryptomilk.org/projects/android/android_device_samsung_slte.git/snapshot/android_device_samsung_slte-cm-12.1.zip
Or is this not the final?
it's 6.8mb, can't be a rom
Yes :/
current situation
can u tell us now which bugs still exist from the already known ofc!! i would like to help but i want details about the current status of the rom !! ty
Not sure if you ever got the requested information about the MTP vendor & product IDs. In short, I get this:
Vendor: 04e8
Product: 6860
I also can provide the full print-out of lsusb for this device, if needed.
Galaxy ALPHA "internals" .... it's memory technology
Hi,
I'm new and I'm carefully following this CM port since I believe this phone (G850F) has some key advanced features which were missed by the mainstream user.
Behind the external design what makes the ALPHA amazing is the technology SAMSUNG used to package its Exynos. This implementation of the 5430 has 4 DRAM & 4 FLASH DIEs stacked with TSV. The DRAMs are implemented using Samsung's flagship Widcon I/O technology!! The connections between the DRAM chips and the Memory Controller are offering a Wide I/O path and I strongly believe there is one DRAM controllers per DIE. This means that memory accesses are arbitrated VERY efficiently allowing the CPU to extract an high amount of SUSTAINED bandwidth from the DRAMs. Please have a look at this link from chipworks: https://chipworks.secure.force.com/catalog/ProductDetails?sku=SAM-KMR2W0009M-A803
Hope this info will get everybody more excited!
Regards
pventi
have anyone tryied this rom on SM-G850m?
dont even think about it,you will lose only time fo flashing it & after that you will immediately back to 444
maybe in this atempt lose IMEI
Hello is the application boot times better than stock? For example how long it takes to load subway surfers, because with the stock rom it takes about 10 seconds
rom custom
hello,
I would like to create a custom rom. Is it possible to have a tutorial to compile a ROM for the Samsung Galaxy alpha please .
progress??
Any progress. I m desperately waiting for your rom ...
modpunk said:
I will release a ROM soon. The camera is working now. Video decoding too. Just SELinux needs to be set to enforcing.
Click to expand...
Click to collapse
What about car BT calling? It seems that is the problem of all Galaxy Alpha custom 5.1.x roms.....
km1306 said:
What about car BT calling? It seems that is the problem of all Galaxy Alpha custom 5.1.x roms.....
Click to expand...
Click to collapse
I do not have a car so I can't test it ...
What is the difference then between modpunks first release and kyasu's one which he aleady released?
I only want to understand how far we are and where the problems are.
I'm no developer, but I understand tecnical lenguage, so would be nice If somebody can give me an overview...
Thanks
slg60 said:
What is the difference then between modpunks first release and kyasu's one which he aleady released?
I only want to understand how far we are and where the problems are.
I'm no developer, but I understand tecnical lenguage, so would be nice If somebody can give me an overview...
Thanks
Click to expand...
Click to collapse
This was asked from modpunk awhile back, here are his answers:
modpunk said:
I have to check, RaymanFX and I are building the OMX codecs from sources and kyasu is using the binary blobs ....
Click to expand...
Click to collapse
modpunk said:
RaymanFX and I are using different sources. We are currently working with Ethan to get them upstream in CM. We also dissassembled the OMX blob to find out the correct values to get NV12 and NV21 video formats working correctly. The sources are newer and fix several bugs. We are getting there ...
Click to expand...
Click to collapse
https://en.wikipedia.org/wiki/Binary_blob
https://en.wikipedia.org/wiki/OpenMAX
https://www.linkedin.com/in/chenethan = Ethan
I don't understand this stuff so well, but I understand from this stuff that modpunk's way is better.