Related
Hello all
I have spent much time recently attempting to modify the zImage included with the Fascinate to include a working recovery image for us to use. However without source code this an extremely difficult (if not possible) goal to achieve.
I am requesting that anyone who owns this device please request the kernel source code from Samsung, so that we may be able to fully utilize our devices. Even if you do not know anything about coding or have any personal use for this source code, it is your right to request it as an owner of the device, and this code will help us all immensely once it is in the right hands.
Requests for source code can be filed on Samsung's website at : opensource . samsung.com/ (remove the extra spaces, apparently I can't post links yet)
Click on the mail icon at the top to submit your request.
Thank you for your assistance.
Requesting right now. Thanks for what your doing! Any updates since last night?
i just finished sending one in
jt1134 said:
Hello all
I have spent much time recently attempting to modify the zImage included with the Fascinate to include a working recovery image for us to use. However without source code this an extremely difficult (if not possible) goal to achieve.
I am requesting that anyone who owns this device please request the kernel source code from Samsung, so that we may be able to fully utilize our devices. Even if you do not know anything about coding or have any personal use for this source code, it is your right to request it as an owner of the device, and this code will help us all immensely once it is in the right hands.
Requests for source code can be filed on Samsung's website at : opensource . samsung.com/ (remove the extra spaces, apparently I can't post links yet)
Click on the mail icon at the top to submit your request.
Thank you for your assistance.
Click to expand...
Click to collapse
You just want everything handed to you, don't you? Quit being so lazy and do some actual work.
But seriously everyone, please take the time to fill out the request. The sooner we get the source, the quicker we'll see some ROMs.
namebrandon said:
You just want everything handed to you, don't you? Quit being so lazy and do some actual work.
But seriously everyone, please take the time to fill out the request. The sooner we get the source, the quicker we'll see some ROMs.
Click to expand...
Click to collapse
This guy again, huh
Seriously, thank you to anyone who fills out the request. Remember, as an owner of the device it is your right to have access to the kernel source code, and it takes less than 2 minutes to fill out the request form. Tell your friends!
http://opensource.samsung.com/reception/reception_main.do?method=inquiryView
There's the direct url for the lazy.
Thanks for direct link. Filled one out through my phone. Made it sound pretty formal lol. Let's hope we get the ball rolling soon, starting to miss all the active development on the older phones.
Submitted a request.
frostman89 said:
Thanks for direct link. Filled one out through my phone. Made it sound pretty formal lol. Let's hope we get the ball rolling soon, starting to miss all the active development on the older phones.
Click to expand...
Click to collapse
Once we get source we will be able to get a working recovery, then the floodgates will be open. My personal mission is to get AOSP/CM on the phone immediately after that happens, can't stand the TouchWiz and I intend to destroy it!!
Submitted a request. Only way I'll be buying this phone is if I can eliminate all Verizon/Samsung UI/apps. Even a vanilla ROM will do over the TouchWiz crap.
I am a little confused. What source code are you requesting?
If you go to h**p://opensource.samsung.com/, click on 'Mobile' at the top, then Ctrl-F for "i9000", you can find (what looks like) a zip containing both the kernel image and files you can plop in an aosp tree in order to build roms for the Galaxy S.
Maybe you guys are talking about source specifically for Fascinate?
partner55583777 said:
I am a little confused. What source code are you requesting?
If you go to h**p://opensource.samsung.com/, click on 'Mobile' at the top, then Ctrl-F for "i9000", you can find (what looks like) a zip containing both the kernel image and files you can plop in an aosp tree in order to build roms for the Galaxy S.
Maybe you guys are talking about source specifically for Fascinate?
Click to expand...
Click to collapse
Yes, we are requesting the source for the fascinate. As the i9000 is a completely different device, and we have the sch-i500
fallingup said:
Yes, we are requesting the source for the fascinate. As the i9000 is a completely different device, and we have the sch-i500
Click to expand...
Click to collapse
Okay, thanks. That clears it up.
So I guess Samsung is currently in violation of the GPL, then? (And probably other licenses).
partner55583777 said:
Okay, thanks. That clears it up.
So I guess Samsung is currently in violation of the GPL, then? (And probably other licenses).
Click to expand...
Click to collapse
Well i am sure they will release the source, its just taking them longer than i would like. They released the source for the Epic about 3 days after the hardware was released, and we are at about a week now.
Yeah, they'll post the code soon, they're just taking their sweet time about it.
Source code released! Thanks guys!
jt1134 said:
Source code released! Thanks guys!
Click to expand...
Click to collapse
and source code fail!
Is the source code on opensource.samsung.com still the wrong one?
ludeboy said:
Is the source code on opensource.samsung.com still the wrong one?
Click to expand...
Click to collapse
Not sure yet. We've confirmed they've had at least two different files for download since last night. The original one wasn't' working. I'm at work, so can't tell you much about the second (latest) one.
Not sure if we've had this response so far but I wanted to share it.
______
Dear Dave,
Thank you for your continuous interest on our product.
In particular, we''d like to recommend to use toolchain 2009q3 version. Our development team recommend this version.
(arm-2009q3-67-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2)
Please send full details of your build error log.
Thank you.
Sincerely yours,
Oh, where to begin..
I believe that's the toolchain they recommend in their "instructions".. Regardless, we figured that out rather quickly.
The problem here is that what they released to us was not their production source code. It was some early development version of it, with a number of issues, the most prominent being it didn't even compile as provided.
The fact that we had to patch sound/soc/codecs/wm8994.c so that the phone wouldn't drop audio 5-10 seconds into every phone call is pretty much concrete proof that what we were given was development code, not production code.
I'm going to pass on the exact same message back, we'll see what happens.
Probably nothing.
at this point it's fairly pointless. we have been hastling them for almost a month now, and they've done nothing. despite all the issues with the code, our dev team has gotten their provided kernel source to boot and run with no issues, hence the overclocking kernels available. even if they did release the actual source now it's basically worthless. unless it's for a higher kernel version we can use for a froyo rom.
sonofskywalker3 said:
at this point it's fairly pointless. we have been hastling them for almost a month now, and they've done nothing. despite all the issues with the code, our dev team has gotten their provided kernel source to boot and run with no issues, hence the overclocking kernels available. even if they did release the actual source now it's basically worthless. unless it's for a higher kernel version we can use for a froyo rom.
Click to expand...
Click to collapse
Its not whether I its pointless or not, they need to be held accountable for uploading bad source which I believe is against the gpl. Funny how their build sh is configured for 2010 and they recommend 2009q3...
Sent from my SCH-I500 using XDA App
I agree, but is sending them a million emails that they mostly ignore really "holding them accountable"? I think not.
So ignoring them is the answer?
I think not.
Feedback is the most civil thing at this point. If its ignored, I'm sure more stern action can be taken, if the community as a whole decides to.
It works but it does not ring. You can use it to test roms if a (developer) needs one. PM me.
send it to the CyanogenMod dev's so we can get the eris on the supported devices list =D
Yeah, I thought one of the things we needed for official support was to send them a phone. Not that the current ports aren't great(tazz's and workshed's) but official support may help resolve some of the minor bugs that are encountered.
Guys, they don't need a phone. What they want is someone to submit a working vendor tree for the Eris on github, following the cm rules. But then that individual has to 'maintain' the tree and become part of the official cm team.
I would, but can't really commit to being the maintainer right now.
I just wanted to up date. The phone speaker phone does not work but he head set does.
workshed said:
Guys, they don't need a phone. What they want is someone to submit a working vendor tree for the Eris on github, following the cm rules. But then that individual has to 'maintain' the tree and become part of the official cm team.
I would, but can't really commit to being the maintainer right now.
Click to expand...
Click to collapse
What is a vendor tree?
Sent from my GSBv1.9 ERIS using XDA Premium App
wildstang83 said:
What is a vendor tree?
Click to expand...
Click to collapse
Most of the source code is not device specific, but since each device is different... There has to be some code that only applies to that particular device. That's the vendor tree. It's basically some build files that grab the correct drivers, libs, and other files for that specific device. Officially supported devices have their trees integrated into the main CM source, so that the device can be selected at build time.
We do the same thing with the Eris, except the tree is pulled in from a separate repo before building.
dwrecording said:
I just wanted to up date. The phone speaker phone does not work but he head set does.
Click to expand...
Click to collapse
If a dev doesn't want it, I would sell it on eBay if you're not up to buying a speaker to replace it yourself. Someone will buy it. Probably make at least $40-$60 or more.
Sent a PM like 6 hours ago lol. Also, since I decided to be a retard and take my phone swimming with me in the Pacific ahaha. I could really use this !
EDIT: I'm kind of a dev. I do have 2 ROMs out...............
roirraW "edor" ehT said:
If a dev doesn't want it, I would sell it on eBay if you're not up to buying a speaker to replace it yourself. Someone will buy it. Probably make at least $40-$60 or more.
Click to expand...
Click to collapse
you could try:
http://swappa.com/
says an eris goes for 90-120$
i dont know how "hot" they are selling but always worth a shot
Seriously, no response to my pm or multiple posts ? Ok.
spc_hicks09 said:
Seriously, no response to my pm or multiple posts ? Ok.
Click to expand...
Click to collapse
I hate lack of communication. If he changed his mind he should just tell you. No offense to the OP if I'm out of line.
So I've been troubleshooting all morning with modifying our device tree + OmniROM source to be able to attempt a jflteatt build of the new ROM, and I finally have my build compiling as I write this.
However, based on the trouble I've had getting the grouper (N7) build to boot - it compiled just fine - I'm doubting that I'll be able to get our device's build booted on the first try either (assuming this build finishes without error).
As such, I wanted to reach out to you guys to see if anyone else is currently working on building this ROM - and hopefully create a place where we can share tips or troubleshoot for our specific devices.
I apologize if this is the wrong forum to post this in, but I figured if I posted this in any of the main forums it would get flooded with "plz build for Sprint S4" or "ETA plz?" posts....lol.
http://forum.xda-developers.com/showthread.php?t=2483622
Grarak might be able to help...
DSA said:
http://forum.xda-developers.com/showthread.php?t=2483622
Grarak might be able to help...
Click to expand...
Click to collapse
Thanks....I saw that thread, but figured that the chipsets are different enough that it wouldn't be of that much use. Am I off-base there?
CPA Poke said:
Thanks....I saw that thread, but figured that the chipsets are different enough that it wouldn't be of that much use. Am I off-base there?
Click to expand...
Click to collapse
no your in the right forum, and yes your also right that that omnirom thread, while semi useful, isnt the best since our processors are different and what works for them might not work for us. Looking forward to watching this develop though,
Do you mean porting from source?
CNexus said:
Do you mean porting from source?
Click to expand...
Click to collapse
Of course. I guess "port" probably wasn't the best verbiage...more precisely, adding our device tree to the OmniROM source
There's a write up on xda-university on porting from source. Might wanna take a look at it
I'm not sure what the point of this thread is though. No point discussing it if you haven't even tried it/reached a compile/runtime error
CNexus said:
There's a write up on xda-university on porting from source. Might wanna take a look at it
I'm not sure what the point of this thread is though. No point discussing it if you haven't even tried it/reached a compile/runtime error
Click to expand...
Click to collapse
That guide was my main starting point with all of this, actually...however I'm thinking that it was written by someone who's first language is something other than English, as I always end up getting lost midway through because I literally can't figure out what he/she is trying to say.
And I've been at work all day but managed to remote in to my home PC a couple times - both times discovering that the build had failed, and both times attempting to troubleshoot each error. I was planning on posting the error and my roomservice.xml (as I suspect it's probably where I'm going wrong), so I'll post them shortly.
CPA Poke said:
That guide was my main starting point with all of this, actually...however I'm thinking that it was written by someone who's first language is something other than English, as I always end up getting lost midway through because I literally can't figure out what he/she is trying to say.
And I've been at work all day but managed to remote in to my home PC a couple times - both times discovering that the build had failed, and both times attempting to troubleshoot each error. I was planning on posting the error and my roomservice.xml (as I suspect it's probably where I'm going wrong), so I'll post them shortly.
Click to expand...
Click to collapse
I don't know your circumstances, but I was able to understand the guide perfectly and my first language is english.
It might be better if you take to the OmniROM irc chat (#omni for dev chat) and say you're trying to add support for your device and just list the error you're getting.
CNexus said:
I don't know your circumstances, but I was able to understand the guide perfectly and my first language is english.
It might be better if you take to the OmniROM irc chat (#omni for dev chat) and say you're trying to add support for your device and just list the error you're getting.
Click to expand...
Click to collapse
Haha, my "circumstances" are that I'm am accountant (see my user name) and I tend to over analyze things and create problems where there are none.
I'm also trying as hard as I can to learn as much as I can, all the while trying not to bother the real devs...but I'm late to the Android game (relatively) and it seems to me that the distribution of users on XDA is pretty polarizing - either they are (a) seasoned devs who either have prior/current experience in programming or have some type of IT background, or (b) are useless, ungrateful noobs who just got rid of their iPhone yesterday and now want to go bonkers hacking their device. At least those users that actually post.
So my problem thus far (and the main reason why I thought this was the most appropriate forum to have this discussion) is that, in the year that I've been on here, I've had a hard time finding any material for folks like me...people who enjoy LEARNING (not just typing a problem and having someone fix it for them), enjoy exploring the extent that our awesome technology can be taken to, and are genuinely interested in being a "seeder" - not a "leecher" - in the development community.
So, again, I apologize if this doesn't belong here. I did read the rules sticky before even starting the OP (imagine that lol), and I guess my interpretation was that this sort of discussion would be welcome. I wasn't asking anyone to fix my problems, I wasn't asking for ETAs...I just wanted to offer up a medium for discussion for anyone interested.
But I will check out the irc. Good idea, thanks.
've been working on it with all the necessary file (so i think). One of my team mates help me out with jf tree but havn' had any successful build yet. usually get an error when its close to being finish so have to troubleshoot one fail build at a time
I dont know why you need to run of to the omini irc and abandon this one...i believe in team work. the IRC is a lot of help they help me t roubleshoot my way through...at the same time will be nice to have a discussion among individuals who actually uses our device. the people i've met in the irc do not use gs4 or any form of it from what i saw
CPA Poke said:
Haha, my "circumstances" are that I'm am accountant (see my user name) and I tend to over analyze things and create problems where there are none.
I'm also trying as hard as I can to learn as much as I can, all the while trying not to bother the real devs...but I'm late to the Android game (relatively) and it seems to me that the distribution of users on XDA is pretty polarizing - either they are (a) seasoned devs who either have prior/current experience in programming or have some type of IT background, or (b) are useless, ungrateful noobs who just got rid of their iPhone yesterday and now want to go bonkers hacking their device. At least those users that actually post.
So my problem thus far (and the main reason why I thought this was the most appropriate forum to have this discussion) is that, in the year that I've been on here, I've had a hard time finding any material for folks like me...people who enjoy LEARNING (not just typing a problem and having someone fix it for them), enjoy exploring the extent that our awesome technology can be taken to, and are genuinely interested in being a "seeder" - not a "leecher" - in the development community.
So, again, I apologize if this doesn't belong here. I did read the rules sticky before even starting the OP (imagine that lol), and I guess my interpretation was that this sort of discussion would be welcome. I wasn't asking anyone to fix my problems, I wasn't asking for ETAs...I just wanted to offer up a medium for discussion for anyone interested.
But I will check out the irc. Good idea, thanks.
Click to expand...
Click to collapse
Your discussion is welcome here. I completely understand your dilemma. But if you are having issues it might be beneficial to post the specific issue you're having instead of trying to promote discussion in this thread. Im sure if you asked someone they would explain how they got to the solution of the problem.
Sent from my XT912 using xda app-developers app
CPA Poke said:
Haha, my "circumstances" are that I'm am accountant (see my user name) and I tend to over analyze things and create problems where there are none.
I'm also trying as hard as I can to learn as much as I can, all the while trying not to bother the real devs...but I'm late to the Android game (relatively) and it seems to me that the distribution of users on XDA is pretty polarizing - either they are (a) seasoned devs who either have prior/current experience in programming or have some type of IT background, or (b) are useless, ungrateful noobs who just got rid of their iPhone yesterday and now want to go bonkers hacking their device. At least those users that actually post.
So my problem thus far (and the main reason why I thought this was the most appropriate forum to have this discussion) is that, in the year that I've been on here, I've had a hard time finding any material for folks like me...people who enjoy LEARNING (not just typing a problem and having someone fix it for them), enjoy exploring the extent that our awesome technology can be taken to, and are genuinely interested in being a "seeder" - not a "leecher" - in the development community.
So, again, I apologize if this doesn't belong here. I did read the rules sticky before even starting the OP (imagine that lol), and I guess my interpretation was that this sort of discussion would be welcome. I wasn't asking anyone to fix my problems, I wasn't asking for ETAs...I just wanted to offer up a medium for discussion for anyone interested.
But I will check out the irc. Good idea, thanks.
Click to expand...
Click to collapse
I understand, I've been through the exact same thing (and am still usually unable to find help on things like source building and kernels). I was not trying to discredit your post, just
And by "circumstances" I meant whatever language/languages you know, or background you come from, etc etc that lead you to have trouble understanding the xda-university write-up.
No offense was intended, but it does help to fix errors when you post the error you're getting lol.
Surge1223 said:
Your discussion is welcome here. I completely understand your dilemma. But if you are having issues it might be beneficial to post the specific issue you're having instead of trying to promote discussion in this thread. Im sure if you asked someone they would explain how they got to the solution of the problem.
Sent from my XT912 using xda app-developers app
Click to expand...
Click to collapse
CNexus said:
I understand, I've been through the exact same thing (and am still usually unable to find help on things like source building and kernels). I was not trying to discredit your post, just
And by "circumstances" I meant whatever language/languages you know, or background you come from, etc etc that lead you to have trouble understanding the xda-university write-up.
No offense was intended, but it does help to fix errors when you post the error you're getting lol.
Click to expand...
Click to collapse
Absolutely agreed. Honestly I was trying to be as non-noob as possible and wanted to try and work through as many of the errors related to syntax, etc on my own, saving the real discussion for the thread.
I'm going to take a look at this for jfltespr this weekend. I'll start adding my notes here as well.
garwynn said:
I'm going to take a look at this for jfltespr this weekend. I'll start adding my notes here as well.
Click to expand...
Click to collapse
I've been working on JFLTEATT for a bit, very, very frustrating since CM's selinux and AOSP selinux are very different. causing a LOT of build issues.
take a look at my github, you'll be able to fork my
android_kernel_samsung_jf
android_device_samsung_jf-common
device trees
https://github.com/jakew02
hopefully this gives you a head-start.
I should have a build up for jflteatt within the next few hours , by tonight im hoping.
Update So, i got a booting build. just needs to be fine-tuned to actually work!
jakew02 said:
I've been working on JFLTEATT for a bit, very, very frustrating since CM's selinux and AOSP selinux are very different. causing a LOT of build issues.
take a look at my github, you'll be able to fork my
android_kernel_samsung_jf
android_device_samsung_jf-common
device trees
https://github.com/jakew02
hopefully this gives you a head-start.
I should have a build up for jflteatt within the next few hours , by tonight im hoping.
Update So, i got a booting build. just needs to be fine-tuned to actually work!
Click to expand...
Click to collapse
Seriously? That's great! I appreciate the PM's btw.
Did you run into this error at all during your compile?
Code:
Install: /home/dev/omni/out/target/product/jflteatt/system/usr/share/zoneinfo/tzdata
/home/dev/omni/out/host/linux-x86/bin/checkpolicy: *loading policy configuration from /home/dev/omni/out/target/product/jflteatt/obj/ETC/sepolicy_intermediates/policy.conf
Install: /home/dev/omni/out/target/product/jflteatt/root/fstab.qcom
device/samsung/jf-common/sepolicy/property.te":2:ERROR 'duplicate declaration of type/attribute' at token ';' on line 6889:
#line 1 "device/samsung/jf-common/sepolicy/property.te"
type bluetooth_prop, property_type;
checkpolicy: *error(s) encountered while parsing configuration
make: *** [/home/dev/omni/out/target/product/jflteatt/obj/ETC/sepolicy_intermediates/sepolicy] Error 1
make: *** Waiting for unfinished jobs....
Edit: Forked your device trees, and syncing now. While that's downloading, I'm curious what "fine tuning" you're referring to? Are you having NFC/bluetooth issues by chance?
I remember reading in the i9500 thread that @Grarak was having issues with bluetooth.
CPA Poke said:
Seriously? That's great! I appreciate the PM's btw.
Did you run into this error at all during your compile?
Code:
Install: /home/dev/omni/out/target/product/jflteatt/system/usr/share/zoneinfo/tzdata
/home/dev/omni/out/host/linux-x86/bin/checkpolicy: *loading policy configuration from /home/dev/omni/out/target/product/jflteatt/obj/ETC/sepolicy_intermediates/policy.conf
Install: /home/dev/omni/out/target/product/jflteatt/root/fstab.qcom
device/samsung/jf-common/sepolicy/property.te":2:ERROR 'duplicate declaration of type/attribute' at token ';' on line 6889:
#line 1 "device/samsung/jf-common/sepolicy/property.te"
type bluetooth_prop, property_type;
checkpolicy: *error(s) encountered while parsing configuration
make: *** [/home/dev/omni/out/target/product/jflteatt/obj/ETC/sepolicy_intermediates/sepolicy] Error 1
make: *** Waiting for unfinished jobs....
Edit: Forked your device trees, and syncing now. While that's downloading, I'm curious what "fine tuning" you're referring to? Are you having NFC/bluetooth issues by chance?
I remember reading in the i9500 thread that @Grarak was having issues with bluetooth.
Click to expand...
Click to collapse
bluetooth should be fixed now
https://github.com/omnirom/android_...mmit/62d71414709f0f6282b8d108cc66716f37872f96
btw remove selinux union
then it should build correct
Grarak said:
bluetooth should be fixed now
https://github.com/omnirom/android_...mmit/62d71414709f0f6282b8d108cc66716f37872f96
btw remove selinux union
then it should build correct
Click to expand...
Click to collapse
MONEY, thanks my friend.
CPA Poke said:
Seriously? That's great! I appreciate the PM's btw.
Did you run into this error at all during your compile?
Code:
Install: /home/dev/omni/out/target/product/jflteatt/system/usr/share/zoneinfo/tzdata
/home/dev/omni/out/host/linux-x86/bin/checkpolicy: *loading policy configuration from /home/dev/omni/out/target/product/jflteatt/obj/ETC/sepolicy_intermediates/policy.conf
Install: /home/dev/omni/out/target/product/jflteatt/root/fstab.qcom
device/samsung/jf-common/sepolicy/property.te":2:ERROR 'duplicate declaration of type/attribute' at token ';' on line 6889:
#line 1 "device/samsung/jf-common/sepolicy/property.te"
type bluetooth_prop, property_type;
checkpolicy: *error(s) encountered while parsing configuration
make: *** [/home/dev/omni/out/target/product/jflteatt/obj/ETC/sepolicy_intermediates/sepolicy] Error 1
make: *** Waiting for unfinished jobs....
Edit: Forked your device trees, and syncing now. While that's downloading, I'm curious what "fine tuning" you're referring to? Are you having NFC/bluetooth issues by chance?
I remember reading in the i9500 thread that @Grarak was having issues with bluetooth.
Click to expand...
Click to collapse
No it boots up.. Shows the boot animation, the capacitative buttons light up and vibrate on touch, but the screen stays black and it eventually force reboots. i originally used CyanogenMod trees but decided to rebase to these device trees.https://github.com/AOSP-S4, but running into errors again.
I PM'd task and he said that he already has it up and running and there's no need to port,, just sync add device trees and build.. but when i did that i ran into about a million build failures that i had to manually fix, hence the github
Update: so based on what task said, I'm going to try just creating my own device tree, basing off of cyanogenmod's very first commit for jflteatt , jf-common , and kernel_samsung_jf. here goes nothing
Sent from my SGH-I337 using Tapatalk
I am surprised that you missed that or maybe I missed it here
I dirtyflashed it over a CM13 and it seems to work
testing now
here are the roms/links
on german x820 forum its clear #1
http://download.mokeedev.com/?device=le_x2
dont forget its without gapps so flash add them when you like google stuff
Se didnt miss it but thanks anyway. That ROM was deleted from xda due to the fact that some users that dont do anything else but complaining, and attacking the dev. The dev from mokee hás informed that hes not posting anymore ROMs in xda. Nougat included
What is the dif btw release n nightlies
nosidefcp said:
Se didnt miss it but thanks anyway. That ROM was deleted from xda due to the fact that some users that dont do anything else but complaining, and attacking the dev. The dev from mokee hás informed that hes not posting anymore ROMs in xda. Nougat included
Click to expand...
Click to collapse
Hello. You forgot to tell the full truth. The case is the dev was asked to release sources and he refused.
Regards Filozof71
Sent from my Le X820 using Tapatalk
Filozof71 said:
Hello. You forgot to tell the full truth. The case is the dev was asked to release sourced and he denied.
Regards Filozof71
Sent from my Le X820 using Tapatalk
Click to expand...
Click to collapse
Thats not true. He said he wasnt releasing the source in that day. Three por four days later he released here the source code
nosidefcp said:
Thats not true. He said he wasnt releasing the source in that day. Three por four days later he released here the source code
Click to expand...
Click to collapse
Incorrect. People were asking for the Device Tree used to build Mokee, which wasn't and still hasn't been provided. XDA isn't a place for you to download roms, it's a developer community. Pretty sure the device tree would have been converted from one that was available (Probably OP3) and not sharing it is disrespectful to every developer who has worked on it previously.
https://github.com/MoKee/android_device_letv_le_x2 is empty.
mikeysteele said:
Incorrect. People were asking for the Device Tree used to build Mokee, which wasn't and still hasn't been provided. XDA isn't a place for you to download roms, it's a developer community. Pretty sure the device tree would have been converted from one that was available (Probably OP3) and not sharing it is disrespectful to every developer who has worked on it previously.
https://github.com/MoKee/android_device_letv_le_x2 is empty.
Click to expand...
Click to collapse
which rule say MUST share device tree?you can ask leeco share official device tree too.TRY HARDER
ffboy2009 said:
which rule say MUST share device tree?you can ask leeco share official device tree too.TRY HARDER
Click to expand...
Click to collapse
Who's talking about rules? This is a community and communities have standards. You're free to do whatever you like but expect people to be unhappy if you disrespect the community.
ffboy2009 said:
which rule say MUST share device tree?you can ask leeco share official device tree too.TRY HARDER
Click to expand...
Click to collapse
First of all: THANKS for your ROMs. Second: i would really consider publishing the device tree, because there might be a few others who would like to contribute.
Although the Max 2 is a rather "specific" smartphone, which - outside of India and China - nobody really considers buying.
ffboy2009 said:
which rule say MUST share device tree?you can ask leeco share official device tree too.TRY HARDER
Click to expand...
Click to collapse
The Open Source rule and spirit. We share our knowledge and we don't hide it.
https://github.com/deadman96385/android_device_leeco_x2
https://github.com/AndroPlus-org/android_device_leeco_x2?files=1
I know is difficult to you to understand this. There must be a reason why you don't want to provide your sources.
http://forum.xda-developers.com/showthread.php?t=3494247
ffboy doesn't own anybody anything. He releases his ROM's for free, he doesn't force you to use them. Many rom developers don't release their source code/device trees, one reason is that people could take there hard work getting everything to work and use to build their own ROM's and get donations from them without doing any hard work themselves. Even my grandma can build a ROM when eveyrthing is handed to her. One example is the very resepected developer arter97 who didn't release cyanogenmod device trees for s6 for a while when he was developing for s6. Get off ffboy's case, he is a developer and doesn't deserve this, if there was a downvote in xda I would downvote the haters. You've already been warned by the mods yet you still pour hate on to the dev.
Edit: I agree with ffboy we should continue petitioning LeEco for device trees.
@whymoo
I am not arter97, i don't care what he does and i don't accept donations.
ffboy released his rom under mokee s name who they aclame to be "open source". Also i except to see the whole source and not part of it.
If ffboy doesn't like this he could publice his rom to a hoster like "mega"
ffboy and not me already copied code and signed the same code as his own and don't gave proper credit.
We are a big community and we help each other. We share our knowledge and don't hide it. I and other people don't like to reinvend the wheel again. This is a waste of precius time who lot of us they don't have. Yes! we can contribute, merge bugs and maybe compile other roms and yes, ffboy must accept, that maybe me or others wanna use his device tree or some other code. BUT we don't forget to give credits.
Btw i don't be warned and i don't see a reason why should be.
It's CM or stock based?
ir work?
monleylord said:
@whymoo
I am not arter97, i don't care what he does and i don't accept donations.
ffboy released his rom under mokee s name who they aclame to be "open source". Also i except to see the whole source and not part of it.
If ffboy doesn't like this he could publice his rom to a hoster like "mega"
ffboy and not me already copied code and signed the same code as his own and don't gave proper credit.
We are a big community and we help each other. We share our knowledge and don't hide it. I and other people don't like to reinvend the wheel again. This is a waste of precius time who lot of us they don't have. Yes! we can contribute, merge bugs and maybe compile other roms and yes, ffboy must accept, that maybe me or others wanna use his device tree or some other code. BUT we don't forget to give credits.
Btw i don't be warned and i don't see a reason why should be.
Click to expand...
Click to collapse
first i opensourced kernel soucre as GPL requirement,but device tree was not GPL and you do not have the right to force me do things i dont like.
2nd i know i made mistakes on kernel source for commit authorship brcause i am not good at git tools but i have already corrected them.
i dont care you like me and my rom or not
i have released all source of mi max on my github
the only reason i dont release max2 device tree is,
Some people here is just do nothing but PUSHING AND ATTACKING me because they want my device tree to build there roms to gain Respect and donations i think.they are so rude and ridiculous
when i said "No plan to release kernel source RECENTLY" and released a few days later,they don't care and start attacking and pushing
i also dont warned by forum moderatoer by not released device tree
So ban me out of this forum if you can
ffboy2009 said:
first i opensourced kernel soucre as GPL requirement,but device tree was not GPL and you do not have the right to force me do things i dont like.
2nd i know i made mistakes on kernel source for commit authorship brcause i am not good at git tools but i have already corrected them.
i dont care you like me and my rom or not
i have released all source of mi max on my github
the only reason i dont release max2 device tree is,
Some people here is just do nothing but PUSHING AND ATTACKING me because they want my device tree to build there roms to gain Respect and donations i think.they are so rude and ridiculous
when i said "No plan to release kernel source RECENTLY" and released a few days later,they don't care and start attacking and pushing
i also dont warned by forum moderatoer by not released device tree
So ban me out of this forum if you can
Click to expand...
Click to collapse
I don't care if you like ne or not either. I gave you also a like. I don't care either to gain Respect or earn money through donations.
You are the only one here who try to gain respect or donations but your behavior shows me clearly that you are reacting like a little defiant child who felt driven into a corner.
I made a Pointment about you and you have to accept it.
monleylord said:
I don't care if you like ne or not either. I don't care either to gain Respect or earn money through donations. You are the only one here who try to gain respect or donations but your behavior shows me clearly that you are rect like a child. I made a Pointment about you and you have to accept it.
Click to expand...
Click to collapse
I'd be interested in the device tree so I could play around building with some custom toolchains. All my phones run ROM's I've compiled myself but I've never shared them with anybody here as they aren't my work.
mikeysteele said:
I'd be interested in the device tree so I could play around building with some custom toolchains. All my phones run ROM's I've compiled myself but I've never shared them with anybody here as they aren't my work.
Click to expand...
Click to collapse
This will become ridiculous be smart and open with everybody we talk about a phone don't forget this please
sdevaux said:
This will become ridiculous be smart and open with everybody we talk about a phone don't forget this please
Click to expand...
Click to collapse
I think you misunderstand. Building ROMs with custom toolchains and then posting them here would be passing off the work of others as my own, which is not on. I'm not making any source code changes.
mikeysteele said:
I think you misunderstand. Building ROMs with custom toolchains and then posting them here would be passing off the work of others as my own, which is not on. I'm not making any source code changes.
Click to expand...
Click to collapse
I understand it's just that everyone should be open with others it would allow us to move forward the rom development for this model that's just my opinion