http://rootzwiki.com/_/articles/general/android-kernel-source-released-for-the-touchpad-r384
great news (about time too), looking forward to the improvements this may bring
Thanks for the news!
Great news lets hope they give the cm team the wifi source code then we should have a really good build seems funny that hp was developing and android port to be released on the hp then pulled out at the last min
So what exactly does this mean for CM9 development? Will it increase the quality of the HW acceleration drivers, or Wi-Fi, or something else?
Good news definitely.
Sent from my ADR6425LVW
ambrar12 said:
So what exactly does this mean for CM9 development? Will it increase the quality of the HW acceleration drivers, or Wi-Fi, or something else?
Click to expand...
Click to collapse
HW - no
WIFI - no
Self-Powered USB host - no
Something else? Maybe.
Twitter: @dalingrin: It will help with things like serial console and Bluetooth. Most other areas it *might* will be minor.
@dalingrin: Kernel source from HP would have been more helpful earlier in development. Don't expect huge gains from this source.
Sent from my GT-P7510 using xda premium
Won't having the proper kernel help with getting the camera working?
BuddyJoe83 said:
Twitter: @dalingrin: It will help with things like serial console and Bluetooth. Most other areas it *might* will be minor.
@dalingrin: Kernel source from HP would have been more helpful earlier in development. Don't expect huge gains from this source.
Sent from my GT-P7510 using xda premium
Click to expand...
Click to collapse
lol you quoted his tweets in the wrong order.
Varemenos said:
lol you quoted his tweets in the wrong order.
Click to expand...
Click to collapse
ye lol.
Doesn't really mather though .. 2 seperate tweets with different content, related though.
Unrealwolf said:
HW - no
WIFI - no
Self-Powered USB host - no
Something else? Maybe.
Click to expand...
Click to collapse
Wifi is controlled via a kernel module. How would source not help? I don't really have issues with my TP's wifi functionality, but the source that was linked does appear to include ar6003-specific logic.
--Matt
Edit: Oh, hmm, I see. It includes a Kconfig file for it but no source. Lame.
mkosem said:
Wifi is controlled via a kernel module. How would source not help? I don't really have issues with my TP's wifi functionality, but the source that was linked does appear to include ar6003-specific logic.
--Matt
Edit: Oh, hmm, I see. It includes a Kconfig file for it but no source. Lame.
Click to expand...
Click to collapse
Some people over on Rootzwiki contacted HP about the WiFi but HP claims to know nothing about it and to have nothing else to release. Of course, they also claimed to know NOTHING about Android for the Touchpad so...
Related
Here's an idea, maybe something else can contribute or confirm it might works..
the Nook honeycomb image is actually running on top of a 2.6.29-omap kernel, which indicate that only some parts might require 2.6.36.3 functions.
I know that the main problem for me porting it, was the libc.so which uses kernel calls not found in our existing 2.6.32.9 kernel. so it crashed due to some cache functions not implemented.
- could the missing cache functions be implemented into our 2.6.32 kernel?
- can the Nook edition with a working libc.so (hopefully without FPU function compiled) be used to replace our xoom image libc.so which crashes?
So to make an early edition can we merge the ARMv5 libs (i assume it is from the emu) and use this with xoom edition and then keep our libnv* environment which is compatible without our nvrm_daemon (which no one can fix, although a proper kernel work for booting 2.6.36.3)
ideas.. but if its possible to put into "real life" is another story.
and how many can do experiments?
Artem wrote he is on the 2.6.36.3 kernel, but since we might have an option to go around, maybe also worth considering, if display driver lacks nvrm_daemon support.
re
I'm not a developer but I can do some beta tests for you if you want.
julio77 said:
I'm not a developer but I can do some beta tests for you if you want.
Click to expand...
Click to collapse
obviously...same here...;-)
I am able to write basic scripts, xml etc.. and have a brain...
Jp
i tries all this out now.. and got passed some link references between libs but the "libc.so" issue came coming back..
so it did not work..
im closing the idea here :-( not worth spending time on, so only the solution with updating kernel and rewriting drivers must be the way forward.
May be I should wait for ubuntu 11.04 or some other linux OS for folio 100
Toshiba &Google is not so kindness. Are they only want to earn more money, right?
Dexter_nlb said:
i tries all this out now.. and got passed some link references between libs but the "libc.so" issue came coming back..
so it did not work..
im closing the idea here :-( not worth spending time on, so only the solution with updating kernel and rewriting drivers must be the way forward.
Click to expand...
Click to collapse
Yup, I also think that waiting for updated kernel + drivers from the new Toshiba folio 200 is a more feasible approach...
xitrumch said:
Yup, I also think that waiting for updated kernel + drivers from the new Toshiba folio 200 is a more feasible approach...
Click to expand...
Click to collapse
If, and its a big if, the 200 has the same hardware.
ma1999 said:
If, and its a big if, the 200 has the same hardware.
Click to expand...
Click to collapse
correct,
we already know it has different resolution . and probably better display now, and no hardware buttons on the side, so no I2C used for this..
i think its very different, as it probably also got 802.11n wifi now, which we dont have and need different ar6000 driver.
i think its a long road downhill for folio100 if the 200 edition should be anything close as source for porting.
Dexter_nlb said:
correct,
we already know it has different resolution . and probably better display now, and no hardware buttons on the side, so no I2C used for this..
i think its very different, as it probably also got 802.11n wifi now, which we dont have and need different ar6000 driver.
i think its a long road downhill for folio100 if the 200 edition should be anything close as source for porting.
Click to expand...
Click to collapse
Please, I'm no expert in this, so bare with me for asking questions.
Honeycomb uses a different kernel than Froyo ok.
For Froyo we have the source for all (hardware) drivers ?
Can the "android" part of Honeycomb (from for example Xoom) be put on
a kernel with required hardware drivers or are there stuff in the "android"
stuff that is hardware dependant ?
Is it hard to port drivers between kernel versions ?
Just trying to understand the many tasks need to get Honeycomb on Folio.
/Martin
The problem in this case is there is no honeycomb kernel sources out there.
Sent from my GT-I9000 using XDA App
Cpasjuste said:
The problem in this case is there is no honeycomb kernel sources out there.
Click to expand...
Click to collapse
xoom kernel source is available, koush used it to make his clockworkmod work , and it works fine, and its also used for oc'ing.
but its pretty much the tegra2 source we can get from nvidia. but alot of porting to do.
So, What we are still missing is?
ibila said:
So, What we are still missing is?
Click to expand...
Click to collapse
all of it!
Lol, guess all we can do now is wait for some ice-cream or get us a native honeycomb tablet.
Sent from my HTC Desire using XDA App
Hey, Asus just released his kernel honeycomb version:
http://www.asus.com/product.aspx?P_ID=gHh4q7I8dvWJzhdV
Choose Download and then Android.
I have started porting the kernel:
https://github.com/DerArtem/android-tegra-2.6.36-honeycomb-folio-nvidia
great news
i dont know how to compile or port stuff but i can say that i love my folio and i love all the devs that are working hard to port honeycomb on our device! THANK YOU SO MUCH!!!
DerArtem said:
I have started porting the kernel:
https://github.com/DerArtem/android-tegra-2.6.36-honeycomb-folio-nvidia
Click to expand...
Click to collapse
really great news!!!
thank you!!!
Thanks a lot!
Thank you a lot !!!
I hope you do 3G Modem Support to !
Just thought some might be interested in this (so sue me, i had to ask it):
http://nookdeveloper.zendesk.com/en...-updated-1-2-source-code?page=1#post_20056491
We will be publishing the updated source in the coming weeks. Thanks for your patience.
Click to expand...
Click to collapse
It will be interesting to see what their new source brings, and what we can use from it. Here is hoping that it is sooner rather than later...
EDIT: Well, i am happy to say it didn't take long.. have at it here: http://images.barnesandnoble.com/PResources/download/Nook/source-code/nookcolor-source-code.zip
Awesome news! The faster we can get dalingrin the updated kernel source the better!
Does complying with the gpl allow for a reasonable delay? Because once you get into grey areas like that, what's reasonable? 2 weeks? 3 months?
Obviously they have the source already, so I don't understand when companies release it some time afterwards.
Aye. I hate the "weeks" portion.. given that its out, i dont think its unfair to demand it now. As it is though, i think the GPL gives 60 days (??) for them to publish the code though, so it may be a while.
Not sure if I don't understand the complexities or everything all the devs here do, but what are the possibilities of the deeper-blue Honeycomb ROM being updated to use a modified version of the 2.2 Nook Color kernel instead of the current 2.1 Nook Color kernel? I assume this would help in getting some items like Flash video etc working properly in the Honeycomb ROM.
Or is the goal still to wait for whenever the 3.0 honeycomb full source is released? Just thinking out loud. Interested to see what others have to say.
ArmitageID said:
Not sure if I don't understand the complexities or everything all the devs here do, but what are the possibilities of the deeper-blue Honeycomb ROM being updated to use a modified version of the 2.2 Nook Color kernel instead of the current 2.1 Nook Color kernel? I assume this would help in getting some items like Flash video etc working properly in the Honeycomb ROM.
Or is the goal still to wait for whenever the 3.0 honeycomb full source is released? Just thinking out loud. Interested to see what others have to say.
Click to expand...
Click to collapse
There isn't much an updated kernel will do to help the Honeycomb SDK.
I don't see any schedules mentioned in the GPL http://www.gnu.org/licenses/gpl.html.
bigbob23 said:
I don't see any schedules mentioned in the GPL http://www.gnu.org/licenses/gpl.html.
Click to expand...
Click to collapse
They will do whatever they want until someone sues. What if we lost?
bigbob23 said:
I don't see any schedules mentioned in the GPL http://www.gnu.org/licenses/gpl.html.
Click to expand...
Click to collapse
I may have been wrong (and will happily say its not the first time); but i did do some reading and found this: http://gplv3.fsf.org/wiki/index.php/User:ashawley/Making_copyleft_work_with_implied_compliance
Not sure if it is totally relevant though..
Source Code
I got this:
Dear Brandon Bennett,
Thank you for your inquiry.
Barnes and Noble will post the updated source code in the near future.
There is still no specific date yet. The link will be posted under terms
of service on the website.
Please accept our sincere apologies for any inconvenience this may have
caused and we look forward to hearing from you.
Sincerely,
Ella
Customer Service Representative - Digital Support
Barnes & Noble
http://www.bn.com/
Visit our NOOK Support site for the latest updates and downloads at:
http://www.barnesandnoble.com/nook/support/
Click to expand...
Click to collapse
Hopefully the source will help dalingrin, verygreen and fattire cut through the current mysteries with the .32 development kernel for CM7.
Seems like a lot of progress was made without B&N's help (smart developers), but even if only a few optimized drivers can be poached that is better than nothing.
nemith said:
I got this:
Click to expand...
Click to collapse
Thanks for the info. The nook dev board had another update:
Well, if history is a guide, we released source of 1.0 about 2-3 weeks after launch...
Click to expand...
Click to collapse
As i replied, the anxious part of me does not understand any delay really, other than trying to keep the source code away from us "hackers" for as long as possible. The code is obviously in use, so why not release it?
Ah well..
There are probably lawyers hemming and hawing over them releasing it. They probably are trying to ensure that they haven't violated some other patent/copyright in their code which they actually might get sued over.
chadamir said:
There are probably lawyers hemming and hawing over them releasing it. They probably are trying to ensure that they haven't violated some other patent/copyright in their code which they actually might get sued over.
Click to expand...
Click to collapse
Perhaps, but the code is already shipping - its not to say an update can't get pushed out, but just because we can't see the source, doesn't mean current violations are excused.
As it is, the linux kernel is GPL; they can't not release it. So again, i am still frustrated at the hold up...
Probably just the usual corporate speed. They don't like to publish anything before they have to, if only for liability and exposure. Probably the last thing on the rollout list, too.
poofyhairguy said:
Hopefully the source will help dalingrin, verygreen and fattire cut through the current mysteries with the .32 development kernel for CM7.
Seems like a lot of progress was made without B&N's help (smart developers), but even if only a few optimized drivers can be poached that is better than nothing.
Click to expand...
Click to collapse
We are actually very close to having a good .32 kernel already. Some of us have been using .32 full time I think. Verygreen did most of the work on the port. He scrapped my .32 work and started over.
We only need a few updated drivers from them and we'll be good. So I expect a prompt release once we have B&N source.
dalingrin said:
We are actually very close to having a good .32 kernel already. Some of us have been using .32 full time I think. Verygreen did most of the work on the port. He scrapped my .32 work and started over.
We only need a few updated drivers from them and we'll be good. So I expect a prompt release once we have B&N source.
Click to expand...
Click to collapse
Rock on good sir.. That sounds most exciting indeed!
Perhaps a silly question, but to the end user- what will the difference be between the current and .32 kernel? Faster/better/stronger/able to make cappuccinos?
dalingrin said:
We are actually very close to having a good .32 kernel already. Some of us have been using .32 full time I think. Verygreen did most of the work on the port. He scrapped my .32 work and started over.
We only need a few updated drivers from them and we'll be good. So I expect a prompt release once we have B&N source.
Click to expand...
Click to collapse
I was actually using it for a while. Just needed more clock/governor steppings and the weird "broken SD" and battery fixed, as you already know. It is flying though.
Edit: forgot about sound
Nburnes said:
I was actually using it for a while. Just needed more clock/governor steppings and the weird "broken SD" and battery fixed, as you already know. It is flying though.
Edit: forgot about sound
Click to expand...
Click to collapse
The clock/governor issue is because only the performance governor is compiled into the kernel right now. The broken SD warning is mostly fixed and I believe the same for the battery.
ftp://ftp.asus.com.tw/pub/ASUS/EeePAD/TF201
I think that the section for TF201 shouldn't be the same of the one for TF101. Else it will become a mess here.
gnufabio said:
I think that the section for TF201 shouldn't be the same of the one for TF101. Else it will become a mess here.
Click to expand...
Click to collapse
Agree! Maybe somebody can make a new section for the TF201?
I agree, but it seemed to be the best place for it at the time.
And I think the point is being missed, for the HD2 and my Hero, lots of other device's Kernel's are imported/exported, and since its source, theirs often lots of improvements that can be made cross device when kernel source is available...
So hes putting it here encase any of the kernel developers want to take a crack at porting it over to the TF101 or using parts/pieces/whole/cannibalize it...
either way, the TF201 needs its own section, but I myself approve of this threads importance even in the TF101 section*...
EDIT:*mainly for those oh so eager Kernel dev's who havent had a kernel source release in almost 3 months now! GO GO GO, PORT PORT PORT, CANNIBALIZE!!!
Hold on, is that a kernel for Honeycomb or ICS? if it's for ICS it should be fairly trivial* to backport it to the TF101 for a working ICS on TF101, right?
*actual level of triviality may be relative
Yes TF201 needs its own thread
But i agree with hammerfist about the kernel when the LGp500 source came out we nicked it straight away to port to the GT540 so maybe some similar could be done with this?
Sent from my tf101 using xda premium 1.54Ghz
Danzano said:
Yes TF201 needs its own thread
But i agree with hammerfist about the kernel when the LGp500 source came out we nicked it straight away to port to the GT540 so maybe some similar could be done with this?
Sent from my tf101 using xda premium 1.54Ghz
Click to expand...
Click to collapse
LG P500 and LG GT540 both use the same MSM7227 CPU and shared a lot of hardware, These two have a lot less common of a base, different hardware, different CPU.
Note: in my search the biggest difference apart from one running donut, and one running froyo/gingerbread. is the LCD size
Hammerfest said:
And I think the point is being missed, for the HD2 and my Hero, lots of other device's Kernel's are imported/exported, and since its source, theirs often lots of improvements that can be made cross device when kernel source is available...
So hes putting it here encase any of the kernel developers want to take a crack at porting it over to the TF101 or using parts/pieces/whole/cannibalize it...
either way, the TF201 needs its own section, but I myself approve of this threads importance even in the TF101 section*...
EDIT:*mainly for those oh so eager Kernel dev's who havent had a kernel source release in almost 3 months now! GO GO GO, PORT PORT PORT, CANNIBALIZE!!!
Click to expand...
Click to collapse
Even if we port it, what pros could we get? As soon as ICS is released by Asus we will get the sources of the 3.0 kernel
gnufabio said:
Even if we port it, what pros could we get? As soon as ICS is released by Asus we will get the sources of the 3.0 kernel
Click to expand...
Click to collapse
and that should be by then end of the yuear.. says "asus".... and anyways we dont have a kernel dev right now...
Huh?
KingDavid63 said:
.... and anyways we dont have a kernel dev right now...
Click to expand...
Click to collapse
What? Really? Did Blades and Netarchy quit the biz?
outerdepth said:
What? Really? Did Blades and Netarchy quit the biz?
Click to expand...
Click to collapse
AFAIK they took a breath from work, but I'm almost 99% sure Blades will come back with Clemsyn on his side
They have given us updates faster than any other Manufacturer AFAIK and give source with release I think instead of a few months latter.
ToyTank said:
They have given us updates faster than any other Manufacturer AFAIK and give source with release I think instead of a few months latter.
Click to expand...
Click to collapse
normally.. but there hasnt been a release in almost 3 months now...
@gnufabio: I know, but somehow I dont think they will release kernel source for TF101 ICS as fast (IE prior) like they have for the TF201... it seems they have REALLY started slacking off on the TF101 source release's (see comment above)... hense why I made mention...
I'm showing 10.19.2011 as the last official firmware release. I assume the last 5 weeks they have been making us some ICS no point wasting resources now for honeycomb since we are getting ICS.
http://support.asus.com/download.aspx?SLanguage=en&p=20&s=16&m=Eee%20Pad%20Transformer%20TF101&os=32
Why hasn't this thread been moved?
Actually, that kernel source isn't ICS (ICS builds on 2.6.38, and this source is 2.6.36), but it has some new kernel configs, and an interesting flag too (it shows that the TF Prime will have 2048MB of RAM, my last info was that it's only 1024!)
fonix232 said:
Actually, that kernel source isn't ICS (ICS builds on 2.6.38, and this source is 2.6.36), but it has some new kernel configs, and an interesting flag too (it shows that the TF Prime will have 2048MB of RAM, my last info was that it's only 1024!)
Click to expand...
Click to collapse
Well everything tells you that it has 1024...
Every website and even the official asus one...
ToyTank said:
I'm showing 10.19.2011 as the last official firmware release. I assume the last 5 weeks they have been making us some ICS no point wasting resources now for honeycomb since we are getting ICS.
http://support.asus.com/download.aspx?SLanguage=en&p=20&s=16&m=Eee Pad Transformer TF101&os=32
Why hasn't this thread been moved?
Click to expand...
Click to collapse
Your looking at the FRIMWARE... aka the ROM itself... NOT the SOURCE code! AND to that fact, its like 2-3 version off from release already! So Firmware isnt even up-to-date!!!
Latest Source: 8-15-2011... like i said... months since kernel source release... maybe read whole thing next time? then answer?
And, probably hasnt been moved because its NOT ONLY for the TF201 but has merit and reason to exist in the TF101 section... Want an example? go to the HD2 section for android dev and count how many OTHER device's Kernel source release's there are there... NO REASON to move it given its possible use in the TF101
Closing as this isn't relevant to the TF 101
ASUS Source Code And User Manual for Transformer Prime
the official source code and user manual for the Transformer Prime are available at http://www.asus.com/Eee/Eee_Pad/Eee_Pad_Transformer_Prime_TF201/#download
Source code is version 8.8.3.23, as of 2011.11.24
What does this mean for the Gtab?
I have been wondering if there might be something recent to make this tablet more relevant as a daily-use device.
I realize that a "pre-Alpha" build from an all-but-defunct tablet other than the G-tab may not be the greatest card we were dealt, but I would like to just ask anyone if this means we might be able to run a ~fully working ICS build sooner rather than later?
Opinions?
Sent from my SPH-D710 using xda premium
Correct me if I'm wrong, but the gtab and the Adam both use the Ventana platform of the Tegra 2, which would mean that it would be possible to use the drivers and workarounds they use on this device.
Maybe?
Edit- Or was it Harmony?
Nospin said:
Correct me if I'm wrong, but the gtab and the Adam both use the Ventana platform of the Tegra 2, which would mean that it would be possible to use the drivers and workarounds they use on this device.
Maybe?
Edit- Or was it Harmony?
Click to expand...
Click to collapse
I am quite sure its harmony
This release is huge for the gtab. Right now, I am editing RaYmAn's kernel to get 2.6.39 to boot on the gtablet. As soon as thats done, we will have to edit the g tablet device tree and compile from source. Once that is done, we too will have a gtab ics build that functions amazing.
fosser2 said:
This release is huge for the gtab. Right now, I am editing RaYmAn's kernel to get 2.6.39 to boot on the gtablet. As soon as thats done, we will have to edit the g tablet device tree and compile from source. Once that is done, we too will have a gtab ics build that functions amazing.
Click to expand...
Click to collapse
This excites me greatly
fosser2 said:
This release is huge for the gtab. Right now, I am editing RaYmAn's kernel to get 2.6.39 to boot on the gtablet. As soon as thats done, we will have to edit the g tablet device tree and compile from source. Once that is done, we too will have a gtab ics build that functions amazing.
Click to expand...
Click to collapse
Thank you for replying.
That is EXACTLY what I'd hoped to hear.
You, sir, just made my morning/day/week.
Hooray!
Sent from my SPH-D710 using xda premium
Same as title. I only use the Touchpad for Skype video.
No
Sent from my touchpad via tapatalk
}{Alienz}{ said:
Same as title. I only use the Touchpad for Skype video.
Click to expand...
Click to collapse
Like he said, no.
}{Alienz}{ said:
Same as title. I only use the Touchpad for Skype video.
Click to expand...
Click to collapse
If you only use Touchpad for Skype, why dont you boot into WebOS. Skype video working perfect there.
Sent from my AT&T Galaxy Note - please forgive if typos
Yeah this is what I'm going to have to do.
That's not exactly a bad thing... webos is great. it has better battery life than I've and Skype is good on it. I don't see any problems with it.
Sent from my HP TouchPad
webOs
}{Alienz}{ said:
Same as title. I only use the Touchpad for Skype video.
Click to expand...
Click to collapse
Webos supports skype very nicely if this is all you use the touchpad for.
I have ICS on mine as well and most of the time I use webOs seems to support almost every site i go to. I have only found a few site it wont work on,Netflix windows live, Hulu.
I use ICS for netflix dont use Hulu and for windows live i just use the webOs email client and hotmail or windows live works fine.
The only thing I am trying to find is a book reader that views text files and has a bookmark or save page function in it , Ics has kemsoft and works but many times bookmark wont work .
}{Alienz}{ said:
Same as title. I only use the Touchpad for Skype video.
Click to expand...
Click to collapse
No.
And aren't there already like 10 other threads about this?
Still no.
[5 minutes later]... Still no.
Camera is most likely not going to be working for a very long time, despite HP releasing the source for the hardware (or are they still delaying it) and its the last on the priorities list for any developer. I suggest use WebOS for skype cuz that works brilliantly
I'm very confused because I read in another thread in the Question-Answer section that it would come out in two weeks?
Could anyone fact check this?
Here
Mast3rmatt said:
I'm very confused because I read in another thread in the Question-Answer section that it would come out in two weeks?
Could anyone fact check this?
Here
Click to expand...
Click to collapse
The sarcasm looks strong with that one.
mkosem said:
The sarcasm looks strong with that one.
Click to expand...
Click to collapse
Hmm I guess I read it in the wrong way
Thanks
Mast3rmatt said:
I'm very confused because I read in another thread in the Question-Answer section that it would come out in two weeks?
Could anyone fact check this?
Here
Click to expand...
Click to collapse
The camera will be fully functional in two weeks. If not, read this again
I really want the camera n mic to work too. Is the ics kernel or driver the problem?
hyperfire21 said:
I really want the camera n mic to work too. Is the ics kernel or driver the problem?
Click to expand...
Click to collapse
This is not the place to pose this question. The place to ask would be Rootzwiki, where the dev's can be found. There you'll find changelogs and sourcecode for just about everything, and you can certainly make changes and compile it yourself.
If you honestly and seriously know what you're talking about, and think you can help, the dev team would probably be very appreciative of assistance. Meaning, if you can code that stuff, great- lend a hand. But if you're just curious, then try to research your question without nagging the devs. They work hard, and for free. You could begin researching the topic, here.
Now, in answer to your question. I could be wrong. I'm just a simple Java/C# coder who can also do a bit of web. But it was my understanding that the driver is the issue. The source code for the kernel has been released, but (also as I understood it, I could be wrong) the entire kernel was not released. The drivers for mic and cam, however, were not released (again, if I understood correctly). So there's the problem. And further, the cam and mic are not at the top of the devs' list of priorities. They are working on other stuff that they feel is more important, about which I tend to agree, unknowingly. I mean, they recently (in the last 4-6 weeks) got us hardware acceleration working (in several applications, but not all). What I mean to say, is that there are bigger fires to be put out that users don't typically see as fires. But also, the cam and mic drivers not being released is a pretty big chunk of code. AFAIK they were going to have to begin to write these from scratch, which is a pretty hefty challenge that they've chosen not to undertake at this point. That's their prerogative, and I'm not going to nit-pick about that.
Basically, if you need cam and mic, you can install CM7 (which has bugs of its own) or you can boot into webOS. Those are our options at the moment.
sean is here. said:
Basically, if you need cam and mic, you can install CM7 (which has bugs of its own) or you can boot into webOS. Those are our options at the moment.
Click to expand...
Click to collapse
Or learn software development and learn to write drivers and contribute!
Personally, I know I can't code worth a damn, so I just accept what other people write.