Okay, so I've been trying to port firefox os to the galaxy tab and have run into a problem. Take a look:
Code:
$ ./config.sh galaxy-tab-10.1
gpg: keyring `/home/kobalt/.repoconfig/gnupg/secring.gpg' created
gpg: keyring `/home/kobalt/.repoconfig/gnupg/pubring.gpg' created
gpg: /home/kobalt/.repoconfig/gnupg/trustdb.gpg: trustdb created
gpg: key 920F5C65: public key "Repo Maintainer <[email protected]>" imported
gpg: key 338871A4: public key "Conley Owens <[email protected]>" imported
gpg: Total number processed: 2
gpg: imported: 2 (RSA: 1)
Get https://gerrit.googlesource.com/git-repo/clone.bundle
Get git://github.com/mozilla-b2g/b2g-manifest
remote: Counting objects: 237, done.
remote: Compressing objects: 100% (139/139), done.
remote: Total 237 (delta 145), reused 166 (delta 80)
Receiving objects: 100% (237/237), 30.29 KiB, done.
Resolving deltas: 100% (145/145), done.
From git://github.com/mozilla-b2g/b2g-manifest
* [new branch] master -> origin/master
* [new branch] nightly -> origin/nightly
fatal: manifest 'galaxy-tab-10.1.xml' not available
fatal: manifest galaxy-tab-10.1.xml not found
Repo sync failed
I think this occurring because it is trying to find "galaxy-tab-10.1" in git://github.com/mozilla-b2g/b2g-manifest when there is no such file or directory with that name in the repository. Any help or thoughts on this would be greatly appreciated, and if this port is successful, I will make sure to post back the results.
I know this isn't helping..but I was wondering, isn't firefox os only for phones?
I didn't know that there was a tablet version..
Please let me know..
Either way, hope it progresses well!
Just saw a tweet from XDA they added a Firefox OS section, might be able to find your answer there
sw6lee said:
I know this isn't helping..but I was wondering, isn't firefox os only for phones?
I didn't know that there was a tablet version..
Please let me know..
Either way, hope it progresses well!
Click to expand...
Click to collapse
Well, I haven't really heard a lot about people using it on their tablets... but worst case scenario, I'll just have to adjust the dpi or a few minor things.
There is no reason I can think of why this wouldn't work.
nakedninja42 said:
Just saw a tweet from XDA they added a Firefox OS section, might be able to find your answer there
Click to expand...
Click to collapse
I posted a thread over there a little bit ago. Hopefully I'll hear back soon; I really want to find out what went wrong so I can get back to building this thing. :fingers-crossed:
Kobalt.Kitsune said:
Well, I haven't really heard a lot about people using it on their tablets... but worst case scenario, I'll just have to adjust the dpi or a few minor things.
There is no reason I can think of why this wouldn't work.
I posted a thread over there a little bit ago. Hopefully I'll hear back soon; I really want to find out what went wrong so I can get back to building this thing. :fingers-crossed:
Click to expand...
Click to collapse
I wish I could contribute more to help out, it would be cool to see Firefox and Ubuntu ported. Best of luck!
Well I figured it out... It was indeed a problem with my manifest.xml file. Anyway, I'm glad I decided to spend the week building this. I've already learned so much about how to use git, c++, and a bunch of other invaluable skills from this little project.
Getting back on topic, this first build (if it works) will only be for us gt-p7510 users. After that, I will start work on the other galaxy tab models.
Cross your fingers. :fingers-crossed:
That's great news! Can't wait to check it out. :victory:
Great initiative, very curious how far you will get with this!
Awesome, if you need testers I will sign myself up for testing as my tab isnt doing anything at the moment.
I too would be happy to test for us. :thumbup:
Sent from my SGH-I747 using xda premium
Hi, this is interesting work, I'll be your next tester if you like... :good:
Also take a look at ReactOS project that has been developed for both ARM and x86, I'm struggling to run it on my tab(P7500)...
It has never been a problem to run P7510 ROMs on P7500, so don't be afraid to test all the things you get for the TABs
Thanks again for trying to bring new life(new OS I mean) in the SGT forums...
Related
So am i the only one here that notices that there hasn't been an update for a ROM in about a month? What's been going on?
Not really. IHO is still alive and well. Some of the froyo roms are at end of life and are considered more or less finished (Harmonia and Bumblebee to name a couple).
Sent from my LG-VM670 using Tapatalk
I don't think it helped that the kernel site was hacked and has been down...?
We are all waiting for kernel.org to be back up, kinda hard to build without source.
Some hackers must sit around and think "Who can I piss off today? I know, most of the android dev community." Some hackers just suck.
Sent from my VM670 using XDA App
This explains a lot.. I've been waiting for an update on IHO for a while
Sent from my LG-VM670 using xda premium
Thanks for the information I had no idea kernel.org got hacked.
Sent from my LG-VM670 using Tapatalk
It is hard waiting for kernel.org to get back up, but I'm more than willing to wait it out patiently. We are talking about the basis to the entire Linux community here, not just Android. While we are pretty sure the hackers couldn't have gotten anything in that wouldn't be noticed due to the inherent nature of the repository system, it is prudent that they do such dilligent work checking everything out to be certain. Imagine if someone was able to insert malicious code at the basis of the kernel's distribution system, botnets that instantly compromise millions of computers, all user data compromised the moment you update your system, the imaginary horror stories are all too real possibilities.
Go outside, fix that garage door, paint that fence, or at least take down last year's xmas lights. Kernel.org will be back up soon enough, and we can all go back to worrying about which color looks best on our phones buttons.
@JerryScript:
I'm guessing you didn't get the codaurora repo patched into your cm7 build system like you mentioned you were going to try?
I bet it's murder to patch CAF source addresses into the repo manifest instead of kernel.org, huh?
bummer.
that blog link you posted over in the build-your-own-rom thread on AC worked great for codeaurora by itself, which I appreciate greatly since I was already working with that before kernel.org bit the big one. then I couldn't sync it for a while until you pointed me the way.
bigsupersquid said:
@JerryScript:
I'm guessing you didn't get the codaurora repo patched into your cm7 build system like you mentioned you were going to try?
I bet it's murder to patch CAF source addresses into the repo manifest instead of kernel.org, huh?
bummer.
that blog link you posted over in the build-your-own-rom thread on AC worked great for codeaurora by itself, which I appreciate greatly since I was already working with that before kernel.org bit the big one. then I couldn't sync it for a while until you pointed me the way.
Click to expand...
Click to collapse
Blarf told me that CAF was to much of a mess to rely on. I'm currently syncing using TI's omapzoom, will let you know if I get a successful build environment setup.
Edit-- There is an easier way than manually patching the mirror, just use the following:
Code:
$ repo init -u git://github.com/inferiorhumanorgans/android.git -b gingerbread --repo-url=git://git.omapzoom.org/tools/repo.git
Notice the --repo-url appended to the normal init line, that will do all the patch magic for you. All you have to do is change the remote.
Big thanks to Sanghee Kim for posting this:
https://groups.google.com/forum/#!topic/repo-discuss/r0wkGaloA5k
@jerryscript I would highly suggest making your own thread with the above information just to make sure all of the devs see. Might help them out a little
Sent from my LG-VM670 using Tapatalk
gannon5197 said:
@jerryscript I would highly suggest making your own thread with the above information just to make sure all of the devs see. Might help them out a little
Sent from my LG-VM670 using Tapatalk
Click to expand...
Click to collapse
I plan on it, as soon as I finish a successful compile.
Sorry I hijacked your thread, to answer your op, should have some new builds soon.
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
So, after about 4 hours of downloading virtualbox, installing Ubuntu onto it, and getting to the point of downloading most of the CM source code, my VM ran out of disk space, and I gave up on attempting to compile a custom version of 10.1 to test out a patch.
So, I humbly ask: if anyone has the capability to compile i717 builds of CM 10.1, can they could do so and incorporate this gerrit patch into an otherwise untouched m2 build, and throw it up on dropbox for me to test?
The issue this patch is attempting to fix is detailed in this bug report I filled here, but in short, images captured in the mms application using the "capture picture" option rotates the preview image in a way that makes the user think the image will be sent incorrectly, when in fact it will send correctly.
I'd love to get this issue solved, and you would have my many thanks for compiling it.
You'll need at least 35G free after the OS is installed for code, compiled bins, etc... that's overestimating, but anything less than 25G would not be good.
I used to build CM9 a while back, but haven't kept up.
You might try sending a couple of the DEVs a PM about this. I'm not positive but they are always checking on their threads and may not even see this. Most all of the DEVs we have are pretty helpful.
khaytsus said:
You'll need at least 35G free after the OS is installed for code, compiled bins, etc... that's overestimating, but anything less than 25G would not be good.
I used to build CM9 a while back, but haven't kept up.
Click to expand...
Click to collapse
Oh man, I feel stupid now, I thought that there would be no way it took more than 15 gigs to install linux and compile something that would end up only being around 100 mb. :/
jagpoag said:
You might try sending a couple of the DEVs a PM about this. I'm not positive but they are always checking on their threads and may not even see this. Most all of the DEVs we have are pretty helpful.
Click to expand...
Click to collapse
I will perhaps try this.
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
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.