Related
I've been using Codename ever since it came out but I got tired of the problems related to the Kernel and switched to ProjectX. I and I'm sure others really want to use a smooth and working JB ROM.
Is there anyone working on the 3.0 Kernel for our device? I know Nik said he contacted someone to help us out but there's been no news on that front yet.
If anyone knows how to modify Kernels, Adi_pat gave some tips here -
http://forum.xda-developers.com/showthread.php?p=33291894
He'll probably help us out if we make some progress in booting up Codename with it at least
TheDareDevil said:
I've been using Codename ever since it came out but I got tired of the problems related to the Kernel and switched to ProjectX. I and I'm sure others really want to use a smooth and working JB ROM.
Is there anyone working on the 3.0 Kernel for our device? I know Nik said he contacted someone to help us out but there's been no news on that front yet.
If anyone knows how to modify Kernels, Adi_pat gave some tips here - http://forum.xda-developers.com/showthread.php?t=1899335&page=38
He'll probably help us out if we make some progress in booting up Codename with it at least
Click to expand...
Click to collapse
Upon the exit of JB roms ago, were used GB modified kernel, now with source code maybe will be possible to compile a fully working kernel, but afaik there are no 3.x kernel for JB, maybe someone is working out of xda on irc channel but don't known..
Sadly I do not have much competence, plus I don't have the phone it's to repair....
There is kernel 3 for incredible 2 and desire s..may be someone can port it..
Sent from my HTC Incredible S using xda app-developers app
I might be crazy, but I remember reading a post not too long ago about a dev that was writing the 3.0 kernel from source for our phones. I haven't heard an update since then, but I remember hearing it was someone with relation to the cm9 team. It sounded promising, but that development was very slow.
Sent from my HTC Incredible S using xda app-developers app
TheMegosh said:
I might be crazy, but I remember reading a post not too long ago about a dev that was writing the 3.0 kernel from source for our phones. I haven't heard an update since then, but I remember hearing it was someone with relation to the cm9 team. It sounded promising, but that development was very slow.
Sent from my HTC Incredible S using xda app-developers app
Click to expand...
Click to collapse
Off the top of my head I seem to recall Noverbose saying he was trying to write a 3.0 Kernel. I also remember at least one other person mentioning something similar to, so there are people working on this. From what I understand it's not easy - I doubt we'll see anything this side of Christmas tbh. I hadn't realised that the Inc 2 and DS had a 3.0 Kernel though. Anyone know if they are actually a made from source version, rather than the same hacked version that we have in Codename, for example?
Well tbh honest a working GB kernel would do too.
Like the front camera and chrome and screen flickering etc.
Damn I wish kaijura was here
Sent from my HTC Incredible S using xda app-developers app
CyanideJack said:
Off the top of my head I seem to recall Noverbose saying he was trying to write a 3.0 Kernel. I also remember at least one other person mentioning something similar to, so there are people working on this. From what I understand it's not easy - I doubt we'll see anything this side of Christmas tbh. I hadn't realised that the Inc 2 and DS had a 3.0 Kernel though. Anyone know if they are actually a made from source version, rather than the same hacked version that we have in Codename, for example?
Click to expand...
Click to collapse
Yes those 3.0 kernels are compiled from source. I checked out AOSP ROM threads in the Desire S and Inc 2 section that had 3.0 kernel, then looked up the creator of the ROM on github and found the sources. I was going to try tackle the 3.0 kernel to get a hang of the make system before building CM9, but I don't have enough monthly data left to download the kernel toolchain! Nov 1st is close, so I can get to work soon! :highfive:
The best way to build an AOSP 3.0 kernel for our device would probably be to look at the source code for 3.0 kernels on our sister devices, and figure it out from there.
ZaySk said:
Yes those 3.0 kernels are compiled from source. I checked out AOSP ROM threads in the Desire S and Inc 2 section that had 3.0 kernel, then looked up the creator of the ROM on github and found the sources. I was going to try tackle the 3.0 kernel to get a hang of the make system before building CM9, but I don't have enough monthly data left to download the kernel toolchain! Nov 1st is close, so I can get to work soon! :highfive:
The best way to build an AOSP 3.0 kernel for our device would probably be to look at the source code for 3.0 kernels on our sister devices, and figure it out from there.
Click to expand...
Click to collapse
Well holy crap, dude, get on that! Seriously though, getting a working 3.0 kernel for our device would go a long way to making JB a usable ROM for our device. Would it be possible to port JellyTime or a similar JB ROM to our device as well?
The source doesn't need changing, it is the ramdisk that is the problem. I have been trying to get help, but so far no luck, adi_pat said he would take a look, but it is hard for me to test as I no longer have an inc s
CyanideJack said:
Well holy crap, dude, get on that! Seriously though, getting a working 3.0 kernel for our device would go a long way to making JB a usable ROM for our device. Would it be possible to port JellyTime or a similar JB ROM to our device as well?
Click to expand...
Click to collapse
I'm gonna worry mainly about compiling CM9 from source once November hits, that's gonna take up the majority of my time. After I get the first release of CM9 out, I'll start work on a 3.0 kernel if it hasn't been done yet. I have no experience whatsoever dealing with kernels though, except for small ramdisk edits, so don't expect any miracles.
It should be possible to port other JB ROM's over using one of nik's ported JB ROM's as a base and reference point, the only problem is I don't know exactly what files I have to substitute to port a ROM. I've PM'd nik about that a few hours ago, so hopefully I'll get some more information on the subject. Nik has been a big help to my dev efforts as a whole.
l0st.prophet said:
The source doesn't need changing, it is the ramdisk that is the problem. I have been trying to get help, but so far no luck, adi_pat said he would take a look, but it is hard for me to test as I no longer have an inc s
Click to expand...
Click to collapse
Interesting, if it's only the ramdisk that needs changing, couldn't you look at the ramdisk from one of niks JB ROM's? Or is it not as simple as that? I'm assuming the latter, seeing as if it were that obvious I'm sure someone would've done it by now. If you ever need help testing, send me a PM I'd be more than willing to test for you.
ZaySk said:
I'm gonna worry mainly about compiling CM9 from source once November hits, that's gonna take up the majority of my time. After I get the first release of CM9 out, I'll start work on a 3.0 kernel if it hasn't been done yet. I have no experience whatsoever dealing with kernels though, except for small ramdisk edits, so don't expect any miracles.
It should be possible to port other JB ROM's over using one of nik's ported JB ROM's as a base and reference point, the only problem is I don't know exactly what files I have to substitute to port a ROM. I've PM'd nik about that a few hours ago, so hopefully I'll get some more information on the subject. Nik has been a big help to my dev efforts as a whole.
Interesting, if it's only the ramdisk that needs changing, couldn't you look at the ramdisk from one of niks JB ROM's? Or is it not as simple as that? I'm assuming the latter, seeing as if it were that obvious I'm sure someone would've done it by now. If you ever need help testing, send me a PM I'd be more than willing to test for you.
Click to expand...
Click to collapse
About using one of Nik's JB roms as a reference
What I understood was that the rom has been built around the old 2.6.x kernel and has to be modified again to work with the 3.0.x kernel, if you guys get one up and running. If that is the case, wouldn't you be going down the wrong path if you model it around nik's existing 2.6.x roms?
We need kaijura here, he was our AOSP kernel master. Hopefully he is doing ok, and has found something else other than xda because he hasn't been online for months. At least other devs, like lordclokan and kali- have moved on and are active with other devices... kaijura hasn't been on at all. Anyone been in contact with him/her?
markj338 said:
About using one of Nik's JB roms as a reference
What I understood was that the rom has been built around the old 2.6.x kernel and has to be modified again to work with the 3.0.x kernel, if you guys get one up and running. If that is the case, wouldn't you be going down the wrong path if you model it around nik's existing 2.6.x roms?
We need kaijura here, he was our AOSP kernel master. Hopefully he is doing ok, and has found something else other than xda because he hasn't been online for months. At least other devs, like lordclokan and kali- have moved on and are active with other devices... kaijura hasn't been on at all. Anyone been in contact with him/her?
Click to expand...
Click to collapse
I know, it would be going down a pretty redundant path. If I was able to port over a JB ROM using nik's ROM's as a base, then my ported ROM would inherit all the same bugs nik's ROM's already have.
I wish kaijura was still around, I have so many questions I want to ask about compiling from source! Luckily lordclokan was a massive help to me in that regard. Kaijura's github hasn't seen action in months either, sadly.
Forgive my ignorance, but isn't the Desire HD essentially our device with a bigger screen and less memory? That being the case, could we not just port across one of the 3.0 Kernels from that?
The problem with the ramdisk that come with the official ROM's that have 3.0 kernels, is that they are built for the sense framework and don't work on AOSP ROM's. The ram disk that is included with Nik's JB ROM's is heavily modified to run a GB kernel with ICS / JB sources, so the problem is I don't have a base to work from, I am basically trying to merge the two init's to make the 3.0 kernel boot.
Saying that we need to port 3.0 kernel is probably a bit misleading, and for that I apologise, the kernel itself has very little Sense specific stuff, it's the ramdisk that is responsible for launching the kernel that is the issue here at the moment.
The only problem with the desire HD kernel would be that our front camera would not work
+ I forgot to link to adi_pat's post - http://forum.xda-developers.com/showthread.php?p=33291894
Sent from my HTC Incredible S using xda app-developers app
l0st.prophet said:
The problem with the ramdisk that come with the official ROM's that have 3.0 kernels, is that they are built for the sense framework and don't work on AOSP ROM's. The ram disk that is included with Nik's JB ROM's is heavily modified to run a GB kernel with ICS / JB sources, so the problem is I don't have a base to work from, I am basically trying to merge the two init's to make the 3.0 kernel boot.
Saying that we need to port 3.0 kernel is probably a bit misleading, and for that I apologise, the kernel itself has very little Sense specific stuff, it's the ramdisk that is responsible for launching the kernel that is the issue here at the moment.
Click to expand...
Click to collapse
Well you can prolly get ideas from adi ( he posted http://forum.xda-developers.com/showpost.php?p=33302707&postcount=387 not sure if you saw it) he seems to know what's up.
TheDareDevil said:
The only problem with the desire HD kernel would be that our front camera would not work
+ I forgot to link to adi_pat's post - http://forum.xda-developers.com/showthread.php?p=33291894
Sent from my HTC Incredible S using xda app-developers app
Click to expand...
Click to collapse
So it looks like the furthest things got regarding a 3.0 Kernel was;
Adi_Pat said:
chan
Ok so 2.6.35 works with Jellybean. Why not pack the ramdisk with zImage compiled from 3.0.y sources(Considering you are using standard boot.img format[?]) Because to get it to boot, you would not require any hacks/changes to source, editing ramdisk(init.rc) is enough to make it boot initally.
EDIT: You may also need to change init binary.
Click to expand...
Click to collapse
l0st.prophet said:
The problem with the ramdisk that come with the official ROM's that have 3.0 kernels, is that they are built for the sense framework and don't work on AOSP ROM's. The ram disk that is included with Nik's JB ROM's is heavily modified to run a GB kernel with ICS / JB sources, so the problem is I don't have a base to work from, I am basically trying to merge the two init's to make the 3.0 kernel boot.
Saying that we need to port 3.0 kernel is probably a bit misleading, and for that I apologise, the kernel itself has very little Sense specific stuff, it's the ramdisk that is responsible for launching the kernel that is the issue here at the moment.
Click to expand...
Click to collapse
Very interesting, thanks for the informative post. :good:
zaysk said:
very interesting, thanks for the informative post. :good:
Click to expand...
Click to collapse
happy november!!!
markj338 said:
happy november!!!
Click to expand...
Click to collapse
A very happy November indeed
Just wondered if anyone could list me the kernels used in AOKP M7ul, PACrom and ReVolt. I'm running test builds of Lord Clockans IceCold ROM but we are having problems getting Bluetooth and NFC running. Having checked sources for both these against AOKP and CM10.1 everything seems to match.
LC thinks its something missing from source but I want to double check this avenue.
I'm no coder though just a layman looking to help so if I'm barking up the wrong tree let me know.
I can link ICJ source on GitHub if needed and to the ROM test folder if anyone has any ideas to help solve this.
Sent from my HTC One using xda premium
Does anyone know of a current AOSPA for this device? I can't seem to find one anywhere!
If not, I have been wanting to build a rom, does anyone know of the correct sources for it?
I asked @cj360 about it since he's already started building for his XT926, and once he gets it stable on there, he'll start building for all the other devices in the family.
As for building it yourself, AOSPA sources are here and our sources are here.
Sent from my MB886 using Tapatalk
penser said:
I asked @cj360 about it since he's already started building for his XT926, and once he gets it stable on there, he'll start building for all the other devices in the family.
As for building it yourself, AOSPA sources are here and our sources are here.
Sent from my MB886 using Tapatalk
Click to expand...
Click to collapse
Thanks so much! Now if only LiquidSmooth was on KitKat!
It is on KitKat and there are files for mb886. Search and you find it
http://forum.xda-developers.com/showthread.php?p=48918250
TecknoFreak said:
It is on KitKat and there are files for mb886. Search and you find it
http://forum.xda-developers.com/showthread.php?p=48918250
Click to expand...
Click to collapse
Thanks man, sorry I didn't search as well as I should have!
No problem mate is hard to see something you will think it will be here posted but this ROM doesn't have its own developing thread for our device for any reason that be.
Alright folks.
As users of Mahdi-Rom have noticed, Dr87 has been awhile on updates. From reading people say he's stated that he's ceased development for the G2 until Android L drops. Given that, I've began working on my on builds of this rom as well as major modfiications to his base kernel based on Dorimanx's Stock kernel. I had tried Bart452's and the audio patch never worked quite right in all apps. It's also lacking hardware acceleration for video on this rom for some reason.
ALL FILES POSTED HERE ARE "AS-IS". THEY SHOULD ALL BE CONSIDERED EXPERIMENTAL.
I don't plan on providing support, adding devices, changing features. These will simply be builds of the ROM based off of a repo sync ... Nothing more, Nothing Less. These are being made based on the Mahdi 4.4.3-CAF repo source. This may or may not be the correct one, but it boots and seems to work on my device. This then gets the sources from Dr87's upgrade guide added in. lunched as VS980 (my device) and the OTApackage made.
If anyone has any tips/recommendations for better places to pull the source from (if there's a more appropriate one).... OR if there a better place to pull individual portions of the ROM from in the manifest, I'm all ears.
As far as my kernel modifications, I'll just be calling it "SimpleKernel+". I may end up talking to Dorimanx to get his blessing to keep the name, as I don't want to steal his credit or work, but also don't want to cause confusion either. This may take some time to start releasing builds of. For the time being, I've just mass-reverted some of one of Bart452's old ports of Dorimanx's kernel. I would only release for the VS980, as thats my device. But it's pretty quick to build for the others and repack them.
I don't want to sound rude or anything like that. But for the people that don't bother reading... I'm not a dev, I'm not maintaining this, I'm not coding for it. So posting feature requests and such will most likely go ignored.
I'm syncing sources and building. For the kernel, I'm picking commits and building. Most all commits to the kernel will probably come from Dorimanx's repo. I just don't feel right keeping the name when I'm not taking *all* his commits, as I'm going to avoid things for sound and video.
All coding has been done by Dr87 and Dorimanx and all the people they thank in their threads.
Links:
Rom:
a18dbeadb32b0e398116de5f5571af20 mahdi_vs980-20OCT2014.zip
Kernels: Github for this Dori Port
307cbb08c7c4f4a733b3223d38280546 Dorimanx-v7.8-d800-kernel-Nexus_Sound.zip
09e66f4ee8f27b14bc818dae6f957696 Dorimanx-v7.8-d801-kernel-Nexus_Sound.zip
434eeaee1ea4a040d6f3fbff0fcf7d71 Dorimanx-v7.8-d802-kernel-Nexus_Sound.zip
a89518e7eae55bc1285e628f0b93f3b7 Dorimanx-v7.8-d803-kernel-Nexus_Sound.zip
3a798dfdff9d916c07b256edc587c629 Dorimanx-v7.8-ls980-kernel-Nexus_Sound.zip
32e8b3e929104741cd5589dcea4e68d0 Dorimanx-v7.8-vs980-kernel-Nexus_Sound.zip
Also, for anyone curious. This should work with fauxsound as it has his mods in it, the STweaks app that's included actually has a volume boost bit in it. Also, cf.Lumen 2.40 *will* work with this rom/kernel combo. You just need to prevent it from updating, as newer version do not work with it.
Known issues :
Kernel Video playback doesn't use hardware modes. This prevents using Netflix. I'll investigate into this.
Some proximity issues.
*saved*
Awesome going to try this out
Sent from my LG-D800 using Tapatalk
Well, this is exciting!
Sent from my LG-VS980 using Tapatalk 2
why does the ROM .zip name include vs980? we download that one appropriate kernel?
MarioMoPho said:
why does the ROM .zip name include vs980? we download that one appropriate kernel?
Click to expand...
Click to collapse
Sorry, I left it out of the op..
You NEED to flash the associated patch still from the official thread.
I build these for my device, hence the name. I only share them because, why not....
Sent from my LG-VS980 using XDA Free mobile app
Yoinx said:
Sorry, I left it out of the op..
You NEED to flash the associated patch still from the official thread.
I build these for my device, hence the name. I only share them because, why not....
Sent from my LG-VS980 using XDA Free mobile app
Click to expand...
Click to collapse
Been running on d803 flawlessly since you first posted it, even dirty flashed over d87s last build. Thanks for putting out builds while Dr seems fairly busy which I fully understand as I built and maintained on the i717 for 2 years.
Yoinx said:
*saved*
Click to expand...
Click to collapse
Same here, going to try this one!
Thanks.
For some odd reason I couldn't get 4g data to connect for the vs980 ...maybe bad download idk...I did full wipe and flashed 2 separate times and no go either time...anyone else have the same issue?
Nugg14 said:
For some odd reason I couldn't get 4g data to connect for the vs980 ...maybe bad download idk...I did full wipe and flashed 2 separate times and no go either time...anyone else have the same issue?
Click to expand...
Click to collapse
Did you flush dr87's patch from his thread? That step is still required.
Works on my vs980 but I know someone else reported similar
Sent from my LG-VS980 using XDA Free mobile app
Yoinx said:
Did you flush dr87's patch from his thread? That step is still required.
Works on my vs980 but I know someone else reported similar
Sent from my LG-VS980 using XDA Free mobile app
Click to expand...
Click to collapse
I did not...Duh....LOL Thanks again
Thanks for this. I havent been on AOSP for a while since Mahdi wasnt getting updated. You rock!!!
Great, THX! On Ls980 until all well.
Has DSB been merged?
Commits:-
Change I3bc7102b: https://gerrit.paranoidandroid.co/4787
Change Id2b105df: https://gerrit.paranoidandroid.co/4788
varund7726 said:
Has DSB been merged?
Commits:-
Change I3bc7102b: https://gerrit.paranoidandroid.co/4787
Change Id2b105df: https://gerrit.paranoidandroid.co/4788
Click to expand...
Click to collapse
Does the official mahdi thread state it has been?
Lawlrus said:
Does the official mahdi thread state it has been?
Click to expand...
Click to collapse
Nope.but these are the unofficial builds so im guessing they will be merged soon
varund7726 said:
Nope.but these are the unofficial builds so im guessing they will be merged soon
Click to expand...
Click to collapse
Why would they? Per my op, I'm only syncing Mahdi repos and building with no modifications. They're unofficial because they agent built by Mahdi. They're unmaintained because I'm not going fixes, changes, or anything of the like. These are only up for people that don't build themselves.
Sent from my LG-VS980 using XDA Free mobile app
Seems 720p YouTube doesn't work for me. Anyone else? Or is this the same as the Netflix issue?
Yoinx said:
Why would they? Per my op, I'm only syncing Mahdi repos and building with no modifications. They're unofficial because they agent built by Mahdi. They're unmaintained because I'm not going fixes, changes, or anything of the like. These are only up for people that don't build themselves.
Sent from my LG-VS980 using XDA Free mobile app
Click to expand...
Click to collapse
Wait a minute, YOU EXPECT PEOPLE TO READ THE OP? SHAME ON YOU..... THATS PREPOSTEROUS!
/sarcasm
Ok, so after spending the last 4 or 5 days trying to shoe-horn Dorimanx's commits in on Dr87's base... through picks, rebases, reverts... etc... I gave up.
What this means, is that I'm abandoning trying to port his kernel to aosp. What I'll be doing is picking various things to improve the kernel, largely from faux123 on nexus5. This should give us a lot of benefit, with minimal issues. I'll also likely pull the nexus tree for mahdi, which i'd bet is what dr87 was building off of... given the similarity in the devices...
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.