Related
If you are still running the original Telus ROM, there is a file I'd really like to get my hands on. It's this:
/etc/SuplRootCert
It's referenced in the original gps.conf file for Telus phones.
SUPL_TLS_HOST=supl.telusmobility.com
SUPL_TLS_CERT=/etc/SuplRootCert
I am hoping it might help with the GPS issues. If you could pull it and post it, I would be very grateful.
marinierb said:
If you are still running the original Telus ROM, there is a file I'd really like to get my hands on. It's this:
/etc/SuplRootCert
It's referenced in the original gps.conf file for Telus phones.
SUPL_TLS_HOST=supl.telusmobility.com
SUPL_TLS_CERT=/etc/SuplRootCert
I am hoping it might help with the GPS issues. If you could pull it and post it, I would be very grateful.
Click to expand...
Click to collapse
No such file or directory.
Juggalo_X said:
No such file or directory.
Click to expand...
Click to collapse
Hmmmm... And it's referenced in the config file. Oh, well...
Thanks for checking!
marinierb said:
Hmmmm... And it's referenced in the config file. Oh, well...
Thanks for checking!
Click to expand...
Click to collapse
probably fragment from files long lost lol
Hi, developers.
We are trying to port the new Android 4.1 aka Jelly Bean on our devices.
So far, we have integrated ICS libs and system files with the JB ones.
Now we are compiling the kernel for making it running on our OLD-BUT-FAST device.
It's only a matter of time.
Devs who are working on this:
- capez ----> Team Android Jelly Bean
- mkalter ----> Team Android Jelly Bean
- b-eock
- DerTeufel1980
- Stratosk
- randomblame
- nasif
- ali1276
- DarknessWarrior
P.S.
Sorry if i'm not always here helping, but Thursday morning i have my final oral test of Maturiry exam, so atm and the next few days i'll be absorbed into study.
Thank you for your understanding,
capez
Now booting
What we've done until now:
Ported from Galxy Nexus:
- /system/app
- changed bluetooth, wifi, gps in /system/etc
- fonts, framework, media, tts, usr, xbin
- copyed busybox from CM9
- Edited build.prop
- Added some missing files in /system/bin
- Added libs
- Updated kernel with JB .rcs
Problems:
- Solve device encryption after boot
maybe this would help in editing boot.img
http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
I've messaged with Faryaab, the developer who ported JB to Galaxy s3 (http://forum.xda-developers.com/showthread.php?t=1737449), and it seems that the problem of unpacking boot.img exists in both galaxy s and galaxy s2.
We are trying to solve it.
picard666 said:
maybe this would help in editing boot.img
http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
Click to expand...
Click to collapse
Thank you. I already have seen it, but it isn't working, because the structure of the boot.img fo some old samsung devices is different from other boot.img.
However we are searching a solution.
try this http://forum.xda-developers.com/showthread.php?t=1630130
srvi12 said:
try this http://forum.xda-developers.com/showthread.php?t=1630130
Click to expand...
Click to collapse
Tried: it isn't working...at least for us. I tried to unpack the boot.img of a Jelly bean ported Rom for Iconia, and the unpacking was succesful.
For now the only problem is unpacking this ICS boot.img and i tried every method existing on google without success
Hi,
it's impossible to do that with dsixda kitchen ? ( In Advanced option )
powerdams said:
Hi,
it's impossible to do that with dsixda kitchen ? ( In Advanced option )
Click to expand...
Click to collapse
I tried and it isn't working; it gives this output:
"Android Magic not found in ./boot.img. Giving up.
gzip: ../../boot.img-ramdisk.gz: No such file or directory
cpio: premature end of archive"
capez said:
I tried and it isn't working; it gives this output:
"Android Magic not found in ./boot.img. Giving up.
gzip: ../../boot.img-ramdisk.gz: No such file or directory
cpio: premature end of archive"
Click to expand...
Click to collapse
do you dwonload the cipo & perl package?
srvi12 said:
do you dwonload the cipo & perl package?
Click to expand...
Click to collapse
There is everything, because for other boot.img from other devices it worked
Im not developer but i just wonder can this jb use boot.img from ics?
sending from the beast wearing AOKP beuty
Im not developer but i just wonder can this jb use boot.img from ics?
Click to expand...
Click to collapse
Thought about the same ;D
saphirrot said:
Thought about the same ;D
Click to expand...
Click to collapse
I will try
capez said:
I will try
Click to expand...
Click to collapse
Tried: adb logcat gives this error:
- exec '/system/bin/sh' failed: No such file or directory (2) -
I'm trying to solve this; maybe it will work without modifying ramdisk (i don't think so)
holy, what now ? Does it boot up ? ^^
saphirrot said:
holy, what now ? Does it boot up ? ^^
Click to expand...
Click to collapse
No, but i'm near to the boot
Holy Moly! Working on Jelly Bean already?
You guys are amazing...I didn't think I'd ever get ICS on my SGS, let alone Jelly Bean!
Good works guys! Can't wait to see how this pans out!
Thanks
IG =]
capez said:
Tried: adb logcat gives this error:
- exec '/system/bin/sh' failed: No such file or directory (2) -
I'm trying to solve this; maybe it will work without modifying ramdisk (i don't think so)
Click to expand...
Click to collapse
Try putting http://db.tt/kukVGi4z that file in system/bin. It is a file named sh I got out of my system/bin. Maybe that is what the kernel is looking for.
capez said:
No, but i'm near to the boot
Click to expand...
Click to collapse
nice to hear...really cant wait to port it to sgs...
***OFFICIAL THREAD FOR THIS ISSUE FOR THE OPTIMUS G PRO E980***
I have the necessary APKs and other files to make a flashable zip, however whenever I try to flash it it succeeds but when I click on quickremote, the app force closes on me and will not load. How can we successfully get this to work on lollipop? I have posted several times in the forums but nobody seems to care about helping get this done.
Here is a the link to my pasted logcat relating to this error. I uploaded it to pastebin.
http://pastebin.com/1GhY8b3T
rjmxtech said:
I have the necessary APKs and other files to make a flashable zip, however whenever I try to flash it it succeeds but when I click on quickremote, the app force closes on me and will not load. How can we successfully get this to work on lollipop? I have posted several times in the forums but nobody seems to care about helping get this done.
Click to expand...
Click to collapse
Take a logcat and see what's in there (use google, to search how to do that. )
Sunandroid said:
Take a logcat and see what's in there (use google, to search how to do that. )
Click to expand...
Click to collapse
I sent you a PM
wow, this is proving to be just as uneventful as it sounds.... dude, if you're going to ask for or write a guide, make its own thread.
berryman13 said:
wow, this is proving to be just as uneventful as it sounds.... dude, if you're going to ask for or write a guide, make its own thread.
Click to expand...
Click to collapse
I replied to one of your posts on another thread. @Snepsts and I are attempting to figure this out at the moment through PM's and such. I will make a thread for it if we get anywhere with it.
I pasted a logcat on pastebin and put the link in the OP
Are you sure, you got all files? Odex file? Another part of the apk? Set the right permissions? Do you use a custom screen density?
Sunandroid said:
Are you sure, you got all files? Odex file? Another part of the apk? Set the right permissions? Do you use a custom screen density?
Click to expand...
Click to collapse
Check your inbox BTW. I just sent you a message.
Code:
03-02 12:34:40.312 E/AndroidRuntime(4334): java.lang.NoClassDefFoundError: Failed resolution
by: java.lang.ClassNotFoundException: Didn't find class "com.lge.systemservice.core.LGContext" on path: DexPathList[[zip file "/system/app/LGQRemote.apk"],nativeLibraryDirectories=[/vendor/lib, /system/lib]]
First is why I asked about density. Try it out with stock density of the G3
2nd: Those are the patha I'd go diggin. Maybe gonna explain a bit closer/have a closer look tomorrow. Got to sleep now.^^
Amything new here? Have you already searched in the fokders I "mentioned"?
I'm back and trying to get this working once more. It is so odd that the way they got this working on the G2 and G3 does not work on ours. It makes me think that the stock LG ROM with lollipop for the G Pro is just a bunch of hacks LG threw into a zip file which just makes this even more difficult. I'm not going to give up yet though. If anyone else has any suggestions please PM me. I would gladly appreciate more ideas.
---
rjmxtech said:
---
Click to expand...
Click to collapse
As already asked, what was the results of digging in the directories I mentioned. And better don't take this to PMs...
Sunandroid said:
As already asked, what was the results of digging in the directories I mentioned. And better don't take this to PMs...
Click to expand...
Click to collapse
I'm pretty sure I tried it and it didn't work but I will give it another go
@Sunandroid, how can I get the odex files without installing the ROM myself. Is there a way to accomplish this?
rjmxtech said:
@Sunandroid, how can I get the odex files without installing the ROM myself. Is there a way to accomplish this?
Click to expand...
Click to collapse
Not sure, but it should be doable by unpacking the roms zip.
Sunandroid said:
Not sure, but it should be doable by unpacking the roms zip.
Click to expand...
Click to collapse
I am pretty sure the odex files are generated when the ROM is installed. This means I need to have someone who has the ROM working to get them to me.. The zip only has the files from the system partition.
rjmxtech said:
I am pretty sure the odex files are generated when the ROM is installed. This means I need to have someone who has the ROM working to get them to me.. The zip only has the files from the system partition.
Click to expand...
Click to collapse
Yeah, and the odes files usually are in system partition. Post a link to the ROM, you want to ectract the remote from, please. Gonna dig in there next weekend if O got the time.
Sunandroid said:
Yeah, and the odes files usually are in system partition. Post a link to the ROM, you want to ectract the remote from, please. Gonna dig in there next weekend if O got the time.
Click to expand...
Click to collapse
Here is the link to the ROM's thread. http://forum.xda-developers.com/showthread.php?t=3043779
Just bumping this up. I have had no luck with it at all. Need help from others.
I am trying to compile LOS 15.1 for my H815 using @kessaras's G4 files from AOSCP, and it broke during the kernel creation.
I looked at the error, and just commented out the line causing it (inside the g4-common/sepolicy/sysinit.te, it was saying unknown type sysinit), and surprisingly it has carried on building. Are there any chances that this could break my phone permanently when I flash it (assuming the build completes)
ThePiGuy said:
I am trying to compile LOS 15.1 for my H815 using @kessaras's G4 files from AOSCP, and it broke during the kernel creation.
I looked at the error, and just commented out the line causing it (inside the g4-common/sepolicy/sysinit.te, it was saying unknown type sysinit), and surprisingly it has carried on building. Are there any chances that this could break my phone permanently when I flash it (assuming the build completes)
Click to expand...
Click to collapse
Which branch of titan are you using?
If something goes wrong it just soft bricks so you will still have TWRP and download mode.
Sent from my LG-H815 using XDA Labs
steadfasterX said:
Which branch of titan are you using?
Click to expand...
Click to collapse
To be honest, I have no idea. I just took the AOSCP device_lge_g4-common, device_lge_h815 and kernel_lge_msm8992 repos and modified them to point to the correct lineage directories instead of AOSCP
steadfasterX said:
If something goes wrong it just soft bricks so you will still have TWRP and download mode.
Click to expand...
Click to collapse
Thanks for confirming this. Its what I thought, and then I came across a forum saying the wrong kernel can hard brick your device
ThePiGuy said:
To be honest, I have no idea. I just took the AOSCP device_lge_g4-common, device_lge_h815 and kernel_lge_msm8992 repos and modified them to point to the correct lineage directories instead of AOSCP
Thanks for confirming this. Its what I thought, and then I came across a forum saying the wrong kernel can hard brick your device
Click to expand...
Click to collapse
Yea ppl often don't know much about the correct brick terms..
So where do you take the repos from? From our suicide org?
Ensure you checkout the oreo branch! For all repos!
git checkout
Sent from my LG-H815 using XDA Labs
steadfasterX said:
Yea ppl often don't know much about the correct brick terms..
So where do you take the repos from? From our suicide org?
Ensure you checkout the oreo branch! For all repos!
git checkout
Click to expand...
Click to collapse
I got them from github.com/cypheros/[reponame] and I obtained them by adding them to the local_manifest (with oreo-mr1-release as the revision) and repo syncing
steadfasterX said:
Yea ppl often don't know much about the correct brick terms..
So where do you take the repos from? From our suicide org?
Ensure you checkout the oreo branch! For all repos!
git checkout
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
I have now tried building the kernel separately from the main android build process (both with suicide squirrel and official AOSCP sources), and It has finished by dumping the files "Image", "Image.gz" and "Image.gz-dtb" in the arch/arm/arm64/boot folder. Are these the files we are supposed to get (I thought we were supposed to get a zImage file)?
Also, it ended with the errors
/home/thepiguy/kernel/kernel/scripts/Makefile.fwinst:45: target '/lib/firmware/sic/p1/L0L55P1_1_11.img' given more than once in the same rule
/home/thepiguy/kernel/kernel/scripts/Makefile.fwinst:45: target '/lib/firmware/sic/p1/p1_limit_mfts_flat.txt' given more than once in the same rule
/home/thepiguy/kernel/kernel/scripts/Makefile.fwinst:45: target '/lib/firmware/sic/p1/p1_limit.txt' given more than once in the same rule
/home/thepiguy/kernel/kernel/scripts/Makefile.fwinst:45: target '/lib/firmware/sic/p1/p1_limit_mfts_curved.txt' given more than once in the same rule
/home/thepiguy/kernel/kernel/scripts/Makefile.fwinst:45: target '/lib/firmware/sic/p1/p1_limit_mfts_folder.txt' given more than once in the same rule
CAT arch/arm64/boot/Image.gz-dtb
I have copied the full terminal output on hastebin if it helps (https://hastebin.com/regeqaqiva.rb)
@steadfasterX, have I done something obviously wrong?
ThePiGuy said:
I have now tried building the kernel separately from the main android build process (both with suicide squirrel and official AOSCP sources), and It has finished by dumping the files "Image", "Image.gz" and "Image.gz-dtb" in the arch/arm/arm64/boot folder. Are these the files we are supposed to get (I thought we were supposed to get a zImage file)?
Also, it ended with the errors
/home/thepiguy/kernel/kernel/scripts/Makefile.fwinst:45: target '/lib/firmware/sic/p1/L0L55P1_1_11.img' given more than once in the same rule
/home/thepiguy/kernel/kernel/scripts/Makefile.fwinst:45: target '/lib/firmware/sic/p1/p1_limit_mfts_flat.txt' given more than once in the same rule
/home/thepiguy/kernel/kernel/scripts/Makefile.fwinst:45: target '/lib/firmware/sic/p1/p1_limit.txt' given more than once in the same rule
/home/thepiguy/kernel/kernel/scripts/Makefile.fwinst:45: target '/lib/firmware/sic/p1/p1_limit_mfts_curved.txt' given more than once in the same rule
/home/thepiguy/kernel/kernel/scripts/Makefile.fwinst:45: target '/lib/firmware/sic/p1/p1_limit_mfts_folder.txt' given more than once in the same rule
CAT arch/arm64/boot/Image.gz-dtb
I have copied the full terminal output on hastebin if it helps (https://hastebin.com/regeqaqiva.rb)
Click to expand...
Click to collapse
Don't know about the txt failures. The image.gz-dtb is your zImage. It's the zImage with appended dtb
So does it boot or not?
Sent from my LG-H815 using XDA Labs
steadfasterX said:
Don't know about the txt failures. The image.gz-dtb is your zImage. It's the zImage with appended dtb
So does it boot or not?
Click to expand...
Click to collapse
This kept causing the android build to fail. I'll see if I can build android using that zimage as a prebuilt kernel
FYI moving this to the Help & Troubleshooting section
ThePiGuy said:
I have now tried building the kernel separately from the main android build process (both with suicide squirrel and official AOSCP sources), and It has finished by dumping the files "Image", "Image.gz" and "Image.gz-dtb" in the arch/arm/arm64/boot folder. Are these the files we are supposed to get (I thought we were supposed to get a zImage file)?
Also, it ended with the errors
/home/thepiguy/kernel/kernel/scripts/Makefile.fwinst:45: target '/lib/firmware/sic/p1/L0L55P1_1_11.img' given more than once in the same rule
/home/thepiguy/kernel/kernel/scripts/Makefile.fwinst:45: target '/lib/firmware/sic/p1/p1_limit_mfts_flat.txt' given more than once in the same rule
/home/thepiguy/kernel/kernel/scripts/Makefile.fwinst:45: target '/lib/firmware/sic/p1/p1_limit.txt' given more than once in the same rule
/home/thepiguy/kernel/kernel/scripts/Makefile.fwinst:45: target '/lib/firmware/sic/p1/p1_limit_mfts_curved.txt' given more than once in the same rule
/home/thepiguy/kernel/kernel/scripts/Makefile.fwinst:45: target '/lib/firmware/sic/p1/p1_limit_mfts_folder.txt' given more than once in the same rule
CAT arch/arm64/boot/Image.gz-dtb
I have copied the full terminal output on hastebin if it helps (https://hastebin.com/regeqaqiva.rb)
Click to expand...
Click to collapse
I have endeavoured to build the H812 UsU LineageOS 15.1 (for general interest and to gain a better understanding of what the build process entails) and have encountered the same text errors as you ran into:
/home/s/Desktop/LineageOS/kernel/lge/msm8992/scripts/Makefile.fwinst:45: target '/lib/firmware/sic/p1/L0L55P1_1_11.img' given more than once in the same rule
/home/s/Desktop/LineageOS/kernel/lge/msm8992/scripts/Makefile.fwinst:45: target '/lib/firmware/sic/p1/p1_limit.txt' given more than once in the same rule
/home/s/Desktop/LineageOS/kernel/lge/msm8992/scripts/Makefile.fwinst:45: target '/lib/firmware/sic/p1/p1_limit_mfts_curved.txt' given more than once in the same rule
/home/s/Desktop/LineageOS/kernel/lge/msm8992/scripts/Makefile.fwinst:45: target '/lib/firmware/sic/p1/p1_limit_mfts_flat.txt' given more than once in the same rule
/home/s/Desktop/LineageOS/kernel/lge/msm8992/scripts/Makefile.fwinst:45: target '/lib/firmware/sic/p1/p1_limit_mfts_folder.txt' given more than once in the same rule
make: Leaving directory '/home/s/Desktop/LineageOS/kernel/lge/msm8992'
ninja: build stopped: subcommand failed.
16:10:27 ninja failed with: exit status 1
You obviously overcame this but I'm wondering how you solved it ultimately? Was it just as you stated in the OP?
I looked at the error, and just commented out the line causing it (inside the g4-common/sepolicy/sysinit.te, it was saying unknown type sysinit)
Did you get to the bottom of the issue finally?
Appreciate any direction/solutions you can provide here.
Thanks,
S.
sdembiske said:
I have endeavoured to build the H812 UsU LineageOS 15.1 (for general interest and to gain a better understanding of what the build process entails) and have encountered the same text errors as you ran into:
/home/s/Desktop/LineageOS/kernel/lge/msm8992/scripts/Makefile.fwinst:45: target '/lib/firmware/sic/p1/L0L55P1_1_11.img' given more than once in the same rule
/home/s/Desktop/LineageOS/kernel/lge/msm8992/scripts/Makefile.fwinst:45: target '/lib/firmware/sic/p1/p1_limit.txt' given more than once in the same rule
/home/s/Desktop/LineageOS/kernel/lge/msm8992/scripts/Makefile.fwinst:45: target '/lib/firmware/sic/p1/p1_limit_mfts_curved.txt' given more than once in the same rule
/home/s/Desktop/LineageOS/kernel/lge/msm8992/scripts/Makefile.fwinst:45: target '/lib/firmware/sic/p1/p1_limit_mfts_flat.txt' given more than once in the same rule
/home/s/Desktop/LineageOS/kernel/lge/msm8992/scripts/Makefile.fwinst:45: target '/lib/firmware/sic/p1/p1_limit_mfts_folder.txt' given more than once in the same rule
make: Leaving directory '/home/s/Desktop/LineageOS/kernel/lge/msm8992'
ninja: build stopped: subcommand failed.
16:10:27 ninja failed with: exit status 1
You obviously overcame this but I'm wondering how you solved it ultimately? Was it just as you stated in the OP?
I looked at the error, and just commented out the line causing it (inside the g4-common/sepolicy/sysinit.te, it was saying unknown type sysinit)
Did you get to the bottom of the issue finally?
Appreciate any direction/solutions you can provide here.
Thanks,
S.
Click to expand...
Click to collapse
So...the conclusion I came to was that those are warnings but not errors.
If you have a full ROM build where it works, if you look closely those still appear and then the build continues as normal
If you post the full build log I can see if I can find the problem (I would imagine the error is above those)
ThePiGuy said:
So...the conclusion I came to was that those are warnings but not errors.
If you have a full ROM build where it works, if you look closely those still appear and then the build continues as normal
If you post the full build log I can see if I can find the problem (I would imagine the error is above those)
Click to expand...
Click to collapse
Just doing another build - if the error still appears, I'll post the full log. If it doesn't I'll indicate what I tried.
Thank you, appreciate it.
S.
ThePiGuy said:
So...the conclusion I came to was that those are warnings but not errors.
If you have a full ROM build where it works, if you look closely those still appear and then the build continues as normal
If you post the full build log I can see if I can find the problem (I would imagine the error is above those)
Click to expand...
Click to collapse
The build failed with the same errors - I pulled off all I could off the terminal. If you have a specific log(s) in mind, please let me know.
Link: https://pastebin.com/3T1GTFQG
I'm really not sure where the build error is arising. I am running a full build make for the H812 UsU using
brunch lineage_h812_usu-userdebug
Thanks again,
S.
sdembiske said:
The build failed with the same errors - I pulled off all I could off the terminal. If you have a specific log(s) in mind, please let me know.
Link: https://pastebin.com/3T1GTFQG
I'm really not sure where the build error is arising. I am running a full build make for the H812 UsU using
brunch lineage_h812_usu-userdebug
Thanks again,
S.
Click to expand...
Click to collapse
Ok so unfortunately I don't think that log goes up high enough (it is the log I am looking for though)
See if you can increase the terminal scroll back size and/or use a method like piping to "tee" to save the output to a file as well
ThePiGuy said:
Ok so unfortunately I don't think that log goes up high enough (it is the log I am looking for though)
See if you can increase the terminal scroll back size and/or use a method like piping to "tee" to save the output to a file as well
Click to expand...
Click to collapse
OK - here you go:
Link: https://pastebin.com/QGWqLAJg
Didn't realize there was a setting in the terminal preferences to increase scroll back length to infinite.
I haven't spotted as yet anything that stands out in the log, so would appreciate you going through it.
Thanks again,
S.
Addendum: Found it, I believe @ThePiGuy
FAILED: /home/s/Desktop/LineageOS/out/target/product/h812_usu/obj/STATIC_LIBRARIES/libedify_intermediates/lexer.cpp
/bin/bash -c "prebuilts/misc/linux-x86/flex/flex-2.5.39 -o/home/steve/Desktop/LineageOS/out/target/product/h812_usu/obj/STATIC_LIBRARIES/libedify_intermediates/lexer.cpp bootable/recovery/edify/lexer.ll"
flex-2.5.39: loadlocale.c:130: _nl_intern_locale_data: Assertion `cnt < (sizeof (_nl_value_type_LC_TIME) / sizeof (_nl_value_type_LC_TIME[0]))' failed.
Aborted (core dumped)
sdembiske said:
OK - here you go:
Link: https://pastebin.com/QGWqLAJg
Didn't realize there was a setting in the terminal preferences to increase scroll back length to infinite.
I haven't spotted as yet anything that stands out in the log, so would appreciate you going through it.
Thanks again,
S.
Addendum: Found it, I believe @ThePiGuy
FAILED: /home/s/Desktop/LineageOS/out/target/product/h812_usu/obj/STATIC_LIBRARIES/libedify_intermediates/lexer.cpp
/bin/bash -c "prebuilts/misc/linux-x86/flex/flex-2.5.39 -o/home/steve/Desktop/LineageOS/out/target/product/h812_usu/obj/STATIC_LIBRARIES/libedify_intermediates/lexer.cpp bootable/recovery/edify/lexer.ll"
flex-2.5.39: loadlocale.c:130: _nl_intern_locale_data: Assertion `cnt < (sizeof (_nl_value_type_LC_TIME) / sizeof (_nl_value_type_LC_TIME[0]))' failed.
Aborted (core dumped)
Click to expand...
Click to collapse
Yep that's exactly what I found
I encountered this error when I began building - it's because Oreo requires an older version of this flex library (or something along those lines)
Run "export LC_ALL=C" before building - that should fix it
ThePiGuy said:
Yep that's exactly what I found
I encountered this error when I began building - it's because Oreo requires an older version of this flex library (or something along those lines)
Run "export LC_ALL=C" before building - that should fix it
Click to expand...
Click to collapse
Yes, just was about to do that as that seemed to be the recommended solution when I searched the error. Seems it cropped up in newer version of ubuntu-based linux versions.
Sorry I troubled you with this - if I had managed to scroll back far enough in the first place, I might have found it ...
Cheers & Thanks again.
S.
sdembiske said:
Yes, just was about to do that as that seemed to be the recommended solution when I searched the error. Seems it cropped up in newer version of ubuntu-based linux versions.
Sorry I troubled you with this - if I had managed to scroll back far enough in the first place, I might have found it ...
Cheers & Thanks again.
S.
Click to expand...
Click to collapse
No worries
I think I asked enough of these questions when I was learning (including this exact one) so I absolutely don't mind answering them too
Hi all,
I am new to study the android. Right now, I faced a problem that the build would be failed at:
Running extra build command(s):
+ eval python build/buildinfo/buildinfo.py
++ python build/buildinfo/buildinfo.py
python: can't open file 'build/buildinfo/buildinfo.py': [Errno 2] No such file or directory
I noticed that there is a command line in the build.config: "EXTRA_CMDS='python build/buildinfo/buildinfo.py'". How the buildinfo folder be created? How can I solve this problem, thanks.
me too
Adlismon said:
Hi all,
I am new to study the android. Right now, I faced a problem that the build would be failed at:
Running extra build command(s):
+ eval python build/buildinfo/buildinfo.py
++ python build/buildinfo/buildinfo.py
python: can't open file 'build/buildinfo/buildinfo.py': [Errno 2] No such file or directory
I noticed that there is a command line in the build.config: "EXTRA_CMDS='python build/buildinfo/buildinfo.py'". How the buildinfo folder be created? How can I solve this problem, thanks.
Click to expand...
Click to collapse
ucantseeme said:
me too
Click to expand...
Click to collapse
i can not tell if you 2 are the same person, trying to make this issue look popular or something. ucantseeme was made today and has 1 post, OP has 1 post but account was made a few months ago.
Either way, just now i synced the repo, and built the kernel after removing the "EXTRA_CMDS='python build/buildinfo/buildinfo.py'" line from build.config and it works just fine, booted to it while i am writing this.
sudoxd said:
i can not tell if you 2 are the same person, trying to make this issue look popular or something. ucantseeme was made today and has 1 post, OP has 1 post but account was made a few months ago.
Either way, just now i synced the repo, and built the kernel after removing the "EXTRA_CMDS='python build/buildinfo/buildinfo.py'" line from build.config and it works just fine, booted to it while i am writing this.
Click to expand...
Click to collapse
Hi Sudoxd,
Thanks for your feedback. I am the creator of this topic and I don't know the "ucantseeme". Currently, I don't solve this compile error issue, but I do successfully to get the kernel image(Image.lz4) where is located at out/android-msm-xxx-xx.xx/private/msm-google/arch/arm64/boot/. I guess the function of buildinfo.py should be only to move the files to the target folder.
Adlismon said:
Hi Sudoxd,
Thanks for your feedback. I am the creator of this topic and I don't know the "ucantseeme". Currently, I don't solve this compile error issue, but I do successfully to get the kernel image(Image.lz4) where is located at out/android-msm-xxx-xx.xx/private/msm-google/arch/arm64/boot/. I guess the function of buildinfo.py should be only to move the files to the target folder.
Click to expand...
Click to collapse
The files are all outputted where they are meant to be (/out/android.../dist) already, and the image.lz4 is the normal output. If yours outputs elsewhere I would sync, delete the buildinfo line and rebuild in a new directory and see what happens.
sudoxd said:
i can not tell if you 2 are the same person, trying to make this issue look popular or something. ucantseeme was made today and has 1 post, OP has 1 post but account was made a few months ago.
Either way, just now i synced the repo, and built the kernel after removing the "EXTRA_CMDS='python build/buildinfo/buildinfo.py'" line from build.config and it works just fine, booted to it while i am writing this.
Click to expand...
Click to collapse
thank you, thank you
I solved it