Hello, I have been looking to port Android 4.4 from the nexus 5 factory image, is this do-able? Thanks guys
Nope, completely different devices. Aside from some of the APKs and some other minor things found in the image, the rest of it would be of no use to getting 4.4 running on the S3. You would have to port the 4.4 code from AOSP to be compatible with this hardware. I would wait for CM11.
Sent from my SGH-I747M using Tapatalk
FabC87 said:
Nope, completely different devices. Aside from some of the APKs and some other minor things found in the image, the rest of it would be of no use to getting 4.4 running on the S3. You would have to port the 4.4 code from AOSP to be compatible with this hardware. I would wait for CM11.
Sent from my SGH-I747M using Tapatalk
Click to expand...
Click to collapse
CM11 source is now out. Some things need worked on though like CM Launcher, lock screen, etc.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Porting the kit kat ROM from the nexus 4 should work though a lot of our specs are the same. I've been trying to work on that.
There's no need to "port" kitkat to this device as Google has released source for kitkat. Just setup your device trees and make sure you have all the hardware repos necessary for this device. Then compile from source.
Task, would you be able to link to some more walkthrough-like instructions to do this? I would like to try to compile AOSP for this device from source.
joemommasfat said:
Task, would you be able to link to some more walkthrough-like instructions to do this? I would like to try to compile AOSP for this device from source.
Click to expand...
Click to collapse
You'll need some knowledge on compiling and messing with AOSP.
There's already a developer working on 4.4 for the i747. The Dev manages Quantum for the S3. It would be a little bit easier to build from CM11 but the code is very rough but it just did get released last night.
Sent from my SAMSUNG-SGH-I497 using Tapatalk
I do have some knowledge of compiling and messing with AOSP. What I don't know how to do is set up a new device tree a get the necessary hardware repos. I have synced the CM-11.0 source, but they also do not have a d2att device tree.
My question is if anyone can help me to do that.
Even if someone else is already on it, perhaps I would just like to learn how.
joemommasfat said:
I do have some knowledge of compiling and messing with AOSP. What I don't know how to do is set up a new device tree a get the necessary hardware repos. I have synced the CM-11.0 source, but they also do not have a d2att device tree.
My question is if anyone can help me to do that.
Even if someone else is already on it, perhaps I would just like to learn how.
Click to expand...
Click to collapse
This may help you building from CM. This may also help too.
A tutorial may not give you all the information you're looking for either. Its all about researching the device.
Sent from my SAMSUNG-SGH-I497 using Tapatalk
Related
As a proof of concept I compiled Kit Kat for our Acer Inconia. It needs a new build of CWM in order to flash. I have not been able to boot up CWM that I compiled so anyone here that has built recovery on here before try to build latest CWM and/or TWRP then we can try out this KitKat build to see if it boots or not. It may need some kernel patches. It's using pio_maski's jb-mr2 trees that I modified for 4.4 for a100 (note: I haven't uploaded yet and won't unless it boots).
Download: http://d-h.st/aKr
What you can do to help:
1. Compile the latest TWRP or CWM and post if it boots. Only do this if you've done it before; I'm not going to teach because it is out of my knowledge why CWM won't boot. If you come across any errors and don't know how to fix PM me or post here I'll help you fix it.
2. NOTHING can be done until we have a working (latest) recovery.
Sources:
Device: https://github.com/awid777/android_device_acer_a100 (cm10.2 branch)
Note for the sources: This isn't the source I used to compile the initial build. However, they are almost identical. The credits for the sources for the ROM go to @pio-masaki for his device and commons trees and prebuilt kernel. I would post the sources I used but I never uploaded them because I ended up deleting them early on as I prefer to use a single device tree. All my commits will now be posted to the listed source.
awidawad said:
As a proof of concept I compiled Kit Kat for our Acer Inconia. It needs a new build of CWM in order to flash. I have not been able to boot up CWM that I compiled so anyone here that has built recovery on here before try to build latest CWM and/or TWRP then we can try out this KitKat build to see if it boots or not. It may need some kernel patches. It's using pio_maski's jb-mr2 trees that I modified for 4.4 for a100 (note: I haven't uploaded yet and won't unless it boots).
Download: Pending upload.
What you can do to help:
1. Compile the latest TWRP or CWM and post if it boots. Only do this if you've done it before; I'm not going to teach because it is out of my knowledge why CWM won't boot. If you come across any errors and don't know how to fix PM me or post here I'll help you fix it.
2. NOTHING can be done until we have a working (latest) recovery.
Click to expand...
Click to collapse
I am not a "DEV", however I have a good amount of talent with photoshop and have some self taught coding experience with linux and html5. I also am willing to learn/eager to learn. I know you mentioned you don't want to teach. Just know if you point me in the direction I am willing to do the work on my end to get the knowledge and apply it. I have been playing with this tablet and working on a hybrid kitkat look alike using 4.1.2 as my base. I tried using 4.3 and applying 4.4 goodies to it. Didn't work that well. The 4.3 Jellytime was a bit quirky at times and didn't seem stable as a daily driver. I have put together a couple new boot animations to compliment kitkat already. I have also modified Arora installer with a very good kitkat theme. I have used it several times to verify it works correctly. I can provide that if wanted. I am waiting for a stable build and willing to help where I can. I plan on installing this tablet into my dash in the very near future. Once that is done, unfortunately I will only be able to help with themes and basic items that don't require the tablet all the time. I have contemplated having the ability to remove the tablet whenever I leave the car so I guess we will see when I get there. Apologize for the long post.
po8pimp said:
I am not a "DEV", however I have a good amount of talent with photoshop and have some self taught coding experience with linux and html5. I also am willing to learn/eager to learn. I know you mentioned you don't want to teach. Just know if you point me in the direction I am willing to do the work on my end to get the knowledge and apply it. I have been playing with this tablet and working on a hybrid kitkat look alike using 4.1.2 as my base. I tried using 4.3 and applying 4.4 goodies to it. Didn't work that well. The 4.3 Jellytime was a bit quirky at times and didn't seem stable as a daily driver. I have put together a couple new boot animations to compliment kitkat already. I have also modified Arora installer with a very good kitkat theme. I have used it several times to verify it works correctly. I can provide that if wanted. I am waiting for a stable build and willing to help where I can. I plan on installing this tablet into my dash in the very near future. Once that is done, unfortunately I will only be able to help with themes and basic items that don't require the tablet all the time. I have contemplated having the ability to remove the tablet whenever I leave the car so I guess we will see when I get there. Apologize for the long post.
Click to expand...
Click to collapse
This is not a port, thus doesn't need modification. It is compiled (built) from source and the work that needs to be done is in the source code so it can be compiled properly and work without modification
http://wiki.cyanogenmod.org/w/Development
awidawad said:
As a proof of concept I compiled Kit Kat for our Acer Inconia. It needs a new build of CWM in order to flash. I have not been able to boot up CWM that I compiled so anyone here that has built recovery on here before try to build latest CWM and/or TWRP then we can try out this KitKat build to see if it boots or not. It may need some kernel patches. It's using pio_maski's jb-mr2 trees that I modified for 4.4 for a100 (note: I haven't uploaded yet and won't unless it boots).
Download: [url]http://d-h.st/aKr[/url]
What you can do to help:
1. Compile the latest TWRP or CWM and post if it boots. Only do this if you've done it before; I'm not going to teach because it is out of my knowledge why CWM won't boot. If you come across any errors and don't know how to fix PM me or post here I'll help you fix it.
2. NOTHING can be done until we have a working (latest) recovery.
Click to expand...
Click to collapse
Thanks for the link and quick response, will take a look through some of that stuff and see if there is anything I can do to help. Also I noticed while I was typing the first one you put up a download... Did you get it to boot. I downloaded and tried using TWRP and was unsuccessful. I tried a couple times to make sure it copied over from the computer correctly. Still the same result.
4.4 updates different. Latest cwn will flash it. Maybe there's an easy way to do this
Sent from my SPH-L710 using XDA Premium 4 mobile app
Ok so I am stuck right now. I spent a couple hours building an environment and started compiling from source. I am stuck at this point:
$ source build/envsetup.sh
$ breakfast a700
Where a700 is, should be a100. I get errors when doing this because CyanogenMod does not have the device in it's file system. Whoever has successfully done this, please advise. I am over half way with this and would like to complete the build. I have about 20gbs of data sitting on my cpu waiting to compile this so the sooner we can find the solution the better. Thanks in advance.
Need help solving this to move further... There might be a work around, however I have never done this and I am stuck.
Wait till tonight. I'll post my code.
Sent from my One SV using Tapatalk
awidawad said:
Wait till tonight. I'll post my code.
Sent from my One SV using Tapatalk
Click to expand...
Click to collapse
Sounds good. I spent a good part of 3 hours compiling a master build of Kitkat which was complete prior to me leaving for work this morning, however my daughter kicked the power strip under the desk and shut everything down. I will try and find a little time tonight to recompile.
Am I missing something?
Sent from my SPH-L710 using XDA Premium 4 mobile app
TWRP Version?
Is this TWRP new enough for your needs if not what is the newest version you are aware of
a100 TWRP 2.6.1.0 windows installer: as far as I can tell the Twrp image is based of linuxsociety's/GodMachine's work I know for sure the installer is his
http://d-h.st/Rfm
I have flashed this and all seems to work well
I also took the 2.6.1.0 from the above linked installer and put it into a flashable.zip that originaly contained GM's 2.2.2.1 TWRP
I updated the script to show the proper version as well attatched below
AngryManMLS Is responsible for both 2.6.1.0 and 2.6.3.0, "if I am not mistaken"?
His windows/Linux installers can be found here: http://www.androidfilehost.com/?a=show&w=files&flid=9577
and Here:http://forum.xda-developers.com/showpost.php?p=47555451&postcount=109 For 2.6.3.0
I also invited AngryManMLS to build the TWRP needed for this project So We'll have to wait and see if he can help "Break US OFF A PEICE OF SOME KIT-KAT---- Iconia???!!!!!!"
I just want to correct something. The only thing I have done was updating the Windows and Linux installers for TWRP. I have no responsibility with the compiling of TWRP itself. At this point we're waiting for the TWRP folks themselves to fix whatever issues that lie with Kit Kat 4.4. I don't know what to say beyond that. Sorry.
AngryManMLS said:
I just want to correct something. The only thing I have done was updating the Windows and Linux installers for TWRP. I have no responsibility with the compiling of TWRP itself. At this point we're waiting for the TWRP folks themselves to fix whatever issues that lie with Kit Kat 4.4. I don't know what to say beyond that. Sorry.
Click to expand...
Click to collapse
My Bad I shouldn't have assumed do you know who is doing the compiling?
I'm going to go ahead and compile TWRP. I've educated myself on the a100 (I've never done programming on this device or any other Tegra based device... Used to Qualcomm and HTC) hopefully it will work. Current TWRP branch on GitHub is twrp2.7 and has all KitKat changes in it. I'll have a build tomorrow morning. Tonight I have to finish my essays and other homework. I'll let you all know if recovery boots or not. If it does boot, I'll go ahead and attempt installing and booting KitKat
hello! I wonder if owners will share files as well as the vendor, I've wanted to compile pacman for this tablet but can not find the source code! Thanks in advance!
josegalre said:
hello! I wonder if owners will share files as well as the vendor, I've wanted to compile pacman for this tablet but can not find the source code! Thanks in advance!
Click to expand...
Click to collapse
Once I have time, which won't be until later tonight. You could use www.github.com/pio-masaki too. Use the jb-mr2 branch for 4.3
http://forum.xda-developers.com/showpost.php?p=41990263&postcount=1
awidawad said:
Once I have time, which won't be until later tonight. You could use www.github.com/pio-masaki too. Use the jb-mr2 branch for 4.3
Click to expand...
Click to collapse
hardslog said:
http://forum.xda-developers.com/showpost.php?p=41990263&postcount=1
Click to expand...
Click to collapse
thank you! I have to have fun these days!
Well I compiled latest TWRP it didn't work it has same errors. I'll take this up with Dees_Troy. Because when I place the same trees and TWRP into the cm-11 source it won't compile, whereas it compiles fine in cm-10 source. When I manually fix compilation errors it compiles but when flashed it doesn't boot. Same story with CWM
Sent from my One SV using Tapatalk
awidawad said:
Well I compiled latest TWRP it didn't work it has same errors. I'll take this up with Dees_Troy. Because when I place the same trees and TWRP into the cm-11 source it won't compile, whereas it compiles fine in cm-10 source. When I manually fix compilation errors it compiles but when flashed it doesn't boot. Same story with CWM
Sent from my One SV using Tapatalk
Click to expand...
Click to collapse
Try compiling cwm then.
Sent from my SPH-L710 using XDA Premium 4 mobile app
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.
I thought of developing a kernel so that i can use it with my CM11 that im going to port shortly. I thought I'll compile the stock kernel from source itself. I use android pre-built tool chain (arm-eabi-4.6)
I get a lot of compiler errors on stock kernel without any modifications itself...
Do i need to change my tool chain?
Sent from my One V using XDA Free mobile app
I never tried to build the stock kernel, but I think they did it with the android 4.0 toolchain.
To run CM, you need a CM-Kernel. You have to port things from the stock or a custom kernel (like Hellboy by maxwen) to the cm11 kernel.
Try to use rastomanchiks kernel sources (https://github.com/rastomanchik/android_kernel_htc_primou). This kernel is mostly working, stable and has a good battery life now.
I'd also like to build cm11, but my download speed is to slow to download the sources.
Exactly. Even my download speed is slow. And i have a cap also. After 8GB, my download speed drastically decreases. It takes ages to sync the sources...
Sent from my One V using XDA Free mobile app
How different is Cm kernel from stock? I mean what changes should i make?
Sent from my One V using XDA Free mobile app
Cm needs many features which aren't included in the stock kernel and also you should get ION memory allocator working.
Help
jonas2790 said:
Cm needs many features which aren't included in the stock kernel and also you should get ION memory allocator working.
Click to expand...
Click to collapse
Yeah. How do I port?
What happened to your CM12 project?
hehaichi said:
Yeah. How do I port?
What happened to your CM12 project?
Click to expand...
Click to collapse
I started working on cm12 again yesterday and finally have cm11 sources now, so expect a cm11 build in some days
I can't help you with porting, because all the porting work was done by rastomanchik and I chatted with him. You'd have to ask him about this, but he wasn't online the last weeks and can't speak english without google translator.
jonas2790 said:
I started working on cm12 again yesterday and finally have cm11 sources now, so expect a cm11 build in some days
I can't help you with porting, because all the porting work was done by rastomanchik and I chatted with him. You'd have to ask him about this, but he wasn't online the last weeks and can't speak english without google translator.
Click to expand...
Click to collapse
Actually I insist on porting myself so that I can learn building properly.
Actually these things are also interesting.. fixing bugs and all...
Have series of exams till May end. I cant build properly until then. I thought why not learn something..
Where did you learn about building and other stuff. Also I want to build the device tree on my own.
If you could specify some sources to learn, that would be grateful!
hehaichi said:
Actually I insist on porting myself so that I can learn building properly.
Actually these things are also interesting.. fixing bugs and all...
Have series of exams till May end. I cant build properly until then. I thought why not learn something..
Where did you learn about building and other stuff. Also I want to build the device tree on my own.
If you could specify some sources to learn, that would be grateful!
Click to expand...
Click to collapse
This is exactly the same point of view I had when I started some months ago
Sadly, there isn't much documentation about own device trees and own kernels out there.
There also is no reference device tree, so every dev does it in his own way. I'm always trying to have a clean, easy device tree and use the CM ones as a reference.
You can find some tutorials about building cm, but only with downloading a ready-to-use device config and kernel.
I just played around with it one or two weeks and learned the most.
If you have enough time, please at least try to get into this stuff, maybe we can get cm12 running.
You can reach me on irc in the channel #hov on freenode.
jonas2790 said:
This is exactly the same point of view I had when I started some months ago
Sadly, there isn't much documentation about own device trees and own kernels out there.
There also is no reference device tree, so every dev does it in his own way. I'm always trying to have a clean, easy device tree and use the CM ones as a reference.
You can find some tutorials about building cm, but only with downloading a ready-to-use device config and kernel.
I just played around with it one or two weeks and learned the most.
If you have enough time, please at least try to get into this stuff, maybe we can get cm12 running.
You can reach me on irc in the channel #hov on freenode.
Click to expand...
Click to collapse
I have sufficient time only after May. Till then I'll have to do some research and learn the basics.
I saw on the CM wiki page, it says you can run a prebuilt kernel also... So would it work if we could tweak the stock kernel a bit?
And how do I apply patches to the kernel?
hehaichi said:
I have sufficient time only after May. Till then I'll have to do some research and learn the basics.
I saw on the CM wiki page, it says you can run a prebuilt kernel also... So would it work if we could tweak the stock kernel a bit?
And how do I apply patches to the kernel?
Click to expand...
Click to collapse
Yes you can use a prebuilt kernel, but it will only work if the kernel supports you cm version.
You apply patches to a kernel by changing files or directories in the kernel. For example you can use another fs module (maybe with more functions) by copy and pasting the folder for the module from another kernel. The problem is, the new module may require some functions your kernel does not have so it won't compile.
Hey i had mailed rastomanchik and he said 3.4.x kernel is an impossibility for cm11? Why?
Sent from my One V
hehaichi said:
Hey i had mailed rastomanchik and he said 3.4.x kernel is an impossibility for cm11? Why?
Sent from my One V
Click to expand...
Click to collapse
1. It would be much, much, much work.
2. I think there are some device-specific drivers that only work with 3.0
I'm ready to do that work only if i knew how to...
Sent from my One V
hehaichi said:
I'm ready to do that work only if i knew how to...
Sent from my One V
Click to expand...
Click to collapse
Try to get into it yourself or talk with people who know about kernel developement, I'm also new to android developement.
What would it take to see a base AOSP ROM put together for the LG G4? I know there's some folks working hard at bringing CM to the G4, but what about an AOSP unmodified ROM with drivers, of course? I've always wondered if that is a better option than say a ROM like CM which has loads of known bugs and issues.
Maybe an AOSP super-stock setup which we could modify after via Xposed / Mods to add in what we want would be a better option?
CJ-Wylde said:
What would it take to see a base AOSP ROM put together for the LG G4? I know there's some folks working hard at bringing CM to the G4, but what about an AOSP unmodified ROM with drivers, of course? I've always wondered if that is a better option than say a ROM like CM which has loads of known bugs and issues.
Maybe an AOSP super-stock setup which we could modify after via Xposed / Mods to add in what we want would be a better option?
Click to expand...
Click to collapse
After we finish the device tree and everything is working, it can be then used to build whatever Rom you desire
You rock, thank you for the quick response! I'm not even sure what kind of rom I desire. I just know it would be neat to go full on basic AOSP and add from there without some of the clutter and bugs introduced with CM's stuff, although CM has always been an enjoyable experience. Whoot for guys like you!
I know this is old thread... but what source tree are we talking about here? Obviously not AOSP itself, i think... right?
CM source?
Maybe i'm missing something about branches of AOSP... and other trees..
many thanks
mythos234 said:
After we finish the device tree and everything is working, it can be then used to build whatever Rom you desire
Click to expand...
Click to collapse
thenextdon13 said:
I know this is old thread... but what source tree are we talking about here? Obviously not AOSP itself, i think... right?
CM source?
Maybe i'm missing something about branches of AOSP... and other trees..
many thanks
Click to expand...
Click to collapse
They talked about device tree here. An example for a pure AOSP one for the device LG H815 is here:
https://github.com/cile381/android_device_h815
See this for an explanation :
http://wp.me/p6ZeCY-3p
AOSP source contains the sources to build a ROM which are the same for all devices and a device tree is a device specific description on how to build or as the above link states:
“A device tree is a tree data structure with nodes that describe the physical devices in a system”
.
Sent from my LG-H815 using XDA Labs
Thank you, steadfasterX.
That provides some clarity, although I think there is still a bit missing for me--
Ugh, i can't post links because of spam rules.. :-/ makes describing things harder.
How did you find the github cile381/android_device_h815 as being the AOSP tree for that phone? My understanding was that the AOSP main repo is here:
android.googlesource.com
And so related to my question previously.. i guess i'm confused specifically who the 'we' is that mythos234 references, and where that source would be located...
many thanks!
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.