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.
is there a way to overclock the asus transformer? because ive been reading about the xoom/gtablet/sgt's overclocking capabilities, but still havent read anything about the transformer being overclocked
We need an overclocking kernal for that, since we don't have full access to everything we cant overclock. (yet!) I expect we should be able to overclock to 1.5 easily.
any update on OC? We already have the source code for TF.
Haven't seen anything about it either. I Would like to know though!
awitee said:
is there a way to overclock the asus transformer? because ive been reading about the xoom/gtablet/sgt's overclocking capabilities, but still havent read anything about the transformer being overclocked
Click to expand...
Click to collapse
Once a custom kernal is released that allows us to overclock it will be all over the blogs, I would assume. So i would imagine that it isnt too far away based on all the publicity the dev would receive.
The full kernel source has been released and can be modded now. I know some people are working on it already. I dont think it would be too hard to incorporate thexoom's ocing into the transformer. After all the transformer code is what helped the kernel dev for the xoom activate the sd card
graffixnyc said:
The full kernel source has been released and can be modded now. I know some people are working on it already. I dont think it would be too hard to incorporate thexoom's ocing into the transformer. After all the transformer code is what helped the kernel dev for the xoom activate the sd card
Click to expand...
Click to collapse
So an unlocked bootloader is not required for overclocking? I didn't think I'd miss the OC from the XOOM but when I just played Avatar at 1280x728 HD the XOOM was much smoother than the TF Also, the sound on the TF stopped whereas the XOOM kept going. I assume it had to do with the massive amount of data from the softdecode... So PLEASE make the OC happen
Is there any update on progress for overclocking? This would definitely be something to look forward to since we have stock android already, and because we have the honeycomb source won't be released till December.
So it looks like kernel work could be a big priority till then since there isn't much else till then.
Thunderbolt Rooted!
BUMP!
C'mon guys, there must be someone on this forum that knows how to modify the Tiamat kernels for the XOOM so make it work on the TF I really didn't think that the TF would be receiving sooo little development despite its apparently good sales!
People are only just now starting to receive them. Give people time.. Not everyone is a developer.
i know for a FACT that there are dev's working on this. The number one rule of dev forums is, well, dont talk about fightclub. But the number 2 rule is don't ask for ETA's. These guys do this for free, and if i remember correctly, I'm not even sure the dev working on these has a tf yet.
djdevine2 said:
We need an overclocking kernal for that, since we don't have full access to everything we cant overclock. (yet!) I expect we should be able to overclock to 1.5 easily.
Click to expand...
Click to collapse
You might overclock it but I do not believe there is a heatsink on the cpu.
dcmtnbkr said:
i know for a FACT that there are dev's working on this. The number one rule of dev forums is, well, dont talk about fightclub. But the number 2 rule is don't ask for ETA's. These guys do this for free, and if i remember correctly, I'm not even sure the dev working on these has a tf yet.
Click to expand...
Click to collapse
I'm not asking for an ETA and I appreciate people working on it in silence. But it would be nice to at least know that something's going on After all, that kind of development is the best reason to donate beer money just like I did for the great guys at the XOOM forum
levenite said:
You might overclock it but I do not believe there is a heatsink on the cpu.
Click to expand...
Click to collapse
Is there one on the xoom? Does the reference Tegra2 design include a heat sink?
funnycreature said:
I'm not asking for an ETA and I appreciate people working on it in silence. But it would be nice to at least know that something's going on After all, that kind of development is the best reason to donate beer money just like I did for the great guys at the XOOM forum
Click to expand...
Click to collapse
No worries I believe it is being done in secret in case nothing comes of it. I wouldnt be surprised to see something in the next couple of weeks though.
seeingwhite said:
Is there one on the xoom? Does the reference Tegra2 design include a heat sink?
Click to expand...
Click to collapse
It might be that the metal casing of the XOOM helps disperse the produced heat. The TF has plastic backing so it might not work as efficiently
Overclock available
Netarchy is working on the Netformer kernel. Thread is here in the development.
Mine seems to run fine at 1.4GHz! Netformer kernel as the previous poster already mentioned!
Thanks!
verkion
verkion said:
Mine seems to run fine at 1.4GHz! Netformer kernel as the previous poster already mentioned!
Click to expand...
Click to collapse
And mine too.
Results @1400Mhz
Mandro Bench: 15217
Quadrant Standard: 3447
Linpack: 57.236
http://www.tmonews.com/2011/10/ice-...a-couple-of-weeks-after-galaxy-nexus-release/
It says 2.3 devices will likely get it.
Maybe LG will actually give a GOOD update for us but with what they've done so far i doubt it. Is anyone planning on a port?
will748 said:
http://www.tmonews.com/2011/10/ice-...a-couple-of-weeks-after-galaxy-nexus-release/
It says 2.3 devices will likely get it.
Maybe LG will actually give a GOOD update for us but with what they've done so far i doubt it. Is anyone planning on a port?
Click to expand...
Click to collapse
Doubt it. Only way we'll get it is through CM9.
No good ROM's will be made until source is released.
Powered by a G2x
mackster248 said:
Doubt it. Only way we'll get it is through CM9.
No good ROM's will be made until source is released.
Powered by a G2x
Click to expand...
Click to collapse
Yes that's probably true. CM9 better be good...
LOL, LG will never touch this device ever again, I will bet actual money on that. CM9, however, is almost a sure thing. Frankly, I consider that better than the alternative.
I am sure that it will happen and I think that those of you who say LG will never touch this device are right as well. I could be wrong thought maybe LG will wake up and fix the device. HAHA
LG has a history of not updating devices. Like I have said before other 2X devices are still on Froyo. I asked girl at LG store in Bangkok when the device will get update to Gingerbread and she said "it is not being updated." So be thankful you got any Gingerbread at all, and don't count on ICS or you will be sure to be disappointed later.
Looks like ics source should be released soon...
http://androidandme.com/2011/10/new...de-will-be-available-soon-get-ready-for-roms/
Sent from my LG-P999 using xda premium
Really? ANOTHER ICS thread?
d12unk13astard said:
Looks like ics source should be released soon...
http://androidandme.com/2011/10/new...de-will-be-available-soon-get-ready-for-roms/
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
That just got me excited.
Hopefully they don't burst the bubble and make us wait into the new year.
And honestly, I don't see why Google wouldn't release ICS. I mean I understand they're waiting for the Nexus to ship, so that people will buy it for ICS. But then their goal is to have all phones updated to the newest OS. By making their OS compatible with all hardware, and releasing the source code, they don't have to do any work while ROM developers make Google's dream come true.
This is the great thing about open sourcing. Love it!
HELL YAH! Can't wait for CM9!
They're probably going to release the source the day the Galaxy goes on sale.
Sent from my Nexus Prime using XDA Ultimate App
[/QUOTE]Won't let me re-post your link
It says 2.3 devices will likely get it.
Maybe LG will actually give a GOOD update for us but with what they've done so far i doubt it. Is anyone planning on a port?[/QUOTE]
You need to read again. It does not say 2.3 devices will likely get it. They are keep their fingers crossed hoping they will get it.
"Rubin wouldn’t specify which tablets or smartphones would receive the update or how fast but we’ll keep our fingers crossed that every current Android 2.3 device receives the update."
And away we go!
htcdev: Kernel source code for the HTC One S has been uploaded: http://t.co/oWFTzI51
very nicee
I'm putting an overclockable kernel from source together tonight.
Sent from my HTC One X using xda premium
Can't wait to try it out!
Sent from F.E.M.A. region 9
oooohhhh yheaaaa!! Gooo modding goooo!!
Woooo
Sent from my HTC One S using XDA
Hah! I wonder if it has anything to do with the e-mail I sent to Peter Chou (htc's CEO) regarding their blatant disregard for GPL rules and continued dishonesty with the community? I'd like to think it was. I'll just pretend for the moment that I made it happen (lol, somehow I doubt it).
I called them on their BS on claiming that the community agreed that 90-120 days was acceptable.
Without a real kernel dev this isn't much worth, in the one x forum's are still not stable and there are real pro's.
Let's see..
I'm pretty sure I know why they waited. Today was the beginning of the update for the One S on T-Mobile US. If I'm not mistaken, T-Mobile's One S is the last one to get the radio and software update to match the rest of the One S devices. So it sort of makes sense, they didn't release the kernel sources until after the update was ready. I, personally, am not bothered cuz I just got my One S today, but I can completely understand the frustration for the 1st day buyers on T-Mo, and the global versions, since you guys have been waiting months now, it would seem. Either way, It's here now, and that means we all will get to reap the benefits. Now, where's my OTA already? LOL
Couldn't see U.S. listed in there.
flamingblue8z said:
I'm pretty sure I know why they waited. Today was the beginning of the update for the One S on T-Mobile US. If I'm not mistaken, T-Mobile's One S is the last one to get the radio and software update to match the rest of the One S devices. So it sort of makes sense, they didn't release the kernel sources until after the update was ready. I, personally, am not bothered cuz I just got my One S today, but I can completely understand the frustration for the 1st day buyers on T-Mo, and the global versions, since you guys have been waiting months now, it would seem. Either way, It's here now, and that means we all will get to reap the benefits. Now, where's my OTA already? LOL
Click to expand...
Click to collapse
I was thinking the same thing. Makes sense
Sent from my HTC VLE_U using XDA
torxx said:
Without a real kernel dev this isn't much worth, in the one x forum's are still not stable and there are real pro's.
Let's see..
Click to expand...
Click to collapse
True...should we start a pool to buy a 1S for a recognized developer?
Sent from my HTC VLE_U using XDA
flamingblue8z said:
I'm pretty sure I know why they waited. Today was the beginning of the update for the One S on T-Mobile US. If I'm not mistaken, T-Mobile's One S is the last one to get the radio and software update to match the rest of the One S devices. So it sort of makes sense, they didn't release the kernel sources until after the update was ready. I, personally, am not bothered cuz I just got my One S today, but I can completely understand the frustration for the 1st day buyers on T-Mo, and the global versions, since you guys have been waiting months now, it would seem. Either way, It's here now, and that means we all will get to reap the benefits. Now, where's my OTA already? LOL
Click to expand...
Click to collapse
While it does seem that HTC waited for the update to release the source... It's unfortunate that they didn't include the source for the US Tmobile version yet.... This probably won't be an issue since most run EU roms anyways(AOKP for me)... The One X for At&t is still waiting for source... As torxx mentioned source means nothing without someone to develop a kernel... Hopefully we will see something on the horizon sooner rather than later
Sent from my BluMagic HTC One S using Tapatalk 2
About time. HTC have dragged their heels for far too long.
Excited for all the new kernels.
Where is ProTekk??
Wohooo! Time to get building! If we're lucky, we can get CM9 running perfectly now. *Gets on it*
Does this mean aokp/cm9 roms will work better? Or better yet will they be able to be completed with working camcorder etc.?
Sent from my HTC One S using XDA
It's great to see that HTC is releasing kernel source code for devices even if they aren't releasing it for other devices, such as the HTC amaze 4G.
Sent from my HTC_Amaze_4G using Tapatalk 2
S4 source should be fairly stable. I should have a kernel built for you guys later tonight. One x tegra source was a mess which is why tegra is taking awhile.
Sent from my HTC One X using xda premium
ridearoundsolo said:
Does this mean aokp/cm9 roms will work better? Or better yet will they be able to be completed with working camcorder etc.?
Sent from my HTC One S using XDA
Click to expand...
Click to collapse
Yep. Should open the door to fix that remaining issue.
Sent from ICS device!
ozzie1p said:
Couldn't see U.S. listed in there.
Click to expand...
Click to collapse
I just noticed that myself. Seems odd. Maybe someone can find out what version the kernel is and compare it to the sources already posted. It seems, however, that this 1.84 update hasn't hit any XDA members yet, since I haven't seen anyone on here post that they received it yet. I saw a lot of talk about an unlocked bootloader being enough to prevent an update from being performed, but I think it's all rumor. I could be wrong though. I have yet to unlock the bootloader & root, because I'm waiting to find out what issues I will run into later. For instance, this Tampered banner sort of has me worried. Plus, re-locking the device has its own separate banner from Locked? Has me really concerned about any potential warranty exchanges in the future, should my device need one. Hopefully this all gets sorted out. I'm really liking Sense, this is my first time using it, and fortunately I got a slimmed down version, vs. 3.x & older. But I do have an itch to go back to some AOSP ICS like I had going on my G2x last month. Either way, I haven't even signed into my Google account yet, and I've had the phone about 7 hours now. There's plenty to do without needing to enter my Google credentials.
What goes into a fully functional ROM for an android phone like our beloved TB's? ICS for us has been an evolution of sorts. From what I understand, first we had woefully buggy ICS because we were missing something that only the manufacturer can provide (the RIL, whatever that is?). Sounded to me like the OS would work, more or less, but it was the calling and data that was missing.
Then we got our leak. The leak provided some critical component, but we still have imperfect ROMs. What did we get, and what do we still need?
I know our devs are leaner and meaner coders than the guys at HTC, and that there have been ROMs which are much improved over the initial BAMF one. But, have we gotten ICS to a sweet spot that can't be improved by an official HTC update? Or can we still benefit from it whenever the hell it comes out?
Duely blundered from my thunderdolt.
If I have to guess, you're seeing them hang back until something a little more refined than that leak comes out. The kernel source will be very helpful in getting some kinks ironed out related to the battery life problem of the leak. Also, I believe there are camera and camcorder issues that are kernel related. Kernel source never gets released until after the official update goes public.
Some of the devs may also be preparing Jelly Bean ROMs and not even paying attention to ICS anymore. I'm hoping for this, as we're still going to be one revision behind when HTC releases Ice Cream Sandwich for Thunderbolt. I've seen at least one dev state that ICS to JB is a snap, relatively speaking, so we should get some sweet 4.1 action fairly quickly one the OTA drops.
The ril was one component we were lacking but jester stumbled across something in his build that gave us 1x data and liquid figured out some of the rest. The main thing we are missing now is official ics kernel. The leak we got was a crappy test build and I think that was among their first test builds but that is just my opinion. Once we get kernel source for ics things will be much better. We also need a kernel dev too because imoseyon has moved on to other devices and won't have time for the thunderbolt.
Sent from my Thunderbolt using Tapatalk 2
Yes, I am currently being a coward. Normally I could live without a camera and camcorder, but I just had a kid. Don't want to miss those moments because daddy hacks his phone.
So we got the RIL and need the kernel. After the real release comes out (probably by the time yet another version of Android will be out), we wait a few months, and bam we have the new htc stock ICS kernel. Is the only way to get it is from them intentionally releasing it? There's no way to reverse engineer it eh?
Guess we wont see another "lean kernel" then if Imo's out of the equation. Hopefully he's not the only show in town.
Duely blundered from my thunderdolt
Kernels can be hacked and changed to your liking but I think you can get into trouble if you publish it.
Sent from my Thunderbolt using Tapatalk 2
Liquid's current ICS ROM is pretty damn good, if only with a few hiccups that can be fixed without the new kernel. I can't even imagine how good it could be with a new official ICS kernel.
Kernels can be hacked and changed to your liking but I think you can get into trouble if you publish it.
Click to expand...
Click to collapse
Wouldn't imoseyon have gotten in trouble for all the great kernels he's released if that were true?
The Linux kernel is free for anyone to modify. If you improve it, you're expected to share your work. That's the beauty of open-source software.
If HTC doesn't release their source for the kernel but you hack it is what I mean.
Sent from my Thunderbolt using Tapatalk 2
If HTC doesn't release kernel source, they will be in violation of the GPL. The only source they can legally withhold is their own software, like Sense, or proprietary driver files. They don't own the kernel, so they must release the source after they release an official ICS build, and they can't go after anyone for hacking it and publishing the source. Of course, if they never release ICS, the wouldn't have to release the kernel source, and some brave dev would have to figure it out. I hope that doesn't happen.
I suspect we're splitting hairs on this one.
Technically, HTC isnt allowed to withhold the kernel source at all. But they do. So reverse engineering / decompiling the kernel is completely legal.
I'm super excited for ICS/JB/BBQ/whatever. I'm running liquid's rom on my bolt right now. It isn't perfect, but I love the overall user experience. It's a shame these things take so long to move through the pipe, but I'm very appreciative of the efforts folks are putting in to make this happen. :good: