Related
I'm not sure if this will help us much at all, but, I figured I'd put this out there.
Froyo and GB ROMs for some GSM variants of the Foxconn FB400 phone (which is what the Triumph is ) can be found here:
http://forum.lowyat.net/topic/1985476
Kernel Source and other goodies can be found here:
http://www.mediafire.com/FB400
or you can ask here http://forum.xda-developers.com/showthread.php?t=1034974
JWhipple said:
Kernel Source and other goodies can be found here:
http://www.mediafire.com/FB400
Click to expand...
Click to collapse
That awasome..mate. thxs 4 sharing
But would be sweet if that link mention Credit to
I believe that link is ardX properties member of Kaskus.us
Motorola is 'preparing' it but if it's hauwei or whatever then that would explain a delay, i love it when companies 'work together'
nonetheless, this thread may be relevant to follow. It is on the motodev blog regarding release of the open source kernel etc for this device...
http://sourceforge.net/motorola/discussion/general_comments/thread/f28d8cb7/
INTRESTING NEWS!!!:
Over at our Android Open-Source Project git servers,the source code
for Android version 4.0 (Ice Cream Sandwich) is now available.
Here's how to get it:Follow the instructions at
http://source.android.com/source/downloading.htmlCheck out the
'ics-release' branch:repo init -u
https://android.googlesource.com/platform/manifest -b android-4.0.1_r1
That's it! However since this is a large push, please be aware that it
will take some time to complete. If you sync before it's done, you'll
get an incomplete copy that you won't be able to use, so please wait
for us to give the all-clear before you sync.
This is actually the source code for version 4.0.1 of Android, which
is the specific version that will ship on the Galaxy Nexus, the first
Android 4.0 device. In the source tree, you will find a device build
target named "full_maguro" that you can use to build a system image
for Galaxy Nexus. Build configurations for other devices will come
later.
Unfortunately we still don't have our Gerrit code review servers back
online. That remains our top priority though, and we hope to have them
back soon.
This release includes the full history of the Android source code
tree, which naturally includes all the source code for the Honeycomb
releases. However, since Honeycomb was a little incomplete, we want
everyone to focus on Ice Cream Sandwich. So, we haven't created any
tags that correspond to the Honeycomb releases (even though the
changes are present in the history.)
JBQ, on behalf of the AOSP team.
--
Jean-Baptiste M. "JBQ" Queru
Software Engineer, Android Open-Source Project, Google.
Questions sent directly to me that have no reason for being private
will likely get ignored or forwarded to a public forum with no further
warning.
Hey dude, this is the development section. If you wanna post in here, you better have something to offer.
If you wanna post relevant news updates, shouldn't it go in the general section or something? Just sayin'
nrvnqsrxk said:
Hey dude, this is the development section. If you wanna post in here, you better have something to offer.
If you wanna post relevant news updates, shouldn't it go in the general section or something? Just sayin'
Click to expand...
Click to collapse
True, but is the code not something to develop a icecream rom?, if not then i will delete it, sorry if i put it in the wrong section
nrvnqsrxk said:
Hey dude, this is the development section. If you wanna post in here, you better have something to offer.
If you wanna post relevant news updates, shouldn't it go in the general section or something? Just sayin'
Click to expand...
Click to collapse
Sounds alot like a development related post when a source code is out
Developement means something you've developed, all developers know the source is out, that's why we don't need a thread in Dev, also this is like the 5th thread I've moved to general about the subject..
TheDeadCpu said:
Developement means something you've developed, all developers know the source is out, that's why we don't need a thread in Dev, also this is like the 5th thread I've moved to general about the subject..
Click to expand...
Click to collapse
Then move it or delete it if u want i dont care, just wanted to share thats all
korrel2008 said:
Then move it or delete it if u want i dont care, just wanted to share thats all
Click to expand...
Click to collapse
Nice attitude
It's nothing wrong, it's just that it's so big news it's hard to miss
No need to keep this thread open mates.
There is another one in the general section.
Thread closed
Cheers
Happened to check the htcdev website tonight and saw that they've released a bunch of kernel source codes for the One XL. Get them here
Hmm you're like a week late...kernel source was released a while ago...many threads about it..and yours will be closed
Did someone say closed?
Appreciate the info but as stated this has been posted several times already and the devs are already working with it.
Thanks
Closed
XDA Moderator
Well as you all know, Nougat just landed officially on Newer Nexuses & AOSP Source code. and unfortunately N5 wasn't "good enough" to get official google support, but we'll soon get Nougat test on our beloved N5 thanks to great Dev community supporting it.
but i was wondering the Question that title says !
though AOSP Source code is uploaded for 7.0 release , there are some binaries that i believe closed source https://developers.google.com/android/nexus/drivers#hammerhead , and i think they should be updated as well to properly work any new update on device , that's why we see binary files updated by google till now for every official update.
but as N5 is now drop-out of Official support,so google surly will not provide updated binary patches, so does hardware company (Broadcom, Qualcomm , LG ) provides these patches after official support OR our Dev do some digging even though they are closed source and finally by trial & error they fix/updates these binaries ? if it's done by Devs individually, wouldn't everyone's thought for dealing with problem might be different which ends up making some ROMs more stable on one area and others in some different area !
( PS: Well you might got it from Question it self that i'm not a proper technical person in Android and even in that matter in coding , i'm just a guy who wonder these thing & tried to find answer on google but didn't get any satisfactory so end up asking in new thread instead on QA thread so that some one like me also get to know about it also , my previous device (Samsung i9070 ), having closed source CPU (NovaThor U8500) & CPU maker drifted from business , gave insane trouble to XDA devs while porting unofficial updates, so they fed-up and drifted away to new device within months which makes me more curious about this Question, hopefully i'll get proper answer from a Dev/Experienced Member )
jineshpatel30 said:
Well as you all know, Nougat just landed officially on Newer Nexuses & AOSP Source code. and unfortunately N5 wasn't "good enough" to get official google support, but we'll soon get Nougat test on our beloved N5 thanks to great Dev community supporting it.
but i was wondering the Question that title says !
though AOSP Source code is uploaded for 7.0 release , there are some binaries that i believe closed source https://developers.google.com/android/nexus/drivers#hammerhead , and i think they should be updated as well to properly work any new update on device , that's why we see binary files updated by google till now for every official update.
but as N5 is now drop-out of Official support,so google surly will not provide updated binary patches, so does hardware company (Broadcom, Qualcomm , LG ) provides these patches after official support OR our Dev do some digging even though they are closed source and finally by trial & error they fix/updates these binaries ? if it's done by Devs individually, wouldn't everyone's thought for dealing with problem might be different which ends up making some ROMs more stable on one area and others in some different area !
( PS: Well you might got it from Question it self that i'm not a proper technical person in Android and even in that matter in coding , i'm just a guy who wonder these thing & tried to find answer on google but didn't get any satisfactory so end up asking in new thread instead on QA thread so that some one like me also get to know about it also , my previous device (Samsung i9070 ), having closed source CPU (NovaThor U8500) & CPU maker drifted from business , gave insane trouble to XDA devs while porting unofficial updates, so they fed-up and drifted away to new device within months which makes me more curious about this Question, hopefully i'll get proper answer from a Dev/Experienced Member )
Click to expand...
Click to collapse
Short answer: they don't. Either they use old binaries that still work, or they use binaries from similar devices that are updated. For example, the nougat build available here for the nexus 5 has been built on old marshmallow binaries. Only the kernel can be modified since it's open source. There is not much we can do with closed source blobs unfortunately...
Hi, i always wanted to know but Never ask..
Now i want to know about and sorry of simple demand.
What is the diference between an official ROM and unofficial ROM ?
And also diference of thread Android development with original Android développement.
Thanks.
green2005 said:
Hi, i always wanted to know but Never ask..
Now i want to know about and sorry of simple demand.
What is the diference between an official ROM and unofficial ROM ?
And also diference of thread Android development with original Android développement.
Thanks.
Click to expand...
Click to collapse
It's actually fairly simple... an "official" ROM is one that is authorized, and often supported by, the development team of that ROM and the device is considered an "officially supported device".
But since the source code for these ROMs is open source, anyone can build or compile them for their device or another device that isn't officially supported. The ROM is not supported by the development team, but by the ROM maintainer/builder only. These types of builds that are either not officially supported devices, have modified the source code outside of the original developers guidelines, or not authorized by the development team are called "unofficial". They may even be by the same maintainer as the official version, but they modified (perhaps used a different toolchain) from the original guidelines for the ROM and it cannot be considered official any longer.
Really, it's boils down to: is the device supported and authorized by the core ROM development team... if yes, it's official... if no, it's unofficial.
Android Original Development is supposed to be for ROMs, kernels, and other projects that are completely original by the author, or authorized originals... Cyanogenmod/LineageOS is a good example of this... ROMs like Resurrection Remix are not considered "original" because they are based on Cyanogenmod, thus they just go into the Android Development section.
If in doubt about what the forum groups are for, read the sticky posts in each group.
Thanks now it's more clear