First let me introduce myself. The name is Darcy and I have been casually using linux and other *nix OS for about a decade. I am in school working on a programing degree ATM, and am a pretty quick study. Anyways, I without much research bought my wife a generic 7" tablet running android 1.6. I know what processor it has and Im hoping that leads me to a place to start. Ok so the device is a "Kasser Net'sGo" we didnt realize that its just a china pad with another companys name on it when we ordered it. So most of the apps dont run correctly, and in general the device sucks(on a software level the HW is fine although generic).
Anyways it apears that i can get into recovery mode to flash if i had no other choices. But since there are no official roms im hoping to find a build thats based on the same CPU or similar hardware to find a starting point. Its running the Marvell Aspen 800mhz chip and standard ddr2. Sadly thats all we have been able to find out about this device.
I have compiled custom builds for linux before, and i have now purchased a Gtab so i have a less garbage device to test some things on(i have allready flashed 2 different roms and fooled with a bunch of the settings). But we would realy like to do something with this other tablet. So if anyone can point me in the direction of some info on how to do android builds or a repository of chipset drivers and such that might help me that would be greatly appreciated.
I have a Galaxy S2 which seems to share the same chipset as the GT 7+.
I've just ordered a tab7+ and as there is a massive amount of roms available for the S2, including ICS. Would the binaries for the S2 help make an ICS rom for the GT7+?
Binaries? No - completely different screen, very different peripherals, and no Honeycomb for the Tab 7. Even when both have ICS, they will be very different builds.
Kernel source? Due to being 2.6.36.x, the Honeycomb source base for your kernels has differences from the S2 codebase - so a lot of stuff can't be directly applied, but a competent developer (you have one with garyd9) can apply the "concepts" in many cases.
Unfortunately, Samsung screwed up the wifi driver in the 7 Plus. It's binary-only (no source code) and it seems to have bugs.
Entropy512 said:
Kernel source? Due to being 2.6.36.x, the Honeycomb source base for your kernels has differences from the S2 codebase - so a lot of stuff can't be directly applied, but a competent developer (you have one with garyd9) can apply the "concepts" in many cases.
Click to expand...
Click to collapse
I don't think there are any kernel mods I'd want to bring over from that device. As far as what the OP called "ROMs", I have no idea what they are referring to. There doesn't seem to be any read-only memory in the tablet.
If he meant "firmware", then I have to admit that I'd prefer not to do that kind of thing. There are many different kinds of developers in the world... some get off working at the lowest possible level (kernels, etc) and others prefer higher level things. I'm the former, and it would take the latter to do firmware development.
Gary
Hello, Please all developers, look at these links it says Samsung released the source code for the galaxy tab 7 plus and galaxy tab 10.1.
http://omgdroid.com/tag/samsung-galaxy-tab-7-plus/
https://opensource.samsung.com/reception/receptionSub.do?method=search&searchValue=GT-P6210
http://www.androidpolice.com/2011/1...galaxy-tab-7-0-plus-and-the-galaxy-tab-10-1n/
thank god, i just got this tablet today and imo its software isnt very good. Old release of kernel source is really nothimg to write home about.
Oh wow...dev's is this what you needed? Hope so.
Great post OP...thank you!!
No, unfortunately this is not what the devs need, because devs already have this. This has been out since November 2011 and hasn't been updated ever since I believe because it doesn't support the latest LA3 firmware. The problem is that samsung didn't provide the wifi driver in the source code.
I whis this was something new, but if I'm not mistaken this source code has been out for a wile now and only contains most of the code. But Samsung left out a few peices of the puzzle, mainly the kernel stuff that the devs on this form need to really get going on this tab.
Sent from my GT-P6210 using xda premium
ohhh someone have a look anyways see what you can make from this
ronlsjr said:
Hello, Please all developers, look at these links it says Samsung released the source code for the galaxy tab 7 plus and galaxy tab 10.1.
http://omgdroid.com/tag/samsung-galaxy-tab-7-plus/
https://opensource.samsung.com/reception/receptionSub.do?method=search&searchValue=GT-P6210
http://www.androidpolice.com/2011/1...galaxy-tab-7-0-plus-and-the-galaxy-tab-10-1n/
Click to expand...
Click to collapse
hold on a sec guys i have been told they are new don't ask who by but i thinks we can get exited now yaaaaay......!!!
well I downloaded it, and there is a modified date of 1/14 for the kernel. There is a whole bunch of files for wifi in /drivers/net/wireless/, they are b43 files. Maybe when I go home I will set vmware up on my pc and try to build this, but I will probably play Skyrim instead.
johnwaynegacy said:
well I downloaded it, and there is a modified date of 1/14 for the kernel. There is a whole bunch of files for wifi in /drivers/net/wifi/, they are b43 files. Maybe when I go home I will set vmware up on my pc and try to build this, but I will probably play Skyrim instead.
Click to expand...
Click to collapse
nooo...build it haha do you think its a new update all the devs seem to ignore it thinking its an old one but my friend who developed vegacomb sed its an update to the last with corrections or something haha they are very ignorant on here haha
The linked news articles both date back to November - completely worthless, they're announcing the original source release.
However there are now three source code drops, one of which appears to be China-specific. One of the others might be new source.
As to a bunch of b43 stuff in drivers/net/wireless - not useful. The b43 driver is for Broadcom's recent desktop chips. Useless for mobile devices, even ones with a Broadcom wifi chipset (which the Tab 7 Plus does not even have.)
Now if there's an AR6K driver - that would be interesting.
Also, this doesn't belong in Development, it belongs in General.
there is an ar9k driver, might that be backwards compatible with an ar6k?
Source for this driver lives in the openmoko git http://linuxwireless.org/en/users/Drivers/ar6k. I bet a wifi driver can be made.
Moved to General for you.
johnwaynegacy said:
there is an ar9k driver, might that be backwards compatible with an ar6k?
Source for this driver lives in the openmoko git http://linuxwireless.org/en/users/Drivers/ar6k. I bet a wifi driver can be made.
Click to expand...
Click to collapse
There's an open source driver for PCI/USB AR6k chips - but I'm not sure if an open source driver for mobile AR6k chips exists. (Same idea as the difference between the b43 drivers and the drivers for mobile BCM4329/4330 chips)
Also, mobile wifi drivers almost always have customizations for the host hardware, like mapping the GPIO interrupts correctly - not knowing these device-specific GPIO customizations presents a challenge.
From what I am reading, that is for mobile ar6k chips. Don't get me wrong, I don't know anything about GPIO interrupts or anything like that. "Openmoko™ is a project dedicated to delivering mobile phones with an open source software stack." This is what it says on their website, it also has an image of some android device. "ar6k is the GPL driver for the Atheros AR6000 mobile 802.11bg chipset used on the OpenMoko." is what is says on the on the link I provided to the driver source. I am not a developer. I have written some applications, compiled and modified code, but I am not proficient at it. That being said, to me, all signs are pointing to source for a mobile driver.
Isn't this what we need https://github.com/psyke83/AR6kSDK.3.0 ?
or how about about this https://github.com/psyke83/AR6kSDK.3.1 ?
Some of those might be useful - but won't have device-specific customizations which may prove important.
FWIW, source has NOT been updated since initial release.
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???