Related
Wondering if someone want's to throw up a complete listing of kernels, roms, etc. like all the other Galaxy S variant forums have.
wait.
damn.
nvm.
I really, really miss my Nexus, but at least I have service now.
Daswolven said:
Wondering if someone want's to throw up a complete listing of kernels, roms, etc. like all the other Galaxy S variant forums have.
wait.
damn.
nvm.
I really, really miss my Nexus, but at least I have service now.
Click to expand...
Click to collapse
im not the flaming type....but this is really unnecessary.
wasupwithuman said:
im not the flaming type....but this is really unnecessary.
Click to expand...
Click to collapse
Isn't that like saying "I'm not the racist type, but...."
Of course it's unnecessary. But there's nothing else to do at the moment on here. It's a little frustrating to see the work in the other variant forums, and to hear crickets and hopes in here.
I KNOW incredible people are hard at work right this minute to fix it, but....
It's looking like we will be last to see Voodoo, last to see Froyo, and last to see CM.
I'm not the whining type, but.....
I'm growing restless. lol.
If you're (the general you, not calling anyone out) interested in development, I suggest joining the IRC channel #samsung-fascinate on freenode. This is where you'll get the most up to date information. (For example, we were testing CWM recovery with Koush long before the first post showed up here).
If you'd like a small project to get you in the swing of things, and you're slightly familiar with linux and can get a VM up and running, you could always download the source from Samsung and learn how to compile your own kernel. I've seen a few people in the channel go from knowing pretty much nothing to getting their kernels compiled. Even if you can't get a linux VM up and running, maybe someone in the channel could help you with that.
Obviously thanks to Samsung, the kernel won't boot, but going through the process will help broaden your knowledge and give you some insight into Android and Linux in general. There's plenty to learn, and there's a wide range of people there with varying levels of expertise.
There are a number of us who have been at this since day 1, and since we "know" each other a little better, we often communicate directly between ourselves. If you pop in the IRC channel and don't see anything, don't take that to mean that no work is being done.
There are some major obstacles to be overcome here, and Samsung didn't do us any favors. We're working a number of things right now, getting the kernel source fixed, AOSP, voodoo, etc.. It will take time, but we're getting there.
Daswolven said:
Isn't that like saying "I'm not the racist type, but...."
Of course it's unnecessary. But there's nothing else to do at the moment on here. It's a little frustrating to see the work in the other variant forums, and to hear crickets and hopes in here.
I KNOW incredible people are hard at work right this minute to fix it, but....
It's looking like we will be last to see Voodoo, last to see Froyo, and last to see CM.
I'm not the whining type, but.....
I'm growing restless. lol.
Click to expand...
Click to collapse
if you notice i did not flame you... I could have, but i respect you as a xda member... I just said this was unnecessary, because it is. Like namebrandon said, join the irc channel, but starting a topic like that, then just saying some nonsense, really doesnt need to be done... Your a senior member, we need to be a good influence for the new people. Like i said, i've seen you help out and i respect that; but lets try to keep the Android Development to Android Development. If it's something like this atleast file it in general.
namebrandon said:
If you're (the general you, not calling anyone out) interested in development, I suggest joining the IRC channel #samsung-fascinate on freenode. This is where you'll get the most up to date information. (For example, we were testing CWM recovery with Koush long before the first post showed up here).
If you'd like a small project to get you in the swing of things, and you're slightly familiar with linux and can get a VM up and running, you could always download the source from Samsung and learn how to compile your own kernel. I've seen a few people in the channel go from knowing pretty much nothing to getting their kernels compiled. Even if you can't get a linux VM up and running, maybe someone in the channel could help you with that.
Obviously thanks to Samsung, the kernel won't boot, but going through the process will help broaden your knowledge and give you some insight into Android and Linux in general. There's plenty to learn, and there's a wide range of people there with varying levels of expertise.
There are a number of us who have been at this since day 1, and since we "know" each other a little better, we often communicate directly between ourselves. If you pop in the IRC channel and don't see anything, don't take that to mean that no work is being done.
There are some major obstacles to be overcome here, and Samsung didn't do us any favors. We're working a number of things right now, getting the kernel source fixed, AOSP, voodoo, etc.. It will take time, but we're getting there.
Click to expand...
Click to collapse
I'm one of those people... First kernel i've ever compiled.
and/or you could harass samsung for the kernel signing keys, no coding ability required.
Jesus people. I'll post a ROM if it'll stop all these nonsense threads.
Voodoo kernel is the works also. Coding helps development, not complaining and being sarcastic.
jt1134 said:
Jesus people. I'll post a ROM if it'll stop all these nonsense threads.
Voodoo kernel is the works also. Coding helps development, not complaining and being sarcastic.
Click to expand...
Click to collapse
really?
you have the signing key for the kernel?
signing key? don't need no stinking signing key. bootloader'll boot any (working) kernel I've tried
HUMAN!!!! YEAH!!! U R EVERYWHERE I LOVE IT!!!
Sent from my SCH-I500 using XDA App
All fair enough. I know the work is being done, and my lack of dev skills makes it unfair for me to complain. My due apologies for the thread, I think I'm just going through flash withdrawals.
I'll make up for it in feedback, assisting, and donation when we get rolling.
Sent from my SCH-I500 using XDA App
jt1134 said:
signing key? don't need no stinking signing key. bootloader'll boot any (working) kernel I've tried
Click to expand...
Click to collapse
my bad.
I was misinformed.
http://forum.xda-developers.com/showthread.php?t=796171
ksizzle9 said:
HUMAN!!!! YEAH!!! U R EVERYWHERE I LOVE IT!!!
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
it's wasup_with_u_man....DAMNIT!!!
Yes jt1134, but as your post says, no customer kernel.
Sent from your mom's house via my fascinate.
Not to jack this thread but,....
I LIKE COOKIES!!!
(Will probably make my way onto IRC at some point)
While I suck at Java I debug like kirwoodd's mother in a flea bath.
Daswolven said:
All fair enough. I know the work is being done, and my lack of dev skills makes it unfair for me to complain. My due apologies for the thread, I think I'm just going through flash withdrawals.
I'll make up for it in feedback, assisting, and donation when we get rolling.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I know what you mean about flashing withdrawls...my Droid 1 i would seriously flash on a weekly base...
Terror_1 said:
Not to jack this thread but,....
I LIKE COOKIES!!!
(Will probably make my way onto IRC at some point)
While I suck at Java I debug like kirwoodd's mother in a flea bath.
Click to expand...
Click to collapse
See, now THATS funny.
wasupwithuman said:
I know what you mean about flashing withdrawls...my Droid 1 i would seriously flash on a weekly base...
Click to expand...
Click to collapse
Lol, I had it so bad on my N1 I would test every fourth nightly CM release with four different kernels for performance and battery. I think I had about 200 advanced quadrant screenshots to delete.
Sent from my SCH-I500 using XDA App
So I had always heard that we would see CM development ramp up after the 2.2 source was out. I went over to http://cmsgs.com/mediawiki/index.php?title=Main_Page to see how things were going. This place is almost dead except for git updates and a little irc discussion. I was thinking it may just be because so few of the developers on XDA know about CMSGS. Well its a project to put AOSP builds of cyanogen on SGS phones like the Vibrant. If you dont know about the project head over and stur up some conversation, and maybe some code.
Forum http://cmsgs.com/phpbb/
Twitter http://twitter.com/#!/CMSGSTeam
Wiki http://cmsgs.com/mediawiki/index.php?title=Main_Page
Building for the Vibrant http://cmsgs.com/mediawiki/index.php?title=Build_CyanogenMod_for_Samsung_Vibrant#Setup_Directories
The code https://github.com/cmsgs
On a serious note, I think everybody really does know about Cyanogenmod (CM7) and if they had the capabilities and want to do so, they would be helping. I knew about CM before I discovered XDA. Somebody correct me if I'm wrong, but from my understanding, the reason CM7 is a slow going process right now is that the source to the drivers have not been released... That is unless the latest source release contains those...
ahronzombi said:
So I had always heard that we would see CM development ramp up after the 2.2 source was out. I went over to http://cmsgs.com/mediawiki/index.php?title=Main_Page to see how things were going. This place is almost dead except for git updates and a little irc discussion. I was thinking it may just be because so few of the developers on XDA know about CMSGS. Well its a project to put AOSP builds of cyanogen on SGS phones like the Vibrant. If you dont know about the project head over and stur up some conversation, and maybe some code.
Forum http://cmsgs.com/phpbb/
Twitter http://twitter.com/#!/CMSGSTeam
Wiki http://cmsgs.com/mediawiki/index.php?title=Main_Page
Building for the Vibrant http://cmsgs.com/mediawiki/index.php?title=Build_CyanogenMod_for_Samsung_Vibrant#Setup_Directories
The code https://github.com/cmsgs
Click to expand...
Click to collapse
Do you have a vibrant? Stupid question I know but its confusing when you have Nexus One and G1 on you signature. Anyhow how do you make a signature lol sorry? Well hopefully more people help the dev thats porting CM7.
A good CM6 isn't even out yet. Hence I see the purpose for it since the source code is out. Who cares about some broke ass CM7. We will have to wait months if ever the source code comes out for gingerbread on the vibrant. I see no point trying to port the CM7 to the vibrant at all. I do see a lot of sense to get a nice clean running CM6, hence the post is a good one.
BlackVision said:
A good CM6 isn't even out yet. Hence I see the purpose for it since the source code is out. Who cares about some broke ass CM7. We will have to wait months if ever the source code comes out for gingerbread on the vibrant. I see no point trying to port the CM7 to the vibrant at all. I do see a lot of sense to get a nice clean running CM6, hence the post is a good one.
Click to expand...
Click to collapse
We don't NEED source for CM7. Considering almost no phones have Gingerbread source, they wouldn't even be working on CM7 like they are if this was a deal breaker. You know the saying "don't knock it 'till you've tried it"? Maybe you should adhere to this as CM7 actually runs pretty well on the Vibrant already.
Now, to respond to the OP. I realize a lot of people were expecting some change in development speed for CM7 with the release of source, but there was no reason for this. Nothing has changed or should change. The source we have now is barely applicable if at all to CM7.
Honestly, though, if you look at the list of bugs, it's not that long or severe. The only real non-issue issue is the complicated installation, which they have no reason to improve until they're satisfied with the rom.
MWBehr said:
Honestly, though, if you look at the list of bugs, it's not that long or severe. The only real non-issue issue is the complicated installation, which they have no reason to improve until they're satisfied with the rom.
Click to expand...
Click to collapse
Can you point me in the direction or post a "how to" to the installation of CM7?
kaizasoshi said:
Can you point me in the direction or post a "how to" to the installation of CM7?
Click to expand...
Click to collapse
Go to the i9000 android development forums, it will explain everything.
Sent from my SGH-T959 using XDA App
Or go to the Vibrant General section for some more CM7 info..
@dumdidum on twitter said he ordered a Vibrant so Im sure he will help port it to the Vibrant once he receives it.
they already started adding the vibrant to the source the other day but i been running it fine from the i9000 plus what scrizz said for the modem and a toggle headset widget
BlackVision said:
A good CM6 isn't even out yet. Hence I see the purpose for it since the source code is out. Who cares about some broke ass CM7. We will have to wait months if ever the source code comes out for gingerbread on the vibrant. I see no point trying to port the CM7 to the vibrant at all. I do see a lot of sense to get a nice clean running CM6, hence the post is a good one.
Click to expand...
Click to collapse
I think thats a good place to start, i would prefer CM6over any existing vibrant rom (sorry not a insult to existing roms)
If their were any dev's that really wanted CM on their Vibrant it would have been done by now or there is something that is really holding them back. I don't know why anyone would want to lose functionality for a little extra speed. Side by side CM7 on the Nexus S is almost identical to the Vibrant running BionixV, why would you want to give up video codec's and a better UI for that? I would love to get Bionix V on my Nexus over CM or stock Gingerbread any day.
I use to see Cyanogen as a god of android back when I had the G1. His ROM was the ONLY thing I ever put on my G1.
I know that the Cyanogen team really only does a lot with HTC handsets since HTC is AWESOME with giving out the source to their drivers. And I was so hoping to see it on my Vibrant, but in all honesty I've given up the dream of seeing a stable build for the Vibrant.
Samsung don't play nice like HTC with what sources they release so I know it's tough for CM team go get a 100% stable rom for Vibrant.
The devs we have here that do make roms for our phones are the greatest. Team Whiskey, Team Einherjar, Eugene, Master... They all do such great work and also calaborate and make my Vibrant so awesome and sleek. So honestly I am not holding my breath for a stable and easy to install CM Mod ROM for our phones. Tho I would like to see one, I'm totally happy with the ROMS we do have to pick from..
Anyways, Good luck to all of you devs who are working on porting CM over or working on an actual CM ROM for our phones.
But for now, I'm loving those ROMS we do have.
Ill help as soon as I can get a new motherboard for my pc
Sent from my SGH-T959 using Tapatalk
Im working on building a update.zip from CM source, but i cant promise ill succeed as there isnt a lot of documentation for this device due to the lack of people working on this branch of cyanogen. If i get a flashable update ill post it, maybe that will inspire someone who can actually dev and not just build existing source code.
Okay this is where im stuck, its a documentation issue look at http://cmsgs.com/mediawiki/index.php?title=Build_CyanogenMod_for_Samsung_Vibrant#Configure_Build
when i get to lunch cyanogen_vibrant-eng i get this error
Code:
build/core/product_config.mk:190: *** _nic.PRODUCTS.[[device/samsung/vibrant/full_vibrant.mk]]: "build/target/product/full_base.mk" does not exist. Stop.
** Don't have a product spec for: 'cyanogen_vibrant'
** Do you have the right repo manifest?
Im sure its a simple config fix, if someone can figure this out and update the code or the wiki we may have fixed the one part of the build process that scares devs away. Im too stupid to fix this
Moved of: Samsung Vibrant > Vibrant Android Development
To: Samsung Vibrant > Vibrant Q&A
Please put your questions to: Vibrant Q&A
Ill b up and running soon working on a vibrant specific build once I'm completely done with ToXic 1.0 =3
Sent from my SGH-T959 using Tapatalk
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?
Hi,
I haven't had my A43 for long, but I bought it as a hacking toy rather than a productive tablet, so I've been reading these and other forums with interest. I thought I'd post where I'm at, and I'd really appreciate it if people could correct me if (when!) I make mistakes. Ultimately I'd like to see a really solid and full-functioned Gingerbread ROM for this tablet (and maybe ICS later, I'm not interested in Honeycomb since the source isn't available).
It seems that all of the kernels available for the Gen8 tablets are based on Archos' 2.6.29 - that includes the CM7 port, OpenAOS, UrukDroid etc. My chosen first task is to get a newer kernel up and running. I'm not confident to do that "blind", i.e. by uploading builds through the SDE menu and hoping it does something intelligent! So, I started looking for a serial console, and I'm pretty sure I've found it.
Looking at the rear of the board (i.e. the bit that is at the back of the tablet when it's all closed up), there are two test points. One of them is definitely carrying UART traffic, only problem is that it's at 1.8V logic levels and running at 1.0Mbps. It'll take me a day or two to organise something that will talk with those parameters.
I've already had a setback, I soldered some standard ribbon cable to those test points and when I went to close the tablet, the test points ripped off the board! This led to all manner of trouble trying to connect (thinner) wires to the remaining bits of test point, but I've managed it now. Probably more photos to come.
Is this interesting to anyone? If there's no interest I won't keep spamming the forum with updates
You can take a look here http://dev.openaos.org/wiki/Gen8Resources For other kernels then the 2.6.29.
The guys could use some help , most of the time they can be reached on irc #openaos on freenode
Maurice
RobBrownNZ said:
I haven't had my A43 for long, but I bought it as a hacking toy rather than a productive tablet, so I've been reading these and other forums with interest. I thought I'd post where I'm at, and I'd really appreciate it if people could correct me if (when!) I make mistakes. Ultimately I'd like to see a really solid and full-functioned Gingerbread ROM for this tablet (and maybe ICS later, I'm not interested in Honeycomb since the source isn't available).
Click to expand...
Click to collapse
Welcome to the world of hacking
RobBrownNZ said:
It seems that all of the kernels available for the Gen8 tablets are based on Archos' 2.6.29 - that includes the CM7 port, OpenAOS, UrukDroid etc. My chosen first task is to get a newer kernel up and running. I'm not confident to do that "blind", i.e. by uploading builds through the SDE menu and hoping it does something intelligent! So, I started looking for a serial console, and I'm pretty sure I've found it.
Click to expand...
Click to collapse
Some work had been started to implement the archos patches and use newer kernel version.
Search the web... there's some efforts, especially for the A43.
As divx118 pointed out openaos.org is the best starting point.
RobBrownNZ said:
Looking at the rear of the board (i.e. the bit that is at the back of the tablet when it's all closed up), there are two test points. One of them is definitely carrying UART traffic, only problem is that it's at 1.8V logic levels and running at 1.0Mbps. It'll take me a day or two to organise something that will talk with those parameters.
Click to expand...
Click to collapse
See this post over here for some related info about UART connection on A101:
http://forum.xda-developers.com/showpost.php?p=16923184&postcount=35
BTW, concerning UART testpoints on A43... you got them.
http://www.openaos.org/archives/757
Google might be your friend
RobBrownNZ said:
I've already had a setback, I soldered some standard ribbon cable to those test points and when I went to close the tablet, the test points ripped off the board! This led to all manner of trouble trying to connect (thinner) wires to the remaining bits of test point, but I've managed it now. Probably more photos to come.
Is this interesting to anyone? If there's no interest I won't keep spamming the forum with updates
Click to expand...
Click to collapse
Yeah handle with care... it's good that you managed to solder a new wire.
Try to fix the connection mechanically with some glue.
I can confirm, the testpoints easily rip off
As you see there's interest, keep on posting....
We need more hacks over here.
Best regards,
scholbert
Well, that's a bit embarrassing... openaos.org has a ton of stuff that I hadn't seen before. It'll take me a while to dig through all that
Thanks divx118 and scholbert.
OK, I got up and running. I've got an FT2232H breakout running into a board of my own with 74LVC2T45 level shifters. My boot log is attached.
Termite (http://www.compuphase.com/software_termite.htm) allows arbitrary baud rates and doesn't require editing inf files, which is nice, although it's pretty basic in every other way!
Okey i dont have experience with hardware^^
Could you please tell me what is going on here?
I saw that you wanna get a newer linux kernel as our 2.6.29 but how do you want to get it with hardware modding?..
Lenn said:
I saw that you wanna get a newer linux kernel as our 2.6.29 but how do you want to get it with hardware modding?..
Click to expand...
Click to collapse
Oh, it's quite simple. If the kernel that I'm working on doesn't boot correctly, so that it doesn't start the adb daemon (for USB debugging) or the LCD for displaying messages, then I can't see what's going wrong. And that happens to me a lot!
By having a serial console, I can see the messages from the kernel as it's starting up, without it having to boot and run those other programs.
So "hardware hacking" is probably a bit of a grand title. But "tacking on a serial console" just doesn't have the same ring to it
Thanks for clearing it up for me!
It looks interesting, i will stay tuned
@RobBrownNZ: You can also join us at IRC #openaos on freenode or use the webplugin http://www.openaos.org/chat
Note: that most people are on european time.
Maurice
thanks RobBrownNZ
i have this Archos..
if you want some test, i am here
(i wait all blacks/france...)
cajl said:
(i wait all blacks/france...)
Click to expand...
Click to collapse
Yessss... we don't have the best record against you in World Cups. It'll be interesting to be sure!
I've been looking through so many kernels that it's doing my head in, but I've settled on 2.6.35.7 from arowboat.org. That's a good mainstream choice for Gingerbread, and an older kernel will hopefully have less differences with the 2.6.29 from Archos.
divx118: I'm on IRC, but being in the southern hemisphere, and having 2 young children, is going to prevent me from participating much! Hopefully we'll be able to chat occasionally though.
I had a look at the openAOS resources page. Hidave's and Prahal's kernel work seems to be aimed at Linux more than Android, and I think they're very brave going for version 3+ kernels. Nicktime is doing something similar to me with 2.6.37, and seems to be doing pretty well. I thought about asking him if I could join in, but I want to learn as much as I can from this so I'll battle on alone for now
So I've got comparisons of the .config files from 2.6.29 and 2.6.35 (after I configured 2.6.35 to have "similar" settings to 2.6.29), and the build logs. I'll get the muxes and serial ports fixed up first which should give me something to boot, hopefully that won't take long at all.
RobBrownNZ said:
divx118: I'm on IRC, but being in the southern hemisphere, and having 2 young children, is going to prevent me from participating much! Hopefully we'll be able to chat occasionally though.
Click to expand...
Click to collapse
Sorry didn't look at the nicknames before posting.
And for the family, that is a known issue. It seems only people with little free time want to join development.
Just for your info, if you didn't know. I am working with bubu and illifant on the gingerbread port, but then with the 2.6.29 kernel.
Maurice
This might not be the right place for this, but is anybody working on porting an ICS kernel to the photon? I do not know enough programming to work on a port, but I am looking forward to something happening. The guys over at the Atrix forum are working on a kernel and are getting pretty far quickly. I do know that the Atrix shares some hardware with our Photons, like the GPU, which I have read is one of the biggest drivers that we need to have a proper working ICS or JB port for our phones. Well hopefully this will point some kernel devs to a forum that could have great benefits to the advancement of our phones. Thanks to any devs that may already or decide to work on this kernel.
Edit: Here is a link to their GitHub: https://github.com/CyanogenMod-Atrix/android_kernel_motorola_olympus/
Did everybody abandon us?
Sent from my MB855 using xda app-developers app
Kernel Devs Wanted
I don't think we've been abandoned. I saw that Th3Bill was on Moto's sourceforge trying to get the sources we need, a rep at Moto is trying to help us but they do not have a time frame yet. I also think that once the Atrix kernel is closer to being finished more devs will jump onboard to get the kernel going for our phones. Really I made this thread to get some devs attentions that may have not known about the Atrix development going on. Until then I am trying to learn some C coding and trying to make heads and tails of how the Atrix guys got to where they are. I've only coded in Javascript and for only about 2 years now, so it's kinda slow going, but We Still Have Hope! Also if I can come across a cheap Photon that I can dev on it may help out a bit, I can't really dev on my only phone.
Maybe some useful info.
A PM I got from lehjr over at the Atrix ICS port thread :
"Porting the kernel as it is right now isn't advisable because you may not know if issues are a problem with the hardware being setup slightly differently, or a problem with the kernel itself. We are currently only in a very early alpha stage.
Porting the kernel once it is stable should be much easier, but keep in mind that you will likely have to refer to device-specific references in the GB source to make the required changes, since technical documentation for the Photon and Electrify seems to be very scarce to non-existent, whereas we at least have documented teardowns and a nearly complete schematic for the Atrix as well as a serial out port from the JTAG port. "
I know that this is not new info, but for the programmers that do not know where to start I think this is a step forward in the right direction.
We're getting close. Well the Atrix is getting close.
I keep following the thread over on the Atrix Forums http://forum.xda-developers.com/showthread.php?t=2016837 and it looks like their project has come together. They have marked almost every aspect of their kernel as Completed. If we still have any developers that know how to modify a kernel to port from the Atrix to our Photons it looks like the time is almost here. The one thing they have marked as "work in progress" is the fingerprint reader which we do not need. Well thought I would share the good news with you guys. A fully working ICS would be nice. Cheers!