Hey guys
First of all: I'm not good in develop! But i want to start with CM porting to our Gen8
I just get some infos from chulri how to port CM.
What have to be do:
Build-Scripts for CM on Gen8
Extract some Gen8 Binaries
Build the Kernel with Touchscreen Drivers
Build-Scripts for CM on Gen8
I started a Thread at the CM Forum about this I'll report here..
( http://forum.cyanogenmod.com/topic/24048-cm-port-to-archos-gen8/ )
Extract some Gen8 Binaries
I hope chulri will answere me soon so i can do this
Build the Kernel with Touchscreen Drivers
This have to be done from a guy who has Kernel Knowledge! Anyone?
If anyone's interested i could send a link with an how to, i've found onthe web
Everybody is invited to help to getting this Project started!
Greetz,
Lenn
I'm not a great porter, but I've shadowed a lot of porting with the cm roms, I'll try to do my part if you host the project on something like github(both kernel and rom). I also have a little bit of kernel development experience.
Scaryghoul said:
I'm not a great porter, but I've shadowed a lot of porting with the cm roms, I'll try to do my part if you host the project on something like github(both kernel and rom). I also have a little bit of kernel development experience.
Click to expand...
Click to collapse
Thats good You know more than me
I just could host the normal kernel and rom, because i've do nothing yet
(When chulri answered me i'll catch the original binaries, you can read this here: http://forum.xda-developers.com/showthread.php?t=1029507&page=3 )
You think you could the first step i described?
That would be assome
thank you for start the ball rolling!
Lennb said:
Thats good You know more than me
I just could host the normal kernel and rom, because i've do nothing yet
(When chulri answered me i'll catch the original binaries, you can read this here: http://forum.xda-developers.com/showthread.php?t=1029507&page=3 )
You think you could the first step i described?
That would be assome
thank you for start the ball rolling!
Click to expand...
Click to collapse
Not sure what you mean, you want me to explain how to extract the original binaries?
If you need a tester i'm your man ^^
(and if i can be of help with anything else learn me and i'll try ^^)
link should be this?
http://forum.cyanogenmod.com/topic/19647-archos-gen8/page__view__findpost__p__196966
Scaryghoul said:
Not sure what you mean, you want me to explain how to extract the original binaries?
Click to expand...
Click to collapse
First of all, Thanks for a help appear!!
I think he mean the step of porting CM7 to gen8 is:
1.Build-Scripts for CM on Gen8
2.Extract some Gen8 Binaries
3.Build the Kernel with Touchscreen Drivers
so, step 1 should be "1.Build-Scripts for CM on Gen8"..
Scaryghoul said:
Not sure what you mean, you want me to explain how to extract the original binaries?
Click to expand...
Click to collapse
I dont know, when chulri respone me i'll report it here
@eagleofdeath13
Thanks for support! Maybe you could search someone with Kernel knowledge who could do the first step, i think this is hard
@LeoNg628
Yep,sorry about that, thank you for correcting me
Thank goes to all you guys!
LeoNg628 said:
First of all, Thanks for a help appear!!
I think he mean the step of porting CM7 to gen8 is:
1.Build-Scripts for CM on Gen8
2.Extract some Gen8 Binaries
3.Build the Kernel with Touchscreen Drivers
so, step 1 should be "1.Build-Scripts for CM on Gen8"..
Click to expand...
Click to collapse
Yep,you're right
But i think its the hardest step and i've kernel knowledge,
We have to find someone with Kernel Knowledge who could do this
(Except chulri, i always ask him, but he has to much work right now..)
Oh, well I've never really created a build script before but there are plenty of guides instructing on how to do so.
Extracting the binaries usually consists of adb pulling all of the binaries required for the complication that are proprietary/closed source. I suppose you could just copy/paste them to your sdcard then copy to a computer if adb weren't around but that's just extra work.
As to which binaries we need, I'm not sure yet but we can cross that bridge in a bit.
To make the build script, we should probably analyze other build scripts for other devices and the directories for them.
This thread might aid in development, I doubt they have the build scripts for archos but they at least have examples in the program I'm sure and other tools to use.
http://forum.xda-developers.com/showthread.php?t=969266
Also for whoever attempts to get a functional kernel for cm7 this page may be useful(or possibly me just making sure I read this later)
http://wiki.cyanogenmod.com/index.php?title=Howto:_Build_a_Kernel_Port
Scaryghoul said:
Oh, well I've never really created a build script before but there are plenty of guides instructing on how to do so.
Extracting the binaries usually consists of adb pulling all of the binaries required for the complication that are proprietary/closed source. I suppose you could just copy/paste them to your sdcard then copy to a computer if adb weren't around but that's just extra work.
As to which binaries we need, I'm not sure yet but we can cross that bridge in a bit.
To make the build script, we should probably analyze other build scripts for other devices and the directories for them.
This thread might aid in development, I doubt they have the build scripts for archos but they at least have examples in the program I'm sure and other tools to use.
http://forum.xda-developers.com/showthread.php?t=969266
Also for whoever attempts to get a functional kernel for cm7 this page may be useful(or possibly me just making sure I read this later)
http://wiki.cyanogenmod.com/index.php?title=Howto:_Build_a_Kernel_Port
Click to expand...
Click to collapse
Thank you!
Okey, you really knows a lot more than i am
I'll do the binaries, just say me where they are?^^
Maybe you could try the Build script(s)...
And for the Touchscreen Driver:
We've to look for somebody who do the instructions i've found on the net
Scaryghoul said:
This thread might aid in development, I doubt they have the build scripts for archos but they at least have examples in the program I'm sure and other tools to use.
http://forum.xda-developers.com/showthread.php?t=969266
Click to expand...
Click to collapse
Okey, i know this Thread, its great except the fact it don't support Archos ^^
I'll send a message at these guys about archos devices and parallels about our gen8 devices ad supported devices, so we could create our own script to do it from scratch like they've do
But i now i go to bed^^
To start with build scripts I would recommend to find a device - which is supported by CM, if there even is one - which has similiar hardware as the Archos Gen8 series and start from there instead to start from scratch.
If there is no such similiar device series you unfortunately would have to start from scratch
chulri said:
To start with build scripts I would recommend to find a device - which is supported by CM, if there even is one - which has similiar hardware as the Archos Gen8 series and start from there instead to start from scratch.
If there is no such similiar device series you unfortunately would have to start from scratch
Click to expand...
Click to collapse
I have Desire and Desire HD also Aria and Legend....but all is HTC...the hardware spec is not similar to Archos gen8....
chulri said:
To start with build scripts I would recommend to find a device - which is supported by CM, if there even is one - which has similiar hardware as the Archos Gen8 series and start from there instead to start from scratch.
If there is no such similiar device series you unfortunately would have to start from scratch
Click to expand...
Click to collapse
Okey,thank you
there is no device similar to our archos that is supported
But is it possible to "mix" it?
Like:
Cpu - from a phone that has Arm Cortex A8
[...]
we put together all parts
woukd that be possible?
Yes, CPU might be the most important common part, then WiFi/BT, DSP (for hardware acceleration of videos), Sound, Touchscreen and in the end USB host port.
Lennb said:
Okey, i understand thank you very much, chulri!
I've searched but i dont found anything about writing build scripts on android...
Click to expand...
Click to collapse
I haven't found anything too, but I did some research in the beginning of this year: http://wiki.cyanogenmod.com/index.p...nMod_for_Sholes#Prepare_the_Build_Environment
After installing the repository on the build machine, you have all the build scripts from other devices and can copy and adapt them.
Lennb said:
Okey, then we'll do this step (binaries) in the end, i think the best would be to write the build scripts first? What do you mean?
Click to expand...
Click to collapse
Agreed
Lennb said:
i think we should write now on the developement thread, then the other guys could read it
Click to expand...
Click to collapse
Agreed too
chulri said:
Yes, CPU might be the most important common part, then WiFi/BT, DSP (for hardware acceleration of videos), Sound, Touchscreen and in the end USB host port.
Click to expand...
Click to collapse
Okey, but how do we get these firmwares out of the archos firmware?
http://wiki.cyanogenmod.com/index.p...nMod_for_Sholes#Prepare_the_Build_Environment
After installing the repository on the build machine, you have all the build scripts from other devices and can copy and adappt them.
Click to expand...
Click to collapse
Okey, i just have a windows pc, but i think i put linux on it
Ubuntu is the best for developening, isn't it?
I have to talk to my brother (with-owner of the pc)
I'll put a dual-boot system on my pc
I want Cyanogen!
Lennb said:
Okey, but how do we get these firmwares out of the archos firmware?
Click to expand...
Click to collapse
a) adb pull (this is what the "extract_files.sh" does)
b) root the device and copy files one by one
c) root the device, copy the filesystem image and extract the files by script
Lennb said:
Okey, i just have a windows pc, but i think i put linux on it
Ubuntu is the best for developening, isn't it?
I have to talk to my brother (with-owner of the pc)
I'll put a dual-boot system on my pc
Click to expand...
Click to collapse
So you start developing? If not, no need for linux at all
Lennb said:
I want Cyanogen!
Click to expand...
Click to collapse
4 days ago you wanted UrukDroid, 3 day ago you wantet Honeycomb, now you want CM, will you stay this time?
chulri said:
a) adb pull (this is what the "extract_files.sh" does)
b) root the device and copy files one by one
c) root the device, copy the filesystem image and extract the files by script
Click to expand...
Click to collapse
Sorry, im a noob I just don´t understand.
Adb pull is copy files over adb(command connection over usb); right?
So you start developing? If not, no need for linux at all
Click to expand...
Click to collapse
I try I reset my Pc anyway
4 days ago you wanted UrukDroid, 3 day ago you wantet Honeycomb, now you want CM, will you stay this time?
Click to expand...
Click to collapse
Same answer as in 2
from what i understand 2.2, 2.3 doesnt support usb hosting which is needed for the archos screen
is there a fix for that?
i know android 3.0, 3.1 support usb hosting...
Related
Basically what I want to do is take the FRX07 bundle.zip and simply replace that system.ext2 with the one from this build (That's a direct link to the .rar file, btw).
The Sense build comes in system.sqsh form and I have already managed to convert that into a working system.ext2.
My dilemma comes in here.. I need help determining which files I need to replace/modify in the initrd.gz/rootfs/system folder/etc. in order to boot this build with the most current features of FRX07 (rootfs and whatnot).
I have some experience with modifying initrd.gz and rootfs images, but I'm still extremely noobish in the sense that I don't know exactly which coding I must change to get the desired effect.
I appreciate any helpful insight in advance!
EDIT: Also, it would be VERY helpful if someone could explain the functions and purposes of the rootfs.img, initrd.gz, and kernel. I have my speculations and assumptions, of course, but knowing for sure gets me a step closer to what I want. again, thanks in advance!!
maff1989 said:
Basically what I want to do is take the FRX07 bundle.zip and simply replace that system.ext2 with the one from this build (That's a direct link to the .rar file, btw).
The Sense build comes in system.sqsh form and I have already managed to convert that into a working system.ext2.
My dilemma comes in here.. I need help determining which files I need to replace/modify in the initrd.gz/rootfs/system folder/etc. in order to boot this build with the most current features of FRX07 (rootfs and whatnot).
I have some experience with modifying initrd.gz and rootfs images, but I'm still extremely noobish in the sense that I don't know exactly which coding I must change to get the desired effect.
I appreciate any helpful insight in advance!
Click to expand...
Click to collapse
90% of the work that went into FRX07 is in system.ext2, not anywhere else. Plus the rootfs itself is designed specifically to work with the system.ext2 from FRX07. That's not to say that it's impossible to modify it, but no forum thread will ever tell you all the changes you'd need to make to get that up and running.
rpierce99 said:
90% of the work that went into FRX07 is in system.ext2, not anywhere else. Plus the rootfs itself is designed specifically to work with the system.ext2 from FRX07. That's not to say that it's impossible to modify it, but no forum thread will ever tell you all the changes you'd need to make to get that up and running.
Click to expand...
Click to collapse
Ohh I see, about the rootfs and the system.ext2. But that's not to say that the work that went into the FRX07 system.ext2 wouldn't be useful for another .ext2
I know the basics of modifying the system and rootfs and I have a general idea of what needs to be done, so all I'm looking for is sorta a nudge in the right direction. I'm not expecting a to-do list, but a little goes a long way.
Plus, I doubt Google would have anything useful on this topic, especially in reference to the Tilt2. Hence, this thread lol.
tiad8
maff1989 said:
Ohh I see, about the rootfs and the system.ext2. But that's not to say that the work that went into the FRX07 system.ext2 wouldn't be useful for another .ext2
I know the basics of modifying the system and rootfs and I have a general idea of what needs to be done, so all I'm looking for is sorta a nudge in the right direction. I'm not expecting a to-do list, but a little goes a long way.
Plus, I doubt Google would have anything useful on this topic, especially in reference to the Tilt2. Hence, this thread lol.[/QUOTE=maff1989;15812348]
you can ask tiad8 he will help u cuz he's a lover of sense build so he will tell u what to do and actually i think he created dis build so u can vist his site http://www.tiad8.com and ask him and he will help u .
Click to expand...
Click to collapse
alaa_hany47 said:
you can ask tiad8 he will help u cuz he's a lover of sense build so he will tell u what to do and actually i think he created dis build so u can vist his site http://www.tiad8.com and ask him and he will help u .
Click to expand...
Click to collapse
Couldn't be more wrong. klinux created the Sense build, it was originally called 'rosie' before tiad8 took it and butchered it to make it appear like it was his work...
alaa_hany47 said:
you can ask tiad8 he will help u cuz he's a lover of sense build so he will tell u what to do and actually i think he created dis build so u can vist his site http://www.tiad8.com and ask him and he will help u .
Click to expand...
Click to collapse
Tiad8 doesn't know ****. Pardon the French. But thanks for the suggestion.
arrrghhh said:
Couldn't be more wrong. klinux created the Sense build, it was originally called 'rosie' before tiad8 took it and butchered it to make it appear like it was his work...
Click to expand...
Click to collapse
I noticed his skills in butchering.
what base are you using for the sense build? I have a successful build booting. The problem I have is with the sqsh file. If I unsquash it and try to rebuild it I get an error on boot. How did you convert it over? And do you have a working radio?
Never mind. I got it from the first post. That one is really slow port of Hero build. I have one that is a direct port and a lot smoother with the exception of the radio not working. But I am using completely updated rootfs, kernel, and initrd. The ones from xdandroid work just fine. But I use these kernels. I dunno if they are different from the ones directly from xdandroid site.
taylorhome11 said:
But I use these kernels. I dunno if they are different from the ones directly from xdandroid site.
Click to expand...
Click to collapse
That's XDAndroid's repo for kernels... There's a .35 and .39 tree there as well.
arrrghhh said:
That's XDAndroid's repo for kernels... There's a .35 and .39 tree there as well.
Click to expand...
Click to collapse
Thanks for clearing that up
So I have been working on this for a while trying to get things to cross compile, and i got this to compile it is the Source and the program runs on the nook. Next we will have to write our new init.rc to mount our own os. Someone will have to help me with some research, but I just thought you should know.
Here are the files:
2nd-init.tar
To recomile with the NDK use the following command:
Code:
/home/<user>/Downloads/android-ndk-r7/toolchains/arm-linux-androideabi-4.4.3/prebuilt/linux-x86/bin/arm-linux-androideabi-gcc --sysroot=/home/<user>/Downloads/android-ndk-r7/platforms/android-14/arch-arm/ 2nd-init.c
(Thanks to Indirect)
GOOD LUCK
Loglud said:
So I have been working on this for a while trying to get things to cross compile, and i got this to compile it is the Source and the program runs on the nook. Next we will have to write our new init.rc to mount our own os. Someone will have to help me with some research, but I just thought you should know.
Here are the files:
2nd-init.tar
To recomile with the NDK use the following command:
Code:
/home/<user>/Downloads/android-ndk-r7/toolchains/arm-linux-androideabi-4.4.3/prebuilt/linux-x86/bin/arm-linux-androideabi-gcc --sysroot=/home/<user>/Downloads/android-ndk-r7/platforms/android-14/arch-arm/ 2nd-init.c
GOOD LUCK
Click to expand...
Click to collapse
Hmm, if only another developer told you how to cross compile. Oh wait! Haha, congrats Loglud.
Loglud said:
So I have been working on this for a while trying to get things to cross compile, and i got this to compile it is the Source and the program runs on the nook. Next we will have to write our new init.rc to mount our own os. Someone will have to help me with some research, but I just thought you should know.
Here are the files:
2nd-init.tar
To recomile with the NDK use the following command:
Code:
/home/<user>/Downloads/android-ndk-r7/toolchains/arm-linux-androideabi-4.4.3/prebuilt/linux-x86/bin/arm-linux-androideabi-gcc --sysroot=/home/<user>/Downloads/android-ndk-r7/platforms/android-14/arch-arm/ 2nd-init.c
(Thanks to Indirect)
GOOD LUCK
Click to expand...
Click to collapse
Awesome! Great job Log. Big Step in the right direction.
Nice. 10char.
So, did development stop on this? how is it installed?
AdamOutler said:
So, did development stop on this? how is it installed?
Click to expand...
Click to collapse
I want know it too... >.<
Jeeze idk, i completely forgot about this thread until you guys posted on it. I never did to much testing. This was mostly done in concurrence with the Kexec-Mod since i had the toolchain up and running. If i remember correctly it did generate the second init file, don't know if it ever loaded it, but i can work on it some more if people want. I was hoping some one would point me in the direction they needed me to go with this.
Loglud said:
Jeeze idk, i completely forgot about this thread until you guys posted on it. I never did to much testing. This was mostly done in concurrence with the Kexec-Mod since i had the toolchain up and running. If i remember correctly it did generate the second init file, don't know if it ever loaded it, but i can work on it some more if people want. I was hoping some one would point me in the direction they needed me to go with this.
Click to expand...
Click to collapse
I prefer first a compatible Custom Recovery
I compiled, but I don't know how adapt the hijack...
what is 2nd-init? Is it a bootloader? kernel? recovery? where does it come in the boot sequence?
http://nookdevs.com/Dump_NookTablet_Partitions
AdamOutler said:
what is 2nd-init? Is it a bootloader? kernel? recovery? where does it come in the boot sequence?
http://nookdevs.com/Dump_NookTablet_Partitions
Click to expand...
Click to collapse
http://and-developers.com/2ndinit
AdamOutler said:
what is 2nd-init? Is it a bootloader? kernel? recovery? where does it come in the boot sequence?
http://nookdevs.com/Dump_NookTablet_Partitions
Click to expand...
Click to collapse
Pratically.. it's the method with many motorola phone (with locked bootloader) can run custom roms like cyanogemod.
However the problem is it requires kexec mod.
Sent from my ADR6425LVW using xda premium
Loglud said:
However the problem is it requires kexec mod.
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
Sorry, but you're wrong.
From this source use the Hijack method. This mean you can instal a custom rom, but you can't replace the kernel or bootloader.
From the source:
It's also important to remember that 2nd-init does NOT unlock the bootloader, nor does it allow you to run a custom kernel. It simply allows us to utilize the kernel that is there for our own means
Click to expand...
Click to collapse
That method is good enough to run CM9 and it's relative simple to port.
The kexec method is something different, but better: is a system call that enables you to load and boot into another kernel from the currently running kernel.
kexec performs the function of the boot loader from within the kernel.... essentially a hijack to allow us to call another kernel as a function of the stock one, allowing us to bypass the locked bootloader.
Source
Someone has had success with this method
See this twitter feed:
http://twitter.com/androidnemith
@AndroidNemith just have seen your photo with the CWM on the Nook tablet. How did you do that since the Bootloader is locked ?
@PetePetePete1 Hijacking . Same way moto defy and others are doing it. Right now i am kicking it manually looking for a better way now.
@AndroidNemith can you show your current state XDA developers, because they are still searching for a method to get a custom bootloader
@PetePetePete1 It's not quite ready and i got distracted by NookColor bits. If you want to see what i am doing look at the Moto Defy CM
Click to expand...
Click to collapse
I take no credit for finding this, as I haven't been talking with @AndroidNemith
HMG10 said:
See this twitter feed:
http://twitter.com/androidnemith
I take no credit for finding this, as I haven't been talking with @AndroidNemith
Click to expand...
Click to collapse
That would be me then I was also asking AndroidNemith if he could show his current state on XDA but he didn´t reply back yet :S Oh yeah and nice picture
http://yfrog.com/nxrztiij
Please...
Maybe we can do some little workshop for absolute beginners...
Builds take up to 4h now
Click to expand...
Click to collapse
After I have read this...
Can someone please post more about creation/compile time?
How to increase Speed of compile?
Only PC Hardware?
Compiler?
Linux or Win as OS for Compiler?
Thanx in advance.
Best Regards
I think that how faster the CPU how faster it builds, and I think that more ram also decrease build time? in combo with CPU
and your internet download speed, you must download files
There are hundreds of tutorials howto compile kernel/platform around on XDA. Really it's just matter of using Search.
Building up kernel can take around 5min~2h, building platform can take around 30min~8hours. Everything depends on amount of RAM and CPU cores u got, I'm building up kernel in around 10minutes and platform in about 1h 30mins, got some laptop intel i7 + 4GB RAM. There's way to speedup platform compilation using CCACHE, but it costs alot of disk space.
Compiling is impossible under Windows, even with Cygwin it would be hard to achieve. I'd recommend Ubuntu 10 or 11 (rather avoid 12). Mac will do too.
Compiling is impossible under Windows...
Click to expand...
Click to collapse
Maybe if I have time... this year... I will try to boot somewhere Linux...
Forgotten... maybe last time Suse loooong time ago installed...
Maybe 4 or 5 years ago...
I am Win Fanboy...
Really it's just matter of using Search.
Click to expand...
Click to collapse
I have not sooo much time for research by my self...
So I thought if we have soo many users in wait status...
They could translate for me in easy words...
Anyway... why not make Workshop for S8500 ...
If for each Android handset many Tutorails exists...
Then easier copy and paste and replace I9000 by S8500 if mandatory...
Not our main Devs...
I mean our enthusiastic waiters...
We have more then 10 users in this Android section... I hope...
Best Regards
I'd recommend Ubuntu 10 or 11 (rather avoid 12). Mac will do too.
Click to expand...
Click to collapse
http://www.ubuntu.com/download
Lesson 1...
Download Ubuntu...
Where to find recomended Version 10 or 11
Thanx in advance.
Best Regards
Why not Ubuntu 12.04 ?
Is there any problem with it ?
@adfree
Here you cand download any version you want
http://releases.ubuntu.com/
Sorry, you are limited to 8 thanks per day
Click to expand...
Click to collapse
Thanx cyber kamikaz
Maybe we could collect all Links to need files/Compiler etc...
Thanx in advance.
Best Regards
adfree said:
Maybe we could collect all Links to need files/Compiler etc...
Click to expand...
Click to collapse
There is a small tutorial made by Mike to install all the applications you need and to compile the sources from his repository
http://polishblood.pl/?page_id=9
I'm not sure if it's also for wave.
yakub234go said:
Why not Ubuntu 12.04 ?
Is there any problem with it ?
Click to expand...
Click to collapse
Many people, including me are experiencing various issues in Ub 12. These are usually fixable simple way but always... it's annyoing.
I would recommend you to use Ubuntu 11.
And download Code Sourcery 2009 which is mandatory for this badadroid project.
And here is a pretty good guide for you,
Link: http://forum.xda-developers.com/showthread.php?t=1186409
That tutorial includes the guide to install Ubuntu also.
If you get stuck anywhere post here or just PM me, i will try to do my best
A note on CodeSourcery2009 - it also isn't fully compatibile with our sourcetree and may fail during compiling WLAN drivers. I switched to AOSP toolchain lately and it works like charm. HOWTO there
http://source.android.com/source/building-kernels.html
New year, new attempt...
Maybe someone else is now able to compile own zImage and can give step by step instructions for noobs... like me.
Screenshots allowed.
Also hints how to download sources are welcome. :angel:
Also links etc... feel free to write most usefull hints.
Thanx in advance.
Best Regards
adfree said:
New year, new attempt...
Maybe someone else is now able to compile own zImage and can give step by step instructions for noobs... like me.
Screenshots allowed.
Also hints how to download sources are welcome. :angel:
Also links etc... feel free to write most usefull hints.
Thanx in advance.
Best Regards
Click to expand...
Click to collapse
I think that you are asking too much and maybe it is time to make the guide yourself . For some devices you can find this kind of "spoon fed" guide, but for most devices you have to figure out how to do most of this your self. The spoon feeding guides can be really helpful depending on how close they are to your own device, but you will actually have to search for them. Another great place to start is xda-university. It took me a few minutes to find this: http://xda-university.com/as-a-developer/getting-started-building-a-kernel-from-source Perhaps this is would be a good place to start....
Need 64bits Linux
Maybe this would help http://source.android.com/source/building.html
adfree said:
New year, new attempt...
Maybe someone else is now able to compile own zImage and can give step by step instructions for noobs... like me.
Screenshots allowed.
Also hints how to download sources are welcome. :angel:
Also links etc... feel free to write most usefull hints.
Thanx in advance.
Best Regards
Click to expand...
Click to collapse
I can make such a TUT & will make one once i got free time
Best Regards
1 "problem" fixed...
"Working" with GitHub files...
If you follow 1 post in this Thread...
http://forum.xda-developers.com/showthread.php?t=1851818
FAQ IS RIGHT HERE, CLICK AND READ BEFORE POSTING
Click to expand...
Click to collapse
Clickclick... then you are here:
http://code.google.com/p/badadroid/wiki/FrequentlyAskedQuestions
Left site... Project Repositories Updated May 2, 2013
http://code.google.com/p/badadroid/wiki/ProjectRepositories
For instance Kernel... aka zImage...
Kernel GIT repository
https://github.com/Rebell/android_kernel_samsung_wave/
I swear I have not ever seen this ZIP Icon... maybe drunken or drugs or blind or braindead or all things together.
I thought only for registered users... but no Account needed to Download all files with 1 click.
My downloaded file android_kernel_samsung_wave-jellybean.zip is 124 MB big...
Later I will check how big is Platform repository...
Best Regards
http://forum.xda-developers.com/showthread.php?t=2276481
:good:
Thanx mylove90
Thanx Tigrouzen
I need more time for my Linux test PC... because 64 bit seems mandatory...
Meanwhile after I saw this today...
If you look into about phone you will notice that compile date is 8 May
Since that time i was trying several stuff like adding SmartassV2 governor but now my sources are corrupted !
I was trying to commit the changes on my repo but it didn't appear :S
Click to expand...
Click to collapse
Again few stupid questions...
Backup/Safety related...
1.
If 10 GB uncompressed is downloaded...
Someone tried to compress/Zip source ?
Maybe as ZIP archive less then 1 GB...
Then maybe not the latest Version, but better then downloading 10 GB ever and ever again...
2.
How to achieve Full Download of 10 GB as Windows Fanboy?
First success with 120 MB Zip was here:
http://forum.xda-developers.com/showpost.php?p=41350507&postcount=18
Is here 1 Button for Windows user...
Thanx in advance.
Best Regards
Adfree
You can download the sources but you have to understand how local_manifest.xml does it
But why to bother doing that while you can't compile on windows ?!
The sources downloaded are compressed already....just try to follow the TUT and you will find out that there is .repo folder with compressed sources downloaded
I guess i am just too noobish to Linux and don't understand how to fix my sources yet
Currently my main issue is time :S....I've to study to pass this year :S
Maybe other experts right here can help us
Best Regards
Hi..im a quite fresh android user after having iphone for the last 4 years....i have a huawei ideos x5 pro that for me at least is a great phone for his price..but the major problem is that we don't have devs for our phone...only one chinese guy that develops roms for at least 7 phones so we aren't his major concern...so im asking if there is a complete noob guide for compiling rom..fixing rom.
i have to tell you and please don't flame that even that i have knowlage over pc's i haven't any knowlage over programming and coding!!so if any guide can't help me it will be ok...i try! but if there is a guide that can help me step by step to understand the basics and then with a bit of research can figure it out the rest it will be helpful!!
Thanks!!
Sorry for my english!
http://lmgtfy.com/?q=make+android+custom+ROM
thewadegeek said:
http://lmgtfy.com/?q=make+android+custom+ROM
Click to expand...
Click to collapse
Yeah i know that...im asking for a user's entirely noob guide...1st time user guide...google is full with guides but not so novice guides!!
There isn't a "type this, click this, A,B,C" guide. That would be called just copying somebody's work. What you need to do is start reading through ALL the guides you can find, compile a kernel, read smali, change colors, mod pictures, unpack-repack boot.imgs. I can't give you a link and say "Read this tutorial and you will be a developer", that's just not how it works.
thewadegeek said:
There isn't a "type this, click this, A,B,C" guide. That would be called just copying somebody's work. What you need to do is start reading through ALL the guides you can find, compile a kernel, read smali, change colors, mod pictures, unpack-repack boot.imgs. I can't give you a link and say "Read this tutorial and you will be a developer", that's just not how it works.
Click to expand...
Click to collapse
ill give it a try thanks!!!
After reading a lot of guides...i can say that i didnt find anything so hard but i haven't try it so far so i can say for sure...but i stuck in one thing...somewhere on all the guides it sais to find your device tree...and many guides that are from samsung or htc using some github and some cyanogen brances...i have an huawei ideos x5 pro...where i will find those trees?do i need them for making the android source work with my device or the source from google is universal meaning that when im build the rom from sources.android.com the rom will work in my device??
pikachukaki said:
After reading a lot of guides...i can say that i didnt find anything so hard but i haven't try it so far so i can say for sure...but i stuck in one thing...somewhere on all the guides it sais to find your device tree...and many guides that are from samsung or htc using some github and some cyanogen brances...i have an huawei ideos x5 pro...where i will find those trees?do i need them for making the android source work with my device or the source from google is universal meaning that when im build the rom from sources.android.com the rom will work in my device??
Click to expand...
Click to collapse
You must have a device tree... If not you have to build your own... The rom built from source.android.com will only work with google nexus devices...
adiles said:
You must have a device tree... If not you have to build your own... The rom built from source.android.com will only work with google nexus devices...
Click to expand...
Click to collapse
So my hands is tied...nice!!there is no way that i can make a tree i don't have so much knowlage!! :/ too bad!!
pikachukaki said:
So my hands is tied...nice!!there is no way that i can make a tree i don't have so much knowlage!! :/ too bad!!
Click to expand...
Click to collapse
look for a device with similar hardware and copy that device tree, then try to make adjustments to get it working and voila. and ask that one dev if he can give you his device tree
I have read all things in xda about my u8800, and xda helps me know about root, install cwm, uprom..etc. thank all of you, thank xda
-Sent from my u8800-
Me Too!
lemonade747 said:
I have read all things in xda about my u8800, and xda helps me know about root, install cwm, uprom..etc. thank all of you, thank xda
Click to expand...
Click to collapse
I'm actually reading everything about my new device, Sony Neo L. This is pretty amazing! XDA rocks!
CrisisCorE said:
look for a device with similar hardware and copy that device tree, then try to make adjustments to get it working and voila. and ask that one dev if he can give you his device tree
Click to expand...
Click to collapse
Hardware we need the same cpu gpu or everything?sensors bt wifi etc?
Sent from my U8800PRO using xda premium
How can i get source code for Vision, since huawei doesnt let you download it?
Sent from my Vision
if u r good at linux, u can try this guide >>> http://handycodeworks.com/wp-content/uploads/2011/02/linux_versus_android.pdf
I compile linux kernels for desktop, but the android kernel is not the same. Cyanogen team and GOOGLE Android developers provides a comprehensive guide on building ur own ROM. But to build ur own OS, u need to understand each component carefully. I don't know abt android, but i am making Linux OS from scratch. I have kernel compiled, tool chain set up, now i am putting apps on it. But android uses DALVIK VM for Java apps, also .... U refer the pdf it will tell u. Once i finish making this OS, i'll focus on Android ROMS. They r similar to Linux OS, but require patches in kernel, a light c lib, new fs, a different vm (dalvik) and different ways of managing i/o interrupts and much more..
this link is on porting android on nokia >> http://www.linuxfordevices.com/c/a/Linux-For-Devices-Articles/Porting-Android-to-a-new-device/
this one is on linux on embedded systems >> http://www.lindusembedded.com/blog/2010/12/07/android-linux-kernel-additions/
Also, sorry to say but learn C/C++/Java . To make ROMS, atleast to make modifications and to understand the kernel u'll need C. Not very hard to learn, Good tuts on Lynda.com and other sites. And be good at Linux. Happy Learning
hello i just want to ask where are touchscreen files and drivers because i found cyanogenmod for similar hardware but only the touch screen is not working so i thought to replace with the working rom for my device
PLEASE HELP ME OUT WITH THIS ONE !
icoolguy1995 said:
hello i just want to ask where are touchscreen files and drivers because i found cyanogenmod for similar hardware but only the touch screen is not working so i thought to replace with the working rom for my device
PLEASE HELP ME OUT WITH THIS ONE !
Click to expand...
Click to collapse
please give me an answer
icoolguy1995 said:
please give me an answer
Click to expand...
Click to collapse
go to the root of your filesystem most root browsers do this anyways and dev then input and it should be the event files
hillconnor13 said:
go to the root of your filesystem most root browsers do this anyways and dev then input and it should be the event files
Click to expand...
Click to collapse
what are event files
i checked there are no files
there is no appropriate answers please i need it pls help me out guys
/sys/android_touch/vendor (open it as a text file)
That tells you the make of your touchscreen. First step to seeing if it is compatible at all.
And you can't just make CM for another device work for yours by replacing a few files. It has to be ported to your device or compiled from source with all the right drivers and binaries. This requires a lot of developer knowledge, which you don't seem to have judging by your questions. So don't go messing around changing files in ROMs and trying to make them work. If you're really interested, learn about porting and compiling from source.
Sent from my Desire HD using xda premium
sashank said:
/sys/android_touch/vendor (open it as a text file)
That tells you the make of your touchscreen. First step to seeing if it is compatible at all.
And you can't just make CM for another device work for yours by replacing a few files. It has to be ported to your device or compiled from source with all the right drivers and binaries. This requires a lot of developer knowledge, which you don't seem to have judging by your questions. So don't go messing around changing files in ROMs and trying to make them work. If you're really interested, learn about porting and compiling from source.
Sent from my Desire HD using xda premium
Click to expand...
Click to collapse
i did not find android_touch in sys folder from root explorer