Related
i actually have a very small question. am new to this forum and wish to know if our optimus black has any dedicated developer (like knzo) who is trying to port or make ROMs for the BLACK???....
i had an x10 mini b4 and i sold it to get this cell. now even the x10 mini (with it's paltry specs) has a working ICS build and i have a "cake on my face" feeling
i had a talk with MIUI about the support and they told me that our cell will get support by Q1 2012.
but as said, i was fancying a RAW UNCUSTOMIZED ICS flavor for our black...now, am NOT trying to create a spam thread about ICS or a hate thread about LG...
i just wanted to know whether any dev is working with our device??
P.S. - please don't kill me for asking this question.
i asked the admin for a dedicated "Q&A" forum, but nobody backed my request
waiting for your replies
Ricardo is our CM9 dev for LG devices.
this is his google plus:https://plus.google.com/115049428938715274412/posts
I dont think we have a dev for ICS ROM in XDA....
But aprold and knzo should be continuing Nova kernel from CM7 to CM9. so we just have to wait for Ricardo to finish his job!(i think still have some bugs left and camera not working)
EDIT: i think the only working ROMs we have are knzo's Nova ROM and Pay's ROM....and for kernel is Quasar kernel done by knzo and currently what i am using now CM7 #20 with knzo's Nova kernel for CM7(but the current dev has been transferred to aprold both of them are working together!) LG devices are kinda cold(i donnoe about LG O2X though pretty popular) so its not surprising to see that we have not much devs. LG peeps have been telling us that we will have our hands on official GB by November this year but i think none of us have the official GB on our phone yet(they fail in promises) that's why we are using CM7(GB) and waiting for CM9(ICS)
CalamitySir said:
Ricardo is our CM9 dev for LG devices.
this is his google plus:https://plus.google.com/115049428938715274412/posts
I dont think we have a dev for ICS ROM in XDA....
But aprold and knzo should be continuing Nova kernel from CM7 to CM9. so we just have to wait for Ricardo to finish his job!(i think still have some bugs left and camera not working)
Click to expand...
Click to collapse
+1, rick is the man
Sent from my heart into yours
Well we do have some senior members helping us on a number of occasions ranging from simple theming, modding and giving little guidance every now and when up to getting overclocking kernel , but only exclusive dev working on ics rom is Ricardo.
But hey till we get our basic requirements being helped, i 'm satisfied with that; and who knows any time a new dev could be coming just like aprold with kernel project and temasek with cherrypicked kangs... So, i 'm happy.
You can see my signature, i 've thanked a few of senior members in our forum here; a little gratitude from my side.
agent205 said:
+1, rick is the man
Sent from my heart into yours
Click to expand...
Click to collapse
officialreloaded said:
Well we do have some senior members helping us on a number of occasions ranging from simple theming, modding and giving little guidance every now and when up to getting overclocking kernel , but only exclusive dev working on ics rom is Ricardo.
But hey till we get our basic requirements being helped, i 'm satisfied with that; and who knows any time a new dev could be coming just like aprold with kernel project and temasek with cherrypicked kangs... So, i 'm happy.
You can see my signature, i 've thanked a few of senior members in our forum here; a little gratitude from my side.
Click to expand...
Click to collapse
yes...i have seen his profile in G+, thanks for the lead.
now, for those who want to gain some knowledge about porting or making AOSP ROMs,i have found a nice little tutorial for them...it's very juvenile and lucid. all you need is to run linux on your workstation. as of me, my idiot idiot brother formatted my workstation along with EVERY single DOCUMENT of mine!!!!
and am on an agonizingly slow bandwidth so cannot d/l ubuntu over again along with other necessities. i am uploading the pdf for your reference (if any1 of you are interested, that is)...all you need is ubuntu, VM/cygwin, git/source, patience and time there are loads of other guides if you are actually wanting to port a nice rom(or even thinking of making one)
(now, making a good,flawless,working ROM requires good knowledge about android and developing skills, yet u can give it a try )
once any1 starts the project and get stuck,post the work in DEV section and hopefully some of our knowledgeable senior members can take the lead
happy trying
RC said that CM10 should be finished about 2 weeks after source's are released. I hate to sound ungrateful for all the devs hard work, but why are there still so many bugs on custom roms?
Odp: If source and official ics is out, why are there still bugs?
Maybe because they are trying to tie ics with jb libraries, if you are so kind, just say: Sources! Repair all rooms! Et voila...
ignorance...
Sent from LG 2X using Tapatalk 3 Beta
Sorry, what I meant was, CM9, why are there bugs with custom ICS if source and official ROM is out?
If I'm not mistaken, what LG published was Kernel sources only. Source code for stuff such as HDMI, radio communications, etc., are not available so no one can really work on debugging ROM-related bugs without reverse-engineering everything.
Besides, we need to keep in mind that developing is something people like tonyp, pengus77, civato and others do on their free time out of passion, as a hobby. They have already done a lot of wonderful stuff, so I guess it is OK to live with a couple of minor bugs if all the major ones have been sorted out.
Hello to all,
The Maclawstudio have announced that they are working on kernel 3.0 for galaxy Ace / Gio.
All those who are interested to port this kernel by Ace / Gio in galaxy mini, please contact me.
I do not think it will be so difficult
Please contact me(pm) :highfive:
greetings
Ma-90 @
Request
Can u also port his cm10.1.
Venomstar said:
Can u also port his cm10.1.
Click to expand...
Click to collapse
Yes, but I do not think there is a need for mini already there
reported .....mods may close this thread..
and dude if you want help goto either general or q and a section.....
post here only when you are done with the project..
Nice idea.. i would really like to join you in that.. but, i hv no time till 16th may..
Can I join you after my exam which will end on 16th may. ?
OJ said:
Nice idea.. i would really like to join you in that.. but, i hv no time till 16th may..
Can I join you after my exam which will end on 16th may. ?
Click to expand...
Click to collapse
ofcourse
MaclawStudio just takes psyke83's work and again saying it's his. What a tool - same for everything else - taken from androidarmv6. And people still download his builds. Pathetic. Then keeps everything closed source (even the kernel, lol) so nobody can see that. x) Just haven't got enough words to describe this "developer"
i dont care if its stolen, remaked, rearanged, modified, etc...the truth is gonna come along with punishment (sound like Jehova whitness), as long as this 3 kernel works...
I don't know if you're aware of that, but erikcas is working on it since the day psyke83 ported it. He never brags about it. The problem is that Ace/Gio/Mini/Fit uses closed source FSR drivers which don't work on 3.x kernel (yet)
TheWhisp said:
I don't know if you're aware of that, but erikcas is working on it since the day psyke83 ported it. He never brags about it. The problem is that Ace/Gio/Mini/Fit uses closed source FSR drivers which don't work on 3.x kernel (yet)
Click to expand...
Click to collapse
So it is not necessary to port kernel since Erikcas already is working on it right?
Erikcas has been working on it for months. Galaxy 5 uses older FSR drivers which have open source package or SDK, not sure. The problem is that Mini/Ace/Gio/Fit uses newer version and that open source package is not working.
TheWhisp said:
Erikcas has been working on it for months. Galaxy 5 uses older FSR drivers which have open source package or SDK, not sure. The problem is that Mini/Ace/Gio/Fit uses newer version and that open source package is not working.
Click to expand...
Click to collapse
But if maclawstudio kernel port about Ace / Gio you can use them on our FSR galy mini, right?
Yes
I only leave this here:
bgm92 said:
Just shut up! Maclaw offered us more stable builds than you or other devs ever did! Show a little respect and stop denigrating him because he did a better job than you!
I really hope Maclaw won't release 3.x kernel sources so you won't steal his work and port it to other phones.
__________________________________________________
And one another important thing! How can you tell us he stoke psyke83's work? From where do you know? Have you got any proofs? How can you just speak like that? Again, just shut up - like a romanian proverb says: If you would shut up, you would remained a philosopher...
Click to expand...
Click to collapse
News flash bro ....Ever tried erikcas's builds please do if you didn't they are the most stable ones available.
also maclaw can/most likely isnt working on a source port for ace/gio but the truth of the matter is that would be sheer waste of time.Psyke83 already did the work,erikcas and wayland ace ported it to gio and ace respectively(they added their defconfigs and nessary parts) so it would be foolish of maclaw to start from scratch.
Also lets clarify he may/most likely is Kanging erikcas , wayland ace and psyke83 's work but since its open to all to build its not actually stealing(provided he gives credit but thats just good manners).
also the fsr module is a proprietary module(source code is not available) the one that psyke83 is using was leaked via a galaxy5 eclair kernel sources and still contained proprietary blobs(possibly that's the problem area).
Erikcas spent about what 3-4 months 14 hrs a day on the kernel trying all permutations and combinations but was not successful so ....you realize if i show doubt to maclaws possiblity of fixing it(nonetheless miracles happen).
PS reported you.(for starting a possible flame war).
PPS also maclaw still breaks the gpl by distributiing a closed source kernel based on opensourced resources(its still linux).
---------- Post added at 07:25 PM ---------- Previous post was at 07:21 PM ----------
marcin1147 said:
I only leave this here:
Click to expand...
Click to collapse
knock knock ....correction Erikcas and psyke83's not TheWhisp.
Dark Passenger said:
Erikcas spent about what 3-4 months 14 hrs a day on the kernel trying all permutations and combinations but was not successful so ....you realize if i show doubt to maclaws possiblity of fixing it(nonetheless miracles happen)
Click to expand...
Click to collapse
COOL STORY BRO
*click*
BTW. Maybe you don't know but our sources are here: https://github.com/MaclawStudio/aosp_kernel
Also the fact that maclaw asked for donations to buy a galaxy mini....
many people trusted him and donated..
and when there was enough he betrayed by stopping development and not using the money what it was meant for ...
most people argue that he promised but as always there is no proof or a written agreement or contract and thus the money donated with trust of further development of various development was pocketed...
I am not blaming or accusing anyone of anything but just stating the facts that i know..
hsay said:
Also the fact that maclaw asked for donations to buy a galaxy mini.... many people trusted him and donated..
Click to expand...
Click to collapse
Maclaw told me that nobody has donated.
and you believed?
anyway lets stop the discussion right here...
if maclaw comes back for development i dont have any problems...
he is welcome anytime
Please, stop this stupid arguing.
I know a lot of people hates me here, I don't care.
Just relax, let every developer like erikcas, TheWhisp etc. do their bests without fighting.
Maybe our device sources are closed, but we've to share kernel sources. If we do 3.x kernel, we'll have to share sources aswell.
Erickas will make 3.x? Great, every Samsung device with msm7x27 will be able to use it with mention that it's ported by him.
We will make 3.x? Great, as up. We must to share kernel sources when we release it.
What a difference?
Hello everyone
This is the first time Im creating a thread in all my years here on XDA. So please bear with me
Im very happy and excited to see the recent boom of custom roms for our device, its going really well and at a break neck speed.
Much rapid then I can download and flash it too
However, the only thing bugging me the lack of custom kernels.
I understand that the pINKman kernel by slukk and unnamed kernel by luca are both fantabulous kernels , and are mighty contenders for your time.
Dont get me wrong, I fully and whole-heartedly appreciate the kernel-devs and the awesome work made by them
The furnace kernel by savoca seemed to be a good one too, but I noticed that the thread has been closed and my recent pm to him about some possible update has not yielded any results.
I dont possibly know where im going with this conversation (lol), but if you catch my drift, we'd certainly want to see the boom of custom kernels just as we did with custom roms
Sorry for such a lengthy post .
*bows out*
:cyclops:
EDIT- lol, sorry for creating a thread in the general section, I botched it
Should have created in the QA section
metalrules321 said:
However, the only thing bugging me the lack of custom kernels.
Click to expand...
Click to collapse
Well, as long as Motorola doesn't release the kernel sources for lollipop, there isn't much that can be done. I found today some commits for lollipop but nothing official (look at Motorola's github kernel under issues). It took Motorola quite a while to release the sources for kitkat, so we have to keep patient.
need some OC and OV feature
@doppelhelix
Whelp
Thanks for clearing that up for me man.
Yeah it kinda sucks , I mean with the recent influx of so many roms and only 2 kernels was an eye-sore xD
Anys ways
*fingers crossed*
@doppelhelix
But on a second thought
How come slukk is developing and updating kernels even though the sources have not been released ??
metalrules321 said:
@doppelhelix
But on a second thought
How come slukk is developing and updating kernels even though the sources have not been released ??
Click to expand...
Click to collapse
based on kitkat. Thats why they don't work on stock lollipop, only cm
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.