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
Related
@all the coders
The community has people with very good coding skills (we know them and they know them each-other), so why you(we) do not concentrate your(our) skills and work on one big open-source app. The synergetic (network) effects would make it possible to build and later host a stable and all included community-based-open-source-group-coded app!
We have so many pseudo-proprietary based tools:
ROM-Kitchen, Hermes ROM Koch, nbhextract, et cetera...
Is think the best would be, to set up something like an open-source-project. - we can host the codesnippets on a subversion or cvs directory or something else to manage the distributed progress.
The efforts would be much bigger and come much faster, that should be clear for everybody.
So please let me know and i will set up such a directory!
Maybe pof can set up a poll for this - so we can get a democracy-based decision!
AFAIK this would be the first joined forces XDA-Developers development and i think it is realy the time for it!
And what are you waiting for ? Start development of this one big open-source app by yourself right now. And others would join if they find it interesting.
Des said:
And what are you waiting for ? Start development of this one big open-source app by yourself right now. And others would join if they find it interesting.
Click to expand...
Click to collapse
I created a svn-repository,
please PM me with your email-adress to send you the account information!
I've meant start development not creating svn res
Des said:
I've meant start development not creating svn res
Click to expand...
Click to collapse
I know but at first my programming skills are not as good as your skills are and at second why i should start a new app since we have a lot of lines already?
but as far as is see you won´t join, will you?
apokryphus said:
why i should start
Click to expand...
Click to collapse
why others should ?
but as far as is see you won´t join, will you?
Click to expand...
Click to collapse
join to what ?
Des said:
why others should ?
join to what ?
Click to expand...
Click to collapse
Others started already, so they just have to put their code in there and others can modify it.
Join the svn...
BTW: You know what a svn is, don´t you?
apokryphus said:
they just have to put their code in there and others can modify it.
Click to expand...
Click to collapse
There is sourceforge for it. And there was cvs rep on xda-developers. If you going to host another - that's good. But how it relates to starting of development of "a stable and all included community-based-open-source-group-coded app" ?
Join the svn...
BTW: You know what a svn is, don´t you?
Click to expand...
Click to collapse
svn is in the first place code hosted there. No code == nothing to join.
Well, e.g. dutty could host his code in there, if he wants; olipro could host his code in there, if he wants; like all the others.
that would be good start.
Then merge the code and bring up new features... like guis (i would do that e.g.)
And yes, i can not host any code because i did not wrote something and i do not want to decompile the versions we have, because of ip, the developer should agree with it first.
besides this is just an idea, but reading your posts it seems this idea is not very welcome.
i wrote something like this to a mod here 2 weeks ago, did not got an answer, so at all i think it could really be a bad idea - however maybe some others will say somthing about it.
apokryphus said:
besides this is just an idea, but reading your posts it seems this idea is not very welcome.
i wrote something like this to a mod here 2 weeks ago, did not got an answer, so at all i think it could really be a bad idea - however maybe some others will say somthing about it.
Click to expand...
Click to collapse
I personally think it's a great idea! It's just too bad I'm not a developer; I wish I could help!
But yes, I believe that if everyone here worked together on a project, the results could be wonderful. I guess that doesn't mean much since I don't have the skills needed to contribute, but it still sounds ideal.
Des I Think Apokryphus Is Main Aim Is An Open Source ROM Kitchen.
With The Issue That ahok_hk Had With Olipro About Him Releasing A Ported Version Of His Software, I Think He Sees The Coders Working Against Each Other (Or At Least Being Rivals). And Wants Everyone To Play Nice To Create One Kitchen That Is Fast And Simple. Which Means That It Has To Be Open Source So Everyone Can Make Reccomendations On How To Update The Software.
Cheers
mousey_ said:
Des I Think Apokryphus Is Main Aim Is An Open Source ROM Kitchen.
With The Issue That ahok_hk Had With Olipro About Him Releasing A Ported Version Of His Software, I Think He Sees The Coders Working Against Each Other (Or At Least Being Rivals). And Wants Everyone To Play Nice To Create One Kitchen That Is Fast And Simple. Which Means That It Has To Be Open Source So Everyone Can Make Reccomendations On How To Update The Software.
Cheers
Click to expand...
Click to collapse
Exactly, but not only for recommendation also for modifying the software, thats the main goal - joined people can add their own lines of code to provide the stability or usability for instance.
i hope i did not got you wrong, what means that i think you meant with update not modifying. but in case of that is the meaning i totaly agree with your opinion.
sorry but i am not a native speaker and sometimes i have got some problem with the meaning of the translations.
see quine, in word and object, chapter 2 about the indeterminacy of translation.
mousey_ said:
Des I Think Apokryphus Is Main Aim Is An Open Source ROM Kitchen.
With The Issue That ahok_hk Had With Olipro About Him Releasing A Ported Version Of His Software, I Think He Sees The Coders Working Against Each Other (Or At Least Being Rivals). And Wants Everyone To Play Nice To Create One Kitchen That Is Fast And Simple. Which Means That It Has To Be Open Source So Everyone Can Make Reccomendations On How To Update The Software.
Cheers
Click to expand...
Click to collapse
I must stress that everyone has their rights for their own intellectual property because the have created them using many many hours of effort. And I was not saying that I am not going to release the code. But just not right now coz it is still in beta and many fixes/function will be added. And there is not such "The Coders Working Against Each Other" in my mine at all. Coders should "respect" each other.
For the case of Olipro, he not only stole and released the code "without my prior agreement", but still releasing it after I suggested him to just put those code in his kitchen.
On the other hand, dutty is good. Why? because he also wanted to use the souce code of aChef, and he did ask me before he wants to put it in his kitchen.
BTW, originally I have successfully added many new functions to aChef that no one has done/thought before, but I see no point to release them or to continue my effort now.
Anyway every one has their own thoughts about intellectual proterty. And I am not going to discuss here anymore. Good luck and Good bye to all.
it's a port... it's not your code, you didn't license your code, and you did not say anywhere that anyone was forbidden from creating a derivative work, I made it to benefit the community, if you want to let ego get in the way, that's your problem buddy, not mine.
while I reconize the merrits of open source, I think people should respect (an appreciate) the hard work that people have done. The people in this forum have made some wonderful software, provided it to us free of charge. If they want to put their hard work out there in an open source form, that's great, if not, that's also great - it should be their choice with no pressure.) I've not even seen anybody complain about their software being incorperated into other programs - they've just asked that you respect their IP which in my opinion is perfectly fair.
If you'd like something put into opensource, write a nice letter suggesting it with no pressure, and then leave it to the developer. If they want to they will, if not, simply thank them for their hard work an appreciate the product they've provided for you. If you push people who don't want to release it for whatever their reason, you'll alienate them and they'll cease development which would be a detrament to everybody!
<steps down off soapbox>Sorry for my pointless ramblings - please, continue ignoring me!
ahlok_hk said:
BTW, originally I have successfully added many new functions to aChef that no one has done/thought before, but I see no point to release them or to continue my effort now.
Click to expand...
Click to collapse
*cough* VAPOURWARE *cough*
we all appreciate your effort including me... but if diddums wants to throw a tantrum the feel free
Wondering if someone want's to throw up a complete listing of kernels, roms, etc. like all the other Galaxy S variant forums have.
wait.
damn.
nvm.
I really, really miss my Nexus, but at least I have service now.
Daswolven said:
Wondering if someone want's to throw up a complete listing of kernels, roms, etc. like all the other Galaxy S variant forums have.
wait.
damn.
nvm.
I really, really miss my Nexus, but at least I have service now.
Click to expand...
Click to collapse
im not the flaming type....but this is really unnecessary.
wasupwithuman said:
im not the flaming type....but this is really unnecessary.
Click to expand...
Click to collapse
Isn't that like saying "I'm not the racist type, but...."
Of course it's unnecessary. But there's nothing else to do at the moment on here. It's a little frustrating to see the work in the other variant forums, and to hear crickets and hopes in here.
I KNOW incredible people are hard at work right this minute to fix it, but....
It's looking like we will be last to see Voodoo, last to see Froyo, and last to see CM.
I'm not the whining type, but.....
I'm growing restless. lol.
If you're (the general you, not calling anyone out) interested in development, I suggest joining the IRC channel #samsung-fascinate on freenode. This is where you'll get the most up to date information. (For example, we were testing CWM recovery with Koush long before the first post showed up here).
If you'd like a small project to get you in the swing of things, and you're slightly familiar with linux and can get a VM up and running, you could always download the source from Samsung and learn how to compile your own kernel. I've seen a few people in the channel go from knowing pretty much nothing to getting their kernels compiled. Even if you can't get a linux VM up and running, maybe someone in the channel could help you with that.
Obviously thanks to Samsung, the kernel won't boot, but going through the process will help broaden your knowledge and give you some insight into Android and Linux in general. There's plenty to learn, and there's a wide range of people there with varying levels of expertise.
There are a number of us who have been at this since day 1, and since we "know" each other a little better, we often communicate directly between ourselves. If you pop in the IRC channel and don't see anything, don't take that to mean that no work is being done.
There are some major obstacles to be overcome here, and Samsung didn't do us any favors. We're working a number of things right now, getting the kernel source fixed, AOSP, voodoo, etc.. It will take time, but we're getting there.
Daswolven said:
Isn't that like saying "I'm not the racist type, but...."
Of course it's unnecessary. But there's nothing else to do at the moment on here. It's a little frustrating to see the work in the other variant forums, and to hear crickets and hopes in here.
I KNOW incredible people are hard at work right this minute to fix it, but....
It's looking like we will be last to see Voodoo, last to see Froyo, and last to see CM.
I'm not the whining type, but.....
I'm growing restless. lol.
Click to expand...
Click to collapse
if you notice i did not flame you... I could have, but i respect you as a xda member... I just said this was unnecessary, because it is. Like namebrandon said, join the irc channel, but starting a topic like that, then just saying some nonsense, really doesnt need to be done... Your a senior member, we need to be a good influence for the new people. Like i said, i've seen you help out and i respect that; but lets try to keep the Android Development to Android Development. If it's something like this atleast file it in general.
namebrandon said:
If you're (the general you, not calling anyone out) interested in development, I suggest joining the IRC channel #samsung-fascinate on freenode. This is where you'll get the most up to date information. (For example, we were testing CWM recovery with Koush long before the first post showed up here).
If you'd like a small project to get you in the swing of things, and you're slightly familiar with linux and can get a VM up and running, you could always download the source from Samsung and learn how to compile your own kernel. I've seen a few people in the channel go from knowing pretty much nothing to getting their kernels compiled. Even if you can't get a linux VM up and running, maybe someone in the channel could help you with that.
Obviously thanks to Samsung, the kernel won't boot, but going through the process will help broaden your knowledge and give you some insight into Android and Linux in general. There's plenty to learn, and there's a wide range of people there with varying levels of expertise.
There are a number of us who have been at this since day 1, and since we "know" each other a little better, we often communicate directly between ourselves. If you pop in the IRC channel and don't see anything, don't take that to mean that no work is being done.
There are some major obstacles to be overcome here, and Samsung didn't do us any favors. We're working a number of things right now, getting the kernel source fixed, AOSP, voodoo, etc.. It will take time, but we're getting there.
Click to expand...
Click to collapse
I'm one of those people... First kernel i've ever compiled.
and/or you could harass samsung for the kernel signing keys, no coding ability required.
Jesus people. I'll post a ROM if it'll stop all these nonsense threads.
Voodoo kernel is the works also. Coding helps development, not complaining and being sarcastic.
jt1134 said:
Jesus people. I'll post a ROM if it'll stop all these nonsense threads.
Voodoo kernel is the works also. Coding helps development, not complaining and being sarcastic.
Click to expand...
Click to collapse
really?
you have the signing key for the kernel?
signing key? don't need no stinking signing key. bootloader'll boot any (working) kernel I've tried
HUMAN!!!! YEAH!!! U R EVERYWHERE I LOVE IT!!!
Sent from my SCH-I500 using XDA App
All fair enough. I know the work is being done, and my lack of dev skills makes it unfair for me to complain. My due apologies for the thread, I think I'm just going through flash withdrawals.
I'll make up for it in feedback, assisting, and donation when we get rolling.
Sent from my SCH-I500 using XDA App
jt1134 said:
signing key? don't need no stinking signing key. bootloader'll boot any (working) kernel I've tried
Click to expand...
Click to collapse
my bad.
I was misinformed.
http://forum.xda-developers.com/showthread.php?t=796171
ksizzle9 said:
HUMAN!!!! YEAH!!! U R EVERYWHERE I LOVE IT!!!
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
it's wasup_with_u_man....DAMNIT!!!
Yes jt1134, but as your post says, no customer kernel.
Sent from your mom's house via my fascinate.
Not to jack this thread but,....
I LIKE COOKIES!!!
(Will probably make my way onto IRC at some point)
While I suck at Java I debug like kirwoodd's mother in a flea bath.
Daswolven said:
All fair enough. I know the work is being done, and my lack of dev skills makes it unfair for me to complain. My due apologies for the thread, I think I'm just going through flash withdrawals.
I'll make up for it in feedback, assisting, and donation when we get rolling.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I know what you mean about flashing withdrawls...my Droid 1 i would seriously flash on a weekly base...
Terror_1 said:
Not to jack this thread but,....
I LIKE COOKIES!!!
(Will probably make my way onto IRC at some point)
While I suck at Java I debug like kirwoodd's mother in a flea bath.
Click to expand...
Click to collapse
See, now THATS funny.
wasupwithuman said:
I know what you mean about flashing withdrawls...my Droid 1 i would seriously flash on a weekly base...
Click to expand...
Click to collapse
Lol, I had it so bad on my N1 I would test every fourth nightly CM release with four different kernels for performance and battery. I think I had about 200 advanced quadrant screenshots to delete.
Sent from my SCH-I500 using XDA App
Why was I getting that error? It's gone now I just want to make sure it's answered for everyone else. I was flashing a rom and it was doing that. Do a reboot. Your system wont be there so reboot into botoloader and go back into recovery.
I'm getting the same error when trying to flash and when I reboot I can't get past the htc screen. I'm using the twrp recovery and I have tried resetting a few times.
EDIT**
I tried resetting my phone a couple more times and it finally just worked. I have no clue what causes this.
Original poster is correct, this method works for whatever reason. I tried it twice now.........
Same thing
Trying to flash a kernal. I tried several reboots of bootloader and recovery and no luck. I am going to flash clockwork since I am using team wins recovery and see if that works.
Same exact thing......OP's solution worked......Thank you
Yeah had this error too. I think it happens when you try to flash a different kernel on the stock ROM. After I switched to a different ROM the error went away.
Sent from my PG86100 using Tapatalk
I'm having the same issues, but rebooting isn't helping. TWRP needs to be updated to address this issue. Until then, no ROMs for me.
That error will usually occur with signature verification failures, you need to make sure that signature verification isn't turned on when installing an unsigned rom.
It would make sense if this has to do with permissions, but I have signature verification turned off in the bootloader. Is there somewhere else that signature verification needs to be turned off?
I'm getting this error trying to root the phone using the sticky guide. It happens when I try to flash the superuser file.
what the op said worked for me as well...restarted and everything worked fine
Don't waste your breath guys.
I've tried diligently to work with the devs of TWRP trying to resolve a number of outstanding issues and polish it up and they don't seem to be receptive.
https://github.com/TeamWin/Team-Win-Recovery-Project/issues/12
myn said:
Don't waste your breath guys.
I've tried diligently to work with the devs of TWRP trying to resolve a number of outstanding issues and polish it up and they don't seem to be receptive.
https://github.com/TeamWin/Team-Win-Recovery-Project/issues/12
Click to expand...
Click to collapse
Diligently work with the devs? Like this "issue" ?
http://github.com/TeamWin/Team-Win-Recovery-Project/issues/6
and this:
https://github.com/TeamWin/Team-Win-Recovery-Project/issues/7
?
And for everyone in this thread, this issue has been covered many times in our thread. It's due to compatibilities with the updater-binary and accompanying script. As we have adopted update-binary api 3, and sideload errors are because the rom/zip is trying to issue an api command no longer supported in api3. Get your nice "devs" to update their scripts.
I was receiving this error for two days after s-off and updated recovery. I was breaking my head trying to figure out a solution. I tried everything from switching recoveries to even pushing SU again. I also downloaded ROMe using my pc and my phone bc many ppl were calling the ROMs "corrupted." Nothing worked. I even received hate mail from multiple XDA members bc I was posting "too" many questions "without" searching the forum.
Solution, changing out my SDcard. LMAO, yes I know, wanted to run through a wall bc i had thought of it right off the back but did not want to believe my 32 gig card was causing the problem. I replaced with the card that came with the phone and BAM have been switching ROMs ever since.
Food for thought.
AssassinsLament said:
Diligently work with the devs? Like this "issue" ?
http://github.com/TeamWin/Team-Win-Recovery-Project/issues/6
and this:
https://github.com/TeamWin/Team-Win-Recovery-Project/issues/7
?
And for everyone in this thread, this issue has been covered many times in our thread. It's due to compatibilities with the updater-binary and accompanying script. As we have adopted update-binary api 3, and sideload errors are because the rom/zip is trying to issue an api command no longer supported in api3. Get your nice "devs" to update their scripts.
Click to expand...
Click to collapse
Recovery can be a pretty scary place for many folks, For you and I this is our bread and butter, for most it's a rare visit. My goal in everything I've ever developed is to make things easier, friendly and inviting.
One of the many patterns you can use to accomplish this is to use professional and consistent verbiage and provide verbosity where it is appropriate. Usability 101.
I am sorry but "Backup Naowz!" is not clear and certainly not professional. This pro-treys no confidence that the following action is actually going to work.
Regarding the Original Posters message about this error which I also experienced. If this is common and you can trap it through exception handling, why not present a user friendly message to the user?
As I mentioned on IRC, I want this to be a polished product. I really think this can develop into one great recovery but right now it needs a little help. When you're ready to listen, I'm willing to help.
myn said:
Recovery can be a pretty scary place for many folks, For you and I this is our bread and butter, for most it's a rare visit. My goal in everything I've ever developed is to make things easier, friendly and inviting.
One of the many patterns you can use to accomplish this is to use professional and consistent verbiage and provide verbosity where it is appropriate. Usability 101.
I am sorry but "Backup Naowz!" is not clear and certainly not professional.
Regarding the Original Posters message about this error which I also experienced. If this is common and you can trap it through exception handling, why not present a user friendly message to the user?
As I mentioned on IRC, I want this to be a polished product. I really think this can develop into one great recovery but right now it needs a little help. When you're ready to listen, I'm willing to help.
Click to expand...
Click to collapse
First off, who really cares about "Backup Naowz!" being an issue but you? I mean seriously, you're just trolling. So do you go tell people they can't speak improper english because you don't like it? Come on. We do this for free, for fun. If you paid us to make this recovery for you, then sure, if what you want is Backup Now!, we can do that for you. But you are using it for free. At least feel grateful of what we've done as a hobby for everyone instead of nitpicking 10+ issues on the smallest inaccuracies that go against your perfect world. Seriously, I'm sure others might like the "Backup Naowz!". Anyways, if you have any suggestion or comments, feel free to do it in our thread, instead of drawing up 10+ issues that are more like "hey can you add this for me? do this for me? change this for me?" issues.
And now you go and try to make it seem like we don't care about helping our users? Nice try.
Here's the zip that was giving me the sideload errors.
I don't see any issues with the updater-script and the updater-binary is ver 3.
myn said:
Recovery can be a pretty scary place for many folks, For you and I this is our bread and butter, for most it's a rare visit. My goal in everything I've ever developed is to make things easier, friendly and inviting.
One of the many patterns you can use to accomplish this is to use professional and consistent verbiage and provide verbosity where it is appropriate. Usability 101.
I am sorry but "Backup Naowz!" is not clear and certainly not professional. This pro-treys no confidence that the following action is actually going to work.
Regarding the Original Posters message about this error which I also experienced. If this is common and you can trap it through exception handling, why not present a user friendly message to the user?
As I mentioned on IRC, I want this to be a polished product. I really think this can develop into one great recovery but right now it needs a little help. When you're ready to listen, I'm willing to help.
Click to expand...
Click to collapse
i completely agree with polish and consistency portraying professionalism, and we're glad for and always open to suggestions. however, in this case, we purposely used that terminology. we, as teamwin, like to have fun with our projects. some of them are very serious (wimax, hdmwin, kernel manager). others are a bit more on the entertaining side (theninjatweeter, twinpic 3d). with the recovery, we wanted to do something that stood apart from the rest. we do things that reflect our personality as a team.
as for the sideload issues that many are experiencing, we've discussed many times in our threads as well as on twitter and even google+; it is an issue with an outdated updater-binary script. update the scripts, no more sideload errors.
to come out and say we're not willing to listen to suggestions seems a bit presumptuous, even dangerous, when the issues you put on our github were more along the lines of requests.
AssassinsLament said:
...
if you have any suggestion or comments, feel free to do it in our thread, instead of drawing up 10+ issues that are more like "hey can you add this for me? do this for me? change this for me?" issues.
And now you go and try to make it seem like we don't care about helping our users? Nice try.
Click to expand...
Click to collapse
I apparently didn't realize that your thread was the official authoritative record for bug tracking. As your code is on github I thought the issue/request tracking would be a far better medium to track these. Hence why github has this feature Interestingly enough 4 of the 10 features/bugs you implemented in your 1.3 TWRP release were reported by me at your github issue repo so apparently this is quite effective
Don't worry about the number of issues/requests out there or who put them in. I've got over 250+ issues/requests reported on Synergy and the thing went gold yesterday. Filter your issues/requests by priority and address them top down from highest first. Some you'll never get to and that's fine .
Again, all I want to provide is a better experience for my users who I can hopefully promote to use TWRP. Please don't shoot the messenger.
myn said:
I apparently didn't realize that your thread was the official authoritative record for bug tracking. As your code is on github I thought the issue/request tracking would be a far better medium to track these. Hence why github has this feature Interestingly enough 4 of the 10 features/bugs you implemented in your 1.3 TWRP release were reported by me at your github issue repo so apparently this is quite effective
Don't worry about the number of issues/requests out there or who put them in. I've got over 250+ issues/requests reported on Synergy and the thing went gold yesterday. Filter your issues/requests by priority and address them top down from highest first. Some you'll never get to and that's fine .
Again, all I want to provide is a better experience for my users who I can hopefully promote to use TWRP. Please don't shoot the messenger.
Click to expand...
Click to collapse
Again, I don't mind real issues... That's not my point. My point is a lot of your so called bugs or issues are the way we cosmetically chose to do it. Your issues are more so opinions, and wish lists. There is a place for opinions, and a place for real bugs. That's all I am saying.
It would be on the same level as me using your bug/issue space to say "hey i don't like that color.", "hey, can you take off myn from everywhere in your rom, I like it without?" <--- these are NOT issues. These are just what I would like/want. Do you understand?
Anyhow, I am looking into your script. Sadly we do not have any documentation of the differences between api's but, I will try to figure it out. It looks simple enough, so it should work. I'll let you know.
hey everyone. ive been googleing and googleing for weeks and weeks trying to educate myself on how the android build process works and how a device tree works. what i have been able to figure out is the device configuration has been moved form /vendor to /device between eclair and froyo. although i am very lost and confused. i have gone through source.android.com several times, and i have also gone through the very outdated platform developers guide. right now i am trying to teach myself how to set up a build environment for a real device. im doing this purely out of learning experience so i can apply it to something useful in the future. i have several devices at my disposal (epic 4g, droid1, atrix 4g, acer iconia a500) any of which i would be willing to use for learning. does anyone have any recommendations on reading material im missing? any good place to ask stupid questions? there is lots of documentation out there but i just cant seem to find it. where should i go from here? i wish i could just take a class on this. because there is so much information out there i have no idea where to go from here.
I was actually going to make a post along the same lines as yours. From what I have found the pinned post in this forum from cyanogen about cooking is probably the most useful information to get started.
The issue I have is a forum just on this topic alone. It would be nice to have a forum that only discussed merging manufacturers released code into AOSP. By googling I have found the Atrix source code that Motorola has released and also the AOSP itself. By reading cyanogens post and mucking around with the source this should give you a good start.
Good luck and if you come across a forum with just this topic discussed post a link.
Also for setting up an environment this post is good for getting everything setup to compile what you need. It is a post to compile CM7 but it can be used for what you are looking for.
gh123man said:
hey everyone. ive been googleing and googleing for weeks and weeks trying to educate myself on how the android build process works and how a device tree works. what i have been able to figure out is the device configuration has been moved form /vendor to /device between eclair and froyo. although i am very lost and confused. i have gone through source.android.com several times, and i have also gone through the very outdated platform developers guide. right now i am trying to teach myself how to set up a build environment for a real device. im doing this purely out of learning experience so i can apply it to something useful in the future. i have several devices at my disposal (epic 4g, droid1, atrix 4g, acer iconia a500) any of which i would be willing to use for learning. does anyone have any recommendations on reading material im missing? any good place to ask stupid questions? there is lots of documentation out there but i just cant seem to find it. where should i go from here? i wish i could just take a class on this. because there is so much information out there i have no idea where to go from here.
Click to expand...
Click to collapse
2nd hit googling android porting.
http://www.netmite.com/android/mydroid/development/pdk/docs/
Nothing is truly "update-to-date" there are somethings that your going to have to do your homework on. That is a very detailed guide on the basics of getting a port going and working towards the "device tree"
Unless the device tree is from a google nexus phone, then most likely the trees are not perfect. Cyanogenmod for example, the devs that work hard on creating those device trees don't just know what will and won't work. Each phone is different alot of trial and error. Do you build a binary from source, or do you use prop files already on the phone, that is all based on what is trying to be done and how much you know. Eventually you figure it out. It hard to just say what creates the device tree. Its just like someone asking for tips on how to write Java.
Bottom line, just do it and have fun.
lithid-cm said:
2nd hit googling android porting.
http://www.netmite.com/android/mydroid/development/pdk/docs/
Nothing is truly "update-to-date" there are somethings that your going to have to do your homework on. That is a very detailed guide on the basics of getting a port going and working towards the "device tree"
Unless the device tree is from a google nexus phone, then most likely the trees are not perfect. Cyanogenmod for example, the devs that work hard on creating those device trees don't just know what will and won't work. Each phone is different alot of trial and error. Do you build a binary from source, or do you use prop files already on the phone, that is all based on what is trying to be done and how much you know. Eventually you figure it out. It hard to just say what creates the device tree. Its just like someone asking for tips on how to write Java.
Bottom line, just do it and have fun.
Click to expand...
Click to collapse
thanks for the response. maybe im just searching for the wrong things... that and its not sinking in to my thick skull lol.. ill keep reading. im just trying to learn how it all works. some of the things i read either dont make sense or are really vague. i am currently cramming java into my head for app development. i suppose thats a good place to start. my end goal is to contribute.
gh123man said:
hey everyone. ive been googleing and googleing for weeks and weeks trying to educate myself on how the android build process works and how a device tree works. what i have been able to figure out is the device configuration has been moved form /vendor to /device between eclair and froyo.
Click to expand...
Click to collapse
I am trying to figure out how to build/port ROMs too. It has been a nightmare trying to study that. Not enough material, or the material is incomplete. Most of the tutorials are meant to be done with nexus devices wich has a native suport from android. No such a help for someone who is seeking a way to build for a new, unusual device (like me).
I didn't get this "three" thing. And, In my case, it is a little bit weirder because I am trying to build for a MTK6577 processor. (Some may say I am screwed).
although i am very lost and confused. i have gone through source.android.com several times, and i have also gone through the very outdated platform developers guide.
Click to expand...
Click to collapse
Many years ago I said: there will be a Time when people will know the "internet junkyard" or the "virtual online trash can".
I was reffering to outdated information. This information is available now and is not completely reliable because it is old and no one got rid of it.
It is something that is new (although the information is old, the event is pretty new) and we must learn how to deal with it. Unfortunally.
To de development point of view, I've been facing an incredible hard time just to find new information about building a custom rom from the source or porting an existent one.
I know i didn't help at all, but, I felt I must say that.
Anyway, knowing about anything, let me know.
Best regards!
gh123man said:
hey everyone. ive been googleing and googleing for weeks and weeks trying to educate myself on how the android build process works and how a device tree works. what i have been able to figure out is the device configuration has been moved form /vendor to /device between eclair and froyo. although i am very lost and confused. i have gone through source.android.com several times, and i have also gone through the very outdated platform developers guide. right now i am trying to teach myself how to set up a build environment for a real device. im doing this purely out of learning experience so i can apply it to something useful in the future. i have several devices at my disposal (epic 4g, droid1, atrix 4g, acer iconia a500) any of which i would be willing to use for learning. does anyone have any recommendations on reading material im missing? any good place to ask stupid questions? there is lots of documentation out there but i just cant seem to find it. where should i go from here? i wish i could just take a class on this. because there is so much information out there i have no idea where to go from here.
Click to expand...
Click to collapse
Here is the Small Guide Made to Begin from scratch for Android Device Tree Building
Wear 24 DevelopmentContributors: @JaredTamana, @davwheat
Current Status: ActiveCurrent Kernel Status: Building, NFC driver working but still potentially WIPSystem ROM Status: Still WIP. Current task: collecting/compiling files, modifying .jarsTHIS ROM IS NOT YET AVAILABLE TO DOWNLOAD AS AN END-USER ROM
This project has a few goals:
- Bringing NFC/Google Pay support to Wear24 [Feasible, main goal]
- Bringing system updates to the Wear24, ie System H [Probably doable, second goal]
- Adding/fixing functionality in the Wear24 (such as new radio bands, no cloud icon, etc) [Maybe possible but needs more research, low on the list)
- Other projects are being considered for the Wear24, but no news on them at this time.
Links
Social
Wear24Dev Blog, periodic updates on this project: http://wear24dev.blogspot.com
Wear24 NFC Discord, open chat so users can see us develop in real-time! Also, tech support. https://discord.gg/8XyTeUC
Development
Wear24-NFC-Kernel GitHub, this is our source for building the kernel. Instructions for building it yourself are in the README. https://github.com/davwheat/Wear24-NFC-Kernel
Travis-CI Build Logs for Kernel: https://travis-ci.org/davwheat/Wear24-NFC-Kernel
Wear24-NFC-ROM GitHub, will soon contain the files needed to make an image/zip, depending on how we decide to distribute. https://github.com/davwheat/Wear24-NFC-ROM
JaredTamana's GDrive dorado folder, may contain files you need: https://drive.google.com/drive/folders/1h6gz-oLMPZ90nwt7BLhWVgHii1DRCW5c
davwheat's GDrive dorado folder, may contain files you need: https://drive.google.com/drive/fold...droid-msm-dorado-3.18-nougat-mr1-wear-release
tetra release for enabling NFC: https://forum.xda-developers.com/sm...ony-smartwatch-3-nfc-support-package-t3219713
NXP Setup Guidelines: https://github.com/NXPNFCProject/NF...r/AN11762-Android_NXP_NFC_Setup_Guideline.pdf
Special Thanks
janjan: Dev guidance
@bensdeals: Donor, help
@yochanmarquos, u/lerxi: Development help.
-- RESERVED -- Because you never know
Someone should have a TWRP backup handy with the images you are looking for. Correct me if I'm wrong, but all the images you require are inside a TWRP backup image.
Anyone remember that Sony SW3 port thread? I'm not sure what happened to the project, but dev seems quiet and the device tree repos are gone. Was hoping to use those as a resource and it wasn't crawled by archive.org. Wonder if external forces got involved, which makes me a bit worried. If anyone has a clone of that repo, it might be really useful.
Please. I beg you to make this happen. Thanks for even trying
I'm definitely interested in this. If I knew I could get Google Pay working on this device, I would definitely buy one. I'll happily throw a few dollars your way too, if you can release something that works.
Hoping I found it
JaredTamana said:
Anyone remember that Sony SW3 port thread? I'm not sure what happened to the project, but dev seems quiet and the device tree repos are gone. Was hoping to use those as a resource and it wasn't crawled by archive.org. Wonder if external forces got involved, which makes me a bit worried. If anyone has a clone of that repo, it might be really useful.
Click to expand...
Click to collapse
Is this what you're looking for? (Sorry, I'm not allowed to post url yet so just remove space before .com)
github .com/FlorentRevest/android_device_sony_tetra
My Wear24 just came in from eBay . It's a really good looking device. I might be able to help you test at some stage. Also willing to donate ducats if you get far enough. Good Luck :good:
I got my wear24 a few months ago, and was slightly disappointed to find out about the lack of root, customization, etc. I'm still not a huge fan of opening it up, but I'm up for helping any other way I can!
YTSec said:
I got my wear24 a few months ago, and was slightly disappointed to find out about the lack of root, customization, etc. I'm still not a huge fan of opening it up, but I'm up for helping any other way I can!
Click to expand...
Click to collapse
I appreciate the thought, but doing anything in the vein of system modification will require opening the watch. Luckily, the pinout is right under the back cover, so chances of damaging the watch are minimal. If you change your mind, let me know.
** NEWS **
Semi-daily updates will be going on this Blogger Page so I don't clog up the thread
http://wear24dev.blogspot.com
Hi, can i flash this rom to zte quartz 2017?
Hi, can i flash this rom to zte quartz 2017?
Eshal said:
Hi, can i flash this rom to zte quartz 2017?
Click to expand...
Click to collapse
Eshal, this ROM hasn't even been built yet. I cannot guarantee compatibility with your device because I'm not building for your device. You can try flashing whatever you like, but I'm not liable for your device.
This ROM is still in its first steps and I quite literally have nothing to release yet. I've just finished bringing backups over to my PC.
JaredTamana said:
I appreciate the thought, but doing anything in the vein of system modification will require opening the watch. Luckily, the pinout is right under the back cover, so chances of damaging the watch are minimal. If you change your mind, let me know.
Click to expand...
Click to collapse
I took a look, it's not as bad as I thought. Its probably worth unlocking the bootloader anyway! I'll let you know tomorrow if I do.
YTSec said:
I took a look, it's not as bad as I thought. Its probably worth unlocking the bootloader anyway! I'll let you know tomorrow if I do.
Click to expand...
Click to collapse
Glad to hear it! Make sure to read the main thread as to tips on how to do it. Use lots of heat, and don't forget the Y000 (0.6) screwdriver.
Kernel builds are now passing, and I've begun debugging the boot process. More info on the Blogspot
Sorry for the late reply, I'm just waiting on a toolkit that works on it, then I'll start ripping it apart to help out! Also, I got that new UI which is great.
How goes the testing? I've noticed that there haven't been any new posts on the blog or on this thread. Hope everything is well
@JaredTamana Have you seen this? BLOCKS announces Project OpenWatch: an Android Oreo-based OS for smartwatches in collaboration with CarbonROM and LineageOS
Here's their GitHub.
VlitalityX said:
How goes the testing? I've noticed that there haven't been any new posts on the blog or on this thread. Hope everything is well
Click to expand...
Click to collapse
Hiya! Sorry for the lack of updates. I've hit a wall with that Binder error. All documentation online seems to be about x86 machines and ranges from IO errors to SELinux errors. I've already tried compiling without SELinux in a few different ways to no avail. I've tried contacting development channels on IRC, but no one seems to have the answers I need (most times I don't even get a reply...)
I'm still brainstorming. I took a look at the kmsg from the stock build and there's a LOT being sent to logs there that isn't from my kernel. I'm not sure where to go next, and I don't want to go knocking on the door of every single developer that might know the answer. The problem is the Binder errors are so vague about what's causing the failed transaction that I can't even start to understand what's wrong.
yochananmarqos said:
@JaredTamana Have you seen this? BLOCKS announces Project OpenWatch: an Android Oreo-based OS for smartwatches in collaboration with CarbonROM and LineageOS
Here's their GitHub.
Click to expand...
Click to collapse
Thanks! I do remember seeing this. Problem is, if I can't even build a stock kernel, nothing else can be done. I need the device booting first before I can move to system changes.