Devs: First I wanted to say that I appreciate everything you do. I found something on the NVIDIA dev site that might help you get less-buggy drivers. If you are already aware of this, just ignore me.
I found NVIDIA to be helpful in compiling against Linux kernel sources in the past. I don't know how useful this will be, but after some digging, the Photon uses the Tegra 2 Ventana, Computer-on-a-chip.
New NVIDIA Tegra Android Dev Kit as of 4/19:
http://developer.nvidia.com/content/tegra-android-development-pack-10r6-available
Linux Kernel binary compilers for Tegra:
http://developer.nvidia.com/linux-tegra
If I had the tool chain, I would compile the libraries against the right kernel version and replace the one we are using. It would be nice to have CM9 with no video issues.
Thanks for reading!
Mods: I didn't know if this was safe to post in the Dev forum, so I posted it here. Please move as you see fit.
Related
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
I've had a search and a look around but can't see anything specific enough to answer this.
I have read that the SGS2 uses the new BCM4330 chipset for it's WiFi-N support.
It looks to me that for existing kernels they are using either the existing kernel support or possibly the b43 driver.
I need to find out, and while I have compiled custom kernels in nix in the past, I have never done so in Android, so I'm a little out of my comfort zone here.
I want to compile a kernel where the WiFI driver will support monitor mode, ideally it would be the CM7 kernel with just this extra functionality added, however a number of the tools that I would use to identify the existing configuration do not seem to be available in the standard CM7 build (lspci being one).
I don't want to frack around too much without having read up first so could anyone point me at a good guide for creating my own Android Kernel, even better if the guide was specific to the CM7 version.
Lastly I mostly run a Fedora environment, however the bits I have read seem to suggest a number of tools are only available in a Ubuntu guise (heimdall springs to mind and while I'm sure it's possible to recreate it for Fedora I'm trying to reduce the number of dependencies I'll have to recreate as much as possible). Therefore can I get some advice regarding the least complicated way to generate an Android build environment in Linux.
Thanks
For kernel compilation on android, you can check the several repositories there are for the several kernels. Depending on each kernel/repository/user, you can find a predefined .config inside them, so you can get the basic configuration to compile the kernel, don't know if CM7 has it in its repository...
As for the enviorment, I haven't tried compiling a kernel, but I did compile some ROM on Gentoo Linux, so I suppose it could also be done in Fedora without many problems. The main thing about using Ubuntu is that is very extended, so they're using it as main Linux base, but that doesn't mean it can't be done in other linux distros. You can check CM7 wiki for building from source to install the required packages for your enviorment. In my case I cross checked the Ubuntu packages with Gentoo to install gentoo's version of that packages/tools to be able to compile without problems.
Also in the case of building kernels, you need a toolchain to be able to compile, but there are several webs/tutorials with info on how to use that.
EDIT: You have a complete tutorial for CM7 in their wiki with the needed packages for both Debian and Red Hat based distributions...
Very useful, thanks for the info.
Very useful info.
Hi,
I'm interested in compiling a custom kernel to support wifi monitor mode, but I read in a previous post that it can be a hardware limitation which makes it impossible to use monitor mode. Can anyone confirm that? Maybe a statement/answer from Broadcom?
I'm just asking it because I don't want to start playing with kernel compilation and driver hacking if it can't be done because of some missing code on the chipset or something.
Thanks.
kepten said:
Can anyone confirm that? Maybe a statement/answer from Broadcom?
Click to expand...
Click to collapse
I doubt Broadcom will answer that, but you can try to search the chipset info in Broadcom's web and see if its supported. Also you can check kernel modules if they can compile against that version.
AzureusPT said:
I doubt Broadcom will answer that, but you can try to search the chipset info in Broadcom's web and see if its supported. Also you can check kernel modules if they can compile against that version.
Click to expand...
Click to collapse
Well, Broadcom's website says nothing about monitor mode but I've found a driver (https:// github.com/cyanogen/galaxy-2636/blob/ics/drivers/net/wireless/bcm4330/src/include/wlioctl.h#L1153) which at least mentions it. This is for Galaxy Tab 10.1 which has the same chipset so maybe someone with a Tab 10.1 could verify if monitor mode works with that kernel/driver? ??
Lemme get some things out of the way.. I am a noob. I have searched. I have read some of the results from the search. I am overwhelmed by the 20+ pages of results (lol). I am not 100% sure this is the correct forum for this (not sure where else would be ).. I believe this is one of those things where I need help based on my situation.. Ok, so here I go.
I wish to start porting ICS to my phone. That's my goal. I have general understanding of how linux works, but I do not know much about the android specifics of how they work, or what needs to be modified for this to work. I do not plan to use the kitchen tool as I wish to learn this the hard way. I believe this will help me become more understanding in what I am doing. However, at this point I don't and that's why I'm here. My phone model is irrelevant almost because its prepaid and usually the communities don't even recognize their existence.. at least that's how I feel about it. But I digress. My phone is the zte warp by boost mobile and I am here to learn hopefully the things that will get me started on porting ICS to this phone. I right now believe that the best thing for me to learn is how the android related files work because as it is, I only looked at guides on how linux works and I understand most of it. I'm not sure that's the best thing that will help me port ics, but I'm certain it is important.
Please help me figure out where I should start in learning how to port ICS to my phone basically.
Thanks XDA
anyone? I am quite serious about wanting to do and go into this but I have yet one thread that anyone's ever replied to.. (or post iirc) which puts a damper on me
Snake X said:
Lemme get some things out of the way.. I am a noob. I have searched. I have read some of the results from the search. I am overwhelmed by the 20+ pages of results (lol). I am not 100% sure this is the correct forum for this (not sure where else would be ).. I believe this is one of those things where I need help based on my situation.. Ok, so here I go.
I wish to start porting ICS to my phone. That's my goal. I have general understanding of how linux works, but I do not know much about the android specifics of how they work, or what needs to be modified for this to work. I do not plan to use the kitchen tool as I wish to learn this the hard way. I believe this will help me become more understanding in what I am doing. However, at this point I don't and that's why I'm here. My phone model is irrelevant almost because its prepaid and usually the communities don't even recognize their existence.. at least that's how I feel about it. But I digress. My phone is the zte warp by boost mobile and I am here to learn hopefully the things that will get me started on porting ICS to this phone. I right now believe that the best thing for me to learn is how the android related files work because as it is, I only looked at guides on how linux works and I understand most of it. I'm not sure that's the best thing that will help me port ics, but I'm certain it is important.
Please help me figure out where I should start in learning how to port ICS to my phone basically.
Thanks XDA
Click to expand...
Click to collapse
From my limited knowledge, I think it is a huge task undertaking, you can download Android source code from Google, the hard part will be the device driver development and porting for Linux kernel (and maybe portion of Android). If you are lucky, you can use the existing phone bootloader (or you have to port one). Understanding the inner of the phone (different chip set may need different device driver) will be another challenging task.
by the device driver development, you mean all the libs that go into the phone? Couldn't I just copy/paste the pre-existing libs that are already made for the phone? Also the phone im working with is a bit strange really.. noone has been able to compile the kernel from its source and get it to boot yet.. when it was compiled the zImage was different than that of the stock one.
And yeah, I have downloaded the aosp source.. I just need to know where to start at and the processes involved really
Snake X said:
by the device driver development, you mean all the libs that go into the phone? Couldn't I just copy/paste the pre-existing libs that are already made for the phone? Also the phone im working with is a bit strange really.. noone has been able to compile the kernel from its source and get it to boot yet.. when it was compiled the zImage was different than that of the stock one.
And yeah, I have downloaded the aosp source.. I just need to know where to start at and the processes involved really
Click to expand...
Click to collapse
To answer you question no the drivers and lib files are different for aosp based rooms then they are for the stock OEM from. The first step will be to get a working kernel. Without anything you do will be pointless
I'm somewhat interested in the same thing, and from what I've gathered, you'll need to do these things to begin ROM development:
1. Read every page on the AOSP site and grab a copy of the AOSP source. It probably wouldn't hurt to read the regular Android developer wiki as well.
2. Learn about Linux driver development:
http://lwn.net/Kernel/LDD3/ (this is apparently considered THE BOOK on Linux driver development)
http://www.freesoftwaremagazine.com/articles/drivers_linux
3. Learn pretty much every detail about your phone and its hardware, especially when it comes to how ROMs are installed on it. For example, my phone (the Droid X2) has a locked bootloader, so 2nd init has to be used to boot new ROMs, and this makes it so that we cannot update the kernel.
You can usually find this sort of information on your phone manufacturer's website. Sometimes they even post the source code to their phone's drivers, which is helpful.
4. Look at other ROMs (preferably for your phone) and see how they work. The source code is freely available for most popular ROMs.
For example: CyanogenMod keeps their source code in a public git repository: https://github.com/cyanogenmod
5. Get to work on porting!
I would highly recommend starting with something smaller, however, just as a start. One good jumping-off point is probably this guide: http://forum.xda-developers.com/showthread.php?t=1272270
If any part of this was wrong, or if I left something out, somebody feel free to correct me, I'm still a noob.
Thank you so much for your direction, however,, android kitchen.. im not sure about that because isnt that only ment for htc devices? My phone is made by zte
what device do you even have?
if it's stuck officialy on 2.1 or 2.2 there's no hope that if you even port it that it'll work
its the zte warp from boost mobile (prepaid). Btw if I compile an aosp ics launcher and put that on my phone whats the chances of that working?
edit: it uses 2.3.5
Well Sebastian responded on android forums, apparently zte is very bad at version control with their kernel sources. So when they complete one project, they use the same source for the next project, and what they release could be for anything. Apparently the blade source had the same issues, it took him a while to get them to correct the source
Sent from my N860 using Tapatalk
Yeah I noticed that there were ppl saying there were things similar but I'm not sure what will work or what won't.. guess its time to start a petition on zte to release the source code lol
edit: seems like zte's bein a bad company and violated the GNU GPL license for not providing a complete source code.. I compiled an email and sent it to someone who can proof read it and send it to the right person for this kinda thing.. danggit zte
Hello there forum users! This thread was created with the sole purpose of helping me (and others) find out how to build ROMs for unsupported devices.
Basically, I've built AOKP from source, but the device I was building for was already supported. What I'm trying to do now if build Dirty Unicorns 4.2.2 for my device, which is not supported by the ROM. From what I've read, I've already forked the "vendor_du", "
android_device_samsung_vibrantmtd", "vendor_samsung", "proprietary_vendor_samsung", "android_hardware_samsung", "android_packages_apps_SamsungServiceMode", and "android_build".
How do I build the ROM for the Samsung Vibrant T959, when it is not supported. If someone has miraculously found a post that I have missed, I would appreciate it very much. Additionally, a list of commands and explanations would greatly assist me. I'm pretty new to the whole Android building thing so I thank you all for help!
Ain't nobody is going to help you ^^ I am looking for that kind of knowledge too. I would like to start building roms from source and make some modifications to CM10's kernel
check out Legion modz team thread
it has a little info on it
http://forum.xda-developers.com/showthread.php?t=2314836
and make google your best friend
so much way to take...
theabnormalguy said:
Hello there forum users! This thread was created with the sole purpose of helping me (and others) find out how to build ROMs for unsupported devices.
Basically, I've built AOKP from source, but the device I was building for was already supported. What I'm trying to do now if build Dirty Unicorns 4.2.2 for my device, which is not supported by the ROM. From what I've read, I've already forked the "vendor_du", "
android_device_samsung_vibrantmtd", "vendor_samsung", "proprietary_vendor_samsung", "android_hardware_samsung", "android_packages_apps_SamsungServiceMode", and "android_build".
My github account is MaxusPrimus
How do I build the ROM for the Samsung Vibrant T959, when it is not supported. If someone has miraculously found a post that I have missed, I would appreciate it very much. Additionally, a list of commands and explanations would greatly assist me. I'm pretty new to the whole Android building thing so I thank you all for help!
Click to expand...
Click to collapse
Im starting to learn to build from source. Theres many tutorials on how to get started. Ill post links when I get to my pc later. First I would get the source code for kernel on samsung. If not available get stock rom to dump required files aswell as other files needed. I dont know if this will guide you in the right direction. Just keep in mind and always remember the kernel hardware devices is different then the operating system. You juz need to learn google how to merge the to.
---------- Post added at 08:51 PM ---------- Previous post was at 08:09 PM ----------
flipinfin said:
Im starting to learn to build from source. Theres many tutorials on how to get started. Ill post links when I get to my pc later. First I would get the source code for kernel on samsung. If not available get stock rom to dump required files aswell as other files needed. I dont know if this will guide you in the right direction. Just keep in mind and always remember the kernel hardware devices is different then the operating system. You juz need to learn google how to merge the to.
Click to expand...
Click to collapse
Heres some starting links that im using starting to build from source. the samsung open source page look for your model number http://opensource.samsung.com. Obviously. you can build your own kernel.
how to unpack repack img http://forum.xda-developers.com/showthread.php?t=1081239
http://www.kandroid.org/online-pdk/guide/index.html very useful link aswell as this one http://source.android.com/source/initializing.html.
heres a link to identify partition tables http://forum.xda-developers.com/showthread.php?t=1959445. . Heres another link that you prolly can pull files from if needed http://www.teamandroid.com/2013/04/...kp-build-6-android-422-jelly-bean-custom-rom/
Dont take this the wrong way but i think your getting confused how roms kernels etc r built its all open source. That rom is based off of jelly bean and alls they did was change the name. Though its open source so i would assume you can repo the rom at https://github.com/. In addition if i was you i would download the rom "which you prolly already have and do some investigating.. heres another useful link http://xda-university.com/as-a-developer/porting-aosp-roms-using-source-code. Never forget google is your best friend. Fogot to mention if you aint on linux i would switch os real soon. I think this link will be ver ver very helpful https://bitbucket.org/bigwillyg/buttered_toast_shooter
Is that Vibrant T-Mobile ? cuz if it is http://aokp.co/devices/vibrantmtd theres your starting point