Lineage 14.1 - Lux - Nightly - X Play Q&A, Help & Troubleshooting

Hello,
I am firing up a server which will pull lineage repo every 24 hours and generate nightly for all of us till lineage can do it on their own.
But I am stuck at a couple of places.
1: As this is a cloud, I have no idea how to extract blob files to it.
2: When I was doing Samsung s3 development, I remember I add to add one more repo and never required blob files, am I missing something for lux?
3: How can i make sure I pull all latest Lineage code changes for lux?
Any support will be appreciated.
I just hope i dont end up spending hundreds of dollars for nothing.

Everything done.
Waiting for blob.

Xtreme666 said:
Everything done.
Waiting for blob.
Click to expand...
Click to collapse
placeholder threads are not allowed. :good:

methuselah said:
placeholder threads are not allowed. :good:
Click to expand...
Click to collapse
What is a `placeholder thread`?
You mean to say, "reply to thread not allowed, use edit instead?"

EDIT: Moderator did the magic. Thankyou.

Related

New Eris Vendor Tree

Ok, folks... Some very industrious devs have worked out a more complete vendor tree for the Eris at http://github.com/punk-kaos/vendor_htc_desirec. I've synced it into -
$AOSPsource/froyo/vendor/htc/desirec <-- this is the level that all of the files are at (i.e. everything under vendor_htc_desirec/ from the repo)
I'm a little lost as to where to go from there. I've looked at multiple vendor trees, and everyone seems to do things a little differently each time.
Can any of you point me in the right direction?
Thanks!
Kudos to Kaos, jamezelle, conap, vinylfreak89, & darchstar! You really rock.
Ok, so I copied it all under
$AOSPsource/froyo/device/htc/
Since that's where the dream, passion, etc. stuff is.
Now, I do a - 'source build/envsetup.sh' and it seems to find the desirec stuff.
including device/htc/desirec/vendorsetup.sh
including device/htc/dream/vendorsetup.sh
including device/htc/passion/vendorsetup.sh
including device/htc/sapphire/vendorsetup.sh​
I'm stuck at what to do a 'lunch' on now. In the vendorsetup.sh, there's a 'cyanogen_desirec-eng'.
When I 'lunch cyanogen_desirec-eng', I get -
build/core/product_config.mk:190: *** _nic.PRODUCTS.[[device/htc/desirec/froyo_desirec.mk]]: "vendor/htc/desirec/device_desirec-vendor-blobs.mk" does not exist. Stop.
** Don't have a product spec for: 'cyanogen_desirec'
** Do you have the right repo manifest?​
Getting closer!
Applause
I read you posts and see the questions you ask(that never seemed to get answered)and you will post some stuff you have learned all to help someone else who might want to get started dinking around with a pretty cool open source operating system. I applaud you for asking questions and when no one replies you answer it again yourself. You are the true definition of open source!
Im fairly new to this whole scene so excuse the "dumb" question but what exactly is a vendor tree?
You are stellar. I am going to try and port a froyo rom and then start to build something from the ground up. The questions you ask and the information you provide is invaluable. Want to put a rom project together?
Sent from my FroyoEris
good progress
paperweight said:
I read you posts and see the questions you ask(that never seemed to get answered)and you will post some stuff you have learned all to help someone else who might want to get started dinking around with a pretty cool open source operating system. I applaud you for asking questions and when no one replies you answer it again yourself. You are the true definition of open source!
Click to expand...
Click to collapse
Thank you. Many devs have helped me to learn all that I have learned. They are busy people just like most of us. Some of them probably don't pay attention to the forum that often. Some just have their own projects. Some hang out in IRC instead of looking in here. Actually, I've learned a lot in IRC, even when I just kick back and lurk. I really do want to get all of the info that I learn out here in the forum where 'noobs' are lurking. I've found that there is a certain level of detail that is available fairly easily with the search box. There's a point where it takes some real digging to figure things out. My hope is that it won't always be that way.
I tried manually taking all of the files and settings from the vendor tree and inserting them into SgtShultz. It didn't fix things. So, I'm thinking that either it really does have to be compiled in or this tree and AOSP Froyo don't quite mesh. Since there is some source code in the tree, that is most likely the issue.
I never could get the lunch command to work. That file is not there, and I'm still not sure what it should contain if I were to create it. Getting this to work would really help both of my other current projects...
MacShannon said:
Im fairly new to this whole scene so excuse the "dumb" question but what exactly is a vendor tree?
Click to expand...
Click to collapse
When you compile AOSP and/or variants from source, there is generally no device specific code - like drivers for instance. The vendor tree just sets everything up to add those proprietary files and settings into the mix, so that the resulting ROM will actually be usable. That's the idea anyway!
thanks for all the work you've been doing recently! i've followed the other thread as well... and am happy to say that i use (and appreciate) your work!
gnarlyc said:
When you compile AOSP and/or variants from source, there is generally no device specific code - like drivers for instance. The vendor tree just sets everything up to add those proprietary files and settings into the mix, so that the resulting ROM will actually be usable. That's the idea anyway!
Click to expand...
Click to collapse
I also have a "dumb" question.
If this is for the Eris, then why are the files under the "desire" name? I thought the eris was based on the hero platform or am I missing something obvious here?
gnarlyc said:
I'm a little lost as to where to go from there. I've looked at multiple vendor trees, and everyone seems to do things a little differently each time.
Can any of you point me in the right direction?
Click to expand...
Click to collapse
Have you tried the steps from this thread?
I am currently working through them, but had to stop because it's time for me to get ready for work.
I have gotten through the step where you copy the vendor files to the htc folder
sbarne3 said:
I also have a "dumb" question.
If this is for the Eris, then why are the files under the "desire" name? I thought the eris was based on the hero platform or am I missing something obvious here?
Click to expand...
Click to collapse
Great question! HTC's 'internal' name for the Eris is 'desirec' apparently. (Note that it's 'desirec' not 'desire'.) It was somewhat confusing when they came out with the Desire...
sbarne3 said:
Have you tried the steps from this thread?
I am currently working through them, but had to stop because it's time for me to get ready for work.
I have gotten through the step where you copy the vendor files to the htc folder
Click to expand...
Click to collapse
Looking at it now. Thanks!
gnarlyc said:
Ok, so I copied it all under
$AOSPsource/froyo/device/htc/
Since that's where the dream, passion, etc. stuff is.
Now, I do a - 'source build/envsetup.sh' and it seems to find the desirec stuff.
including device/htc/desirec/vendorsetup.sh
including device/htc/dream/vendorsetup.sh
including device/htc/passion/vendorsetup.sh
including device/htc/sapphire/vendorsetup.sh​
I'm stuck at what to do a 'lunch' on now. In the vendorsetup.sh, there's a 'cyanogen_desirec-eng'.
When I 'lunch cyanogen_desirec-eng', I get -
build/core/product_config.mk:190: *** _nic.PRODUCTS.[[device/htc/desirec/froyo_desirec.mk]]: "vendor/htc/desirec/device_desirec-vendor-blobs.mk" does not exist. Stop.
** Don't have a product spec for: 'cyanogen_desirec'
** Do you have the right repo manifest?​
Getting closer!
Click to expand...
Click to collapse
Did you run extract-files.sh? Iirc, the vendor_blob file is created when you run it.
Sent from my FroyoEris using XDA App
Resun said:
Did you run extract-files.sh? Iirc, the vendor_blob file is created when you run it.
Sent from my FroyoEris using XDA App
Click to expand...
Click to collapse
Holy cow! I did not run it because I already have all of those files in place. It didn't occur to me to check and see if 'extract-files.sh' does something more than just pull the files.
Thank you.
Np, been working on my own, I've done the same thing about 10 times in the past week.
Sent from my Froyo Eris using XDA App
So, I commented out all of the 'adb pull' statements in the 'extract-files.sh' script, since the files are already there. Now I see that extract-files was creating the ...blobs.mk file under vendor/htc/desirec instead of device/htc/desirec. So, I changed that and ran it all again...
cd $AOSPsource/froyo
device/htc/desirec/extract-files.sh
source build/envsetup.sh
lunch cyanogen_desirec-eng
And this gives me -
build/core/product_config.mk:192: *** vendor/htc/desirec/froyo_desirec.mk: PRODUCT_NAME must be unique; "desirec" already used by device/htc/desirec/froyo_desirec.mk vendor/htc/desirec/froyo_desirec.mk . Stop.
** Don't have a product spec for: 'cyanogen_desirec'
** Do you have the right repo manifest?​
Here I go again! Thanks for all of the help. I really want to get this working, so that it can be scripted.
gnarlyc said:
So, I commented out all of the 'adb pull' statements in the 'extract-files.sh' script, since the files are already there. Now I see that extract-files was creating the ...blobs.mk file under vendor/htc/desirec instead of device/htc/desirec. So, I changed that and ran it all again...
cd $AOSPsource/froyo
device/htc/desirec/extract-files.sh
source build/envsetup.sh
lunch cyanogen_desirec-eng
And this gives me -
build/core/product_config.mk:192: *** vendor/htc/desirec/froyo_desirec.mk: PRODUCT_NAME must be unique; "desirec" already used by device/htc/desirec/froyo_desirec.mk vendor/htc/desirec/froyo_desirec.mk . Stop.
** Don't have a product spec for: 'cyanogen_desirec'
** Do you have the right repo manifest?​
Here I go again! Thanks for all of the help. I really want to get this working, so that it can be scripted.
Click to expand...
Click to collapse
Shouldn't have it in both, should only be in the device subfolder.
Resun said:
Shouldn't have it in both, should only be in the device subfolder.
Click to expand...
Click to collapse
Thanks again! I know better than to do a drive by like that. I spent two minutes testing, posted the results, and then left to run errands for most of the day.
I'll try again when i get home.
so ive patched up the vendor on my computer (some files were pointing to devices/htc/desirec) and when i finally got it to behave i ran into something worse..
Code:
build/core/combo/TARGET_linux-arm.mk:39: *** Unknown ARM architecture version: armv6. Stop.
i ended up changing the lunch to desirec-eng because it wouldnt resolve the product name... im not a dev but i sure have a nose for this sort of thing, and help or an armv6.mk file would be appreciated

Android 4.2 For Nexus S

More then one thread is making me dizzy
Please refer to the development thread for new rom releases and comments:
http://forum.xda-developers.com/showthread.php?t=1992411
Going to maintain this Rom from there
IAmTheDarkOne said:
I'm new as a posted to XDA but I'v ebeen making kernels for the Nexus S for a good while now. I've managed to take the GIT of android 4.2 and get to to compile with the crespo source from the cyanogenmod jellybean GIT repo with some minor modifications.
I currently have a GT9020A (fido canada network) and I'm currently running android 4.2 on it with my custom kernel.
Kernel Changes
-Overclocking enabled to 1.3 ghz as that's the highest I could get my phone to go stable
-added VR i/o scheduler as default
-added smartassv2 as default governor
-removed fsync for performance (francisco kernel)
I upgraded this os from a stock android 4.1.2 firmware all I needed to do is wipe cache no factor reset
I don't currently have a working installation of APPS and the image is not rooted. Like I said I'm new to this.
Since I haven't posted on the forums before I can't post a link to the firmware I made. Can anyone help me with this?
Click to expand...
Click to collapse
I'm more than willing to try and test your work. What kind of help do you need?
You can upload files here: http://goo.im/
ej8989 said:
I'm more than willing to try and test your work. What kind of help do you need?
You can upload files here:
Click to expand...
Click to collapse
I guess the issue is that I haven't currently made 10 posts on xda-developers therefore I'm not allowed to post external links guess I'll have to be patient and post regularly so I can actually get the links out there.
Contact the user darkargon here on xda. Or on irc.freenode.net #andromirror. He hosts builds/roms for free and with great support.
Can we PM? I want to build for sgs1 i9000 which should be similar to your device.
I have fully synced android-4.2_rc1 and cyanogenmod jellybean git repo as you did but now I'm stuck.
droidjam said:
Contact the user darkargon here on xda. Or on irc.freenode.net #andromirror. He hosts builds/roms for free and with great support.
Can we PM? I want to build for sgs1 i9000 which should be similar to your device.
I have fully synced android-4.2_rc1 and cyanogenmod jellybean git repo as you did but now I'm stuck.
Click to expand...
Click to collapse
Yeah sure we can PM. Like I said I'm new to this but I'll try to help the best I can
It's not that hard to find 10 useful things to post..
I don't think the problem is hosting, as others have seemed to assume. I think he can't post the link without having 10 posts
I would to try that ROM as well. It easy to see 10 posts.
Sent from my Nexus S using Tapatalk
Kitch16 said:
I don't think the problem is hosting, as others have seemed to assume. I think he can't post the link without having 10 posts
Click to expand...
Click to collapse
Yep.
IAmTheDarkOne said:
I guess the issue is that I haven't currently made 10 posts on xda-developers therefore I'm not allowed to post external links guess I'll have to be patient and post regularly so I can actually get the links out there.
Click to expand...
Click to collapse
IAmTheDarkOne said:
I guess the issue is that I haven't currently made 10 posts on xda-developers therefore I'm not allowed to post external links guess I'll have to be patient and post regularly so I can actually get the links out there.
Click to expand...
Click to collapse
Just post it with spaces in between the letters, that way xda won't pick it up as a link.
like this:
www. google .com
SuBethi Isthmian
navjot94 said:
Just post it with spaces in between the letters, that way xda won't pick it up as a link.
like this:
spaces used to be here
Click to expand...
Click to collapse
Trying with spaces I can't even replay to your comment with the quote in it with spaces
IAmTheDarkOne said:
Trying with spaces I can't even replay to your comment with the quote in it with spaces
Click to expand...
Click to collapse
Well, PM someone the link and then they reply with the link in a post, then you can edit the OP with that post as a quote
ok. I ask you on your thread so you can get more posts.
how did you "lunch (crespo-userdebug)"?
I don't have such an option, there are just full-eng full_manta-userdebug full_tilapia-userdebug full_x86-eng mini_mips-userdebug full_grouper-userdebug full_mips-eng full_toroplus-userdebug mini_armv7a_neon-userdebug mini_x86-userdebug full_maguro-userdebug full_panda-userdebug full_toro-userdebug mini_armv7a-userdebug vbox_x86-eng
where do I have to put the necessary files or which I have to edit to get a galaxysmtd-userdebug?
thanks!
give me the link per PM I'll post it here for you, if you want
it's not difficult to read his link..downloading right now
.....
booting now
droidjam said:
ok. I ask you on your thread so you can get more posts.
how did you "lunch (crespo-userdebug)"?
I don't have such an option, there are just full-eng full_manta-userdebug full_tilapia-userdebug full_x86-eng mini_mips-userdebug full_grouper-userdebug full_mips-eng full_toroplus-userdebug mini_armv7a_neon-userdebug mini_x86-userdebug full_maguro-userdebug full_panda-userdebug full_toro-userdebug mini_armv7a-userdebug vbox_x86-eng
where do I have to put the necessary files or which I have to edit to get a galaxysmtd-userdebug?
thanks!
give me the link per PM I'll post it here for you, if you want
Click to expand...
Click to collapse
the option doesn't exist in the 4.2 stock source because google isn't making one for the crespo. I added crespo to the source from CM10
you can add it by extracting this file to the root of your 4.2 source
dubdubdubdotfreefilehostingdotnetslashdevicesourcetar
fanguru said:
it's not difficult to read his link..downloading right now
.....
booting now
Click to expand...
Click to collapse
Please report how it works. Whats broken etc.
Interested to know how this works.
ubnub82 said:
Interested to know how this works.
Click to expand...
Click to collapse
+1
the link pls ...i cant understand from the post ...
what is working and not working list ...
how to flash ...
leap_ahead said:
+1
the link pls ...i cant understand from the post ...
What is working and not working list ...
How to flash ...
Click to expand...
Click to collapse
+2 link please!!
http://www.freefilehosting.net/fullcrespo-ota-engdark

[ROM] [Unofficial] [4.4.2] PAC-man ROM - All in One - PA/CM/AOKP

I have all the repos downloaded to do this, and I'm going to build it asap, any testers?
pro_granade said:
I have all the repos downloaded to do this, and I'm going to build it asap, any testers?
Click to expand...
Click to collapse
Yes please
Yay
Alrighty, first build that comes out, I will send to you. Have you ever done this before?
pro_granade said:
I have all the repos downloaded to do this, and I'm going to build it asap, any testers?
Click to expand...
Click to collapse
im down to test this. Ive tested MANY beta roms on my OG Evo 4G, S2, S3, Bionic, Rezound, Incredible 1 and 2 (you get the idea)
lemme know if you need any other testers
I'm down to test. Hit me up
Sent from my SM-G900P using XDA Free mobile app
I would be careful creating threads before something is built and booting, there's more than just downloading repos to getting a working build.
Just sayin.
If you need help with anything hit me up, working through various builds as well
I'll also test.
Id try it
I'd test it for you as well. :good: :good:
Hey PM me
sleshepic said:
I would be careful creating threads before something is built and booting, there's more than just downloading repos to getting a working build.
Just sayin.
If you need help with anything hit me up, working through various builds as well
Click to expand...
Click to collapse
Hey, xD, I need some help. I'm getting some errors with ./build-pac.sh and I need chur help.
I'm in as well. Working on some builds myself but no success yet. :good:
pro_granade said:
Hey, xD, I need some help. I'm getting some errors with ./build-pac.sh and I need chur help.
Click to expand...
Click to collapse
Best thing might be having this moved to general until a build is out. Then we could troubleshoot/go over build errors on record for the benefit of all. I was going to just put out the PAC builds, but we could do it together (in general) as it tends to be one of the easier ones to start with.
It building now it's just kernel issues. And alrighty I'm sorry for that >. <
Sent from my SM-G900P using XDA Premium 4 mobile app
Mod?
Could we get this thread moved to General?
pro_granade said:
I have all the repos downloaded to do this, and I'm going to build it asap, any testers?
Click to expand...
Click to collapse
hell yeah, count me in!!
pro_granade said:
It building now it's just kernel issues. And alrighty I'm sorry for that >. <
Sent from my SM-G900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Post that error again, and your roomservice.xml(can use Pastebin for that). I dont believe your kernel source is where it is supposed to be. Look in /kernel/samsung, is there anything in there?
:/
sleshepic said:
Post that error again, and your roomservice.xml(can use Pastebin for that). I dont believe your kernel source is where it is supposed to be. Look in /kernel/samsung, is there anything in there?
Click to expand...
Click to collapse
No there isn't but I looked in the BoardConfig.mk and changed the location to where I had the kernel. Now it's complaining about the obj idek what that is.
pro_granade said:
No there isn't but I looked in the BoardConfig.mk and changed the location to where I had the kernel. Now it's complaining about the obj idek what that is.
Click to expand...
Click to collapse
You dont want to change the boardconfig. You're gonna want the klte kernel folder in there where its supposed to be
Post your roomservice.xml from .repo/local_manifests. You prob just need to sync a klte kernel repo to your tree
Aside from a few build errors(overlay/base package stuff) you should be able to essentially sync and build once your roomservice is figured out. It's not yet a supported device so its not gonna write it for you, thats what youre running into
sleshepic said:
You dont want to change the boardconfig. You're gonna want the klte kernel folder in there where its supposed to be
Post your roomservice.xml from .repo/local_manifests. You prob just need to sync a klte kernel repo to your tree
Aside from a few build errors(overlay/base package stuff) you should be able to essentially sync and build once your roomservice is figured out. It's not yet a supported device so its not gonna write it for you, thats what youre running into
Click to expand...
Click to collapse
I have no roomservice.xml xD
pro_granade said:
I have no roomservice.xml xD
Click to expand...
Click to collapse
Boom, progress
I just got out off work and have to drive home but im working on stuff, ill shoot you some of the things you'll need when I get back. There are several folders you're missing
Edit: or if thats too much of a wait. Just make one up based off the cm.dependencies file in garwynn's klte repo(github), check that out and make up a local_manifest/roomservice.xml those folders, that tells you exactly what you need.
sleshepic said:
Boom, progress
I just got out off work and have to drive home but im working on stuff, ill shoot you some of the things you'll need when I get back. There are several folders you're missing
Edit: or if thats too much of a wait. Just make one up based off the cm.dependencies file in garwynn's klte repo(github), check that out and make up a local_manifest/roomservice.xml those folders, that tells you exactly what you need.
Click to expand...
Click to collapse
Alright, I'll look into it, if I can't comprehend it I'll wait xD

Resurrection Remix - Nougat - v5.8.0 (Soon to arrive)

*Content to be deleted by moderator*
HParra97 said:
Hey guys, I came across this rom while looking for an update on Nougat roms on RN3. Found this https://www.androidfilehost.com/?fid=601275311581037403
I have already installed it but I get a bootloop (waited like 12 minutes and no luck) (I have the goodix sensor model, maybe that is the reason why?). I do not want to offend the developer or anybody who is contributing with him for not having it done yet. I just wanted to bring this up to people's attention that we will soon be getting a Nougat version of RR for our device
Click to expand...
Click to collapse
Official RR maintainer for kenzo @war_machine28 confirmed that we gonna have a build today. So I think there is no need to create a new thread just for publishing a build that is also not yours. Please respect the developers and don't publish anyone's build without proper permission.
shanx_verma said:
1. If the developer didn't publish his ROM openly, you have NO F***ING right to do SO - STRICTLY against XDA RULES!!
2. Even if you really are having an URGE, the "GUIDES, NEWS, & DISCUSSION" is the section to go for - BUT precedence goes to no. 1 @HParra97.
DELETE THE CONTENT RIGHT NOW, please!
Click to expand...
Click to collapse
ansariabdulla1994 said:
Official RR maintainer for kenzo @war_machine28 confirmed that we gonna have a build today. So I think there is no need to create a new thread just for publishing a build that is also not yours. Please respect the developers and don't publish anyone's build without proper permission.
Click to expand...
Click to collapse
Apologize sincerely. I will delete the [post immediately. How do I delete this thread, as I have never done so before.

Unlocking Oculus Go

https://developer.oculus.com/blog/unlocking-oculus-go/
Now that we have an unlocked bootloader officially provided from Facebook, what can we do that we couldn't before?
https://reddit.com/r/oculusgo and the related discord room at https://discord.gg/HVahbueBkT have been puzzling over it, but we're kinda stuck at getting a Magisk onto the device and it seems we don't have access to recovery, so any assistance would be appreciated.
moocow1452 said:
https://developer.oculus.com/blog/unlocking-oculus-go/
Now that we have an unlocked bootloader officially provided from Facebook, what can we do that we couldn't before?
https://reddit.com/r/oculusgo and the related discord room at https://discord.gg/HVahbueBkT have been puzzling over it, but we're kinda stuck at getting a Magisk onto the device and it seems we don't have access to recovery, so any assistance would be appreciated.
Click to expand...
Click to collapse
Now the bootloader is unlocked and we can install any operating system, if one existed.
Now we can write our own operating system.
I know I am a bit late to this, however I did manage to port TWRP recovery for the Oculus Go. I have the source code uploaded to my GitHub if any devs want to take a look. I am trying to port AOSP to the device, but I am having issues with it. Might work towards getting LineageOS instead but I am not feeling too hopeful.
TWRP source device tree:
https://github.com/WolfLink115/twrp_device_oculus_pacific (remove spaces, I don't think I am able to post links as I don't really post too much on this account)
Wolf_Link115 said:
I know I am a bit late to this, however I did manage to port TWRP recovery for the Oculus Go. I have the source code uploaded to my GitHub if any devs want to take a look. I am trying to port AOSP to the device, but I am having issues with it. Might work towards getting LineageOS instead but I am not feeling too hopeful.
TWRP source device tree:
h t t p s :/ / github. com /WolfLink115/ twrp_device_oculus_pacific (remove spaces, I don't think I am able to post links as I don't really post too much on this account)
Click to expand...
Click to collapse
Oh, I should add on to this, I have no idea what isn't working. So far I can tell that mounting for the most part works, flashing Magisk seems to work, bit the screen isn't layed out properly. It is pretty much sideways (I think it is trying to diplay in portrait mode but I cannot seem to fix it.)
Wolf_Link115 said:
TWRP source device tree:
https://github.com/WolfLink115/twrp_device_oculus_pacific (remove spaces, I don't think I am able to post links as I don't really post too much on this account)
Click to expand...
Click to collapse
Hello and good afternoon, @Wolf_Link115
I've attached the link to your quoted post but you should have been able to do that, too. The restraint you've mentioned is no longer valid since the transition of the website from vBulletin to Xenforo.
Regards
Oswald Boelcke
Senior Moderator

Categories

Resources