Only problem there is the EVO and Epic have VERY different WiMax radios. From everything I've heard, the Epic's radio follows Linux standard, whereas the EVO's does not, making the WiMax radio in the Epic much easier to get functioning than the EVO's.
[Dev] AOSP Gingerbread
- Thread starter msponsler
- Start date
Only problem there is the EVO and Epic have VERY different WiMax radios. From everything I've heard, the Epic's radio follows Linux standard, whereas the EVO's does not, making the WiMax radio in the Epic much easier to get functioning than the EVO's.
Well I hope so.. do you have a source on that? Id love to read up on the differences.
Sent from my SPH-D700 using Tapatalk
the evo wimax was filled with proprietary bits, and even then it was reversed and still using htc stuff.
whats the status on this? as i would imagine unless your building the kernel against current cm6 source your not going to get a whole lot farther then a kernel panic... but thats just my theory on it all
whats the status on this? as i would imagine unless your building the kernel against current cm6 source your not going to get a whole lot farther then a kernel panic... but thats just my theory on it all
AOSP Gingerbread != the kernel.
Gingerbread (android in general basically) is the set of programs, daemons, etc... that sit in user space and interact with the kernel, that sits in kernel space.
You wouldn't necessarily need 2.6.35 (kernel on nexus s gingerbread) to run gingerbread. Obviously, 2.6.35 would have the best features and optimizations for Gingerbread -- since it was written for 2.6.35. But you could technically use 2.6.29 and on. As long as gingerbread does not make any specific system calls into kernel space that are only supported with 2.6.35 and onward.
The specific module's source files for the SGX530 video, Qualcomm QSC6085, etc... are included with samsung's 2.6.29 kernel source. I'm trying to compile them with 2.6.36, and will try with 2.6.35 as well. Modules can be a lot trickier, as they usually are a lot more tailored for a specific kernel. Especially if they are already compiled.
A couple of avenues that I am taking:
-Attempt to compile epic 4g's modules with 2.6.36, 2.6.35, and on backward.
-I re-compiled samsung's 2.6.29 kernel with the driver modules and ext4, etc... I'm going to attempt to run gingerbread off that, and watch how quickly it blows up...
-I'm going to look at other kernel's, like noobnl's kernel he put in cyanogenmod. It's 2.6.32, and it has video / wifi / CDMA radio / etc.. in it. I need to get ahold of him and figure out a) what source is he using -- from samsung, kernel.org, etc... and what modules he's using. b) his .config file for the kernel.
I'm going to take the same avenue with Dameon87 about his compiled kernel's for epic 4g froyo. As well as looking toward the manufacturer for information about their kernel drivers for their hardware.
Using 2.6.35 modules from the nexus s kernel wouldn't be too bad for things like the camera, wifi, video, etc... but WOULD be a problem with the CDMA radio / GPS since they are different obviously (CDMA vs. HSPA+).
I've got a bunch of options and ideas I'm throwing around in my head. Feel free to contribute your thoughts / concerns / ideas. I'm not trying to do this in the dark and say "look what I did on my own!" if / when I get any type of usable progress. It's Linux, and it's a community effort
With that said, I will work diligently on this as much as possible. Between work (and if you've ever been a Sys Admin, you know that you're never really "off the clock"), my wife, my addictive StarCraft II habit, the gym, and every Thursday happy hour... I'm focused on this 100%!!!
AOSP Gingerbread != the kernel.
Gingerbread (android in general basically) is the set of programs, daemons, etc... that sit in user space and interact with the kernel, that sits in kernel space.
You wouldn't necessarily need 2.6.35 (kernel on nexus s gingerbread) to run gingerbread. Obviously, 2.6.35 would have the best features and optimizations for Gingerbread -- since it was written for 2.6.35. But you could technically use 2.6.29 and on. As long as gingerbread does not make any specific system calls into kernel space that are only supported with 2.6.35 and onward.
The specific module's source files for the SGX530 video, Qualcomm QSC6085, etc... are included with samsung's 2.6.29 kernel source. I'm trying to compile them with 2.6.36, and will try with 2.6.35 as well. Modules can be a lot trickier, as they usually are a lot more tailored for a specific kernel. Especially if they are already compiled.
A couple of avenues that I am taking:
-Attempt to compile epic 4g's modules with 2.6.36, 2.6.35, and on backward.
-I re-compiled samsung's 2.6.29 kernel with the driver modules and ext4, etc... I'm going to attempt to run gingerbread off that, and watch how quickly it blows up...
-I'm going to look at other kernel's, like noobnl's kernel he put in cyanogenmod. It's 2.6.32, and it has video / wifi / CDMA radio / etc.. in it. I need to get ahold of him and figure out a) what source is he using -- from samsung, kernel.org, etc... and what modules he's using. b) his .config file for the kernel.
I'm going to take the same avenue with Dameon87 about his compiled kernel's for epic 4g froyo. As well as looking toward the manufacturer for information about their kernel drivers for their hardware.
Using 2.6.35 modules from the nexus s kernel wouldn't be too bad for things like the camera, wifi, video, etc... but WOULD be a problem with the CDMA radio / GPS since they are different obviously (CDMA vs. HSPA+).
I've got a bunch of options and ideas I'm throwing around in my head. Feel free to contribute your thoughts / concerns / ideas. I'm not trying to do this in the dark and say "look what I did on my own!" if / when I get any type of usable progress. It's Linux, and it's a community effort
With that said, I will work diligently on this as much as possible. Between work (and if you've ever been a Sys Admin, you know that you're never really "off the clock"), my wife, my addictive StarCraft II habit, the gym, and every Thursday happy hour... I'm focused on this 100%!!!
not to be a **** but where did you hear that it has hspa+?
even google seems to be convinced its just regular umts
Wouldn't the CM6 Epic kernel source be available on his Github? https://github.com/noobnl
(Dunno if it's actually on there, but it might save some trouble.)
I'm in. Not super familiar with kernel building, but I am very familiar with embedded code development, cross-compiling, OSEK, debugging, configuration management, issue reporting etc, make-support, and flash bootloaders.
As far as I know, all he did was take the DK28 kernel, ripped out the initramfs, made some changes to point to various things, and repacked the zImage. We still don't have the source.
not to be a **** but where did you hear that it has hspa+?
My golden retriever, Rupert, told me.
My black lab, Nibbler, also concurred. I took their word for it.
Honestly, I just assumed it was HSPA+. It's CDMA and not compatible with Sprint's network, which is what matters.
The source would be nice to have. I'll have to bug him about it. I've got plans tonight, and I won't be able to do any tinkering until tomorrow.
uhh ok well i think you might have soem things mixed up so ill try to give teh laymans of it
GSM:
worldwide standard
uses analog (1G)
edge (akin to dialup data)
3g (umts/wcdma)
Hspa+ (4g)
CDMA:
more americanized standard
analog (1g)
cdmaone (dialup/digital version of cdma)
evdo (3g)
4g (LTE/wimax)
so as you see the nexus s is not compatblie with any cdma carriers, in fact its barely compatble with ATT and tmobile.. (well i mean it "works" on either but tmo gets 3g data only and att i think gets edge)
With that said, I will work diligently on this as much as possible. Between work (and if you've ever been a Sys Admin, you know that you're never really "off the clock"), my wife, my addictive StarCraft II habit, the gym, and every Thursday happy hour... I'm focused on this 100%!!!
LOL, sound like you have a lot of free time, jk. Thanks for your efforts!
Sent from my SPH-D700 using XDA App
LOL, sound like you have a lot of free time, jk. Thanks for your efforts!
Sent from my SPH-D700 using XDA App
Samsung should just release whatever they have and jut let the devs fix it. I wouldn't be surprised if 5 people here could et it up and running faster than they could.
Sent from my SPH-D700 using XDA App
Sent from my SPH-D700 using XDA App
Once cm6 is out of beta and cm7 is released im guessing gingerbread isnt to far away.
Anyways don't take my word or anything im no dev.
But i 100% support this more devs the better. Keep up the work.
Sent from my SPH-D700 using XDA App
Anyways don't take my word or anything im no dev.
But i 100% support this more devs the better. Keep up the work.
Sent from my SPH-D700 using XDA App
Why would tmobile / samsung release the nexus s non-hspa+ ??
I get that nexus S isn't cdma compatible. My point was, you could get a nexus s rom to run on the epic -- you just won't have a working 3G radio.
But, the compiled kernel modules for the video, wifi, and such (not radio) should be portable to the epic.
Similar threads
- Locked
Top Liked Posts
-
There are no posts matching your filters.
-
6Yeah, 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...1
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.1
uhh ok well i think you might have soem things mixed up so ill try to give teh laymans of it
GSM:
worldwide standard
uses analog (1G)
edge (akin to dialup data)
3g (umts/wcdma)
Hspa+ (4g)
CDMA:
more americanized standard
analog (1g)
cdmaone (dialup/digital version of cdma)
evdo (3g)
4g (LTE/wimax)
so as you see the nexus s is not compatblie with any cdma carriers, in fact its barely compatble with ATT and tmobile.. (well i mean it "works" on either but tmo gets 3g data only and att i think gets edge)1
I haven't used any of your Roms, so I don't know what kernel rev you use. Do you have any kernel / Samsung module source on got hip I can sift through?
I realize that the chances of success are slim at best, but hey why not give it a shot?
What's the worst that happens? I fail horribly? I can live with that.
Sent from my Samsung-SPH-D700 using XDA App
