Hey folks,
I have a Samsung Galaxy S 8.4" T705 LTE tablet that is very hard to find quality AOSP ROM's for. Not many people are developing for it.
There has been only one AOSP ROM that has full radio/LTE functionality so far. An unofficial CyanogenMOD build:
http://forum.xda-developers.com/gal...official-blck-cyanogenmod-12-sm-t705-t3053004
Unfortunately, the developer has left XDA and abandoned this project. We haven't had an update to the ROM in almost two months.
I'm not a developer or a coder. I do have VMware and basic Linux skills. But I don't have a ton of time to invest in learning how to port a ROM.
How hard would it be for me to take the existing ROM zip (do not have source code) and update it with the latest Cyanogen commits/fixes?
Are we talking about a couple hours of learning or weeks?
I'm guessing I would need the source code?
Related
Hi
Short and sweet, I am busy getting into ROM development, and as exercise to get a better grasp on what is going on, I mostly dabbled with AOSP until yesterday. I am in the process of porting Cyanogenmod 10.2 to Galaxy S2 (i9100).
While going through the CM instructions, there was a segment on how to extract "proprietary blobs" from CM running on the device in question. This is required as part of the build for hardware specific reasons they did not give too much details about.
I just have one query. Has anyone tried to, or know if it is possible to do this blob extraction from ROMs other than CyanogenMod?
That's all folks.
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
Hi all,
I've been experiencing with Team-Gummy Rom source code for quite some time now. I usually compile from source to get the latest, along with some of my own addition. Lately I've been obsessed with having Android L code running on my Galaxy S4 (qcom) and so I downloaded AOSP source and after some failed attempts I was able to build it with the S4 device package from Team gummy.
So way cool! I may have in my hands the first (maybe not but as far as I know anyway) Android L build on the S4. But before going further, I have a question. In theory if I flash the system.img file produced by the build process and keep the kernel and boot.img from my current install, it should all come together right? Anyone here has an Idea what it would do?
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.
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...