Here is my build of LineageOS 13.0 for the Galaxy S4 LTE A. It is based on the pure LineageOS code unless indicated otherwise.
* IMPORTANT *
Please note that these builds are based on nothing else than the unchanged official code from LineageOS. So every credit goes to the ones providing the code.
I will not and cannot make any changes to the code. The only thing I can do and will do is build the ROM.
Also, it should be understood that I take no responsibilities whatsoever if anything goes wrong when you install the ROM. Like any custom ROM this is completely at your own risk!
However, you can expect that any ROM I share has been installed on my own GT-I9506 (starting with the latest official Samsung firmware 5.0.1) and runs without obvious issues. Your mileage may vary.
https://www.mediafire.com/?c8q4lqh675hc97b,7dhley6dl6j9dnb
Based on LineageOS official code up to https://review.lineageos.org/154230
Which modem and boot loader can you recommend?
audianer said:
Which modem and boot loader can you recommend?
Click to expand...
Click to collapse
I flashed the latest official Samsung firmware to prepare for LineageOS 13.0
I'm trying to build the latest version, which does build without error, but upon booting gets stuck at starting the apps, i.e. just before showing the lock screen. The latest working build was from January 5th 2017 and I experienced the error first on a build of January 8th 2017. So I suspect the commit in question is one from January 6-8.
Before I'm forced to manually investigate commit-by-commit from the latest working version, does anyone know what has changed that causes this error? I was not able to get any output from adb logcat either, so I have no idea what went wrong... which is rather frustrating.
What device tree and kernel did you use?
DualJoe said:
What device tree and kernel did you use?
Click to expand...
Click to collapse
The same as the working previous build: LineageOS/android_kernel_samsung_ks01lte & LineageOS/android_device_samsung_ks01lte. As far as I can see nothing in the kernel or device tree has changed, thus it must be some incompatibility with the rest of the LineageOS code.
I just tried another build just an hour ago, same result: stuck at the final starting apps (before the vibration). I also tried reverting to a working state of the source (of January 5) by using "repo forall -c 'git checkout `git rev-list --all -n1 --before=", but that one didn't even build.
I would appreciate any help here. It's not like there were some exhaustive documentation about how to build LineageOS. And anyway, apparently building is not the issue here.
If that's still Solk2's stuff it might be very old indeed.
DualJoe said:
If that's still Solk2's stuff it might be very old indeed.
Click to expand...
Click to collapse
No. It seems that @solk2 has started to develop the ks01lte again. See the github commits:
https://github.com/LineageOS/android_kernel_samsung_ks01lte/tree/cm-13.0
https://github.com/solk2/android_kernel_samsung_ks01lte/commits/cm-13.0
https://github.com/LineageOS/android_device_samsung_ks01lte/tree/cm-13.0
https://github.com/solk2/android_device_samsung_ks01lte/commits/cm-13.0
(Note: There is no cm14.1 branch on @solk2's github repo yet.)
WeirdSoup said:
No. It seems that @solk2 has started to develop the ks01lte again. See the github commits:
https://github.com/LineageOS/android_kernel_samsung_ks01lte/tree/cm-13.0
https://github.com/solk2/android_kernel_samsung_ks01lte/commits/cm-13.0
https://github.com/LineageOS/android_device_samsung_ks01lte/tree/cm-13.0
https://github.com/solk2/android_device_samsung_ks01lte/commits/cm-13.0
(Note: There is no cm14.1 branch on @solk2's github repo yet.)
Click to expand...
Click to collapse
Uhm... There are cm-14.1 branches too.
zardak said:
Uhm... There are cm-14.1 branches too.
Click to expand...
Click to collapse
I said "@solk2's repo".
And as you can see, there are no additional commits on CM14.1 branch in LOS's ks01lte device repo, compared to cm13.
WeirdSoup said:
I said "@solk2's repo".
And as you can see, there are no additional commits on CM14.1 branch in LOS's ks01lte device repo, compared to cm13.
Click to expand...
Click to collapse
Well, solk2 started to push changes on his kernel's repo days ago, even on cm-14.1 branch.
Anyway, I think is just a matter of time. We'll get official builds sooner or later.
I just don't understand why solk2, kyasu, and possibly gugu0das and others don't collaborate all together to only one kernel/device for this phone
zardak said:
Well, solk2 started to push changes on his kernel's repo days ago, even on cm-14.1 branch.
Anyway, I think is just a matter of time. We'll get official builds sooner or later.
Click to expand...
Click to collapse
Oh, I'm sorry. I misstated. I mean, the "device" repo. (https://github.com/solk2/android_device_samsung_ks01lte/commits/cm-13.0)
zardak said:
Well, solk2 started to push changes on his kernel's repo days ago, even on cm-14.1 branch.
Anyway, I think is just a matter of time. We'll get official builds sooner or later.
I just don't understand why solk2, kyasu, and possibly gugu0das and others don't collaborate all together to only one kernel/device for this phone
Click to expand...
Click to collapse
It looks like a waste of time and work, doesn't it? There is no point in having 3 or more different builds with no particular differences. Devs might want to join the official repos instead and make their changes there.
zardak said:
It looks like a waste of time and work, doesn't it? There is no point in having 3 or more different builds with no particular differences. Devs might want to join the official repos instead and make their changes there.
Click to expand...
Click to collapse
You are absolutely right. I dont know, maybe they have reasons not to join the LineageOS team, but when I got my S4 I was rather confused with all this different versions. I mean for many devices you get unofficial builds with extra features/improvements, but for the I9506 its hard to tell the differences. However at the moment I would say the build by gugu0das is the best, but it looks like he is not going to update it anymore. So yes, it would be great to have all those talented developers out there working on the same repos.
PixelChris95 said:
So yes, it would be great to have all those talented developers out there working on the same repos.
Click to expand...
Click to collapse
I believe this is some sick "if you don't figure it out yourself, you're not supposed to know how to do it" attitude of some (most?) developers. Or another symptom of "not invented here" syndrome.
If LineageOS official builds are available I will surely not waste time to build it myself, but in the meantime I would like to be up-to-date. So still, anyone pointing me to information how to do it is very welcome.
zardak said:
Well, solk2 started to push changes on his kernel's repo days ago, even on cm-14.1 branch.
Anyway, I think is just a matter of time. We'll get official builds sooner or later.
I just don't understand why solk2, kyasu, and possibly gugu0das and others don't collaborate all together to only one kernel/device for this phone
Click to expand...
Click to collapse
I think the same of you. It could be better for all of us to make a ROM with the best of their ROMs.
JohnMcClane1htc said:
I think the same of you.
Click to expand...
Click to collapse
What do you think? That I do not share what I do? I have provided a ROM for i9506 based on cyanogenmod 11.0 for a long, long time, as well as one for Nexus 7. And I have always made clear from where the sources for those builds came. Perfect transparency, don't you think?
It is because of disrespectful people like you that developers (and people like me, because I am not a developer) stop sharing!
NeuDLi said:
What do you think? That I do not share what I do? I have provided a ROM for i9506 based on cyanogenmod 11.0 for a long, long time, as well as one for Nexus 7. And I have always made clear from where the sources for those builds came. Perfect transparency, don't you think?
It is because of disrespectful people like you that developers (and people like me, because I am not a developer) stop sharing!
Click to expand...
Click to collapse
If my comment has offended you, I apologize. My comment doesn't want to disparage anyone. And I recognize the effort of the developers because, although I am not, I know how difficult it must be to develop a ROM.
If my comment has offended you, I apologize. I am sorry.
I also create content in Htcmania and always share and show the sources. I only would want to say that sometimes, when finding so many ROMs based on CM, it can be difficult to decide for one or the other, since the changes between them are very subtle.
Regards
Maintaining/creating roms is usually the way people learn Linux, Android, compiling, git and such. That's why there are so many one-man projects. Once they are into it most vanish again/go over to other stuff though. Only few people keep over long time like Temasek. In the end there can't be enough roms. More options are always better than none. As long as people are posting the source code for other people to pick up they do work together already.
Related
Could someone educate me on what it takes to get CM 12.1 on to the S2?
I understand that you have to root, install TWRP, and flash the ROM but who actually puts together CM 12.1 rom together and makes it compatible for the S2? Is it the official CM team or a developer on this forum who takes the time and energy to put it all together?
Thank you for your help in educating me......
There is no Cyanogen for our tablet for the moment
You can check here : http://download.cyanogenmod.org/
So it is the CM Team that takes the time, energy, and resources to put it together for the S2?
I will keep an eye on the CM website and hope they put something together soon. I wish I had someway to contribute but my skill set is very limited.
Thanks
Dekan54 said:
So it is the CM Team that takes the time, energy, and resources to put it together for the S2?
I will keep an eye on the CM website and hope they put something together soon. I wish I had someway to contribute but my skill set is very limited.
Thanks
Click to expand...
Click to collapse
No.. it takes someone with enough knowledge to build it for our hardware. I've never done it, but I'm attempting. Learning as I go... emphasis on attempting.
Okay - That makes sense.... I will help test if you get to that point.
Would be nice with cm12 but probably with lots of drawbacks. Samsung won't release source code of drivers and could be problematic with exynos nor will fingerprintscanner work.
BigBot96 said:
No.. it takes someone with enough knowledge to build it for our hardware. I've never done it, but I'm attempting. Learning as I go... emphasis on attempting.
Click to expand...
Click to collapse
You may want to ask @eousphoros for help. He got it rolling on the the tab s I bet he could help you big time!
BigBot96 said:
No.. it takes someone with enough knowledge to build it for our hardware. I've never done it, but I'm attempting. Learning as I go... emphasis on attempting.
Click to expand...
Click to collapse
Good to hear someone is working on it. ?
Sent from my not-so-stock SM-T810
CM is always buggy and lots of features wont work or plain buggy. Bloat is very minimal and works quite smoothly stock. Dont blame you if you like the "fun" of constantly flashing roms and waitkng for bug fixes.
Dekan54 said:
Could someone educate me on what it takes to get CM 12.1 on to the S2?
I understand that you have to root, install TWRP, and flash the ROM but who actually puts together CM 12.1 rom together and makes it compatible for the S2? Is it the official CM team or a developer on this forum who takes the time and energy to put it all together?
Thank you for your help in educating me......
Click to expand...
Click to collapse
Hey there. As a dev myself I will explain you the difference between official CM builds (build = the ROM) and unofficial builds. Official builds are made by the pros. The guys that are in the CyanogenMod group. They know how things work and patch them due their high knowledge. They will try to update the ROM regularly and fix it as well as they can. Then there are the unofficial builds from people like me. It depends what your skills are and with what board you are working (Exynos is a pain in the ass). Not to forget what version of android your device is currently running. Unofficial builds can be buggy and could take some time to get fixed. However devs will listen to the feedback of the community too.
I recently decided to do some personal builds of CM for the OnePlus 3. I have seen that the other threads are not updating their builds since they are the ones working on them. I am simply sharing the current builds from the CyanongenMod Repos. I did not do any of the development work and I will kill this thread the moment we get official nightly builds. I am not responsible for anything that may happen and I do not care what does and does not work. You are deciding to flash this ROM. Bugs can be reported to the CM devs but include a logcat or GTFO.
Link to build folder - https://www.androidfilehost.com/?w=files&flid=74080
Instructions:
1. Unlock Bootloader
2. Flash TWRP
3. Fastboot format userdata
4. Boot into TWRP
5. Flash ROM
6. Flash GAPPS
7. Reboot
Thanks for making another ROM for our OP 3
papi92 said:
I recently decided to do some personal builds of CM for the OnePlus 3. I have seen that the other threads are not updating their builds since they are the ones working on them. I am simply sharing the current builds from the CyanongenMod Repos. I did not do any of the development work and I will kill this thread the moment we get official nightly builds. I am not responsible for anything that may happen and I do not care what does and does not work. You are deciding to flash this ROM. Bugs can be reported to the CM devs but include a logcat or GTFO.
Link to build folder - coming soon (waiting on AFH approval)
Instructions:
1. Unlock Bootloader
2. Flash TWRP
3. Fastboot format userdata
4. Boot into TWRP
5. Flash ROM
6. Flash GAPPS
7. Reboot
Click to expand...
Click to collapse
Hehe thanks for this Started building them as well but don't really know how, so made a little guide for others like me Feel free to share your knowledge if you want
build is up
papi92 said:
build is up
Click to expand...
Click to collapse
Downloading...
_MartyMan_ said:
Downloading...
Click to expand...
Click to collapse
Thanks
Thanks for doing this dude. Going to download now. Can finally ditch OOS.
Sent from my ONEPLUS A3000 using Tapatalk
Wooohoo! Everything is working Good job!
_MartyMan_ said:
Wooohoo! Everything is working Good job!
Click to expand...
Click to collapse
Does VoLTE work? I haven't stuck in my T-Mobile SIM lol and i didn't do anything so no thanks to me. It's all @Grarak and @Romanbb
Not trolling but we dont need several twrp, cm, resurrection and so on rom threads here. I believe the mods starting closing these. Not discouraging you from building but several threads just confuse people.
Nah mods don't close it, maybe move it.
It's a nightly build from cm13, did u see a nightly build around? Nope.
Good work, fastest cm13 build around, good to have some nightlys around. Thanks
fix-this! said:
Not trolling but we dont need several twrp, cm, resurrection and so on rom threads here. I believe the mods starting closing these. Not discouraging you from building but several threads just confuse people.
Click to expand...
Click to collapse
These are nightlies. I'm more than happy to close once CM sends the OnePlus into Jenkins.
I really hope this thread doesnt get closed till we see official builds. I know some devs might be mad about this. But since you dont ask for any reward for compiling these builds its ok.
nadejo said:
I really hope this thread doesnt get closed till we see official builds. I know some devs might be mad about this. But since you dont ask for any reward for compiling these builds its ok.
Click to expand...
Click to collapse
Yeah not my work at all. Nor would I pretend it is. Way over my head
So anyone confirm VoLTE is working? I want to switch to T-Mobile once it does.
nadejo said:
I really hope this thread doesnt get closed till we see official builds. I know some devs might be mad about this. But since you dont ask for any reward for compiling these builds its ok.
Click to expand...
Click to collapse
Tbh i dont think alot of devs even have the device in hand yet. thats why im running stock rooted. no offense to the op, wasnt my intention. just been seeing alot of the same threads pop up and its confusing and uneeded. im sure these nightlies are appreciated.
Put up a second build. I saw some commits to snap and wanted to share.
Possible to link the source?
Not that I know where it is, but I'm to lazy to search all the time.
Only thing I noticed is the battery drain compared to stock, not a big one, maybe it need to settle a little.
1 hour SOT 21% on cm
1 hour SOT 14-16% on stock.
Lets see how it settle.
Edit:
Compared to others Roms who looks like they are on a older source, it's running like it should, compared to stock min. the same smoothness, maybe even better.
And I can't test lte because I only have a h+
secXces_debaki said:
Possible to link the source?
Not that I know where it is, but I'm to lazy to search all the time.
Only thing I noticed is the battery drain compared to stock, not a big one, maybe it need to settle a little.
1 hour SOT 21% on cm
1 hour SOT 14-16% on stock.
Lets see how it settle.
Edit:
Compared to others Roms who looks like they are on a older source, it's running like it should, compared to stock min. the same smoothness, maybe even better.
And I can't test lte because I only have a h+
Click to expand...
Click to collapse
The source is just github.com/cyanogenmod
papi92 said:
Does VoLTE work? I haven't stuck in my T-Mobile SIM lol and i didn't do anything so no thanks to me. It's all @Grarak and @Romanbb
Click to expand...
Click to collapse
Sorry I can' test that
So I just installed this today, how often do security updates come out? It currently has Patch level May 1 2016. I'm guessing there are no OTA updates.
What about nightly updates? I guess I would have to use CM 13? I really dont know anything about this stuff besides what I learned today to install it.
10pmStalker said:
So I just installed this today, how often do security updates come out? It currently has Patch level May 1 2016. I'm guessing there are no OTA updates.
What about nightly updates? I guess I would have to use CM 13? I really dont know anything about this stuff besides what I learned today to install it.
Click to expand...
Click to collapse
I think Google updates the Android source code (AOSP) every day, anyone can take that code and build it for their devices. Custom ROMs are created by enthusiasts in their free time, and only they can update it. CM is a full time project that is maintained by a large team who work on it 24/7, and so, they can update it almost nightly.
Gus Ghanem said:
I think Google updates the Android source code (AOSP) every day, anyone can take that code and build it for their devices. Custom ROMs are created by enthusiasts in their free time, and only they can update it. CM is a full time project that is maintained by a large team who work on it 24/7, and so, they can update it almost nightly.
Click to expand...
Click to collapse
Alright thanks, so is the nexus experience the same as CM with it getting the same updates as everyone else, or is this more like a separate thing with separate updates? Are you on nexus experience? I'm not even sure if it's that popular.
10pmStalker said:
Alright thanks, so is the nexus experience the same as CM with it getting the same updates as everyone else, or is this more like a separate thing with separate updates? Are you on nexus experience? I'm not even sure if it's that popular.
Click to expand...
Click to collapse
NX ROM is based on AOSP, basically unmodified from what Google releases, which is similar to what comes on Google's Nexus Phones. CM modifies the AOSP code, adding it's own features and bug fixes to it. All Android ROMs use the same source code from Google, but each developer/maintainer has to do their own updates to their own ROM. Yes, NX and CM are seperate, and different. The NX maintainer has to keep adding the updates from the Google source code himself/herself, and that depends on the person having the time to do it. The same with CM, the developers/maintainers have to keep adding their own and Google's updates to it.
I've been using CM exactly because it's the most well maintained, supported, and updated version of Android you can get.
Gus Ghanem said:
NX ROM is based on AOSP, basically unmodified from what Google releases, which is similar to what comes on Google's Nexus Phones. CM modifies the AOSP code, adding it's own features and bug fixes to it. All Android ROMs use the same source code from Google, but each developer/maintainer has to do their own updates to their own ROM. Yes, NX and CM are seperate, and different. The NX maintainer has to keep adding the updates from the Google source code himself/herself, and that depends on the person having the time to do it. The same with CM, the developers/maintainers have to keep adding their own and Google's updates to it.
I've been using CM exactly because it's the most well maintained, supported, and updated version of Android you can get.
Click to expand...
Click to collapse
When you flash every new update, does it reset everything?
10pmStalker said:
When you flash every new update, does it reset everything?
Click to expand...
Click to collapse
No, it doesn't. I update to every nightly as soon as it's available from the built-in CM updater. All your installed apps, and settings remain as they were. After every update you will see app optimization during boot, but after the phone finishes booting, everything will be the same as it was.
Gus Ghanem said:
No, it doesn't. I update to every nightly as soon as it's available from the built-in CM updater. All your installed apps, and settings remain as they were. After every update you will see app optimization during boot, but after the phone finishes booting, everything will be the same as it was.
Click to expand...
Click to collapse
Awesome thanks. I might look into straight up CM and ditch this nexus experience.
Title says it all, anyone know? There's hasn't been builds for a long time now.
https://github.com/AOKP
https://github.com/PAC-ROM
Both appear to be making commits, not sure on if/when they plan to release anything.
Dopamin3 said:
https://github.com/AOKP
https://github.com/PAC-ROM
Both appear to be making commits, not sure on if/when they plan to release anything.
Click to expand...
Click to collapse
Thanks! For some reason didn't think to check their github, but it's good to know they're not 100% dead! Those have always been some of my favorite roms!
H4X0R46 said:
Thanks! For some reason didn't think to check their github, but it's good to know they're not 100% dead! Those have always been some of my favorite roms!
Click to expand...
Click to collapse
I personally can't wait for LiquidSmooth to make a return. I remember their 4.4 ROMs for a few devices I had and man, it ran great and the amount of features were second to none.
Hi, I am looking for a new ROM for my Mi Mix and thought that the Bliss Rom looks the most promising to me.
However, the thread has been closed by the author, @heindrix and moderator @gregbradley without explanation.
Anyone knows why it is closed and if the ROM is a dead-end?
Thanks!
pzkfwg said:
Hi, I am looking for a new ROM for my Mi Mix and thought that the Bliss Rom looks the most promising to me.
However, the thread has been closed by the author, @heindrix and moderator @gregbradley without explanation.
Anyone knows why it is closed and if the ROM is a dead-end?
Thanks!
Click to expand...
Click to collapse
Hi there,
It's glad to see that somebody still wants to use the rom i maintained some times ago.
Unfortunately i've been so busy in my job, and well i've switched device to OP6T, that's why i decided to close the thread down to prevent any long wait and further disappoinment for never-ending wait.
Last time i checked the Bliss Rom source, they already updated and patched many things i've done before, so i can tell you that the source already very dependable.
All you need is another dev to cook it using Lineage Tree, and all will be good. :fingers-crossed:
Thank you so much for your answer @heindrix!
Still, even if it is not the latest source code, is your latest build stable enough to be used day-to-day? The comments look good and there does not seem to be any major bug (like the proximity sensor, for example).
pzkfwg said:
Thank you so much for your answer @heindrix!
Still, even if it is not the latest source code, is your latest build stable enough to be used day-to-day? The comments look good and there does not seem to be any major bug (like the proximity sensor, for example).
Click to expand...
Click to collapse
if i remember, the last build fairly good but can be improved. last time i've build the new update but i've deleted it and forgot to post it, lol.
i suggest you use rom build by inkypen. :fingers-crossed:
SyberiaOS I suppose? (there are at least two)
So, I actually tried first to install Bliss and it is so nice that I don't see any reason to try another one! Thanks @heindrix !
Maybe there is something I am missing about what can provide an actively maintained ROM?
pzkfwg said:
So, I actually tried first to install Bliss and it is so nice that I don't see any reason to try another one! Thanks @heindrix !
Maybe there is something I am missing about what can provide an actively maintained ROM?
Click to expand...
Click to collapse
yeah, actually the rom from Bliss Team is very nice, it's full of features, and it's still my favorite team until now.
you can learn to build the rom and maintain it, there's so many tutorial and threads and telegram groups that will help you learn how to build a rom.
heindrix said:
Hi there,
It's glad to see that somebody still wants to use the rom i maintained some times ago.
Unfortunately i've been so busy in my job, and well i've switched device to OP6T, that's why i decided to close the thread down to prevent any long wait and further disappoinment for never-ending wait.
Last time i checked the Bliss Rom source, they already updated and patched many things i've done before, so i can tell you that the source already very dependable.
All you need is another dev to cook it using Lineage Tree, and all will be good. :fingers-crossed:
Click to expand...
Click to collapse
Congrats on your new job! I know its pretty late to ask, but will you work on porting drivers for Adreno 630 now?