Related
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
Can anyone either give a step-by-step guide to building a kernel from source on Ubuntu. or give a link to a good guide. I have searched the web but I cant find a straightforward guide.
I think I have done most things but when I try to 'make' I get the error 'make: arm-eabi-gcc: Command not found'
Im guessing I dont have the correct gcc toolchain but I dont know how to get/install it.
From the flykernel post:
erasmux said:
Kernel Sources
My sources with all my updates and changes are found on github:
http://github.com/erasmux/hero-2.6.29-flykernel
Use hero_defconfig for the regular version and hero-bfs_defconfig for the BFS version.
See the wiki for more information about building the kernel. Another great resource about kernel building is the cyanogen wiki - do note that currently the CM kernel will not work on the hero.
Please feel free to contact me regarding my sources and kernel development.
Click to expand...
Click to collapse
The cyanogen wiki is excellent.
You just need Android NDK!
Hi,
you just need Android NDK and add proper dir to environment PATH variable to fix your problem...
If you should have any problems, here is a step by step guide for you:
1) Get latest Android NDK from: developer.android.com/sdk/ndk/index.html
(Ubuntu: android-ndk-r5-linux-x86.tar.bz2)
2) Extract it wherever you wish (tar -xvjf android-ndk-r5-linux-x86.tar.bz2)
3) Set some variables typing:
export CROSS_COMPILE=arm-eabi-
export PATH=$PATH:/path/to/android-ndk-r5/toolchains/arm-eabi-4.4.0/prebuilt/linux-x86/bin/
And U R ready to compile your kernel
For your first compilation I recommend use erasmux's flykernel!
Just follow the steps from this short wiki github.com/erasmux/hero-2.6.29-flykernel/wiki
Have a fast compilation dude
f_padia said:
Can anyone either give a step-by-step guide to building a kernel from source on Ubuntu. or give a link to a good guide. I have searched the web but I cant find a straightforward guide.
I think I have done most things but when I try to 'make' I get the error 'make: arm-eabi-gcc: Command not found'
Im guessing I dont have the correct gcc toolchain but I dont know how to get/install it.
Click to expand...
Click to collapse
first download the prebuilt binaries from android source:
run this command in bash:
Code:
git clone git://android.git.kernel.org/prebuilt
then download the kernel source, for example Behnaam old kernel:
Code:
mkdir android
cd android
git clone https://github.com/behnaam/HeRo-2.6.29-GoDmOdE.git
then follow these steps:
https://github.com/behnaam/HeRo-2.6.29-GoDmOdE/wiki/
yes, that easy
Does this code link closely to any programming languages like Java? Visual Basic? I've been learning C++ and would like to get into the developing scence
Calico5 said:
Does this code link closely to any programming languages like Java? Visual Basic? I've been learning C++ and would like to get into the developing scence
Click to expand...
Click to collapse
There is some Java of course but I'm pretty sure there's also some C and C++
Calico5 said:
Does this code link closely to any programming languages like Java? Visual Basic? I've been learning C++ and would like to get into the developing scence
Click to expand...
Click to collapse
The kernel code is pure C.
The android code is mostly Java and C++, maybe also some c.
As far as I know no visual basic, thank god
erasmux said:
The kernel code is pure C.
The android code is mostly Java and C++, maybe also some c.
As far as I know no visual basic, thank god
Click to expand...
Click to collapse
No man that would be great! That's the only coding language besides Windows DOS I speak :'(
erasmux said:
The kernel code is pure C.
The android code is mostly Java and C++, maybe also some c.
As far as I know no visual basic, thank god
Click to expand...
Click to collapse
Thanks for the info! I think i'll finish off learning C++, before having a look at Java... then maybe one day i can become an android developer
C0mpu13rFr34k said:
No man that would be great! That's the only coding language besides Windows DOS I speak :'(
Click to expand...
Click to collapse
same here! VB is just soo easy albeit rubbish in pure programming talk
Well this link is little old but should work to, anyway the basics
http://forum.androidcentral.com/htc...how-build-your-own-kernel-package-source.html
elelinux said:
Well this link is little old but should work to, anyway the basics
http://forum.androidcentral.com/htc...how-build-your-own-kernel-package-source.html
Click to expand...
Click to collapse
thanks! I did finally come across this page after much searching. its an excellent guide and very easy to follow... now on to the compiling...
I have started adding some info for developers to my flykernel wiki. I have done some minor updates to the page about building the kernel, including adding the link brought by elelinux, big thanks to him
I have also added a small git tutorial which can be very helpful to developers new to git.
Hi all!
Polish community (lgswift.pl and android.com.pl) started an action on official CyanogenMod forums about adding GT540 to supported devices list.
There is maaaany Swift/Optimus users all around the world so if we will speak together as one maybe we will get what we want and deserve
I hope you would help by posting in: forum.cyanogenmod.com/topic/7108-lg-optimus-gt540/
Sorry for bypassing links but its not spam and moderation of n00bs will be better
If its wrong place for this topic please move it ^^
Sorry for my bad english
I'll try to spread this into the bulgarian forums !
People
we have to fight for themselves. The more people the better it is typed. Team CyanogenMod may finally be interested in our phone. You can also do petitioners in this case. Who is behind this let him write here.
I'm sorry I write with translator.
pass this link around and when we have enough signed up ill email CM devs to see what they say
http://www.petitiononline.com/CMGT540/petition.html
keep topic alive
signed and sealed
Signed
Sent from my GT540 using XDA Premium App
Signed but only 286
Sent from my GT540-Sense using XDA App
More than 350 now 4pda and modaco power
Sent from my GT540 using XDA Premium App
signed and sealed
Now more than 365
I think that more than 70 bulgarians have signed the petition !
907 signatures !!!!!!
CM Team got interested in supporting our device but... there is another case T.T
We need project maintainer and the source code must be published.
Unfortunately Mur4ik refused when he was asked to become the maintainer.
Oh. I'm not ready atm to be a maintainers for our device and regularly support for new CM changes.
Maybe in future.
Click to expand...
Click to collapse
Here is his explanation, but I think he will be a right person in right place
Another user from lgswift.pl has sended request to Joestone (We will see what he think about it soon, I hope), but he has his own project...
The other ideas was to ask Ankuch or Quarx, but they have different devices now so I dont think they will be interested (but who knows).
There was also the idea to ask arekl1988 who created v20a_openpl_fastboot.kdz rom.
Anyway without Mur4ik's source codes the support won't be possible so he is our only hope
Yep arek created fastboot rom, and ported Amon Ra recovery... but he haven't got time and knowledge
Quarx don't have diffrent device but he gt540 is broken... he collect money for new swift
Sorry for my english
Can you guys provide a walkthrought on how to quickly add a device by merging this code and the device source code?
What to look for in source, where to place it
How to safely test it, etc
With this walkthrought you can get users quickly enabled to start on creating support for their own devices as wel as more community maintainership
pretty pretty pretty please
bachera said:
Can you guys provide a walkthrought on how to quickly add a device by merging this code and the device source code?
What to look for in source, where to place it
How to safely test it, etc
With this walkthrought you can get users quickly enabled to start on creating support for their own devices as wel as more community maintainership
pretty pretty pretty please
Click to expand...
Click to collapse
This is on the way
We have a load to document, and we will be doing it as quickly as possible. We can provide a guide on how to go from AOSP => Omni quickly. It's a bit complex to explain how to safely test on any device, as that depends on specific per-device knowledge that a developer of that device has.
But we'll do our best to help people get building
pulser_g2 said:
This is on the way
We have a load to document, and we will be doing it as quickly as possible. We can provide a guide on how to go from AOSP => Omni quickly. It's a bit complex to explain how to safely test on any device, as that depends on specific per-device knowledge that a developer of that device has.
But we'll do our best to help people get building
Click to expand...
Click to collapse
I have been following this guide...but its rather incomplete and is not clear on some explanation so I got stuck halfway through. Wasn't sure what it meant by looking for the commit of new device addition in the vendor (for ominirom) so i kinda stop halfway through...lol maybe you can make some sense out of it, clarify it and help me by me helping you
http://xda-university.com/as-a-developer/porting-aosp-roms-using-source-code
---------- Post added at 03:42 PM ---------- Previous post was at 03:41 PM ----------
bachera said:
Can you guys provide a walkthrought on how to quickly add a device by merging this code and the device source code?
What to look for in source, where to place it
How to safely test it, etc
With this walkthrought you can get users quickly enabled to start on creating support for their own devices as wel as more community maintainership
pretty pretty pretty please
Click to expand...
Click to collapse
Lol meant to quote you
mgbotoe said:
I have been following this guide...but its rather incomplete and is not clear on some explanation so I got stuck halfway through. Wasn't sure what it meant by looking for the commit of new device addition in the vendor (for ominirom) so i kinda stop halfway through...lol maybe you can make some sense out of it, clarify it and help me by me helping you
http://xda-university.com/as-a-developer/porting-aosp-roms-using-source-code
---------- Post added at 03:42 PM ---------- Previous post was at 03:41 PM ----------
Lol meant to quote you
Click to expand...
Click to collapse
.
Vendor is the manufacturer i believe. OR the devices code name. Ex. HTC EVO 4G is the supersonic and HTC EVO 4G LTE is the Jewel.
Well i gathered that part (been catching up on my source lingo) what i meant is finding the add new device commit on ominirom vendor commit. I guess i need to see some example? Ominirom vendor is listed as android_vendor_custom if you want to take a look
mgbotoe said:
Well i gathered that part (been catching up on my source lingo) what i meant is finding the add new device commit on ominirom vendor commit. I guess i need to see some example? Ominirom vendor is listed as android_vendor_custom if you want to take a look
Click to expand...
Click to collapse
Wasnt the repo int "repo int http://www.github.com/omnirom/android.git (something else) android-4.3" ?
Sent from my EVO using XDA Premium 4 mobile app
lreyes said:
Wasnt the repo int "repo int http://www.github.com/omnirom/android.git (something else) android-4.3" ?
Sent from my EVO using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I used this repo init -u git://github.com/omnirom/android.git -b android-4.3 and it worked fine...just actually got done syncing.
Its essentially the same, you just forgot the -b
mgbotoe said:
I used this repo init -u git://github.com/omnirom/android.git -b android-4.3 and it worked fine...just actually got done syncing.
Its essentially the same, you just forgot the -b
Click to expand...
Click to collapse
Yeah that "(something else)" was the -b I just forgot what it was. I got the source all correct and fully synced but as you read in my thread I'm gonna have to do some dirty work.
Sent from my EVO using XDA Premium 4 mobile app
For htc explorer,all i needed to do was place the device,kernel,vendor repositories in the correct place,rename the makefile(not sure if even required,but did it anyways),and built.that;s it
sakindia123 said:
For htc explorer,all i needed to do was place the device,kernel,vendor repositories in the correct place,rename the makefile(not sure if even required,but did it anyways),and built.that;s it
Click to expand...
Click to collapse
what build commend did you use?
mgbotoe said:
what build commend did you use?
Click to expand...
Click to collapse
same as aosp, "make otapackage"
sadly i keep getting an error. I think i choose the wrong time to learn source codes and building them lol
Code:
build/core/tasks/kernel.mk:86: **********************************************************
build/core/tasks/kernel.mk:87: * Kernel source found, but no configuration was defined *
build/core/tasks/kernel.mk:88: * Please add the TARGET_KERNEL_CONFIG variable to your *
build/core/tasks/kernel.mk:89: * BoardConfig.mk file *
build/core/tasks/kernel.mk:90: **********************************************************
make: *** No rule to make target `otapackage'. Stop.
awesome, just installed virtual machine to run Ubuntu. I am wagering I need that to start git syncs and move source files around in this sync.
Really guys I am clueless. I probably need to create a fork first so I dont sync g2 stuff to base lol.
I think I am not up to the task
sakindia123 said:
same as aosp, "make otapackage"
Click to expand...
Click to collapse
How I didn't remember this! I had a hard time unpacking system image and creating a flashable zip. LoL
found it http://docs.omnirom.org/Setting_Up_A_Compile_Environment
bachera said:
I give up. Cant get sdk installed lol
Click to expand...
Click to collapse
Welcome to Linux my friend :fingers-crossed:
sakindia123 said:
same as aosp, "make otapackage"
Click to expand...
Click to collapse
I just brunch, works great
sevenup30 said:
Welcome to Linux my friend :fingers-crossed:
Click to expand...
Click to collapse
achievement unlocked syncing first git.
is it normal some stuff cant be downloaded?
bachera said:
achievement unlocked syncing first git.
is it normal some stuff cant be downloaded?
Click to expand...
Click to collapse
I would say normally not, but I believe it's that the omni source isn't finished on github.
Edit, I believe, if I remember correctly, one on the device trees on the manifest to be synced isn't on their github. Which will probably be fixed soon enough.
Just because one is anonymous doesn't mean that one has privacy.
syncing going on. I got a lg g2 d802 with sources from lg,
Am starting an experiment. Wont get the speed anywhere near the pros.
I got sources from LG for the 4.2.2 rom. Will this be a version de mismatch with 4.3?
Now I need to add\edit some files. No walkthrough for that yet.
Anybody has a good hook on where I can check next steps? I was thinking probably along the lines in this post:
http://forum.xda-developers.com/showthread.php?p=46453349
I have been running about, trying to create a basic custom ROM for my device.
Have tried most of the methods mentioned in forums. Nothing seems to work.
Anybody out here who can guide me through it?
Also, explaining customising the Android system.
Thanking everyone in advance.
arbajmessiali said:
I have been running about, trying to create a basic custom ROM for my device.
Have tried most of the methods mentioned in forums. Nothing seems to work.
Anybody out here who can guide me through it?
Also, explaining customising the Android system.
Thanking everyone in advance.
Click to expand...
Click to collapse
Create??????
Really don't get the "thanks in advance" thing!!
akshmau5 said:
Create??????
Really don't get the "thanks in advance" thing!!
Click to expand...
Click to collapse
Yes. Create.
I mean building or compiling.
arbajmessiali said:
Yes. Create.
I mean building or compiling.
Click to expand...
Click to collapse
If you are an up and coming developer (I am assuming) then Github or the best place to start would be from lineage os website and their guide "how to build for your device".
And ofc you would need all possible help from our lead device developers like Shivam Kumar Jha and Sagar for the device trees, kernel source codes and what not!! I have no clue.
The base is already compiled from AOSP by the respective main contributors rather head developers. You have to take the source code and tweak it/compile it (ofc not easy) for our device.
You asked the question to explain android customisation in general!!! Well, if you don't know that, then unless you are on NZT-48 or a really genius programmer, I doubt you can do it. (Also great if you prove me wrong here). Don't mean to discourage you.
Wouldn't we do it all for ourselves??!!!!!
For Android customization - the basics would be to root and go tweaking, fiddling and modding around on the stock rom first. Lots of amazing stuff already. (Why to reinvent the wheel!)
Then depends on your requirements.
Good luck.
akshmau5 said:
If you are an up and coming developer (I am assuming) then Github or the best place to start would be from lineage os website and their guide "how to build for your device".
And ofc you would need all possible help from our lead device developers like Shivam Kumar Jha and Sagar for the device trees, kernel source codes and what not!! I have no clue.
The base is already compiled from AOSP by the respective main contributors rather head developers. You have to take the source code and tweak it/compile it (ofc not easy) for our device.
You asked the question to explain android customisation in general!!! Well, if you don't know that, then unless you are on NZT-48 or a really genius programmer, I doubt you can do it. (Also great if you prove me wrong here). Don't mean to discourage you.
Wouldn't we do it all for ourselves??!!!!!
For Android customization - the basics would be to root and go tweaking, fiddling and modding around on the stock rom first. Lots of amazing stuff already. (Why to reinvent the wheel!)
Then depends on your requirements.
Good luck.
Click to expand...
Click to collapse
A real thank you.
Have already started the learning process.
Hope to come up with a ROM soon.
arbajmessiali said:
A real thank you.
Have already started the learning process.
Hope to come up with a ROM soon.
Click to expand...
Click to collapse
Oh that's great mate!
Are you in computer science?
Or what programming languages do you know?
akshmau5 said:
Oh that's great mate!
Are you in computer science?
Or what programming languages do you know?
Click to expand...
Click to collapse
I am pursuing Mechanical Engineering.
But I do know Java and web development.
arbajmessiali said:
I am pursuing Mechanical Engineering.
But I do know Java and web development.
Click to expand...
Click to collapse
Good stuff!!
Attaboy:good:
I am trying the same thing myself using the lineageOS 15.1 branch.
I am using the directions provided in the lineageOS Wiki for the X00TD device (can't post a link because i am a newbie).
The instructions are clear enough but I am having specific problems with the brunch command - specific errors come up for missing files.
Is this the right place to start posting specific technical questions?