CLOSED
XDA:DevDB Information
QualComm AptXHD Drivers, Tool/Utility for the HTC 10
Contributors
Eliminater74, thewalkingdude, indian-mafia
Source Code: https://github.com/TheMuppets/proprietary_vendor_htc/commit/4a5c92c6213c89b31838335ab7a61397e4a1418e
Version Information
Status: Snapshot
Created 2017-02-16
Last Updated 2017-02-22
Downloads:
CLOSED
Reserved
Since we know these questions are coming, here's how to check and make sure the mod works:
Option 1: Computer
Run this command: adb logcat | grep -i "aptx"
This must be done on the computer. adb logcat uses the adb.exe to read the logcat from the device, then piping the output of the log into a search command to look for aptx. You have to do this quickly after you first start playing music. If you're too slow, you will miss the buffer and the message will no longer be there. If the command spits out some lines containing aptx, then it works.
Option 2: Phone
Open a terminal emulator and type:
Code:
su
logcat | cat > /sdcard/logtemp.txt
**close the terminal window and start a new one. Since the logcat keeps going, that window will no longer take commands**
su
grep -i "aptx" /sdcard/logtemp.txt
You have to do this quickly after you first start playing music. If you're too slow, you will miss the buffer and the message will no longer be there. If the command spits out some lines containing aptx, then it works.
I'm sad I didn't get a credit for giving you the source lol
noob question: so if I flash this on my htc 10, it would improve the sound quality with any bluetooth devices? or do I need a specific aptxHD-compatible bluetooth device? thanks
c19932 said:
noob question: so if I flash this on my htc 10, it would improve the sound quality with any bluetooth devices? or do I need a specific aptxHD-compatible bluetooth device? thanks
Click to expand...
Click to collapse
You need a compatible Bluetooth device. aptx.com has a list of them.
prsterero said:
Since we know these questions are coming, here's how to check and make sure the mod works:
Run this command: adb logcat | grep -i "aptx"
quickly after you first start playing music. If you're too slow, you will miss the buffer and the message will no longer be there. If the command spits out some lines containing aptx, then it works.
If it's needed, I'll edit this post with a bit more detail.
Click to expand...
Click to collapse
Should I type [adb logcat | grep -i "aptx"] in android terminal?
BrianKuo1853 said:
Should I type [adb logcat | grep -i "aptx"] in android terminal?
Click to expand...
Click to collapse
Check out my updated post
Is it possible to make a systemless/Magisk-compatible version of this mod?
Captain_Throwback said:
Is it possible to make a systemless/Magisk-compatible version of this mod?
Click to expand...
Click to collapse
That's a had great idea! That would definitely be possible. It's very simply 3 libs and a build.prop addition.
tabp0le said:
I'm sad I didn't get a credit for giving you the source lol
Click to expand...
Click to collapse
Dear OP,
Honestly... Are you kidding me? No comment...
tabp0le said:
I'm sad I didn't get a credit for giving you the source lol
Click to expand...
Click to collapse
they pulled the source.. lucky I have it on my github still..
But Thank you @tabp0le For supplying the source.
dh.harald said:
Dear OP,
Honestly... Are you kidding me? No comment...
Click to expand...
Click to collapse
Hes joking man....... we hang out together in slack................
Eliminater74 said:
they pulled the source.. lucky I have it on my github still..
But Thank you @tabp0le For supplying the source.
Hes joking man....... we hang out together in slack................
Click to expand...
Click to collapse
OK, Here's my thread:
https://forum.xda-developers.com/oneplus-3/themes/mod-aptx-codec-t3521228
so... are you kidding me?
Eliminater74 said:
they pulled the source.. lucky I have it on my github still..
But Thank you @tabp0le For supplying the source.
Hes joking man....... we hang out together in slack................
Click to expand...
Click to collapse
dh.harald said:
OK, Here's my thread:
https://forum.xda-developers.com/oneplus-3/themes/mod-aptx-codec-t3521228
so... are you kidding me?
Click to expand...
Click to collapse
Lmao! I didn't say I wrote the source. I gave him the link to it. Hahaha you need to go take a pill. Maybe don't talk crap if you don't know what your talking about.
dh.harald said:
OK, Here's my thread:
https://forum.xda-developers.com/oneplus-3/themes/mod-aptx-codec-t3521228
so... are you kidding me?
Click to expand...
Click to collapse
First off I dont go around on the threads looking at other devices to see if they support something for us.. I took my crap Direct from qualcomm my self.........
then did all the work my self.. I did not take nothing from nowhere else.. if you think I did.. then go report it.. cause I got proof.
Eliminater74 said:
First off I dont go around on the threads looking at other devices to see if they support something for us.. I took my crap Direct from qualcomm my self.........
then did all the work my self.. I did not take nothing from nowhere else.. if you think I did.. then go report it.. cause I got proof.
Click to expand...
Click to collapse
If you got that libraries from Qualcomm, why didn't got the original aptxHD library? Just because it's libaptXHD-1.0.0-int-Android21-ARMv7A.so from LG V20 rom, I just renamed it, lol...
dh.harald said:
If you got that libraries from Qualcomm, why didn't got the original aptxHD library? Just because it's libaptXHD-1.0.0-int-Android21-ARMv7A.so from LG V20 rom, I just renamed it, lol...
Click to expand...
Click to collapse
And your point to all this is?, Yes I got it from a Public Repo called the Muppets that you pushed there and that was reverted by Dan..... and that 100 other people took......
so whats your point? its all public............................ But if you are the one that took it from the v20, then guess you deserve a thanks too..
I threw this crap up on this thread really to just let others use it.. I put the little zip together really quick and uploaded it..
I dont even read this thread.. a friend of mine showed me your post.........
But in the future if you dont want your stuff leaked out, Then dont push it to Huge public Repos.............
But thank you for your work.... and I will change the #op when I get a chance with your name............
Eliminater74 said:
And your point to all this is?, Yes I got it from a Public Repo called the Muppets that you pushed there and that was reverted by Dan..... and that 100 other people took......
so whats your point? its all public............................ But if you are the one that took it from the v20, then guess you deserve a thanks too..
I threw this crap up on this thread really to just let others use it.. I put the little zip together really quick and uploaded it..
I dont even read this thread.. a friend of mine showed me your post.........
But in the future if you dont want your stuff leaked out, Then dont push it to Huge public Repos.............
But thank you for your work.... and I will change the #op when I get a chance with your name............
Click to expand...
Click to collapse
That's everything, that I need
Thanks!
Anyone found a difference with the htc stereoclip? This codec is backward compatible with aptx devices but would it enhance their audio quality or they will still be limited by their hardware?
Sent from my HTC 10 using XDA-Developers Legacy app
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
@Eugene_373 wow. Thanks man. should hopefully have AOSP 2.3 for vibrant ready to flash this weekend. Trees are ready to go.
dligon said:
@Eugene_373 wow. Thanks man. should hopefully have AOSP 2.3 for vibrant ready to flash this weekend. Trees are ready to go.
Click to expand...
Click to collapse
That's great news but... next time ________ (I'll let someone else fill in these blanks about where this thread should have been posted)
Oh, oh I know...Pick me Pick me. Is it the general Section?!
sorry about that i was just excited about the tweet...
dligon said:
sorry about that i was just excited about the tweet...
Click to expand...
Click to collapse
Lol, no big. It's awesome news. We're not even officially on 2.2 and now we're moving onto a 2.3 daily driver. Did Eugene share any other info about the source\leak?
What happened what did eugene do?
Sent from my SGH-T959 using XDA App
I love Eugene.
Sent from my SGH-T959 using XDA App
wow... really...
maybe you should post WHO posted that tweet.
This was actually posted from Krylon360 Twitter.
YES! LOVE that guy.
Paging Dr B said:
Lol, no big. It's awesome news. We're not even officially on 2.2 and now we're moving onto a 2.3 daily driver. Did Eugene share any other info about the source\leak?
Click to expand...
Click to collapse
no he was just retweeting what @Krylon360 hat tweeted.
sorry about that man. i was copying and pasting and left that out.
krylon360 said:
wow... really...
maybe you should post WHO posted that tweet.
Click to expand...
Click to collapse
what do you think stopped the build
jokersax11 said:
what do you think stopped the build
Click to expand...
Click to collapse
It's a PRODUCT_COPY_FILES is malformed (vibrant_full.mk) error.
there is only 1 line that uses that command in my mk, and thats to copy over the full list of APNs.
But it does tell it to call device.mk where pretty much all of the files are copied over. So I'll have to dig through both.
krylon360 said:
It's a PRODUCT_COPY_FILES is malformed (vibrant_full.mk) error.
there is only 1 line that uses that command in my mk, and thats to copy over the full list of APNs.
But it does tell it to call device.mk where pretty much all of the files are copied over. So I'll have to dig through both.
Click to expand...
Click to collapse
are you running a 64 or 32bit ubuntu
jokersax11 said:
are you running a 64 or 32bit ubuntu
Click to expand...
Click to collapse
x32, but commented out where it calls for 64bit. Though, from what Im seeing, that hack doesnt work anymore. I think I saw an actual patch somewhere on google groups.
krylon360 said:
x32, but commented out where it calls for 64bit. Though, from what Im seeing, that hack doesnt work anymore. I think I saw an actual patch somewhere on google groups.
Click to expand...
Click to collapse
are you running that line before or after the system.img is made. btw alot of people have had problems with the same thing.
ok once again sorry if i caused any confusion for not posting the complete tweet. sorry krylon360 and the other devs that worked tirelessly on this.
jokersax11 said:
are you running that line before or after the system.img is made. btw alot of people have had problems with the same thing.
Click to expand...
Click to collapse
it would be before. It error's out during the Lunch process. So..it goes like this. (path is a example..not the actual path to my source)
[email protected]/home/aosp/:
lunch
[email protected]/home/aosp/:
1: full-eng
2: sim-eng
3: passion-userdebug
4:...something else, cant remember
5: full_crespo-eng
6: full_vibrant-eng
[email protected]/home/aosp/: 6
error happens here.
so I don't even have a chance to run make -j4
krylon360 said:
it would be before. It error's out during the Lunch process. So..it goes like this. (path is a example..not the actual path to my source)
[email protected]/home/aosp/:
lunch
[email protected]/home/aosp/:
1: full-eng
2: sim-eng
3: passion-userdebug
4:...something else, cant remember
5: full_crespo-eng
6: full_vibrant-eng
[email protected]/home/aosp/: 6
error happens here.
so I don't even have a chance to run make -j4
Click to expand...
Click to collapse
good luck i would try to help but im leaving now. if you still have the issue in the next few days ill try to help. some of the teamdouche team might help.
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 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
Hi guys.
With one guy, who doesn't have Huawei phone, we try to debug why 3.10.90 isn't booting, but logcat seems that everything is okkey, and cat /proc/kmsg and other adb shell commands gives errors. So I try go get a help, could someone upstream the following kernel (3.10.89) to 3.10.90 and make it bootable too ? I tried it for 4 days, modifying ramdisk, etcetc... nothing worked... couldn't debug cuz adb shell wasn't working(i mean it was working, but next commands weren't, i even installed adb insecure ap, usb debugg on etc).
@XTutorials @surdu_petru @haky 86 @XePeleato(if you know somehow ) @DingDongPow or others. Thanks!
https://ufile.io/rvlmk (why no github ? 1. ffs can't even upload it there 2. only when i finish the upstreams)
You must learn to crawl before you can walk.
In the first place you are debugging userspace when the change you made was in the kernel, obviously you aren't catching the error, whatever it is.
Brian Kernighan said:
Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it.
Click to expand...
Click to collapse
In this case if you don't understand the code, you are obviously not going to be able to debug it.
Spend some time familiarizing yourself with the kernel, it's the only way to learn.
DingDongPow said:
Soo what do you want me to do fam?
(I don't use linux anymore soo i doubt i can really help)
Click to expand...
Click to collapse
I knew you can't help me, i just tagged you.
@dominj97
Here I am, days pass noone help... A guy with totally different phone helped me more than actual p8 lite devs, ty... (i understand that some can't help, but the rest?.. Shame)
We just don't have the time to spoonfeed you. We are no tech support nor we have to provide you with support, the shame is that you refuse to actually learn something and just want to compile that damn kernel no matter the cost. It takes like five minutes to someone with enough skill to compile a kernel (it's just running a command).
The sooner you understand that this is out of your league and start with the basics, the better.
It's your choice to take this as advice or as a rant.
D1stRU3T0R said:
Here I am, days pass noone help... A guy with totally different phone helped me more than actual p8 lite devs, ty... (i understand that some can't help, but the rest?.. Shame)
Click to expand...
Click to collapse
XePeleato said:
We just don't have the time to spoonfeed you. We are no tech support nor we have to provide you with support, the shame is that you refuse to actually learn something and just want to compile that damn kernel no matter the cost. It takes like five minutes to someone with enough skill to compile a kernel (it's just running a command).
The sooner you understand that this is out of your league and start with the basics, the better.
It's your choice to take this as advice or as a rant.
Click to expand...
Click to collapse
We continue here, okey xd
First, i already learned the basics. I know the command to build, but bcs we don't have a source kernel, I'm running from problems to problems.i can solve easy problems, but when not even google heard about it nor other phone devs, it's something interesting.... I know that you aren't a scam tech supp...i mean tech support, but damn, it's soo hard to answer to at least 1 message out of 5? I'm having more help from a stranger, who is pshichologist, and work alot, but still help more than from actuall "friends".. I understand you, no phone no help, XTutorials did everything he could, haky too (somehow). I'm here being ignored bcs I didn't borned with Linux under my as...house. I don't think that it's sooooooooooo hard to answer a question, even a harder one, you won't lose your job or school free time with that "ruined" 2-10 min. This start to be off topic anyways. I already passed these problems. Now i try to work with hakys kernel
Can you post it here? Any picture or log of that error?
D1stRU3T0R said:
We continue here, okey xd
First, i already learned the basics. I know the command to build, but bcs we don't have a source kernel, I'm running from problems to problems.i can solve easy problems, but when not even google heard about it nor other phone devs, it's something interesting.... I know that you aren't a scam tech supp...i mean tech support, but damn, it's soo hard to answer to at least 1 message out of 5? I'm having more help from a stranger, who is pshichologist, and work alot, but still help more than from actuall "friends".. I understand you, no phone no help, XTutorials did everything he could, haky too (somehow). I'm here being ignored bcs I didn't borned with Linux under my as...house. I don't think that it's sooooooooooo hard to answer a question, even a harder one, you won't lose your job or school free time with that "ruined" 2-10 min. This start to be off topic anyways. I already passed these problems. Now i try to work with hakys kernel
Click to expand...
Click to collapse
tried to delete that file, more errors...
https://m.imgur.com/a/Tw9VI
Which file? There's no need to remove any file, it complains because the toolchain (aarch64-...) isn't in your PATH, so get the toolchain and edit PATH so that the build system can find it
D1stRU3T0R said:
tried to delete that file, more errors...
Click to expand...
Click to collapse
XePeleato said:
Which file? There's no need to remove any file, it complains because the toolchain (aarch64-...) isn't in your PATH, so get the toolchain and edit PATH so that the build system can find it
Click to expand...
Click to collapse
Hmm.. I was watching that... Little chance that there is something wrong, as i know for sure that i modified it to the right path. Will check, maybe gcc is named linux_x86-x64 not only linux_x86 idk, thanks for the hint. (build.sh file)
Try to run in a Terminal 'aarch64-linux-android-gcc' if it can't find it, then it isn't set properly. It also complains because where you are trying to build it is not clean, Are you building in a different directory? (out/)
D1stRU3T0R said:
Hmm.. I was watching that... Little chance that there is something wrong, as i know for sure that i modified it to the right path. Will check, maybe gcc is named linux_x86-x64 not only linux_x86 idk, thanks for the hint. (build.sh file)
Click to expand...
Click to collapse
XePeleato said:
Try to run in a Terminal 'aarch64-linux-android-gcc' if it can't find it, then it isn't set properly. It also complains because where you are trying to build it is not clean, Are you building in a different directory? (out/)
Click to expand...
Click to collapse
K I'll try. Out of directory? Downloaded/extracted to downloads, renamed, (modified), changed build.sh and that's it xd.
Well, it says it isn't clean so you've tried to compile it without specifying an out directory (make whatever) instead of (make O=out/ whatever)
D1stRU3T0R said:
K I'll try. Out of directory? Downloaded/extracted to downloads, renamed, (modified), changed build.sh and that's it xd.
Click to expand...
Click to collapse
XePeleato said:
Well, it says it isn't clean so you've tried to compile it without specifying an out directory (make whatever) instead of (make O=out/ whatever)
Click to expand...
Click to collapse
Actually, I'm using your(i mean hakys kernel, but you fixed his wifi problems) kernel. Will that work on stock?
Oooohhh and i had a problem with config.. It said something config not found for merge_hi6250(p9 right?)... So i copied Alice defconfig and renamed that, and than it was working *insert black guy meme pointing at his head*
There's where I can't help, I don't know if it will work. That wifi thing was made for non EMUI systems, but that doesn't mean that it can't work on EMUI.
D1stRU3T0R said:
Actually, I'm using your(i mean hakys kernel, but you fixed his wifi problems) kernel. Will that work on stock?
Oooohhh and i had a problem with config.. It said something config not found for merge_hi6250(p9 right?)... So i copied Alice defconfig and renamed that, and than it was working *insert black guy meme pointing at his head*
Click to expand...
Click to collapse
D1stRU3T0R said:
Actually, I'm using your(i mean hakys kernel, but you fixed his wifi problems) kernel. Will that work on stock?
Oooohhh and i had a problem with config.. It said something config not found for merge_hi6250(p9 right?)... So i copied Alice defconfig and renamed that, and than it was working *insert black guy meme pointing at his head*
Click to expand...
Click to collapse
You mean this guy????
XePeleato said:
There's where I can't help, I don't know if it will work. That wifi thing was made for non EMUI systems, but that doesn't mean that it can't work on EMUI.
Click to expand...
Click to collapse
Builded, after some mins it booted, 3 sec later system crashed, automatically rebooted :/ ... second boot isnt happening anymore. Fail.
D1stRU3T0R said:
Builded, after some mins it booted, 3 sec later system crashed, automatically rebooted :/ ... second boot isnt happening anymore. Fail.
Click to expand...
Click to collapse
What do You need? Maybe i can help you!
RootingPro-18 said:
What do You need? Maybe i can help you!
Click to expand...
Click to collapse
Nothing right now... No kernel is working how much i would like. I'm using esal right now, but sadly can't be upstreamed to 3.10.90 due to errors at boot. Hakys new kernel has system problems, etcetc