Im not quite sure what it wants cause there isnt any folder there that it is calling
Code:
Notice file: system/core/netcfg/NOTICE -- /home/joe/[ubuntuTouch]/out/target/product/jewel/obj/NOTICE_FILES/src//system/bin/netcfg.txt
Import includes file: /home/joe/[ubuntuTouch]/out/target/product/jewel/obj/EXECUTABLES/pngtest_intermediates/import_includes
Export includes file: external/libpng/Android.mk -- /home/joe/[ubuntuTouch]/out/target/product/jewel/obj/EXECUTABLES/pngtest_intermediates/export_includes
Notice file: external/libpng/NOTICE -- /home/joe/[ubuntuTouch]/out/target/product/jewel/obj/NOTICE_FILES/src//system/bin/pngtest.txt
Import includes file: /home/joe/[ubuntuTouch]/out/target/product/jewel/obj/EXECUTABLES/radiooptions_intermediates/import_includes
Export includes file: hardware/ril/rild/Android.mk -- /home/joe/[ubuntuTouch]/out/target/product/jewel/obj/EXECUTABLES/radiooptions_intermediates/export_includes
Notice file: hardware/ril/rild/NOTICE -- /home/joe/[ubuntuTouch]/out/target/product/jewel/obj/NOTICE_FILES/src//system/bin/radiooptions.txt
make: *** No rule to make target `/home/joe/[ubuntuTouch]/out/target/product/jewel/obj/SHARED_LIBRARIES/libril_intermediates/export_includes', needed by `/home/joe/[ubuntuTouch]/out/target/product/jewel/obj/EXECUTABLES/rild_intermediates/import_includes'. Stop.
make: *** Waiting for unfinished jobs....
any help would be appreciated
I figured it out lol this is my first time being serious building something, but yay its still building so fingers crossed:fingers-crossed:
T10NAZ said:
Im not quite sure what it wants cause there isnt any folder there that it is calling
Code:
Notice file: system/core/netcfg/NOTICE -- /home/joe/[ubuntuTouch]/out/target/product/jewel/obj/NOTICE_FILES/src//system/bin/netcfg.txt
Import includes file: /home/joe/[ubuntuTouch]/out/target/product/jewel/obj/EXECUTABLES/pngtest_intermediates/import_includes
Export includes file: external/libpng/Android.mk -- /home/joe/[ubuntuTouch]/out/target/product/jewel/obj/EXECUTABLES/pngtest_intermediates/export_includes
Notice file: external/libpng/NOTICE -- /home/joe/[ubuntuTouch]/out/target/product/jewel/obj/NOTICE_FILES/src//system/bin/pngtest.txt
Import includes file: /home/joe/[ubuntuTouch]/out/target/product/jewel/obj/EXECUTABLES/radiooptions_intermediates/import_includes
Export includes file: hardware/ril/rild/Android.mk -- /home/joe/[ubuntuTouch]/out/target/product/jewel/obj/EXECUTABLES/radiooptions_intermediates/export_includes
Notice file: hardware/ril/rild/NOTICE -- /home/joe/[ubuntuTouch]/out/target/product/jewel/obj/NOTICE_FILES/src//system/bin/radiooptions.txt
make: *** No rule to make target `/home/joe/[ubuntuTouch]/out/target/product/jewel/obj/SHARED_LIBRARIES/libril_intermediates/export_includes', needed by `/home/joe/[ubuntuTouch]/out/target/product/jewel/obj/EXECUTABLES/rild_intermediates/import_includes'. Stop.
make: *** Waiting for unfinished jobs....
any help would be appreciated
Click to expand...
Click to collapse
I had same wrong . How to figure out? @T10NAZ
luzifer1984 said:
I had same wrong . How to figure out? @T10NAZ
Click to expand...
Click to collapse
You need to go to the directories that are said here that was in that error,
Code:
`/home/joe/[ubuntuTouch]/out/target/product/jewel/obj/SHARED_LIBRARIES/libril_intermediates/export_includes', needed by `/home/joe/[ubuntuTouch]/out/target/product/jewel/obj/EXECUTABLES/rild_intermediates/import_includes'.
and make the needed files. So i think i went all the way to the libril_intermediate folder then i needed to create the export_includes folder
T10NAZ said:
You need to go to the directories that are said here that was in that error,
Code:
`/home/joe/[ubuntuTouch]/out/target/product/jewel/obj/SHARED_LIBRARIES/libril_intermediates/export_includes', needed by `/home/joe/[ubuntuTouch]/out/target/product/jewel/obj/EXECUTABLES/rild_intermediates/import_includes'.
and make the needed files. So i think i went all the way to the libril_intermediate folder then i needed to create the export_includes folder
Click to expand...
Click to collapse
Thank U.
I add
Code:
$(shell mkdir -p $(OUT)/obj/SHARED_LIBRARIES/libril_intermediates)
$(shell touch $(OUT)/obj/SHARED_LIBRARIES/libril_intermediates/export_includes)
in 'BoardConfig.mk' . Compiled successfully. but don't work.
I figured it out.
WITH In BoardConfig.mk Comment out this line
> # RIL
> BOARD_PROVIDES_LIBRIL := true
ANY way . Thank u for reply
luzifer1984 said:
Thank U.
I add
Code:
$(shell mkdir -p $(OUT)/obj/SHARED_LIBRARIES/libril_intermediates)
$(shell touch $(OUT)/obj/SHARED_LIBRARIES/libril_intermediates/export_includes)
in 'BoardConfig.mk' . Compiled successfully. but don't work.
I figured it out.
WITH In BoardConfig.mk Comment out this line
> # RIL
> BOARD_PROVIDES_LIBRIL := true
ANY way . Thank u for reply
Click to expand...
Click to collapse
Sorry for digging up this old thread, but I am trying to build for the Evita and encountered this same error. Here was my error.
Just for clarification, did this allow a successful build after editing the BoardConfig.mk? Did it boot?
Black!Jack said:
Sorry for digging up this old thread, but I am trying to build for the Evita and encountered this same error. Here was my error.
Just for clarification, did this allow a successful build after editing the BoardConfig.mk? Did it boot?
Click to expand...
Click to collapse
I dont know if you already found your answer, But I have tried the boardconfig edit and it seems like its building right now it got past the RIL thing
Oh also I had to add qcom media-caf to help get past some libstagefright error too
T10NAZ said:
I dont know if you already found your answer, But I have tried the boardconfig edit and it seems like its building right now it got past the RIL thing
Oh also I had to add qcom media-caf to help get past some libstagefright error too
Click to expand...
Click to collapse
Yeah I ran into some issues with QCOM as well. I just went in, temporarily, to the directory listed in the error, and commented out the line that was stalling the build. Longest Ive been able to keep it building so far.
One other thing that I had to do was pull in the nfc-extras folder from frameworks/base... as I was constantly getting stalled there as well.
Black!Jack said:
Yeah I ran into some issues with QCOM as well. I just went in, temporarily, to the directory listed in the error, and commented out the line that was stalling the build. Longest Ive been able to keep it building so far.
One other thing that I had to do was pull in the nfc-extras folder from frameworks/base... as I was constantly getting stalled there as well.
Click to expand...
Click to collapse
That's good. One snag that I did hit was everything built just fine and flashed a ok, but it didnt boot >.< I dont know why it didnt. I am thinking its because it is having a hard time going to the data partition or something idk
T10NAZ said:
That's good. One snag that I did hit was everything built just fine and flashed a ok, but it didnt boot >.< I dont know why it didnt. I am thinking its because it is having a hard time going to the data partition or something idk
Click to expand...
Click to collapse
Did you update the kernel config file for your device? Any patches?
What device are you building for?
Another thing I am going to attempt is bringing up the phablet source to cm11, rather that cm10.1, which was 4.2.2
Black!Jack said:
Did you update the kernel config file for your device? Any patches?
What device are you building for?
Another thing I am going to attempt is bringing up the phablet source to cm11, rather that cm10.1, which was 4.2.2
Click to expand...
Click to collapse
Yea I put all the kernel configs that I didnt have in and the only thing that I did change was removing the nosuid thing from the data. I did find however that in the scripts/touch folder for the ramdisk has the partition calling and mounting script thing. I wonder if I need to edit that in order for it to boot
Black!Jack said:
Another thing I am going to attempt is bringing up the phablet source to cm11, rather that cm10.1, which was 4.2.2
Click to expand...
Click to collapse
UT moved from CM to AOSP. There is a new AOSP 4.4 based phablet tree.
Sent from my TF300T using Tapatalk
f69m said:
UT moved from CM to AOSP. There is a new AOSP 4.4 based phablet tree.
Sent from my TF300T using Tapatalk
Click to expand...
Click to collapse
Awesome news indeed! I'm on the mailing list, but honestly I haven't paid much attention to it as of late. Now I just have to do some work to the CM device tree to get it to build with AOSP.
Related
i have been trying to teach myself about kernels and followed this thread
http://forum.xda-developers.com/showthread.php?t=817387
im not sure where to get initramfs or if i need it.
if anyone who has built a kernel before can give me some pointers that'd be great
Dani897 said:
i have been trying to teach myself about kernels and followed this thread
http://forum.xda-developers.com/showthread.php?t=817387
im not sure where to get initramfs or if i need it.
if anyone who has built a kernel before can give me some pointers that'd be great
Click to expand...
Click to collapse
Man i have no idea i would try to reach out to the kernel gurus over in the captivate forum
Sent from my SAMSUNG-SGH-I997 using XDA Premium App
i asked glitterballs who linked me to that thread by stumpzy. i really am starting from scratch though. ive never compiled a kernel for anything before. at least now i know why the instructions in the readme file that comes in the source package didnt work. just a matter of editing one line in makefile. i tried to build it after that change but get errors.
Dani897 said:
i asked glitterballs who linked me to that thread by stumpzy. i really am starting from scratch though. ive never compiled a kernel for anything before. at least now i know why the instructions in the readme file that comes in the source package didnt work. just a matter of editing one line in makefile. i tried to build it after that change but get errors.
Click to expand...
Click to collapse
what errors?
/tmp/ccgqkvQY.s: Assembler messages:
/tmp/ccgqkvQY.s:2583: Error: can't resolve `.text' {.text section} - `.LFB1126' {.ARM.extab section}
make[1]: *** [arch/arm/kernel/process.o] Error 1
make: *** [arch/arm/kernel] Error 2
this is what i got without doing anything with .config.
another time after changing .config according to stumpzy's thread it went farther but had errors related to drivers, maybe the source isn't complete. i wish i had some background in this stuff, im just trying to teach myself and informations is hard to find if you dont know what you are looking for.
the above error appears to be from using the wrong toolchain. i tried one that unhelpful posted a while back but it doesnt seem to help at all. back to the one stumpzy posted
drivers/media/video/samsung/tv20/s5p_stda_grp.c: In function 's5ptvfb_set_par':
drivers/media/video/samsung/tv20/s5p_stda_grp.c:614:12: error: lvalue required as left operand of assignment
make[5]: *** [drivers/media/video/samsung/tv20/s5p_stda_grp.o] Error 1
make[4]: *** [drivers/media/video/samsung/tv20] Error 2
make[3]: *** [drivers/media/video/samsung] Error 2
make[2]: *** [drivers/media/video] Error 2
make[1]: *** [drivers/media] Error 2
make: *** [drivers] Error 2
i get these errors when i try to use stumpzy's instructions
did you use
the samsung tree of the 2.6.35 tree on open source. The full release of the code for the infuse has a readme text that says how to use the make to get the kernel.
Thanks
Jon
I am still trying to get the Ubuntu up and running so I can learn more also. We had a bad storm and lost power during the upgrade so still working on the computer.
the readme is wrong. the makefile needs to be editied to use that toolchain and i still get the errors.
just install stumpzy's vm, if you want a gui on it then apt-get fluxbox or another window manager.
cool
okay still trying to get my workspace set will let you know what happens and pls keep me in the loop also.
using these two:
http://forum.xda-developers.com/showpost.php?p=5626300&postcount=3
and
http://forum.xda-developers.com/showthread.php?t=633246
the second one may work with the modifie kitchen
Thanks
Jon
I have a good idea: let's move this to Android's Chef Central, where all the Android devs roam.
So here's the thing, after wrestling a lot with android sources to get them to compile, I did.
So now comes the task of adding a new device so I can actually compile it for my phone. Here's what I already did:
1. Used the existing CM sources for my phone and put them in devices/samsung/ancora (also ran extract-files.sh, and did all the necessary changes)
2. Got all the vendor files and put them in vendor/samsung/ancora
3. Altered the envsetup.sh to include the line "aokp_ancora-userdebug" so I can actually tell it to build the damn thing
4. Added an ancora.mk to the vendor/aokp/products folder with all the necessary information
Now what happens when I try to build is I get the error:
Code:
build/core/product_config.mk:205: *** No matches for product
How do I go about fixing this?
Thanks in advance for all those who help.
KezraPlanes said:
So here's the thing, after wrestling a lot with android sources to get them to compile, I did.
So now comes the task of adding a new device so I can actually compile it for my phone. Here's what I already did:
1. Used the existing CM sources for my phone and put them in devices/samsung/ancora (also ran extract-files.sh, and did all the necessary changes)
2. Got all the vendor files and put them in vendor/samsung/ancora
3. Altered the envsetup.sh to include the line "aokp_ancora-userdebug" so I can actually tell it to build the damn thing
4. Added an ancora.mk to the vendor/aokp/products folder with all the necessary information
Now what happens when I try to build is I get the error:
Code:
build/core/product_config.mk:205: *** No matches for product
How do I go about fixing this?
Thanks in advance for all those who help.
Click to expand...
Click to collapse
In vendor/products, did you also edit AndroidProducts.mk?
KBizzle said:
In vendor/products, did you also edit AndroidProducts.mk?
Click to expand...
Click to collapse
Yes I did. And it points to the ancora.mk that I created.
Ok guys, starting this theard also to find other devs that also are working on porting ubuntu touch to the same device and buildup a team, anyone interested?
So my 1st try was when CM wasn't final release and got stuck at boot, i could connect with adb, but i only got displayed ubuntu and kernel version, and only a few commands worked, this is my 2nd try, so let's hope it will work better this time, also i will put my work on github.
24.NOV.2013:
-Having issues with libstagefright: http://pastebin.com/C8cuCAYA
Not much at rom porting but I'm a strictly linux only user and will help anyway I can. Send me a pm or post where your git is.
Sent from my GT-I9505 using xda app-developers
JustSueMe said:
Not much at rom porting but I'm a strictly linux only user and will help anyway I can. Send me a pm or post where your git is.
Sent from my GT-I9505 using xda app-developers
Click to expand...
Click to collapse
Nice to have people interested in this project, I will get GIT up when I will have it running 1st 13.10 since its stable.
nyl said:
Nice to have people interested in this project, I will get GIT up when I will have it running 1st 13.10 since its stable.
Click to expand...
Click to collapse
Nice I have a dev build env for ubuntu touch but unsure how to pull repo for unknown device. But if u get a build that boots I'm more than eager to work on it
Sent from my GT-I9505 using xda app-developers app
I've tried a few times to get it going for the M919 but each time I can't get past the Samsung Splash screen. I wasn't even able to connect via adb. Granted, I don't exactly know what I'm doing, but I do have a build environment set up and do have a little experience building and debugging builds. I should have time to tinker with it again in a few weeks.
ubuntu build
nyl said:
Nice to have people interested in this project, I will get GIT up when I will have it running 1st 13.10 since its stable.
Click to expand...
Click to collapse
i have a build enviroment made up and pulled repos ect.. i just need to work a few things out before im ready to test it and post on here, if you can point in right direction (if yours boots)
need to do the audio part but can boot without sound in the alpha
neeed to add in apparmor later, can be done later ubuntu should boot without it
brightness, i dont think it matters so much as booting up is priority but i dont seem to have file it wants me to change "device/[manufacturer]/[codename]/init.[codename].rc"
problem with the way fstab has to be setup
within my android source my fstab is "void.fstab" which has lines that look like :
dev_mount sdcard /storage/sdcard1 auto /devices/platform/msm_sdcc.4/mmc_host/mmc2/ /devices/platform/msm_sdcc.2/mmc_host/mmc2/
ubuntu port guide for fstab asks to find a filename like "fstab.jfltexx" and have lines that look like:
/dev/block/platform/omap/omap_hsmmc.1/by-name/EFS /efs ext4 nosuid,nodev,barrier=1
help with fstab will be much appreciated.
then ill make my build ready for testing/debugging + suppose ill upload files output files for others that are interested to use
Try this
Code:
# Android fstab file.
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,barrier=1,errors=panic wait
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 noatime,nosuid,nodev,journal_async_commit wait,check
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 noatime,nosuid,nodev,journal_async_commit,noauto_da_alloc,errors=panic wait,check,encryptable=footer,length=-16384
# recovery
/dev/block/platform/msm_sdcc.1/by-name/boot /boot emmc defaults recoveryonly
/dev/block/platform/msm_sdcc.1/by-name/recovery /recovery emmc defaults recoveryonly
# vold managed volumes
/devices/platform/msm_sdcc.2/mmc_host/mmc2 auto auto defaults voldmanaged=sdcard1:auto
/devices/platform/msm_hsusb_host/usb auto auto defaults voldmanaged=sda:auto
Yes I used part of that, problem now is compile errors, I have fixed a lot of them which involved discarding some features for the time being.
Boot is the main priority though
Im stuck on a compile errors for shared library, ill attempt this one after I've slept.
Hope fully this is the last error, then ill have a .zip to upload .
Thats some great news ^^
What is the rom size?
Sent from my GT-I9505 using XDA Premium 4 mobile app
coolnessQ said:
Thats some great news ^^
What is the rom size?
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Erm i haven't got a system to flash yet, possibly I could try just getting a boot.img and flashing a ubuntu filesystem but the system modified will be needed to boot fully, in theory I'd only get a shell. I did have a boot.img [seemed to have misplaced it :s , comes out at 7.3mb]
When I've got more time I will go bk to source code and try work out how to solve the errors so I can have boot.img and system.img.
If anyone else is working on this, share problems and solutions With me ti help further the progress.
JustSueMe said:
Erm i haven't got a system to flash yet, possibly I could try just getting a boot.img and flashing a ubuntu filesystem but the system modified will be needed to boot fully, in theory I'd only get a shell. I did have a boot.img [seemed to have misplaced it :s , comes out at 7.3mb]
When I've got more time I will go bk to source code and try work out how to solve the errors so I can have boot.img and system.img.
If anyone else is working on this, share problems and solutions With me ti help further the progress.
Click to expand...
Click to collapse
are you unsing tw stock sources for the kernel? with 7.3mb it almost looks like that.
I have tried porting it before and here is my advise, you really have to look at the errors that it gives you during compiling rather then skipping it, or ignoring it, this is the only way you will get it decently working. the rom itself is only around 100mb if i remember correctly. the ubuntu package is like 400mb on top, but thats all proprietary files so universal.
Im using ubuntu tool.
So sources come from cyanogen's clone with modifications (if thats correct)
Yes I have been fixing errors hence no nfc support, but atm it's a problem with libstagefright [hardware video decoder] I was advised to remove it as not needed to make 1st boot but seems to be hardcoded in there
$ grep -r -H "stagefright" *
JustSueMe said:
Im using ubuntu tool.
So sources come from cyanogen's clone with modifications (if thats correct)
Yes I have been fixing errors hence no nfc support, but atm it's a problem with libstagefright [hardware video decoder] I was advised to remove it as not needed to make 1st boot but seems to be hardcoded in there
$ grep -r -H "stagefright" *
Click to expand...
Click to collapse
Here is the reference :good:
Code:
[email protected] /media/broodplank/linuxdatanew/AOSP-KK/device/samsung $ grep -r 'stagefright' .
./qcom-common/qcom-common.mk: libstagefrighthw \
also if you need clean sources for some particular things just use my repos from AOSP 4.3 (https://github.com/aosp-s4). it only includes the needed commits for jf devices only. way less filled with potential compile breakers like the source of cm.
broodplank1337 said:
Here is the reference :good:
Code:
[email protected] /media/broodplank/linuxdatanew/AOSP-KK/device/samsung $ grep -r 'stagefright' .
./qcom-common/qcom-common.mk: libstagefrighthw \
also if you need clean sources for some particular things just use my repos from AOSP 4.3 (https://github.com/aosp-s4). it only includes the needed commits for jf devices only. way less filled with potential compile breakers like the source of cm.
Click to expand...
Click to collapse
Ah I see this seems to of cleared it up abit for me, im busy today but may get look in at code, if not then tomorrow and clean it up abit and try recompile.
If it looks like a lost cause ill jump over to your git and pull that repo.
Fingers crossed
Sent from my GT-I9505 using xda app-developers app
commit to github so we can all take a look at it
.
..
You need to copy some header files for libstagefright to compile:
cp hardware/qcom/media/mm-core/inc/QCMediaDefs.h frameworks/av/media/libstagefright/
cp hardware/qcom/media/mm-core/inc/QCMetaData.h frameworks/av/media/libstagefright/
cp hardware/qcom/media/mm-
core/inc/QOMX_AudioExtensions.h frameworks/av/media/libstagefright/
cp hardware/qcom/media/mm-core/inc/OMX_QCOMExtns.h frameworks/av/media/libstagefright/
cp hardware/qcom/media/mm-core/inc/QCMediaDefs.h frameworks/av/media/libmediaplayerservice
My cm compiled but it wont boot (after flashing .zip and ubuntu system)
hmm.. did you remove all unecessary APPS? that are only needed by android not ubuntu touch? at you it seems relating to mounting points, something in your source doesn't let the kernel mount the partitions, maybe find a different approach to mount and add it to the source tree.
http://e2fsprogs.sourceforge.net/
everyone with interest in using ubuntu
if your interested in ubuntu touch on jfltexx and want to help
your now in luck
go here http://forum.xda-developers.com/showthread.php?p=48344910#post48344910
there is the download links and a few fixes for connectivity
Here is the link to the AT&T/Tmobile rom download : http://www.androidfilehost.com/?fid=23252070760974893'
Here is the link to the how to site (now instead of the phablet download use the one above) : http://forum.xda-developers.com/showthread.php?t=2564187
Oh and you need to flash the lokidoki zip file if used for AT&T.
Had it working perfectly, it is in extreme alpha, I had the wifi working and sound only works when plugged into headphones.
This should be more than enough to get the rom started up and getting a nice UT running shortly where everything works :3
I am not responsible for whatever happens to you or your device before, during, or after this. :3
When I run the ./get-prebuilts command i get "no such file or directory exists". I also get a "remote object '/system/app/CIRModule.apk' does not exist" when running the ./extract-files.sh. Any help? Thanks.
go to your device tree and open proprietary-files.txt and delete the line then save it bud.
Evolutionmods said:
go to your device tree and open proprietary-files.txt and delete the line then save it bud.
Click to expand...
Click to collapse
Why just delete it? I did this then it complained about "system/app/EasyAccessService/EasyAccessService.apk" so I removed it and it complained about "system/vendor/lib/libtime_genoff.so"
Something doesn't seem right here.
I am trying to build cm 12.1 btw.
jfain said:
Why just delete it? I did this then it complained about "system/app/EasyAccessService/EasyAccessService.apk" so I removed it and it complained about "system/vendor/lib/libtime_genoff.so"
Something doesn't seem right here.
I am trying to build cm 12.1 btw.
Click to expand...
Click to collapse
You don't have to delete them , it's just a work around. Those errors are are initially from the vendor, when you ran the extract-files.sh it didn't pull those most likely. You can gather from the Rom itself or find a more complete m8 vendor on github.
OK, those three files was the only missing from the current nightly I believe. I'll look on git hub this evening.
Thanks!
"Blobs" are the files specific to each device that we need in order to compile custom ROMS that work on our device. The process of finding them is tedious and slow... I have been picking away at them for months when I have time. There are over 600 files so far! But there are also references to files that are not being found. They are either missing, or they are not located where they are expected to be located. This is where I need help.
So, if you want to help, go HERE:
https://github.com/mightysween/android_vendor_motorola_payton
and look through the proprietary-files.txt file for anywhere that it says "warning".... and then search inside of the firmware (working on 8.0+ now, not 7.1 please) and try to track down the file that it says is missing [obviously, you will need a system dump, or to search on a rooted device]. If you find it, please post below like this:
LINE NUMBER OF THE WARNING (from github)
PATH TO THE MISSING FILE (relative to /system... in other words, don't inlude your own local path)
Once this file is complete, we can use it to automatically pull the correct vendor files into our build environments... having a working recovery, active kernel developement and completed vendor blobs should open us up to more development efforts.
Also, if anyone has done any testing and knows of other proproetary files that are needed, please post them here so I can include them.
My time at the computer to work on this is really limited, so I have only identified a dozen or so daemons that definitely call for proprietary libs... I am sure there are more
I would love to pitch in on this but have zero experience with anything related to development. Do you think I could still be of help? Sounds like a basic enough task that it wouldn't be too difficult. Let me check and see that I understand the process.
Went to github and looked at proprietary-files.txt. The first warning I found was in line 49: "blob file libpn553_fw.so missing or broken". Then searched for that file in my device's system folder using ES File Explorer with Root Explorer enabled.
So is this what you're looking for?
49
/system/vendor/firmware/libpn553_fw.so
---------- Post added at 14:31 ---------- Previous post was at 14:07 ----------
I'd like to contribute in some way but if this is best not left to a complete noob then I totally understand
mightysween said:
Also, if anyone has done any testing and knows of other proproetary files that are needed, please post them here so I can include them.
My time at the computer to work on this is really limited, so I have only identified a dozen or so daemons that definitely call for proprietary libs... I am sure there are more
Click to expand...
Click to collapse
Do you have a link to a system dump?
TheBassDude said:
I would love to pitch in on this but have zero experience with anything related to development. Do you think I could still be of help? Sounds like a basic enough task that it wouldn't be too difficult. Let me check and see that I understand the process.
Went to github and looked at proprietary-files.txt. The first warning I found was in line 49: "blob file libpn553_fw.so missing or broken". Then searched for that file in my device's system folder using ES File Explorer with Root Explorer enabled.
So is this what you're looking for?
49
/system/vendor/firmware/libpn553_fw.so
---------- Post added at 14:31 ---------- Previous post was at 14:07 ----------
I'd like to contribute in some way but if this is best not left to a complete noob then I totally understand
Click to expand...
Click to collapse
Thanks, that is all there is to it
Just time consuming (especially after the first 500)...lol
QWZR said:
Do you have a link to a system dump?
Click to expand...
Click to collapse
Nah, too big to conveniently upload... but if you are rooted, you can use the phone to search
mightysween said:
Nah, too big to conveniently upload... but if you are rooted, you can use the phone to search
Click to expand...
Click to collapse
Mine gets here next week
mightysween said:
Nah, too big to conveniently upload... but if you are rooted, you can use the phone to search
Click to expand...
Click to collapse
If you have root on the system you can find the files for, you should be able to find any given filename with:
find / -name "filename" -print
And it should output any filenames that match. I don't have time at the moment to dig into this any more, but would this resolve much of it?
ebrandsberg said:
If you have root on the system you can find the files for, you should be able to find any given filename with:
find / -name "filename" -print
And it should output any filenames that match. I don't have time at the moment to dig into this any more, but would this resolve much of it?
Click to expand...
Click to collapse
Any way that works is fine by me
I am on the road a lot and just don't have enough time to sit and work on it... so it is taking months. I bet a few people helping could finish it in a matter of hours.
I am hoping to have a few hours next week to work on it. But the sooner this is done, the sooner I can shift to trying to compile Lineage OS with working hardware.
BTW, Lineage *does* compile if I comment out all the stuff causing make errors... not much works, obviously.
The next step will be compiling with these blobs, then logging all the new errors and chasing down all the additional broken symlinks... and then adapting the kernel as needed.
Then, MAYBE we can get a base Lineage tree up and open up the X4 to building for other roms. I know someone started a skeleton tree for Carbon already on Github... they are likely just waiting for the completed device tree, too.
mightysween said:
Thanks, that is all there is to it
Just time consuming (especially after the first 500)...lol
Click to expand...
Click to collapse
ebrandsberg said:
If you have root on the system you can find the files for, you should be able to find any given filename with:
find / -name "filename" -print
And it should output any filenames that match. I don't have time at the moment to dig into this any more, but would this resolve much of it?
Click to expand...
Click to collapse
I don't own this device yet, but I was thinking of getting one. I figured this might help you all out (you'll need to be running linux):
First, let's get a list of all the files on the phone, to make searching faster.
Code:
adb shell
su
find / > /sdcard/allfiles.txt
exit
exit
adb pull /sdcard/allfiles.txt
Now you should have allfiles.txt on your machine. Also grab the proprietary-files.txt, and then run this:
Code:
grep -Po '(?<=(blob file )).*(?= missing or broken)' proprietary-files.txt | xargs -I @ grep "@" allfiles.txt
That should find the paths of all the missing files (except the ones marked "wildcard")
BLuFeNiX said:
I don't own this device yet, but I was thinking of getting one. I figured this might help you all out (you'll need to be running linux):
First, let's get a list of all the files on the phone, to make searching faster.
Code:
adb shell
su
find / > /sdcard/allfiles.txt
exit
exit
adb pull /sdcard/allfiles.txt
Now you should have allfiles.txt on your machine. Also grab the proprietary-files.txt, and then run this:
Code:
grep -Po '(?<=(blob file )).*(?= missing or broken)' proprietary-files.txt | xargs -I @ grep "@" allfiles.txt
That should find the paths of all the missing files (except the ones marked "wildcard")
Click to expand...
Click to collapse
Thanks, I had recently completed this, but your code worked fantastic for double checking, and actually helped me find one that I had missed :good:
Now, on to identifying any more daemons that need proprietary files... and then assembling the tree itself... PROGRESS!
PHASE 1 is complete!
https://github.com/mightysween/android_vendor_motorola_payton
I am 99% sure that this is only ~75% of what will be needed to actually build LOS15. But it is a good foundation to work off of now.
My plan is to start attempting to compile LOS and take error logs to chase down the remaning missing stuff. LOTS to be done still to get to that point...hoping for some other builders/devs to materialize here and help out
Hi! Just a question: it´s mandatory to use A/B partition scheme to build a custom ROM for this device or it will be possible to use a traditional partition scheme and free up some GBs of internal storage for use?
christianrj said:
Hi! Just a question: it´s mandatory to use A/B partition scheme to build a custom ROM for this device or it will be possible to use a traditional partition scheme and free up some GBs of internal storage for use?
Click to expand...
Click to collapse
It would seem that we will still be stuck with A/B, as the bootloader does the initial check of the active slot. Perhaps there may be some clever ways around this in the future...but nothing I will be tackling.
mightysween said:
It would seem that we will still be stuck with A/B, as the bootloader does the initial check of the active slot. Perhaps there may be some clever ways around this in the future...but nothing I will be tackling.
Click to expand...
Click to collapse
You would probably need a custom kernel to do it properly. The bootloader passes a kernel param (androidboot.ro.boot.slot_suffix) specifying which slot to use. In the absense of a kernel param, the value is read from the ro.boot.slot_suffix build property.
That being said, you might be able to just repartition your device to only have 1 slot, flash your ROM, and use
Code:
fastboot --set-active=_a
. If your ROM has disabled OTA updates from the OEM, you should be fine.
I'm going to get an X4 in the coming weeks. I'd like to help with this soon. I'm a seasoned developer by trade and can collab on GitHub. Hope to be able to start working with you soon. :good:
I don't know if any of you have seen this article, but it seems promising that it might not be too difficult to achieve for this device:
https://www.xda-developers.com/xiaomi-redmi-note-4-project-treble/
Hariiiii said:
I don't know if any of you have seen this article, but it seems promising that it might not be too difficult to achieve for this device:
https://www.xda-developers.com/xiaomi-redmi-note-4-project-treble/
Click to expand...
Click to collapse
@vache at the Moto G5 Plus forums has already managed it using the /oem partition which is otherwise unused for custom ROMs
Hariiiii said:
I don't know if any of you have seen this article, but it seems promising that it might not be too difficult to achieve for this device:
https://www.xda-developers.com/xiaomi-redmi-note-4-project-treble/
Click to expand...
Click to collapse
Cool... seems it may be possible. Will follow the progress on the Redmi and G5 devices
navenedrob said:
I'm going to get an X4 in the coming weeks. I'd like to help with this soon. I'm a seasoned developer by trade and can collab on GitHub. Hope to be able to start working with you soon. :good:
Click to expand...
Click to collapse
The more I am reading about enabling Treble, the more I think it is entirely possible.... and probably the best direction to focus our efforts.
Seems like we have partitions that could be used as /vendor. I am reading up on exactly how the Treble vendor partition is set up. Tricky, but not implausible.
EDIT: Actually, none of the partitions we could potentially re-purpose for /vendor are big enough. So, it may be harder on this device than on others. It may require repartitioning.