Related
Any word from any one on when the devlopers will get the source code for this phone? I realize that this will help everyone developer wise get a better handle on kernels and greatly help the community.
I went back to GB for a second there but the charging issues have gotten out of control with the kernels which is why I'm starting to wonder when the sourrce will be released. We obviously need it to make further advancement with the community ROMs at this point.
I also seen where HTC said that they will unlock their bootloaders here soon.
Thanks for any one who contributes to this conversation.
Gingerbread? Or Froyo? Cuz Froyo been out...
Thunderbolt «» das BAMF Remix
Kid_Cudi said:
Gingerbread? Or Froyo? Cuz Froyo been out...
Thunderbolt «» das BAMF Remix
Click to expand...
Click to collapse
I like Kid Cudi as well first of all.
What I mean is and I'm probably not going to use the right term here but the RIL or perhaps SDK.. Bear with me here I'm good at trouble shooting stuff but not programming.
I was googling it didn't help me get the right term lol. Chime in who ever knows what the hell I'm talking about here lol.
The kernel source itself has been out for quite some time. We will never see the "source" for the RIL (Radio Interface Layer) because it is proprietary on both HTC and Qualcomm's side. That's about as simple as it gets.
ProTekk said:
The kernel source itself has been out for quite some time. We will never see the "source" for the RIL (Radio Interface Layer) because it is proprietary on both HTC and Qualcomm's side. That's about as simple as it gets.
Click to expand...
Click to collapse
Yeah I think it's RIL. It's what the Cookers keep stating they're waiting for to finish their ROMs like CM7 for instance. The developer for it states that he's waiting for RIL to be able to officially finish his work. We really need to get this released from HTC so we can fix some of the issues people are having with CM7 and the leak for GB. I went back to Froyo because of the issues the leaks having with charging etc..
thewebsiteisdown said:
Any word from any one on when the devlopers will get the source code for this phone? I realize that this will help everyone developer wise get a better handle on kernels and greatly help the community.
I went back to GB for a second there but the charging issues have gotten out of control with the kernels which is why I'm starting to wonder when the sourrce will be released. We obviously need it to make further advancement with the community ROMs at this point.
I also seen where HTC said that they will unlock their bootloaders here soon.
Thanks for any one who contributes to this conversation.
Click to expand...
Click to collapse
HTC and google do not have to release any of the android source if they don't want to because the source (NOT THE KERNEL) uses the apache license, which is very permissive like the BSD/MIT licenses. It lets you use any code additions you make to the source for commercial projects without having to give it back unless you choose to http://en.wikipedia.org/wiki/Apache_license. This is why google doesnt have to release the Honeycomb source as long as they didn't make any additions/modifications to the kernel itself.
Google went through lots of effort as well to make sure they would not be bound by the GPL by writing their own clibs based off of code from various BSD ports. See here for an interesting article on some of the low level features of android (it's a bit old, but most of it is still relevant). http://codingrelic.geekhold.com/2008/11/six-million-dollar-libc.html
The kernel (like all linux kernels) is GPL and must be released.
RIL will be released when it is finished. Slayher is working hard as hell on it. Not saying anyone is under appreciating just give the man some time and soon we will all have MIUI and CM7 running flawlessly on our devices.
miketoasty said:
RIL will be released when it is finished. Slayher is working hard as hell on it. Not saying anyone is under appreciating just give the man some time and soon we will all have MIUI and CM7 running flawlessly on our devices.
Click to expand...
Click to collapse
I think there is a misunderstanding here. The RIL from Slayher is not the same as the RIL from HTC/Qualcomm.
Slayher will merge his "source" into the public CyanogenMod repo once he deems it's ready.
On the other hand, the "source" from HTC/Qualcomm is a whole different subject. We won't be getting a drop of it from them. Not now, not ever.
miketoasty said:
RIL will be released when it is finished. Slayher is working hard as hell on it. Not saying anyone is under appreciating just give the man some time and soon we will all have MIUI and CM7 running flawlessly on our devices.
Click to expand...
Click to collapse
I deffinately appreciate all the hard work. I just thought that HTC had to release this info. I didn't know that Slayher or any other coder could just reverse engineer it.
thewebsiteisdown said:
I deffinately appreciate all the hard work. I just thought that HTC had to release this info. I didn't know that Slayher or any other coder could just reverse engineer it.
Click to expand...
Click to collapse
No the RIL source and Sense source run under the apache license which states that the software developer can use the open source code but does NOT have to repost anything he or she produces.
So it is up to our dev's to do that and make it readily available.
I know a good one needs source, but can't it be done without source?
Edit: crap don't even know what this has to do with a g2x, sorry...
No. You do not need source to create a ROM. If you plan on basing it off of cm7 then you would likely want to compile your own copies to work with. But in general, no.
Sent from my LG-P999 using Tapatalk
smashpunks said:
I know a good one needs source, but can't it be done without source?
Edit: crap don't even know what this has to do with a g2x, sorry...
Click to expand...
Click to collapse
You can manipulate android however you want without source. However, you'll more or less be stuck within the confines of the OEM. Likewise, without source for things like HTC sense, ROMs based on that for the G2X for example are very difficult to get fully functional. We really don't know what in HTC sense to change to get that working with the device based on our hardware. More or less a custom ROM not based on source is still very similar to the original ROM you created it from, where as AOSP roms can be completely different. That's really a very generalized explanation, but that sums it up pretty well I think.
This is a noon question and I appolagize but I figured I would ask anyways. If I were to build the ics myself and flash it would I have any issues getting back to 3.2.2 if I so wished to? I ask because I know the bootloader it picky for the images released for 3.2.2 and have never actually built it myself before. If its not obvious already I own a xoom 4g.
Sent from my ADR6400L using xda premium
Where do you plan to get all the code for all of the hardware drivers? Those are NOT included in the source code.
While we appreciate your enthusiasm for ICS and the developer community. We ask that you do many hours of research before diving into anything near the task you seek to accomplish. To start, you might want to try by flashing between roms, looking at different rom sourcecode, and different driver codes for hardware.
Thanks for the info, like I said I have never done anything like it before. I am kinda embarassed that I didnt even think about the hardware drivers that would be required as well. After doing a little reading on the aosp source site I come to find out an additional bit of information. As of ICS there is more needed than just the source code, there will also be some additional information for the graphics hardware acceleration to work , and the Xoom wasnt mentioned (only the Official Google Devices). Guess I will just sit tight and be happy with flashing ROMs for now. Thanks again.
So at the moment I am currently working on developing a "bare bones" stock rom and modifying it as much as possible with scripts and such.
But what I would like to know from you all is what would you all like to see in the next rom?
Cyanogenmod?
More themes?
Faster?
Battery life?
Cool features?
I think it'd be good to hear you all thoughts & input.
Sent from my SK4G on XDA Premium
Cm6 or 7 and cooler apps to use and batter theams
Sent from my SGH-T839 using xda premium
CM6 an CM7 have both been asked for in the past sadly i think the only way to get it is to mail one of the cyanogen developers a SK4g since it seams none of them have one to even begin making it avail on our phones by making the drivers an kernals from complete scratch like they have with devices like the nook. CM6 i don't know understand fully why we can't get because it is froyo based so the thing would be making a kernal (with out drivers in it from how much i understand building a android kernal). Then when creating the rom an figuring how to make it function more correctly with our odd frame work build. Honestly with themes if you got CM7 working that problem would be more or less taken out with the gingerbread theme engine they use in their roms which makes it a hell of alot easier to change how your phone looks.
Now to the people saying we need a kernal for gingerbread i understand that but then i do look at my nook color an I've tesed a ICS alpha build an have to say "um...... if a kernal is so godly important then how did they make one to run ics on a device that should never be able to run it that has bluetooth drives that were hand made because B&N never intended the device to have bluetooth an they had to hand make alot of other drivers just for the nook color. Anyways I'm getting a spare android phone in the next 10 days (xperia x10 mini) which is even capable of running gingerbread..... and has a alpha ics build.... am i missing something here?..
the kernel is what provides all of the drivers for the phone's hardware. The reason that it is difficult to build an updated kernel for the sidekick is because it uses hardware that isn't found in any other phones, and the drivers are only designed for the 2.6.32 kernel, rather than the 2.6.35 kernel required for GB/ICS.
The reason that ICS alpha builds are being released for the nook color and the xperia are because the CM devs put in the work to get the CM kernel working correctly. The CM kernel is designed in such a way that it can be updated quite easily with little breaking of drivers, but typically requires a large amount of rewriting drivers.
Basically, the reason that it came so fast to the nook color and the xperia is that the CM devs actually wanted those devices, so they bought them, and ported CM to them.
The fact is that the CM devs don't want anything to do with the Sidekick, and won't do anything with it short of someone handing them a free phone to work on.
sduvick said:
The fact is that the CM devs don't want anything to do with the Sidekick, and won't do anything with it short of someone handing them a free phone to work on.
Click to expand...
Click to collapse
is there any particular reason they don't want anything to do with the sidekick?
also, i assume we haven't tried collecting a glob of money to buy an sk4g off ebay or something... have we? seems like it'd be worth it...
I'm not 100% sure why, as I'm not one of them, but I'm guessing that it's because the sidekick is perceived as a teen/feature phone. Typically the support for Samsung phones is limited, and the amount of customization from Samsung on this phone compared to previous phones would require even more work out of them.
Basically in order to get CM7/CM6 it would require the CM dev team 2 things:
1: Interest/Willing-ness to work on the phone
2: A Free SK4G to work on lol
I like the idea of the community all pitching in on buying the CM dev team the SK4G just so that they can begin to work on CM for our phone. CM would open up so many doors for new roms and ports
If it wasn't for the some slight disconfort in giving away my SK4g I'd mail it to a CM dev for them to go crazy with it.... after sending it to someone that can make the sidekick unbreakable modded >.> I'm getting the xperia X10 mini pro cause I can find them for cheap (got mine for 125 after shipping) an it has a hardware keyboard. I'll gladly pitch in money for one of the CM devs to get a sidekick though if they are interested.
it'd be nice to get a feel for the likelihood of the cm devs porting cm to sk4g if they had a phone. that way we can get more concrete on whether we should raise funds for a phone to send to them. i tweeted cyanogen to ask, but got no response. maybe someone else can get to him or other cm devs?
i did posted in the cm forums someone in the xda forums made a bounty request?
and did any dev respond?
stock GB or ICS(cm7/9 would be fine too), better battery life (the current crop of roms are terrible), stripped down lite version would be nice too( no preinstalled apps just bare min)
No one replied
Sent from my SGH-T839 using XDA App
wuziq said:
is there any particular reason they don't want anything to do with the sidekick?
also, i assume we haven't tried collecting a glob of money to buy an sk4g off ebay or something... have we? seems like it'd be worth it...
Click to expand...
Click to collapse
I think that none of the cm team want anything to do with the sk4g is that cyanogen himself didn't like the sk4g. So in result his cm team of followers didn't want anything to do with it. They would be embarrased to be caught with one. For some one that has worked on many diffrent phones like them, it shouldn't be hard to rewrite a kernel.
Think about it, they get cm on almost any new phone that comes out? Don't you think that every phone that comes out have diffrent drivers? Someone has to backwards engineer a driver to get a kernel out that's compatible with cm "roms". Its just a matter of having a member that knows how to code, cm isn't the only person in the world that know how to.
But then again this is just my opinion...
insanedrunk said:
I think that none of the cm team want anything to do with the sk4g is that cyanogen himself didn't like the sk4g. So in result his cm team of followers didn't want anything to do with it. They would be embarrased to be caught with one. For some one that has worked on many diffrent phones like them, it shouldn't be hard to rewrite a kernel.
Think about it, they get cm on almost any new phone that comes out? Don't you think that every phone that comes out have diffrent drivers? Someone has to backwards engineer a driver to get a kernel out that's compatible with cm "roms". Its just a matter of having a member that knows how to code, cm isn't the only person in the world that know how to.
But then again this is just my opinion...
Click to expand...
Click to collapse
so pretty much we got swcred because of cm dislikement of the phone and his groupies don't want to get kicked out of their team so they don't do anything about it? WOW talk about tyrany
xtrem88 said:
so pretty much we got swcred because of cm dislikement of the phone and his groupies don't want to get kicked out of their team so they don't do anything about it? WOW talk about tyrany
Click to expand...
Click to collapse
Yuup, even if it sounds rediculous, seems that way.
insanedrunk said:
I think that none of the cm team want anything to do with the sk4g is that cyanogen himself didn't like the sk4g. So in result his cm team of followers didn't want anything to do with it. They would be embarrased to be caught with one. For some one that has worked on many diffrent phones like them, it shouldn't be hard to rewrite a kernel.
Think about it, they get cm on almost any new phone that comes out? Don't you think that every phone that comes out have diffrent drivers? Someone has to backwards engineer a driver to get a kernel out that's compatible with cm "roms". Its just a matter of having a member that knows how to code, cm isn't the only person in the world that know how to.
But then again this is just my opinion...
Click to expand...
Click to collapse
did cyanogen actually say somewhere that he didn't like the sk4g?
even if he did, why would he poopoo on another dev that ported cm to it? he'd want cm to be on as many phones as possible. "how dare someone do work that i didn't really want to do?" no. he's not some evil overlord with a bunch of peon devs who back off whenever he gives a stern look.. because.. OSS projects don't work like that?
also, someone correct me if i'm wrong, but they're not rewriting kernels. they'd have to update sk4g drivers for the cm kernel.
wuziq said:
did cyanogen actually say somewhere that he didn't like the sk4g?
even if he did, why would he poopoo on another dev that ported cm to it? he'd want cm to be on as many phones as possible. "how dare someone do work that i didn't really want to do?" no. he's not some evil overlord with a bunch of peon devs who back off whenever he gives a stern look.. because.. OSS projects don't work like that?
also, someone correct me if i'm wrong, but they're not rewriting kernels. they'd have to update sk4g drivers for the cm kernel.
Click to expand...
Click to collapse
i know that they dont like EVERY phone that CM is on but they still "port" CM to as many phones as possible because that is their goal
i think that it could either be due to lack of interest or lack of not having the SK4G
wuziq said:
did cyanogen actually say somewhere that he didn't like the sk4g?
even if he did, why would he poopoo on another dev that ported cm to it? he'd want cm to be on as many phones as possible. "how dare someone do work that i didn't really want to do?" no. he's not some evil overlord with a bunch of peon devs who back off whenever he gives a stern look.. because.. OSS projects don't work like that?
also, someone correct me if i'm wrong, but they're not rewriting kernels. they'd have to update sk4g drivers for the cm kernel.
Click to expand...
Click to collapse
I don't have the exact quotes, but they (the usual cm members) were reviewing the sk4g cm said he didn't like the fact that samsung made it, from there evry one weighed in on it..... source: it was on twitter. @koush @cyanogen and others, plus the retweet crap..
insanedrunk said:
I don't have the exact quotes, but they (the usual cm members) were reviewing the sk4g cm said he didn't like the fact that samsung made it, from there evry one weighed in on it..... source: it was on twitter. @koush @cyanogen and others, plus the retweet crap..
Click to expand...
Click to collapse
so b/c samsung made the sk4g and other galaxy s phones they won't port CM to the phones?
i think if we get enough community support by having a lot of us post on cyanogen's twitter and on their forums about it we could get possibly get them to port it
I've been thinking about the possibility of extracting the firmware from a Galaxy Tab 2 (ICS) and merging it with the kernel and build.prop from the 7 Plus (Honeycomb).
Technically I can't think of a reason that it wouldn't work, I'd think that the challenge would be getting the kludged FW back onto a 7 plus.
Would it be a futile effort? Maybe if Samsung releases ICS for the Plus, but who knows when that will be.
I don't have any experience on these two Android device other than in an end user capacity (though I have been reading) and very little on a few other Android devices so I dunno if it's feasible, but I thought I'd mention the idea.
Anyone with deeper experience on these things think it might be viable?
I know the devices have different hardware specs so I don't know if it would meld...
fewt said:
Technically I can't think of a reason that it wouldn't work, I'd think that the challenge would be getting the kludged FW back onto a 7 plus.
/QUOTE]
technically: different hardwares, the ics may need some changes on kernell itself to work, so you may not be able to use hc one.
besides the differences of one device to other is not just encapsulated on kernel, the dalvik virtual machine needs to be ported to every machine depending on aspects.
Enviado do meu MB525 usando o Tapatalk
Click to expand...
Click to collapse
leodfs said:
fewt said:
Technically I can't think of a reason that it wouldn't work, I'd think that the challenge would be getting the kludged FW back onto a 7 plus.
Click to expand...
Click to collapse
technically: different hardwares, the ics may need some changes on kernell itself to work, so you may not be able to use hc one.
besides the differences of one device to other is not just encapsulated on kernel, the dalvik virtual machine needs to be ported to every machine depending on aspects.
Enviado do meu MB525 usando o Tapatalk
Click to expand...
Click to collapse
Technically, it shouldn't as kernel interfaces don't change that much between releases. Since both processors are ARM, I wouldn't expect a problem with the Dalvik VM either but I guess I could be wrong there.
Would be interesting to see, but I can tell there isn't any interest in it. I've been trying to find a good reference on where to get started with this stuff, but it just seems like a hodgepodge of information sprawled all over the place.
Anyone have a solid guide to getting started building custom firmware that isn't the great google?
fewt said:
Technically, it shouldn't as kernel interfaces don't change that much between releases. Since both processors are ARM, I wouldn't expect a problem with the Dalvik VM either but I guess I could be wrong there.
Would be interesting to see, but I can tell there isn't any interest in it. I've been trying to find a good reference on where to get started with this stuff, but it just seems like a hodgepodge of information sprawled all over the place.
Anyone have a solid guide to getting started building custom firmware that isn't the great google?
Click to expand...
Click to collapse
I suggest you read the CyanogenMod 9 thread in development as you will experience the same problems porting this over without a working ICS kernel.
Here are some threads I've found useful on porting and building from source:
http://www.iphoneandroidtips.org/miui/how-to-port-miui-v4-to-android-phones/
http://forum.xda-developers.com/showthread.php?t=1153233
http://forum.xda-developers.com/showthread.php?t=1499411
http://forum.xda-developers.com/showthread.php?t=1169570
http://forums.androidcentral.com/ht...how-build-your-own-kernel-package-source.html
http://source.android.com/source/index.html
http://wiki.cyanogenmod.com/wiki/Building_Kernel_from_source
These threads are for all different models of phones and the methods may or may not work for our tablets but the principles are pretty much the same. In the instance of porting over MIUI 4 you have to start with a working CM9 ROM as it requires a working AOSP ICS kernel, which we don't have yet. Our devs are working their butts off trying to port one over from another device but its slow going without the proper source code that Samsung won't release.
I would think if it were as easy as combining the two, who would need XDA?
kzoodroid said:
I suggest you read the CyanogenMod 9 thread in development as you will experience the same problems porting this over without a working ICS kernel.
Here are some threads I've found useful on porting and building from source:
http://www.iphoneandroidtips.org/miui/how-to-port-miui-v4-to-android-phones/
http://forum.xda-developers.com/showthread.php?t=1153233
http://forum.xda-developers.com/showthread.php?t=1499411
http://forum.xda-developers.com/showthread.php?t=1169570
http://forums.androidcentral.com/ht...how-build-your-own-kernel-package-source.html
http://source.android.com/source/index.html
http://wiki.cyanogenmod.com/wiki/Building_Kernel_from_source
These threads are for all different models of phones and the methods may or may not work for our tablets but the principles are pretty much the same. In the instance of porting over MIUI 4 you have to start with a working CM9 ROM as it requires a working AOSP ICS kernel, which we don't have yet. Our devs are working their butts off trying to port one over from another device but its slow going without the proper source code that Samsung won't release.
Click to expand...
Click to collapse
This is awesome, I really appreciate you taking the time to write it up.
I hope you have success, either way you will learn, that's why we bought our android for.
I think there's a lot of interest, but this thing is dangerous, lots of devs have their devices bricked trying port or improve,.
My advice is not of an android developer, but of someone that has some experience of customizing or compiling the Linux Kernel. any little thing you forget render you with a system that will not boot. And even if they use the same kernel, ics may need some things activated that hc may not
Sent from my GT-P6210 using Tapatalk 2 Beta-5