you wouldnt have a working radio at all, not just 3g. no data no voice calls etc but i mean that of course could be patched in with cm6. as for why samsung/google went with a non hspa+ phone for tmobile i have no idea..
you wouldnt have a working radio at all, not just 3g. no data no voice calls etc but i mean that of course could be patched in with cm6. as for why samsung/google went with a non hspa+ phone for tmobile i have no idea..
I know. I was implying it.you wouldnt have a working radio at all, not just 3g. no data no voice calls etc but i mean that of course could be patched in with cm6. as for why samsung/google went with a non hspa+ phone for tmobile i have no idea..
This is no easy task and in all honesty, I doubt you will get very far. Some of the proprietary crap for the epic we don't even have di18 source. Also, the ext4 crap in 2.6.29 (di18) is broken. Modules compiled against the kernel will not load, and when compiled in kernel, the kernel will not recogize ext4 partitions. I've tried extensively.
Anything you get from di18 is likely not going to compile against anything higher than 2.6.29. Those modules we do have source for would require heavy modification to compile against the new kernel.
Those we do not have source for are not going to load, since the modules were compiled against 2.6.29.
For google to have went with 2.6.35, likely means they used something included in the release or found reason to upgrade.
Either way, good luck, but in all honesty, it probably won't happen before we have the grounds for cm7 on the epic.
You also assume that the nexus s uses the same exact hardware as the epic, in which case you would be wrong. There is a diff bluetooth chip, as well as wifi I believe.
Camera I'm not sure on. Either way, even if you did manage to get a Bootable kernel, you wouldn't get much farther than that.
Not trying to be pessimistic, just trying to be real.
Sent from my SPH-D700 using Tapatalk
Whatever happens, thanks for trying.What's the worst that happens? I fail horribly? I can live with that.
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.
I may be mistaken but if you're hoping for source from a 2.2 kernel I don't believe any exists.
Also, terran, protoss, or zerg?
I may be mistaken but if you're hoping for source from a 2.2 kernel I don't believe any exists.
Also, terran, protoss, or zerg?
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.)
Not sure where to put this sorry if it is in wrong place. Rep at ces says froyo is in carriers hands and 2.3 has been seen on epic. Rep doubts carriers will release it, but hopes carriers will go straight to 2.3. Said with new phones coming out with 2.3 the carriers don't want to release updates to improve sales of new devices.
Sent from my SPH-D700 using XDA App
Not sure where to put this sorry if it is in wrong place. Rep at ces says froyo is in carriers hands and 2.3 has been seen on epic. Rep doubts carriers will release it, but hopes carriers will go straight to 2.3. Said with new phones coming out with 2.3 the carriers don't want to release updates to improve sales of new devices.
Sent from my SPH-D700 using XDA App
I have it just about booting(;
Sent from my SPH-D700 using XDA App
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.
This is no easy task and in all honesty, I doubt you will get very far. Some of the proprietary crap for the epic we don't even have di18 source. Also, the ext4 crap in 2.6.29 (di18) is broken. Modules compiled against the kernel will not load, and when compiled in kernel, the kernel will not recogize ext4 partitions. I've tried extensively.
Anything you get from di18 is likely not going to compile against anything higher than 2.6.29. Those modules we do have source for would require heavy modification to compile against the new kernel.
Those we do not have source for are not going to load, since the modules were compiled against 2.6.29.
For google to have went with 2.6.35, likely means they used something included in the release or found reason to upgrade.
Either way, good luck, but in all honesty, it probably won't happen before we have the grounds for cm7 on the epic.
You also assume that the nexus s uses the same exact hardware as the epic, in which case you would be wrong. There is a diff bluetooth chip, as well as wifi I believe.
Camera I'm not sure on. Either way, even if you did manage to get a Bootable kernel, you wouldn't get much farther than that.
Not trying to be pessimistic, just trying to be real.
Sent from my SPH-D700 using Tapatalk