Based on the posts I've read, is there really no official stable version of Gingerbread released for the Epic 4G, and are all the GB ROMs buggy?
And I thought that we would be working towards ICS for the Epic 4G...
I'm new at this, but I thought that Android being open-source means that it would be easier to hack and modify and less reliant on the carriers to release new OS updates. Have I gotten it wrong?
AndroAsc said:
Based on the posts I've read, is there really no official stable version of Gingerbread released for the Epic 4G, and are all the GB ROMs buggy?
And I thought that we would be working towards ICS for the Epic 4G...
I'm new at this, but I thought that Android being open-source means that it would be easier to hack and modify and less reliant on the carriers to release new OS updates. Have I gotten it wrong?
Click to expand...
Click to collapse
Android is by far the best medium for end users. But the major hold up is that the source code has been held out by samsung. There was a leak of the source code recently. The rom to look for is Cyanogen. These guys build it from the ground up with no source code. If you really want to try a gingerbread leak . This is a good one. He also has a 2.2 android that is complete no bugs. here is the link to gingerbread http://forum.xda-developers.com/showthread.php?t=1190337
And the link to his 2.2 http://forum.xda-developers.com/showthread.php?t=1146630
At the moment I am using the beta cyanogen very close to completion. It is 2.3.7 and it runs smooth and fast. There are a few minor bugs like no 4g. The 4g was not a big deal for me as it only covered a small area for me.
Cyanogen link http://forum.xda-developers.com/showthread.php?t=1299621
Let us know if you need more help
Can tell you are new. Gingerbread is still only a leak. However kernel source was released for 2 days. If you look in Development and read the OPs on the ROMs find one based on the released source like the one with Heimdall in the title. They are stable with no reboots.
Sent from my SPH-D700 using XDA App
AndroAsc said:
I'm new at this, but I thought that Android being open-source means that it would be easier to hack and modify and less reliant on the carriers to release new OS updates. Have I gotten it wrong?
Click to expand...
Click to collapse
Yes... You've got it wrong. Hacking can only get you so far... Major version updates require source from the manufacturers.
If you want timely updates switch to iOS. With Android it's not *when* you're getting updates but *if* you're getting updates.
http://theunderstatement.com/post/11982112928/android-orphans-visualizing-a-sad-history-of-support
AndroAsc said:
Based on the posts I've read, is there really no official stable version of Gingerbread released for the Epic 4G, and are all the GB ROMs buggy?
And I thought that we would be working towards ICS for the Epic 4G...
I'm new at this, but I thought that Android being open-source means that it would be easier to hack and modify and less reliant on the carriers to release new OS updates. Have I gotten it wrong?
Click to expand...
Click to collapse
I'm currently running ACS' ICS beta rom. The ICS is just a launcher but its nifty. If you want a pretty stable eh17 rom w/o the ICS I used titanium to uninstall the launcher (and the other 2 launchers [beats me]) and used launcher pro plus. Makes for a stable gingy rom. I've also flashed the eh17 honeycomb explosion theme. Looks great and run awesome.
Supposedly nubernal fixes reboots... ill see as soon as I find time to flash
Lord Syrics Jr.
EPIC 4G
ACS ICS BETA v6
Eh17+ (soon nubernal)
There's always going to be bugs... Especially when devs start modifying what was most times just crap to begin with.
I strive to put out a stable ROM, but when you want to update something, something else may not always act as it did.
I'm in the midst of getting a second test version out of my ROM... Come back tonight and check it out. If you're into something semi-stock, then you'll like what i have to offer. =)
AndroAsc said:
I'm new at this, but I thought that Android being open-source means that it would be easier to hack and modify and less reliant on the carriers to release new OS updates. Have I gotten it wrong?
Click to expand...
Click to collapse
For the most part, "Android is open source" only applies to device manufacturers, and owners of Google-branded Nexus devices. The latter of which have (nearly) all platform source code available in Git repositories, including instructions for building a source-based ROM for them.
Third-party manufacturers do not release the majority of Android platform code for their devices. Some of this, like custom UI code, is not particularly relevant to us. But other of this, including proprietary kernel modules and userspace drivers for peripherals, is very much relevant. Not having the source to this makes getting full functionality out of source-based ROMs rather difficult. It doesn't help that Samsung's devices are "uniquely different" from HTC and others which makes porting source-based ROMs to them painful to begin with.
Ok... so in other words, to have a stable usable and relatively bug-free release of Android OS, we will need the carriers to release some official version for it?
Not necessarily. However it is often easier to support a new version of Android if the manufactuer provides an update to it.
AndroAsc said:
Ok... so in other words, to have a stable usable and relatively bug-free release of Android OS, we will need the carriers to release some official version for it?
Click to expand...
Click to collapse
No. I've been running GB forever now. Most of the issues were temp slip ups with roms or themes. The only pervasive one in all the leaked based roms is the reboots, which frankly I never found to be as big of a deal as many made it out to be. Our best guess is that it is sleep related, so in other words, it only happens when your phone is sitting untouched.
I had them quite a bit, but really not a big deal.
Install ACS ICS v6, and the nubernel kernel, and the reboots aren't an issue either.
At this point I couldn't care less if the official ever drops. (Not that I think it wont, it's just, also, IMHO, not nearly as large of a concern as some are making it.) To the extent I DO care, it's only because it will probably consolidate the efforts of the devs. Lots of work still being done on Froyo roms, and there's probably some hesitation on getting involved in any particular leak, because you never know when another leak will drop and make everything you're doing outdated.
Edit: This is anecdotal, but most of the "problems" people report are from people who seem to give gingerbread a shot for about 5 seconds. I'm willing to bet most of them restore data, or a titanium backup, from their froyo rom, then attribute any problems to gingerbread being buggy. It's not. It's fine. If anything a lot of the real not-just-whining outrage is over how GOOD it is. (AKA, the leaks are so solid, what's the hold up exactly)
After looking through quite a few pages and using the search I couldn't anything on a 2.3.7 Rom for this phone. I'm guessing that most of the Epic roms run off of the base of the stock Samsung rom. I don't know much about Samsung phones as I own an OG Droid running Liquid Smooth, and a Droid X running OMFGB and have found it easy enough to always update those to the latest version of Android.
I'm looking for a stock Android rom for this phone without all the extra crap attached to it.
I'm also trying to figure out how to undervolt this thing as it heats up to 104F after ten minutes of use. I put ACS's ICS EI22 V2 on there and it seems to have helped. While also uninstalling useless .apk's I don't need.
This is my wife's phone, so any roms where something doesn't work are out of the question. It was hard enough to explain the difference between Touchwiz and Launcher Pro. Thanks for any help you can provide!
2.3.5 is the highest stable stock rom. Check to the Development Sections. As far as UV/OC you'll find Kernels that support that as well.
is there are reason why roms only go up to 2.3.5?
Thanks for the help!
shreddinit said:
is there are reason why roms only go up to 2.3.5?
Thanks for the help!
Click to expand...
Click to collapse
Changes above 2.3.5 are only for phones with the NFC chip which the Epic don't have and pertain to Google Wallet.
Will this be the last official update now that Ice Cream Sandwich is coming to a phone near me (but not mine)?
CM7 Selfkang reads as 2.3.7, but without NFC, it really doesn't add anything.
kennyglass123 said:
Changes above 2.3.5 are only for phones with the NFC chip which the Epic don't have and pertain to Google Wallet.
Click to expand...
Click to collapse
I saw that, but can't find a real changelog. All I know is that it definately made both of my phones run better.
sgtkwol said:
CM7 Selfkang reads as 2.3.7, but without NFC, it really doesn't add anything.
Click to expand...
Click to collapse
Yeah, I think there is no real change for the Epic from 2.3.5 on CM7. It is more to keep all the versions uniform.
I have a general IT background of 10+ years with basic scripting skills so understand on a general level about drivers but I have been reading for several months trying to understand the EXACT nature of the problem for why i still don't see a ICS rom for the evo4g with working (or semi-working) wimaxx.
Can someone please educate me? Here is my version....
Sprint has retired the evo4g via end of life decision process and so does not have a formal team working on an ICS build of any kind for my phone. I don't agree with this decision, but i understand why Sprint is not providing me with one.
Because Sprint has retired the phone, HTC is not doing any development for the phone and so THEY aren't providing me with any drivers. I'm not sure who of these two made the business decision, Sprint or HTC, probably HTC. Either way, no formal support from either of them. I don't agree, but accept that.
As for developers coming up with their own, this is where I'm expecting magic and so instead of just crying "where are my drivers, where is my rom" i am attempting to learn why they aren't here and am requesting an education on the subject.
From my understanding, AOSP is Googles contribution for free to the world. This is a great operating system for running phones for a variety of reasons. From there, manufacturers take the basic kernel and modify it to work with their equipment. This is where it gets a bit confusing for me.
I think that the manufacturers do two things. One, is that they work with chip manufacturers to obtain proprietary drivers for specific chipsets that integrate into the basic kernel. Two is that phone manufacturers ALSO modify the kernel so as to make a proprietary version of the kernel. So HTC made a propritary version of the kernel and incorporated SENSE (among other things) into that proprietary kernel, and hooked up proprietary drivers that may or may not work with the AOSP kernel to provide services such as video and wimax and sound etc.
I know teamwin some how reverse engineered or manufactured a wimax driver for gingerbread such that the wimax driver was available for the AOSP Gingerbread kernel, but teamwin or nobody else has done that such that a wimax driver is available for the AOSP ICS kernel
I know that HTC has wimax working on some of its phones that have ICS via threads that talk about it being leaked (i.e Nexxus 4g).
So here are some questions... I suspect none of them are accurately asked.
Version1
Does AOSP ICS kernel have the ability to have a wimaxx driver built/interfaced into it?
If so, is it HTC that technically owns this driver or another specific company?
Version2
If AOSP ICS kernel does not, does that mean we currently need both a specific evo4g ICS kernel AND the wimax driver built?
Or are either of these easy to build and we just need one part of them built...meaning the wimax driver is out in the world for developers now and all that needs to happens is for someone to put some "hooks" into a new evo4g kernel such that they would work with the driver.
I apologize in advance if i broke some posting rules. I can't post in developement section yet so i placed in q/a where it says "any question". I did some basic research on the subject so i'm not just whining i don't have my driver. I am trying to get at the specific thing that needs to happen for my evo4g rom to have wimax working on ICS.
My theory is "HTC owns the wimax driver for ICS but won't release the source code as they only want to bring certain wimax devices into the ICS generation. It is proprietary to a specific kernel so if it was released, it would not instantly work with the AOSP kernel and other kernels. It would still need further development (but on which end???). It is illegal and difficult for someone to reverse engineer this ICS WIMAXX driver. It is legal, but still difficult for someone to create a generic ICS WIMAXX driver. Since both are difficult they will not happen soon."
Thanks for your thoughts in advance.
*DISCLAIMER - everything I say below is based on belief and may be wrong.
Believe that the majority of what you said is correct.
Slight thing - nexxus 4g (I believe this is sammy/goog, no?)
While kernel may have specific customizations for sense, believe sense is built on top of OS (ICS) and not IN the kernel itself per se.
(MOST LIKELY SCENARIO): Believe that HTC has to release an update where ICS and Sense crap all play nicely together and sprint has to test it and release it and then xda devs need to fix it to remove bloat, optimize, and ensure no more CIQ-ish kind of crap or htc spy crap or root removal...can't trust any of these bastards. The update will have ICS + Sense + Kernel (including the proprietary or binary blob drivers for things like wimax, camera, screen).
(IDEAL SCENARIO): HTC quit being little Apple-tards, realize that their differentiator is that they ARE NOT a walled garden - that customer enthusiasm is a good thing. They get off their asses and send a working kernel source for ICS AOSP (just the kernel) to team douche/team win/team kang... somebody cool (officially or unofficially) and BAM - everything works great in the AOSP/AOKP world. I mean really - if we are going to be in a walled garden, is not Apple's the best? Why not just buy iphones if HTC's gonna be a giant douche? Turd sandwich or Samsung would be better options.
Please correct me if I'm wrong. This is a learning experience for me too!
Wondering about this as well. It would be nice if the source code for the nexus 4g(wimax) would help us on the EVO front.
One of the biggest problems for the ics rom is its not based on the kernel its supposed to be running. The kernel has been frankenkerneled from tiamats gb kernel with the correct settings to run as ics. While I know that the kernel has been updated to somewhat but its not the true ics kernel some of these other phones are running and also while team douche or team win got the wimax working on aosp gb back in the day...they are no longer working on the evo and also wimax back then wasn't a quick fix. It was on the back burner for the longest time. I commend you on wanting to work on the drivers and learn. I would start by contacting prelude drew via twitter and or atyoung the current dev for the mason ics kernel that hes had great success with. Those two could point you in the right direction or bring on board with them on getting everything working especially with your strong IT background it will come in handy.
Forgive my fading memory, but wikipedia reports Android supports wimax directly.
I thought I read elsewhere that 2.3 GB or 3 and on was supposed to support wimax natively - thereby obviating team win's wimax "fix."
?So ICS doesn't support wimax (or it does?) but we need a driver from the mfg? Is this a broadcom/qualcomm thing? Proprietary driver? Supplied to HTC as a binary blob rather than source?
Will we likely have a first breakthrough when HTC releases the source to ANY ICS kernel?
Will we similarly have a closer breakthrough when HTC releases source to a phone with wimax by same mfg?
What happened to the leaks? Ninja911? Fxck it seems dev has stagnated on these devices. So much hardware and we can't use any of it! GRRRR Why is anyone still buying HTC when they are cxckblocking us so entirely?
Surely if HTC wanted to they could release an ICS AOSP kernel source with little to no effort that works with AOSP roms right? They don't have to do any of their purported excuse for the delay (i.e. get ICS and Sense to play nice, right?)
As it is ICS AOSP can't use 4G, Netflix, Front Camera, HWA...?
On the E3d there's no 4G, no 3D camera, no 3d display, ...
HDMI/MHI surely won't work, will they?
Basically anything that makes the Evo special above a free android type phone?
Along with other issues.
GOD I'd LOVE a 4G working MIUI ICS, CM9, ... but it will never happen - just HTC's corporate culture? I think we have to vote with our $ and support Samsung or a hungry underdog (like HTC used to be) such as Huawei, LG?
Sorry for the vent. Please correct if I've miss-stated above. Learning experience.
My sentiments exactly...
I've been curious about this for the past couple months, I just assumed it was because Sprint felt the Evo4G had run its course, had a good life, etc, and it was time to retire it.
And then since Sprint was no longer supporting HTC followed suit by deciding since Sprint was cutting support for it, HTC realized it was kinda pointless for them to upgrade it. It IS almost 2 years old, so I'm not too irked by it, but I'd like to echo the OP's concern about them not just releasing some ICS compatible drivers for those of us with tinkering hands to play with.
*sigh* Guess I'll just have to wait until the LTEVO is released...
The evo was classified EOL(end of life) before ICS source was even released by Google, therefore HTC has no ICS drivers for them to release because a) they never built anything ICS for the evo and b) alot of the hardware drivers are proprietary and come from the individual hardware manufacturers and not HTC. HTC simply compiles the drivers into a final build to make each specific device function
Sent from my SPH-D710 using xda premium
-EViL-KoNCEPTz- said:
The evo was classified EOL(end of life) before ICS source was even released by Google, therefore HTC has no ICS drivers for them to release because a) they never built anything ICS for the evo and b) alot of the hardware drivers are proprietary and come from the individual hardware manufacturers and not HTC. HTC simply compiles the drivers into a final build to make each specific device function
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Ok, so i understand that HTC and Sprint are out of it, but WHO is the manufacturer of my wimax antenna and is this antenna in any device that has ICS running on it? If so, I'm sensing from this post that even if they release this driver, it still won't help cuz the EVO 4g ICS rom's are actually frankensteined gingerbread code? That seems even weirder. Why wouldn't the EVO 4g ICS roms be frankensteined ICS code massaged for the evo from ICS?
Thanks for the term BLOB. I'll research how that interplays with kernel and OS version and driver and see if i can get a better handle on it. It just annoys me that i'm paying for wimax but in order to use it i have to be on older OS. This phone is totally fine for my basic needs and still has plenty of life left in it. They are accellerating the "planned obselecense" way to fast. Sorry for the typos...its late for me. Thanks everyone.
ittsmith said:
Ok, so i understand that HTC and Sprint are out of it, but WHO is the manufacturer of my wimax antenna and is this antenna in any device that has ICS running on it? If so, I'm sensing from this post that even if they release this driver, it still won't help cuz the EVO 4g ICS rom's are actually frankensteined gingerbread code? That seems even weirder. Why wouldn't the EVO 4g ICS roms be frankensteined ICS code massaged for the evo from ICS?
Thanks for the term BLOB. I'll research how that interplays with kernel and OS version and driver and see if i can get a better handle on it. It just annoys me that i'm paying for wimax but in order to use it i have to be on older OS. This phone is totally fine for my basic needs and still has plenty of life left in it. They are accellerating the "planned obselecense" way to fast. Sorry for the typos...its late for me. Thanks everyone.
Click to expand...
Click to collapse
Its Frankenstein gb code with ics code intertwined cause there are no drivers for ics that'll run the evo so the other kernel was modified to work for ics
I'm no expert on Android but I do understand operating systems pretty well, so here is my best guess as to what is going on:
1) A kernel is pretty hardware generic (maybe architecture dependent only) and provides various functions to the software that runs on top of it (e.g. the Dalvik VM that runs most Android apps and Android/Sense UI) and it is provided by Google. Each kernel will need to have certain features/capabilities that are specific to a given Android release (i.e. you can't just use a GB kernel with ICS since it will be missing some features expected by the ICS UI and Dalvik VM).
2) Individual manufacturers need to add drivers (kernel modules) in with the generic kernel from Google to support the specific chips on a given phone. So, for our Evo 4g there need to be drivers for the WiMax chip, camera, bluetooth, etc.. These drivers need to be updated for each new Android release kernel. Depending on how a release kernel changes, this could be just a re-compile or it might require somebody to rework the code. If the WiMax code needs more than just a recompile, then it is either a lot of work for an amateur dev team to try and refactor the GB WiMax code to work for an ICS kernel OR HTC needs to do the work and release it for us. Since the latter is unlikely to happen, getting WiMax working would require a lot of work from an amateur developer.
3) It is also possible that some drivers are just released as binary blobs that are loaded by the kernel. In this case, a binary driver that was compatible with a GB kernel may no longer be compatible with the ICS kernel. In this case if HTC doesn't release it, it would require a ground up write of an ICS driver for WiMax, which is unlikely to happen.
The above is my best guess as to what is going on as a general field expert on kernels/drivers. Since I'm not as familiar with Android specifically, I could be off on what is happening here. We'd need somebody who has played around with Android kernel development for the Evo 4g to say for sure.
bjohanso said:
I'm no expert on Android but I do understand operating systems pretty well, so here is my best guess as to what is going on:
1) A kernel is pretty hardware generic (maybe architecture dependent only) and provides various functions to the software that runs on top of it (e.g. the Dalvik VM that runs most Android apps and Android/Sense UI) and it is provided by Google. Each kernel will need to have certain features/capabilities that are specific to a given Android release (i.e. you can't just use a GB kernel with ICS since it will be missing some features expected by the ICS UI and Dalvik VM).
2) Individual manufacturers need to add drivers (kernel modules) in with the generic kernel from Google to support the specific chips on a given phone. So, for our Evo 4g there need to be drivers for the WiMax chip, camera, bluetooth, etc.. These drivers need to be updated for each new Android release kernel. Depending on how a release kernel changes, this could be just a re-compile or it might require somebody to rework the code. If the WiMax code needs more than just a recompile, then it is either a lot of work for an amateur dev team to try and refactor the GB WiMax code to work for an ICS kernel OR HTC needs to do the work and release it for us. Since the latter is unlikely to happen, getting WiMax working would require a lot of work from an amateur developer.
3) It is also possible that some drivers are just released as binary blobs that are loaded by the kernel. In this case, a binary driver that was compatible with a GB kernel may no longer be compatible with the ICS kernel. In this case if HTC doesn't release it, it would require a ground up write of an ICS driver for WiMax, which is unlikely to happen.
The above is my best guess as to what is going on as a general field expert on kernels/drivers. Since I'm not as familiar with Android specifically, I could be off on what is happening here. We'd need somebody who has played around with Android kernel development for the Evo 4g to say for sure.
Click to expand...
Click to collapse
You're fairly close, the android kernel is essentially the Linux kernel, HTC doesn't build the wimax driver I believe its qualcomm that makes the radios in our devices but I'm not sure they make the wimax radio or just the cdma radio. They make a good amount of the hardware in the evo from radios to gpu to audio control components. Building the drivers isn't an easy task for any single dev without existing source to modify, even someone who does it for a living would have a long, difficult road to building a driver from the ground up with no preexisting source to use as a map I've been working on drivers for ics for a cpl months and its not easy starting with a blank page and starting code from scratch. Even with the existing aosp wimax drivers available for the evo, so much has changed in ics modifying the drivers is basically like starting from scratch cuz so much code needs to be reworked. It will probably be one of the last things to be added just like it was on gb
Sent from my SPH-D710 using xda premium
What about when they update the EVO3D? Will either the ics update for the 3d or when they release the kernel source for 3d ics help?
sinnedone said:
What about when they update the EVO3D? Will either the ics update for the 3d or when they release the kernel source for 3d ics help?
Click to expand...
Click to collapse
Probably not since the 3d uses a different chipset and the insides look nothing like the evo
sinnedone said:
What about when they update the EVO3D? Will either the ics update for the 3d or when they release the kernel source for 3d ics help?
Click to expand...
Click to collapse
The Evo Design 4G update would help us more than the EVO 3D would since the specs are similar to ours
Sent from my PC36100 using Tapatalk 2 Beta-6
Papa Smurf151 said:
Probably not since the 3d uses a different chipset and the insides look nothing like the evo
Click to expand...
Click to collapse
I was going on the assumption that the only roms with newer versions of sense that have working 4g are ports from the Evo3d.
you guys are nerds and i envy you all...
There is so much awesome going on.. our best bet, would be to grab the EVO design 4g update. That would be as close as we can get.
then someone can port it here
Hopefully HTC will release a source code for the kernel & or RUU. Then we can go from there...
Sent from my PC36100 using xda premium
Thank you, i am learning alot.
Is there a page that discusses the evo 4g specifically and shows what parts are frankensteined and what are not. Ideally, something like
Radio
- wimax - unavailable
- cmda - Use ICS wrapper on Gingerbread kernel driver 2.2. wrapper created by developer abc. Gingerbread kernel driver - HTC Android 2.3 patch - version 12341
Graphics
- something - blob - developer xzy
- something else - blob - developer def
- something else - kernel driver - Standard Android 4.0 patch - version 5.6
Camera
- front - ICS blob - developer pdq
- back - unavailable
Microphone
- standard - ICS Kernel Driver - Standard Android 4.0 patch - version 3.3
etc
I would think that each phone has a "map" of what is available and I would think developers would share. Obviously the first thing I would look at on this map is what did Teamwin do? I can't imagine they created a BLOB, but instead did they use a wrapper on a Froyo wimaxx driver or a wrapper on a gingerbread sense patch or did they write it themselves.
Doing some research I've gotten this data...am I on the right track to build my map of the EVO 4g for ICS. Why isn't this public knowledge somewhere. I am trying and not being lazy...well, not super lazy...
I got this from the cm9 thread for evo, thanks people in there for posting details
mason v14sbc ics kernel (Nonfso nonsbc, hwa kernel)
back camera - system/lib/hw/1sd8k.so
Camcorder
libmediaplayerservice.so
libOmxCore.so
libOmxVdec.so
libOmxVidEnc.so
libstagefright.so
libstagefrighthw.so
@ittsmith, sounds like you are aiming to be the next kernel genius. With this type of info you will be able to develop on kernels for far more devices than just evo...
Anyhow, I am no developer by any means just getting into programming, but I wanted to lay out my train of thought and see if it stands up or has any insight.
Any manufacturer has to start with AOSP source, and then build for their specific device. So, if theoretically HTC was building an ICS kernel they would begin there, with the latest source from Google. Then they would add in the device tree, much like building a ROM from source only here we are talking core drivers and such for proprietary hardware, and finally build a custom kernel for that device.
Now of course these guys have full access to source and drivers and the like of which we may not have... Though htcdev does have kernel source on their site. So, like you said initially why not take the ICS kernel and make it compatible to EVO? That is exactly what HTC would do, and does for the other devices that are receiving updates...
I remember running gingerbread long before there was an update to the evo, and there were gingerbread kernels... So I am just thinking we don't have the tools and know how to get the job done but all the pieces may be there. I would say petition either toastcfh or even Adam Outler, as these two are pretty damn magical when it comes to Android devices and the linux kernel.
I noticed the Evo Shift has working WiMax on ICS Roms because of processor similarities and leaked Roms. Is it possible the Evo 4g will get working WiMax on ICS Roms also?
EDIT: Found this thread: http://forum.xda-developers.com/showthread.php?t=1604732
Possible not probable?
Sent from my brain using my hands
i was recently using a ICS rom where 4G was working just fine... i forgot which one it is, ive been switching ICS Roms back and forth
Not any time soon as code has to be written from scratch due to HTC not supporting evo any longer. And any rom that's says its working is not true ics as of right now
XDA Moderator
XenonV said:
i was recently using a ICS rom where 4G was working just fine... i forgot which one it is, ive been switching ICS Roms back and forth
Click to expand...
Click to collapse
Was probably an ICS themed gingerbread ROM, no ICS roms currently have WiMax. Might as well just hope they start working on WiMax for jellybean.
To shed some light onto this Wimax is indeed working on a ICS Rom (CM9) For the Evo 3D Quote from Toast member of Teamwin"
http://techerrata.com/file/toastcfh/ … <~~ wimax in cm9! check it out."
What does this mean? Well Wimax is working on ICS but that's all. Until Teamwin is ready to submit the Code were not going to see it here anytime soon.
Also do not download that rom it's for the Evo 3D not 4G.
also...
I was wondering about this. It seems like most devs are making the jump to other devices... What i've noticed by working on the HTC Hero and on the HTC Evo 4g is that the further we can push legacy devices, the more we find out about optimization not only for those devices, but newer devices as well. At least in the case of the Hero vs Evo, the ability to run optimized code with the Hero lead me to even more optimization in the Evo. So for those devs pumping it out with legacy devices, KUDOS! You've helped me a TON with holding on to my Evo for nearly 2.5 years and being not only satisfied with its operation, but able to jock any Apple fanbois I come across
Another question that seems pertinent to this discussion: How about a 3.0+ Linux kernel? Is it possible for the Evo to run this? Is there development as of now? I thought that ICS and Jellybean were difficult ports because of the kernel specifically... is that the reason?
Cheers
Soc
Atyoung has said that he's working on a 3.x kernel, but recently, his job moved him, and he's been busy with that stuff. So, it's coming. Just don't expect it soon.
Edit: From my understanding, it's not so much the kernel version that makes ICS development difficult. It's the lack of drivers being released. That's why HWA support took so long, and that's why the FFC still doesn't work in ICS.