You can get it from here:
http://android.git.kernel.org/?p=ke...;hb=refs/heads/android-tegra-2.6.36-honeycomb
This is thanks to Koush, who posted it here:
http://www.koushikdutta.com/2011/02/motorola-xoom-rooted.html
One thing to note though, is that he said this:
"Unfortunately the kernel was not available in the Android repositories. At first, I tried using the Harmony kernel, since they are both tegra 2 250 chips. That turned out to be major fail. As soon as I was about to give up, I noticed that AOSP had updated their tegra kernel repository with some new tasty branches for stingray. Kudos to these guys for being so on the ball! I was able to compile that up and get a working recovery to obtain root, and then get Superuser on the device."
I'm sure someone tried the same thing, and the harmony kernel didn't work on our Vega tablets, either. Hopefully this should work with little changes to implement.
But, it saves us having to wait for Advent to try and create a honeycomb rom in the future.
EDIT: Here's a changelog for the kernel source too.
http://android.git.kernel.org/?p=kernel/te...id-tegra-2.6.36
Good luck!
Anymore news on this or if anyone else is looking to port honeycomb to the vega?
Work is not being done at the moment as far as I know, for 2 reasons
Google AOSP has not released sources for Honeycomb yet
And its likely that a lot of backporting will need to take place for it to work on the vega (this will be assisted if the vega or a clone get an official honeycomb rom soon). Backporting is hard work and can take a lot of time.
It is likely we will see Honeycomb, but don't expect anything soon.
I must say I rather thought the AOSP would have been released by now. I wonder what the hold up is....
I purchased a Sprint Galaxy Tab to give myself an opportunity to get acquainted with Android (it came with ver 2.2 Froyo). After two months reading the xda threads I have basically learned that Android isn't just a few variations (Froyo, Gingerbread, Honeycomb, etc.) - but rather each device has its own flavor of Android within those larger general classes. Different ROMs, different kernels, different application compatibilities, etc.
This surely isn't good for Google and/or Android in the marketplace.
This has come to light most vividly while trying to get my Netflix subscription to work on my Samsung Galaxy Tab. Netflix promotes that they support "Android devices" which technically may be true. I suspect there are at least a handful of Android devices supported. Sadly my Galaxy Tab is not among the selected few. And based on the extremely long threads on this subject with such a wide variety of proposed possible solutions, it is not isolated to the Galaxy Tab. This should not be such a big deal. And yes, I realize it is likely the fault of Netflix themselves trying to be the DRM cops that complicate this issue. But dang - how hard can it be???
I've got to ask why? How is it that this same Galaxy Tab can display video from a variety of sources, but not Netflix? And why are there so many 'apps' that will not run on similar (but not identical) Android platforms?
Sorry for venting a bit. But dang....
It would be nice if phone hardware had more of a PC architecture so when a new version of Android was released by google, you could just go and download it, possibly with a Google installer that would auto detect drivers and such. But that's just a dream.
avrillapete said:
... with a Google installer that would auto detect drivers and such. But that's just a dream.
Click to expand...
Click to collapse
20 years ago it would have been a dream. But today? And a company as agressive as Google? WHY would it still be just a dream?
Google says they want to set an open source 'standard' and I think that is commendable. But it feels like the whole process of implementing and supporting the Android OS is stuck in the '80s - with the same problems and limitations that plagued the early CPM and MSDOS world. Surely Google has resources and smarts enough to do better!
Mostly I am surprised and disappointed that Google hasn't done a better job with this aspect of Android. Surely it will get better...
Google has acknowledged this issue, and it WILL get better. Android 4.0 (Ice Cream Sandwich) will have even less fragmentation than honeycomb, and be on ALL devices from its release onward. many pre-existing devices will be upgraded to it as well, ending, for the most part, all android fragmentation.
Is anyone interested in porting lollipop to this device from the i900
http://forum.xda-developers.com/galaxy-s-i9000/i9000-development/rom-t3054101
sleimoha said:
Is anyone interested in porting lollipop...
Click to expand...
Click to collapse
I appreciate your enthusiasm for this device. Unfortunately, there is no meaningful open-source kernel support for Samsung devices. While we were able to get the SGS 4G running reasonably stably for KitKat, taking it to Lollipop would be a far stretch. This is not the same device as the Galaxy S (I9000), no matter the external similarities.
Mine is limping along on OmniROM 4.4.4 as a spare phone for my foreign SIM, but it takes a few minutes to boot. I can't imagine taking the time to develop and build the kernel drivers required for Lollipop.
I'd suggest continuing to run one of the ROMs available in this forum, or purchasing a more contemporary phone if you want to run Lollipop.
I'd love to see Lollipop be ported to this device, which I have. However, I have moved on, and now have 2 devices running Lollipop, if you look at my signature.
It's not an impossible feat, it's a matter of resources and time. Some debug tools like a riff box or other jtag. And time that, for me at least, is pretty busy with work and other projects.
The biggest problems of any sgs port is the lack of internal storage and slow mmc (so moving data to mmc is bad) and the ST-Ericsson radio. Also, the internal onenand flash is bigger then the other sgs devices so you have to update the flash layout.
The kernel on my github has either a gpio issue or wake-lock unbalance. So if the screen turns off, the phone basically doesn't wake up.
Without some serious work done to the kernel, and someone's time, I don't for see lollipop on the sgs4g.
Sent from my Nexus 5 using Tapatalk
Aquí estamos presentes ...
Use case
Ignoring free hardware for a moment, I'm looking for a phone (for daily use) where I can build almost all of the firmware/software (no binary blobs apart from the baseband firmware) running on (at least) the main processor from source. My interest lies heavily on the driver side of things.
Devices considered
Apart from the GTA04 (no BLE) and Neo900 (early prototype phase), Samsung's Z1/2/3 devices seem most promising. (If I missed anything that can be used on a daily basis, please correct me.) I have a Samsung Galaxy S4 (i9505), but have only seen old blog posts about Tizen having been spotted running on it.
Questions
Has anyone looked at the source code provided for these devices and determined how much of a workable image can be built from it?
Samsung's source releases:
Z1: opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=z1
Z2: opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=z200
Z3: opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=z300
The ideal resource would be something like the page for the Sunxi (wiki.tizen.org/wiki/Sunxi)
Thank you.
I've been under the impression that the Relay wasn't about to get Nougat support, because it's graphics chip was too old to do Vulkan. However these two sites indicate that Relay support is in the works. http://www.gizmoadvices.com/list-devices-supported-official-lineage-os/ http://lineageosdownload.com/devices-supported-by-lineage-os/
I'd not be prone to trust that, since they seem to essentially be the same list. (echo-chamber?) However this site http://www.theandroidsoul.com/download-lineage-os/ with download links shows some supported Samsung devices of similar vintage to the Relay, perhaps even older.
I plan to look into this more, but in the meantime, does anyone else know anything?
I also plan to upload my Dec 3 and Dec 29 images from last year to my google drive, and will make those known here, once I have. They're not fully tested - I did a bit more explicit testing of the Dec 3 image, but I'm currently running the Dec 29 image.
Edit - some content:
https://drive.google.com/open?id=0B_MKeoY9qBceVGlWV05fUlVObUU
https://drive.google.com/open?id=0B_MKeoY9qBceRDd5elpZbFZETVk
https://drive.google.com/open?id=0B_MKeoY9qBcecmxBR2xzV2N2cTQ
https://drive.google.com/open?id=0B_MKeoY9qBceVWJQSEUwaXpiNFk
(I fear I've lost track of which is which, but two are zips and two are checksums. Two are Dec 4 and two are Dec 29.)
Nice one! i've been running my relay on the stock OS for years. It's running slow as a dog. I really need to learn how to flash it with a nice new ROM.
That would be awesome if the Relay would get a second life.... i'm sooo close to drop it and buy the Nokia 6... hope HMD is living up to some customers expectations and is building a new communicator... love my old buddy E7.
---------- Post added at 06:26 PM ---------- Previous post was at 06:22 PM ----------
by the way, the Relay is in basic the S III. But I'm quite astonished that they support the Relay ()
SinnedNima said:
That would be awesome if the Relay would get a second life.... i'm sooo close to drop it and buy the Nokia 6... hope HMD is living up to some customers expectations and is building a new communicator... love my old buddy E7.
---------- Post added at 06:26 PM ---------- Previous post was at 06:22 PM ----------
by the way, the Relay is in basic the S III. But I'm quite astonished that they support the Relay ()
Click to expand...
Click to collapse
By "E7" you mean the Nokia E7, right? Oh, I have often fantasized about a device in an E7 chassis but with new internals and running Android... except for the weight, that was my favourite form factor ever, keyboard or not
---------- Post added at 07:41 PM ---------- Previous post was at 07:38 PM ----------
BTW since my Relay is definitely not my daily driver, more than happy to give these builds a whirl...
so will there bea linage os for the relay 4g. if so I would be interested for afriend of mine . he loves the relay and so he is wondering if there will be development for linage for the relay 4g. please let me know.
I'm updating here the last CM recovery in case someone needs it.
mrk2815 said:
so will there bea linage os for the relay 4g. if so I would be interested for afriend of mine . he loves the relay and so he is wondering if there will be development for linage for the relay 4g. please let me know.
Click to expand...
Click to collapse
The leaks of the soon to be supported devices have the Relay on it. I can't believe it yet but why not? The Relay is the last Android QWERTY with decent hardware. As i stated before in another thread the S III is nearly identical to the Relay and the SoC is/was quite popular and built in many devices. The chances are high (to good to be true)
SinnedNima said:
The leaks of the soon to be supported devices have the Relay on it. I can't believe it yet but why not? The Relay is the last Android QWERTY with decent hardware. As i stated before in another thread the S III is nearly identical to the Relay and the SoC is/was quite popular and built in many devices. The chances are high (to good to be true)
Click to expand...
Click to collapse
I've done a bit of looking since, and see that Lineage OS is advertising both Marshmallow and Nougat support. I suspect that means that the Relay is going to get Marshmallow, not Nougat. My impression is that Nougat required Vulkan graphics, and the Relay's graphics chip wasn't capable of that. Still, Marshmallow will be newer and presumably more secure than KitKat.
phred14 said:
I've done a bit of looking since, and see that Lineage OS is advertising both Marshmallow and Nougat support. I suspect that means that the Relay is going to get Marshmallow, not Nougat. My impression is that Nougat required Vulkan graphics, and the Relay's graphics chip wasn't capable of that. Still, Marshmallow will be newer and presumably more secure than KitKat.
Click to expand...
Click to collapse
Even Marshmallow would be a welcome advance for the Relay venerable Relay.
I love my Relay so much that I want it keep it forever.
I bought a couple of extras, so I have some hardware for testing and I am eager to assist anyone who wishes to continue development for the Relay.
Please contact me if I can assist you and/or please direct me to someone whom I can assist.
thanks in advance,
- Soul Singin'
LineageOS released their list of officially supported devices and the Relay is not on it. I jumped onto the Lineage OS IRC channel to ask the devs what exactly they'd need to get the Relay officially supported. They said they need a working device tree + kernel. I emailed them the info they asked for and will let you guys know how it goes.
My Relay is my daily driver running CM11 and an more up to date rom would be amazing.
check out the development area here at xda, i'm sure there was a kernel over there. i do think that for someone like reventech from the validus project that task would be easy as a pie. don't they have the sources of cyanogenmod? the mirrors are down am i right? on that github should have been the source. i'm not able to build android yet. as an administrator my free time is quite limited
gerbilfat said:
LineageOS released their list of officially supported devices and the Relay is not on it. I jumped onto the Lineage OS IRC channel to ask the devs what exactly they'd need to get the Relay officially supported. They said they need a working device tree + kernel. I emailed them the info they asked for and will let you guys know how it goes.
My Relay is my daily driver running CM11 and an more up to date rom would be amazing.
Click to expand...
Click to collapse
Would you be willing to send me the device tree, as well. Or perhaps since I have the sources sitting around, I presume there's a device tree there. I've read about the device tree on Phoronix, but have never really walked through one.
Also, since I've got a source tree, I've also got a kernel in there. However will Marshmallow use the same kernel as KitKat? Oh, google was my friend: https://android.stackexchange.com/questions/51651/which-android-runs-which-linux-kernel
Android Version |API Level |Linux Kernel in AOSP
----------------------------------------------------
1.5 Cupcake |3 |2.6.27
1.6 Donut |4 |2.6.29
2.0/1 Eclair |5-7 |2.6.29
2.2.x Froyo |8 |2.6.32
2.3.x Gingerbread |9, 10 |2.6.35
3.x.x Honeycomb |11-13 |2.6.36
4.0.x Ice Cream San|14, 15 |3.0.1
4.1.x Jelly Bean |16 |3.0.31
4.2.x Jelly Bean |17 |3.4.0
4.3 Jelly Bean |18 |3.4.39
4.4 Kit Kat |19, 20 |3.10
5.x Lollipop |21, 22 |3.16.1
6.0 Marshmallow |23 |3.18.10
7.0 Nougat |24 |4.4.1
7.1 Nougat |25 |4.4.1 (To be updated)
So the problem is that we need a new kernel, and need to map the old config to the new. OK, I always save my kernel configs, and one of my home machines goes clear back to 3.7 and up to the present, except that while I have configs for 3.16 and 3.20, I'm missing everything in between. Another system has five different 3.18 kernel configs, but only goes back to 3.16.3. I know these configs are not usable for Android, but I'm hoping they can give me an indication of what changed between the relevant levels. Scratch that, one the first machine mentioned, I have a 3.18.8 kernel config laying around as well as 3.10.0, 3.10.9, and 3.10.10 configs. Sadly, there are 1570 lines of diff between the two. Haven't looked at any details yet.
This looks like a bit of a chicken-and-egg problem. I'm going to presume that I can't just stuff a 3.18.10 kernel into my CM11 build and expect it to work - though that's the way Linus would like it to be, and the two kernels aren't that far apart.
Pardon the rambling.
EDIT: I just checked my source tree, and I appear to have the kernel source there. Actually there seem to be two sources, "samsung/d2" and "samsung/t1". Neither appears to have been compiled, because I only see .c and .h files in there, nor is there a .config file. Luckily I just checked my Relay, and found "/proc/config.gz". Oh, and here's the other oddity: "uname -a" returns "3.4.104-cyanogenmod-g61tc527e", not the expected 3.10. I may have to grab a Validus image, if I can still find one.
phred14 said:
So the problem is that we need a new kernel, and need to map the old config to the new. OK, I always save my kernel configs,
Click to expand...
Click to collapse
Attached is my: /cm_repo/kernel/samsung/d2/arch/arm/configs/cyanogen_apexq_defconfig for CM 11, which uses kernel 3.4.95 and android 4.4.4
Does this help? If so or if not, please tell me how I can help.
And thank you for your help!
- Soul Singin'
would to know how it goes as well, any updates?
from what i've been told they have no plans for it either
https://www.facebook.com/LineageAndroid/posts/1499401083412550?comment_id=1499658536720138
any new news on any development for this device. i know that the s3 has gotten its linage os 14.1 rom and how come the relay whihc is based off of the s3 cant get a 14.1 rom. just wondering.
I know everyone hates a 'me too'. I have been a T699 user for about as long as it's been introduced. I also use a Stratosphere II and a Galaxy S5, but my Relay is still my favorite. I hope the developers at LineageOS will still consider supporting this phone. Thanks in advance.
Even though it's not my main phone anymore, I love pulling out my Relay now and then. In fact I'm using it as a music & podcast player since the SD card reader in my main phone died. The only thing that stops me from using it more is that the battery drops like a stone when it's got cellular signal/data going, to the point that it almost unusable day-to-day as a connected device. But it's got great standby life so I'm pretty sure it's the OS, not the battery. I would love it if a new OS actually fixed the battery drain...
It would be a dream to geht lineage OS in the relay 4g. Any advance Herr???