Develop Bugs

[ANNOUNCEMENT]LGE Stock kernel 3.4.0 for iprj, batman, cayman

Hi,
LGE open 3.4.0 kernel for I_BOARD (i_series, ijb_series), 325_BOARD (batman series), 120_BOARD (cayman series).
LG-F100L (batman_lgu_kr), LG-F100S (batman_skt_kr), LG-F120S (cayman_skt_kr) have same kernel source and there's i series source and config.
But it does not have CAF capability.
Please modify this kernel source.
LGE Opensource site, search f100l or f100s and download JB source.

Yes, we know about it. Its not easy but we can adapt it for our device.
I am started port P930 features to F120S sources, but need a lot time for it.
When it will boot, I will upload kernel to Github for fixing drivers together.

Help me too!!!
miroslav_mm said:
Yes, we know about it. Its not easy but we can adapt it for our device.
I am started port P930 features to F120S sources, but need a lot time for it.
When it will boot, I will upload kernel to Github for fixing drivers together.
Click to expand...
Click to collapse
Could you make it for F100S too? I have download the kernel source of F100S but i don't understand how to build it to compatible with CM rom. I was read many guide to build cm kernel but i confused where must i start to buil. Maybe i'm not develop....:laugh::laugh::laugh:

CM-11 Snapshot M13

If, like me, you despaired of CM ever releasing another "stable" version of CM-11, your wait is over.
I found out they had FINALLY done another M-SNAPSHOT code freeze, so I synced the source and built one of my own.
http://d-h.st/aihU
Link to Kernel source (if you feel you need it)
https://github.com/CyanogenMod/android_kernel_samsung_hlte
-blaine

Frankenbiker said:
If, like me, you despaired of CM ever releasing another "stable" version of CM-11, your wait is over.
I found out they had FINALLY done another M-SNAPSHOT code freeze, so I synced the source and built one of my own.
Link removed. Apparently we can't post links to builds any more without a full kernel code dump in the post.
If anyone is actually interested, PM me and I'll send you the link.
-blaine
Click to expand...
Click to collapse
This has been the case for as long as XDA has been GPL compliant. Any distribution of a binary (meaning kernel boot,img) that is not unmodified manufacturer's stock requires a link to kernel source, not a code dump. Anyone building CM from source should have no issues getting the link to source code and including it.

Frankenbiker said:
If, like me, you despaired of CM ever releasing another "stable" version of CM-11, your wait is over.
I found out they had FINALLY done another M-SNAPSHOT code freeze, so I synced the source and built one of my own.
http://d-h.st/aihU
Link to Kernel source (if you feel you need it)
https://github.com/CyanogenMod/android_device_samsung_msm8974-common
-blaine
Click to expand...
Click to collapse
There is no kernel source in that link. Please post proper kernel source.
Edit: Thank you for updating the link to kernel source

SlimRom 6.0 for Galaxy S6 - V2 - 12/21/2015

SlimRoms is a custom android operating system. The main goal is to offer users a slimmed down but still feature rich alternative to other android operating systems.
The entire SlimTeam work together to bring you this tailor-made beauty straight from Android Open Source Project (AOSP) source code.
All of the sources can be publicly viewed through GitHub and you can stop by the public Gerrit to submit patches of any type.
Important links:
slimroms.org - The official webpage where you find everything you need to know about SlimRoms.
Downloads - Download the rom for S6 from here
Kernel Source - The source of your device's kernel.
Get in touch! - Contact SlimRoms at these places if you have questions, requests or feedback.
Google+
Twitter
Facebook
Thanks!
The entire team who helped with the device tree to make this device get CM. Hats off guys. Really appreciate your hard work.
For dual boot, kindly follow this link.
If you have any other queries, kindly see this link for any issues other users face before posting here.
Working and Not working:
Everything as in CM
/* Supported devices */
Galaxy S6 International (SM-G920F/I, zerofltexx)
Galaxy S6 SK (SM-G920S, zeroflteskt)
Galaxy S6 KT (SM-G920K, zerofltektt)
Disclaimer: SlimRoms are not responsible for any damages to your device.
XDA:DevDB Information
SlimRom 6.0 for Galaxy S6 , ROM for the Samsung Galaxy S6
Contributors
a2441918
ROM OS Version: 6.0.x Marshmallow
Version Information
Status: Testing
Current Beta Version: 0.2
Beta Release Date: 2015-12-21
Created 2015-12-16
Last Updated 2015-12-23

No offense but you're the 3rd one to release a rom that has the exact same source as the original CM13 thread, and all others have been shutted down. You should invest your time helping the main branch fixing their stuff instead of dividing everybody. Releasing a ROM that is exactly the same with a different name is a total lack of respect to those who really worked hard to make this happen, plus your sources are not even public :/

virulentt said:
No offense but you're the 3rd one to release a rom that has the exact same source as the original CM13 thread, and all others have been shutted down. You should invest your time helping the main branch fixing their stuff instead of dividing everybody. Releasing a ROM that is exactly the same with a different name is a total lack of respect to those who really worked hard to make this happen, plus your sources are not even public :/
Click to expand...
Click to collapse
I have no sources. I have published the link to the kernel source. Every Rom is based off CM tree and it is not the same. Its SLIM.

a2441918 said:
I have no sources. I have published the link to the kernel source. Every Rom is based off CM tree and it is not the same. Its SLIM.
Click to expand...
Click to collapse
I'm pretty sure it's an XDA rule to publish the source of every rom/kernel. Otherwise it could contain malware/keylogger or could be fake. I took a look at SLIM's github and i didn't see anything related to the S6.

Dude you dont get it. According to XDA you should publish a source for the kernel and I did. Go ahead with the link I posted and it will direct you to the kernel source. It is not necessary that the kernel should belong to Slim.

I see no official source on your GitHub. Is this just a rebrand of CM 13 for S6?

Nevermind keep it coming
Sent from my SM-G920F using Tapatalk

bio4554 said:
I see no official source on your GitHub. Is this just a rebrand of CM 13 for S6?
Click to expand...
Click to collapse
Dude, I used Slim rom sources and this device kernel and vendor tree and built the rom. There is no need for sources in my github. And Slim and CM are different. I am not just rebranding. I am building this from source.

a2441918 said:
Dude, I used Slim rom sources and this device kernel and vendor tree and built the rom. There is no need for sources in my github. And Slim and CM are different. I am not just rebranding. I am building this from source.
Click to expand...
Click to collapse
It's like steeling the bigmac sauce's receipe to make your own burger restaurant, but saying that you use a different bread.

Omg whats the issue with you guys? I gave credit for the developers, linked to the kernel tree of the actual developer and now what is that you people need?

a2441918 said:
Omg whats the issue with you guys? I gave credit for the developers, linked to the kernel tree of the actual developer and now what is that you people need?
Click to expand...
Click to collapse
http://forum.xda-developers.com/gal...yanogenmod-13-galaxy-s6-t3269984/post64321767
Having a second ROM with same issues doesn't help at all. Why wouldn't you wait for it to be stable instead of releasing another alpha rom?

virulentt said:
http://forum.xda-developers.com/gal...yanogenmod-13-galaxy-s6-t3269984/post64321767
Having a second ROM with same issues doesn't help at all. Why wouldn't you wait for it to be stable instead of releasing another alpha rom?
Click to expand...
Click to collapse
You could have pointed that out in the first post itself rather than us spamming this thread. I will remove the download link and keep this thread closed for now.

virulentt said:
I'm pretty sure it's an XDA rule to publish the source of every rom/kernel. Otherwise it could contain malware/keylogger or could be fake. I took a look at SLIM's github and i didn't see anything related to the S6.
Click to expand...
Click to collapse
The only source required to be posted by GPLv2 and XDA requirements is kernel source. Also Slim and CM both have posted open permissions to build.

New build up. See OP for download link.

Download Link is dead for me.
a2441918 said:
New build up. See OP for download link.
Click to expand...
Click to collapse

ripv2 said:
Download Link is dead for me.
Click to expand...
Click to collapse
Try it out now mate.

Up and reachable Ill give it a shot!
a2441918 said:
Try it out now mate.
Click to expand...
Click to collapse

Any changelog ? and is this usable for edge version ? or it has same screen issue ?

bigbossclk said:
Any changelog ? and is this usable for edge version ? or it has same screen issue ?
Click to expand...
Click to collapse
I guess its usable. But a different build for S6 Edge is in the works.

Doesnt Boot on my 920f latest recovery clean install with and without gapps. Never finnishing Boot animation.

Blobs and a kernel build

Hello,
I am trying my first kernel build, and there is one item I am not understanding, and I cannot seem to find a definitive answer on the web.
I cannot figure out how device blobs are incorporated into the kernel build. Are they required for functionality, or does the device specific kernel source code on GitHub already contain them?
I tried the kernel build described in CM, however that was unsuccessful for me, I was unable to make it through the 'installboot' command.
Therefore, I have been watching, and reading, all the guides on how to build a kernel but none of them (at least that I could find) mention what to do with the device blobs. What am I missing? It seems that if I do not add them I will lose functionality?
I am new to this so maybe I am missing something obvious.

Erik63 said:
Hello,
I am trying my first kernel build, and there is one item I am not understanding, and I cannot seem to find a definitive answer on the web.
I cannot figure out how device blobs are incorporated into the kernel build. Are they required for functionality, or does the device specific kernel source code on GitHub already contain them?
I tried the kernel build described in CM, however that was unsuccessful for me, I was unable to make it through the 'installboot' command.
Therefore, I have been watching, and reading, all the guides on how to build a kernel but none of them (at least that I could find) mention what to do with the device blobs. What am I missing? It seems that if I do not add them I will lose functionality?
I am new to this so maybe I am missing something obvious.
Click to expand...
Click to collapse
Hello,
Please tell us the make and model of the device you building for.
Regards
Vatsal,
Forum Moderator.

Hi,
This is for an LG V500 tablet. Thanks!

Uses the code fefifofum as a base, but asks permission from him before

edsmat said:
Uses the code fefifofum as a base, but asks permission from him before
Click to expand...
Click to collapse
Thanks edsmat. sorry, but I am a little confused, does the code from fefifofum contain the blobs? Actually, I have the blobs, grabbed them from he V500. What I am confused about is how these blobs are incorporated into the kernel build (I have the kernel source from github).

[ROM][7.1.2][Unofficial]ResurrectionRemix 5.8.3 N for Athene

Resurrection Remix​Resurrection Remix ROM is the ultimate full featured, stable rom combined with the best features of open source roms .
We are also providing lot of awesome original Resurrection Remix ROM add-ons in the builds. It includes the best of performance, customization, power and the newest features on your device! It is one of the most customizable ROMs out-of-the-box!​
This version is almost the same as official one
But, without "Lucky" Control
Last Build is here: https://drive.google.com/open?id=0B57Q-f4sogZ_YjhDVFhGcExCWGs
Sources:
https://github.com/ResurrectionRemix
https://github.com/murigny64/proprietary_vendor_motorola-RR
Enjoy :fingers-crossed:

Thanks!!!
What's lucky control btw?

Droidphilev said:
Thanks!!!
What's lucky control btw?
Click to expand...
Click to collapse
Look at official RR thread and find "lucky"

Droidphilev said:
Thanks!!!
What's lucky control btw?
Click to expand...
Click to collapse
murigny64 said:
Look at official RR thread and find "lucky"
Click to expand...
Click to collapse
If you're referring to "Lucky Patcher detection" which Silesh uses in InvictaOS, than unless it's in RR sources officially, it's not in my official builds either. Also, unless you're using my device and kernel trees, and are compiling the kernel with Linaro, than these builds aren't the same as mine. If anything, I would assume they're the same as ///TheNexus/// nightly builds.

Jleeblanch said:
If you're referring to "Lucky Patcher detection" which Silesh uses in InvictaOS, than unless it's in RR sources officially, it's not in my official builds either. Also, unless you're using my device and kernel trees, and are compiling the kernel with Linaro, than these builds aren't the same as mine. If anything, I would assume they're the same as ///TheNexus/// nightly builds.
Click to expand...
Click to collapse
Sources are only official RR and modified Themuppets vendor tree.
Don't know about yours. Sorry, I thought you had to keep this functionality from silesh.
So, my build is useless.

murigny64 said:
Sources are only official RR and modified Themuppets vendor tree.
Don't know about yours. Sorry, I thought you had to keep this functionality from silesh.
So, my build is useless.
Click to expand...
Click to collapse
No worries! Silesh uses his own tweaked device tree and MM kernel in his builds. When I took over, I switched over to Lineage trees. I have a few extra commits here and there but nothing too serious and the only commits I've made in the vendor tree (at this time) is for the removal of "Device is HD Capable" notification that everyone hates lol.