yashsingh1/xdaforums huggingface dataset:
[EVO 4G Android Development] -shift-:
you forgot that credit must be given to the proper parties as well. too many times "devs" "borrow" code (rom/kernel/app) and don't credit the source. that makes the free open source act equal to thievery.

it's a proprietary implementation. with the race on for the fastest wireless network, it's only natural for sprint to hold their biggest cards close to their chest. verizon/att will be doing the same when they launch their lte phones.
[EVO 4G Android Development] salesrep2189:
Donation

Please put me down for $30 at least. I love cyanogenmod and I hate having to keep a backup of some crappy Sense based rom to restore when I have to tether 4g. It's a beating!
[EVO 4G Android Development] mitchellvii:
Never gonna happen...

If they haven't figured out 4G on CM6 by now, they never will. There is something obviously vital in the process that without access to the source code will be pretty much impossible to figure out.

CM6 is great but will NEVER have 4G (unless a spy gets them the source code).
[EVO 4G Android Development] -shift-:
You have no idea what you're talking about.

Edit:

(I'm slightly drunk right now but...) WiMAX is a very tough nut to crack, but not impossible to reverse....

Swyped from my EVO via the XDA app
[EVO 4G Android Development] jefbal99:
Hasn't cyanogen tweeted that they have most of 4g done and it will be in 6.1.1?

I can't wait to see it and give CM a try...

Swyped from my Fresh EVO via XDA App
[EVO 4G Android Development] uhhmoney:
put me down for $25
[EVO 4G Android Development] -shift-:
yes. wimax and hdmi will be in 6.1.1. work on wimax is ongoing.
[EVO 4G Android Development] sarahlegs:
Put me down for $13.37 because that's what these guys are. If they can make the 0004 hardware camera, HDMI and 4g work, I will shower them with joy (and probably a bit more scratch).

Cheers.
[EVO 4G Android Development] dj_L:
Unfortunately shift_, attribution is not required under all free licenses. Fortunately, a good percentage of developers operating under those licenses *choose* to do so whether required or not. From some of the comments I've seen in the past few months, I gather that a small, yet still significant portion of the ROM developers are still a little wet behind the ears WRT open source software. Don't get on them too hard about it. A bit of time to grow up and that small portion will either get bored and leave, or they'll begin to understand and give credit where credit is due, and continue to contribute. Also, don't ever put it past someone to simply forget. Often times, a polite inquiry as to the source will correct those oversights.

Correct. Additionally, I don't believe that Sprint owns the software to begin with, so no option for them to open it up. Please understand that none of what I'm saying is fully understood or confirmed. It is only what I've been able to dig up so far and I haven't had the time to *really* dig yet, so take my comments with a grain of salt. With that said, I'm pretty sure that Sprint is using Sequans's S3Max. I suppose the only way to get that is to buy a dev board from Sequans, which still would not provide us with legally redistributable software.

The other alternative that I've seen, as far as a ready made solution, is to utilize the CLEAR Connection Manager (which is open source, at least partially if not completely). I suspect, however, that a significant portion would have to be modified for the Sequans hardware, and even further for Android. Again, I'm still not fully versed on any of this yet, and I have not been able to catch the dev on IRC yet to confirm any of my limited research. I'm told that one very popular person in particular is on a mission of sorts to get this done, and has been actively working on it. I also have a book that I've been neglecting while the other authors/editors have been carrying my weight as I play with Android, so I've got to focus a bit more on that for the next few days.

Anyway, I am probably way OT at this point. This thread is about giving a little back to the devs, not the actual development work.
[EVO 4G Android Development] kthejoker20:
I am working on a kernel for4g. hopefullyI can get it working. I want there bounty. unless someone beats me to it
[EVO 4G Android Development] dj_L:
Let us know how that kernel goes on 35...some significant changes needed, but much more than working kernel needed.
[EVO 4G Android Development] -shift-:
here's the agreement that devs have to abide by if they are to post and share their work on xda:

http://xdaforums.com/showthread.php?t=755531

still, i agree that. at its most basic level, it is simple courtesy to acknowledge the source. i'm usually lenient on most new guys when they play with code and want to share, but since the last kernel debacle here, my patience with them runs very thin.

you're correct. glad to see someone with knowledge sharing their thoughts instead of the usual "ZOMG NO 4G YET?? IT'S EASY, COPY AND PASTE FROM SENSE YO!"...
[EVO 4G Android Development] ted3ma1:
Put me down for 8$
[EVO 4G Android Development] p-slim:
i think its a little bit more then the kernal. cyanogenmond kernal actually has support for wimax already implemented.
[EVO 4G Android Development] strung:
put me down for $20
[EVO 4G Android Development] Shinzul:
I am genuinely curious - not trying to offend anyone at all here, but, does it seem like this thread is having any impact on the state of 4G in CM?

Is there even any way we can tell that?
[EVO 4G Android Development] strung:
they workign on it. at least with thsi fund they could buy xtra phones if they need 'em for testing
[EVO 4G Android Development] mrmylanman:
Glad to see this thread grows every time I check back! I have been using MIUI lately (mostly) but I think once 4G works on CM it will probably be portable to MIUI (hopefully?). Still can't wait for it to happen since I spend a lot of time in a 4G area.
[EVO 4G Android Development] jgonza34:
Put me down for $10

Sent From My Cyanogen Evo
[EVO 4G Android Development] illogic6:
I will chip in $10.75, but only if the 75 cents is counted in the total.
[EVO 4G Android Development] brian m:
I will see your $.75 and raise you $.50!!! ;)

I'll contribute $11.25
[EVO 4G Android Development] dj_L:
Actually, IIUC, there were some changes in sdio in 2.6.3{5,6} that left the current patches unusable. http://xdaforums.com/showpost.php?p=9050649&postcount=6118 so some kernel work is actually needed, however, that is not exactly a priority ATM. Getting the connection and EAP auth working with current kernel is the main issue as I've understood it. Again, I have no contact with the real devs, just what I've picked up from various threads. The updated kernel module will come pretty quick when Sprint updates the available open source for the kernel, or when the day comes that we can test ourselves without using a Sense build. :-)
[EVO 4G Android Development] dj_L:
I'm not familiar with the kernel debacle mentioned above, however, I did read the URL you posted. I think it should probably be extended a bit so that people understand their rights as developers too. I personally give away everything that I've ever contributed, even if the original code falls under BSD, research, or even limited use licenses. GCC-3.3 patches for JDK under both the SCSL and JRL licenses were fun to dance around (well before OpenJDK was an option). Between website update scripts and manual deletions of my READMEs over a couple of months, I finally put the entire text of both licenses into the header of the patches themselves.

It's probably not a huge deal since most things developed here will be java and the classpath exception applies under OpenJDK, and by proxy the mobile edition in its current revision. However, a mention of the "GPLv2 with Classpath Exception" and LGPL should probably be made. I'll try and take a stab at a revision a little later on this week if it would be welcome. I'll have plenty of time to compose a short addition once I get to working on Xorg and Trinity this week. Both of those take quite a while to compile.

Thanks, and correct about which? Remember I haven't confirmed anything just yet regarding my own comments above. If you can confirm or deny any of my suspicions mentioned previously, please, please do so as it might save me (and potentially others) some work. While the ground-up approach is better for all of us as a whole, I am still looking at the alternatives for a 'quick fix' when I have the time...mostly because I enjoy toying with my devices (though I would certainly like to work with the latest available ground-up bits sometime after I get my book updates done to the bigger packages that I've committed to).

TIA.
[EVO 4G Android Development] kpoz:
New total: $2,178.37
[EVO 4G Android Development] sladehawke:
$10.73

Are we going to get PM's when it is time for donations? I don't regularly watch this or the CM thread...
[EVO 4G Android Development] mkeena0305:
Raise mine to 50
[EVO 4G Android Development] Doncabezon:
CM with 4G count me in. 20 USD.
[EVO 4G Android Development] Crossrocker:
I think this thread does a lot to motivate cm team to work on 4g. Cm is on many many devices and we are not special. So, there is no need for them to put SO much work into 4g while they could be working at other stuff. Kpoz, thank you.

A drop of Chuck Norris's semen was placed on the IPhone. We now have the Htc Evo
[EVO 4G Android Development] mskpop:
Put me down for 10$ even though we don't have 4g yet lol. Eventually we will.. hopefully.. pm me when it's due
[EVO 4G Android Development] strung:
http://twitter.com/cyanogen/status/7691907190755328
[EVO 4G Android Development] lovethexi23:
So all these people are basically posting for nothing.

If thats the case...........i Offer my yearly salary of $89,294 as a bounty, lol
[EVO 4G Android Development] kpoz:
Yes. I will notify everyone accordingly.
[EVO 4G Android Development] kpoz:
You need to read his response in context.
[EVO 4G Android Development] strung:
4gggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggg
[EVO 4G Android Development] Crossrocker:
Kpoz you forgot to add the $83,249 ;)

A drop of Chuck Norris's semen was placed on the IPhone. We now have the Htc Evo
[EVO 4G Android Development] LifeInTheGrey:
It's $89,294 ... and not a penny less!
[EVO 4G Android Development] strung:
i took a look the other night while running the cyanogenmod nighlty

the sequans driver was there, so i insmod'd it into the kernel

then i saw wimax0 under netcfg, so that was good

but i guess we need some userspace stuff to setup the device

so at least the driver (kernel module) is there and the interface exist
[EVO 4G Android Development] kpoz:
When you give me your bank account number and a statement confirming the presence of the above referenced funds, I will add it to the list.
[EVO 4G Android Development] Crossrocker:
Right. haha.

A drop of Chuck Norris's semen was placed on the IPhone. We now have the Htc Evo
[EVO 4G Android Development] strung:
I took a look at it again today. It looks like "insmod sequans_sdio" and then /system/bin/sequansd is run when the 4G is turned on. Possibly some shell script is run first that I couldn't find. You can see what it does in /data/wimax/log/sequansd.log. I don't know how to figure out what arguments are given to sequansd or how the system kicks that thing off in the first place. That thing (sequansd) apparently initalizes the wimax device by uploading a firmware and then setting a bunch of stuff. After it's all setup you have a wimax0 interface. Maybe these binaries could be copied over to CM along with the appropriate init script modifications; I haven't tried it yet.
[EVO 4G Android Development] toastcfh:
Well so far I've been working on the libhw part of wimax. I've pretty much got all or enough native stuff in. Move to the java end of it now. Basically just reversing some of the api that we need. Started out with device control server and connecting to it. That's basically where im at.

When u do wimax a few things gotta happen. I've got them pretty much setup to happen. Then u reach the limit of sequansd automagic.

Basically goes as follows.

Start the driver

Prep the iface (chown the directory, put wimax0 up and do some socket configuring)

Start sequansd

It'll start and wait for some things from the api. Which is what I'm on now.

Next

The api connects to device control server

Once if connected sequansd should at be loading the config files. Getting some basic properties from the nand. It will also do this an do it successfuly with what I've got reversed so far. The catch is dc server needs to be doing its thing.

Once it pulls the props its going to need some properties from java and jni. Or else it'll fail there and refuse to move forward.

If it were to move forward it would need to be put into scan state.

Once in scan state it begins looking for wimax.

Once it gets it it does a dhcp request.

If u get an ip if all good :)

These are just the basics of what needs to happen. HTC of course add extra stuff for all sorts of things that are in needed.

Since were using sequansd we have to do things the way it asks or needs them done. This isn't like wpa_sup for WiFi where we have the source for the userspace daemon. Reversing sequansd is way to much work also. The way I see it is that sequansd is fine for using this way. And sqn the supporting userspace for sequansd doesn't rely on external classes that only HTC uses for wimax.

But what I'm trying to do is interface with it the way HTC does, as sequansd was made to be interfaced with the way HTC is doing it. It's basically the only way were gonna do it unless someone reverse engineers everything including sequansd. I've been dumping quite a bit of time into getting even this far. I'm not sure still how things will go down at each step either till I get there. The hope is once I connect to device control server that squads will have more automagic love. Of course there are other previsioning steps needed even after connecting to dcs . But I take things one step at a time and start from scratch often just to clear my desktop and head ;p anyhow I just want the thing to work ;x
[EVO 4G Android Development] bedoig:
Thanks toast!
[EVO 4G Android Development] strung:
Nice work, sir!
[EVO 4G Android Development] sarahlegs:
Toastcfh, you rock and we are trying to send coding help your way somehow in addition to these funds. We love you! <3
[EVO 4G Android Development] AssassinsLament:
Can you repeat that in BSB terms please?
[EVO 4G Android Development] phelony:
So does this mean its going to be fixed?

I may pee on myself a little! I am getting my Evo tomorrow and knowing that CM is on its way with 4g would make life a lot less lame!
[EVO 4G Android Development] kpoz:
We're not worthy! We're not worthy!
[EVO 4G Android Development] madunix:
i predict half of the ppl won't hold up on their bounty.
[EVO 4G Android Development] toastcfh:
If not I'm fine with that. I'm not doing it for the cash. I just wanna see it working and I've said that from day one. Anyone who knows me knows that.

My name is toastcfh and I'm an androidoholic. ;x
[EVO 4G Android Development] iomthd:
Thanks for an amazing update on your progress! I hope things go well with the java side of things!
[EVO 4G Android Development] p-slim:
Yeah toast thanks for the update, it definitely gives us hope. We didn't know anybody was actually working on it, we thought we had to wait till 6.1 final. Don't worry about that other poster, though you don't do it for $, most people like myself will probably contribute more then what they put down when its actually working. No homo, but I love you man.
[EVO 4G Android Development] Stephanie95:
time to put it to sleep?

Nice job so far, I tried this Rom when it first came out- because it was one of the first froyo roms...

But... most of the other roms have everything working with custom looks...

Gingerbread will be fully working before 4g works here?

lol;-)

Just my 2$

:rolleyes:
[EVO 4G Android Development] derekwilkinson:
i will hold up to it. :)
[EVO 4G Android Development] jrdulog:
That's what I'm saying. I used to love CM on my G1, but I'm still boggled to see this problem still on-going. Not trying to be a douche on here, but just been wondering why people who are so concerned with 4G haven't hopped on a different rom (AVA's are phenomenal).
[EVO 4G Android Development] p-slim:
Because cm6 is taking a massive dump on every other rom out there, none even come close to the performance and.customizable options. Its not even fair to compare Regular rom to cm.
[EVO 4G Android Development] mrmylanman:
I have moved on to MIUI, however since they are both AOSP I am told any benefits from CM can be ported to MIUI, so I'm still hoping they get 4G working :-)
[EVO 4G Android Development] sarahlegs:
As will I!
[EVO 4G Android Development] toastcfh:
well really the goal i have in mind is just finding a open way to do wimax in android. in the end it will open doors for future projects i reckon. i mean really if a rom doesnt have wimax out the box from htc basicly it doesnt work. there is no alternative route. its either htc compiled for it or they didnt. so were stuck with only having htc rom/builds if we want wimax. this may be fine now. but if htc doesnt update the evo to 2.3 then we just wont have wimax on 2.3. same goes for all devices with wimax. so the next device sprint releases will be in the same boat. right now the chip we have to work with is sequans and that seems to be htc's choice of chip for the next few devices (that i know of) that will get wimax.

of course things would be 100x easier if htc gave us source. but they didnt, so were stuck reversing it if we want it. but what they did give us is a few daemons that start and run wimax and a shotgun implementation that happens to use those daemons. which eases the pain a little. all we need to do is interact with the daemon like it wants us to and we good.

im not going to tell anyone this will work tomorrow or even a month from now. i was just stating what ive found and my progress. of course anyone on this same journey is welcomed to contact me and maybe we can put two heads on it at once. :)
[EVO 4G Android Development] xlGmanlx:
The importance is 4G for all regardless of your preference of roms
[EVO 4G Android Development] donatom3:
Alot of us are just watching this thread to see progress and to find out when and who to send the money too.
[EVO 4G Android Development] p-slim:
If I was a coder I would definitely help, where are all those people who are creating these rooting process'. Maybe its because most of them don't have 4G in there area.

It sounds like if toastcfh had a little help they might be able to accomplish this.
[EVO 4G Android Development] toastcfh:
Ironically I don't have 4G in my area either >_< and that's part of a testing issue. I spent the better part of a week just trying to make changes, get logs and have others test ideas of possible quick fixes. Made things hectic working with other peoples schedules and finding able willing participants. Lots of thanks to those who took out hours to help me doing so.
[EVO 4G Android Development] mitchellvii:
People, they are never gonna figure out 4g. I mean come on, they've had the code for months now. Just accept that AOSP roms will NEVER have 4g.

And oh yeah, I promise that 80% of the people who pledged here would never have ponied anyway.

These guys know they will be heroes forever if they get this. They haven't because they can't. Nothing against them, it is just undoable without the proprietary code.
[EVO 4G Android Development] sarahlegs:
So OK, I'll take this trollbait for a second, because toast and hard-working open source coders everywhere deserve to have couth-challenged individuals like this permakicked.

I would ask you to explain how you understand wimax software implementation so well that you can unilaterally decide that someone you have not met cannot decipher it, but I know you don't. So I won't. Know how I know that? Because you make posts like this:

Further, there are three primary reasons your toxic post logic fails: First, toast does not expect money. Second, whether you think some other people on the internet will do something they said they would or not would be completely irrelevant to our lives if I had the power to ban you, but I don't. Third, whether toast and anyone who steps up to code for the benefit of others actually find the Wimax promised land or not, it it still worth the journey to some of us, for the joy of it.

Posts like this make me want to go back to the days of SysOps and seclevels in moderated BBS'es. Hell, I'd ban this guy for being offtopic and take the ban myself for calling him out offtopic, but sadly, I don't see that happening.

As it stands: toast, we love and support you and cyanogen, and please please please ignore these persistent trolls even though some of us can't.

Love,

Us
[EVO 4G Android Development] -shift-:
*FACEPALM*

i will reiterate what i said to you earlier when you made this ridiculous statement:

you have no idea what you're talking about.

you have not shown that you know how to code, nor have you shown ample knowledge on what goes into reverse engineering software. so, please, before making these silly blanket claims, think twice. i personally know toast is working crazy hard at this. he's making a lot of progress in conquering it. he needs help and, those who are knowledgeable, are stepping up to provide it. so, kindly keep your uninformed claims to yourself.

also, it's wimax, not 4g. if you did have knowledge of the particulars of this issue, you'd know 4g is just a marketing term and wimax is the more appropriate term.

ps:

be glad i didn't use rosier language. it's posts like yours that piss off the hardworking developers that the evo community is known for in the android community.

pps:

i couldn't resist. you're an idiot.
[EVO 4G Android Development] toastcfh:
Tbh ur post contributes nothing and and is considered trolling.

On another note... what code have we had for months? The kernel source? That is only on piece of the puzzle.

Also I would like to state it CAN be done. Its only compiled code and that can be reversed. Most of the Java code was simply reversed at that. Its only a matter of implementation of what's been reversed. There are over 400+ classes that need to be gone through, cleaned up, and added to aosp. That's not even touching the HTC API. Its just a lot of work and HTC paid a team of people to do it with source. This isn't the case for us. What we have is a couple people who do this in their free time as a hobby reversing, testing and implementing the changes. So of course what took HTC prolly a year to do with data sheets and code is going to take a couple hackers as while to reverse.
[EVO 4G Android Development] sarahlegs:
we love you toast. That is all.
[EVO 4G Android Development] xlGmanlx:
I agree, no one said it was going to be a rose garden. If we were dealing with a full deck, there are plenty of folks that could get this running
[EVO 4G Android Development] Shauli20:
I believe people like this guy only write what they write to get the rest of us worked up. Of course he has no clue what he is talking about, and he knows it. I'm always debating whether to simply ignore these idiotic comments, or to fire back to show our support.

Piss off...

Sent from my EVO rockin' MikFroYo!
[EVO 4G Android Development] Karadorde:
You know we would all be willing to test if you needed more people. I have wimax in my area but rarely use it because I run CM. Always willing to try out things for testing. Feel free to throw anything my way and I will do my best to get you the information that you need.

Also, kpoz, put me down for $20.00.

Sent from me to you via the interwebs.
[EVO 4G Android Development] kpoz:
Dear madunix and mitchellvii,

Please learn how to read.

Love,

kpoz