Hello everyone!
I am quite a newbie to build the LineageOS, earlier this week I was trying to write my own device tree files, I had prepared most of the files needed and was managed to add my device to the lunch menu.
However when I was trying to building my twrp recovery image following peter9811's tutorial(link), the compilation was always failed with
Code:
[100% 140/140] out/soong/.bootstrap/bin/soong_build out/soong/build.ninja
FAILED: out/soong/build.ninja
out/soong/.bootstrap/bin/soong_build -t -l out/.module_paths/Android.bp.list -b out/soong -n out -d out/soong/build.ninja.d -globFile out/soong/.bootstrap/build-globs.ninja -o out/soong/build.ninja Android.bp
error: vendor/lineage/build/soong/Android.bp:30:8: module "generated_kernel_includes": cmd: unknown variable '$(PATH_OVERRIDE_SOONG)'
16:47:35 soong bootstrap failed with: exit status 1
1.I looked up the 'vendor/lineage/build/soong/Android.bp' and found $(PATH_OVERRIDE_SOONG) is defined somewhere else, possibly in my Android.mk.
2.I tried google the problem but got nothing except an unresolved post.
3.I tried to lunch aosp_arm-eng or aosp_arm64-eng and it gives the same error, however, lineage_arm64-userdebug works just fine.
As far as I know the aosp is switch from makefile to soong, my wild guess is this process makes some of those tutorials outdated, if that so, could somebody post some up-to-date instructions?
Could anyone please tell me what is going on there, which file should I modify to avoid this kind of problems.
Thanks for reading my post, and any possible solution will be much appreciated.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
hi man!
not sure if you still interested in solving this. This occurs because the config files inside vendor/lineage isn't being included in some build/*.mk files. This is weird because you're using LOS repo, so it should already have the commit where it does this inclusion. Repo sync might help you in there.
If it doesn't, take a look at this commit. It's a lineage-18.1 commit, but you should compare it and see what still needed on your side.
Did you find any solution to this? i am facing similar issue while building cafex and still cant find any solution. M from sources is up to date.
akshatpro said:
Did you find any solution to this? i am facing similar issue while building cafex and still cant find any solution. M from sources is up to date.
Click to expand...
Click to collapse
I had the same issue and solved it by using the breakfast command before building rom. No extra editing required.
Relevant XDA post/thread
Source
eatmyriceboi69420 said:
I had the same issue and solved it by using the breakfast command before building rom. No extra editing required.
Click to expand...
Click to collapse
Ohhh how I wish that fixed it for me. Lunch, bacon, refreshmod, clobber. Nothing works
Vinnom said:
If it doesn't, take a look at this commit. It's a lineage-18.1 commit, but you should compare it and see what still needed on your side.
Click to expand...
Click to collapse
Thank you sir! These look exactly like the droids I have been looking for!
EDIT: soooo that just created new errors (vendor/lineage/build/soong/soong_config.mk doesn't exist)
Had a brain spark, deleted the entire local/working folder. (not .repo of course).
Then a simple repo sync -l and now I'm at least building.
Fingers crossed
Related
Essentially, in an attempt to learn C# better, I had an idea for an app (windows) to have a database of devices (only ET4G now because it isn't done and it's the phone I have) and allow easy access to ADB commands, rooting (Device-specific, wiki links, etc.)
So, for example the ET4G screen may contain things like (it's not finished yet, so it could contain any number of features):
Device Status
Root
ADB Remount
Built-in ADB shell
Wikis
I don't know how my development schedule will work for this since i have many other projects (that are real production projects), but in my spare time I'm planning to finish a working prototype
I just want to see if anybody would be interested in it, it is noob friendly and I already started it as a learning project
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
bbedward said:
Essentially, in an attempt to learn C# better, I had an idea for an app (windows) to have a database of devices (only ET4G now because it isn't done and it's the phone I have) and allow easy access to ADB commands, rooting (Device-specific, wiki links, etc.)
So, for example the ET4G screen may contain things like (it's not finished yet, so it could contain any number of features):
Device Status
Root
ADB Remount
Built-in ADB shell
Wikis
I don't know how my development schedule will work for this since i have many other projects (that are real production projects), but in my spare time I'm planning to finish a working prototype
I just want to see if anybody would be interested in it, it is noob friendly and I already started it as a learning project
Click to expand...
Click to collapse
most awesome, I remember we had something like this on the samsung vibrant, really useful
Great job, and thanks for the effort.
Sent from a phone with kNOw CIQ ...
If enough interest would be generated I think it'd be cool to make a PC rom manager - type application. I dont have lots of interest in auto rooting and stuff since we already have apps for that.
I'd like to make a full application with a database of devices and list of roms/kernels etc. But itll take a lot of time and I don't have that eventually I think this can come together well.
Sent from my SPH-D710 using Tapatalk
Hey Guys,
The Admins decided to basically add the Charm forums into the Flipout forums, so far only the main forum heading has been changed, hopefully the admins will do the rest of the changes soon.
In the meanwhile, i thought it would be useful to post useful threads on the charm porting, basically since flipout and charm are the same phone with a different design, these should be applicable with respective changes to flipout also.
[PORT][CWM v5.0.2.6] Boostrapped Recovery for Charm and Flipside
Author : polovinamozga
Post : http://forum.xda-developers.com/showpost.php?p=14796425&postcount=412
Content :
polovinamozga said:
Big Bootstrapped Recovery Update
20 June Update
25 Sep 2011
mot_boot_mode.bin updated
12 Oct 2011
Version bump from 2.x.x.x to 5.x.x.x
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I totally reworked process for start clockwork recovery.
Now it started via hijacking mot_boot_mode.
More stable.
Not needed symlinks for mot_boot_mode.
Not needed shell-scripts for reboot into recovery (rr.sh).
Not needed terminal or adb shell acess.
APK available
How it works.
It hijacked mot_boot_mode executable if /data/.recovery_mode file exist
system at boot will start recovery from
/cdrom/recovery !!!
Code:
# ls -l /cdrom/recovery
Code:
-rwxr-xr-x root root 483020 2011-06-17 03:52 hijack
-rwxr-xr-x root root 1422867 2011-06-17 03:52 recovery.zip
-rwxr-xr-x root root 255908 2011-06-17 03:52 update-binary
Hijacked executable will unpack recovery.zip via update-binary, restart root-hacked adbd.
Don't forget that will be /cdrom/cdrom_vfat.bin REMOVED
If you need it backup it by hands.
If you use my previous recovery you need
or manually remove all files (needed normal lvl of unix knowledge)
or reflash your phone via RsdLite or sbf_flash
known bug:
system can't remount from recovery menu.fixed
Needed TESTERS
Needed Designer for create logo for apk
Features request welcome!
Apk in attach.
Mirror here
Oh!
Needed smart guys with C-code experience for develop own Bootmenu.
I do not have time to do everything.
source code here:
https://github.com/fedya/CharmBootstrap
Click to expand...
Click to collapse
Credits to the respective author and aforementioned credits.
Looks Interesting, but i dont think that there is any use of it for me.
Yeh cause absolutely no good roms out there for the Charm muchless Flipside. Not any I have found with working links yet. ****ty.
Sent from my EVO using Tapatalk 2
Yeh cause absolutely no good roms out there for the Charm muchless Flipside. Not any I have found with working links yet. ****ty. <br />
<br />
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
Finaly theres CM7 MB511 Ruth Flipout. That could be used by devs to Port it to other devices.
Btw. Sorry for my Last Post, well used it can get pretty usefull
Sent from somewhere...
Hi, I'm trying to sync CM9 sources. I've set up my Ubuntu 11.10 from differents pages of xda, like the guide of Rom2Maru.
So, all libs are intalled, jdk6 is also installed ,etc. So, yesteray I started to start to sync, using the instructions of the PecanCM's github:
Code:
repo init -u git://github.com/PecanCM/android.git -b ics
repo sync -j16
And I don't know why but after 4 hours it stucks. I have tried 3 times and in the 3 times it stucks at the final. I've got a lot of memory left on my hard drive so I don't know why it stucks.
I have run a log and nothing special, here you have a Screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
In the first terminal, here is my sync stucked. In the second one, Here is the log. So, in the thirst I did a "repo sync", but it stucks too.
So, please, can anyone help me? I'm really interested in learn about android and can compile it.
Thanks a lot
hi, try this
from root of source
Code:
cd .repo
rm -rf manifest*
rm -rf repo
cd ..
mv .repo ../.repo
cd ..
rm -rf {name of source folder}
mkdir cm9
mv .repo cm9/.repo
cd cm9
repo init -u git://github.com/PecanCM/android.git -b ics
repo sync -f
hope this works for you
Thanks for your help, but it's stucked in:
Fetching projects: 100% (258/258), done.
I don't know what can I do. Do you have another idea?
And, Which version of ubuntu are you using? Are you using wubi? And what post do you use to set up your ubuntu (jdk, libs,etc)?
Thanks
Some time it happens with me too but i fix it by repo sync -f ! try only repo sync -f I hope it will work for you
Ok, I've done what you said, I restarted to sync again, and I have some news problems:
First, It stucks agains here:
Then, It said that I have to use repo sync -f --force-broken, so I did:
But It said that can't sync, and there isn't git in bootloader.
Any one can help me please? thanks
repo sync -f should work bro !
OK guys here a surprise for you
I just compile a clockwork mod recovery from Ubuntu Touch source code based on Phablet-10.1 (CM-10.1) so i think we have a good probability after I port this recovery to make Ubuntu Touch more compatibility after this one i will start to build the rom now and test it if work or not.
P.S. : the recovery is not working good i think used to deploy the zip automatically over adb so i will not upload it fow now.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What a surprise. That's a good start...
LeroViten said:
What a surprise. That's a good start...
Click to expand...
Click to collapse
OK i try it with a rom that i compiled a few weeks ago, after deploying to sdcard and installation start automatically once rebooted to recovery but still won't boot.
In the second test i will edit the device tree and making system partition mounted automatically and see if work or not
The little phone that could. Good job!!!
Via the Internet
New Test
OK guys i am compiling a rom using phablet-4.4.2 with modifications of device tree such as no prebuilt, no power, no selinux, no camerahal to get compiled without errors so if anyone can told me commits of cm11 for that errors i will insert him to thanked person if got booted .
Hmmm, nice work bro.. why dont you post your errors and progress here?, maybe someone can help you.
K_TECH said:
Hmmm, nice work bro.. why dont you post your errors and progress here?, maybe someone can help you.
Click to expand...
Click to collapse
I know bro the only problem is Canonical because they switch back from AOSP to Cyanogen Mod source again so if we want to work on Ubuntu Touch we must decide on which version should be ported Trusy or Saucy?
https://wiki.ubuntu.com/Touch/Building
And also they still updating the porting guide since released the full version so i think we should wait
I have no stats for Kernel Wakelocks in BetterBatteryStats. I've installed the latest version, installed the system app, but still get nothing. Everything else shows and works fine. Anyone else having this issue?
Yes, I face the same issue. Its a known issue and dev does not have cycles right now.
Cycles?
I think it also took a special fix for the LG g5 to show them...
Haldi4803 said:
Cycles?
Click to expand...
Click to collapse
lol...that's dev-speak for time for development work.
Ok, thanks for the heads up. It's not a huge deal, was just wondering if it was me, or something else.
I could be wrong but I get this.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Custom Rom? Custom Kernel?
Installed as System App?
This is the leedroid rom, but it worked on the US ruu one too. I don't think I installed it as system.
Sent from my HTC 10 using XDA-Developers mobile app
V2.2B6?
devsk said:
HTC init scripts are not mounting the debugfs. That's the reason for missing kernel wakelocks in HTC 10. Do the following from a root shell:
Code:
mntP=$(grep /sys/kernel/debug /proc/mounts | awk '{print $2}')
if [[ "${mntP}" != "/sys/kernel/debug" ]]
then
mount -t debugfs none /sys/kernel/debug
fi
Relaunch BBS and it should show the kernel wakelocks now.
Click to expand...
Click to collapse
Don't forget su, and you need to kill the App after the command
Haldi4803 said:
Don't forget su, and you need to kill the App after the command
Click to expand...
Click to collapse
Is this something that needs to be run on every boot, or once run it should stay? If it needs to be re-run on boot I suppose I'll just make Tasker run the script.
duowing said:
Is this something that needs to be run on every boot, or once run it should stay? If it needs to be re-run on boot I suppose I'll just make Tasker run the script.
Click to expand...
Click to collapse
This needs to be done every boot and as root.