yashsingh1/xdaforums huggingface dataset:
[HTC Amaze 4G] texasice:
The below can only be validated once we get the 3.0 kernel source. Without kernel source we basically cant do anything for aosp ics since it has pmem issues. that should be easy to fix.

It trying to get wifi working on ruby i switched over to the stock 3.0 kernel so i could use its modules and start trying to get some networking stuff going.

I did some research on its wifi chip. The firmware files tell me its a TI wl127x (dont know if the last number is a 1 or 3)

Then reading the kmesg we see:

<4>[ 3.967895] fm_drv: module is from the staging directory, the quality is unknown, you have been warned.
<6>[ 3.982757] Compat-wireless backport release:
<6>[ 3.982879] Backport based on wl12xx.git v3.1-rc6-14229-g8635dd0

This is actually just the fm module

google reveals a random kmesg and after some reading turns out to be the tegra one x (endeavoru)

What? the endeavoru and ruby have the same wifi chip?

No but close the endeavoru has a wl128x.

But we can use the same wpa_supplicant and finally get wifi turning on (still not totaly functional).

Endeavoru source:https://github.com/TeamNDVRu/android_hardware_ti_wlan

remirrored here for us: https://github.com/Evervolv/android_hardware_ti_wlan/tree/ics

But what about the driver? The endeavoru has kernel source maybe we can use theirs? (when we get our 3.0 kernel source)

Source says no (i may be wrong here)

https://github.com/TeamNDVRu/htc-ke...b/master/drivers/net/wireless/wl12xx/Makefile

#We will build wl12xx.ko and wl12xx_sdio.ko at vendor/ti/wlan/

so it only builds wl12xx_spi.ko a module our stock kernel doesnt have so thats no use. And i dont know where to find the vendor repo.

then i find:

http://linuxwireless.org/en/users/Drivers/wl12xx

which links to the source:

http://git.kernel.org/?p=linux/kernel/git/luca/wl12xx.git;a=summary

but this is the entire kernel. what we want:

http://git.kernel.org/?p=linux/kernel/git/luca/wl12xx.git;a=tree;f=drivers/net/wireless/ti/wl12xx

But this only builds wl12xx.ko so we still need wl12xx_sdio.ko and most of these:

bluetooth.ko cfg80211.ko hid-magicmouse.ko mac80211.ko wl12xx_sdio.ko
bnep.ko compat.ko hidp.ko rfcomm.ko
btwilink.ko fm_drv.ko kineto_gan.ko wl12xx.ko

kineto_gan.ko seems not needed since it is actually from 35 kernel and doesnt even load. lol

<3>[ 7.698760] kineto_gan: version magic '2.6.35.13-g222a32a SMP preempt mod_unload ARMv7 ' should be '3.0.16-ga4fb83c SMP preempt mod_unload ARMv7 '

TLDR

So what does this mean?

I guess the question is does the endeavoru (one x tegra) have the source for their wifi driver? If not we need to join with them and get the sources released since (i am only assuming) they are the same.

we'll get the kernel source eventually but until then no builds can be released because the pmem errors render the device almost unusable.
[HTC Amaze 4G] hasoon2000:
I just tweeted this to faux. Hopefully he gets a look at it. I have no clue how that stuff works but it does sound logical to me lol. We need a dev project or something going on. That is the only way we can get this done. Since HTC is being a b*tch and crying like a little girl, we'll just have to snatch the lollipop and make it worse on them. Thank you sir for looking into this!
[HTC Amaze 4G] fcpelayo:
Wow finally some light :rolleyes:
[HTC Amaze 4G] Kaiouss:
Has anyone tried asking HTC if they have or could release anything for interfacing with the wifi driver that is not the source of the driver itself? Maybe I'm off-base here, but if the compiled driver could be packaged with a wrapper (bad ndiswrapper flashbacks), seems like that would at least increase what's capable or make things easier. It also gives HTC the option to reduce the inflow of support inquiries related to this problem without revealing whatever proprietary information they're trying to protect. Honestly, the Amaze probably doesn't have enough traction to make them dig their heels in to get and release the wifi driver source or the kernel source.

Also, anyone gotten a response from HTC indicating why any of this stuff can't be released? If we can find out what the hold-up is, might be able to use carrots/sticks better. I noticed a lot of the HTC replies were "I don't know why blah blah" just reply and reiterate that the question was why it can't be released, not whether they know why. What isn't known can be discovered.

EDIT: I also noticed online that a lot of people have passed on the Amaze and possibly HTC altogether because CM (7 or 9) isn't available for the Amaze. Perhaps it might be worth it to send a compilation of these links to HTC so they can see that there's real loss involved. If we take even the 5 or so people I've come across, not sure how much HTC makes per phone, but seems worth it to at least bug TI. One employee spending a few hours trying to work with TI to get the code released would almost unquestionably be worth it to HTC's bottom-line; however small the impact may be.
[HTC Amaze 4G] EclipzeRemix:
bit.ly/MDBApF :)
[HTC Amaze 4G] bedwa:
I know that its the ti wlan1271/1273 chip and I found this

http://processors.wiki.ti.com/index...uetooth_for_ARM_Processors_Open_Source_Driver

I haven't had a chance to peruse as of yet, but it's for the same chip, used with some of TI's open source platforms. We could try to port from one to the other, but that would be a pain. However, we could use this as leverage to get HTC to release their "changes" to the existing code. This would be extremely helpful. If anyone can beat me to looking at it, great, but I think we may be on to something here. TI is HUGE on open source, so that is a good avenue of attack as well.

Btw: I got the 90-120 response as well.

Edit: another important link.

http://processors.wiki.ti.com/index.php/TI-Android-ICS-4.0.3-DevKit-3.0.1_ReleaseNotes

We have the firepower thanks to TI, we just need to use it.
[HTC Amaze 4G] hasoon2000:
It's "proprietary" so they can't (they don't want to release it actually). People are actually not buying HTC phones because how they treated us. They don't help us, we say F*ck you to them. It's nothing personal, just business ;) lol

I know! I saw it in the morning but I finally got on the computer now. Gonna update the OP!

You, my friend, is going to make lives easier! Great to see the article brought you here!! Hopefully you can help us out and we can get the show on the road!
[HTC Amaze 4G] texasice:
Ok some more info i learned.

So it seems a fair portion of the wl127x chip drivers are open source. fm, bluetooth and uim (shared user trasport) and most of the utilities needed to get wifi working (iw, calibrator, wpa_supplicant) and the generic wl12xx wifi driver.

which can all be found in the rowboat repo: http://gitorious.org/rowboat

what isnt open source is the most vital part the sdio driver which configures the gpios and such so we can actually communicate with the chip.

according to ti:

so although ti is doing their part for the opensource commutity there is likely little the y can (or will) do to push htc to release their proprietary sdio driver (but im a pessimist)
[HTC Amaze 4G] shekki:
We could always ask TI to communicate with HTC to release it. Who knows, it may end up working.
[HTC Amaze 4G] fcpelayo:
This what you are talking about is what I understood but wasn't sure. This is the root of HTCs evil. We need to let htc know, that we know what they are doing. This is plain out dirty, scandalous and that by doing this they are not working with the community.

IMO HTC thinks they are fooling us and that we don't know and they were right until now. We should be more direct not allowing them to go around the bush.
[HTC Amaze 4G] dinklebert4u:
Waste of TIME

Hello- I haven't posted in a while.

I think this is an ABSOLUTE waste of time.

First of all, did you think you were emailing tech support, and not corporate?

Well, you are. I have emailed HTC technical support many times before, and spoken with the incredibly sweet, and helpful, support staff in both Canada and Tennessee on the phone.( PS in North America, I was told by HTC tech support that they only have 2 call centers)

If you want your voice heard, you should probably find a way that is not SPAMING HTC tech support's inbox. If you would take the time to consider that people are actually emailing them with real issues with their devices, and know that they have to filter through all the spam to answer people's questions, you may re-consider SPAMING their inbox. Also, what makes you think that they are in charge of releasing this information? If you knew anything about marketing you may consider that they may not have the means to provide you with this information, and that you are barking up the wrong tree. How am I to know? I am just an end user, right?

I am sending this message, because I don't think it is right to spam people, especially since you are more than likely barking up the wrong tree.

Sincerely,

Dr. Dinklebert-
[HTC Amaze 4G] andy55:
You should've kept the streak going.

And its not spamming if there's a legitimate issue, which there is. Customers have every right to voice their opinions, concerns, etc towards a product or service the company has to offer, and if there are more people out there who care enough to open dialogue about a certain topic then it isn't spam. We want to get information about a product, something legitimate, and also providing feedback to a company that seems to not want to listen to its customer base, again, that isn't spam.

You should read this whole topic and understand what we're after here, and do yourself and all of us a favour, try to keep that post count down.
[HTC Amaze 4G] justin lamantia:
I'm no expert but just wanted to kno do we have pretty much half the ics kernel . Is that what you guys are saying ?
[HTC Amaze 4G] sedrader:
YES

This NEEDS to happen.

Sportsstar89 is doing a WONDERFUL job, and these codes will make developing so much easier. Plus it brings cm9 and miui to this beast of a device :cool:
[HTC Amaze 4G] andy55:
I came across some *.ko files and wanted someone who knows what they're looking at to see them, I doubt they're anything useful but I'd rather have someone who knows tell me they're useless. So devs, take a look, and if they're junk I'll delete the post
[HTC Amaze 4G] fcpelayo:
I think we should let faux know or maybe he already knows :rolleyes:
[HTC Amaze 4G] spiz516:
My approach is to go back to Samsung. I left them for lack of developer community support and lack of timely updates, only to find HTC has taken on this role. If I have to wait for updates, I may as well do it with a company that releases its sources to the developers.

I wish Asus would get into the business of making phones. :(
[HTC Amaze 4G] andy55:
they make one hell of a phone

http://event.asus.com/design_story/padfone/
[HTC Amaze 4G] saulcho009:
Even made it so it can converted into a tablet :) it does look close to an iPhone though. Sorry to be off topic but Asus looks like the next company to go :)
[HTC Amaze 4G] spiz516:
How have I missed this? I would go with this purely on the fact that Asus makes great hardware and is friendly to the concept of open source. Love this! Yep, let's all just jump to this... that should send the message to HTC. :cool:
[HTC Amaze 4G] hasoon2000:
Let's keep this on topic ladies!!

I just sent them a pissed off tweet.

https://twitter.com/PaliHustlaOD/status/217839426276032512

I miss Nokia :/
[HTC Amaze 4G] Biohazard0289:
Sent another tweet, and they finally responded to my e-mail. Standard cookie cutter reply.
[HTC Amaze 4G] andy55:
I wonder if all this has anything to do with the oneS being offered in select markets with the S3 (MSM8260 S3 vs MSM8260A S4) that our phones have. Originally the oneS was supposed to have the MAM8260A... who knows what else it will share with the amaze, so that may possibly be holding up the release of source.

http://reviews.cnet.com/8301-19736_...ing-offered-in-select-european-asian-markets/
[HTC Amaze 4G] Old-school:
There are quite a few One S kernel source codes for different regions on the htcdev website. Would it help at all if we could figure out which of those is for the ones with the S3?
[HTC Amaze 4G] CalicoJeb:
Sounds plausible to me
[HTC Amaze 4G] shekki:
I say it doesn't hurt to try. Maybe that'll give our device the needed kick to kick start development again.
[HTC Amaze 4G] daswahnsinn:
I thought I might be able to woo them with poetry, ROFL

http://twitter.com/daswahnsinn/status/219770206380244995

Also started on Google + (g+)

https://plus.google.com/u/0/105983594520322058171/posts/WEsw7t1QXaB
[HTC Amaze 4G] oryan_dunn:
I get a bad feeling that HTC will never release the source. My guess is, they contracted with Integrity Project to port the TI WL1283 drivers for them, and Integrity probably still owns the copyright.

http://www.integrity-project.com/wilink-drivers-and-solutions/

and they show HTC as one of their clients

http://www.integrity-project.com/category/clients/

Perhaps start directing some communications towards them?

They're on Twitter, but not active

https://twitter.com/integrity_prjct
[HTC Amaze 4G] fcpelayo:
I emailed integrity about 2 days ago and quickly responded with this.

"

Hi Floyd,

I'm not sure I understand why you are approaching Integrity or HTC/TI.

TI has open-source community which supply drivers+fw files.

Please see: http://processors.wiki.ti.com/index.php/OMAP_Wireless_Connectivity_ OpenSource_WLAN_related_components

Thank you and good luck! - Elad"
[HTC Amaze 4G] oryan_dunn:
Looks like you have a broken link:

http://processors.wiki.ti.com/index...nnectivity_OpenSource_WLAN_related_components
[HTC Amaze 4G] fcpelayo:
What does their response mean? So should we even bother?
[HTC Amaze 4G] Kaiouss:
Sounds like they're trying to say that the drivers are on that site.
[HTC Amaze 4G] broker32:
This makes sense, TI does hold the rights for the wifi drivers, what if we focus on asking TI for the wifi drivers while still bugging HTC about releasing the ics source already?
[HTC Amaze 4G] fcpelayo:
I thought so.

I agree. Anybody else want to give it a shot to TI ?
[HTC Amaze 4G] oryan_dunn:
What's interesting is that the Integrity site seems to imply they modify the drivers for different platforms. I assumed the open-source drivers were for a different platform, and that they modified them. Perhaps I was reading it wrong and they're open-source linux drivers that they modify for the windows platform. At any rate, I didn't seem to see any download links on that site, and I wonder if HTC used all the components on that site, or just a subset?
[HTC Amaze 4G] Kaiouss:
It links to the e2e site, but I didn't see any drivers or driver source code anywhere, though that might just be the fact that I'm using my phone. What file extension do we expect for the driver source? .so maybe? If anyone knows, will see what I can find. Also if there would be any string in this particular driver for the amaze, that would help.
[HTC Amaze 4G] oryan_dunn:
Linux driver source usually is a zip, bz2, tgz, etc. It'll be a compressed archive with the source tree for that driver. .so files are shared object libraries, similar to a dll on windows. .ko are kernel object files, a compiled driver for a specific kernel version.

They give a couple git links for the firmware and TI utils, but under the "mac80211: We are using a compat-wireless version created from TI internal wlan releases", so I dunno where you'd go about getting that. Perhaps it's already part of the kernel source, but I'd find that hard to believe that it'd have gone overlooked by the xda community for so long.
[HTC Amaze 4G] Kaiouss:
Yah was just going to do a filetype:tar.* site:e2e.to.com <string> but guessing as you mentioned, xda has known about that site. Will still look later, though. You never know. Thanks for info.
[HTC Amaze 4G] fcpelayo:
Hard to believe but possible. We need somebody with more knowledge that can help guide us in the right direction
[HTC Amaze 4G] shekki:
If HTC doesn't release the source code within their 90-120 day window them I'm going to raise all sorts of hell. Those are the terms of GPL and they have to abide to them. Mark your calendars for Sept 21 since that's 4 months from when they released the ICS OTA update.
[HTC Amaze 4G] broker32:
Is this it? http://processors.wiki.ti.com/index.php/Android_wireless_build_and_porting_guide
[HTC Amaze 4G] brainbone:
From what I can see, the TI WL1283 drivers are not GPL.

Needless to say, the HTC "Amaze" is the last HTC phone I'll purchase. I've not been "Amazed".
[HTC Amaze 4G] oryan_dunn:
Interesting, nice find. I wonder how different it is for the WL1283, which is the chip I think the Amaze has. When I get some time tonight, I'll give that a read.
[HTC Amaze 4G] oryan_dunn:
I found this:

http://www.omappedia.org/wiki/Porting_MCP_WLAN_to_Android

Man, I really wish I didn't need my phone and could use it to test this stuff out.
[HTC Amaze 4G] Old-school:
The blackberry playbook uses the wl1283, shouldn't we be able to use those drivers?

I read somewhere that the main issue was getting the WiFi chip to play nice with the Snapdragon processor. Can anyone confirm if this is why we cannot use the drivers from the playbook?
[HTC Amaze 4G] rbaruch:
This kind of brain storming is how progress begins :-)
[HTC Amaze 4G] Jaa-Yoo:
I havent been keeping up with this thread and forgive me for asking, but are devs waiting for a 3.0 kernel source or only wifi drivers?
[HTC Amaze 4G] saulcho009:
Both would help greatly so we are waiting for both. Wifi will help us with GB roms (CM7) since we have the source code for GB. Nothing much can be done with ICS until HTC drops the ICS Source (3.0 Kernel).

I just read the brainstorm and I couldn't help but smile. Hopefully this will get us somewhere :)
[HTC Amaze 4G] Jaa-Yoo:
I was just over on htcdev.com to check something out and decided to see if they had anything for the amaze. Theres a 3.0 kernel source code download available for the Telus version.

http://htcdev.com/devcenter/downloads

select Amaze on the list

select Kernel code just below that

click find files

Is this useful?
[HTC Amaze 4G] hasoon2000:
Oh wow. You've got to be kidding me lol. I'm downloading it just in case HTC removes it (because they are dipsh*ts like that)

I also wonder if my little movement worked or anything. I guess I'll never know.
[HTC Amaze 4G] oryan_dunn:
Wow, they must have just released that. I was over on htcdev just the other day, and only saw the Telus & T-Mobile GB kernel. I wonder what the difference is between the two. I may just have to download both GB kernels and do a tree diff.
[HTC Amaze 4G] ndp_singe:
It is for Telus but is it useful for Tmobile too?
[HTC Amaze 4G] oryan_dunn:
That's why I want to diff the GB kernels, to see what they changed between the two carriers. I'd image that 99% would be the same, perhaps some tweaks for the air interface on the cell radio or something.

Also, after thinking about it some, I think the SDIO module isn't really for IO lines. SDIO is an extension of the SD card interface for accessories https://www.sdcard.org/developers/overview/sdio/

And I think the SDIO module is just the hardware interface. I'm not sure what would need to be specifically configured for our model. Perhaps the kernel sees the WL12xx the same as it would if it were an external card in an SD slot.
[HTC Amaze 4G] fcpelayo:
This doesn't make sense how the sdio is the sd card but it's also related to our WiFi? Anyways I'm no guru but let us know what you find in differences and if telus kernel may be useful for T-Mobile.

I think hasoon has a point though. It seems that now that were actually finding out integrity, ti, and HTC are all in this, bugging all of them is starting to release what we want. I don't think integrity and ti image reputation wants to be damaged along with HTCs.
[HTC Amaze 4G] brainbone:
SDIO WLAN:

The term SDIO WLAN refers to the SD-Card interface extension called SDIO in the functionality variant WLAN (wireless LAN). This techonlogy can be used to bring wireless networking to existing TI processors running Linux or Windows CE (WCE) or Windows Mobile (WM) in a relatively straight forward plug-and-play way.

The seemingly defined functionalities for SDIO are:

mass storage (most often in form of a solid state device, anyways the classical device type)

WLAN (aka WiFi or IEEE-802.11b/g)

GPS

BlueTooth

TV-Receiver/Camera/Scanner

Sound Card

Fingerprint Sensor
[HTC Amaze 4G] oryan_dunn:
Yeah, I think it was developed back when PDAs had SD card slots, but didn't have on-board anything. They made cameras, WiFi, etc. that you could put in an SD card slot to give the PDA that fuctionality. I'd guess that HTC just wired the TI chip to an SDIO port on the proc.

I'm not sure which thread to post in with all the new ICS kernel threads popping up.

In other news, I was looking through the ICS kernel for Telus, and saw this, which seems very promising:

arch/arm/configs/ruby_defconfig

# HTC_WIFI_START
# CONFIG TI NLCP WIFI
CONFIG_WL12XX_MENU=y
CONFIG_WL12XX=m
# CONFIG_WL1251 is not set
CONFIG_WL1271=m
# CONFIG_WL1271_SPI is not set
CONFIG_WL1271_SDIO=m
CONFIG_WL12XX_PLATFORM_DATA=y
CONFIG_TIWLAN_POWER_CONTROL_FUNC=y
# HTC_WIFI_END

I'd hope that a build of the kernel with this config would create the WiFi drivers. Unfortunately, my linux box is down and I don't have a kernel build envirionment handy to test. I have a funny feeling the WiFi source had been there all along, it just need to be built.

I also diffed the GB Telus and T-Mobile source. There weren't many differences, but more than I thought there'd be. Most seemed to be in the USB and Video trees. Does the Telus Amaze have some sort of extra USB/Ethernet passthrough or something? It seems that's what most of the USB driver changes are related to.

What's interesting, in the tar file for the GB kernels, the root folder has the carrier name as part of the name; however, the ICS root folder doesn't have the carrier name.
[HTC Amaze 4G] brainbone:
I like to use vmware player or VirtualBox for these situations -- though it can take some time to get your build environment configured.

Surprised that I can't seem to find any android kernel development virtual appliances. A pre-built, virtual, android kernel development environment would likely give the development community a boost.
[HTC Amaze 4G] Kaiouss:
Darn being a n00b. If someone could make a separate thread for this, I would be grateful. Anyone have a virtual env they can send out as a vmdk for loading into VirtualBox portable? This is a great idea imho. May also help to get more people involved and/or familiar with bug-testing and/or dev. And/or.
[HTC Amaze 4G] oryan_dunn:
After looking at that, and the drivers/net/wireless/wl12xx/Makefile

wl12xx-objs = main.o cmd.o io.o event.o tx.o rx.o ps.o acx.o \
boot.o init.o debugfs.o scan.o

#wl12xx_spi-objs = spi.o
#wl12xx_sdio-objs = sdio.o
#wl12xx_sdio_test-objs = sdio_test.o

#wl12xx-$(CONFIG_NL80211_TESTMODE) += testmode.o
#obj-$(CONFIG_WL12XX) += wl12xx.o
#obj-$(CONFIG_WL12XX_SPI) += wl12xx_spi.o
#obj-$(CONFIG_WL12XX_SDIO) += wl12xx_sdio.o

#obj-$(CONFIG_WL12XX_SDIO_TEST) += wl12xx_sdio_test.o

# small builtin driver bit
# HTC_WIFI_START
obj-$(CONFIG_WL12XX_PLATFORM_DATA) += wl12xx_platform_data.o
# HTC_WIFI_END

I don't see how any of those modules would be built. It looks like HTC commented all of that out. But on my phone running ICS, there certainly are wl12xx and wl12xx_sdio modules. I guess I'm just not following HTC's modifications here. It doesn't seem to add up to building the same kernel we've got on our phones.

Edit: for comparison, here is the default 3.0.16 makefile http://lxr.linux.no/#linux+v3.0.16/drivers/net/wireless/wl12xx/Makefile

Uncommenting those lines should build those modules. I guess I'm just puzzled by this.
[HTC Amaze 4G] fcpelayo:
What do you mean htc commented and we need to uncomment?
[HTC Amaze 4G] oryan_dunn:
The Makefile for the wl12xx drivers I posted above, HTC commented out the lines that actually build the wifi driver. You'd need to uncomment those lines, rebuild the kernel to get a wl12xx driver.