CyanogenMod was brilliant for old devices. You could take CM9, tweak it around, and install it on something like the Galaxy Ace GT-S5830. You could breathe life into an old device.
Will there be older versions of LineageOS to accomplish the same thing? For example, an Android 4.2 Jelly Bean LineageOS? Or will it go no lower than Nougat 7.1?
Doofitator said:
CyanogenMod was brilliant for old devices. You could take CM9, tweak it around, and install it on something like the Galaxy Ace GT-S5830. You could breathe life into an old device.
Will there be older versions of LineageOS to accomplish the same thing? For example, an Android 4.2 Jelly Bean LineageOS? Or will it go no lower than Nougat 7.1?
Click to expand...
Click to collapse
Any device that was actively being developed when CM ended should be picked up by Lineage OS. If the device was no longer supported by CM, it is not likely to be supported now.
It goes back to 6.0.1 but no further.
It will do both, apparently.....
Someone appears to have updated the cm-12.1 branch, FWIW. I'm wondering if they're slowly working backwards.
Sent from my HTC One M8 using Tapatalk
MJPollard said:
Someone appears to have updated the cm-12.1 branch, FWIW. I'm wondering if they're slowly working backwards.
Click to expand...
Click to collapse
That would be my assumption since it's probably a lot easier to find people with knowledge to build CM13/12.1 than people with building knowledge for CM7 per say.
LilAnt530 said:
That would be my assumption since it's probably a lot easier to find people with knowledge to build CM13/12.1 than people with building knowledge for CM7 per say.
Click to expand...
Click to collapse
Funny you should say that, because I had to do just that very thing. I own an old phone (Motorola Atrix 4G) that never officially got support beyond CM7, so I've created my own custom CM7 for it (I'm using it as a glorified media player, but it's also allowed me to hone up on my Android ROM tinkering skills). When CM became LinOS, I created a Github organization (https://github.com/CM-Archive) to preserve the CM "gingerbread" branch, and found that there were a few things that need to be changed in order to make a clean compile. I'd offer to bring the "gingerbread" branch on LineageOS up to date for those few people who really need the CM7 code, as I've already done the work and know what needs to be changed, but as I've never made any contributions to CM or any ROM project, I don't know how to go about it. Can anyone tell me what I need to do? Something easy to follow, not "Get the frimfram and keloplotz the FTL missengibble on the gonfropple."
MJPollard said:
Funny you should say that, because I had to do just that very thing. I own an old phone (Motorola Atrix 4G) that never officially got support beyond CM7, so I've created my own custom CM7 for it (I'm using it as a glorified media player, but it's also allowed me to hone up on my Android ROM tinkering skills). When CM became LinOS, I created a Github organization (https://github.com/CM-Archive) to preserve the CM "gingerbread" branch, and found that there were a few things that need to be changed in order to make a clean compile. I'd offer to bring the "gingerbread" branch on LineageOS up to date for those few people who really need the CM7 code, as I've already done the work and know what needs to be changed, but as I've never made any contributions to CM or any ROM project, I don't know how to go about it. Can anyone tell me what I need to do? Something easy to follow, not "Get the frimfram and keloplotz the FTL missengibble on the gonfropple."
Click to expand...
Click to collapse
That's pretty epic dude! I have an LG Lucid vs840 from that had a CM9 out fot it was considering doing the same thing. As for helping them with their efforts I have no idea where to start.
But I do have a question, do you think it'd be very hard to update the cm7 cm9 or cm11 to Marshmallow devices? This might sound foolish but im still curious lol
The CM repo is moved wholesale to LineageOS, so if you know how to build, you could still build any version you like from the new source, provided that the older version was there previously in CM. I've built Lineage 13 (CM13) for several of my devices just now since I still need Xposed.
You can't expect any useful updates for <CM12.1 though, as CM had stopped working on them long ago. Not worth the extra effort of maintaining them, plus unfixable security holes.
Not looking to maintain them, simply to update them to compile from the LinOS repo. Specifically, the default.xml in the android package needs the references to CyanogenMod changed to LineageOS, and other references need to be changed as well. Once that's done, nothing further needs to be done.
Sent from my HTC One M8 using Tapatalk
Hi im looking for lineageOS 13.0-20170513-nightly-x2 this must be the last official version of that rom right?
i got it at my device but delete the zip and i dont found any working download link...
did someone got it for me please?
thx chris
jhedfors said:
Any device that was actively being developed when CM ended should be picked up by Lineage OS. If the device was no longer supported by CM, it is not likely to be supported now.
Click to expand...
Click to collapse
You say that, but there was CM for my old 2011 LG phone but I would be tremendously surprised if a LOS ROM ever shows up because there doesn't seem to be any active development for that device anymore. Makes me sad because I would love to have LOS on it (and security updates newer than 2012) but I wouldn't bank on it... the newest CM ROM I can find for it is from 2015.
Related
Hello, everyone!
Dunno if it was asked before or is it thу right place to ask this, but anyway:
Is CM team going to release official CM rom? May be even someone know how soon it will be? I don't like samsung stock rom because of the bloatware it has, but I think I am not the only one.
Thanks in advance!
kortik9 said:
Hello, everyone!
Dunno if it was asked before or is it thу right place to ask this, but anyway:
Is CM team going to release official CM rom? May be even someone know how soon it will be? I don't like samsung stock rom because of the bloatware it has, but I think I am not the only one.
Thanks in advance!
Click to expand...
Click to collapse
Don't know if there will be an official build, but unofficial build by crpalmer works great.
Rutr said:
Don't know if there will be an official build, but unofficial build by crpalmer works great.
Click to expand...
Click to collapse
Yup, I saw that, just wondering if we will get official anytime soon.
kortik9 said:
Hello, everyone!
Dunno if it was asked before or is it thу right place to ask this, but anyway:
Is CM team going to release official CM rom? May be even someone know how soon it will be? I don't like samsung stock rom because of the bloatware it has, but I think I am not the only one.
Thanks in advance!
Click to expand...
Click to collapse
I've never quite figured out why people get so hung up on "official"... When there is an official build of CM, it will still be me maintaining it and the only differences will be that:
* you'll get nightly and M builds which makes them more frequent
* you'll get slower device specific updates to the core software (right now I change it and build it, when it's official it can take weeks to get a change in the frameworks approved and you won't see it until it's approved).
that said, it will be official but doing so takes effort from me and from other people that are very busy and so all I can say is it isn't official yet.
crpalmer said:
I've never quite figured out why people get so hung up on "official"... When there is an official build of CM, it will still be me maintaining it and the only differences will be that:
* you'll get nightly and M builds which makes them more frequent
* you'll get slower device specific updates to the core software (right now I change it and build it, when it's official it can take weeks to get a change in the frameworks approved and you won't see it until it's approved).
that said, it will be official but doing so takes effort from me and from other people that are very busy and so all I can say is it isn't official yet.
Click to expand...
Click to collapse
Actually before creating this thread I saw your "unofficial" build thread and checked your profile to see if you are somehow connected to CM dev team, but you have no information in your profile. I don't like unofficial builds because often they have something tuned\installed\uninstalled, but I like how CM works and I don't want anything else, this is why I want official build. But in this case I think I should try your build, as you maintain official ones anyway.
Thanks for clarifying this!
kortik9 said:
Actually before creating this thread I saw your "unofficial" build thread and checked your profile to see if you are somehow connected to CM dev team, but you have no information in your profile. I don't like unofficial builds because often they have something tuned\installed\uninstalled, but I like how CM works and I don't want anything else, this is why I want official build. But in this case I think I should try your build, as you maintain official ones anyway.
Thanks for clarifying this!
Click to expand...
Click to collapse
Not necessarily having visibility into any framework changes I've made is a pretty reasonable concern. There's only one change that I have already submitted for review so nothing too magical going on behind the scenes. Everything else is available in my public git repos for anyone to verify.
Most of the time official builds start out as unofficial builds. At least that's what I've noticed.
Presenting CM13 unofficial. Built from mostly pure CyanogenMod sources, with a few tweaks that I try to keep updated on my github. This is only possible due to the work of Ziyan and MWisBest.
Instructions
First time flashing CM13 to your toroplus (or coming from another ROM)?
Unlock & install a recovery
Wipe data & cache partitions
Flash CyanogenMod.
Optional: Install the Google Apps addon package.
Updating from a previous build?
Just install the latest ROM zip. If you had Google Apps installed, they will be reinstalled automatically.
Click to expand...
Click to collapse
Downloads
Latest cm-13.0 build: https://www.androidfilehost.com/?fid=24588212152305191
Final cm-12.1 build: https://www.androidfilehost.com/?fid=24438995911970260
All builds: https://www.androidfilehost.com/?w=files&flid=23531
Unofficial TWRP recovery: https://www.androidfilehost.com/?fid=24459283995311440
Google Apps: http://opengapps.org/
- Platform: ARM
- Android: 6.0
- Variant: pico (recommended), or nano
Bugs
LTE Data does not work. (3G works)
XDA:DevDB Information
UNOFFICIAL CyanogenMod 13.0 (DDK 1.9), ROM for the Samsung Galaxy Nexus
Contributors
musical_chairs
Source Code: https://github.com/CyanogenMod
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.0.x
Based On: CyanogenMod
Version Information
Status: Beta
Created 2014-09-25
Last Updated 2016-07-15
now with Marshmallow!
Will this be updated to work with the new GPU drivers? Thank you!
Sent from my LG-LS980 using XDA Free mobile app
illinoissparks18 said:
Will this be updated to work with the new GPU drivers? Thank you!
Sent from my LG-LS980 using XDA Free mobile app
Click to expand...
Click to collapse
Short answer: yes. I'm going to try grabbing the relevant code from MWisBest's githib. If it turns out to be too involved for my limited skills, it will have to wait until Ziyan submits the changes to CM.
musical_chairs said:
Short answer: yes. I'm going to try grabbing the relevant code from MWisBest's githib. If it turns out to be too involved for my limited skills, it will have to wait until Ziyan submits the changes to CM.
Click to expand...
Click to collapse
OK I am going to be on board with testing for sure. I left a post in the now no longer current official thread that I flashed the last official build yesterday and I had perfect 3G to LTE to 3G handoff, rock solid WiFi strength, basically everything seemed to work very well. I am looking forward to seeing how things progress. I haven't been able to keep any of the official CM builds from bootlooping until now. Hopefully you stick with it because I am getting better performance from this device than I have seen in a long while
Sent from my Galaxy Nexus using Xparent Gray Tapatalk 2
musical_chairs said:
Short answer: yes. I'm going to try grabbing the relevant code from MWisBest's githib. If it turns out to be too involved for my limited skills, it will have to wait until Ziyan submits the changes to CM.
Click to expand...
Click to collapse
Awesome!! Thank you!!
Sent from my LG-LS980 using XDA Free mobile app
I should've had a machete to hack through the jungle of build errors from pulling a modified OmniROM device tree into a CyanogenMod build. Looks like the build is rolling now though, with any luck it might just complete successfully - who knows, it might even boot.
The only thing slower around here than me is my poor old computer.
Its kind of ironic that the Galaxy Nexus was the first official LTE device for Sprint and I am only just recently starting to get LTE on a semi regular basis.
@musical_chairs, take your time with your builds. I assure you that they are appreciated. Now that this device is actually getting decent (for Sprint) signal and still has current builds makes it more enjoyable to use than just about any time I can remember....I just miss Imoseyon's Lean kernels. I got GREAT battery on those. They were compiled in the now deceased (I think) CMRemix ROMs but the LTE is definitely a plus
Update: For now, I have stopped working on building CyanogenMod with the DDK 1.9 drivers. I was ending up with a completely unsustainable mess of a device tree, and was still running into build errors. If new drivers are what you want, use FML. I'll focus on keeping the regular CM builds updated for the time being.
musical_chairs said:
Update: For now, I have stopped working on building CyanogenMod with the DDK 1.9 drivers. I was ending up with a completely unsustainable mess of a device tree, and was still running into build errors. If new drivers are what you want, use FML. I'll focus on keeping the regular CM builds updated for the time being.
Click to expand...
Click to collapse
Link to toroplus build for fml?
Zeinzu said:
Link to toroplus build for fml?
Click to expand...
Click to collapse
I'm following its developements, but haven't had time to try it personally yet.
http://forum.xda-developers.com/galaxy-nexus/sprint-develop/rom-fml-fork-life-10-13-2014-t2903695
Thanks for trying anyhow. I'm glad cm11 still has a fighting chance with the GNex, thanks to you, and all the others who are able to help out.
We're all waiting for cm12 to get to a buildable state. In the meantime, I've been working on upgrading my build box. My old machine was just barely capable of building android, the 'new' one isn't new but it was a real beast in its day. Time for a clean build has dropped from a day and a half to two and a half hours. I'm happy...
jd14771 said:
just curious, how difficult is it to compile roms? Do you need to know how to write your own code or is it over glorified copy and pasting with packages and stuff?
Click to expand...
Click to collapse
I do a lot of copying and pasting, a lot of reading guides, and a whole lot of google-ing. I don't know how to write my own code, but I have lots of experience with applying patches. Compiling roms is not that hard if you're a Linux user, have a working knowledge of the command line, and have a basic understanding of git. Take away any one of those things and it becomes a whole lot harder.
jd14771 said:
Yeah i haven't gotten to play with linux, nor do i know what git's are (i think they are large batch's of code posted in plain text?) . always wanted to try but don't have the time.
Click to expand...
Click to collapse
git is the software the devs use to keep track of changes in the code. Most Android devs have their git repositories on Github, those are probably what you are thinking of. Every little change (called a 'commit') has its own unique hash number. It's pretty amazing, you can look through somebody else's commits and find one that fixes a bug you are working on, or split tens of thousands of changes in half, then in half again, then in half again, etc., and pinpoint the exact commit that causes a bug on your system - though that's more useful in Linux kernel development than in Android.
I don't really have the time either, but it's such a fun hobby...
Using quickboot?
Coming from Vanir. Really like the facility quickboot gives. Anyone "enabled" it? I can't seem actually show the field to turn it on. Settings search finds it, but that's it... Noticed Dev options is hidden also. What's up?
Props for keeping CM11 updated. Really like I can actually use SMS in Hangouts.
I haven't been following the nightly changes since toroplus went dark, but I ran a build today--nothing special, just the latest cm...whatever changes they are. I could post it but don't know if I should make another thread or just link to it in here.
Anything substantial get added to general cm in the last few months?
I tried to run a build of cm12 but it looks like things still aren't ready for building yet, either that or I'm not sure how to switch back and forth between the cm11 repo and cm12 without getting repo update errors.
yotvb531 said:
I tried to run a build of cm12 but it looks like things still aren't ready for building yet, either that or I'm not sure how to switch back and forth between the cm11 repo and cm12 without getting repo update errors.
Click to expand...
Click to collapse
I got cm12 built and booting for toro for the first time today. I'm trying to get mobile data working on that, then I'll give toroplus a shot. Looks like it shouldn't be too much trouble. Feel free to post any of your builds here, or start your own thread if you prefer.
Here's my cm11 build from yesterday--equivalent to a plain nightly. It's been running fine since I dirty flashed it last night. Md5sum is linked as well and noted below.
https://www.dropbox.com/s/lp4j3yayuktmlot/cm-11-20141227-UNOFFICIAL-toroplus.zip?dl=1
https://www.dropbox.com/s/z1b72j7oh70eg5w/cm-11-20141227-UNOFFICIAL-toroplus.zip.md5sum?dl=1
MD5 Sum: e6c265c57e00b4949362d6ff53c9a799
Well I got cm12 built and booting on toroplus, unfortunately the RIL is completely borked, so no cell service at all at this point. I'll keep working on that, in the mean time check out the updated cm11 build in the post right above this one.
Is there a way that someone can make a Lollipop ROM for SM-T210R? Preferably CM 12.1 or a stock ROM. I have seen multiple people on these forums ask when this will happen. I've seen the Galaxy Tab 2 AND the ORIGINAL Galaxy Tab get Lollipop before Tab 3. The Tab 4 already got it...
Thanks, and I hope that we will see a day where everyone will have the latest version of Android on their devices...
TrendingTech said:
Is there a way that someone can make a Lollipop ROM for SM-T210R? Preferably CM 12.1 or a stock ROM. I have seen multiple people on these forums ask when this will happen. I've seen the Galaxy Tab 2 AND the ORIGINAL Galaxy Tab get Lollipop before Tab 3. The Tab 4 already got it...
Thanks, and I hope that we will see a day where everyone will have the latest version of Android on their devices...
Click to expand...
Click to collapse
Tab 3 has closed source I wouldnt expect any CM in the future
Sent from my white GT-I9305
why?
Minto107 said:
Tab 3 has closed source I wouldnt expect any CM in the future
Sent from my white GT-I9305
Click to expand...
Click to collapse
How come, I don't understand, there are serveral other ROM's for KITKAT, why would it be impossible to build a Lollipop ROM? I have NO idea how to build a rom, otherwise I would give it a try.
What makes it so difficult?
We don't have drivers to build any custom ROM rather than Samsung based one. We probably can have MIUI based on Sammy but if you want custom ROMs you've chosen a wrong tablet. Tab 2 7 would do a job correctly
Sent from my white GT-I9305
Minto107 said:
We don't have drivers to build any custom ROM rather than Samsung based one. We probably can have MIUI based on Sammy but if you want custom ROMs you've chosen a wrong tablet. Tab 2 7 would do a job correctly
Sent from my white GT-I9305
Click to expand...
Click to collapse
isn't there a Galaxy Tab 3 Lite lollipop ROM that we can port over to SM-T210R?
TrendingTech said:
isn't there a Galaxy Tab 3 Lite lollipop ROM that we can port over to SM-T210R?
Click to expand...
Click to collapse
None of TAB 3 family devices got 5.x so there's nothing to port. Tab 3 7,8,10 won't be updated to 5.x
Wysłane z mojego Lenovo TAB S8-50L przy użyciu Tapatalka
Tab 3 8.0 has unofficial cm-12.1
Tab 3 8.0 has unofficial cm-12.1 and tab 3 10.1 also got it,
Grynot said:
Tab 3 8.0 has unofficial cm-12.1 and tab 3 10.1 also got it,
Click to expand...
Click to collapse
Omg but 8.0 uses Exynos 10.1 uses Intel and 7 uses ****ty Marvel CPU! You don't have source so no CM for you
Wysłane z mojego Lenovo TAB S8-50L przy użyciu Tapatalka
So, im just stuck with effin 4.2? Since i originally rooted over a year ago, i have then tried to go back to stock to update, but ii can never get an ota update.....im just frustrated with all this. Trying to teach myself and getting stuck, SUCKS!!! I KNOW I DONT USE it to its fullest potential.....ANY help would rock....oh and would help my brain hurt LESS!! Thanks! !
rheecollinskelley said:
So, im just stuck with effin 4.2? Since i originally rooted over a year ago, i have then tried to go back to stock to update, but ii can never get an ota update.....im just frustrated with all this. Trying to teach myself and getting stuck, SUCKS!!! I KNOW I DONT USE it to its fullest potential.....ANY help would rock....oh and would help my brain hurt LESS!! Thanks! !
Click to expand...
Click to collapse
You know that Tab 3 8.0 is only 4.2.2 supported, not even close to KitKat, although you can find yourselves SM-T21x Kit Kat roms. Lollipop will not be supported by any chance, even for custom roms man!
It really depends on the amount of work you are willing to do.
Some parts are binary blob only *at this time*, but may change in the future.
For example, the Vivante GPU driver has some patches under review for the mainline Linux kernel and a open source driver in progress (look up etnaviv).
If you *really* want the Tab 3 7.0" to have Lollipop, you have to be willing to do some work. Maybe try to get some of the drivers that are used in the device into the mainline kernel. Maybe get basic functionality working.
In any case, it really is up to the community at this point, and we are part of the community.
vorpalblade77 said:
It really depends on the amount of work you are willing to do.
Some parts are binary blob only *at this time*, but may change in the future.
For example, the Vivante GPU driver has some patches under review for the mainline Linux kernel and a open source driver in progress (look up etnaviv).
If you *really* want the Tab 3 7.0" to have Lollipop, you have to be willing to do some work. Maybe try to get some of the drivers that are used in the device into the mainline kernel. Maybe get basic functionality working.
In any case, it really is up to the community at this point, and we are part of the community.
Click to expand...
Click to collapse
Yeah but XDA is full of noobs that only asks when, why it takes so long time... Bringing Lollipop to TAB 3 7inch is very hard work... This tablet wasn't a beast, since release date it was low end tablet with such tragic performance. For such noobs who just want and doesn't want to help I've got an advice. Get Nexus 7 2013... 6.0 on board, noob friendly
Wysłane z mojego Lenovo TAB S8-50L przy użyciu Tapatalka
As I know so far, Marvell didn't release source codes for Galaxy Tab 3, so it's impossible to build CM12 for this device.
DroidTwe4kz said:
As I know so far, Marvell didn't release source codes for Galaxy Tab 3, so it's impossible to build CM12 for this device.
Click to expand...
Click to collapse
I *thought* everything that was necessary to build a working ROM was in Samsung's source dumps. Maybe not all the information required, but all the source code.
For that matter, I was under the impression that the unofficial Cyanogenmod port was working (Cyanogenmod 11) with an unofficial kernel.
Am I wrong?
If I am, then that might be why I have yet to successfully build a booting recovery, but other people have.
vorpalblade77 said:
I *thought* everything that was necessary to build a working ROM was in Samsung's source dumps. Maybe not all the information required, but all the source code.
For that matter, I was under the impression that the unofficial Cyanogenmod port was working (Cyanogenmod 11) with an unofficial kernel.
Am I wrong?
If I am, then that might be why I have yet to successfully build a booting recovery, but other people have.
Click to expand...
Click to collapse
@gr8nole built unofficial CM11 from his own source. He wrote device specific tree I think.
vorpalblade77 said:
I *thought* everything that was necessary to build a working ROM was in Samsung's source dumps. Maybe not all the information required, but all the source code.
For that matter, I was under the impression that the unofficial Cyanogenmod port was working (Cyanogenmod 11) with an unofficial kernel.
Am I wrong?
If I am, then that might be why I have yet to successfully build a booting recovery, but other people have.
Click to expand...
Click to collapse
The only sources that Samsung provides is kernel sources. That is not nearly enough to build a completely working rom.
DroidTwe4kz said:
@gr8nole built unofficial CM11 from his own source. He wrote device specific tree I think.
Click to expand...
Click to collapse
Yes, I did build from my own device tree, but there were other devs that contributed a lot of the early work on that tree. I'm not going to try to mention all the names because I don't want to leave anyone out. But, suffice it to say, it wasn't just me. :good:
To wrap up this post, the reason I gave up on CM for that device is because the Marvel hardware was too difficult (for me) to get working properly. Things like Wifi and hardware acceleration never worked well (or at all) and I don't have the ability to get them working any better. With essentially no other Marvel based devices to use as a guide, it was beyond my capabilities.
gr8nole said:
The only sources that Samsung provides is kernel sources. That is not nearly enough to build a completely working rom.
Yes, I did build from my own device tree, but there were other devs that contributed a lot of the early work on that tree. I'm not going to try to mention all the names because I don't want to leave anyone out. But, suffice it to say, it wasn't just me. :good:
To wrap up this post, the reason I gave up on CM for that device is because the Marvel hardware was too difficult (for me) to get working properly. Things like Wifi and hardware acceleration never worked well (or at all) and I don't have the ability to get them working any better. With essentially no other Marvel based devices to use as a guide, it was beyond my capabilities.
Click to expand...
Click to collapse
You already did more than enough for our device and I'm thankful for that. Someone will continue to build CM based on your source.
gr8nole said:
To wrap up this post, the reason I gave up on CM for that device is because the Marvel hardware was too difficult (for me) to get working properly. Things like Wifi and hardware acceleration never worked well (or at all) and I don't have the ability to get them working any better. With essentially no other Marvel based devices to use as a guide, it was beyond my capabilities.
Click to expand...
Click to collapse
For hardware acceleration, did you ever look at the etnaviv project? I know that they are working on getting patches upstreamed for the GPU on the SM-T210 (Vivante GC 1000)?
For that matter, the Marvell SD8787 wifi chip has firmware mainlined (as of 2011, updated in 2015) and has driver support in "drivers/net/wireless/mwifiex/sdio.h" as of commit 4a7f5db1 (take a look at CONFIG_MWIFIEX). I don't know if its worth attempting to backport or not (some issues may have been fixed). Maybe look at the linux-firmware tree?
I'm pretty certain that at one point Marvell was looking at getting a device tree for the PXA986/PXA988 into the mainline kernel, but I don't think they succeeded.
Parts on the SM-T210R that I haven't found in the mainline kernel is the touchscreen. I haven't looked at everything else yet, and I'm not *absolutely* certain that the touchscreen isn't in the mainline kernel either (I might be looking at a config option and assuming the wrong thing from Samsung's sources).
EDIT1: I've been trying to build cyanogenmod on systems that aren't officially supported by AOSP, which is why I may have never been able to build it myself and *actually* contribute and check to see if etnaviv works, and if the mainline driver works better. Anyway, thanks for your work gr8nole (and everyone else's).
EDIT2: For SD8787 bluetooth support, look at CONFIG_BT_MRVL/CONFIG_BT_MRVL_SDIO
vorpalblade77 said:
For hardware acceleration, did you ever look at the etnaviv project? I know that they are working on getting patches upstreamed for the GPU on the SM-T210 (Vivante GC 1000)?
For that matter, the Marvell SD8787 wifi chip has firmware mainlined (as of 2011, updated in 2015) and has driver support in "drivers/net/wireless/mwifiex/sdio.h" as of commit 4a7f5db1 (take a look at CONFIG_MWIFIEX). I don't know if its worth attempting to backport or not (some issues may have been fixed). Maybe look at the linux-firmware tree?
I'm pretty certain that at one point Marvell was looking at getting a device tree for the PXA986/PXA988 into the mainline kernel, but I don't think they succeeded.
Parts on the SM-T210R that I haven't found in the mainline kernel is the touchscreen. I haven't looked at everything else yet, and I'm not *absolutely* certain that the touchscreen isn't in the mainline kernel either (I might be looking at a config option and assuming the wrong thing from Samsung's sources).
EDIT1: I've been trying to build cyanogenmod on systems that aren't officially supported by AOSP, which is why I may have never been able to build it myself and *actually* contribute and check to see if etnaviv works, and if the mainline driver works better. Anyway, thanks for your work gr8nole (and everyone else's).
EDIT2: For SD8787 bluetooth support, look at CONFIG_BT_MRVL/CONFIG_BT_MRVL_SDIO
Click to expand...
Click to collapse
I haven't looked at any of this in a long time, and have no real desire to at this point.
gr8nole said:
I haven't looked at any of this in a long time, and have no real desire to at this point.
Click to expand...
Click to collapse
Fair enough. I'll probably look into once I know I have my build environment set up correctly. E.g., I can build a recovery and have it work correctly.
hi guys, we've got 5.1.1 officially but cm13, based on android 6.0, is even sweeter (doze, app permission control, etc) . did you hear any news from devs?
It looks like that Temasek and Joshndroid are already preparing an unofficial CM 13 Build for our SM-P600 Tablet.
Look at https: //github.com/temasek/android_packages_apps_Settings/commits/cm-13.0
&
https: //github.com/Joshndroid/device_samsung_lt03wifi/tree/cm-13.0-test-rebasecm12
I can tell you that the p600 will get official CM13 if @joshndroid, @ Shawn, and myself can figure out why we get a black screen after rebooting from recovery.
Sent from my SM-P600 using Tapatalk
we are trying as hard as we can. hopefully we all can come up with the goods, I have put a lot of time into it already pushing to cm's gerrit to fix broken things, but unfortunately i cant do it on my own. Shawn and orion116 are definitely assisting in getting this done, hopefully raymanfx comes to the party as well lol
joshndroid said:
we are trying as hard as we can. hopefully we all can come up with the goods, I have put a lot of time into it already pushing to cm's gerrit to fix broken things, but unfortunately i cant do it on my own. Shawn and orion116 are definitely assisting in getting this done, hopefully raymanfx comes to the party as well lol
Click to expand...
Click to collapse
How is the status? Any progress?
Stogie87 said:
How is the status? Any progress?
Click to expand...
Click to collapse
i am getting succesful builds but am getting black screen (back light turns on but nothing shows). unsure whether its kernel or vendor related or even tree related with something not activated? looking at some other device trees to see what they have changed
ok, this tricky problem still reamains. I have seen, that temasek released his second alpha build of cm 13. You don't want to use his source again for further releases?
Stogie87 said:
ok, this tricky problem still reamains. I have seen, that temasek released his second alpha build of cm 13. You don't want to use his source again for further releases?
Click to expand...
Click to collapse
best to work on the base cm rom first before working on derivatives. I will be releasing a temasek rom for cm-13.0. But we need cm-13.0 working first. More hands on a single distro makes hopefully better/lighter work. Once we get a cm happening, all the derivatives will come next so everyone wins.
I'm trying to build Stock AOSP (Not LineageOS) straight from Google for the OnePlus 3/3T?
I searched for a guide, but haven't found one.
Thanks in advance!
You can't
AOSP source is available for Pixel and Nexus devices
But you can build CAF for OnePlus 3, is clean and close to AOSP
Sent from my ONEPLUS A3003 using Tapatalk
Since you're doing it on your own I suggest using a rom here as a base GZR recently posted GZOSP a Oreo base for Developers to use as a base for their roms you should check it out it's a great start if you're new to development
liam_davenport said:
Since you're doing it on your own I suggest using a rom here as a base GZR recently posted GZOSP a Oreo base for Developers to use as a base for their roms you should check it out it's a great start if you're new to development
Click to expand...
Click to collapse
That would be doing him a great dis-service. Buy using anothers base you dont learn everything you need and rely on others code way too much. Not to mention if a cm/los issue happens (underlying bug in their base code so you are waiting for them to fix it) This is the reason that whole project will not work.
Starting from scratch is a great start and a place everyone should start
... If he's never built a rom before then starting from scratch is most definitely *not* the place to start. GZOSP would likely be the best place to start as at least you can sync all and it actually builds. Would learn a ton just by figuring out how to remove all the GroundZero naming to make it your "own" rom.
There aren't any default AOSP device tree's available for OP3(you'd *have* to use someone else's code and it would likely require manually fixing it to build) so can't start there really, and good luck trying to find which branch(s) of caf and which repo's you need to build.. Writing device trees from scratch by yourself for aosp is drunkeness unless you've done it before and *know* what you're doing.
--
TLDR: There's no guide because it's not a thing currently. Would start with GZOSP if I were you.
HolyAngel said:
... If he's never built a rom before then starting from scratch is most definitely *not* the place to start. GZOSP would likely be the best place to start as at least you can sync all and it actually builds. Would learn a ton just by figuring out how to remove all the GroundZero naming to make it your "own" rom.
There aren't any default AOSP device tree's available for OP3(you'd *have* to use someone else's code and it would likely require manually fixing it to build) so can't start there really, and good luck trying to find which branch(s) of caf and which repo's you need to build.. Writing device trees from scratch by yourself for aosp is drunkeness unless you've done it before and *know* what you're doing.
--
TLDR: There's no guide because it's not a thing currently. Would start with GZOSP if I were you.
Click to expand...
Click to collapse
I mean in Biology, you don't start at the organism, you start at the atom. You start at the base and build from there.