http://forum.archosfans.com/viewtopic.php?f=34&t=40921
it is for eclair
not froyo
Sorry my bad, should have checked the links
Froyo:
http://www.archos.com/support/download/software/sources/gen8-gpl-froyo.tgz
Or you an just go to the Archos Support link... both Eclair and Froyo are downloadable under "Notice of GNU General Public License and Lesser General Public Licence"
http://www.archos.com/support/support_tech/updates.html?country=gb&lang=en
cajl said:
it is for eclair
not froyo
Click to expand...
Click to collapse
Froyo link:
http://www.archos.com/support/download/software/sources/gen8-gpl-froyo.tgz
Froyo link has been linked for well over a week now by supagforce at http://forum.xda-developers.com/showthread.php?t=859678 .
MoonPhantasm said:
Froyo link has been linked for well over a week now by supagforce at http://forum.xda-developers.com/showthread.php?t=859678 .
Click to expand...
Click to collapse
Double ouch! Not only was I a few seconds late now you point out that I am a week late.
It happens. Thanks for trying to help anyway. Good intention is always good.
I just wanted to keep the discussions about the GPL from fragmenting into two separate threads, especially when there are useful hints already in the original thread. ^^
Related
http://opensource.dell.com/releases/streak/
Let the custom rom's come pouring in.
Sent from my HTC HD2 using XDA App
boo to the buggy 2.1, yay to those that will fix it and make it useable.
boo to dell for releasing yet another near useless kernel
cowballz69 said:
http://opensource.dell.com/releases/streak/
Click to expand...
Click to collapse
2.06? It doesn't even build properly...
smokku said:
2.06? It doesn't even build properly...
Click to expand...
Click to collapse
Its a friday build
See this from Cyanogenmod forum posted by photopuppet:
At least the support for it is strong.
If any of you people reading this have Twitter, make sure you take a quick minute to hit up @LionelatDell @mdomsch and @DellCares with a comment indicating your displeasure and demanding a full source release! Remember to add #dell and #dellstreak tags too.
If you have extra time, also send an e-mail reporting this problem at www.gpl-violations.org
The more people we can get on-board with protest, the more attention this issue will get!
Click to expand...
Click to collapse
Lets hope they sort it out in the next few days or so *hoping* >.<
new one up today............hope it's good
digthemlows said:
new one up today............hope it's good
Click to expand...
Click to collapse
its good hipeeeeeeeeeeee
has anyone compiled this into an easy update?
How to install the 2.1 on the dell streak?
Godo_PPL said:
has anyone compiled this into an easy update?
Click to expand...
Click to collapse
there is NO point in "updating" to this, its only the SOURCE for the kernel thats already installed on your streak, its useful so devs can compile different modules into the kernel to enable things like "Wifi tether for root users" other BlueZ enhancments, etc... obviously having the source makes it easier to port Froyo and Vanilla 2.1 builds. Once again, this doesn't pertain to you unless you are able to compile it yourself, if you have questions, well its probably not something that you need to even worry about.
Flashed the unofficial 2.2 for samsung vibrant, and my MMS are all blurry and dont even blow up right
anyway to fix this?
thank you
thehollywoo
TheHollywoo said:
Flashed the unofficial 2.2 for samsung vibrant, and my MMS are all blurry and dont even blow up right
anyway to fix this?
thank you
thehollywoo
Click to expand...
Click to collapse
Did you even read the OP for the rom you installed? Either it was Eugene373's Macnut, Team Whiskey's Obsidian, Master's Axura, or Anderdroid's Aosp'ish... Really its a moot point as they are all basically Eugene's Macnut, just with framework mods ( exception might be Obsidian, as he doesnt directly credit Eugene for any work ) Anyway, the blurry MMS is a stated shortcoming of the current batch of 2.2 roms... Search is your friend... it saves you from posting qusetions that already have anwsers.
Frizzmmm said:
Did you even read the OP for the rom you installed? Either it was Eugene373's Macnut, Simbionix's Obsidian, Master's Axura, or Anderdroid's Aosp'ish... Really its a moot point as they are all basically Eugene's Macnut, just with framework mods ( exception might be Obsidian, as he doesnt directly credit Eugene for any work ) Anyway, the blurry MMS is a stated shortcoming of the current batch of 2.2 roms... Search is your friend... it saves you from posting qusetions that already have anwsers.
Click to expand...
Click to collapse
Wow. Not at all.
Macnut was originally on JPM
My ROM went on JPA & JPO before eugene. And the 2.0 version which is still in development doesn't use ONE thing of eugenes.
And Sombionix's rom doesn't use ONE thing of eugenes either
Eugenes macnut isnt JK2 either. People like you think that we base everything on Eugene.
Did YOU even read the OP's?
And to the OP:
Yes we are all aware of it, and it is an issue we are all trying to fix.
Master™ said:
Wow. Not at all.
Macnut was originally on JPM
My ROM went on JPA & JPO before eugene. And the 2.0 version which is still in development doesn't use ONE thing of eugenes.
And Sombionix's rom doesn't use ONE thing of eugenes either
Eugenes macnut isnt JK2 either. People like you think that we base everything on Eugene.
Did YOU even read the OP's?
And to the OP:
Yes we are all aware of it, and it is an issue we are all trying to fix.
Click to expand...
Click to collapse
Master I would first like to offer my apology for offending you, not my goal or intention, and as I have, you have my apologies.
In retro spect, my wording on a quickly typed reply to fly under the radar while I am work seems to have not conveyed the message I originally intended.
I did not wish to say that all roms are copies of Eugene's work, but similarly suffer from the same shortcomings, and I had a noted exception of Team Whiskeys offering as they are the sole developer which does not credit any work from eugene.
and unless I am confused, your axura rom comes with eugene's #45 kernel and in its op states that mms is blurry.
I understand that your Rom is based on JPO, Macnut is based on JPM and Team Whiskey derives their work from JK2... All of which are available for easy reading ( Ill admit, i used the search feature for that info )
And to answer your retort, Yes, I do read the OP. I use the search feature before Posting a question to make sure there hasnt been a similar question or an answer to it, and even when getting my facts straight. Thank you for your time and giving me a chance and reason to better explain my reply to the OP of this post.
I invite you to continue any further discusion about my errors in DM, rather than airing any problems or errors as if they were dirty laundry.
FRIZZ
I read and I read well, but its a simple question to read if there is a fix for it.
I am running JK2 as i stated above, its the UNOFFICIAL 2.2
TheHollywoo said:
FRIZZ
I read and I read well, but its a simple question to read if there is a fix for it.
I am running JK2 as i stated above, its the UNOFFICIAL 2.2
Click to expand...
Click to collapse
Here, Ill save you the difficulties.
http://forum.xda-developers.com/search.php
Save you even more trouble, The answer is no.
My method for arriving at this conclusion, Navigate to the relevant thread, search the realevant thread with the keywords blurry mms fix, read the postings listed ( all 17 of them ) and derive the answer, no, there is no fix yet.
Fix for this in the themes section by TEAM whiskey its a zip file
Sent from my SGH-T959 using XDA App
los0325 said:
Fix for this in the themes section by TEAM whiskey its a zip file
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
+1
As there are other ways of getting around this, Like replacing the apk's with cyanogen's.
Both of which fix the blurry MMS.
Can you take a pic of the blurry MMS? I am running the same ROM and have yet to see anything blurry about mms. Im really curious what the fuss is.
Are there any HD2 Android roms using Android 2.3 yet?
When people say the dev's here are wizards they mean it metaphorically. They do make wonderful rom's, but can't work on something that isn't released yet.
Uh...it was released on the 11th...
agentfazexx said:
Uh...it was released on the 11th...
Click to expand...
Click to collapse
There's no confirmed release date yet, especially seeing it's not even finished.
Edit: But if you look at Google's tweet a few days ago, maybe Christmas = Gingerdroids?
http://www.physorg.com/news/2010-11-android-gingerbread-days.html
11/11/10 OTA update for Android 2.3. Look at the top of the page.
(PhysOrg.com) -- While Google hasn't made any official announcements on the release date for Android 2.3 several clues online over the weekend point to an imminent release of Gingerbread.
The OS update may be provided to Android developer handsets as early as this Thursday, November 11. Google’s last update to Android was the May release of Android 2.2 (Froyo).
Patience young fandroid........ your gingerbread is in the oven.........
agentfazexx said:
http://www.physorg.com/news/2010-11-android-gingerbread-days.html
11/11/10 OTA update for Android 2.3. Look at the top of the page.
Click to expand...
Click to collapse
But that never happened...
Expected to be released isnt the same as released.
conantroutman said:
Patience young fandroid........ your gingerbread is in the oven.........
Click to expand...
Click to collapse
And if I just happened to actually take ginerbread out of the oven right before reading this hilarious (and ironic) quote?
curiousGeorge said:
And if I just happened to actually take ginerbread out of the oven right before reading this hilarious (and ironic) quote?
Click to expand...
Click to collapse
well, you'll get your hands burnt and get a half baked fr(o)y..o!
curiousGeorge said:
And if I just happened to actually take ginerbread out of the oven right before reading this hilarious (and ironic) quote?
Click to expand...
Click to collapse
pakure said:
well, you'll get your hands burnt and get a half baked fr(o)y..o!
Click to expand...
Click to collapse
lol
Stay out of the kitchen when Granny Google is baking..........
If your lucky you might get to lick the spoon
K well now that I've proven myself to be a total retard, which forum should I keep an eye on for Android 2.3 HD2 ROMS? Link would be most helpful.
agentfazexx said:
K well now that I've proven myself to be a total retard, which forum should I keep an eye on for Android 2.3 HD2 ROMS? Link would be most helpful.
Click to expand...
Click to collapse
Here........
When 2.3 arrives it will be all over the front page, not sure how long it will take the devs to sort out Roms for the HD2 though....... probably not long knowing that lot.........
Has it released the source code for 2.2 yet ?
If not, could you please direct me to where i should be monitoring.
I think i was looking at the right place because it had open source Tar.s and tgiz for t959D but not t959.
No, they have not:
http://opensource.samsung.com/
It will say Froyo when they do, like the canadian Fascinate does.
Since they released 2.2 in US for the Vibrant, they have to release source as per GPL?
mrxela said:
Since they released 2.2 in US for the Vibrant, they have to release source as per GPL?
Click to expand...
Click to collapse
I was thinking the same, but it seems they can stretch it out 6 months before they truly have to release it.
Thanks for the replies guys !!
This thread maybe deleted/locked.
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.