Will htc ever.......... - Droid Eris Android Development

release the kernel that will enable developers here to overclock or use apps2sd??? sheesh!!!

iflip said:
release the kernel that will enable developers here to overclock or use apps2sd??? sheesh!!!
Click to expand...
Click to collapse
I think we can do app2sd we just really dont need it. OC is another thing....

I hope so, from what I understand you should be able to ask HTC and get the source code without a problem because it's opensource (correct me if I'm wrong) but HTC just won't give it up for some reason. It'd be nice to get overclocking, I don't want push it to a gig or anything, I just think 700mhz is a nice number.

Spencer_Moore said:
I think we can do app2sd we just really dont need it. OC is another thing....
Click to expand...
Click to collapse
dont quote me on this but i believe jcase stated that once we do get it, that 600 was the sweet spot since our proc is just like the >???? cant rem which one he said was pretty much the same as ours.
cannot wait. as i know you devs are saying the same thing as you actually know how to do all this ****. thanks again you guys.

I wouldn't get too excited about the overclocking. It's not going to help much with the Eris CPU.

HTC is currently in violation of the GNU by not releasing the source code. Email them about it, and tell them what you think.

seanmcd72 said:
I wouldn't get too excited about the overclocking. It's not going to help much with the Eris CPU.
Click to expand...
Click to collapse
I dont know if thats fact, i mean we dont even know what the cpu is capable of. I don't think anyones advocating clocking a 528 to 1gig or anything. I think people just want a little more headroom (say 600mhz) is all.

As I understand it HTC doesn't have to give us anything because the phones are shipped with proprietary software installed by HTC.

Not sure if this is right or not, but from what I read the kernel source was already released @ http://developer.htc.com/
Is this right?

hmm....nevermind. Just read a little more into the release of that kernel source. Disregard.

looks Like that's the source codes for 1.5 & 1.6 I guess when the upgrade to 2.1 is official, well be able to overclock, hopefully our devs will still have eris's by then. Lol.
Sent from my Eris using the XDA mobile application powered by Tapatalk

Unheard said:
HTC is currently in violation of the GNU by not releasing the source code. Email them about it, and tell them what you think.
Click to expand...
Click to collapse
The linux kernel is licensed under the GNU General Public License and it i available from kernel.org
The bulk of Android however is released under the apache license. I do not believe there is any legal requirement to provide source code to changes made to it, but I could be wrong. However, the android source code itself is available from google.
Additions to android, such as HTC Sense, use completely different and most likely closed-source licenses. There is no legal requirement to provide sources for them, depending on license of course.

Related

Roms and Kernels

Sorry for noob question (and PLEASE DONT FLAME ME BECAUSE OF THIS) but will roms/kernels for other devices work with the incredible? just wondering\
AND PLEASE, IF YOU THINK I AM A COMPLETE IDIOT FOR POSTING THIS THEN JUST KEEP IT TO YOURSELF
pretty sure they won't or people would be posting about which ones worked well and which ones didnt.
i think a rom has to have a certain amount of customization for the actual device it is going to be loaded on before it will work.
JustinD2473 said:
pretty sure they won't or people would be posting about which ones worked well and which ones didnt.
i think a rom has to have a certain amount of customization for the actual device it is going to be loaded on before it will work.
Click to expand...
Click to collapse
Thank you
How is your froyo port going to work if you didn't know this? Just wondering.
Sent from my ADR6300 using XDA App
grape ape---i did know, just confirmiing
rr12106 said:
will roms/kernels for other devices work with the incredible? just wondering
Click to expand...
Click to collapse
No, if you try to flash a rom or kernel made for another device you can brick your phone.
Captchunk said:
No, if you try to flash a rom or kernel made for another device you can brick your phone.
Click to expand...
Click to collapse
Or get stuck in boot loops
TNS201 said:
Or get stuck in boot loops
Click to expand...
Click to collapse
or explode in a ball of flame...
oh wait... that was mixing gasoline with new roms... and fire...
But yea, should probably avoid flashing roms for other devices without properly porting them.
Never flash a ROM that was meant for another device. You risk not being able to use the phone again.
And if anyone were to flame you for posting this questions they'd take a lot of crap from a lot of people for being a douche.
Don't ever be afraid to post a question
hexto said:
And if anyone were to flame you for posting this questions they'd take a lot of crap from a lot of people for being a douche.
Click to expand...
Click to collapse
Usually this is true, but the OP knew he was risking flame because he's claimed in other threads to be an experienced in building ROMs and knew how to port Froyo to the Incredible.
That doesn't really mesh well with his noob question here.
Reported. This again BELONGS IN GENERAL...man the second post in like 3 hours to be in the wrong section..
elborak said:
Usually this is true, but the OP knew he was risking flame because he's claimed in other threads to be an experienced in building ROMs and knew how to port Froyo to the Incredible.
That doesn't really mesh well with his noob question here.
Click to expand...
Click to collapse
However, he knows, as well as we, that he was over exaggerating on his original claims. We did encourage him to ask questions and learn, can't flame him for making an effort to go down the right path, ask questions, learn, experiment. I'd rather him ask questions, then post falsified claims of froyo builds etc. Much rather.
CaptainTaco said:
We did encourage him to ask questions and learn, can't flame him for making an effort to go down the right path, ask questions, learn, experiment. I'd rather him ask questions, then post falsified claims of froyo builds etc. Much rather.
Click to expand...
Click to collapse
True. Very true.
Thread moved to General.
rr12106 said:
Sorry for noob question (and PLEASE DONT FLAME ME BECAUSE OF THIS) but will roms/kernels for other devices work with the incredible? just wondering\
AND PLEASE, IF YOU THINK I AM A COMPLETE IDIOT FOR POSTING THIS THEN JUST KEEP IT TO YOURSELF
Click to expand...
Click to collapse
I've watched your posts, I know a few folks who are ambitious and think this whole "programming thing" is easy. I'll try to make this simple.
Think of it like this... I compiled an ultra small Kernel of Linux, I only compiled it for a specific computer so I built as much as I could for this specific computer into the kernel, AMD MP, Intel GPU and northbridge, USB 2.0... this way I didn't have to load Modules, it was part of the kernel.
When you install Unix, old school anyway, you are prompted for computer specs so it knows which pre-compiled kernel to select (AMD versus i586 versus i386... etc.) to run the best on your machine. These days it autodetects and makes it easy.
Android is a form of *nix so behaves the same... manufactures compile kernels specific to their devices so that they perform better.
Now, If I used an old Kernel that didn't support USB2 and only supported USB1 then I would be running slow at USB1 or would have to compile without USB at all and load a module that enabled support for USB2...
Android versions are being released with updated kernels for greater support of a wider variety of devices at the kernel level, less modules to load means a faster machine. Some functions still work better with poer saving setups as a module (802.11b/g/n for instance will almost always be a module).
"ROM" which means Read Only Memory are copies of modified kernels from the same device. If I copied the kernel from my machine to another it wouldn't work unless it was identical specs, even one item off and you get kernel dumps, it doesn't know how to talk to your hardware.
Get an idea of what is involved in compiling a kernel here: http://www.linuxforums.org/forum/linux-kernel/55612-mini-howto-compile-linux-kernel-2-6-a.html
I hope this helps you to see that even someone who knows BSD, Linux and Unix... with multiple certifications for Linux (and countless other platforms) and more than 20 years as an engineer... I won't touch making a ROM or trying to modify the bootloader. I wait for the people who know Android's OS, the way it's built, the way it functions... I allow these geniuses to build cool ROMs. I send them donations for their time as some have sent me donations on other forums for my time on other subjects.
It's not as easy as dropping "som 1337 romz" into some folder and presto, "i'z rokn FroYo homz"... it's so much more than that. Someone has to compile the kernel and get the hardware working... it's just easier to wait for the manufacturer to release an update and then find a way to gain root access to do what we want with it.
Additional note:
Check the latest kernel version of Linux here: http://www.kernel.org/
Go into settings and see what version your Doid's Kernel is.
I am going on a limb here but I'm pretty sure there is a correlation.
compnird said:
It's not as easy as dropping "som 1337 romz" into some folder and presto, "i'z rokn FroYo homz"... it's so much more than that.
Click to expand...
Click to collapse
LMAO!! Nice explanation, though.
compnird said:
I've watched your posts, I know a few folks who are ambitious and think this whole "programming thing" is easy. I'll try to make this simple.
Think of it like this... I compiled an ultra small Kernel of Linux, I only compiled it for a specific computer so I built as much as I could for this specific computer into the kernel, AMD MP, Intel GPU and northbridge, USB 2.0... this way I didn't have to load Modules, it was part of the kernel.
When you install Unix, old school anyway, you are prompted for computer specs so it knows which pre-compiled kernel to select (AMD versus i586 versus i386... etc.) to run the best on your machine. These days it autodetects and makes it easy.
Android is a form of *nix so behaves the same... manufactures compile kernels specific to their devices so that they perform better.
Now, If I used an old Kernel that didn't support USB2 and only supported USB1 then I would be running slow at USB1 or would have to compile without USB at all and load a module that enabled support for USB2...
Android versions are being released with updated kernels for greater support of a wider variety of devices at the kernel level, less modules to load means a faster machine. Some functions still work better with poer saving setups as a module (802.11b/g/n for instance will almost always be a module).
"ROM" which means Read Only Memory are copies of modified kernels from the same device. If I copied the kernel from my machine to another it wouldn't work unless it was identical specs, even one item off and you get kernel dumps, it doesn't know how to talk to your hardware.
Get an idea of what is involved in compiling a kernel here: http://www.linuxforums.org/forum/linux-kernel/55612-mini-howto-compile-linux-kernel-2-6-a.html
I hope this helps you to see that even someone who knows BSD, Linux and Unix... with multiple certifications for Linux (and countless other platforms) and more than 20 years as an engineer... I won't touch making a ROM or trying to modify the bootloader. I wait for the people who know Android's OS, the way it's built, the way it functions... I allow these geniuses to build cool ROMs. I send them donations for their time as some have sent me donations on other forums for my time on other subjects.
It's not as easy as dropping "som 1337 romz" into some folder and presto, "i'z rokn FroYo homz"... it's so much more than that. Someone has to compile the kernel and get the hardware working... it's just easier to wait for the manufacturer to release an update and then find a way to gain root access to do what we want with it.
Click to expand...
Click to collapse
Thanks...that helped alot
Sent from my Incredible using XDA App

CyanogenMod 6.1 is on its way! And its easy to get on Captivate!

Sorry if this has already been posted.
I apologize for not keeping the site up to date, I’m a slacker We also had a database issue and lost the last post about 6.0′s release, if you were wondering why it went missing.
6.1 is the current work-in-progress and is coming together nicely. There’s a few new features like touch-to-focus in the camcorder, dismiss notifications by swiping, kernel updates for most devices, and improved performance. There will also be support for a few new devices- Acer Liquid, HTC Wildfire and Samsung Vibrant. My eye is also on the new HTC phones that are about to get released like the G2.
A lot of people ask me about adding support for their phone, but we can only support phones that we actually own. The CM team is always looking for new hackers to join up with us to add support for their favorite device. Get in touch with me if you’d like to help.
CyanogenMod is open source. The quality of code being added to CM has vastly improved because of the code review system that we’ve put in place, Gerrit. It’s the same system used by Google to manage the Android Open Source Project. It allows anyone to submit code to the project in a highly-visible way and gives us a way to examine and improve it before it’s actually merged. We want your code, so send us your patches. If there’s something you don’t like, change it.
Nightly builds of CM are always available if you’re brave and want to try out the latest code. If you’re running nightly builds, the best way to stay up to date on new changes is to follow @cmsrc on Twitter.
Our user base is approaching a quarter of a million users. This project has come a long way Thanks for all the support, we are only as strong as the community!
Source- Cyanogenmod.com
Porting a vibrant rom to the captivate is not hard
no wayyyy this is finally coming to our cappy, i'd be beyond happy
Hate to sound like a douche, but is there anything in there (besides maybe some of the features of CM6.1) that we havent known for a long time? No release date, we know thier working on it, and we know they are working with the vibrant.
Well if you look here it still shows as in progress for version 6.0...They have said in the past that the vibrant won't be supported till 6.1 and then someone will still have to port it to the captivate..
https://spreadsheets.google.com/lv?key=0Aledx886TFpZdHdwNzNKZzJLczJjTnA5ekFWRzNxX2c&hl=en&authkey=CNf7ie8G
So I don't think we will be seeing anything soon...
so, i'm sure everyone will get a good laugh, because everyone talks about how this is the best thing about to come since sliced bread........
but what is SO great about this?
buddy17 said:
so, i'm sure everyone will get a good laugh, because everyone talks about how this is the best thing about to come since sliced bread........
but what is SO great about this?
Click to expand...
Click to collapse
Froyo! Plus lots of custom stuff.
well i knew it was based on 2.2....but the "custom stuff" is what i meant. What are some of the big things it does that are so great
I'm new to the whole Android scene so excuse my ignorance but can someone explain how CM6.1 can possibly be put on a GalaxyS phone when there is no source code for the kernel?
Sent from my SAMSUNG-SGH-I897 using XDA App
sdotbrucato said:
I'm new to the whole Android scene so excuse my ignorance but can someone explain how CM6.1 can possibly be put on a GalaxyS phone when there is no source code for the kernel?
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
The other custom roms seem to use the 2.1 kernel.
I checked that spreadsheet about 3 weeks ago, and it was still in development like it is now for the vibrant.
buddy17 said:
well i knew it was based on 2.2....but the "custom stuff" is what i meant. What are some of the big things it does that are so great
Click to expand...
Click to collapse
Its not really about a wealth of extra features. Cyanogenmod has extra configurability. In addition it is a bit more cohesive than typical roms. I definitely preferred it over the stock Nexus One rom and the stock nexus one rom is better than stock Captivate.
The rapid updates and support is enough for me to use Cyanogenmod.
z28james said:
The other custom roms seem to use the 2.1 kernel.
Click to expand...
Click to collapse
But 6.1 is Froyo, all the ROMs I've seen are Eclaire... How are they using a 2.1 kernel with Froyo?
I was under the impression the reason for no Froyo ROMs on the Captivate was due to lack of source from Samsung?
Sent from my SAMSUNG-SGH-I897 using XDA App
Who needs this when we have cognition?!
designgears said:
Who needs this when we have cognition?!
Click to expand...
Click to collapse
exactly
designgears said:
Who needs this when we have cognition?!
Click to expand...
Click to collapse
i'm sure when this comes out you'll be able to strip the FroYo out of it and make it your own, and better
CM6.1 will come to the captivate after is released to the vibrant, kernel differences are minimal between the two so porting CM6.1 to the captivate will only require few kernel changes.
yeah i'm sure the port will be done in the time it takes to heat up a pop tart.
designgears said:
Who needs this when we have cognition?!
Click to expand...
Click to collapse
+1 Finally got my Cappy right where I want it. CM is awesome, I'm just tired of all the hype, not to mention the waiting for this stuff to happen.
designgears said:
Who needs this when we have cognition?!
Click to expand...
Click to collapse
Everyone who is waiting to use Voice Actions, Chrome-to-phone, and any other cool 2.2-only apps.
Yeah, like real Flash or having the speed boost of the JIT compiler.

What features the X10 misses after Gingerbread (what do we need from developers)

I am just trying to combine all the required things in here so that it is easy for a developer or a newcomer to the world of the Xperia X10 to know what the phone really lacks.
1)Real Multitouch:
After the debate whether the chip of the X10 is Cypress or Clearpad, no progress was made in that direction even fixing the buggy dual touch we have (cross-axes problem) giving us a full dual touch.
2)16 million color:
yes, it may not be so crucial to anyone, but really why don't we get a puppy while we can unleash a dragon, and who doesn't want an extra feature in his phone?
(Thanks Z for the Bravia Engine and the FPS uncap).
3)Unlocked Bootloader:
This is the big deal and the door to unleashing the X10, Custom ROMs and Kernels will be much better, features that SE don't want us to get will be easily achieved (MT, 16M, even porting other OS like WP7 or MeeGo or ice cream sandwich :O), developing for the X10 will be easier and more open, and we would really get a phone that can compete with the Arc.
P.S.: I would like to thank the developers working on the X10 now Z, J, Ericwill, Achotjan, Wolfbreak, Cobrato, Doomlord, kxhawkins, Androxyde, ThJap, viousAD, & Trip.
Guys, without you the X10 would have been a bulk of **** staying in the eclair era with one touch and nothing would have improved, your work has saved us a lot, and we are asking you not to leave us because we really like you.
Please if you have a feature or anything that you feel missing from the phone you can post it, it is just a collection of the flaws in the X10.
I agree with op as well. We certainly need the bootloader its what keeps us from unleashing the beast heck I wouldn't be surprised if x10 is faster than arc
Sent from my X10i using XDA App
couldn't we achieve the custom kernels on gingerbread using the bootloader bypass thing?
I think the devs are waiting for se to release kernel sources
OP
I Agree.
I think the problem is and always has been having a developer who can write the drivers. Until then, I don't think it matters.
agentJBM said:
I think the problem is and always has been having a developer who can write the drivers. Until then, I don't think it matters.
Click to expand...
Click to collapse
It's much more complex that it seems.
Not even OEMs (SE, HTC, Motorola, you name it) write the device drivers for themselves.
Most of the source is provided by the hardware manufacturer (qualcomm, atheros, broadcom) - and a huge part of it is under NDA (non-disclosure agreement).
Without the thorough documentation and source code examples, it's highly unlikely to write any device driver by your own
Obviously, you could try to reverse-engineer stuff, but it's a "rocket science", even for experienced developers/companies.
Cheers,
z
zdzihu said:
It's much more complex that it seems.
Not even OEMs (SE, HTC, Motorola, you name it) write the device drivers for themselves.
Most of the source is provided by the hardware manufacturer (qualcomm, atheros, broadcom) - and a huge part of it is under NDA (non-disclosure agreement).
Without the thorough documentation and source code examples, it's highly unlikely to write any device driver by your own
Obviously, you could try to reverse-engineer stuff, but it's a "rocket science", even for experienced developers/companies.
Cheers,
z
Click to expand...
Click to collapse
So, would you agree that none of this stuff will ever happen without help from the manufacturers or a "Rocket Scientist" Developer?
Edit: Not that you aren't a genius. Just clarifying that we don't have the resources, no matter what.
agentJBM said:
we don't have the resources, no matter what.
Click to expand...
Click to collapse
Totally agree
Cheers,
z
Stop calling developers some glorified copy pasters of cyanogen mod files.
True.. without source code it becomes string theory.
Rocket science is too easy.
@op you forgot fps cap removal
Sent from my x10 on official gingerbread
Lion3494 said:
@op you forgot fps cap removal
Sent from my x10 on official gingerbread
Click to expand...
Click to collapse
no he didnt,FPS cap is already removed, just see the android section!!
kunalgahlot said:
no he didnt,FPS cap is already removed, just see the android section!!
Click to expand...
Click to collapse
Not to 54 frames buddy. Thats just on stock the 34
Sent from my x10 on official gingerbread
Lion3494 said:
Not to 54 frames buddy. Thats just on stock the 34
Sent from my x10 on official gingerbread
Click to expand...
Click to collapse
No what he means is its already been achieved with custom kernels.
Sent from my X10i using XDA Premium App
I meant to mention things that aren't yet developed for the X10.
A feature that was exciting but was pulled back is the ability to dual boot two roms using xrec 1.0, I liked it despite never using it because it would be beneficial for the future usage :]
At least I thought that in future devs can make dual touch fully working but Z says its not possible without sources
Sent from my X10i using XDA Premium App
Wifi Proxy
I thought this new GB will include the support proxy setting. I have seen in some ROM I forget which one it was that have the proxy setting in it.
I know, this is sad, for lots of school, and corporate that have proxy server, most android phone/tablet are not able to connect to the net. This is a big thing if the android want to get to some of corporate and the education sectors of the market.
I hope the DEV would do something that could enable this proxy feature.
Since day one that I have the X10, I have been disappointed with the lack of this feature.
Not to mention that it also lack of the Cisco IPSEC VPN setting as well.
i did'nt ask for a dual core implement or 32 finger multi touch i just asked for a precise dual touch which SE Fails to provide me with!
KInG GaME said:
i did'nt ask for a dual core implement or 32 finger multi touch i just asked for a precise dual touch which SE Fails to provide me with!
Click to expand...
Click to collapse
All of us do want that
Sent from my X10i using XDA App

Spam Cyanogen?

My cousin recently put his Streak to rest because he upgraded to the Motorola Atrix, he was saying how the Streak became the forgotten golden child. I was thinking why not Spam Cyanogen on Twitter and ask for Streak development? Maybe someone would be bold enough or kind enough to offer him a an old Streak to work on? Long shot but I don't think it would hurt to try.
Just trolling out loud is all lol
http://twitter.com/cyanogen
cyanogenmod is overrated imho
aaronv89 said:
cyanogenmod is overrated imho
Click to expand...
Click to collapse
As Much as I miss Cyanogenmod on my HTC ARIA I would not trade it for for my Simple streak 1.2!
refthemc said:
. . . . because he upgraded to the Motorola Atrix, . . . .
Click to expand...
Click to collapse
I would not call anything with MotoBlur an upgrade.
marvin02 said:
I would not call anything with MotoBlur an upgrade.
Click to expand...
Click to collapse
atrix is beast tho
Don't spam Cyanogen, they are willing to make rom for Streak (actually DJ_Steve tried it), but nobody can because we don't have all drivers for Dell Streak (audio driver was not released and Dell won't release it in the future).
But if you want to spam something, check this:
http://www.ideastorm.com/ideaView?id=087700000008XYuAAM#comments
marvin02 said:
I would not call anything with MotoBlur an upgrade.
Click to expand...
Click to collapse
+1. Motoblur is the worst android coding I've ever seen. It doesn't even run well on many dual core phones.
Revin said:
Don't spam Cyanogen, they are willing to make rom for Streak (actually DJ_Steve tried it), but nobody can because we don't have all drivers for Dell Streak (audio driver was not released and Dell won't release it in the future).
Click to expand...
Click to collapse
CM7 isn't overrated, its AOSP with tweaks, built-in overclocking settings, status-bar tweaks, unlock screen tweaks, DSP manager, all built from source, no bloat, very fast and compatible... nothing to not like about it.
As far as audio drivers not working, Fards seems to have it working just fine in his fork of the 'alpha' gingerbread source code that Dell released, so I'd say that's patently false... Although his kernel is still quite buggy (certain sensors not working, wakelock issues, etc)... I'd say his kernel fork is probably the closest thing to getting CM working on our Streaks.
The work Fards/AWD_Maniac have done is phenomenal, that being said, I have no idea how much work would need to be done to make the kernel work with a CM7 userland.
*edit*, the Atrix blows, also being obnoxious never got anyone anywhere.
I too think that Fards/AWD_Maniac did great job, but just check the forums with CM6.1 alpha and MIUI alpha from DJ_Steve. He stopped the development because audio was not working and he needed audio drivers for Dell. I believe, that if there will be some way he will make it. I am not sure if you can make driver for something you know nothing about and without support.
But of course it will be nice to have CM/MIUI for our devices.
Anyway, please comment and vote, if you check page 3/4, there are people asking for Gingerbread. Actually Amy from Dell wrote on twitter that who wants Gingerbread should vote/post there:
http://www.ideastorm.com/ideaView?id=087700000008XYuAAM#comments
So I am asking everyone - please go there and give there as many votes as possible. Create another accounts, ask your friends etc.
We can have at least Gingerbread officially!
Revin said:
I too think that Fards/AWD_Maniac did great job, but just check the forums with CM6.1 alpha and MIUI alpha from DJ_Steve. He stopped the development because audio was not working and he needed audio drivers for Dell. I believe, that if there will be some way he will make it. I am not sure if you can make driver for something you know nothing about and without support.
Click to expand...
Click to collapse
Maybe you're not getting what I'm saying, Fards is already compiling kernels for gingerbread... FROM SOURCE, even if binary blobs are being used for audio libraries, they were compiled for Linux kernel 2.6.35, the version needed by GB. I don't think this is a stumbling block for anyone anymore since we now have a working kernel from source for gingerbread.
It seems that DJ_Steve never had too much luck compiling the Android userland for the Streak, in fact, I don't think anyone really has, except for those TERRIBLE MIUI/CM ports, but I'm thinking even those were binary rips. All the Streakdroid versions (sans 2.0.0) used pre-compiled files from official dell builds for the Android userland.

NVDIA TEGRA Documentation to be Released

Will this help development of ICS and JB ROMS? http://www.engadget.com/2012/09/23/nvidia-to-offer-up-documentation-for-tegra-graphics-core/
This should solve the video camera issues and other issues I think.
It's the documentation for the Tegra chips.
Looks like a good news and a bit of light for ICS+JB for our Atrix. Lets keep waiting...
No idea, but good find nevertheless.
Assuming this is released, what else will be needed to release a stable CM9?
It really depends on whats is going to be released. We don't know if its going to be useful yet.
Sent from my MB860 using xda app-developers app
Yeah it will help even to make better kernels, is a shame that my Atrix touchscreen died totally two days ago (thread reported will move soon, does not belong here).
RAFAMP said:
Assuming this is released, what else will be needed to release a stable CM9?
Click to expand...
Click to collapse
Once Tegra2 graphic driver source is released, Atrix devs then just simply update and compile the expecting module (.ko file) to put into the kernel of their roms
hainguyen273 said:
Once Tegra2 graphic driver source is released, Atrix devs then just simply update and compile the expecting module (.ko file) to put into the kernel of their roms
Click to expand...
Click to collapse
Thank you for your replies, guys!
So, with the graphics drivers into the kernel we would get 100% working roms?
RAFAMP said:
Thank you for your replies, guys!
So, with the graphics drivers into the kernel we would get 100% working roms?
Click to expand...
Click to collapse
Yes.
fviero said:
Yes.
Click to expand...
Click to collapse
I hope it's soon then!
hainguyen273 said:
Once Tegra2 graphic driver source is released, Atrix devs then just simply update and compile the expecting module (.ko file) to put into the kernel of their roms
Click to expand...
Click to collapse
I'm not particularly knowledgable about the ins and outs of Nvidia's modules so I might be wrong here, but I seem to recall a dev on this forum saying that is wasn't just a matter of the binaries being compiled against a different kernel (which could be worked around if it was just version checking), but that it depends upon functionality that only exists in newer kernel versions.
If somebody on this forum were skilled enough/had the time to donate to port the Nvidia 3.1.10 sources to the Atrix, we could have fully functional ICS/JB today. But it's not reasonable to expect the few skilled kernel devs here to make up for Motorola's slack.
Over in the One X forum, richardtrip has ported the reference 3.1.10 kernel using only a few bits of hTC code for the camera, so it is certainly possible for somebody without 'inside knowledge' to do, but it has taken him months of hard work. (we're on 2.6.39 'till hTC's official jellybean drops, which uses a 3.1.10 kernel anyway)
Well.. there is still the matter of the fingerprint scanner beyond the kernel. But we can't get too greedy now can we?
thantos said:
Well.. there is still the matter of the fingerprint scanner beyond the kernel. But we can't get too greedy now can we?
Click to expand...
Click to collapse
The phone would probably be functional without a fingerprint driver, though.
This is not kernel module source they are releasing; they are just saying they are willing to provide more information to the opensource community. NVIDIA has recently indicated they may provide documentation to those working on the nouveau drivers (opensource NVIDIA PC drivers); under an NDA. Meaning that they will provide the documentation to those that work on the opensource driver but not allow the information to be shared. For this to be helpful we would need the documentation provided to someone who is working on opensource Tegra drivers; which I do not believe there is anyone. So this would probably be picked up by those working on the nouveau drivers. Best case if all the information is provided and they decide to work on it it would probably be at least a year before we would have anything stable for use.
thantos said:
Well.. there is still the matter of the fingerprint scanner beyond the kernel. But we can't get too greedy now can we?
Click to expand...
Click to collapse
Yeah, same for the lapdock.
Enviado desde mi MB860 usando Tapatalk 2

Categories

Resources