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!
So, Since the Cyanogenmod source is so big (I heard that it has 19GB), people like us who have gay as slow internet have no chance of even trying to cook a ROM for our unsupported devices.
Since I can't download the whole CM source and I see awesome ROM's out there, I Ported one ROM called Cyanfox (which was made for Samsung S2 i9100) to Samsung Infuse 4G using Beanstalk ROM as a base. I followed a guide which asks me to replace some folders and edit some files. It was walking fine. Then came an update to both the ROMs, Thinking that cince it is a update, it will have the updated apps and source, I tried porting them again but this time Beanstalk updated ROM as a base cause a bootloop while the Beanstalk old ROM works fine as a Base ROM.
Now what I don't get is, why is Beanstalk new ROM not working as a base? (Since the new Beanstalk ROM will have updated Source, I want to use that ROM as my base.)
And the second question is, what files does actually matter when you are Porting or cooking an Android ROM? (I mean like windows works on all kind of PC's all it needs is the drivers right? The drivers actually matter on windows)
And the 3rd question is can I update the source files somehow without downloading the whole 19GB CM source and if possible how?
The 4rth is, I heard from somewhere that boot.img is the file which separates the phones? Then why can't we just port ROM's by replacing boot.img since these two phone's are from the same vendor and it has likely specs. (Which is not possible I think)
I am really really a newbie to this thingies, I just wanted to clear out these things. Sorry for my noobness.
Thanks!
Hello everyone! I am a little new to this, so please take it easy on me. I have actually never created my own Android ROM via the AOSP, but I have opened up Zip files for ROMs other developers have created and have been able to do basics.
I recently bought this device: MPie G7 (gearbest . com/cell-phones/pp_76182.html)
As you can all tell, it is not exactly a very popular phone. So, finding source code for this phone's ROM is basically, impossible. I have also been unable to find the manufactures website address either (anyone have any ideas?).
Anyway, here are my very noob questions. I am obviously planning on hitting base with the AOSP code, but with Lollipop. This poses a new problem to me, because I cannot find the source code, how am I supposed ot create a kernel specific ROM? This thing runs on a MTK, most precisely: MTK6582. It came with Android 4.4.2 (KitKat).
I am also worried about one small other thing, which is the gestures. If my phone is on standby, screen is off, I can do gestures on the off screen to do certain things. Similar to the OnePlus One. But, I am worried I will not be able to do that if I build my own ROM from source.
Anyone have suggestions? Or can possibly help? Thank you very much. All your help is appreciated!
By
omarquazi said:
Hello everyone! I am a little new to this, so please take it easy on me. I have actually never created my own Android ROM via the AOSP, but I have opened up Zip files for ROMs other developers have created and have been able to do basics.
I recently bought this device: MPie G7 (gearbest . com/cell-phones/pp_76182.html)
As you can all tell, it is not exactly a very popular phone. So, finding source code for this phone's ROM is basically, impossible. I have also been unable to find the manufactures website address either (anyone have any ideas?).
Anyway, here are my very noob questions. I am obviously planning on hitting base with the AOSP code, but with Lollipop. This poses a new problem to me, because I cannot find the source code, how am I supposed ot create a kernel specific ROM? This thing runs on a MTK, most precisely: MTK6582. It came with Android 4.4.2 (KitKat).
I am also worried about one small other thing, which is the gestures. If my phone is on standby, screen is off, I can do gestures on the off screen to do certain things. Similar to the OnePlus One. But, I am worried I will not be able to do that if I build my own ROM from source.
Anyone have suggestions? Or can possibly help? Thank you very much. All your help is appreciated!
Click to expand...
Click to collapse
Why don't you list down some of the specifications of your phone and compare them with other mediatek devices!!!
That way if u have the stock ROM of the phone then u can port ROMs from another mediatek device like xolo q700i which has a dedicated thread!!! xolo q700i has many different number of ROMs !!! That way by zip based theming and porting you might be successful in at least creating a ROM for yourself which u can use as a base for different roms!!!
The way I see it if you don't have source or downloadable ROM from your OEM, you have two options:
- like @thecoolster said you could try flashing ROMs from similar devices, and hope you don't end up stuck with a soft brick.
- or, likely your device can be easily rooted (in the settings perhaps?) if it isn't already. Then you can make nandroid to give yourself a stock ROM to cook.
Actually porting your ROM from a developer device tree and AOSP or CM is hard if you are only a hobbyist cook.
Even with a cooked ROM, you'd need a recovery that lets you flash it or you'd have to use SP flashtool and make your own config files for the flash.
Hi everybody,
since my Sensation is on its last legs, I wanted to try building a ROM myself. I've never tried anything of the sort, but given all the resources we have, it shouldn't be impossible for a power user, given the right tutorials? At least, the building part. Making it work perfectly is another thing... But I wanted to at least try. Cyanogenmod 12.1 is a bit too heavy for me, and Slimkat was just perfect.
I've looked everywhere for tutorials on how to build a custom rom for a specific device but I've only found stuff from 2011 that uses android kitchen (deprecated)... Can anybody give me a few pointers?
I thought I could use Slim's Github and maybe have ivanich's device tree as a base?
Hi guys, i am new to android and everything and i have an intention to build a CM based ROM for Hammerhead and i really looking forward on help. I need beta testers and a dev who can help me out, cuz so far iḿ following the rom building guide by this guy called jackeagle, and honestly sometimes it just makes no sense at all so I appreciate any help, don't judge me by any reason.
If you want to build CM rom use CM instructions (there are on cm wiki page). If you want your customizations you need github, fork cm source and modify it.
After it you need to modify local_manifest to use your source, not CM to build rom and voila, everything should work fine.
I know what i'm saying, i've built CM roms for D802, WT19i and some other devices.