Related
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!
I'm at my wits end.. I've downloaded and compiled GB 2.3.5 to find no auto-rotate on my 9020A NS.. So I downloaded 2.3.4 and compiled that, STILL no auto rotate..
I downloaded and extracted into the code the 4 binaries from google but the accelerometer isnt among them.
Is this a problem for the AOSP builds of 2.3.4 and 2.3.5?
Am I nuts?
Is there a patch?
Any info would be awesome.
Take libakm.so from stock rom and put it in your build.
Worked perfectly! Thanks a bunch Pete!
As this thread floats into oblivion, if there is any interest in a unmodified completely 100% AOSP compile of 2.3.5 for the Nexus S, (I couldnt find one that was 100% unmodified, perhaps I didnt look hard enough) everyone let me know I'll produce a cwm zip of my build. I realize AOSP is easy for the semi initiated, but some people might not have the time/desire/knowhow,etc..
My goal of starting this is to port over some aspects of Honeycomb I like, including the launcher, lockscreen and what not by modifying existing functioning gb code..
Hopefully I'll finally make my first dev ROM in a couple of weeks.
Thanks again to Pete for the accelerometer fix.
Hello respected Developers ,
Jelly Bean is released today with some new and important features. Nexus ROM is already available for download. Since Jelly Bean brings updated UI and few new features only it may be possible to port Nexus ROM.
Kindly consider its possibility and reply
Thank you all !
Here is direct download link
http://goo.im/roms/fabolous/maguro/bigxie_JRN84D_rooted_busybox_deodexed.zip
Hmm...so I was right. It can be ported.
Jelly Bean ported to HTC One X http://forum.xda-developers.com/showthread.php?t=1737736
I hope so.
I'm not a Developer, but I hope so :good:
nothing will be done until the source code is released (google said mid july)
Guys, chill. It is best we wait until ics is fully developed with the kernel 3.x before we talk about this. I am sure that this needs ICS as base. I have been researching about this jellybean update the whole day. it is somewhat a small update to the ICS with automatic widget resizing, GoogleVoice (commandable just like siri) and also less lag... this is just like a froyo to gingerbread update as they said in vid reviews.
now our future is on the 3.X kernel:good:
Hi
Did anyone noticed that kernel for jelly bean port on HTC one x.
It is 2.6.xxx
Sent from my GT-I9003 using Tapatalk
neil05 said:
@vishal
You are not the moderator in this forum. So don't act like a mod
Cheers:beer:
Click to expand...
Click to collapse
No, but I am
Thread moved and cleaned. Development section is only for roms/kernels, etc. being worked on with some kind of bootable image. This is not. (First hint was the title ends in a question mark)
Keep it polite guys.
---Jay--- From the Nexus
The porting Guide can be found here
http://forum.xda-developers.com/showthread.php?t=1739561
Thanks Jay
And apologies for posting in wrong section. Everyday we learn something new
Thanks !
Maybe...
I'm not a developer and i don't know how to port a ROM. However, I think porting an I9000 Jellybean Rom will be easier since I9000 and I9003 has similar specs.:laugh:
chung1213 said:
I'm not a developer and i don't know how to port a ROM. However, I think porting an I9000 Jellybean Rom will be easier since I9000 and I9003 has similar specs.:laugh:
Click to expand...
Click to collapse
an i9000 stock rom is impossible because samsung wont release one. and jb code is not out until mid-july. let's wait for cm10 to start
Sent from my Transformer Prime TF201 using xda app-developers app
NEXUS S got the jelleybean working
http://forum.xda-developers.com/showthread.php?t=1738756
Galaxy s are on there way to port jellybean.
Vasishta Reddy said:
NEXUS S got the jelleybean working
http://forum.xda-developers.com/showthread.php?t=1738756
Galaxy s are on there way to port jellybean.
Click to expand...
Click to collapse
i9003 will follow, once kernel 3.0 + ics is completely ported and good for day-to-day basis ^^
Everytime it happens that when we work on perticular version of cynogenmod then suddenly new version of galaxy device releases or new version of android releases then current development looks old to us. So we leave it in incomplete stage & we move forward to achieve new things of new cynogenmod but again everytime same story repeats & thats why we have so many incomplete cyanogenmod roms.
I want to suggest that if the developers are working on ICS cm9 then they must work on first to achieve kernel 3.0 & get stable cm9. People now should not rush to achieve JB leaving behing cm9 work incomplete. "One time one task"
vishal24387 said:
Everytime it happens that when we work on perticular version of cynogenmod then suddenly new version of galaxy device releases or new version of android releases then current development looks old to us. So we leave it in incomplete stage & we move forward to achieve new things of new cynogenmod but again everytime same story repeats & thats why we have so many incomplete cyanogenmod roms.
I want to suggest that if the developers are working on ICS cm9 then they must work on first to achieve kernel 3.0 & get stable cm9. People now should not rush to achieve JB leaving behing cm9 work incomplete. "One time one task"
Click to expand...
Click to collapse
K bro,why to waste time in partially working ports lets wait for source code's release .
Vasishta Reddy said:
K bro,why to waste time in partially working ports lets wait for source code's release .
Click to expand...
Click to collapse
Source code of jelly bean is of no use for us until we get kernel 3.0. Because building jelly bean rom or cm10 based on 2.x kernel is again a waste of time & again one more incomplete rom
vishal24387 said:
Source code of jelly bean is of no use for us until we get kernel 3.0. Because building jelly bean rom or cm10 based on 2.x kernel is again a waste of time & again one more incomplete rom
Click to expand...
Click to collapse
You're right on that one bro.
Regarding porting Jelly Bean, it's another challenge for our great developers. And it is possible since it has already started coming on many devices. Another point is that JB does not introduce System level changes like ICS but a major update over it. So JB should easier than ICS.
Regarding Incomplete ROMs, each and every developer has his own set of skills and can't do what other can do and we must respect this. What dhiru can do is not necessarily doable by others too. But this should not come as deterrent for some quality work like MIUI and AOKP. If we would have kept waiting for 'Perfect and Complete' ICS then we would never have these great ROMs. These guys are working within known limitations and doing a great job. So i would always encourage new challenges, innovations, ideas, development and ROMs. We again might have many things not working on JB Ports but that's what fuel the developers to take up challenge and win it. Remember the first ICS and MIUI Ports ? And look today Thankfully Lolation, Frank, UT36104, Vurrut did not get discouraged by current limitations and went on to port these great ROMs and fix bugs. Thank You guys
Take every new thing as a challenge and give your best with whatever you have in hand instead of crying of what's not there or what will come someday
Good Day guys
silentvisitor said:
Regarding porting Jelly Bean, it's another challenge for our great developers. And it is possible since it has already started coming on many devices. Another point is that JB does not introduce System level changes like ICS but a major update over it. So JB should easier than ICS.
Regarding Incomplete ROMs, each and every developer has his own set of skills and can't do what other can do and we must respect this. What dhiru can do is not necessarily doable by others too. But this should not come as deterrent for some quality work like MIUI and AOKP. If we would have kept waiting for 'Perfect and Complete' ICS then we would never have these great ROMs. These guys are working within known limitations and doing a great job. So i would always encourage new challenges, innovations, ideas, development and ROMs. We again might have many things not working on JB Ports but that's what fuel the developers to take up challenge and win it. Remember the first ICS and MIUI Ports ? And look today Thankfully Lolation, Frank, UT36104, Vurrut did not get discouraged by current limitations and went on to port these great ROMs and fix bugs. Thank You guys
Take every new thing as a challenge and give your best with whatever you have in hand instead of crying of what's not there or what will come someday
Good Day guys
Click to expand...
Click to collapse
I completely agree. People learn by doing hands on, and what I mean is building roms. Discouraging them just because you want them to complete a rom is very selfish, everybody has to start somewhere. Not everybody has sufficient knowledge in android programming to help with completing roms, i believe people feel a sense of accomplishment after building their first rom, only to be struck down by others that want a complete rom. I just want to say guys, don't discourage new roms please, think about other people's feelings. Thanks.
Cheers
Sent from my GT-I9003 using xda app-developers app
bscraze said:
I completely agree. People learn by doing hands on, and what I mean is building roms. Discouraging them just because you want them to complete a rom is very selfish, everybody has to start somewhere. Not everybody has sufficient knowledge in android programming to help with completing roms, i believe people feel a sense of accomplishment after building their first rom, only to be struck down by others that want a complete rom. I just want to say guys, don't discourage new roms please, think about other people's feelings. Thanks.
Cheers
Sent from my GT-I9003 using xda app-developers app
Click to expand...
Click to collapse
Its not about discouraging new rom development. Its about how well we concentrate on each thing to complete it. I am not saying that we should stuck to only one perticular rom development. But remember guys that google will not take a pause for us so that we can complete current cynogenmod rom. New versions of android will contineously come out by google but we must have to think whether we should run behind new roms or should we first build a base kernel 3.x without which every future development will remain incomplete...???
Please do not spam this thread with useless questions, thank you posts etc.
You can use (or create) a thread in the general section for that.
I will subscribe to this thread and have a look every now and then if my assistance is needed - but if this thread gets too cluttered with non-development related crap I'll stop doing so.
I found something nice accidently.
The Motorola Atrix - another T2 phone without an ICS release - got pretty well working CM10 and CM10.1 ROMs (w/o hwa of course).
What they did is similiar to the "hackfest" CM10 by benee (based on arcee's CM9 port), but they worked even further.
Here's the manifest:
https://github.com/epinter/android/tree/cm-10.1-olympus
What needs to get done:
Setting up the P999 device tree according to this repo:
https://github.com/epinter/android_device_motorola_olympus/commits/cm-10.1
The most interesting part in here is the BoardConfig.
The hackfest CM10 P990 repo might help here as well - I don't think the P999 ones still exist.
https://github.com/tonypp/android_device_lge_p990/tree/hackfest_cm10
https://github.com/tonypp/android_device_lge_star-common/tree/hackfest_cm10
The commits just need to get merged into the P999 one (+ the storage paths need to get adapted.
I think Mazout360 has a hackfest kernel repo (which lacks proper commit authorship, but better than nothing).
With this working and some compile fixes you should already get it booting. :good:
Thanks to the Atrix guys it's not too much or too hard work.
Without owning a P999 I won't work on it, this would be too messy. But I will at least follow this thread and see if I can do some quick help.
But if some devs are still interested this is a v ery good starting point.
Note: This is totally unrelated to the work adampk and Mazout are doing to use the P990 ICS release to get CM10/CM10.1 working on the P999.
We're talking about a no-hwa release here, same as hackfest (read: all CM9 / CM10 ROMs with working signal) - but more stable and up-to-date.
tonyp said:
Please do not spam this thread with useless questions, thank you posts etc.
You can use (or create) a thread in the general section for that.
I will subscribe to this thread and have a look every now and then if my assistance is needed - but if this thread gets too cluttered with non-development related crap I'll stop doing so.
I found something nice accidently.
The Motorola Atrix - another T2 phone without an ICS release - got pretty well working CM10 and CM10.1 ROMs (w/o hwa of course).
What they did is similiar to the "hackfest" CM10 by benee (based on arcee's CM9 port), but they worked even further.
Here's the manifest:
https://github.com/epinter/android/tree/cm-10.1-olympus
What needs to get done:
Setting up the P999 device tree according to this repo:
https://github.com/epinter/android_device_motorola_olympus/commits/cm-10.1
The most interesting part in here is the BoardConfig.
The hackfest CM10 P990 repo might help here as well - I don't think the P999 ones still exist.
https://github.com/tonypp/android_device_lge_p990/tree/hackfest_cm10
https://github.com/tonypp/android_device_lge_star-common/tree/hackfest_cm10
The commits just need to get merged into the P999 one (+ the storage paths need to get adapted.
I think Mazeout360 has a hackfest kernel repo (which lacks proper commit authorship, but better than nothing).
With this working and some compile fixes you should already get it booting. :good:
Thanks to the Atrix guys it's not too much or too hard work.
Without owning a P999 I won't work on it, this would be too messy. But I will at least follow this thread and see if I can do some quick help.
But if some devs are still interested this is a v ery good starting point.
Note: This is totally unrelated to the work adampk and Mazeout are doing to use the P990 ICS release to get CM10/CM10.1 working on the P999.
We're talking about a no-hwa release here, same as hackfest (read: all CM9 / CM10 ROMs with working signal) - but more stable and up-to-date.
Click to expand...
Click to collapse
Well, guess I'm on it.
Will try this tomorrow, thanks!
EDIT : After my first try, it didn't compile directly. It seems like they didn't update their specific sources with newer CM changes. I'll work on this
Hey guys, I have been looking for a jb miui ROM for this device and i cant find one, i know there are some ics miui ROMs, but i would really like a jb miui ROM.
There is one for the vibrant, can I use it for my Galaxy s 4G or can anyone port it to our device?
Vibrant MIUI JB ROM:
http://forum.xda-developers.com/showthread.php?t=2289234
Thanks
i'll build it when miui comes out with miui 4.2
airfluip1 said:
i'll build it when miui comes out with miui 4.2
Click to expand...
Click to collapse
Thank you i will be looking forward to it.
Beast said he would do it.
sent from me
that's been in my queue for a while along with aokp aries and paranoid android.
airfluip1 said:
i'll build it when miui comes out with miui 4.2
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2313073
Just because there are some homebrew ports doesn't mean that MIUI is 4.2 yet.
http://en.miui.com/download.html
Official Downloads
Author : MIUI Developer Team
Kernel : Android 4.1
Latest update : 3.6.21
Download : http://www.miui.com/download.html
Language : Chinese and English
Click to expand...
Click to collapse
Why does it matter ? We use unofficial ROMs anyway...
sent from me
That's like saying that since a car, airplane, and weed-whacker all run on gas, you should just put the same stuff in each. Actually, the unofficial ROMS is a more tenuous connection than my gas connection. It's more like saying that since a bullet train, horse, and diesel bus all run on fuel, the fuel which goes into each shouldn't matter. It's all fuel.
Hey, you could (please don't) use an unofficial Vibrant ROM too. That's unofficial. What's the difference? The difference is that it won't work. And might brick your phone. That's bad.
Our only current Aries kernel is 4.2.2 and still has issues. MIUI is still 4.1.2 and would introduce an entirely new set of issues tied into GPS, Bluetooth, and so forth if/when a 4.1.2 Aries kernel was compiled. Does that make it impossible? No. But it means that as the build impetus - when MIUI is 4.2 - has not happened yet... it's not a great use of time yet. Unless one of the devs wants it. In which case, MIUI being not-updated is something they don't need to be hammered over the head with.
http://forum.xda-developers.com/showthread.php?t=2313073
4.2.2?
Port. If YOU see source linked from that page so our devs could actually do something useful to build that...
Hi Theraze
I have to disagree with you.
Port is not a dirty word and most of our ROMs are actually ports and not built from source. Furthermore, MIUI ROM is usually ported and not built from source and only recently did Xiaomi open their sources for the public. Even more than that, both MIUI versions brought to us by Beast were ports from Nexus and not built from source.
Now, regarding the incompatibility between kernel & OS - if it works on Nexus, I assume the adjustments were made, so one can enjoy both 4.2.2 & MIUI benefits. There is no logical reason why it couldn't be ported to our beloved device.
sent from me
I'm not saying it can't be done. I'm saying that our build-from-source dev who asked you to let him know when it hit 4.2 hasn't had his request met.
Does that mean that someone (him or another dev) CAN'T port it? Nope. But it makes it a lot less likely that air can just pull the source in and compile it using the Aries bits if the buildable MIUI is still only 4.1.2 and our Aries is 4.2.2 instead.
Again, I think we're agreeing on the general bits... yes, this is possible. But airfluip1 asked to be notified when buildable MIUI was 4.2.2 and that's when he said he'd build it. Not port it.
I don't care if a ROM is ported or built from source.
I will try to play with porting it myself.