Related
This kernel will be kept simple and inline with stock and free from buzzfree stuff..as the aim is a stable day-to-day use kernel..this kernel is NOT for those who want to break records..as i do not believe and rely on benchmarks..(its me..)
Disclaimer:
i nor xda would be at fault if something weird beyond my test results happen to your phone..also this is not a benchmark kernel..if you like crunching numbers and breaking records go use another kernel..this is meant to save juice and be efficient and stable as a daily driver for Samsung based ROMS..
Features:
- Based on i9205/i9195 source from Samsung OSRC(Thanks for the borked source)
- Fixed a few things left by Samsung to be broken
- Simple and no fancy stuff thats gonna bork your phones..more stuff does not guarantee it's better..
- User voltage control from faux123 for Krait CPU's..
- EXFat support(by Samsung OSRC..)
- OC(if already stable)
- will populate more as things get stable
- Selinux permission is set from enforcing to permissive via ramdisk
- insecure boot image
- Disabled Rooting security measures implemented by Samsung..
Pre-requisites
- Install busybox via CWM or via Playstore before installing my kernel..this is to make sure init.d and also some scripts work properly..
Downloads here: Test build 5(ML1 Ramdisk)
My git: source
Credits:
- noone in particular but thanks to ALL the wonderful devs here in XDA..
If you like the builds please help me get a Soda/pay bills..or the least is just hit the Thanks Button..
one more in case..
uploading..
please report/feedback on any issue you might encounter..please do provide logs(last_kmsg, logcats, dmesg...etc..) so that i can shoot things out..i do not own the device yet and surely things can go wacky along the way..
TIA
kindly someone report if the build boots up..
What do you mean with those features?
- Fixed a few things left by Samsung to be broken
- Removed most of the crappy and buggy stuff..
- GPU Idling fix..
Click to expand...
Click to collapse
I cannot see them on your sources
Grarak said:
What do you mean with those features?
I cannot see them on your sources
Click to expand...
Click to collapse
will push them tomorrow(just have to know if the build boots or not)..samsung left an issue on the video drivers for ebook mode(scenario mode)..which can hinder compilation..why so curious?? you're the idol..
kairi_zeroblade said:
will push them tomorrow(just have to know if the build boots or not)..samsung left an issue on the video drivers for ebook mode(scenario mode)..which can hinder compilation..why so curious?? you're the idol..
Click to expand...
Click to collapse
I was curious how you described these features. If it's only an e book reader issue, you cannot call it remove crappy stuff by samsung.
Sent from my Galaxy Nexus using xda app-developers app
Grarak said:
I was curious how you described these features. If it's only an e book reader issue, you cannot call it remove crappy stuff by samsung.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
ok so if it bothers you then i will ninja edit it then..its just a general template i used on my previous OP..dont be so harsh on me..
update: edited it to "fit" your standards.. (what a way to welcome me here........now i can go to bed..and get my beauty sleep.. )
update: good morning guys!! any reports or comments if it boots up?? need feedbacks so i can start pushing more stuff..
I tried it on a I9200.
Device boots
No wifi
Lost root
For some reason, Google+ stopped working
Logcat attached.
Silesh.Nair said:
I tried it on a I9200.
Device boots
No wifi
Lost root
For some reason, Google+ stopped working
Logcat attached.
Click to expand...
Click to collapse
thanks will invetigate the logs provided..can you upload a stock image of the i9200 btw??so i can check if there are specific differences from the ramdisk of the i9200 from i9205..afaik aside from the LTE there should be other differences from them..
re: root it might have been because of the ramdisk i used..can you shift to Koush's superuser??chainfire's supersu has been finicky with my HTC 4.3 update but Koush's never had a glitch..
Thank you very much for the feedback!!
edit: get the SuperUser by Koush here
Stock MJ1 I9200 boot image attached. I'll let you know if I succeed to root.
Silesh.Nair said:
Stock MJ1 I9200 boot image attached. I'll let you know if I succeed to root.
Click to expand...
Click to collapse
can you pull me a last_kmsg from my kernel??it seems there is a hardware initialization issue..TIA
kairi_zeroblade said:
can you pull me a last_kmsg from my kernel??it seems there is a hardware initialization issue..TIA
Click to expand...
Click to collapse
Attached.
Silesh.Nair said:
Attached.
Click to expand...
Click to collapse
ok nailed down the culprit..will release a new test build in a few minutes thanks Silesh..it seems i was missing a few stuff..
kairi_zeroblade said:
update: new test build here OP updated as well
kindly test and provide feedback so i can push more stuff in..i have to do alot more maintaining also to my git..
Click to expand...
Click to collapse
I am testing my slimkat build. Will flash and let you know in an hour.
Silesh.Nair said:
I am testing my slimkat build. Will flash and let you know in an hour.
Click to expand...
Click to collapse
thank you it seems i made a minor derp..will fix it now..and upload a new kernel.
OK. When you upload, mention me so that I get a noification. Else I need to check the thread often.
Silesh.Nair said:
OK. When you upload, mention me so that I get a noification. Else I need to check the thread often.
Click to expand...
Click to collapse
update: get test build 3 here
kairi_zeroblade said:
update: get test build 3 here
Click to expand...
Click to collapse
Still no wifi. Root works, both SuperSU and Koush. Logs attached.
Silesh.Nair said:
Still no wifi. Root works, both SuperSU and Koush. Logs attached.
Click to expand...
Click to collapse
ok got it..will switch to the ML1 ramdisk you gave me..will post a new build in a few minutes..
edit: it seems i was messing with the UCNA2 update with SELINUX..thats why i was borking things..i am now using the ML1 ramdisk..
@silesh
new build up..here
Just another source of daily CM12 builds
(These builds are run automatically every 24h, so they aren't tested and *might* be broken. So far, CM has been pretty good with keeping their ROM booting though. Also, if the build fails, nothing will be uploaded (obviously), if that happens, shoot me a PM or something)
http://downloads.codefi.re/herna/chaosagent
I *might* start adding my own features or cherry-picking things later if I have time and there is demand.
OT chatter removed...:crying:
What is the PA ota I see here?
cpu999 said:
Just another source of daily CM12 builds
(These builds are run automatically every 24h, so they aren't tested and *might* be broken. So far, CM has been pretty good with keeping their ROM booting though. Also, if the build fails, nothing will be uploaded (obviously), if that happens, shoot me a PM or something)
http://downloads.codefi.re/herna/chaosagent
I *might* start adding my own features or cherry-picking things later if I have time and there is demand.
Click to expand...
Click to collapse
Could you create and share a google drive folder so we can add it to our folders and have the build updated automatically to our hdd?
Thanks a lot
ZX64 said:
What is the PA ota I see here?
Click to expand...
Click to collapse
I just randomly built pa cuz I was bored lol
(It doesn't flash, BTW)
provolinoo said:
Could you create and share a google drive folder so we can add it to our folders and have the build updated automatically to our hdd?
Thanks a lot
Click to expand...
Click to collapse
I don't have a good way to automatically upload these builds to drive...
Did anybody test these builds?
giaur said:
Did anybody test these builds?
Click to expand...
Click to collapse
From the OP (which is just 3 or 4 posts above you) ;
(These builds are run automatically every 24h, so they aren't tested and *might* be broken.
Click to expand...
Click to collapse
LiquidSolstice said:
From the OP (which is just 3 or 4 posts above you) ;
Click to expand...
Click to collapse
I mean if anybody tried them
giaur said:
I mean if anybody tried them
Click to expand...
Click to collapse
I try every 3-4 of these builds and I haven't run into any non-booting ones so far....
Every 24h, what time source is refreshed from git? I want to look into commits to get to know about changes.
Perhaps you could also auto generate some changelog file (obviously, got from git commit logs). Should be quite easy to develop some script for generating changelogs
cpu999 said:
I try every 3-4 of these builds and I haven't run into any non-booting ones so far....
Click to expand...
Click to collapse
No more builds?
giaur said:
No more builds?
Click to expand...
Click to collapse
Why?
accuphase said:
Why?
Click to expand...
Click to collapse
Ok, 21.12 is already there
giaur said:
Ok, 21.12 is already there
Click to expand...
Click to collapse
This is for developers, willing to contribute in for fixing Xposed on 64-bit Samsung devices.
If you're just a regular user, please don't post on this thread.
Now that deodexing Android 5.1 firmware is possible, I went on porting Xposed to Galaxy S6 Android 5.1 with almost the same procedures that I've done with Sammy's Android 5.0, but now with AArch64 compilation.
I managed to fix core-libart.jar to match AOSP's style until the point where Zygote completely dies without complaining which functions are missing or malfunctioning.
Seems like Samsung has played around ART runtime even more with 64-bit devices.
(PS, deodex'ed firmware without installing Xposed's new files boots just fine without issues)
Built with GCC 4.9:
Logcat - http://pastebin.com/WXvryB0m
Tombstone - http://pastebin.com/pKzb47nm
Sources are available at https://github.com/arter97/android_art/tree/samsung-lollipop-5.1 and
modified core-libart.jar is at http://www.arter97.com/browse/tmp/core-libart.jar
Re-building ART runtime completely with Clang compiler has revealed slight more debugging info.
Clang tombstone - http://pastebin.com/Ngemxy4H
Seems like somewhere between artAllocArrayFromCodeResolvedRosAllocInstrumented and BuildArgArrayFromObjectArray is causing boot issues.
oatdump can get somewhat debuggable info but I've yet to find a relation with the crash.
https://code.google.com/p/android/issues/detail?id=173420
@wanam also reported the almost same issue on Android 5.0 - https://github.com/rovo89/android_art/issues/9
This issue also made me think that it actually might be the Exynos 7420 issue itself, and Samsung has implemented a workaround just for it,
considering there're some AArch64 erratum fix commits - https://github.com/arter97/android_art/commit/d07021b38087ca0e385ebf46dd1b78239ed702b2 & https://github.com/arter97/android_art/commit/c5d9beb95d2c392820048ca42f582e4a50a9ca4d
I'm still working on how to fix this annoying issue.
If you have any ideas or tips, please let me know.
I'm having a hard time understanding if people can't see the very first paragraph on this thread.
No testers are needed.
arter97 said:
This is for developers, willing to contribute in for fixing Xposed on 64-bit Samsung devices.
If you're just a regular user, please don't post on this thread..
Click to expand...
Click to collapse
arter97 said:
I'm having a hard time understanding if people can't see the very first paragraph on this thread.
No testers are needed.
Click to expand...
Click to collapse
Mod Edit
Thread cleaned.
Please read people...
Thank you
malybru
Forum Moderator
@arter97 did you try the Cortex-A53 Erratum 843419 workaround in OatWriter? it is already included on the M previews, i tried to merge it with 5.1.1 sources but it seems it has some dependent commits.
wanam said:
@arter97 did you try the Cortex-A53 Erratum 843419 workaround in OatWriter? it is already included on the M previews, i tried to merge it with 5.1.1 sources but it seems it has some dependent commits.
Click to expand...
Click to collapse
No, I didn't saw that commit until now.
I'll try that later
wanam said:
@arter97 did you try the Cortex-A53 Erratum 843419 workaround in OatWriter? it is already included on the M previews, i tried to merge it with 5.1.1 sources but it seems it has some dependent commits.
Click to expand...
Click to collapse
I think grepping "64", "arm64", "AArch64", "Cortex" from Google's master branch's 'git log' might get us somewhere.
arter97 said:
I think grepping "64", "arm64", "AArch64", "Cortex" from Google's master branch's 'git log' might get us somewhere.
Click to expand...
Click to collapse
That's what I did, but I found only the two erratums 843419 and 835769 that seems related to Exynos, the first one was merged on the stock toolchain, but I'm not sure if there is any explicit option to enable the fix on the compilation.
wanam said:
That's what I did, but I found only the two erratums 843419 and 835769 that seems related to Exynos, the first one was merged on the stock toolchain, but I'm not sure if there is any explicit option to enable the fix on the compilation.
Click to expand...
Click to collapse
Merged to "toolchain"?
Sent from my SM-G920F using XDA Free mobile app
wanam said:
That's what I did, but I found only the two erratums 843419 and 835769 that seems related to Exynos, the first one was merged on the stock toolchain, but I'm not sure if there is any explicit option to enable the fix on the compilation.
Click to expand...
Click to collapse
Huh, ok, seems like Samsung is at least not using 843419.
I can't get any 843419 related fixes on built binaries.
I can't say the same thing as 835769 as its change is so minimal that it'll be hard to determine just from the binaries.
I'll try to enable 835769 later.
arter97 said:
Merged to "toolchain"?
Sent from my SM-G920F using XDA Free mobile app
Click to expand...
Click to collapse
I'm talking about this: https://android.googlesource.com/pl....9/+/6a20db030e486326e70968612662938d12d86a7b
wanam said:
I'm talking about this: https://android.googlesource.com/pl....9/+/6a20db030e486326e70968612662938d12d86a7b
Click to expand...
Click to collapse
https://gcc.gnu.org/ml/gcc-patches/2014-10/msg00906.html
Passing -mfix-cortex-a53-835769 enables that workaround for GCC. I'll also try that out later.
Another very interesting CyanogenMod Gerrit code review
http://review.cyanogenmod.org/#/c/103085/
It's a bit unfortunate that it seems it's actually quite common on AArch64.
http://www.slideshare.net/hidenorly/arm-cortex-a53-errata-on-andoid
Slide 8
Please note that ADRP is not used on L MR0 / MR1.
And then patches for 843419 are not needed.
Click to expand...
Click to collapse
Android 5.1 is MR1. So we can skip 843419
We're getting some progress here.
Finger crossed..
Nope. Dead end.
Those erratum commits still don't fix our issue.
More digging required.. GARR
@arter97 @wanam guys i guess u need @darkera13 maybe he can help u & join to urs for helping to fix Xposed for our S6 64 bit
Sent From My Awesome G920F Powered by EchoeRom
thereassaad said:
maybe he can help u & join to urs for helping to fix Xposed for our S6 64 bit
Sent From My Awesome G920F Powered by EchoeRom
Click to expand...
Click to collapse
lol.
Sent from my SM-G920F using XDA Free mobile app
arter97 said:
lol.
Sent from my SM-G920F using XDA Free mobile app
Click to expand...
Click to collapse
[emoji14]
Sent From My Awesome G920F Powered by EchoeRom
thereassaad said:
@arter97 @wanam guys i guess u need @darkera13 maybe he can help u & join to urs for helping to fix Xposed for our S6 64 bit
Sent From My Awesome G920F Powered by EchoeRom
Click to expand...
Click to collapse
I think we need someone with a good experience on binary analysis to decompile stock art libs and give us some hints about any specific commits used by Samsung.
Sent from my SM-N910C using Tapatalk
Edit: I no longer own this phone. Information in the OP may be outdated and/or incorrect. Please go to the new thread at http://forum.xda-developers.com/nexus-6/development/rom-cyanogenmod-13-nightlies-snapshots-t3363769
DISCLAIMER: I AM IN NO WAY RESPONSIBLE FOR ANY PROBLEMS ON YOUR DEVICES CAUSED BY FLASHING THESE BUILDS. THE UPSTREAM CODE AND BUILDING IS MAINTAINED BY THE CYANOGENMOD TEAM, NOT ME. I AM NOT ASSOCIATED WITH THEIR TEAM, I AM JUST THE THREAD OWNER.
It was a fun round of unofficial nightlies but the official upstream CM13 builder for shamu is active! Please use the new download links below to grab the official nightlies. Dirty flash seems to work fine if you go from my unofficial 11-29 build to the official 11-30 one. As mentioned in the first post, I will be ceasing my personal builds for now and leave it to the CM team.
Notes: CyanogenMod's stock kernel forces encryption of storage. Please download one of the third party kernels if you wish to avoid this. Also this thread assumes you have kept up to date with bootloaders and radio. At the time of writing, the latest is from the MRA58K release and can be downloaded here.
CyanogenMod 13.0 Nightlies: Download
Open GApps: Download (I recommend arm, 6.0, micro)
Changelog: CMX Changelog
Third party kernels:
Elite Kernel
Hells Core
XDA:DevDB Information
CyanogenMod 13.0, ROM for the Nexus 6
Contributors
djh816
ROM OS Version: 6.0.x Marshmallow
Based On: CyanogenMod
Version Information
Status: Nightly
Created 2015-11-22
Last Updated 2015-12-06
There's already a thread
http://forum.xda-developers.com/nexus-6/development/rom-cyanogenmod-13-0-android-6-0-t3231497
HipKat said:
There's already a thread
http://forum.xda-developers.com/nexus-6/development/rom-cyanogenmod-13-0-android-6-0-t3231497
Click to expand...
Click to collapse
Correct, but not nightly and as far as I can tell albinoman887 is also making fixes which implies altering of upstream code. My thread intends to serve as a purely upstream source build.
djh816 said:
Correct, but not nightly and as far as I can tell albinoman887 is also making fixes which implies altering of upstream code. My thread intends to serve as a purely upstream source build.
Click to expand...
Click to collapse
I would like to say thank you, and I believe that this ROM deserves its own thread respectfully. Since there isn't much action from that other Alpha build and if you are truly building on a nightly basis then this is much appreciated and I look forward to testing.
Thanks!
HipKat said:
There's already a thread
http://forum.xda-developers.com/nexus-6/development/rom-cyanogenmod-13-0-android-6-0-t3231497
Click to expand...
Click to collapse
A Thread with Zero Support from the Thread OP and no Nightlys , its good to see this Thread with hopfully regular updates since I currently have working in the border guarding Work and never have time for building. But what i know from @djh816 updates come many times.
Tylog said:
A Thread with Zero Support from the Thread OP and no Nightlys , its good to see this Thread with hopfully regular updates since I currently have bodybuilding in the border guarding Work and never have time for building. But what i know from @djh816 updates come many times.
Click to expand...
Click to collapse
Thanks for the support and glad to build it. Just to make sure credit is given where due, any bug fixes will be made only by the CyanogenMod team and/or any git contributors. Not sure if you'll get much support from me either but I'll certainly be glad to give any tips I find. For example, if this one specific bug rears its ugly head again, you may need to rename the SetupWizard apk inside /system/app-priv/ as that has been constantly force closing for me prior to today's build.
djh816 said:
Thanks for the support and glad to build it. Just to make sure credit is given where due, any bug fixes will be made only by the CyanogenMod team and/or any git contributors. Not sure if you'll get much support from me either but I'll certainly be glad to give any tips I find. For example, if this one specific bug rears its ugly head again, you may need to rename the SetupWizard apk inside /system/app-priv/ as that has been constantly force closing for me prior to today's build.
Click to expand...
Click to collapse
MAybe test other Gapps, i had this isues with a few cm 13 builds in combination with banks gapps , i like Banks gapps but for now not with CM13 . No support for me no problem , only 1 builds in 3 Weeks in this early stage is a problem , thats what i mean . I have at the moment zero time , i am one day in the week at home and thats time for my son and my wife
Thanks for the builds. I tried (unsuccessfully) to build my own, so this helps out a lot!
nightlies has not started yet.. looking forward..
Awesome! Thanks!
Sent from my Nexus 6 using Tapatalk
Can anyone confirm that you can write to system on this build???? Wasn't working on a build from 11.20.
Sent from my Nexus 6 using Tapatalk
mexiken said:
Can anyone confirm that you can write to system on this build???? Wasn't working on a build from 11.20.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Still is not working.. I'd love to know of a fix, if any...
mexiken said:
Can anyone confirm that you can write to system on this build???? Wasn't working on a build from 11.20.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I modified build.prop just fine.
---------- Post added at 03:10 AM ---------- Previous post was at 03:08 AM ----------
Thanks OP, for bringing this to us. Seems pretty good for such an early build. I just barely flashed it but seems great so far.
Does ad away work on this build? It wouldn't work on the previous build.
Is security disable on the ROM?
cz829x18 said:
Does ad away work on this build? It wouldn't work on the previous build.
Click to expand...
Click to collapse
Doesn't seem to just yet. As others have mentioned, no /system writing just yet.
evolishesh said:
Is security disable on the ROM?
Click to expand...
Click to collapse
Doesn't seem like it, I've tried "adb shell" with "su" after but still drops me to a "$" shell rather than "#"
Will you be adding any features or will this be more of a slim to stock cm13 builds? Also thanks for your contributions
nighthawk626 said:
Will you be adding any features or will this be more of a slim to stock cm13 builds? Also thanks for your contributions
Click to expand...
Click to collapse
No features added whatsoever If they add it upstream (included in CM) it'll be here, otherwise no. Absolutely stock. Consider me a third party buildbot slave
Very nice ROM. Just to let everyone know I just finished flashing with the Open GApps Pico and it's working fine. I know, it's bad form to use something that's not recommended.
One quick question, do we get any notification that the new nightly is ready to flash or do we just check the download site?
dlbarron said:
Very nice ROM. Just to let everyone know I just finished flashing with the Open GApps Pico and it's working fine. I know, it's bad form to use something that's not recommended.
One quick question, do we get any notification that the new nightly is ready to flash or do we just check the download site?
Click to expand...
Click to collapse
For now just the download site. I may setup something similar to the pushbullet feed Chroma has if people are interested but haven't spent the time to do it yet. New 11-23 build is up now though
Edit: Woot, looks like they fixed the system rw mounting. Hm but my test file disappeared on reboot.. maybe not yet
Original ROM thread: https://forum.xda-developers.com/galaxy-j5/development/rom-6-0-1-cyanogenmod-13-0-samsung-t3454915
Keep up the great work.
Device: SM-J500F on 6.0.1
Status: Rooted, Debloated and BusyBoxed. No other modifications.
Country: India
Recovery: TWRP 3
Advantages of custom ROM-
Faster. Sleeker. And Smoother.
Really lag-free.
Multi-Window Mode
Startup takes little time, even the first one.
Internet speed increased considerably.
High storage space available due to small ROM
High RAM available
Button reconfiguring in Settings
Viper4Android, SU installed.
Additional appealing functions in settings.
Debloated.
MTP and other PC functions such as debugging worked fine.
Pre-installed useful features and apps.
However, I also noticed some of the below bugs and disadvantages.
Camera failed (as you said). I tried Google Camera, doesn't seem to work at all. Displays camera screen but closes showing "Unable to connect to camera."
Google Play Store is very fast but downloading never happens. (Solved - see 10 Jan 2017 Update)
First startup requires network connection from either SIM or WiFi.
Suggestions:
I think that replacing the two scripts (files) in the Camera folder in the zip flash file of the ROM with the stock one might have the camera working. I tried it myself but couldnot extract the files from the stock image. Trying.
Notification panel must be more customisable.
Mobile data enable in one click from notification panel. Like in stock Samsung.
Alternative option for enabling stock notification panel. (I just love the Samsung one. Very convenient.)
The rest are all fine.
So, why was this thread closed. I know "GPL Complaint". But is this site for discouraging custom modifications and creations?
Update - 10 Jan 2017
Solved: Google Play Store downloading. Just a temporary network glitch.
Bug (may have been mentioned before in earlier posts): Unable to switch to 3G only mode in either SIMs. Option shows selected but doesn't work actually and connects to 2G. 3G works if automatically detected.
KaushikMajumdar said:
So, why was this thread closed. I know "GPL Complaint". But is this site for discouraging custom modifications and creations?
Click to expand...
Click to collapse
If you know why it was closed, why do you ask?
XDA has rules like any other forum. You must obey the rules. If you're not obeying them, then it's your fault.
Simple as that.
I don't know why you made this thread, because it won't change anything. Actually, it will just start discussions again.
#Henkate said:
If you know why it was closed, why do you ask?
XDA has rules like any other forum. You must obey the rules. If you're not obeying them, then it's your fault.
Simple as that.
I don't know why you made this thread, because it won't change anything. Actually, it will just start discussions again.
Click to expand...
Click to collapse
I didn't open the thread to question the closing. You misunderstood me. I did it to review on the ROM and encourage the developer.
And yes, starting up discussion of developing Cyanogen mod 13 for J500* is a part of it.
KaushikMajumdar said:
I didn't open the thread to question the closing. You misunderstood me. I did it to review on the ROM and encourage the developer.
And yes, starting up discussion of developing Cyanogen mod 13 for J500* is a part of it.
Click to expand...
Click to collapse
All your gonna do by starting up this discussion again is cause an argument.
It ain't gonna lead any where.
The Dev responsible for this ROM ain't gonna start up this ROM again on XDA.
If finished his work, posted it on a different site and has moved on by finishing his work and changing phones to find a development community that appreciates his work.
Sent from my Honor 8 using XDA Labs
johnhux7 said:
All your gonna do by starting up this discussion again is cause an argument.
It ain't gonna lead any where.
The Dev responsible for this ROM ain't gonna start up this ROM again on XDA.
If finished his work, posted it on a different site and has moved on by finishing his work and changing phones to find a development community that appreciates his work.
Click to expand...
Click to collapse
Just a review. Don't think so further. It's not THAT serious.
KaushikMajumdar said:
Just a review. Don't think so further. It's not THAT serious.
Click to expand...
Click to collapse
That's the problem though mate it was that serious.
Read up on the old threads and you will see the history of it all.
Bad times
Sent from my Honor 8 using XDA Labs
johnhux7 said:
That's the problem though mate it was that serious.
Read up on the old threads and you will see the history of it all.
Bad times
Click to expand...
Click to collapse
CyanogenMod 13 for J5 can be rebuilt without the violations over again.
KaushikMajumdar said:
CyanogenMod 13 for J5 can be rebuilt without the violations over again.
Click to expand...
Click to collapse
Cool, good luck. R u the man for the job ?
I thought that nick and co where building CM13 ?
The one that Zonik build has been finished a while back.
It's available in FB
Sent from my Honor 8 using XDA Labs
johnhux7 said:
Cool, good luck. R u the man for the job ?
I thought that nick and co where building CM13 ?
The one that Zonik build has been finished a while back.
It's available in FB
Click to expand...
Click to collapse
Well, if it is so then could you please forward me the link to the Facebook page.
And is the Zonik Build for J500F on 6.0.1?
KaushikMajumdar said:
Well, if it is so then could you please forward me the link to the Facebook page.
And is the Zonik Build for J500F on 6.0.1?
Click to expand...
Click to collapse
PM me
Deleted
Sent from my Honor 8 using XDA Labs
The thread is still open for your suggestions XDA Community. I am awaiting for response.
Deleted
Let me remind everyone here that providing links to non GPL compliant development, via PM or otherwise on XDA, is against the rules.
The Merovingian said:
Let me remind everyone here that providing links to non GPL compliant development, via PM or otherwise on XDA, is against the rules.
Click to expand...
Click to collapse
I am sorry if posting this was a violation. As you see I am a new member. I am not giving an excuse but the purpose of this thread was to start further development of CyanogenMod ROM for J5 and not continuation of the original non-GPL complaint ROM. It was just an cited example to illustrate the ROM type.
If I knew how to make a kernel (and had the correct resources) I would happily continue where zonik left and why don't you warn before performing what you did, aren't humans error prone?
#Henkate said:
If you know why it was closed, why do you ask?
XDA has rules like any other forum. You must obey the rules. If you're not obeying them, then it's your fault.
Simple as that.
I don't know why you made this thread, because it won't change anything. Actually, it will just start discussions again.
Click to expand...
Click to collapse
1. DJ_Steve's kernel IS GPL complaint
2. Now the developers that are banned from XDA made a aroma TWRP AND stable cyanogenmod 13
3. (for mods) unban them
Telepracity said:
1. DJ_Steve's kernel IS GPL complaint
2. Now the developers that are banned from XDA made a aroma TWRP AND stable cyanogenmod 13
3. (for mods) unban them
Click to expand...
Click to collapse
1. https://forum.xda-developers.com/showpost.php?p=69643216&postcount=217 .
2. I will try AROMA TWRP in future too.
3. Read rules.
4. Dont reply to this post.
#Henkate said:
1. https://forum.xda-developers.com/showpost.php?p=69643216&postcount=217 .
2. I will try AROMA TWRP in future too.
3. Read rules.
4. Dont reply to this post.
Click to expand...
Click to collapse
1. Why does skiesrom use that kernel and has not been taken down?
2.Nice
3.No need, I already read them
4.Sorry, I had to. I need to clean the forums
1. I'm always watching.
2. See #1.
The Merovingian said:
1. I'm always watching.
2. See #1.
Click to expand...
Click to collapse
1. I know.
2. I know.
o sh*t this is going offtopic xDxdD