Hello, I should be buying a Swift 2 Plus soon, and as a complete noob, I don't know what the death of Cyanogen is going to do to my device. Obviously it won't instantly brick it, but how am I gonna get future Android updates without installing a custom rom?
have a sexy christmas
Please, read my post here, and the (unconfirmed) Wileyfox's response to Cyanogen move here. It should be enough to clear your doubts
linuxct said:
Please, read my post here, and the (unconfirmed) Wileyfox's response to Cyanogen move here. It should be enough to clear your doubts
Click to expand...
Click to collapse
One thing relating more to the custom ROM area. So some of the CM team (not COS) are rebranding as lineage OS right. And they are continuing off the codebase of CM however we don't have a build of CM so how will and developer , from lineage or anywhere else, build a custom ROM without code from CM or AOSP. Unless Cyanogen Inc release the source code for our phone which I'm not sure they will. (Sorry if this is a noob question)
person123321 said:
One thing relating more to the custom ROM area. So some of the CM team (not COS) are rebranding as lineage OS right. And they are continuing off the codebase of CM however we don't have a build of CM so how will and developer , from lineage or anywhere else, build a custom ROM without code from CM or AOSP. Unless Cyanogen Inc release the source code for our phone which I'm not sure they will. (Sorry if this is a noob question)
Click to expand...
Click to collapse
You're absolutely correct. We can't start with the development with no sources. However, I don't think Cyanogen would do that at the moment, and, after seeing Wileyfox's response to Cyanogen moves, I think (and actually hope) they'll switch to an AOSP-based ROM with Android N 7.0 upgrade, and if that happens I'm really sure they'll have no problem on releasing the source code (remember Wileyfox devices tend to be quite developer-friendly). From that, we can work on bringing Lineage...
Related
I've been following the development of so-called ROMs for the Vibrant (and other SGS devices), but I have yet to see a single AOSP ROM. Even when Samsung released the original kernel sources for 2.1, there were no AOSP 2.1 ROMs. Why not? Is it because they don't know which BLOBs to pull for insertion or the proper vendor overlays?
Some developers have done great work with SGS kernels (especially supercurio and his Voodoo kernels ... eugene373's tend to always wipe the internal SD card unnecessarily ...). But, a kernel does not a ROM make ... therefore I ask, what is truly missing to build an AOSP ROM. I've gone through the sources, but I don't follow makefiles too well.
I know we have another month or so before Samsung is obligated to release their 2.2 kernel sources, but that should have no impact on 2.1 AOSP ROMs. Therefore, I ask "what is the hold up?" What is missing, and what might I contribute ...
Need 2.2 source code...
2.1 is a dead horse--why bother when 2.2/2.3 are out?
The reason to bother is to at least get AOSP running. Once its on 2.1, it'll be easier to get 2.2 AOSP running on it. But claiming 2.1 is a "dead horse" is the wrong path ... the real question still stands: after 9 months on the market their still are no AOSP ROMs.
MIUI
Now that vibrant 2.2 source is released ... we finally have a REAL AOSP port and my all time favorite from my old HD2 the MIUI.... so keep your heads up and wait for it to get finished.
Get a custom rom. There are so many good devs doing them don't waste your time on AOSP....... until they release the actual source code...... on April 22
sarim.ali said:
Now that vibrant 2.2 source is released ... we finally have a REAL AOSP port and my all time favorite from my old HD2 the MIUI.... so keep your heads up and wait for it to get finished.
Click to expand...
Click to collapse
Except, the 2.2 source for the Vibrant has not been released. The SGH-T959D that shows Froyo sources on Samsung's site is for the Canadian Fascinate, not the US T-Mobile Vibrant. Samsung has yet to release the 2.2 sources.
oka1 said:
Get a custom rom. There are so many good devs doing them don't waste your time on AOSP....... until they release the actual source code...... on April 22
Click to expand...
Click to collapse
Except the so-called "custom ROMs" are just modifications on the stock theme, a replacement kernel and a change of some of the supplied applications.
There is nothing close to a full "custom ROM" such as CyanogenMod or MIUI because we don't have Samsung's sources. What is passing for a "custom ROM" for the Vibrant are just repackaged files. It is akin to the "ROM cooking" that took place for the WinMo phones, not a truly ground-up build from source that is possible with Android.
EDT/Devs4Android has the MIUI build. From Source.
TW has a 2.2.1 in testing.
EDT has a 2.2.1 Beta released.
TW has a 2.3 AOSP in testing. From Source.
EDT has 2.2 AOSP in testing. From Source.
What you want is out there for you.
Watch the forums and reply when a call for Alpha testers is posted.
Hopefully it won't be long before you see a full TW/EDT/Devs4Android collaboration!
I think what the original poster is trying to ask (and I have the same question) is why were there never any real 2.1 AOSP, cyanogen5 for the vibrant. The source for 2.1 has been around for many months. Were some other proprietary bits missing, was the released source code such a mess that it was unbuildable, something else? With those questions in mind, why will things be any different when the 2.2 source comes out?
mattb3 said:
I think what the original poster is trying to ask (and I have the same question) is why were there never any real 2.1 AOSP, cyanogen5 for the vibrant. The source for 2.1 has been around for many months. Were some other proprietary bits missing, was the released source code such a mess that it was unbuildable, something else? With those questions in mind, why will things be any different when the 2.2 source comes out?
Click to expand...
Click to collapse
Yes, this is more towards what I was getting at. We do not have Samsung's kernel sources for 2.2. And, we do not have a Samsung provided vendor overlay.
When we receive these two pieces, then a true AOSP build will be possible. However, we do have the 2.1 kernel sources, so why wasn't a true AOSP build possible then? What was missing, and can we actually expect Samsung to release the overlay that's needed?
Actually, that's true. I know it was old but why didn't anyone build a 2.1 cyanogen or aosp rom? (Not to say its easy.)
Sent from my SGH-T959 using XDA App
A noob question, kindly can someone explain what is the vendor overlay stuff?
Many thanks!
Where have you been?
rpcameron said:
I've been following the development of so-called ROMs for the Vibrant (and other SGS devices), but I have yet to see a single AOSP ROM. Even when Samsung released the original kernel sources for 2.1, there were no AOSP 2.1 ROMs. Why not? Is it because they don't know which BLOBs to pull for insertion or the proper vendor overlays?
Some developers have done great work with SGS kernels (especially supercurio and his Voodoo kernels ... eugene373's tend to always wipe the internal SD card unnecessarily ...). But, a kernel does not a ROM make ... therefore I ask, what is truly missing to build an AOSP ROM. I've gone through the sources, but I don't follow makefiles too well.
I know we have another month or so before Samsung is obligated to release their 2.2 kernel sources, but that should have no impact on 2.1 AOSP ROMs. Therefore, I ask "what is the hold up?" What is missing, and what might I contribute ...
Click to expand...
Click to collapse
Dude theres been a true AOSP ROM for the Vibrant since like december and thats CM 6.1
Im running it now
rpcameron said:
I've been following the development of so-called ROMs for the Vibrant (and other SGS devices), but I have yet to see a single AOSP ROM. Even when Samsung released the original kernel sources for 2.1, there were no AOSP 2.1 ROMs. Why not? Is it because they don't know which BLOBs to pull for insertion or the proper vendor overlays?
Some developers have done great work with SGS kernels (especially supercurio and his Voodoo kernels ... eugene373's tend to always wipe the internal SD card unnecessarily ...). But, a kernel does not a ROM make ... therefore I ask, what is truly missing to build an AOSP ROM. I've gone through the sources, but I don't follow makefiles too well.
I know we have another month or so before Samsung is obligated to release their 2.2 kernel sources, but that should have no impact on 2.1 AOSP ROMs. Therefore, I ask "what is the hold up?" What is missing, and what might I contribute ...
Click to expand...
Click to collapse
For probably the same reason that many phones with non AOSP firmware running 1.5/1.6 did not bother with AOSP 1.5/1.6 when they were released around the time 2.1 source hit. Why bother developing at all for what is essentially an "out of date" OS.
The only people it seems who actively continue to develop for existing (as opposed to new) firmware are manufacturers and carriers. This stupidity should be left to the manufacturers who still do this.
One of the larger snags way back then (sits in his rocking chair on the porch) was a lack of understanding of the phones proprietary aspects and how to work around them. But we have a fairly clear understanding of Samsung's boot process now, and RFS can now easily be turned into a distant memory.
I would wager a guess that the apathy towards 2.1 will not repeat itself once we have 2.2 source widely available and the low level similarities between 2.2 and 2.3 should have Gingerbread being more than the experiment it currently is. It's been barely more than a week since Eugene's little present manifested and there are already proper and stable kernels available.
Keep in mind that the devs we do have, have done a phenomenal job of cleaning up, speeding up, and drastically enhancing our existing 2.2 release. And perhaps to the point where many will not really care, though I know many would still like to see CyanogenMod6/7 properly on this phone.
Master&Slave™ said:
Dude theres been a true AOSP ROM for the Vibrant since like december and thats CM 6.1
Im running it now
Click to expand...
Click to collapse
Um, that's not quite true. The CyanogenMod.com website lists 0 files available for download for either experimental or stable files. The CM6.1 you must be running is not a true CM build.
Also, CM is not AOSP, but rather AOSP with modifications.
phrozenflame said:
A noob question, kindly can someone explain what is the vendor overlay stuff?
Many thanks!
Click to expand...
Click to collapse
The vendor overlay tells the AOSP build system which proprietary files are needed from the device that are not available in source form. This includes things like GPS and video drivers, baseband firmware for wireless radios, &c.
hi everybody !
a month age i decided to compile a new rom for my Galaxy S absolutely from AOSP source ( branch 2.2.1_r1 ) after some compile-time problem and many painful steps to resolve ,eventually the rom successfully built and can boot it up flawlessly on emulator.
i create a nandroid backup of current rom and installed the compiled one. but i am facing new problem :
1- the phone successfully boots but after short while screen began
flicking several time and the phone go in deep sleep and never wakeup
( power button or menu button does not do any thing )
2- touch screen works only for some second that I can unlock the
phone
3- there is no network available
4- I have downloaded samsung opesource package for GT-I9000. it
contains a folder named 'platform' but when i merge these files to
AOSP , the compile process stops and fails again. if there any one can
help me which files from samsung source should i merge and how ? if
you now the answer and dont have spare time then some internet link or
online document is really useful .i have no problem studding and
reading and searching . reaching to target is my only hope .
I am really disappointed why there is not a good and complete step2step tutorial to compile an AOSP rom for galaxy s (GT-I9000) !!
such docs is available for phones like dell streak , desire , dream , magic , .... . i really want to to active these aspect on XDA forum and with help of all you ( mods and masters ) try to create such tutorial that any one in world can use to refer . i think XDA is the only reference on net to collect and create such help and document. please help me and leave PM or comment to agree ot disagree and from where can i start ?!! thank in advanced .
edit :
there is a google groups post that i send my question in Android-platform . if you prefer please join this group and active that post to ask any question related to 'galaxy s compile from source ' .
post located at http://groups.google.com/group/android-platform/browse_thread/thread/da5d6f18f3bd3c9b
I know Its pretty dumb to ask after seeing a lot of tutorial here, But I really can't understand! My Device is a huawei ascend y300. I have lots of custom rom on various forums. So I wanna built one myself! One of the developer built cm 11 from source and he is rolling out nightly on a daily basis. My interest is to build the cm11 too on my own computer based on his device specific changes he has done. and he has done a lots of changes for our device. Also if I can make any other rom from its source based of his work like mokee rom, or slimbeam etc. ANy help is appriciated. thnk you
I am curious if anyone is currently working on getting CM (or any custom ROM) working for our devices. I'm not trying to bug anyone or get an ETA, but I was thinking about attempting to port CM with their tutorial.
If anyone is working on porting a ROM, or has any tips for me I'd love to talk. Thanks.
I've just started looking into porting CM over to the 5x. I've never built a port before and I'm a bit lost in the CM documentation for it. Feel free to PM me or post below with any tips or advice.
jmiller99 said:
I've just started looking into porting CM over to the 5x. I've never built a port before and I'm a bit lost in the CM documentation for it. Feel free to PM me or post below with any tips or advice.
Click to expand...
Click to collapse
I have only built unofficial builds before, but hopefully since we have source and other Huawei devices with CM, it should be fairly easy.
If you haven't built CM for a device that it's already been ported to, I'd recommend doing that before you attempt to port it.
Good luck. I'll post any progress I make.
Am too eagerly waiting for cm on 5x .fed up of bad performance from stock .heating up too much .I was really disappointed by the heating problem .
What else I had hopes On was the on cm12.1 or 13 .
I usually check for a thread if anyone build one cm ROM for our device but still the development haven't started !
gopinaidu77 said:
Am too eagerly waiting for cm on 5x .fed up of bad performance from stock .heating up too much .I was really disappointed by the heating problem .
What else I had hopes On was the on cm12.1 or 13 .
I usually check for a thread if anyone build one cm ROM for our device but still the development haven't started !
Click to expand...
Click to collapse
I'm *trying* to get CM 12.1 to work for our device, but I've never ported before so don't expect anything soon
gopinaidu77 said:
Am too eagerly waiting for cm on 5x .fed up of bad performance from stock .heating up too much .I was really disappointed by the heating problem .
What else I had hopes On was the on cm12.1 or 13 .
I usually check for a thread if anyone build one cm ROM for our device but still the development haven't started !
Click to expand...
Click to collapse
It's still early. The fact that Huawei makes bootloader unlock codes available and has provided the amount of source code for the kernel that they have has allowed development here to happen much more rapidly than many devices do (particularly devices that lie out side of "volume" interest -- like an S5 or S6). I'm pretty optimistic.
The flip side is that life is so busy for me at the moment that it makes patience pretty easy (as in, if a stable cm13 suddenly became available I still would take my sweet time in getting around to flashing it). If I had more time on my hands it would probably be different.
Yes lets see how long we need to wait !
Can someone (hopefully a dev like @deadman96385, @EarlyMon @cyrusalmighty) confirm/agree that the Honor 5X's (I have KIW-24, US ver.) vendor = HONOR and codename = HNKIW-Q. I'm a little perplexed by what the codename is since HNKIW-Q doesn't seem right. I got that name from the build.prop ro.product.device like CM recommends.
Can anyone confirm that I have the vendor and codename right? Thanks.
EDIT: After looking at similar Huawei devices (Ascend Mate 2) it looks like the codename should just be "kiw". The Mate 2's actual ro.product.device = hwMT2LO3, but it's CM codename is "mt2." Because of this, I think for the CM codename should be "kiw". Does that sound right?
Bandit Development said:
Can someone (hopefully a dev like @deadman96385, @EarlyMon @cyrusalmighty) confirm/agree that the Honor 5X's (I have KIW-24, US ver.) vendor = HONOR and codename = HNKIW-Q. I'm a little perplexed by what the codename is since HNKIW-Q doesn't seem right. I got that name from the build.prop ro.product.device like CM recommends.
Can anyone confirm that I have the vendor and codename right? Thanks.
EDIT: After looking at similar Huawei devices (Ascend Mate 2) it looks like the codename should just be "kiw". The Mate 2's actual ro.product.device = hwMT2LO3, but it's CM codename is "mt2." Because of this, I think for the CM codename should be "kiw". Does that sound right?
Click to expand...
Click to collapse
In theory but the kiw stands for kiwi this info is directly from Huawei and we all like Kiwi more lol. You also do have a L24 US variant
deadman96385 said:
In theory but the kiw stands for kiwi this info is directly from Huawei and we all like Kiwi more lol. You also do have a L24 US variant
Click to expand...
Click to collapse
Thanks. So any custom ROM development for this device will be like Huawei/kiwi? I'm just wondering, because I'd like to know how I should be naming my files specific to Honor 5X ROM development.
EDIT:
Also, @deadman96385 do you mind sharing the partition sizes you used for building TWRP?
Name it kiwi .it sounds really great ! Moreover i dont what others are thinking on naming this device ,but kiwi is maximum minds .Go for it !
Bandit Development said:
Thanks. So any custom ROM development for this device will be like Huawei/kiwi? I'm just wondering, because I'd like to know how I should be naming my files specific to Honor 5X ROM development.
EDIT:
Also, @deadman96385 do you mind sharing the partition sizes you used for building TWRP?
Click to expand...
Click to collapse
https://github.com/Huawei-Kiwi
deadman96385 said:
https://github.com/Huawei-Kiwi
Click to expand...
Click to collapse
I didn't realize you had already started working on a CM port. I guess I can't really help out then. :/
Don't get me wrong, I do really appreciate all the work you do for this device.
Bandit Development said:
I didn't realize you had already started working on a CM port. I guess I can't really help out then. :/
Don't get me wrong, I do really appreciate all the work you do for this device.
Click to expand...
Click to collapse
That cm tree was just to build cm recovery we are still in the very early stages of a full cm tree.
Hi.
I don't know if this is the right place for posting or not. But I just wanted to share it with you guys.
I was a fan of Simple AOSP ROM on my Nexus 4 back in the day. According to me, it had all the essential features for a ROM.
Now I have switched to OP2. The development of OP2 was very slow in the early stages but now it has picked up pace.
Keeping that in mind, I want to request someone to please build this ROM for our OP2. Since I have no idea or the time to build it myself, I would love to see someone take this up.
Here is the official source code - https://github.com/SAOSP-M
Regards,
Reserved.
I'm not a developer myself but I do try and flash the roms on my OP2. Not sure if you yourself are a developer so please ignore if you already have checked these, but Paranoid android, Exodus are all aosp based.. and this, http://forum.xda-developers.com/oneplus-2/orig-development/rom-aosp-caf-oneplus2-t3386553
I think is purely aosp-caf based.
I don't know if I'm out of line suggesting an alternative rom but, http://forum.xda-developers.com/oneplus-2/orig-development/rom-halogenos-oneplus-2-t3377799
Similar to the suggestion above but is way more current. June security update, beta 2 released today.
Are there any Android Go ROMs available / underdevelopment for i9100? My phone has gone extremely slow and I think only something like Android Go could revive the old work horse.
Thanks for your time.
The unofficial LineageOS 15.1 builds by rINanDO (https://forum.xda-developers.com/galaxy-s2/development-derivatives/rom-lineageos-15-0-t3674567) are the first such ROMs currently, although, as of right now, it is in WIP phase, and although it is stable enough not to crash every few moments, a lot of things may be broken or not work at all.
I was wondering too. Thank you for the answer. I hope in 6months the bugs will be removed.
Cyanic Sword said:
The unofficial LineageOS 15.1 builds by rINanDO (https://forum.xda-developers.com/galaxy-s2/development-derivatives/rom-lineageos-15-0-t3674567) are the first such ROMs currently, although, as of right now, it is in WIP phase, and although it is stable enough not to crash every few moments, a lot of things may be broken or not work at all.
Click to expand...
Click to collapse
Are you sure those rINanDO's builds are based on Android Go and not full grown Android 8.1 ?
:fingers-crossed:
tnttrx said:
Are you sure those rINanDO's builds are based on Android Go and not full grown Android 8.1 ?
:fingers-crossed:
Click to expand...
Click to collapse
By nature, all Android Go builds are based on full grown Android 8.1, as they are built the same way, from the same source code, but the Android Go builds have an additional build flag attached at the very end.
So yes, they are based on Android Go, which in turn is based on Android 8.1.
and the flag is set !