Until recently while reading the cyanogenmod thread, I had never figured out how to use github to find nightlies changelog, to weigh the pros and cons of flashing. I have been checking these sites pretty often and here are the changelogs:
Gingerbread
Simplified version http://cm-nightlies.appspot.com/?device=epicmtd
changelog working again
Github Version http://review.cyanogenmod.com./#q,epicmtd,n,z
ICS Github
Disclaimer: Please note that I am not a developer of epic mtd cyanogenmod, nor a developer in general. I may may mistakes because I am not as informed as the rest of you. I only know what is posted in this which as aprosammuarai states is not merged. It is used simply as a place holder and as such will not be as representative to their cm9 progress as it could be. Even so this github could be interesting to follow.
http://review.cyanogenmod.com./#q,statuspen+project:CyanogenMod/android_device_samsung_epicmtd+branch:ics,n,z
Update:
There was some activity in the ICS merged cyanogenmod github for the epic, so here is the link...
http://review.cyanogenmod.com./#q,status:merged+project:CyanogenMod/android_device_samsung_epicmtd+branch:ics,n,z
Ics Kernel Github Link
xboxfanj pointed this out, so thanks that guy nots me
http://review.cyanogenmod.com./#q,statuspen+project:CyanogenMod/android_kernel_samsung_victory+branch:ics,n,z
HEY I SAID KERNEL not kernle or kernal(haha)
Cmstats
Just found cmstats(lol im a noob) for anyone who wants to konw about installs and such
http://stats.cyanogenmod.com/
We are under epic, epicmtd, and sph-d700 so use your browser find tool if interested
(P.S. the smiley face is in there to status : open in the link which forms the smily
This is pretty big progress: http://review.cyanogenmod.com./#change,11663
I know its preliminary, but still exciting.
Hopefully Jt1134's comment helps them.
Two more things:
Preliminary kernel change too: http://review.cyanogenmod.com./#change,11662
And to the OP: please update your post to include links to kernel changes too. those are called something with victory. I think its android_kernel_samsung_victory.
1. ICS was forked automatically for us (as I understand).
2. All of the current changes are for Galaxy S devices in general (updating the graphics drivers, etc).
3. We'd still have a fair bit of work to do to rectify our own set-up to ICS, since we deviate from the other Galaxy S devices by a lot (we're the misfit at the current moment).
xboxfanj said:
Two more things:
Preliminary kernel change too: http://review.cyanogenmod.com./#change,11662
And to the OP: please update your post to include links to kernel changes too. those are called something with victory. I think its android_kernel_samsung_victory.
Click to expand...
Click to collapse
I agree with the poster above that those are a general ics kernel change, I was posting specifically about the ICS epic mtd branch and if you can show me where that applies to us helping on ics ill update my post, for now Ill add it, though
irule9000 said:
I agree with the poster above that those are a general ics kernel change, I was posting specifically about the ICS epic mtd branch and if you can show me where that applies to us helping on ics ill update my post, for now Ill add it, though
Click to expand...
Click to collapse
Epic=Victory
Victory kernel changes are epic cm kernel changes. So all those changes are epic specific or not used by all Galaxy S devices because they use a different touchscreen driver for AOSP. And also, jt1134's comments could help them a lot because he posted a possible way to fix touchscreen (using the Charge's kernel because we use the same AOSP touchscreen driver). Their commits aren't that interesting per-se, but jt1134's comments are because he contributed greatly to the other galaxy s devices and ours (helped deca on cm7), and got many galaxy s devices ics. So if he can help epic on cm7 and other devices on cm9, he can help epic on cm9.
Also, jnadke, are you still working on ICS?
xboxfanj said:
Epic=Victory
Victory kernel changes are epic cm kernel changes. So all those changes are epic specific or not used by all Galaxy S devices because they use a different touchscreen driver for AOSP. And also, jt1134's comments could help them a lot because he posted a possible way to fix touchscreen (using the Charge's kernel because we use the same AOSP touchscreen driver). Their commits aren't that interesting per-se, but jt1134's comments are because he contributed greatly to the other galaxy s devices and ours (helped deca on cm7), and got many galaxy s devices ics. So if he can help epic on cm7 and other devices on cm9, he can help epic on cm9.
Also, jnadke, are you still working on ICS?
Click to expand...
Click to collapse
My appologies xbox, op updated
irule9000 said:
My appologies xbox, op updated
Click to expand...
Click to collapse
You're ok. Don't worry. No need to apologize. And you're right. Not particularly interesting commits, but the comments should help because we use the same touchscreen driver and gpu drivers as the charge (which is what jt1134 linked to) so that means touchscreen should be working soon most likely which is a big deal considering how ics uses different touchscreen drivers than gb so its harder but now that charge has it, the devs should be able to use that.
Sent from my SPH-D700 using Tapatalk
Those changes are not merged yet as they are just placeholders until another patch set is pushed.
Sent from my Epic 4G
AproSamurai said:
Those changes are not merged yet as they are just placeholders until another patch set is pushed.
Sent from my Epic 4G
Click to expand...
Click to collapse
UberPinguin said we use the same gpu and touch drivers as the charge, so that should be helpful since jt1134 just released cm9 for charge.
Sent from my SPH-D700 using Tapatalk
xboxfanj said:
UberPinguin said we use the same gpu and touch drivers as the charge, so that should be helpful since jt1134 just released cm9 for charge.
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
I know what I'm saying is those changes aren't merged yet lol.
Still in testing only a placeholder.
Sent from my Kindle Fire using xda premium
Do we have a time frame on when the changelog is gonna be back up? Git hurts my eyes and mind late at night.
Two more commits by uberpinguin (will keaney) today for ics
http://review.cyanogenmod.com/#change,11760
http://review.cyanogenmod.com/11764
Sent from my SPH-D700 using Tapatalk
Yep looks that way.... http://review.cyanogenmod.com/#change,11852
poizone181 said:
Do we have a time frame on when the changelog is gonna be back up? Git hurts my eyes and mind late at night.
Click to expand...
Click to collapse
Sorry didnt even notice, I will note this in the op as I went to bed at 4am last night/this morning and woke up at 5am
Mkasick updated the touchscreen driver so the touchscreen should theoretically work now.
Sent from my SPH-D700 using Tapatalk
So excited. If a fully functional/stable release of cm9 is possible I will hold onto my upgrade for the rest of the year once I get it this summer probably.
Sent from my SPH-D700 using Tapatalk
Zeinzu said:
So excited. If a fully functional/stable release of cm9 is possible I will hold onto my upgrade for the rest of the year once I get it this summer probably.
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Same, Ill probably wait until the next pure google devices, after the sammy updates I dont have the same want for the galaxy s III . Cant wait for cm9
I'm waiting for the next great qwerty. Until then, this Hummingbird powered, CM9(eventually) filled, Victory will be my baby.
Sent from my Legendary 2.2 infused device.
I personally find no need for more than one or two cores in a mobile phone. I will get the newest Google flagship when my contract is over. I wont deal with bloatware and locked bootloader BS anymore no matter the specs. After playing with AOSP roms it makes you notice that some phones start that way and gets updates almost instantly.
<3 pure google or cyanogenmod
Sent from my SPH-D700 using Tapatalk
Related
Sorry to say but, at this point (unless someone pulls a miracle), it looks like the vibrant wont make the CM 6.1 release
(basing my info on 2 tweets)
wesgarner
@TheDudesAndroid @noobnl_epic @cyanogen @koush what do you think? http://review.cyanogenmod.com/#change,2152
@noobnl_epic
@wesgarner @TheDudesAndroid @cyanogen @koush should be removed
the link in wes's tweet says
Change I36172fd3: vibrant: Temporarily remove from CM manifest
vibrant: Temporarily remove from CM manifest
Reasons:
1. It doesn't compile - this can be fixed, though
2. It doesn't work... - currently the kernel inside the repo doesn't work plus the build system is not set up to flash the kernel
3. The Vibrant repo is about 2mths old
4. The Vibrant repo contains proprietary. On my fork, I have changed everything over to use extract-files, removed proprietary from all commits using filter-branch
We can refork my repo for the Vibrant, but at the same time - it still isn't ready, so mostly having it on the CM repos for 6.1 RC's this weekend is pretty pointless considering where we are in getting CM6 for the Vibrant
My manifest (git://github.com/wesgarner/android.git) is setup for the current Galaxy S repos (aka my Vibrant repo and noobnl's Epic repo), but this is still such a WIP that keeping it on CM repos really just confuses people about the current status and makes it seem like it's ready when it isn't
Change-Id: I36172fd3e2709d9ff9f23d0cc5c05a8f12d607dc
Of course, i may be completely wrong. We can always hope
Whatever. Bionix is currently rocking my Android world. I'm not sure how much better it could really get short of Froyo involvement.
opiate46 said:
Whatever. Bionix is currently rocking my Android world. I'm not sure how much better it could really get short of Froyo involvement.
Click to expand...
Click to collapse
Dude, CM is based on froyo
opiate46 said:
Whatever. Bionix is currently rocking my Android world. I'm not sure how much better it could really get short of Froyo involvement.
Click to expand...
Click to collapse
Umm you have no idea what CM is do you?
Sent from my SGH-T959 using XDA App
opiate46 said:
Whatever. Bionix is currently rocking my Android world. I'm not sure how much better it could really get short of Froyo involvement.
Click to expand...
Click to collapse
Dude......
I hit it and it goes bang
karimsaud21 said:
Dude, CM is based on froyo
Click to expand...
Click to collapse
CM is not based only on froyo.
i'm fine with that. bionix is honestly better than cm was on my g1, and those cm guys are a bunch of assholes. if (mostly) one guy can build a rom from scratch, i don't understand how a whole team can't figure it out.
You cant expect one guy to make a rom for all android devices. If it doesnt work. O well. I mean there are other roms out there for those wanting to mess with there phones. Bionix is one. And many more to come to the vibrants way. You ppl keep asking these devs who have other lives outside xda. And then get pissed when theres no special rom for ur phone. C'mon now.
Sent from my SGH-T959 using Tapatalk
So, what happens to all the money donated for CM Vibrant development?
Yeah that's what I am wondering also. I mean I understand the part of the devs having outside lives bit jeez let us know something
Sent from my SGH-T959 using Tapatalk
whodatfever said:
So, what happens to all the money donated for CM Vibrant development?
Click to expand...
Click to collapse
the donations were made to wes/scepterr... that has nothing to do with CM. true they are members of the CM team, but all they ever said was that they had plans to port CM6... that doesn't mean they have to, and anyone who decided to donate should have realized that a PLAN does not equal a promise.
if it fails, well crap. if they come back to it later and it works, hooray! until then, your donations belong to whoever you donated to. because that's how donations work.
christpuncher said:
i'm fine with that. bionix is honestly better than cm was on my g1.
Click to expand...
Click to collapse
You do understand that the g1s 528mhz processor was crappy as hell right? How can You possibly compare that too a 1ghz hummingbird?
Sent from my SGH-T959 using XDA App
whodatfever said:
So, what happens to all the money donated for CM Vibrant development?
Click to expand...
Click to collapse
beer money
Wow.... Are you serious? d
First you're comparing your Vibrant to a G1, of course it will be better! Even with a stock Vibrant.
Second, the CM guys or any dev for this matter, who gives their free time to make ROMs and MODs for peasants like you and I who cant do it ourselves, are assholes?! How?!
Third, yes it only takes one talented dev to build a ROM from scratch, but without the SOURCE they have no base to work on. It really isnt easy to make a ROM from scratch, and as far as I know only a few devs have successfully done so. Most of them base it on another dev's work or samsung itself...
christpuncher said:
i'm fine with that. bionix is honestly better than cm was on my g1, and those cm guys are a bunch of assholes. if (mostly) one guy can build a rom from scratch, i don't understand how a whole team can't figure it out.
Click to expand...
Click to collapse
whodatfever said:
So, what happens to all the money donated for CM Vibrant development?
Click to expand...
Click to collapse
I think yall misunderstood me, the Vibrant and other Galaxy S variants aren't off the boards for CM, they just PROBABLY wont make the 6.1 release
karimsaud21 said:
Reasons:
1. It doesn't compile
2. It doesn't work...
Click to expand...
Click to collapse
Umm....
Uhhh....
Do these guys know someone who can code ?
I hope so since those 2 lines coming from someone who CAN code are at best knocks against themselves.
*I coded something that won't compile* = I failed to do what I intended.
*I coded something that doesn't work* = I failed to do what I intended.
I would be ashamed.
christpuncher said:
i'm fine with that. bionix is honestly better than cm was on my g1, and those cm guys are a bunch of assholes. if (mostly) one guy can build a rom from scratch, i don't understand how a whole team can't figure it out.
Click to expand...
Click to collapse
Haha.... You think that the bionix ROM came from scratch??? He took eugenes base from the Ftwiz ROM. He even says it in the credits. Not trying to sell the ROM or development short, because it is a great ROM.
All the devs that are tied to the vibrant are trying to reverse engineer the code to get the 2.2 source which samsung has not released. Building 2.2 with out the source code is like building a sky scrapper from the top to the bottom, everything will crash. Where as 2.1 with source is building from ground up, you start from a solid foundation, then work your way up...
Wes also stated to anyone who wanted there money back, they can email him for a refund.
Just give it time. The source for the i9000 froyo was just released; it will come eventually, but development is going to lag behind that for the Nexus One, Dinc, etc. Just be glad we're getting some kind of CM; think of all the other phones that aren't even on the list.
Sent from my SGH-T959 using XDA App
Kubernetes said:
Just give it time. The source for the i9000 froyo was just released; it will come eventually, but development is going to lag behind that for the Nexus One, Dinc, etc. Just be glad we're getting some kind of CM; think of all the other phones that aren't even on the list.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Very true!
after reading their various tweets regarding them passing the buck on vibrant development, yes, they're assholes. it was clearly a joke to them because they know it's a huge hassle, so they should have just said it was probably never going to happen. i'm very grateful for the handful of devs that have actually stepped up and made this phone into what it should have been out of the box. it was clear that the cm team never cared in the first place.
Gingerbread sources out
http://opensource.samsung.com/
Yes, yes, YES!!!
**Simply Honey 3.0, Voodoo GB hack, JVE modem**
Is it really out? Is this one it GT-I9000_OpenSource_GB.zip ??
Don't mind me saying, but that's fast! Very good news indeed.
Sent from my GT-I9000 using XDA App
So early... wow samsung
Samsung galaxy s
And now comes supercurio and hardcore ;D awesome news!
Sent from my GT-I9000 using XDA Premium App
Awesome!
I'm actually curious, what other manufacturers release source code and how promptly do they do it?
It comes really fast, I'm impressed and big thanks to Samsung, custom kernels in the way !
Nice, cant wait to see the kernels start rolling in
Dear Samsung, Thanks.
haloimplant said:
Awesome!
I'm actually curious, what other manufacturers release source code and how promptly do they do it?
Click to expand...
Click to collapse
Correct me if I'm wrong, but I believe all manufacturers are bound by the GPL license of the Linux-derived kernel to publish the source code every time they release a new kernel to the public (i.e., their users). In practice, this means they will publish a new kernel source code with each new phone and each new version of Android (2.1, 2.2, 2.3, etc.). Also, if there are any critical updates that they have to apply to the kernel, they will publish that too, but such situations aren't that common. Most of the big manufacturers will publish their source code within a week of releasing their latest Android upgrade or phone.
Sent from my GT-I9000 using XDA App
Wow, Go Samsung, freaking awesome, can't wait, this is going to be an amazing week!
err am i blind? i cant see anything there. ???
edit: oops, forgot to log in. my bad sorry..
ooohhh2 said:
err am i blind? i cant see anything there. ???
Click to expand...
Click to collapse
Yeah, you are blind. Like in that song: "stop and stare".
Chedburn said:
Yeah, you are blind. Like in that song: "stop and stare".
Click to expand...
Click to collapse
"I think I'm moving but I go no whereee"
cashyftw said:
"I think I'm moving but I go no whereee"
Click to expand...
Click to collapse
yeah,i know that everyone gets scared
Samsung know the problems will be fixed quickly once sources released....
Galaxy s has an awesome dev team.
Sent from my GT-I9000 using Tapatalk
thanks samsung...
come on XDA kernel developers..
Tricky103 said:
Samsung know the problems will be fixed quickly once sources released....
Galaxy s has an awesome dev team.
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
and we are indebted to you -thank you Tricky. Cant what to see what you can make of SGS GB, if its anything like what Froyo has evolved to, then good things will come
Madrenergic said:
In practice, this means they will publish a new kernel source code with each new phone and each new version of Android (2.1, 2.2, 2.3, etc.).
Click to expand...
Click to collapse
Correct me if I'm wrong as well, but, at 125MB, this seems like more than kernel source code. The kernel patches are GPL'd, but the rest of Android is released by Google under the Apache License, meaning (as we've seen) manufacturers don't have to release any source code of customizations like blur, or sense. (see wikipedia for android, under licensing -- I had a link here, but I'm not allowed to post it until I reach 8 posts)
And if this is a 125mb kernel source download, just ignore this post...
Edit: After taking a look inside, there's both kernel source and some platform source code (I'm seeing things like webkit, bluetooth, email...), so at least some of this looks to be optionally-released stuff.
Bug Tracker
Playground ICS
I would like to take a moment and humbly thank AllDroid.org for supporting my campaign to keep Android development moving forward as a community. We are a single voice reminding everyone that as much as we are Android, Android is us.
Yeah, still downloading...
Hey man. Every one I've downloaded the past couple of days gives me the same sideload error lol
Chyrux said:
Hey man. Every one I've downloaded the past couple of days gives me the same sideload error lol
Click to expand...
Click to collapse
If it helps, I don't think we will have quite as many of those issues anymore.
Gotcha good stuff. What causes the error?
Chyrux said:
Gotcha good stuff. What causes the error?
Click to expand...
Click to collapse
40% not using proper neutral text editors on all the install scripts, 20% the mistake of trying to make the built universal, and another 20% bad file combinations.
Sent from my ADR6400L using Tapatalk
So when i install the base, I boot to the unlock screen and cannot get the screen to unlock due to screen inaccuracy. When I try to flash the port I receive an error and the installation aborts.
So, now that ICS has been released to AOSP, do you think these small bugs will be worked out?
fireshaper said:
So, now that ICS has been released to AOSP, do you think these small bugs will be worked out?
Click to expand...
Click to collapse
Please read post 1, paragraph 1.
Sent from my ADR6400L using Tapatalk
I guess I'm confused as well... AOSP was released and that is not the entire source?
htowngator said:
I guess I'm confused as well... AOSP was released and that is not the entire source?
Click to expand...
Click to collapse
The nexus source was released. In Git terms, it is just one branch.
And apparently I am going to have disappearing ink...(meaning you all get to miss my witty responses to the random comments)
Sent from my ADR6400L using Tapatalk
This is a development thread. We know about source. We know what was and wasn't released. This is not a place for general questions or chit-chat. If you have something to contribute, please post. If not, hit the thanks button, pull up a chair, and wait with the rest of us.
mrkite38 said:
This is a development thread. We know about source. We know what was and wasn't released. This is not a place for general questions or chit-chat. If you have something to contribute, please post. If not, hit the thanks button, pull up a chair, and wait with the rest of us.
Click to expand...
Click to collapse
*smack* yeah, I am still trying to put together a frankenstein build process for the mecha. Right now it is a little ugly, but it is starting to make sense.
...and another case of dew gives its life to the cause...
Sent from my ADR6400L using Tapatalk
kite edit: well, it wasn't aimed at you, obviously
Not sure if I know what I am doing, but when the poop hits the propeller, I have never had to build source that wasn't already at least somewhat modified for my device.
I got all the proprietary stuff, the countless extra common additions, and now it seems I have to go find all the hardware build parts missing because all we got was a nexus layout and dashed hopes of much more.
It may or may not be realistic to just merge in the missing parts, but at least it is a good start. Everything is configured to work, it just wants some stuff I am still downloading.
Sent from my ADR6400L using Tapatalk
I downloaded and built ICS today. However, it is based on a 3.0 kernel and HTC hasn't released the source for that yet. It would make things go a lot faster if they release it soon.
Sent from my ADR6400L using XDA App
chuckbeasley said:
I downloaded and built ICS today. However, it is based on a 3.0 kernel and HTC hasn't released the source for that yet. It would make things go a lot faster if they release it soon.
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
Is your build functional
Sent from my ADR6400L using XDA App
I am starting a fund to get a Nexus S and port directly from the device. After looking over this source, that seems to be more realistic than attempting to rewrite the entire thing.
Sent from my ADR6400L using Tapatalk
c2thej said:
Is your build functional
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
Have you ever built android from source? Do you know what we have? Do you know what you're asking?
Development. I think if this guy had built something that ran he'd mention it.
mrkite38 said:
Have you ever built android from source? Do you know what we have? Do you know what you're asking?
Development. I think if this guy had built something that ran he'd mention it.
Click to expand...
Click to collapse
I will post every detail I can, but I will admit a lot of it is currently mixed in with DHD and Dinc, as we have been working as one team instead of separate devices. I will make a point to link up what has been going on soon. That was overlooked on my part.
The builds in the first post are functional, but the version being built from source should not and will not be a [email protected]$$ rip -off of another device. That is costing time...
Sent from my ADR6400L using Tapatalk
Ffej5647 said:
oh wow! look at you being a cool forum mod on the internet! You show your authority foo!
A lot of people say they did something and oh yeah i rooted the inc...oh yeah where is the method...ummmm tell you in a week or so just making sure i can release it...couple days later it was all fake. It mostly always is. If people make claims they should show proof but you believe everything everyone says you amazing mod you.
ps: if someone makes a dumb comment ignore it. bc your a mod doesnt mean you can shoot off dumb*** comments, not everyone is as smart as you im sorry to say it.
Click to expand...
Click to collapse
While I do not always agree with the Mods on this forum, I have been in contact with the one keeping a watch over this forum and he has a good understanding of what is and isnt relevant. He responded to make a valid point because a lot of the posts that have been removed are the direct result of not reading the first post. There have been MANY posts throughout the entire site pushing for releases only days after the initial release of a partial source. I think it is best you keep in mind, that nothing he said is directly rude unless you choose to read it that way.
To read up on a lot of the details of what is going on, a lot of the work is better documented http://forum.xda-developers.com/showthread.php?t=1343361
FC09 being released OTA starting 3/26.
http://community.sprint.com/baw/message/405733#405733
FC19.rdf posted, still 2.3.6, still lists GLMS, still lists HDMI video jack?
http://device.sprintpcs.com/Samsung/SPH-D700/FC19.rdf
FC14.rdf posted. still 2.3.6
http://device.sprintpcs.com/Samsung/SPH-D700/FC14.rdf
And now it's FC09.rdf
http://device.sprintpcs.com/Samsung/SPH-D700/FC09.rdf
Sprint has posted the FC07.rdf file. Still 2.3.6, they're still working on stuff.
http://device.sprintpcs.com/Samsung/SPH-D700/FC07.rdf
A firm maybe on this one. It looks like a D700 rdf file, but it's in the wrong directory. Most of the info in the rdf looks like an OG Epic D700, but it was posted in the D710 directory. Not that it really matters.
http://device.sprintpcs.com/Samsung/SPH-D710/FB29.rdf
FB15 leaks, no rdf in sight! WTF?
And now it's FB01...still 2.3.6
http://device.sprintpcs.com/Samsung/SPH-D700/FB01.rdf
http://device.sprintpcs.com/Samsung/SPH-D700/FA31.rdf
Posted January 31st. Still listed as 2.3.6, what could they possibly still be working on
http://device.sprintpcs.com/Samsung/SPH-D700/FA06.rdf
Posted January 6th
http://device.sprintpcs.com/Samsung/SPH-D700/EL30.rdf
EL30 is the first rdf with no mention of CIQ!
http://device.sprintpcs.com/Samsung/SPH-D700/EL20.rdf
(Still lists 2.3.6 as Android version and still lists CIQ as included.)
http://device.sprintpcs.com/Samsung/SPH-D700/EL09.rdf
http://device.sprintpcs.com/Samsung/SPH-D700/EL07.rdf
http://device.sprintpcs.com/Samsung/SPH-D700/EK30.rdf
http://device.sprintpcs.com/Samsung/SPH-D700/EK23.rdf
What are these files?
"RDF" files appear to be xml based documentation files for firmware releases. You can't actually use them for anything, but it is proof that Sprint was actually working on a new firmware release as of the date code of the file. The date code is interpreted as follows:
E L 09:
Y M D
E O A
A N Y
R T
..H
Years...... D- 2010 E-2011, F-2012
Months.....A-Jan B-Feb C-March D-April E-May F-June G-July H-August I-Sept J-Oct K-Nov L-Dec.
Therefor EL09 was released for testing on Dec 9th 2011. These files best viewed in Internet Explorer (I know...but try it.)
poit said:
http://device.sprintpcs.com/Samsung/SPH-D700/EK23.rdf
This one slipped by us, Guess we were all too busy eating Turkey. Looks like they are still working on updates for the Epic. It lists Android version 2.3.6
Click to expand...
Click to collapse
Just when you thought it was safe to go back in the Gingerbread....da dum...da dum...dum dum dum dum
Sent from my SPH-D700 using XDA App
samsung confuses the $#!+ out of me. hmmm ics?
Sent from my SPH-D700 using xda premium
who knows.. they might actually FIX something..
Wait.. who am I kidding.. they'll find a way to break something totally different.. XDA devs to the rescue!
it's 2.3.6!
hope some reboots problems addressed as well....
stud_muffler said:
it's 2.3.6!
hope some reboots problems addressed as well....
Click to expand...
Click to collapse
From our work. *slaps samsung*
sent from my always aosp epic
Just as maddogin finished the lock mod for ei22 this pops up
Hopefully it will be easier since he did the ei22 one
I thought EI22 would be the last...and would have argued that at length.....until now lol.
Oh well, I'll be interested to see if anything official actually comes from it and what they will supposedly be fixing. Once you load up all the patches and a custom kernel there is not much in the way of updates needed, but for stock folks I feel sorry for the awful keyboard skips and weak GPS.
Maybe it comes with google talk with video capabilities.
I would say gps fix. With the devs here I have a great working gps and a sweet workin keyboard. I actually use it every single time now that it doesn't skipp
Sent from my SPH-D700 using xda premium
rocket321 said:
I thought EI22 would be the last...and would have argued that at length.....until now lol.
Oh well, I'll be interested to see if anything official actually comes from it and what they will supposedly be fixing. Once you load up all the patches and a custom kernel there is not much in the way of updates needed, but for stock folks I feel sorry for the awful keyboard skips and weak GPS.
Click to expand...
Click to collapse
I'm sure this is just a maintenance update.
mattallica76 said:
I'm sure this is just a maintenance update.
Click to expand...
Click to collapse
Could be an early ics build in disguise. They've done that before.
Sent from my SPH-D700 using Tapatalk
Im all for official ics but... the epic wasnt exactly a success, what would motivate them to give us eclair then froyo then gingerbread then ics?
Sent from my SPH-D700 using xda premium
xboxfanj said:
Could be an early ics build in disguise. They've done that before.
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Not on the Epic they haven't and not going to. It would take them a year to get ICS working on this. 2.3.X is Gingerbread...period.
Sent from my SPH-D700 using XDA App
kennyglass123 said:
Not on the Epic they haven't and not going to. It would take them a year to get ICS working on this. 2.3.X is Gingerbread...period.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
There were some gb builds marked as froyo. Just wishful thinking on my part.
Sent from my SPH-D700 using Tapatalk
stud_muffler said:
it's 2.3.6!
hope some reboots problems addressed as well....
Click to expand...
Click to collapse
The reboot issue is the only major issue I've seen with EI22. The GPS issue is easily resolvable. I hope they fix it because I sure as hell have failed in my attempts.
toadlife said:
The reboot issue is the only major issue I've seen with EI22. The GPS issue is easily resolvable. I hope they fix it because I sure as hell have failed in my attempts.
Click to expand...
Click to collapse
I agree. I'm wondering if the reboot issue is something deep enough in GB that the fix requires the version changes to 2.3.6?
poit said:
I agree. I'm wondering if the reboot issue is something deep enough in GB that the fix requires the version changes to 2.3.6?
Click to expand...
Click to collapse
The reboot issue is caused by a bug in the kernel. A bug in the kernel and hardware flaws are the only two thing that can cause spontaneous reboots.
etiRkca said:
Maybe it comes with google talk with video capabilities.
Click to expand...
Click to collapse
+1 to that.
I requested Gtalk for our Epics be available from both the Android Market Team, and the Gtalk team itself, I would be LMMFAO right now if this is how it went down.
Android Market Team: Gtalk team, a user has cordially requested you "ok the Gtalk.apk to be seen and downloaded by SPH-D700 users on the Android Market.
Gtalk Team: Sure thing! Oh wait, we're testing Gtalk.apk, and while he assured you guys (and us) that it would natively work, there's a few bugs.. we'll be sure to contact the Samsung Devs responsible for the SPH-D700 and tell them we have the updated files for this to work, thanks for the heads up Android Market Team!
Gtalk Team: Hey Samsung Devs, a user on Gingerbread brought up a good point, with native front-facing camera support, Gingerbread isn't quite "finished" unless our Google Video chat is working, don't fret, we have the files necessary, it should be a quick fix, here you go!
Samsung Devs: *facepalm* we just released EI22 and it took a MONTH for Sprint to trust us and OTA it, but thanks.. looks like it's back to the drawing board.
Samsung Devs: Hey Sprint, we have another incremental update, should fix a few bugs, not as big fix as EI22 but still necessary, sorry we didn't include it.
Sprint: You sons of.... fine, we're cool. But you BETTER have Ice Cream Sandwhich up your sleeves for our Flagship phone or we're throwing down, YOU HEAR ME?!
Samsung Devs: We can try.
Lol... This story is of course made-up by me just now, but if it entertained you, don't mind a thanks getting hit
Afterall, I did request Gtalk.apk from Android Market and the Gtalk team, that part of the story wasn't a joke. lol
toadlife said:
The reboot issue is caused by a bug in the kernel. A bug in the kernel and hardware flaws are the only two thing that can cause spontaneous reboots.
Click to expand...
Click to collapse
There is such a low percentage of people experiencing random reboots still and even less of a percentage within the pure stock users out in the world. So I don't think that will change. Probably adding features like Gtalk with video and maybe enabling TV out...yeah right!
http://forum.xda-developers.com/showthread.php?t=1831561 captivate glide ics leak is out.
finally an official ics version for a tegra 2 phone.so this proves ics is coming to tegra 2. The other thing is some of our developers may be able to use those drivers.
yesss!!!!
Sent from my MB860 using xda app-developers app
Probably won't help, it uses a newer version of the kernel and we don't have a 3.X kernel for the Atrix.
yes..it seems it wont help..but this gives hope for our official update
Sent from my MB860 using xda app-developers app
I don't know if it's a kernel module or built-in.
But if it's built-in we need the sources. That means leaks won't help us we have to wait for an official release of the kernel-source.
When it comes to drivers, the kernel doesnt always mean a whole lot. If that phone is the same variant of Tegra 2 used in the Atrix, there's a good chance its drivers could be used.
Jotokun said:
When it comes to drivers, the kernel doesnt always mean a whole lot. If that phone is the same variant of Tegra 2 used in the Atrix, there's a good chance its drivers could be used.
Click to expand...
Click to collapse
From what I understand, the only reason the Mimosa drivers couldn't be used is because it was for a different kernel version. We don't have a 3.X kernel, so any drivers made for a 3.X kernel probably aren't going to work for us, unless someone wants to port Moto's changes in 2.6 up to a 3.1 kernel, I guess.
Sir_Brizz said:
From what I understand, the only reason the Mimosa drivers couldn't be used is because it was for a different kernel version. We don't have a 3.X kernel, so any drivers made for a 3.X kernel probably aren't going to work for us, unless someone wants to port Moto's changes in 2.6 up to a 3.1 kernel, I guess.
Click to expand...
Click to collapse
The Mimosa drivers couldnt be used because the Tegra 2 variant in that one was the AP25. The Atrix is AP20H. The kernel had nothing to do with it.
Jotokun said:
The Mimosa drivers couldnt be used because the Tegra 2 variant in that one was the AP25. The Atrix is AP20H. The kernel had nothing to do with it.
Click to expand...
Click to collapse
Where did you find this? The hwlibs in the system dump from that device suggest it is an AP20H with a higher clockspeed.
i think we dont have developers.. Really hard decompiling kernel and modding things , add extra things and recompiling kernel again?
Captivate Glide has the same Tegra 2, AP20H, so this leak should help.
I posted it in two threads but I didn't see any response from devs.
Sir_Brizz said:
Where did you find this? The hwlibs in the system dump from that device suggest it is an AP20H with a higher clockspeed.
Click to expand...
Click to collapse
I'm having difficulty finding the thread, but its been discussed here on XDA before. Maybe you'll have better luck with search than I did. But the AP25 does have a higher clock speed than the AP20H.
Jotokun said:
I'm having difficulty finding the thread, but its been discussed here on XDA before. Maybe you'll have better luck with search than I did. But the AP25 does have a higher clock speed than the AP20H.
Click to expand...
Click to collapse
Don't get me wrong, I hope you are right and that this leak will help us out for sure. I'm just trying to rein in my expectations because I want a fully functional ICS or JB build SO BAD.
I'm feeling optimistic about this leak. =)
Sent from my MB860 using xda app-developers app
Zeljko1234 said:
Captivate Glide has the same Tegra 2, AP20H, so this leak should help.
I posted it in two threads but I didn't see any response from devs.
Click to expand...
Click to collapse
Let's give them time to research and analyze
http://m.gsmarena.com/samsung_i927_captivate_glide-4071.php
Hmmm. The ATRIX is also ap20h
From ATRIX 4g, ty all that made that possible @ ATRIX 4g community.
samcripp said:
http://m.gsmarena.com/samsung_i927_captivate_glide-4071.php
Hmmm. The ATRIX is also ap20h
From ATRIX 4g, ty all that made that possible @ ATRIX 4g community.
Click to expand...
Click to collapse
Think anything can be used from it Sam?
Will have to look at it on my day off. Saturday, which also happens to be my 2 year anniversary. All my time right now is spent on rf, and pca.
From ATRIX 4g, ty all that made that possible @ ATRIX 4g community.
samcripp said:
Will have to look at it on my day off. Saturday, which also happens to be my 2 year anniversary. All my time right now is spent on rf, and pca.
From ATRIX 4g, ty all that made that possible @ ATRIX 4g community.
Click to expand...
Click to collapse
Take your time sam!! just don't abandon us
I'm willing to donate my time to you Sam. My Wednesday officially belongs to you. Please take it as a sign of gratitude =)
Sent from my MB860 using Tapatalk 2
This kinda of things involving the creation of builds and what not are simply hard for me. I currently share my desktop with my gf, and have no laptop until after sept 5, when i get the rest of my fasfa money. So please don't get too exited.