[Q] Android 3.0 Kernal/Source Code???? - T-Mobile LG G2x

So i have been reading and seeing alot of people wanting a rom that ports honey comb to be compatible with the g2x... ive been reading all about how google hasnt released this yet and probably wont be releasing up until icecream sandwhich is released. But this is where my question forms, to port honey comb to be compatible with our device the source code needs to be found, the same source code used in development of apps for the 3.0+ os correct? i might of stumbled accross something but i doubt its a new find as im sure this topics been searched very throughly. Could someone please reply to inform me of what information is needed to begin development of a rom that ports honey comb to our phones.

It was tried in the nexus one forum, there is a port but unfortunately not fully working you might want to search for it very interesting stuff and they managed to get pretty far along.
Sent from my LG-P999 using Tapatalk

As much as we would all like something new, honeycomb is for tablets. Someone correct me if i'm wrong, but it doesn't make alot of sense to me to port something meant for tablets and have to change EVERYTHING to now make it fit a phone. Not to mention the apps made for honeycomb are made for a big screen, which again we won't have.

dont get me wrong GB is fine with me till ICS comes out, i just read about people making new roms and there always being a honeycomb port request. and for the stated problem of the apps on honeycomb are meant for larger screens, would it not just make since to adjust the resolution in the framework down to 190 when the rom is being made rather than leave it up to the end user to do it? this is all just thoughts, and i wanted to see if i found the correct source code for whomever decides they want to attempt to build a rom off honeycomb, as stated i do not have the developing know how as of now to do such a build.

Related

Froyo on the G1 and other devices

First off, allow me to introduce myself: I'm an 18 year old cook from new orleans and I'm fairly tech savvy. I have an ipod touch and enjoyed hacking the **** out of it, and now I have a G1 and look forward to hacking the hell out of it as well, espcially since android is much more hack friendly and so far I absolutely love it compared to the iphone os.
Ok, so I just downloaded sign-passion-frf50-from-ere27.1e519a24.zip
From what I understand this is Froyo (2.2), which cannot(?) run on the G1.
Can I get this to run on the G1? If not, can I get 2.1 to run on the G1?
If it is possible, but very difficult, please let me know anyway so at least I know what I'm up against.
On this note, what is the process of manually updating the android os anyway?
P.S. I did search before posting this, and nothing seemed to spefically match this post
mattj7 said:
First off, allow me to introduce myself: I'm an 18 year old cook from new orleans and I'm fairly tech savvy. I have an ipod touch and enjoyed hacking the **** out of it, and now I have a G1 and look forward to hacking the hell out of it as well, espcially since android is much more hack friendly and so far I absolutely love it compared to the iphone os.
Ok, so I just downloaded sign-passion-frf50-from-ere27.1e519a24.zip
From what I understand this is Froyo (2.2), which cannot(?) run on the G1.
Can I get this to run on the G1? If not, can I get 2.1 to run on the G1?
If it is possible, but very difficult, please let me know anyway so at least I know what I'm up against.
On this note, what is the process of manually updating the android os anyway?
P.S. I did search before posting this, and nothing seemed to spefically match this post
Click to expand...
Click to collapse
Even if all Android systems have the same roots, they differs on various devices. This is caused by different hardware specs: CPU architecture, drivers, customizations; and there are some custom add-ons as well: Google apps, Sense UI, etc. This is why it isn't possible to run OS designated for other devices, even if both of them are running "the same" system.
Porting is a process of mixing up bits from both systems to get some features from one device to another. And adding some missing parts. We have to wait for someone to manage to build workable version of Froyo system for G1 devices.
Ahh and there is no problem with 2.1 on G1 - there are plenty of 2.1 roms for this device, I personally recommend CM5.0.7 .
I see. So do you think that froyo will be ported to the g1? Where can I download the roms for the g1? and how do I install them? Is there a way to get sense ui on the g1 after I install CM5.0.7? Thanks for all the help
Well first you will need to root your phone. There is tons of information on that. I'm sure you'll find a guide no problem. Is you want cm5, which I highly recommend as well, go to cyanogenmod.com and look in the forums under experimental. You cannot, however, simply add sense to a rom. It's a lot more complicated than that. There are lots of sense roms though. Check the g1 forum here on xda. As for froyo, time will be popping up soon enough but we're all going to have to wait until the source is released sometime in the next week or two.
Hope that helps,
Samuel Maskell
-------------------------------------
Sent via the XDA Tapatalk App

[Q] 2.2 (Non-USCC) or 2.3 ROM for Mesmerize?

Is there a 2.2 (that doesn't come from USCC) or 2.3 ROM available for the Mesmerize?
King Mustard said:
Is there a 2.2 (that doesn't come from USCC) or 2.3 ROM available for the Mesmerize?
Click to expand...
Click to collapse
Well, being that 2.2 isn't out yet for the Mesmerize from USCC, yes. Now if you are talking about something other than the intended firmware, then the simple answer is no. If you want to flash AOSP there is a few variations floating about. All of which will make some part of your phone non functional. There is a mostly non working port of MIUI that is available also. There are several options right now. None of which are really that great for someone who wants a fully functional phone at this point and most of which are for the Fascinate so I really don't recommend them even though a lot of people are able to flash them and come back. It really depends on what you are wanting. We are currently working on a couple of things, but again, they will be based on the firmware that is coming out from USCC so if you are trying to get away from that type of firmware, then you will have to wait until those projects are done and we get source code for 2.2 to get other things working.
phidelt82 said:
Well, being that 2.2 isn't out yet for the Mesmerize from USCC, yes. Now if you are talking about something other than the intended firmware, then the simple answer is no. If you want to flash AOSP there is a few variations floating about. All of which will make some part of your phone non functional. There is a mostly non working port of MIUI that is available also. There are several options right now. None of which are really that great for someone who wants a fully functional phone at this point and most of which are for the Fascinate so I really don't recommend them even though a lot of people are able to flash them and come back. It really depends on what you are wanting. We are currently working on a couple of things, but again, they will be based on the firmware that is coming out from USCC so if you are trying to get away from that type of firmware, then you will have to wait until those projects are done and we get source code for 2.2 to get other things working.
Click to expand...
Click to collapse
I was hoping there was news of a experimental build of CyanogenMod for the Mesmerize or something like that, but if not, that's fine. Hurry up USCC, release 2.2!
King Mustard said:
I was hoping there was news of a experimental build of CyanogenMod for the Mesmerize or something like that, but if not, that's fine. Hurry up USCC, release 2.2!
Click to expand...
Click to collapse
There is a spot on their site for Galaxy S, but no team assigned, so no cyanogen - at least in the near future.
These things are on my list guys (= But as the semester progresses I have less and less free time. If you want to wait I will get around to it eventually. Alternatively, you can read up on Android development and start to chip in (= It would be awesome to get some others working on this stuff since it's a lot for 2 people to handle right now. Soo that's the current situation..
Work 40+ hours a week, plus 10 college credits this semester... If I had some free time I'd love to get involved in development. Maybe in the summer if there's still a need in the scene.
dcow90 said:
These things are on my list guys (= But as the semester progresses I have less and less free time. If you want to wait I will get around to it eventually. Alternatively, you can read up on Android development and start to chip in (= It would be awesome to get some others working on this stuff since it's a lot for 2 people to handle right now. Soo that's the current situation..
Click to expand...
Click to collapse
Soon as I learn more about java, I'll be pitching in for sure
Well Android is written in C and a little C++, might want to read up on that.

Cyanogenmod6 port possible?

Possibly a noob question but since cyanogenmod7 is based off gingerbread an there is a froyo based cyanogenmod6 for the google G1 is it possible to do a port over to our phone since its froyo as well. I know drivers an such would have to be messed with but least we could have cyanogen on our phones even if its not the latest gingerbread powered version.
I don't know why people find cyanogen roms to be the be all end all of android. Not saying that I don't want them, but they're not the only thing that makes a phone good. CM6 is based off of the same kernel as CM7 which requires a newer source than we have.
Cyaongen mod roms are rubbish, they contain many bugs that are dealbreakers anyways. I know the devs are hard at work, but any current rom in these sk forums have far less bugs than cm. Cm7 on my mytouch 4g was horrible. Not belittling anyone, but just speaking from experience and hardships with those roms since the old g1 days.
Insanedrunk.....you are so ignorant if you believe Cyanogen ROMs are rubbish.
First off, the "ROMs" in the Sidekick 4G forum are nothing more than modified T-Mobile ROMs....that's all they are....nothing more.
Cyanogen and his team completely rebuild Android from scratch, that's why it's called "AOSP". Their ROMs require far more knowledge than simply zipaligning, deodexing, and deleting junk applications. If you have ever even attempted to build Android using the SDK, you would respect these guys.
You obviously are some n00b that doesn't even understand the concept of Android rooting and modding at all.
Please, if all you can do with Android is talk crap to legitimate developers, go somewhere else, you don't even deserve to type xda-DEVELOPERS into your address bar.
Sent from my stock, unlocked Sidekick 4G
Actually, AOSP stands for Android Open Source Project. It's plain vanilla android, from google's source. Yes, eventually into CM6 and 7 they got more hacky with it, but up to CM5, it was just standard google source releases patched together.
troby86 said:
Insanedrunk.....you are so ignorant if you believe Cyanogen ROMs are rubbish.
First off, the "ROMs" in the Sidekick 4G forum are nothing more than modified T-Mobile ROMs....that's all they are....nothing more.
Cyanogen and his team completely rebuild Android from scratch, that's why it's called "AOSP". Their ROMs require far more knowledge than simply zipaligning, deodexing, and deleting junk applications. If you have ever even attempted to build Android using the SDK, you would respect these guys.
You obviously are some n00b that doesn't even understand the concept of Android rooting and modding at all.
Please, if all you can do with Android is talk crap to legitimate developers, go somewhere else, you don't even deserve to type xda-DEVELOPERS into your address bar.
Sent from my stock, unlocked Sidekick 4G
Click to expand...
Click to collapse
I actually have pulled directly from source, but for mt3g, still have my linux setup ready to go, does take time, still, I don't add **** code to my roms that cause memory leaks, I'm not as ignorant to the extent that in which you think of. I'm not brown nosing any self proclaimed douche bags either.... and if you frequent this site, you wouldn't have to constantly type it in your address bar, so noob? Maybe to the sk4g scene, but not to android.
Still, I would like to say I'm sorry if my post came off as rude as you thought, but I was simply.saying I think our sk4g devs can go a diffrent direction than cm.
Cm7 for defy is amazing. Cm7 was available for the defy long before any leaked gb was available. Even with a locked bootloader. I wish somebody from that thread was here
Sent from my MB525 using XDA App
Then go find them. Don't just act helpless, if you really want someone from those threads to get over here, pay the $300 to buy a CM dev an SK4G. until then, be happy for what you have.
heard that ^
Sent from my MB525 using XDA App

Building from source question.

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.

What would you all like to see in the next rom?

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

Categories

Resources