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.
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.
BETA ICS 4.0.X Brought to you by Team DRH is NOW AVAILABLE ELSEWHERE! (And if you don't know where elsewhere is you don't deserve it )
February 2nd
IceCreamSandwich is now available brought to you by the genius's that make up Team DRH! Due to the Teams wishes no direct links shall be posted so if you want it you will have to do one of the following:
1. Go over to -that other site-, find the Gtab section and the ICS Beta thread and download it, OR
2. wait for it to be officially posted on XDA here (which I have no idea when it will happen.)
and that's all I have to say on the matter. This here post can be found later in the thread but I'm quoting it here as well for convenience:
fosser2 said:
When the beta build gets released to SD please keep direct links off of XDA. I know that its not exactly protocol around here to link to SD but XDA will get the full rom in the development section. SD will have it first.
PS: links are live! you all know where to get it
Click to expand...
Click to collapse
Click to expand...
Click to collapse
January 15th
HAPPY NEW YEAR!
Sorry I haven't updated in a while! been a bit busy but I come bearing wonderful news! in the last 2 months development has shifted entirely from Honeycomb to IceCreamSandwich and rather than the .36 kernel it's being built with the .39 kernel. While this may sound like it would take a lot longer it really isn't due to the source code for ICS being released so the devs don't have to jump through hoops trying to get stuff to work.
The reality of it is that it's a heck of a lot easier to get ICS working than it would be to have continued with HC3.2. and ICS IS working. Fosser2 said that there's a possibility that a public beta build MIGHT be released next week if everything goes well. (so we can cross our fingers and hope). I believe everything BUT the camera is working now so they are likely just polishing some things up and making sure it won't kill out tablets before releasing anything publicly.
Here's a couple videos made by one of the alpha testers to wet your whistles.
ICS on GTab UPDATE!
ICS on gtab with sound!
I'll keep this thread more updated if anything new comes to light
Click to expand...
Click to collapse
Old Updates from Honeycomb
It appears that the folks over at Slatedroid have gotten the the .36 kernel to boot into Linux and Honeycomb 3.2 on our tabs! This is great news cause this will give them the ability to see what they need to change in the kernel to get full Hardware Acceleration!!! For the ones that don't know, the .36 kernel is the magical kernel that gives honeycomb hardware acceleration on our chips. He's a quote from the dev thread:
UPDATE 11/24
So Ch3vr0n5 over at SlateDroid has posted that they are accepting 20 applications for alpha testing the .36 kernel. Space is limited so make sure to read this thread over on SD if you wish to apply
http://www.slatedroid.com/topic/25230-bl-12-26363-development-alpha-testing-112411/
This is what we've been waiting for. alpha means we are getting VERY CLOSE to public release!!
Click to expand...
Click to collapse
Update 11/20/11
Hey, due to BLT24 not having time to keep this thread updated I've taken over. Just keep the same format as it's easier.
Anyways on the newsfront a fellow by the name of dwagner has fixed the long press power button issues so now it does what it's suppose to. One step closer to a public release
Click to expand...
Click to collapse
Update 11/15/11
Im so sorry that I haven't updated for almost a month now. My computer went kaput and I am no longer able to keep up with the updates I am working right now to get this thread handed over to someone else so that it can continue to keep people informed. Again I'm so sorry for the inconvenience, you can head to the last page of this thread to see updates from Pawnty, or you can click the link at the bottom of this post to head over to the original thread
Click to expand...
Click to collapse
Check-in 10/20/11
Well the Dev thread has been very quiet lately. Don't worry though, they are still very hard at work on this kernel. Right now they are working on different hardware drivers and tweaks. Hopefully it will be ready in the next coming weeks! Keep watching! I am still actively following the Dev thread and IRC!
Click to expand...
Click to collapse
Update 10/05/11
We have ALL the nvidia proprietary drivers working in the .36 kernel now. The streak image would have been useful if it had the same accelerometer as we do , but it doesn't.
I'm not sure what sound chip the streak 7 has, but if it was the same as ours it would be useful.
Each manufacturer has the ability to use whatever sensor devices they want. This also changes how they are connected to the tegra2.
Update:
Wake from sleep fixed, I was trying to get the lowest power sleep mode to work, but it seems to be an issue in the bootcode embedded in the tegra2. There is a workaround but the bootloader needs to support it, which is why I was trying the hannspad 1.3 bootloader.
lp1 isn't bad however, my tab slept all night and woke up with a full battery.
There is a really annoying error on the i2c bus at the moment causing the capacitive keys not to work. (really, really annoying)
The heat issue seems to be wifi related, others are not having the same issue.
Once the i2c issue is fixed then most of the kernel issues are done.
Sound is likely a mix of kernel and rom issues.
Click to expand...
Click to collapse
Reminder:
guys, can you make sure people dont use my hannspad kernel on the gtab.
.36 doesn't use the ODM like .32 does, so things like gpios, buses and regulators look a lot more device specific now.
I'm concerned you could do some damage by using it.
obviously happy for you to use the rom, its roughly based on VC9,with some Adam changes and pulls from the a500, but you really need a gtab kernel,to play with it.
I've used some of treznorx changes in my repo, (hell I've even been that lazy i haven't bothered changing his file names yet)so there's obviously shared ground, and I'm happy to pay it back how I can...
it looks like mohan has a pretty solid gtab kernel built now.
have fun ..
Click to expand...
Click to collapse
Update 09/28/11
Yes that is currently how we are testing the kernel by injecting the kernel into the Vegacomb ROM and making a change in init.harmony.rc; however, once we get closer to a polished product we will give tlbardeljr and anyone else who is interested notice so they can starting tinkering away at 3.2 for a future release. We should have an alpha test version out in a week or so but don't hold us to that
Cheers
Also the flashback team have finally responded!! Here is a quote:
"Give it a few weeks when this kernel is complete the Flashback team or other modders will probably make a 3.2 port."
Flashback: We are all ready tabletcraze just have not been posting here because dont want to distract from your work. (awesome job to all of you!)
I do expect there will need to be framework changes. Newbe and the vega guys are digging through these now so a lot have been fixed already.
If there is anything you guys want me to do now just let me know.....otherwise I will go back to staying out of your hair so you can continue the awesome work.
So keep a lookout for a flashback update soon after this kernel releases!!
Click to expand...
Click to collapse
Update 09/26/11
Great work from Kushiels over in the Adam camp getting sound code working well! Actually, great work from everyone who has contributed by way of code,testing,building,gathering info,cheering the devs,etc! The gang on our IRC channel have all done a fabulous job getting everything to where it is today...
I have sound on both speakers...volume buttons fixed...working on volume level and a new sensors library right now....
todo :
wakelocks,
PM,
fix long hold on pwr button,
fix USB so it works without workaround,
fix battery fuel guage,
fix media buffering,
fix mmc so it static maps to avoid SD card issues at boot,
and last but not least the crappy camera...
It will soon be time to get this in the hands of our ROM developers to do preview and perform their magic.
Click to expand...
Click to collapse
Thanks bluecobras09 for the update!
Update 09/22/11
Touch screen is fully functional
Still no sound but they are close!
Click to expand...
Click to collapse
Update 09/21/11
Wifi working
Youtube full HD video working
still no sound
touchscreen wonky but working
Market Working
Seems like we're moving into alpha territory!
Click to expand...
Click to collapse
Update 09/19/11
Honeycomb 3.2 booting to desktop then Freezes
Mouse working
No touchscreen yet
2.6.36 based on Raymans github
Update #2
No more Freeze, stable desktop
Click to expand...
Click to collapse
Update 09/10/11
Ok, I have been gone for a while dealing with stuff but the dev team has been trucking along and we have new contributors. Currently I think we are actually moving to a 2.6.38.3 base instead of 2.6.36.3 because it just likes our tablet much better. Yay! rootfs Ubuntu is booting and touchscreen works with wifi so I feel we are closer to our end goal, booting android and having full HW acceleration. Hope to post a more in depth update later when I get a few minutes to get back into the game. Check page ten (I think) for a youtube video showing Ubuntu running.
YouTube video of xubuntu booting on gtab/.38 kernel HERE!
Click to expand...
Click to collapse
Update 09/08/11
A new .38 kernel was found that plays a lot nicer with our tabs with Linux. We were able to boot Backtrack 5 with it and have working touch screen, WiFi, and even Bluetooth. We are working now to see how it does with android!
Stay tuned, some exciting things are happening!!!
Click to expand...
Click to collapse
Update 09/05/11
"Still working on it. Mayday-Jay has been doing a lot of work on the kernel and he is able to get the Gtab working on the BackTrack5 correctly.
Yesterday, I got a few debug logs from the 4950 and Pershoot's .43 kernel. With those, we think we will be able to bridge the gap and have something that will boot on Android.
The biggest hurdle right now seems to be related to the clocks since the frequencies are different from 2.6.32 and 2.6.36.
If anyone is playing with the kernel and got some debug logs or more information, do not hesitate to send it to us."
"Hi Icewyng,
Thank you.
Sure, please find in attachment dmesgs of stock and kernel from this thread"
We finally got dmesgs!!! Now this thing gets a lot easier!
Click to expand...
Click to collapse
Update 09/02/11
That just means we are working hard... or hardly working...
Still just trying to get things like ADB working. Mayday is about to go on vacation so he will be spending time on the kernel and Icewyng has been working steadily. As for me, I have been busy with some life stuff but I have still been compiling and testing. We are at the point where hopefully one of us will make that "breakthrough" we are all working towards so hold on to your seat... the ride is about to get bumpy.
Cheers =)
Click to expand...
Click to collapse
Update 8/25/2011
We know that we are hanging on init.rc and have a few ideas one how to proceed. Mayday_Jay (Give him and Icewyng a big thank you because they have made this project viable) is working on getting all the developers a proper update.zip that will help those with out a usb to serial converter get some useful debug information.
Don't fret when it takes a couple days for us to update. If you want bleeding edge news, join us on the kernel dev irc channel which is found further on in the thread. We are still working!
Click to expand...
Click to collapse
"PROGRESS!
Just wanted to post an update:
There has been some progress so far. Mayday-Jay has been able to start the kernel in Linux (with Backtrack 5) but the touchscreen was not working. He is trying to compile the Kernel and give Android a shot.
There is still some way to go but I think we can expect the Kernel sooner than later. "
Click to expand...
Click to collapse
I Will update this thread as updates come out there.
If you want to follow the development yourself, you can find it HERE
BLT24 said:
It appears that the folks over at slatedroid have gotten the the .36 kernel to boot into Linux on our tabs! This is great news cause this will give them the ability to see what they need to change in the kernel to get it to boot. For the ones that don't know, the .36 kernel is the magical kernel that gives honeycomb hardware acceleration on our chips. He's a quote from the dev thread:
I Will update this thread as updates come out there.
If you want to follow the development yourself, you can find it HERE
Click to expand...
Click to collapse
Actually, it's not a port of VegaComb 3.2 (Honeycomb 3.2) they are working on as the title suggests.
They are just in the beginning stages of trying to convert the Adam .36 kernel that Rayman did. Rayman had to rewrite various drivers for the Adam hardware (which is similar to, but not the same as ours) to get it working on the Adam. Hopefully they can do the same for ours.
Update 08/25
@aabbondanza
yes you are right atm but none of our honeycomb ports are built to use hardware acceleration(even though they can be changed to do so). So that means our only option for testing is vegacomb. So if they get it to boot vegacomb then that will be our first rom with HW ACC and the others can rewrite their already made honeycomb ports to use the new kernel
BLT24 said:
Update 08/25
@aabbondanza
yes you are right atm but none of our honeycomb ports are built to use hardware acceleration(even though they can be changed to do so). So that means our only option for testing is vegacomb. So if they get it to boot vegacomb then that will be our first rom with HW ACC and the others can rewrite their already made honeycomb ports to use the new kernel
Click to expand...
Click to collapse
Granted, a VegaComb 3.2 port would be great, but, no one has gotten it to work on the gTab and no one has announced that they are working on a VC 3.2 port.
Our current HC roms are operating on .32 kernels that don't fully support HC, while Rayman has created a .36 HC kernel that supports full h/w accelleration on the NI Adam (another close cousin of the gTab as the Vega is).
Even the guys over at Slatedroid who trying to convert the Adam .36 kernel discussed trying to use the Vega release as a starting point but decided that since the Adam kernel now supports full hardware accelleration & that Rayman had offered assistance if needed, that would be easiest route to getting this working on the gTab.
IMO, the first step in achieving full accelleration is going to be switching a .36 kernel. Once we have a working gTab .36 kernel then we should look forward to newer versions of Honeycomb & or Icecream Sandwich.
Yes you are right sorry I guess that I didn't understand your last post lol Thank you for going into more detail
Any updates / progress on this?
mdaddy said:
Any updates / progress on this?
Click to expand...
Click to collapse
I've been following them on their IRC and things look good, they got the usb/serial cable to work last night and today they are working on getting a logcat so they can find out what stopping them. Things are looking really good so hang in there and i'll keep you updated!
BLT24 said:
I've been following them on their IRC and things look good, they got the usb/serial cable to work last night and today they are working on getting a logcat so they can find out what stopping them. Things are looking really good so hang in there and i'll keep you updated!
Click to expand...
Click to collapse
Thank you very much!!
Update 09/02/11
bump!
isn't anyone else excited! ?
hoyitzpnoiboi said:
isn't anyone else excited! ?
Click to expand...
Click to collapse
Title is still kind of misleading. Kernel programming is no simple task. They are at the very beginning stages. I'll be much more excited when they start making progress. Hats off to them though because I surely couldn't do it. At this point they appear to be wavering between continuing to work with the Adam kernel or maybe switching to the Vega one.
Update 09/05/11
BUMP!
i dont plan on retiring my gtab for another 10 years! rooting for yall
Just thought I'd drop by.
A few people had success with getting a working kernel for Backtrack 5 ( I know Mayday-Jay has a config that works great with it) but we still have some way to go to get Android working on 2.6.36 with the Gtab.
If anyone wants to help out, let us know! The more people we have, the better the chances to get this thing on the road quickly!
Update 09/08/11
Update 09/10/11
excited
How do we go about as a community to contribute financially to this team??????
MX Video Player apk v1.3 beta2 Download for Android
Working 720p play videos download in youtube ....
working 720p @ 30fps !! Gtablet android 3.0.1
I should receive my gtablet this week and I'm following this thread daily. Hope they can achive their goals and release a nice kernel.
PS: I thought gtablet was a really famous tablet with lot of improvements thanks to xda users. But it seems that there is not too much development lately... am I wrong?
Gday guys,
I have a question regarding the short term future of the Nook Tablet. Now, Celtic Solutions have finished making CM7 ROM, I am unsure about what happens next.
I have got the latest CM7 Rom installed on my Tablet when it was released in Early April, if i wanted a more recent update version of CM7, what must i do.
I'm just a bit unclear about what is meant to happen next? Apart from CM9.
Is it possible that someone can shead some light on this topic for me.
Cheers Steve
CM7 is complete enough that it can be used quite well as a daily driver. It was never really meant to be an end all be all for the Nook tablet; more of an interim rom until CM9 was complete/stable. A new developer is being brought in for CM9 so stay tuned for development.
I don't really know if there is being much work done on CM7 but like I said, its fairly complete as is. CM9 is as well, with the exception of the proper kernel and subsequently hardware acceleration (netflix, higher end games).
Ah I see, well I can't wait for the full release of cm9 then. I've seen them talking about the cm7.2, does that relate to the 8GB tablet.
I know I'm not meant to ask this but... Have they put a rough ETA on when cm9 will be released? Loads of guys donated to buy some developers a nook tablet, do we can't be far off. What do ya think?
Sent from my Nook Tablet using XDA
There was a misunderstanding about some gpl issues beetween the NT build config and proper source git sync.
All got clear after original_ganjaman spoke with CelticWebSolutions.
So CelticWebSolutions when find some time may update CM7.
Theres never an ETA.
I'm so happy with CM7 I'm not even looking anymore
steveflack said:
Ah I see, well I can't wait for the full release of cm9 then. I've seen them talking about the cm7.2, does that relate to the 8GB tablet.
I know I'm not meant to ask this but... Have they put a rough ETA on when cm9 will be released? Loads of guys donated to buy some developers a nook tablet, do we can't be far off. What do ya think?
Sent from my Nook Tablet using XDA
Click to expand...
Click to collapse
Can't you just play with some themes for CM7 and make it look like ICS?
There is no such thing as ETA on things like these.
(Off topic- I understand why captcha is used, heck I use it on my own websites, but this one in particular is really annoying).
JRam13 said:
Can't you just play with some themes for CM7 and make it look like ICS?
Click to expand...
Click to collapse
did you do look over this post ?
http://forum.xda-developers.com/showthread.php?t=1512373
JRam13 said:
(Off topic- I understand why captcha is used, heck I use it on my own websites, but this one in particular is really annoying).
Click to expand...
Click to collapse
agreed and it goes away after ten ?
steveflack said:
Ah I see, well I can't wait for the full release of cm9 then. I've seen them talking about the cm7.2, does that relate to the 8GB tablet.
I know I'm not meant to ask this but... Have they put a rough ETA on when cm9 will be released? Loads of guys donated to buy some developers a nook tablet, do we can't be far off. What do ya think?
Sent from my Nook Tablet using XDA
Click to expand...
Click to collapse
Is there something wrong with the 7.2 build you have now? CyanogenMod's 7.2 branch is the latest release, their fixes are mostly bugfixes related to specific devices now, since they've moved most of their development to the CM9 devices.
As said previously, there is no ETA for cm9. When they get the kernel working, when they finish their respective tweaks, it'll be done. If you have any programming knowledge, they're actively looking for new members to help with the work though!
Hi all,
I am noob at XDA. (About myself: I am a software engineer aged 30. I have been hacking computers since I was 10.)
I am here because I am planning to buy a new Android device soon. (And unless something really revolutionary happens, I don't plan to upgrade it in the next 2 years or so, so it's a long-term decision.)
My short-list is:
- HTC One S
- Sony Xperia S
or, if everything else fails:
- Samsung Galaxy Nexus
The hardware of the One S and the Xperia S is obviously more powerful than the Galaxy Nexus; my only concern is the software side of things.
The thing is, I really don't like the customization the hardware vendors do with the software, so I want to run raw vanilla AOSP, or something very close to it.
(CM definitely qualifies.)
Also, I am sick of waiting for ages for new android versions to be ported to my device.
Obviously, Galaxy Nexus is guaranteed to be get Android upgrades first, so that's a safe choice in this respect, but since I like the hardware of Xperia S (and One S) so much, I would like to gain a better understanding the software situation of them, so I can make an informed decision about my purchase.
I am aware of the fact that Sony is actively supporting the Free Xperia Team, which is bringing CM9 to Nozomi (among other devices), but I have no information about the details of the project, or it's limitations.
So, my questions are the following:
1. What is the exact nature of the support Sony is providing to the FXP team? (HW? HW docs? Binary drivers? Driver source? Consultation?) Has this changed in any way, now that Sony Ericsson has become Sony? Was this a one-time action, or have they made any commitment about the future?
2. What does one need to build a vanilla android ROM for the S, using the AOSP sources? (Let's forget Cyanogenmod for now.) What is the status of the required device drivers?
3. What are the current obstacles, hindering the release of CM9 (or any other derivative of AOSP) for this device? As far as I know, Nozomi was released in 2012.02, ~4 months ago. ICS was released in 2011.10, ~8 months ago. Official ICS (Sony's version, with Timescape) is rolling out about now; CM9 is not yet released. I wonder what is taking so long?
(Please understand that I really, literally wonder: I am not demanding anything, and I am not trying to offend or accuse anyone; I am totally aware that I don't understand the process; I would like to have more information to understand what needs to be done. And since I am software engineer, and I am not afraid of getting my hand dirty, so eventually, I might end up helping with it...)
4. Do we have any information about Sony's plan for this device beyond ICS? Jelly Bean is coming up soon. Regardless of Sony's decision, when JB is released, I would like to run it on my device, as soon as possible. What are our prospects for porting JB to Nozomi? Is Sony going to help with porting the device drivers to the new kernel, is something like that would come up?
* * *
Thank you for explaining this:
Csillag
1) No one knows for sure, but I'm pretty sure that it's not game changing, judging by the progress me and Doomlord made on AOKP without any help from Sony (obviously).
2) You can try building Gingerbread, but no one cares, right? For ICS, see the next answer.
3) The most important problem is that we don't have the drivers/kernel sources, and there's not much motivation for building it from scratch considering the soon(ish) ICS release. There are leaks with files for so called 'brown' or developer devices, but they also don't give much because of different low-level software. So the state of things is that almost everything but wireless is working, but wireless doesn't work at all. That means data, calls and WiFi.
4) JellyBean will likely be a minor upgrade (4.1 that is) and there's nothing stopping Sony from releasing anything on the 4.x branch. When 5.0 comes, it will depend on the hardware requirements but I'd guess we're getting it too.
K900 said:
1) No one knows for sure,
Click to expand...
Click to collapse
How is that possible?
The FXP guys (bin4ry, jerpelea, etc) are here on these forums...
... did they have to swear secrecy, even about the circumstances?
but I'm pretty sure that it's not game changing, judging by the progress me and Doomlord made on AOKP without any help from Sony (obviously).
2) You can try building Gingerbread, but no one cares, right? For ICS, see the next answer.
3) The most important problem is that we don't have the drivers/kernel sources,
Click to expand...
Click to collapse
You mean we don't have the kernel sources for ICS, right? Because for GB, we do have something, in this thread... I guess I should ask this in the relevant thread, but has anybody determined the exact differences between this source and the stock ( 2.6.35 ? ) kernel this is based on? How many non-standard drivers are there? Do they come from Sony directly, or do they come from 3rd parties? I will need to look into this...
and there's not much motivation for building it from scratch considering the soon(ish) ICS release.
Click to expand...
Click to collapse
And according to past experience, how long does it take Sony to release the kernel for ICS, after the imminent official ICS release?
There are leaks with files for so called 'brown' or developer devices, but they also don't give much because of different low-level software. So the state of things is that almost everything but wireless is working, but wireless doesn't work at all. That means data, calls and WiFi.
4) JellyBean will likely be a minor upgrade (4.1 that is) and there's nothing stopping Sony from releasing anything on the 4.x branch. When 5.0 comes, it will depend on the hardware requirements but I'd guess we're getting it too.
Click to expand...
Click to collapse
OK, that part sound good.
* * *
Thank you for explaining:
Csillag
csillag said:
How is that possible?
The FXP guys (bin4ry, jerpelea, etc) are here on these forums...
... did they have to swear secrecy, even about the circumstances?
Click to expand...
Click to collapse
I haven't seen them tell anyone, and I've never seen them do anything that's not available for everyone else (thankfully).
csillag said:
You mean we don't have the kernel sources for ICS, right? Because for GB, we do have something, in this thread... I guess I should ask this in the relevant thread, but has anybody determined the exact differences between this source and the stock ( 2.6.35 ? ) kernel this is based on? How many non-standard drivers are there? Do they come from Sony directly, or do they come from 3rd parties? I will need to look into this...
Click to expand...
Click to collapse
There are kernel sources for GB, the same ones from which the stock kernel was built. If you mean the upstream Linux kernel, it'll be a huge diff that's not so easy to port without datasheets (which we don't have) and actual understanding of how the hardware works. Speaking of drivers, I'm pretty sure you misunderstand the way Linux / Android 'drivers' work. Kernel-space drivers (modules) and userspace drivers (libraries and daemons) are two different things. They have to open source their kernels because Linus's tree ('official' Linux) is GPL, but the userspace parts are proprietary. ICS also brought many ABI changes, so just taking old libs and placing them in a new ROM often doesn't suffice.
csillag said:
And according to past experience, how long does it take Sony to release the kernel for ICS, after the imminent official ICS release?
Click to expand...
Click to collapse
It takes time, can't say how long really, but it shouldn't take too long because they know we want those sources.
K900 said:
I haven't seen them tell anyone, and I've never seen them do anything that's not available for everyone else (thankfully).
Click to expand...
Click to collapse
Have you seen them being explicitly asked about this?
(Because not saying anything because not being asked is completely different that refusing to reveal this info....)
There are kernel sources for GB, the same ones from which the stock kernel was built. If you mean the upstream Linux kernel,
Click to expand...
Click to collapse
Yes, that was what I have meant when I wrote "stock". Now I see that it was ambiguous wording...
it'll be a huge diff
Click to expand...
Click to collapse
That's sad.
I was hoping for finding only some added drivers, plus some small configuration changes elsewhere.
that's not so easy to port without datasheets
Click to expand...
Click to collapse
obviously
(which we don't have)
Click to expand...
Click to collapse
We don't have it, but the "official" FreeXperia team might, or they might be able to ask for it. This is exactly the kind of information I am trying to find about their collaboration with Sony...
and actual understanding of how the hardware works. Speaking of drivers, I'm pretty sure you misunderstand the way Linux / Android 'drivers' work.
Click to expand...
Click to collapse
No, actually I get that part. (I am exclusively using Linux for about 13 years now, and I have also done some kernel hacks earlier.) But maybe my wording was ambiguous again...
Kernel-space drivers (modules) and userspace drivers (libraries and daemons) are two different things. They have to open source their kernels because Linus's tree ('official' Linux) is GPL,
Click to expand...
Click to collapse
Well, that does not stop some vendors (like NVidia) to ship binary kernel modules, so I would not be too surprised to find even binary kernel modules bundled with the code. But if they are open source, that that's great.
but the userspace parts are proprietary.
Click to expand...
Click to collapse
I did not know the devices require userspace parts. I was assuming that the kernel modules implement standard linux device interfaces; for example cameras are simply accessible via v4l[2], the modem is a character device, etc...
...so you say this is not the situation, and besides the kernel modules, they require custom user-space parts for operation, right?
ICS also brought many ABI changes, so just taking old libs and placing them in a new ROM often doesn't suffice.
Click to expand...
Click to collapse
Yes, that part is clean.
It takes time, can't say how long really, but it shouldn't take too long because they know we want those sources.
Click to expand...
Click to collapse
So, you say that it's a totally possible situation that we need to wait for several further months until we can get access to the kernel sources, and build proper CM9, right?
Unfortunately, this is exactly what I would like to avoid.
Maybe I should just stick to Galaxy Nexus, in spite of the older hardware...
Thank you for explaining:
Csillag
csillag said:
Have you seen them being explicitly asked about this?
(Because not saying anything because not being asked is completely different that refusing to reveal this info....)
Click to expand...
Click to collapse
They tend to ignore such questions. PM me if you want my personal opinion, I'll try to stick to the facts here.
csillag said:
Yes, that was what I have meant when I wrote "stock". Now I see that it was ambiguous wording...
Click to expand...
Click to collapse
Nevermind.
csillag said:
That's sad.
I was hoping for finding only some added drivers, plus some small configuration changes elsewhere.
Click to expand...
Click to collapse
They add some stuff, but they also change stuff internally. Tweaks and patches and many different things to get the best performance on this specific board. CAF has a generic msm-3.0 kernel, but that's not as customized. And we're not really waiting for the kernelspace here.
csillag said:
We don't have it, but the "official" FreeXperia team might, or they might be able to ask for it. This is exactly the kind of information I am trying to find about their collaboration with Sony...
Click to expand...
Click to collapse
Such things are very, very strongly NDA protected. That's Qualcomm's secret sauce, and it wouldn't be secret any more if they gave datasheets to the community.
csillag said:
No, actually I get that part. (I am exclusively using Linux for about 13 years now, and I have also done some kernel hacks earlier.) But maybe my wording was ambiguous again...
Click to expand...
Click to collapse
Nevermind
csillag said:
Well, that does not stop some vendors (like NVidia) to ship binary kernel modules, so I would not be too surprised to find even binary kernel modules bundled with the code. But if they are open source, that that's great.
Click to expand...
Click to collapse
Actually what NVIDIA does is ship a GPL'ed kernel module whose only function is to set up an interface through which the userspace (libGL) can talk to the hardware. So their kernel module is open source, but all the magic happens in the proprietary userspace.
csillag said:
I did not know the devices require userspace parts. I was assuming that the kernel modules implement standard linux device interfaces; for example cameras are simply accessible via v4l[2], the modem is a character device, etc...
...so you say this is not the situation, and besides the kernel modules, they require custom user-space parts for operation, right?
Click to expand...
Click to collapse
Android has a HAL of its own, so mostly it's about HAL modules, libGL and libril (Radio Interface Layer) to talk to the modem. And here is where many hardware vendors pull an NVIDIA.
csillag said:
So, you say that it's a totally possible situation that we need to wait for several further months until we can get access to the kernel sources, and build proper CM9, right?
Click to expand...
Click to collapse
No, the kernel isn't that much of a problem. If we have to wait for too long, we'll just take CodeAurora msm-3.0 and port it which shouldn't be too hard cause it's as generic as possible.
csillag said:
Maybe I should just stick to Galaxy Nexus, in spite of the older hardware...
Click to expand...
Click to collapse
If you want AOSP now, you should go with the GNex. But the XPS is a nice phone, and the prospects with AOSP are good. Also would be nice to have someone more experienced with Linux (I'm just a student here) on the team/forums. If you get the XPS, PM me or Doomlord and I hope you'll help get AOKP running
Today XDA's Aamir Siddiqui posted an Article on how Poco, even though they promised to do so, still haven't released the Kernel Source for our Poco X3 yet.
So far the Developers are doing an amazing Job in providing us Users with already very well working Custom ROM Options.
But, of course, complete sources, as promised, would be very welcome.
A couple of guys have already tweeted at Poco quoting the following Article.
Maybe we could boost that message a little, to speed up that process to get the Sources.
Of course I don't really mean that we should annoy the shi* out of them or be rude, but maybe a little reminder, from their users, might help.
Tweet: https://twitter.com/xdadevelopers/status/1327165355979059200
I for one, fully agree. Sadly, though, I'm not on Twitter. :good:
Another appropriate venue for this gentle pressure would be the official forum at https://c.mi.com/forum-2861-1.html.
Can you document other Twitter posts here? They would come handy as templates and indicators...
.
Gizchina now posted an article about it as well.
https://www.gizchina.com/2020/11/13...ot-available-despite-launch-days-promise/amp/
Do you guys really believed that a company that makes you wait one week to unlock the bootloader will give you the kernel source right away?
I don't go by what I believe, I go by what they said.
That being said. No, I don't believe that.
Sill, it doesn't hurt to ask and remind them again. Worst case, nothing happens, best case, it helped a little.
editheraven said:
Do you guys really believed that a company that makes you wait one week to unlock the bootloader will give you the kernel source right away?
Click to expand...
Click to collapse
They did so before, dunno what's keeping them from doing it now.
Maybe because of Dynamic Partitions?
Dynamic Partitions
Ezzady said:
Maybe because of Dynamic Partitions?
Dynamic Partitions
Click to expand...
Click to collapse
Why is dynamic partitions stopping them from sharing source?
Google shared the kernel source for pixel 4a and 5 already
Kernel released, guys.
https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/surya-q-oss
Looks like we have annoyed them enough and they finally released it, thank god
Maybe. ?
Not sure if there is a correlation, but I'm sure it definitely didn't hurt. I'm just glad we have them now.