Related
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.
I am currently using the HTC EVO 4G LTE. I have found with more updated roms using jellybean that the MAP profiles work and allow SMS to my Ford Mustang. There are a couple of complications though. When calling someone or receiving a call the caller id on car dash shows "Unknown" and when I receive a SMS the car thinks I sent it so when you reply it replies back to your self. I found while searching all over the internet that someone had found a way to edit a MapUtils.java file to make it work correctly. I have downloaded the source code on my ubuntu machine for CM10.0 and edited this file and built it successfully. When installed on my phone it would not get past the boot animation. Only way I got it to boot was to "fastboot" flash a boot.img file from another working CM10.0 rom. After this process the issue was resolved but It wound up breaking "Message Notification" in the Ford Sync system. Is there something I am missing about what is being changed in this file or why my original build would not boot? I would really like to use a SENSE rom but can not figure out where to build it from source (if you can) and where that file would even sit. I would appreciate it if someone could help me out with this.
Car - 2013 Ford Mustang with standard Stereo
Original Post Bellow
"Once you've got your build environment setup with CM7, CM9, or CM10, open up
packages/apps/Bluetooth/src/com/android/bluetooth/map/MapUtils/MapUtils.java and find this line (It's on line 539 as of today):
sb.append("TEL:").append(bmsg.recipient_vcard_phon e_number)
Replace it with this line:
sb.append("TEL:").append(bmsg.originator_vcard_pho ne_number)"
wilhar0046 said:
I am currently using the HTC EVO 4G LTE. I have found with more updated roms using jellybean that the MAP profiles work and allow SMS to my Ford Mustang. There are a couple of complications though. When calling someone or receiving a call the caller id on car dash shows "Unknown" and when I receive a SMS the car thinks I sent it so when you reply it replies back to your self. I found while searching all over the internet that someone had found a way to edit a MapUtils.java file to make it work correctly. I have downloaded the source code on my ubuntu machine for CM10.0 and edited this file and built it successfully. When installed on my phone it would not get past the boot animation. Only way I got it to boot was to "fastboot" flash a boot.img file from another working CM10.0 rom. After this process the issue was resolved but It wound up breaking "Message Notification" in the Ford Sync system. Is there something I am missing about what is being changed in this file or why my original build would not boot? I would really like to use a SENSE rom but can not figure out where to build it from source (if you can) and where that file would even sit. I would appreciate it if someone could help me out with this.
Car - 2013 Ford Mustang with standard Stereo
Original Post Bellow
"Once you've got your build environment setup with CM7, CM9, or CM10, open up
packages/apps/Bluetooth/src/com/android/bluetooth/map/MapUtils/MapUtils.java and find this line (It's on line 539 as of today):
sb.append("TEL:").append(bmsg.recipient_vcard_phon e_number)
Replace it with this line:
sb.append("TEL:").append(bmsg.originator_vcard_pho ne_number)"
Click to expand...
Click to collapse
Cannot build from Sense ROM source. You'd have to smali edit if you're experienced with byte code.
However looking at the code posted, seems like whatever you quoted is adding a space in phone_number (phon e_number).
Make sure when you replace the code you take out the space to read:
Code:
sb.append("TEL:").append(bmsg.originator_vcard_phone_number)
exSD said:
Cannot build from Sense ROM source. You'd have to smali edit if you're experienced with byte code.
However looking at the code posted, seems like whatever you quoted is adding a space in phone_number (phon e_number).
Make sure when you replace the code you take out the space to read:
Code:
sb.append("TEL:").append(bmsg.originator_vcard_phone_number)
Click to expand...
Click to collapse
Thank you for your response. I did make sure that the space was taken out of that line. The author of the original post must have done it by accident. Not sure if I would get the same rests if I tried to build a aokp ROM instead of CM. The build worked just would not boot with originally boot.img file. I fixed the main issue that I was attempting but broke other things that were already working.
wilhar0046 said:
Thank you for your response. I did make sure that the space was taken out of that line. The author of the original post must have done it by accident. Not sure if I would get the same rests if I tried to build a aokp ROM instead of CM. The build worked just would not boot with originally boot.img file. I fixed the main issue that I was attempting but broke other things that were already working.
Click to expand...
Click to collapse
Are you signing the apk once you recompile it?
Post a snapshot of your code or I can run a join.me session with you to look at it with you.
exSD said:
Are you signing the apk once you recompile it?
Post a snapshot of your code or I can run a join.me session with you to look at it with you.
Click to expand...
Click to collapse
I am creating a ROM not a application. I am building CM from source and compiling it. I end up with a flashabe zip of the ROM I can flash with TWRP or CWM recoveries.
wilhar0046 said:
I am creating a ROM not a application. I am building CM from source and compiling it. I end up with a flashabe zip of the ROM I can flash with TWRP or CWM recoveries.
Click to expand...
Click to collapse
You are compiling a ROM and editing the Maps application.
Link me to the git/source you're editing the java code from.
exSD said:
You are compiling a ROM and editing the Maps application.
Link me to the git/source you're editing the java code from.
Click to expand...
Click to collapse
Here is the code I used to get the source
repo init -u git://github.com/CyanogenMod/android.git -b jellybean
exSD said:
You are compiling a ROM and editing the Maps application.
Link me to the git/source you're editing the java code from.
Click to expand...
Click to collapse
BTW MAP is referring to Message Access Profile/Protocol ..not sure which p it is lol. It allows Bluetooth devices to access certain messages on your phone such as Text messages. The car can receive them and read them aloud. The hole point in editing the java file is so that the text appears to come from the correct sender instead of me. I could not make my original build work. Something is wrong with the boot.IMG file. When I flash a working boot.IMG over my existing build it boots and fixes the initial problem but winds up breaking other things that were originally workong., such as message notifications.
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.
The screenshot is attached! Got this error after the download was complete!
Syncing work tree: 58% (268/462) error: in `sync -f`: revision refs/heads/cm-11.0 in CyanogenMod/android_frameworks_base not found
Anyone has any idea what can be wrong? Or any solution?
shahrukhqasim said:
The screenshot is attached! Got this error after the download was complete!
Syncing work tree: 58% (268/462) error: in `sync -f`: revision refs/heads/cm-11.0 in CyanogenMod/android_frameworks_base not found
Anyone has any idea what can be wrong? Or any solution?
Click to expand...
Click to collapse
it looks like you initialised your repo to 'refs/heads/cm-11.0' when it should just be 'cm-11.0' but I can't be 100% sure.
Try just 'repo sync' rather than 'repo sync -f'
is it the first time this has happened? Is it the first time you have done a repo sync?
matt4321 said:
it looks like you initialised your repo to 'refs/heads/cm-11.0' when it should just be 'cm-11.0' but I can't be 100% sure.
Try just 'repo sync' rather than 'repo sync -f'
is it the first time this has happened? Is it the first time you have done a repo sync?
Click to expand...
Click to collapse
I have tried that too -f gives some other error in fetching some project. I have deleted everything and restarted. I hope error will disappear. Its so huge download anyway. And yes, its my first time trying to get code. Wanted to start development.
shahrukhqasim said:
I have tried that too -f gives some other error in fetching some project. I have deleted everything and restarted. I hope error will disappear. Its so huge download anyway. And yes, its my first time trying to get code. Wanted to start development.
Click to expand...
Click to collapse
It's good you're wanting to start developing! Maybe give it a day and try again, it may be a CM side problem.
You can always ask here for help: http://forum.xda-developers.com/showthread.php?t=2620389
matt4321 said:
It's good you're wanting to start developing! Maybe give it a day and try again, it may be a CM side problem.
You can always ask here for help: http://forum.xda-developers.com/showthread.php?t=2620389
Click to expand...
Click to collapse
Here in our country, internet connection is slow. It took like 3 days last time to sync all the code. I am doing it again. I'll keep in touch! I am very much hopeful I won't run into any problems this time. Thanks!
matt4321 said:
It's good you're wanting to start developing! Maybe give it a day and try again, it may be a CM side problem.
You can always ask here for help: http://forum.xda-developers.com/showthread.php?t=2620389
Click to expand...
Click to collapse
Found the issue. It had something to do with the file system. Some error occurred. A directory was not accessible neither could delete nor read. I checked the file system from windows. It was actually an NTFS drive. I mount it on Ubuntu. Then I was able to delete it and now started from scratch.
I wanted to ask if it is OK to use NTFS file system? Or it might cause some issues like if file names become very long or any other issue?
matt4321 said:
it looks like you initialised your repo to 'refs/heads/cm-11.0' when it should just be 'cm-11.0' but I can't be 100% sure.
Try just 'repo sync' rather than 'repo sync -f'
is it the first time this has happened? Is it the first time you have done a repo sync?
Click to expand...
Click to collapse
how can i resolve this
Syncing work tree: 59% (277/469) error: in `sync -f`: revision refs/heads/cm-11.0 in CyanogenMod/android_frameworks_base not found
repo init also not working how can resolve this
"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.