Am I the only one who is unhappy with the slim pickings of ROMs that are available for the SK4G?
Does anyone know anything about an ASOP ROM?
It's AOSP (Android Open Source Project) and you're not the only one not happy with the current SK4G options. I personally want MIUI or CM7, but seeing as we're currently stuck with Froyo, we'll have to see what the devs can cook up.
Sent from my SGH-T839 using XDA App
For future reference, questions go in the General forum, not the Development Forum.
As for AOSP or MIUI, I know that AyoTeddy and Revolution are currently working on separate MIUI roms, and for AOSP, I'm working on that, but not sure exactly what you want from AOSP that's different from what we have?
If you are unhappy with the selection of ROMS here, you are always welcome to make your own, android is open source for a reason.
sduvick said:
For future reference, questions go in the General forum, not the Development Forum.
As for AOSP or MIUI, I know that AyoTeddy and Revolution are currently working on separate MIUI roms, and for AOSP, I'm working on that, but not sure exactly what you want from AOSP that's different from what we have?
If you are unhappy with the selection of ROMS here, you are always welcome to make your own, android is open source for a reason.
Click to expand...
Click to collapse
If they want the real miui we will need some sort of aosp gingerbread to start with and a custom CM7 kernel or something.. Since we dont have either yet I guess we'll have to make the best out of what we have now like we have been. But those wanting a taste of miui may like what I have planned for my next release.
Sent from my SGH-T959 using XDA App
ayoteddy said:
If they want the real miui we will need some sort of aosp gingerbread to start with and a custom CM7 kernel or something.. Since we dont have either yet I guess we'll have to make the best out of what we have now like we have been. But those wanting a taste of miui may like what I have planned for my next release.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
And so anticipation had set in, i can't wait ayoteddy. im very excited. SMX was great, and SMGC was awesome, and now with this? whewwww. think i better go lay down, lol.
I'm also interested in porting CM7 to Sk4g cause I'm used to when I had G1 and now I'm using Sk4g without it.
I have programming skill and understanding of linux architecture. I've read about android architecture and AOSP and how to build Cyanogen from source. I'm running a tech firm (about 30 employees) - we are developing games that's why I don't have enough time to port it faster but I'm going to do it in a month or two.
So, I need help from experienced dev for android who is willing to build AOSP rom for Sk4g.
Here is what I'm going to do:
1) I'm gonna try to build Kd1 rom from source (there is an opensource code from samsung) and flash it to my Sk4g
2) Change the platform in original source to AOSP 2.2 and remove all TMOBILE apps - then build and flash
3) I'll try to find all hardware specs of the phone to compare with other samsung devices. It can help to exctract proprietary drivers of the phone. I think that the drivers are commonly the same, but I need to identify it.
After that I'm gonna upgrade to AOSP 2.3 but I don't have enough knowledge right now. Can some experienced devs answer the questions:
1) Are the linux kernels of AOSP 2.2 and 2.3 identical?
2) Can I use device drivers from 2.2 on 2.3?
If someone is interested in this project - please let me know and let's start the job. I think that my progress wouldn't be fast due to lack of time.
Thank you for joining the Sidekick 4G section , & we welcome you but if you want you could pause the game's for the ROM if anything & Question 1 is a no & Question 2 no cause they have to be compiled with the 2.3 kernel .
- Said by Sduvick
jmpz said:
I'm also interested in porting CM7 to Sk4g cause I'm used to when I had G1 and now I'm using Sk4g without it.
I have programming skill and understanding of linux architecture. I've read about android architecture and AOSP and how to build Cyanogen from source. I'm running a tech firm (about 30 employees) - we are developing games that's why I don't have enough time to port it faster but I'm going to do it in a month or two.
So, I need help from experienced dev for android who is willing to build AOSP rom for Sk4g.
Here is what I'm going to do:
1) I'm gonna try to build Kd1 rom from source (there is an opensource code from samsung) and flash it to my Sk4g
2) Change the platform in original source to AOSP 2.2 and remove all TMOBILE apps - then build and flash
3) I'll try to find all hardware specs of the phone to compare with other samsung devices. It can help to exctract proprietary drivers of the phone. I think that the drivers are commonly the same, but I need to identify it.
After that I'm gonna upgrade to AOSP 2.3 but I don't have enough knowledge right now. Can some experienced devs answer the questions:
1) Are the linux kernels of AOSP 2.2 and 2.3 identical?
2) Can I use device drivers from 2.2 on 2.3?
If someone is interested in this project - please let me know and let's start the job. I think that my progress wouldn't be fast due to lack of time.
Click to expand...
Click to collapse
Revolution, thanks for relaying my responses.
jmpz, I tried building the source before, but was unable to build it completely, but that was possibly because of some errors with my dependencies. The kernel compiles fine from source, you just need to pull initramfs, or you can get it from Dr. Honk's github.
Thank you for your answers.
So, can anyone enumerate the list of drivers which we should extract from kernel?
I can name these:
1) Keyboard
2) Mic
3) 2 speakers
4) buttons
5) front camera
6) rear camera
7) trackpoint
8) lcd
9) digitizer
10) 3.5 jack
Please correct me and add missing
If I understanding it rightly the key problem is getting proprietary drivers from the kernel. Right?
nope, the key problem is trying to build the system entirely, without any errors, which may be easier with someone following a stock designed build environment. I don't use Ubuntu which is what has the listed dependencies for every tutorial I can find. You can get the drivers out of Dr. Honk's voodoo kernel ramdisk here: http://forum.xda-developers.com/showthread.php?t=1145139
There shouldn't be any problems if you just set up a build environment following the directions in any of the tutorials, then add the platform from the samsung source.
I'm a linuxoid - so these tutorial are for me. Thank you for the link.
By the way, drivers are in Linux Kernel, so I don't think that I need to use Samsung Platform from the source. Instead I wanna use platform from AOSP or Cyanogen. Correct me if I'm wrong.
I think that grabbing drivers from kernel source from samsung would be enough to build the rom.
jmpz said:
I'm also interested in porting CM7 to Sk4g cause I'm used to when I had G1 and now I'm using Sk4g without it.
I have programming skill and understanding of linux architecture. I've read about android architecture and AOSP and how to build Cyanogen from source. I'm running a tech firm (about 30 employees) - we are developing games that's why I don't have enough time to port it faster but I'm going to do it in a month or two.
So, I need help from experienced dev for android who is willing to build AOSP rom for Sk4g.
Here is what I'm going to do:
1) I'm gonna try to build Kd1 rom from source (there is an opensource code from samsung) and flash it to my Sk4g
2) Change the platform in original source to AOSP 2.2 and remove all TMOBILE apps - then build and flash
3) I'll try to find all hardware specs of the phone to compare with other samsung devices. It can help to exctract proprietary drivers of the phone. I think that the drivers are commonly the same, but I need to identify it.
After that I'm gonna upgrade to AOSP 2.3 but I don't have enough knowledge right now. Can some experienced devs answer the questions:
1) Are the linux kernels of AOSP 2.2 and 2.3 identical?
2) Can I use device drivers from 2.2 on 2.3?
If someone is interested in this project - please let me know and let's start the job. I think that my progress wouldn't be fast due to lack of time.
Click to expand...
Click to collapse
I 100% support your efforts. I want Cyanogen on the SK4G badly, but I'm not sure what kind of help a non-programmer like me could do, but do have some experience with flashing phones and such, so if there is anything you need let me know.
If you do get rolling heavily on this, I'd be willing to donate monetarily to your efforts.
If anyone can get CyanogenMod 7 on the Sidekick they would definetely get a donation from me. Id be thrilled. Glad to see its going to be worked on.
Sent from my Sidekick 4G using XDA Premium App!
Hello all, I want to learn how to compile the CM source to get a ROM and then install on my Nexus S.
Could someone help with some steps?
Best regards.
+1
So im trying to get everything up and running on my computer so I can build us all a pure vanilla 4.2 rom. I have been following a guide to setting everything up on Ubuntu 10.04 to build 4.2 roms, my only problem is finding our device tree. I am a bit unsure if I can just use CM's d2vzw device tree or if I need to find another one.
If it does needs to be a different device tree I have found one, https://github.com/Joelz9614/android_device_samsung_d2vzw , but yet again I dont know if it would be better to use CM's device tree or this one. For the time being I am going to use this one until someone chimes in and lets me know which one would be best to use, or if there is another I dont know about that I need to use to build 4.2 .
Thanks in advance guys
I was wondering if anyone could point me in the direction of some information on porting from one version of android to a higher version. Preferably from 1.6 Donut to 2.2 Froyo or 2.3 Gingerbread. Is this even possible?
Also, could anyone tell me what phone I could use that is similar to the Behold II (SGH-t939)? Is the Behold II in the cyanogen repo? If it is, anyone know it's codename?
I have a build environment set up for cyanogenmod, and I followed this guide. I have got to the gpg import and was wondering if the gpg block is device specific somehow or if it is universal.
Tying in to my first question, is whether there is any way I could get the proprietary files and kernel information out of a rom file instead of off the phone. I have a custom rom installed on the phone that isn't working 100% but I don't really want to put the oem rom back on. Unless I absolutely have to.
Also, once I do actually get the proprietary information and kernel stuff, how exactly do I incorporate all that into a new build?
Sorry, I am just starting to learn about android development and need some guidance. Any help would be greatly appreciated.
Thanks
This one is for anyone who has made a rom for the xoom. Im going to attempt to create a rom or at least contribute towards getting L working on our Xooms. ive just got a Nexus 9 so Xoom is up for extreme experimentation.
I need some help to get started on integrating BigPart into the rom, I remember last time the rom wouldnt build because of the partition sizes (I have much better hardware and tools now so mabe i can figure it out when i get home but heads up would be nice )
You need this efi.c in your kernel basically. The patch is integrated at the bottom.
https://github.com/Schischu/xoom-ElementalX/blob/master/fs/partitions/efi.c
Thanks! been a while since ive programmed in C too used to c# and java. any tips on an IDE or editors for aosp?