Related
Yeah, I know...let's get a stable Froyo first.
But...
I pulled the 2.3.1 (gingerbread) source, and it's currently building. I hit a couple of snags, but I'm off and running so far.
I've also compiled the latest 2.6.36 kernel -- compiled, not tested! Don't get excited just yet.
I'm not going to lie, I'm green to android. But I've worked with Linux professionally for 15+ years. I've been compiling kernels since Linus released 2.0 oh so long ago. Building Linux x86 from scratch (go gentoo linux!) is nothing new to me. But android and arm...ehh...bear with me.
So is anyone else trying to do this? I'd like to collaborate and hear about your progress and any problems you've had. No need to try to reinvent wheels or anything.
Step 1 is getting it to boot...
Here's my 2.6.36 kernel zImage file and .config build if anyone is curious.
My suggestion...change your title to [Dev] AOSP Gingerbread. Start a github or similar repository and get cracking. I'm sure there are plenty of people that would consider jumping on board. With the Nexus S source out, some things shouldn't be TOO hard, but I think porting the CDMA stuff is probably a huge challenge.
plapczyn said:
My suggestion...change your title to [Dev] AOSP Gingerbread. Start a github or similar repository and get cracking. I'm sure there are plenty of people that would consider jumping on board.
Click to expand...
Click to collapse
id jump on board if i knew what i was doing
Glad your focusing on this! I don't think we have to finish froyo to start gingerbread. Not sure how much I can help but hit me up if you need anything done.
Sent from my SPH-D700 using Tapatalk
I glad too see that someone is taking initiative here. My thinking all along is the drivers for froyo will most likely work in someway for gingerbread but without kernel source for froyo yet, I would think you would have to start from ground up. But good luck to you regardless.
Sent from my SPH-D700 using XDA App
This is delicious. Now it only needs sauce.
Everyone can learn from the OP's example. Less posturing more action.
msponsler said:
Yeah, I know...let's get a stable Froyo first.
But...
I pulled the 2.3.1 (gingerbread) source, and it's currently building. I hit a couple of snags, but I'm off and running so far.
I've also compiled the latest 2.6.36 kernel -- compiled, not tested! Don't get excited just yet.
I'm not going to lie, I'm green to android. But I've worked with Linux professionally for 15+ years. I've been compiling kernels since Linus released 2.0 oh so long ago. Building Linux x86 from scratch (go gentoo linux!) is nothing new to me. But android and arm...ehh...bear with me.
So is anyone else trying to do this? I'd like to collaborate and hear about your progress and any problems you've had. No need to try to reinvent wheels or anything.
Step 1 is getting it to boot...
Click to expand...
Click to collapse
About time!
Thank you for working on this. I never really understood the source argument. I just put gingerbread on my old hero and everything works except for camera and screen rotation. It sure as hell doesn't have an official/leaked release or even froyo source. Anyways just ranting about the things I hear. I know I dont have the skills to work on this stuff, so thanks for the effort.
Sent from my SPH-D700 using XDA App
I have it just about booting(;
Sent from my SPH-D700 using XDA App
somedude0608 said:
Thank you for working on this. I never really understood the source argument. I just put gingerbread on my old hero and everything works except for camera and screen rotation. It sure as hell doesn't have an official/leaked release or even froyo source. Anyways just ranting about the things I hear. I know I dont have the skills to work on this stuff, so thanks for the effort.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I agree, I had froyo on my hero long before I even thought about switching to the epic.... and they've made so much progress on gingerbread... I often wonder whether I made the right choice or not going with the epic. Although the evo doesn't have a keyboard and is really square, it gets a lot of attention and has had many official updates. I wish samsung would get off of their asses and just release the source.
I'd love to help out any way I can. I'm not a programmer, but I hve a great understanding on what the issue is. I had a hero before the epic, and they have fully functional froyo despite never having kernel source. One would have to be built, cause I don't think samsung is going to really support us that much longer (if at all) and give us any hope for gingerbread source. The trickiest part is the cdma/wimax radios (wimax still not supported in cyanogenmod for evo).
Sent from my SPH-D700 using XDA App
bubby323 said:
I have it just about booting(;
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Did you build gingerbread from source?
What kernel are you using?
I built a 2.6.36 last night...but the more I thought about it, the more I realized it doesn't do me any good as it is right now.
I've downloaded samsung's kernel source for 2.6.29 and I'm trying to get the modules for the video, radio, etc... to compile with 2.6.36.
The nexus s is using 2.6.35, which is fine when it comes to the video drivers, wifi, and such....but it doesn't do us any good when it comes to 3G because tmobile doesn't use CDMA, so it wouldn't have the same radio kernel modules.
I'm currently running noobnl's cyanogenmod (froyo) on my epic, and that has a 2.6.32.9 kernel. I'll have to take a closer look at how you built that kernel.
Thank you for your initiative OP! I appreciate it.
Sent from my SPH-D700 using XDA App
nerdtaco said:
Thank you for your initiative OP! I appreciate it.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Seconded! I know nothing about developing software but I'm a pretty good test dummy =)
This is pretty kickass. Is there anything in particular you could use for help? I have some limited experience with both linux and android specific kernels.
furysama said:
This is pretty kickass. Is there anything in particular you could use for help? I have some limited experience with both linux and android specific kernels.
Click to expand...
Click to collapse
At this point I don't necessarily need any assistance. But thanks for all the offers!
If I have any questions / requests I'll sure to let everyone know!
Thanks!
The only other question i have is this: how difficult is it to integrate Samsung's 4g drivers into an AOSP mod? Now, I know if we wanted to keep it 100% AOSP it would be... difficult. But is it possible to run a 90% AOSP mod, and just keep the drivers for 4G in the AOSP kernel?
furysama said:
The only other question i have is this: how difficult is it to integrate Samsung's 4g drivers into an AOSP mod? Now, I know if we wanted to keep it 100% AOSP it would be... difficult. But is it possible to run a 90% AOSP mod, and just keep the drivers for 4G in the AOSP kernel?
Click to expand...
Click to collapse
Very very difficult considering it took a team of developers a few months on the EVO to get 4G working with a AOSP kernel. I guess it will depend on how Samsung releases the code, they'll probably not release the 4g code because it doesn't fall under the GPL. If they were to release the drivers as modules that could be included in a kernel, that would be great, but I doubt they'd do that either.
In other words... don't hold your breath...
-Daryel
daryelv said:
Very very difficult considering it took a team of developers a few months on the EVO to get 4G working with a AOSP kernel. I guess it will depend on how Samsung releases the code, they'll probably not release the 4g code because it doesn't fall under the GPL. If they were to release the drivers as modules that could be included in a kernel, that would be great, but I doubt they'd do that either.
In other words... don't hold your breath...
-Daryel
Click to expand...
Click to collapse
The reason it took the CM team so long is because they developed their own drivers from the ground up. I'm willing to bet that it's much easier to rip the drivers out of the kernel we already have than to replicate the work that the CM team did.
The GPL licensing is *why* the CM team developed their own drivers; not because its impossible to get Samsung's code, but because doing so would have violated the licensing terms of Samsung's code and of Cyanogenmod.
I'm not sure that I understand unlocked bootloaders. If there is no lock, why is there not already a gingerbread Rom out for this phone? What is stopping any dev from making a gingerbread Rom?
Sent from my Inspire 4G using XDA App
Having to rewrite that majority of the code for the OS for the infuse might be a little bit of a time constraint.
/sarcasm
But really, there is no proper port out for the infuse and I think the devs are just waiting for a gingerbread ROM to leak out, whether it is from the Canadian Infuse or elsewhere
seh6183 said:
I'm not sure that I understand unlocked bootloaders. If there is no lock, why is there not already a gingerbread Rom out for this phone? What is stopping any dev from making a gingerbread Rom?
Sent from my Inspire 4G using XDA App
Click to expand...
Click to collapse
Simple. The Android userland license doesn't require manufacturers to release source code for the userland portion of the Android stack - the only thing that manufacturers must release source code for is the kernel.
So all device-specific userland code must be reimplemented to get AOSP running on a device.
In many cases, even if someone had device-specific Froyo userland source, a lot of changes were made from Froyo to Gingerbread that require device-specific stuff to be reimplemented. (Look at the state of xdandroid for example - Gingerbread is missing a LOT of stuff that works in Froyo.)
So what is stopping developers from a Gingerbread ROM for the Infuse?
1) Time
2) Time
3) Time
4) Probably lack of documentation on some of the device-specific stuff, fortunately the Infuse is very architecturally similar to the Galaxy S series.
5) Time
6) Lack of the right device in the right developer's hands - the Cyanogenmod guys are so experienced at device porting that between that despite 4), they could likely target the Infuse quickly if one of them had a device. None do yet, there are some threads where people are trying to line up hardware donations.
Please not that to my knowledge, there are ZERO AOSP-source-derived builds for the Infuse for any Android version. All ROM builds currently in existence are "tweaked" variants of the stock Android userland stuff.
Ah hah, I see now. I was assuming this Rom I am using on my inspire was not an official gingerbread Rom, now I know that it must be.
Given samsungs track record for updates. I'm nervous to switch to this phone because it may never receive gingerbread
Sent from my Inspire 4G using XDA App
Unlocked means you can flash anything... Doesn't mean you have that thing to flash.
Sent from my Infuse 4G
MikeyMike01 said:
Unlocked means you can flash anything... Doesn't mean you have that thing to flash.
Sent from my Infuse 4G
Click to expand...
Click to collapse
Got it.
Sent from my Inspire 4G using XDA App
seh6183 said:
Ah hah, I see now. I was assuming this Rom I am using on my inspire was not an official gingerbread Rom, now I know that it must be.
Given samsungs track record for updates. I'm nervous to switch to this phone because it may never receive gingerbread
Sent from my Inspire 4G using XDA App
Click to expand...
Click to collapse
I'm not saying it's impossible to port AOSP GB or the Cyanogenmod source tree to the Infuse, I'm just saying it hasn't happened yet. The Infuse has been out for a few months less than the Inspire, and it took some time for CM7 to become stable on the Inspire too.
In the case of the Inspire it apparently has. The Cyanogenmod team seems a bit HTC-focused, however that's because Samsung seems to be a slightly later player in the Android game. Samsung is clearly interested in catching up - they already donated a GSII to one of the Android devs.
My guess is that the Infuse is similar enough to the GS i9000 that once the right dev gets their hands on one it won't be long. After all, we're using the CWM from the i9000.
The thing to keep in mind, the most important thing actually, is that all of these things take time AND the efforts of a team of people to accomplish. Every well-known/famous/appreciated dev I've ever spoken too about this very topic all says the same thing - they can't do these things alone OR they can do it alone but it'll take forever to get done.
Hence my donation thread
this is my 6th android phone, and I can say it's the only one I'm not in a huge hurry to put a custom ROM on
I loaded ADW EX on it, and the phone's fast enough to run it buttery smooth with no lag. I also absolutely hate Cyanogenmod's camera software, and really enjoy the native camera software on Samsung devices.
I was considering the Evo 3D instead of keeping the Infuse (still in 30 days) but I'm not sure I could move back to an HTC screen. I hated the screen on my mytouch 4g (went there from the Vibrant). Samsung also flat out makes far better camera hardware and software on their phones.
I don't see any reason to get a different phone right now
Its been like almost three weeks since i havent seen anything new from the development area. So i guess we are left behind. What do you guys think? i remember when i used to have the mytouch 4g and the vibrant even the lg g2x and there were a lots of updates, roms, themes, like every day. But with this devices i guess we got stuck with the same things. Sucks!!!
Sent from my SGH-T959V using XDA App
I don't think we're left behind. At least, not yet Currently all the devs have to work with on a GB level are the leaked GB ROMs. That means they have no source code to work with thus what they can do is limited. Also, there has not been a new GB leak since last month, so no updates from that end, either.
I'm sure once Samsung releases GB/ICS or whatever they're planning & the guys can get their hands on source code that things will pick up.
Just my 2 cents
Also remember that there are about 3 devs for this phone. Dsexton currently has no computer. Whitehawkx said he would update Valhalla if/when 2.3.7 is released. And Raver who has a couple roms that are probably as good as they can get without source. Without source code we won't get too much more. And unfortunately by the time we see it many will have moved on to other devices and ics. This is where Samsung always drops the ball. They take forever to update Android and by the time they do the next operating system is out on several better phones so people move on to them.
Sent from my SGH-T959V using xda premium
I miss my mytouch 4g. Faux123 was the best damn dev ever.
We should send him a phone. I bet we would have CM in a week. He's the kernel king from like 4 different phones now for AOSP stuff.
Sent from my SGH-T959V using XDA App
I believe krylon is willing to pass on the phone. If faux is willing to take up the task maybe krylon will pass on the phone in that direction.
Sent from my SGH-T959V using xda premium
new infuse source code is available on Samsung open source release center.
it doesn't specifically say gingerbread but there are now 2 listings for i997 usa.
will download it later. not sure if this is uckl2 which they were in violation of gpl by not releasing sources or if its lb3 and we should expect yet another update in the coming days. we'll see I guess.
https://opensource.samsung.com/index.jsp;jsessionid=9772B2876689860AEB70F77E9A56FC38
I'm also gonna download and check it out when I get home... hoping for gingerbread ...
sent from my SGH-I717 using XDA premium app
hoping for B3,
I'd personally rather see b1. B3 is smoother and less laggy, no touchscreen issues...but having "long" messaging issues that I didn't have with b1. I'll sit back shut up and be patient while the dev's work their magic and hopefully super one click will be rocking and rolling. Thanks for all you do guys.
Sent from my SAMSUNG-SGH-I997 using XDA App
that's a modem issue. source code is for kernels
not to mention it wont be lb1 because lb1 isn't official, lb3 has potential to be very soon. it could be kl2 because kl2 was released to the public, Samsung didn't release the code then pulled the update and hid behind the update being pulled to say they didn't need to release the code anymore which is a piss poor excuse being that the code was supposed to be there upon initial release. Samsung likely was trying to buy time with att or the public by saying they had unexpected issues. typical Samsung USA move.
Dani897 said:
that's a modem issue. source code is for kernels
not to mention it wont be lb1 because lb1 isn't official, lb3 has potential to be very soon. it could be kl2 because kl2 was released to the public, Samsung didn't release the code then pulled the update and hid behind the update being pulled to say they didn't need to release the code anymore which is a piss poor excuse being that the code was supposed to be there upon initial release. Samsung likely was trying to buy time with att or the public by saying they had unexpected issues. typical Samsung USA move.
Click to expand...
Click to collapse
Actually, they simply ignored all requests for UCKL2 source... I NEVER saw a response to any source code request.
GPL-violating ****ers... The I777 is likely to be my last non-Nexus Samsung device if Sony keeps it up with their (uncharacteristic for Sony) level of developer support.
I got a response. 2 actually. both identical, and they said the update was being held and sources would be released when the problems were fixed.
obviously bull**** because the sources were supposed to be released with the update. seems planned. like kl2 was just an appeasement for the anxious customers.
the odd thing is that Samsung was doing very good with source releases for the last year or so. guess they wanted to see what they could get away with.
Obligatory "will this source help with bluetooth issues on non-infuse roms" post
lol
Dani897 said:
that's a modem issue. source code is for kernels
not to mention it wont be lb1 because lb1 isn't official, lb3 has potential to be very soon. it could be kl2 because kl2 was released to the public, Samsung didn't release the code then pulled the update and hid behind the update being pulled to say they didn't need to release the code anymore which is a piss poor excuse being that the code was supposed to be there upon initial release. Samsung likely was trying to buy time with att or the public by saying they had unexpected issues. typical Samsung USA move.
Click to expand...
Click to collapse
source code is for kernels?
hey dani, does it mean we`ll get new custom kernel soon?
kangshoo said:
source code is for kernels?
hey dani, does it mean we`ll get new custom kernel soon?
Click to expand...
Click to collapse
Check Entropy's DD second to last page.. as of now.
Sent from my A500 using Tapatalk
well yes, ill try but ill need guidence... no promises... hell im not even that optimistic that ill get anything done..
entropy however has already patched some code into the dd kernel but it doesnt fix hdmi yet. entropy dd is based on hellraiser which linux bozo tried to bake froyo mhl drivers into but the adapter causes a forced reboot, even with some new mhl code it still force reboots, entropy is flying blind but he may come up with something.
Well its a step in the right direction... maybe since it seems they are finalizing GB for our device, maybe they start ICS development. Just a thought, probably won't happen though
Sent from my SGH-I997 using XDA App
dustinhayes93 said:
Well its a step in the right direction... maybe since it seems they are finalizing GB for our device, maybe they start ICS development. Just a thought, probably won't happen though
Sent from my SGH-I997 using XDA App
Click to expand...
Click to collapse
HA! seriously though...atleast GB finally hit...then got pulled (face-palm)
why is it that an older Model of an Phone Called the Motorola Atrix I & II will get ICS but we Infuse Owner which phone came out after the Atrix will not be getting it at all. ?
Atrix =dual core.... Infuse=single core
sent from my SGH-I717 using XDA premium app
dman3285 said:
Atrix =dual core.... Infuse=single core
sent from my SGH-I717 using XDA premium app
Click to expand...
Click to collapse
nexus s = single core
but ics LoL
Nexus=has kernel. Infuse=doesn't have kernel. Any questions?
sent from my SGH-I717 using XDA premium app
inick73376 said:
why is it that an older Model of an Phone Called the Motorola Atrix I & II will get ICS but we Infuse Owner which phone came out after the Atrix will not be getting it at all. ?
Click to expand...
Click to collapse
Atrix 2, you damn straight will get it.
Sent from my MB865 using xda premium
inick73376 said:
why is it that an older Model of an Phone Called the Motorola Atrix I & II will get ICS but we Infuse Owner which phone came out after the Atrix will not be getting it at all. ?
Click to expand...
Click to collapse
you can discuss this in one of the many existing ics threads...
you can blame Samsung USA for this. although Samsung Korea put a lot of effort into updates for the i9000 all of the American galaxy s counterparts have been slow on updates and are lucky to get more than one major update. also the infuse is based on the galaxy s which is almost a year older. when the subject of ics on the galaxy s came about Samsung stated that they didn't have the rom storage or ram to run ics with touchwiz over top of it. while the infuse has the ram it has identical partitions to the galaxy s and has even more usage of the current rom storage.
on one hand Samsung played that game with gingerbread. saying they "might" update the i9000 to gingerbread but then it became the first non nexus device to receive the update internationally. on the other hand they have the s2 as a new flagship with the s3 on the way and might not want to continue with the dated i9000. basically if the i9000 doesn't get ics we have zero hope.
now that that's over with, can we keep the discussion to gingerbread or pending update related talk please.
As far as kernels for ICS if Samsung releases source code for kernel does it have to be solely for our device or can it be (ported so to speak) from another device as long as it's a samsung
Sent from my SGH-T959V using XDA
anoymonos said:
As far as kernels for ICS if Samsung releases source code for kernel does it have to be solely for our device or can it be (ported so to speak) from another device as long as it's a samsung
Sent from my SGH-T959V using XDA
Click to expand...
Click to collapse
Team kick ass is working on it (mostly Erik)... Be patient...
Sent from my BAMF SGH-T959V!
Well I just read that samsung has released source for ICS kernel for the new Note just wondering if this can be used for our device. Also I read this from engagement.com source was from Open Source Market
Sent from my SGH-T959V using XDA
Ok I am personally going to start a new trend of not talking about ICS, CM9, or heck even Jelly Bean. If I can see that the Devs are starting to get annoyed with the constant onslaught of ICS, CM9, and CM7 questions and soon next month if it is released Jelly Bean. I guess if you can't help Develop, then you really have absolutely no place to complain about how long things are taking this is not a "customer Service" situation. Devs are here because they want to improve their own phones, or this is their hobby. They are not here to develop you a product. That's what Samsung is for in our case. If you are honestly angry about how long it is taking for us to get ICS then write T-mobile and Samsung not the Devs here that are spending their free time in order to eventually bring these awesome ROMS to our phones. Since I joined a year ago I watched Devs and entire teams leave (when is the last time you saw a Team Whiskey ROM?)So I for one am going to Back off on all the ICS business and let the Devs do their thing Without Having to stop constantly and answer the same questions over and over again. We have limited Devs that can at any sell off their SGS4g's and say "screw this" and move on to another phone. Guys seriously instead of constantly asking the Devs lets try something new ( or old to some of us) and ask Google, Yahoo, Ask.com, and or any other search engine you so choose and let the Devs concentrate on Developing.
One day people will learn how to ignore annoying posts. One day..........
i say "TEAM WHISKEY ROM" haha. lol
airfluip1 said:
i say "TEAM WHISKEY ROM" haha. lol
Click to expand...
Click to collapse
LOL thanx I didn't even see the typo, fixed it
thomas.raines said:
Team kick ass is working on it (mostly Erik)... Be patient...
Sent from my BAMF SGH-T959V!
Click to expand...
Click to collapse
Lol thanks thomas
thomas.raines said:
Team kick ass is working on it (mostly Erik)... Be patient...
Click to expand...
Click to collapse
I go away for a few days and now we're working on an ICS kernel. I should go away more often. lol
hechoen said:
I go away for a few days and now we're working on an ICS kernel. I should go away more often. lol
Click to expand...
Click to collapse
now that's comedy! !
My question had still not been answered a
Sent from my SGH-T959V using XDA
The answer( as I have come to understand, but I maybe wrong) is well parts can but for the most part the linux kernel is the part of the OS that houses all the device, and processor specific drivers. To make matters worse is some of those drivers are also OS specific. meaning Froyo versions won't work with a Ginger bread distro and so on. To port an Android distro you have one of two choices to make it work. Recompile some or all of the libs to work with the older kernel. Or create a kernel from scratch by finding other devices the have the same hardware that have been upgraded to ICS. Often many devices have pieces of the same hardware as your phone. Sometimes it takes scouring different phones to find phones that share pieces of your hardware.
Sent from my SGH-T959V
@ bot42
You are precisely correct. We at Team Kick Ass have found a way to do just that. Unfortunately, it is a very time consuming process as we have to pull many of the information, files, and things from source. I said this once and I will say it agian. Everything is in the process of being worked on. Please be patient.
Thanks sorry if I sounded rude but all the comments that were posted were way off topic that's all I'm in no hurry for ics just seen that Samsung released source for it was trying to be helpful
Sent from my SGH-T959V using XDA
it's taking me forever to properly port voodoo sound into CM7. Precisely as thomas and bot said. If it takes so long to properly port a little thing, think about how long it's gonna take to port a whole kernel.
airfluip1 said:
it's taking me forever to properly port voodoo sound into CM7. Precisely as thomas and bot said. If it takes so long to properly port a little thing, think about how long it's gonna take to port a whole kernel.
Click to expand...
Click to collapse
Yep to port a feature from one device to the next is hard a kernel/whole rom requires a lot of time and that is where my free time is being spent between reading and trying a lot of stuff
So, there are two efforts going on.
The first is what TeamKickAss is working on. I haven't seen what they are doing or any plans posted.
The second is what I'm working on over in the aosp port thread.
This port is a little more ambitious to port to three different versions.
first port sgs4g specific parts to android-samsung-2.6.35-gingerbread
then port that set of changes to android-samsung-3.0-ics branch (both branches originate from the upstream aosp samsung kernel)
the last port I will do will be to Linus's tree at whatever version it is when I get to this step.
So in the end, we'll have:
a stock kj6 kernel
the various kernels that forked from my bml and mtd kernels
aosp gb port
a couple ics kernel ports (one by teamacid, and one by teamkickass)
3.6 kernel port(or maybe 3.7)?
So, there is a peek in the crystal ball I have.
The future's so bright, gotta wear shades
Hi Bryan
Wassup?
I have a friend with SGS i9000, (which didn't get official ICS) nevertheless he installed an ICS 4.04 AOSP ROM on it, working flawlessly.
So my question is, once kernel port will reach its purpose, will we be able to successfully port such ROM ? (PS. I downloaded that ROM and saw some MTD_over_BML stuff inside)
Sent from my SGH-T959V using xda premium
i bet kickass can port it within a few days of an ICS kernel, but ports aren't always the most reliable/stable/fast. It'd be easier just to build from source. That way, we'd have a stable rom, and easier bug fixing.
itzik2sh said:
Hi Bryan
Wassup?
I have a friend with SGS i9000, (which didn't get official ICS) nevertheless he installed an ICS 4.04 AOSP ROM on it, working flawlessly.
So my question is, once kernel port will reach its purpose, will we be able to successfully port such ROM ? (PS. I downloaded that ROM and saw some MTD_over_BML stuff inside)
Sent from my SGH-T959V using xda premium
Click to expand...
Click to collapse
Yea, with so many developers on teamhacksung... they can WORK TOGETHER and port their Aries kernel to any Aries phone. Our phone is kinda funky and we have very few developers.
Sent from my SAMSUNG-SGH-I717 using xda premium