Error building a rom - Galaxy Ace II Q&A, Help & Troubleshooting

Hello, when i try to build Resurrection Remix (i have the correct sources) give this error
host StaticLib: libzipfile (/home/ol100/RR/out/host/linux-x86/obj/STATIC_LIBRARIES/libzipfile_intermediates/libzipfile.a)
make: *** No hay ninguna regla para construir el objetivo «vendor/cm/proprietary/lib/armeabi/libjackpal-androidterm4.so», necesario para «/home/ol100/RR/out/target/product/codina/system/lib/libjackpal-androidterm4.so». Alto.
make: *** Se espera a que terminen otras tareas....
host SharedLib: libSR_G2P (/home/ol100/RR/out/host/linux-x86/obj/lib/libSR_G2P.so)
[email protected] ~/RR $
Screenshot
http://imgur.com/MYKwVgC
Any idea for a solution?

1. Not this section
2. cd vendor/cm; ./get-prebuilds

jereksel said:
1. Not this section
2. cd vendor/cm; ./get-prebuilds
Click to expand...
Click to collapse
1.ok
2../get prebuilds in terminal doesn't do anything.

rol525 said:
1.ok
2../get prebuilds in terminal doesn't do anything.
Click to expand...
Click to collapse
I see you're trying to compile ResurrectionRemix, am I right? You should compile it with included script (build-rr.sh).

jereksel said:
I see you're trying to compile ResurrectionRemix, am I right? You should compile it with included script (build-rr.sh).
Click to expand...
Click to collapse
Yes. ResurrectionRemix, Codina userdebug or eng?

rol525 said:
Yes. ResurrectionRemix, Codina userdebug or eng?
Click to expand...
Click to collapse
userdebug

Building, thanks for your help.
But the rom didn´t have OMX, right?

Are You using TC sources or Macław?
Sent from my GT-I8160 using XDA Premium 4 mobile app

rol525 said:
Building, thanks for your help.
But the rom didn´t have OMX, right?
Click to expand...
Click to collapse
If you don't patch it, it won't have OMX.

I´m using TC sources, if build is ok, Then it will not have OMX.

So sad. So are You going to patch it in near feature?
Sent from my GT-I8160 using XDA Premium 4 mobile app

Why tehre will be no OMX owrking ??
All 4.4 patches :
Patches for OMX and various bugs :
Native patch : https://github.com/TeamCanjica/andr...mmit/d9dd39ca7935c16a34ce8b3e8c00dd6bae680d49
Av patch : https://github.com/TeamCanjica/android_frameworks_av/commit/803bb5dd145630c0239a61bd4d58c3728f2dba57
Core patch : https://github.com/TeamCanjica/android_system_core/commit/7bd81ee140c09066ede2ffab47da1a1c4e54e021
Base patch : https://github.com/TeamCanjica/andr...mmit/3826055d49ec70ab3d0e130a8e444fd334806fa5
Fix for shutdown/reboot bug : https://github.com/TeamCanjica/android_system_core/commit/b6cb91b1f70c969bb0f818a24111c0ca055be590
Patch for swapping storages : http://review.cyanogenmod.org/#/c/56515/
Patch for ART : https://github.com/cernekee/android_art/commit/fc2ac71d0d9e147c607bff9371fe2ef25d8470af
Use this device trees :
https://github.com/TeamCanjica/android_device_samsung_codina/tree/cm-11.0
https://github.com/TeamCanjica/android_device_samsung_u8500-common/tree/cm.11.0
This kernel ( for now ) :
https://github.com/TeamCanjica/android_kernel_samsung_codina/tree/cm-11.0
And this vendor files:
https://github.com/TeamCanjica/android_vendor_samsung_u8500-common/tree/cm-11.0
Good luck

I use this:
<project path="vendor/samsung/u8500-common" name="TeamCanjica/android_vendor_samsung_u8500-common" revision="cm-11.0" />
<project path="device/samsung/u8500-common" name="TeamCanjica/android_device_samsung_u8500-common" revision="cm-11.0" />
<project path="hardware/u8500" name="TeamCanjica/android_hardware_u8500" revision="cm-11.0" />
<project path="device/samsung/codina" name="TeamCanjica/android_device_samsung_codina" revision="cm-11.0" />
<project path="kernel/samsung/codina" name="TeamCanjica/android_kernel_samsung_codina" revision="cm-11.0" />

That is good. But you will need skme changes specific for RR ROM.
For omx: Cherrypick patches i posted up there.
Sent from my GT-I8160 using Tapatalk

Rox said:
That is good. But you will need skme changes specific for RR ROM.
For omx: Cherrypick patches i posted up there.
Sent from my GT-I8160 using Tapatalk
Click to expand...
Click to collapse
Ok, tomorrow i try. Now i´m building for see if there are any error.

I get this error in the final:
make[4]: *** [arch/arm/boot/compressed/vmlinux] Error 1
make[3]: *** [arch/arm/boot/compressed/vmlinux] Error 2
make[2]: *** [zImage] Error 2
make[1]: *** [sub-make] Error 2
make[1]: se sale del directorio «/home/ol100/RR/kernel/samsung/codina»
make: *** [TARGET_KERNEL_BINARIES] Error 2
make: *** Se espera a que terminen otras tareas....
Preparing output jar [/home/ol100/RR/out/target/common/obj/APPS/Keyguard_intermediates/proguard.classes.jar]
Copying resources from program jar [/home/ol100/RR/out/target/common/obj/APPS/Keyguard_intermediates/classes.jar]
Total time elapsed: 191 minutes (11476.601262499 seconds)
============ RESURRECTION REMIX ROM ® KITKAT 4.4.+ ========
====================== ENJOY THE ROM ======================
================ WWW.RESURRECTİONREMİX.COM ================
[email protected] ~/RR $

@Rox, any idea?

Post more console log. I suggest pastebin link..

Rox said:
Post more console log. I suggest pastebin link..
Click to expand...
Click to collapse
Here: http://pastebin.com/akL6ZwFV

@Rox, is kernel related problem?

Related

CyanogenMod 9 Development

I'm working on porting CM9 to HTC One X. I've made a lot of progress but there are still issues. I wanted to get the source out as soon as possible to get more people working on it.
See the wiki for more information.
Status
Working:
Radio (calls and 3G)
Audio
Hardware Acceleration
WiFi
Bluetooth
GPS
NFC
Camera
FM Radio
Echo/In call volume fixed
Wifi Tethering
Issues/TODO list:
Wifi Direct
Blank screen on rotation
Data connection occasionally fails
Camera focusing on face issue
Nightly Builds
Thanks to jangrewe for providing the nightly builds.
Downloads: http://mirror.faked.org/cm9/
Jenkins: http://faked.org/jenkins
Reporting issues
https://github.com/intermediaterepresentation/android_device_htc_endeavor/issues
Flashing ROM
Using CWM you can flash the ROM.
The kernel must be flashed manually unless you have S-OFF:
Extract the zip file.
Code:
fastboot flash boot boot.img
Building
Add the following to your .repo/local_manifest.xml:
Code:
<project name="intermediaterepresentation/android_hardware_ti_wlan" path="hardware/ti/wlan" remote="github" revision="p-ics-mr1-release"/>
<project name="intermediaterepresentation/android_kernel_htc_endeavor" path="kernel/htc/endeavor" remote="github" revision="master" />
<project name="intermediaterepresentation/android_device_htc_endeavor" path="device/htc/endeavoru" remote="github" revision="master" />
Sync code.
Code:
repo sync
And compile:
Code:
add_lunch_combo cm_endeavoru-userdebug
lunch cm_endeavoru-userdebug
(cd device/htc/endeavoru && ./extract_files.sh)
make -j4 otapackage
Contributions
Please send me pull requests on GitHub if you want to contribute.
Sources
Device Configuration - https://github.com/intermediaterepresentation/android_device_htc_endeavor
Kernel - https://github.com/intermediaterepresentation/android_kernel_htc_endeavor
Change Log
5/19/2012 - Initial import of project
5/20/2012 - Bluetooth support added
5/20/2012 - GPS added
5/21/2012 - NFC added
5/28/2012 - Add build links
5/28/2012 - Auto brightness, ICS switcher for hardware key, and more (thanks gorbi) - https://github.com/intermediaterepresentation/android_device_htc_endeavor/pull/1
5/28/2012 - Camera is now working!
5/30/2012 -
akaspin - fix bug with editing custom backlight levels
tgascoigne - fix usb mass storage
gorbi - fix for chrome. system tweaks.
6/26/2012 - Update changelog and add wiki link
I guess someone from XDA (JDR0iD?) is also working on CM9 you might wanna ask them as well.
I thought its already out, but its only posted in the modaco forum
Sent from my HTC One X using Tapatalk 2
Good to see that someone who actually shares the open source work works on cm9 now! The guy over at modaco seems like a bit of a douche, cause he insist on not sharing his repo and as I think this shouldn't be supported because open source is about open source!
Keep up the work, I hope you can fix at least the heavy bugs like mobile connection so you can post a build
Sent from my HTC One X using XDA Premium HD app
Code:
error: revision refs/heads/ics in intermediaterepresentation/android_device_htc_endeavor not found
When syncing my repo.
Edit:
I fixed it by changing
Code:
<project name="intermediaterepresentation/android_hardware_ti_wlan" path="hardware/ti/wlan-omapzoom" remote="github" revision="p-ics-mr1-release"/>
<project name="intermediaterepresentation/android_kernel_htc_endeavor" path="kernel/htc/endeavor" remote="github" />
<project name="intermediaterepresentation/android_device_htc_endeavor" path="device/htc/endeavor" remote="github" />
to
Code:
<project name="intermediaterepresentation/android_hardware_ti_wlan" path="hardware/ti/wlan-omapzoom" remote="github" revision="p-ics-mr1-release"/>
<project name="intermediaterepresentation/android_kernel_htc_endeavor" path="kernel/htc/endeavor" remote="github" [COLOR="red"]revision="master"[/COLOR]/>
<project name="intermediaterepresentation/android_device_htc_endeavor" path="device/htc/endeavor" remote="github" [COLOR="Red"]revision="master"[/COLOR]/>
Edit 2:
Next error:
Code:
fh-mac:cm9 fh$ lunch cm_endeavor-userdebug
Looking for dependencies
Traceback (most recent call last):
File "build/tools/roomservice.py", line 150, in <module>
fetch_dependencies(repo_path)
File "build/tools/roomservice.py", line 127, in fetch_dependencies
dependencies = json.loads(dependencies_file.read())
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/json/__init__.py", line 326, in loads
return _default_decoder.decode(s)
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/json/decoder.py", line 360, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/json/decoder.py", line 378, in raw_decode
raise ValueError("No JSON object could be decoded")
ValueError: No JSON object could be decoded
** Don't have a product spec for: 'cm_endeavor'
** Do you have the right repo manifest?
endursa said:
Good to see that someone who actually shares the open source work works on cm9 now! The guy over at modaco seems like a bit of a douche, cause he insist on not sharing his repo and as I think this shouldn't be supported because open source is about open source!
Keep up the work, I hope you can fix at least the heavy bugs like mobile connection so you can post a build
Sent from my HTC One X using XDA Premium HD app
Click to expand...
Click to collapse
It is his choice, so get over it. Just be glad he is sharing his ROM with the community for free. He doesn't owe us anything. Seriously, you people are ungrateful brats
Sorry about that...looks like my cm.dependencies was empty. I put an empty JSON object in there and all is good. repo sync or pull the changes from android_device_htc_endeavor and lunch should work.
Edit 2:
Next error:
Code:
fh-mac:cm9 fh$ lunch cm_endeavor-userdebug
Looking for dependencies
Traceback (most recent call last):
File "build/tools/roomservice.py", line 150, in <module>
fetch_dependencies(repo_path)
File "build/tools/roomservice.py", line 127, in fetch_dependencies
dependencies = json.loads(dependencies_file.read())
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/json/__init__.py", line 326, in loads
return _default_decoder.decode(s)
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/json/decoder.py", line 360, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/json/decoder.py", line 378, in raw_decode
raise ValueError("No JSON object could be decoded")
ValueError: No JSON object could be decoded
** Don't have a product spec for: 'cm_endeavor'
** Do you have the right repo manifest?
Click to expand...
Click to collapse
intrepresentation said:
Sorry about that...looks like my cm.dependencies was empty. I put an empty JSON object in there and all is good. repo sync or pull the changes from android_device_htc_endeavor and lunch should work.
Click to expand...
Click to collapse
Seems to work now, thanks!
I am so happy that you have stated this. I really miss cm9 since I sold my GN. And the nightly hours of compiling for myself... Lets hope that some geniuses will help you to get it running soon. CM9 is open and has to stay open. Otherwise he uses the wrong name for the ROM.
Next one...
Code:
fh-mac:cm9 fh$ make -j4 otapackage
============================================
<...>
============================================
build/core/base_rules.mk:166: *** hardware/ti/wlan/mac80211/config: MODULE.TARGET.ETC.wpa_supplicant.conf already defined by external/wpa_supplicant_8/wpa_supplicant. Stop.
Planet X said:
I am so happy that you have stated this. I really miss cm9 since I sold my GN. And the nightly hours of compiling for myself... Lets hope that some geniuses will help you to get it running soon. CM9 is open and has to stay open. Otherwise he uses the wrong name for the ROM.
Click to expand...
Click to collapse
exactly...same goes for other devs here as well which use normal HTC builds. they create something awesome, devs asks permission from the creators if they can use their tweaks or mods in their roms and like the divas they are most of the times they say no..so tell me what is open source then. same goes for the guy who is compiling the cm9 Trip whatever his name is...android is open. and if by doing the right procedure and giving the right credits people should be helping each other out to make the community better..not worse by acting like little divas.
@OP ask a mod if you can move this thread in development cause you guys are compiling a build from source so it makes more sense if it was there instead of general..you do not lose anything by asking.. i wish you all the best cause cm9 is by far the best ICS i tried
F4M0U569 said:
It is his choice, so get over it. Just be glad he is sharing his ROM with the community for free. He doesn't owe us anything. Seriously, you people are ungrateful brats
Click to expand...
Click to collapse
No, he doesn't owe us anything, but he has said things on the modaco thread that I dislike, whilst it is nice that he has released it to the community, he has not acknowledged that he is only modifying the work of other people, it is not just his work and so his attitude doesn't seem brilliant. He isn't selling his work, so releasing the source code wouldn't be detrimental to him and would help many people.
empyyy said:
Next one...
Code:
fh-mac:cm9 fh$ make -j4 otapackage
============================================
<...>
============================================
build/core/base_rules.mk:166: *** hardware/ti/wlan/mac80211/config: MODULE.TARGET.ETC.wpa_supplicant.conf already defined by external/wpa_supplicant_8/wpa_supplicant. Stop.
Click to expand...
Click to collapse
Let's try changing this in local_manifest.xml:
Code:
<project name="intermediaterepresentation/android_hardware_ti_wlan" path="hardware/ti/wlan-omapzoom" remote="github" revision="p-ics-mr1-release"/>
to
Code:
<project name="intermediaterepresentation/android_hardware_ti_wlan" path="hardware/ti/wlan" remote="github" revision="p-ics-mr1-release"/>
Remove the old one hardware/ti/wlan-omapzoom.
Code:
rm -rf hardware/ti/wlan-omapzoom
Now sync and you'll get hardware/ti/wlan updated and also I just changed something in device/htc/endeavor too.
See if that works.
intrepresentation said:
See if that works.
Click to expand...
Click to collapse
It works now and starts building, however, I'm getting the following error now:
Code:
external/zlib/x86/adler32.c: In function ‘adler32_MMX’:
external/zlib/x86/adler32.c:747: error: can't find a register in class ‘GENERAL_REGS’ while reloading ‘asm’
external/zlib/x86/adler32.c:747: error: ‘asm’ operand has impossible constraints
make: *** [out/host/darwin-x86/obj/STATIC_LIBRARIES/libz_intermediates/adler32.o] Error 1
I think it has to do something with Mac OS...
empyyy said:
It works now and starts building, however, I'm getting the following error now:
Code:
external/zlib/x86/adler32.c: In function ‘adler32_MMX’:
external/zlib/x86/adler32.c:747: error: can't find a register in class ‘GENERAL_REGS’ while reloading ‘asm’
external/zlib/x86/adler32.c:747: error: ‘asm’ operand has impossible constraints
make: *** [out/host/darwin-x86/obj/STATIC_LIBRARIES/libz_intermediates/adler32.o] Error 1
I think it has to do something with Mac OS...
Click to expand...
Click to collapse
Yeah it probably does. I am on Mac but I do my building on an Ubuntu VM. You can get VirtualBox for free if you need some VM software.
Hi, thanks a lot for sharing your sources!
I'm currently trying to build them, but the extract_files.sh already gives me a lot of missing objects - i'm trying to copy them off of a phone that's running an old build by TripNRaver.
here's the output: http://pastebin.com/vGS5gZq7
Is that "bad"? Should i go back to stock and try to copy them then?
cens0r said:
Hi, thanks a lot for sharing your sources!
I'm currently trying to build them, but the extract_files.sh already gives me a lot of missing objects - i'm trying to copy them off of a phone that's running an old build by TripNRaver.
here's the output: http://pastebin.com/vGS5gZq7
Is that "bad"? Should i go back to stock and try to copy them then?
Click to expand...
Click to collapse
Yeah run against stock. I may have some additional files that are not needed but run against stock to be safe.
intrepresentation said:
Yeah run against stock. I may have some additional files that are not needed but run against stock to be safe.
Click to expand...
Click to collapse
Thanks, i'll do that shortly. The compiling is running smoothly currently, good job so far!
Okay, mobile data is now working! Had to add this into build.prop:
Code:
ro.telephony.ril.v3=signalstrength,skipbrokendatacall
intrepresentation said:
Okay, mobile data is now working! Had to add this into build.prop:
Code:
ro.telephony.ril.v3=signalstrength,skipbrokendatacall
Click to expand...
Click to collapse
building now... got the proprietary files from the unbranded EU 1.29 RUU
EDIT: hitting an error:
in function wpa_driver_nl80211_ops:driver_nl80211.c(.data.rel.ro.wpa_driver_nl80211_ops+0x1c8): error: undefined reference to 'wpa_driver_nl80211_driver_cmd'
Code:
target Executable: wpa_supplicant (out/target/product/endeavor/obj/EXECUTABLES/wpa_supplicant_intermediates/LINKED/wpa_supplicant)
prebuilt/linux-x86/toolchain/arm-linux-androideabi-4.4.x/bin/../lib/gcc/arm-linux-androideabi/4.4.3/../../../../arm-linux-androideabi/bin/ld: out/target/product/endeavor/obj/EXECUTABLES/wpa_supplicant_intermediates/src/drivers/driver_nl80211.o: in function wpa_driver_nl80211_ops:driver_nl80211.c(.data.rel.ro.wpa_driver_nl80211_ops+0x1c8): error: undefined reference to 'wpa_driver_nl80211_driver_cmd'
collect2: ld returned 1 exit status
make: *** [out/target/product/endeavor/obj/EXECUTABLES/wpa_supplicant_intermediates/LINKED/wpa_supplicant] Error 1
make: *** Waiting for unfinished jobs....
EDIT 2:
add the following as line 57 in "device/htc/endeavor/BoardConfig.mk"
Code:
BOARD_WPA_SUPPLICANT_PRIVATE_LIB := lib_driver_cmd_wl12xx
EDIT 3: built & booted! looking good for a first try!

[CLK]Android 4.3.1 (CM10.2) and how to build your own version -

First you can use my source or my roms to build your own rom only say thanks in your own thread.
I like to share my way to compile Android 4.3.1 for the HTC LEO.
First thanks to mark1706, sportsstar89, evervolv team, devs that make CLK possible and tytung.
YOU CAN FIND "MY" CM-10.2 build here: DEV-HOST
Kernel soure and leo files: GITHUB
This "how to build your own Android" will work with a updated 2.6.35 kernel by mark1706. It use some parts of sportsstar89 kernel.
First setup your 64bit Linux.
I use Linux-Mint (the DEBIAN 7 based version)
You have to install Oracle Java 7: http://www.webupd8.org/2012/06/how-to-install-oracle-java-7-in-debian.html
After Java install follow this how to: https://www.techsomnia.net/2012/11/building-android-on-debian-7/
!! BUT do not install OPEN JDK (sudo apt-get install openjdk-6-jdk) !!
And stop at this point: "Now, prepare the repo:"
Next step get adb working: http://bernaerts.dyndns.org/linux/75-debian/280-debian-wheezy-android-tools-adb-fastboot-qtadb
Now we can start to sync the Android source. (based on this
To install Repo:
Make sure you have a bin/ directory in your home directory and that it is included in your path:
Code:
mkdir ~/bin
PATH=~/bin:$PATH
Download the Repo tool and ensure that it is executable:
Code:
curl [URL]http://commondatastorage.googleapis.com/git-repo-downloads/repo[/URL] > ~/bin/repo
chmod a+x ~/bin/repo
After installing Repo, set up your client to access the Android source repository:
Create an empty directory to hold your working files. If you're using MacOS, this has to be on a case-sensitive filesystem. Give it any name you like:
$ mkdir WORKING_DIRECTORY
$ cd WORKING_DIRECTORY
Run repo init to bring down the latest version of Repo with all its most recent bug fixes. You must specify a URL for the manifest, which specifies where the various repositories included in the Android source will be placed within your working directory.
Code:
repo init -u git://github.com/CyanogenMod/android.git -b cm-10.2
To pull down the Android source tree to your working directory
Code:
repo sync
We have to load the leo device tree, vendor files and the leo kernel.
Attached you find my local.xml View attachment local_manifests.zip.
Put this file at this place:
Code:
WORKING_DIRECTORY/.repo/local_manifests/...
Now sync again:
Code:
repo sync
Next you have to connect your Leo with running Android and Adb to your PC
We need to download some special files (This will fixed in future)
Go to this folder:
Code:
Working_Directory/device/htc/leo
and run the this script
Code:
sh extract_files.sh
We have to clean the kernel folder:
Go to this folder:
Code:
Working_Directory/kernel/htc/leo
and run this command
Code:
make mrproper
One step more:
Go to this folder: Working_Directory/vendor/cm
and run the this script
Code:
sh get-prebuilts
It is time to start compiling:
Make sure you are in this folder "Working_Directory"
run this commands:
Code:
. build/envsetup.sh
brunch leo
[SIZE=3]** you can use brunch leo -jX too X = numbers of cpu core (or threads) **[/SIZE]
Now wait and you will find your working Android 4.3.1 in this folder:
Working_Directory/out/target/product/leo
Problems with this Android builds:
- auto select GSM network
- mobile data not working well
- switch between wifi and mobile data
- AGPS (GPS works)
You can fix this problems by using files from tytungs NexusHD2 rom.
(AGPS, auto select GSM network)
Auto select GSM network is a telephony_common.jar framework problem.
But there are no source how it was fixed in tytungs rom. Maybe someone find a way to fix it again.
If you like to use 3.x kernel change this in local_manifest.xml:
Code:
<project path="kernel/htc/leo" name="walter79/android_kernel_htc_leo_2.6.35-mark1706-based" remote="github" revision="cm-10.2" />
to
<project path="kernel/htc/leo" name="walter79/android_kernel_htc_leo" remote="github" revision="cm-10.2" />
@walter79
- Can i use your instruction to built Slimroms for HD2??
- How to compile slimroms for HD2??
---------- Post added at 05:24 PM ---------- Previous post was at 05:17 PM ----------
walter79 said:
Auto select GSM network is a telephony_common.jar framework problem.
But there are no source how it was fixed in tytungs rom. Maybe someone find a way to fix it again.
Click to expand...
Click to collapse
You can ask Macs18max. I used telephony_common.jar of Macs18max's compile and it work great with 4.3.1!!
You can use it for slimrom but you need to edit /device/htc/leo/cm.mk. Check working devices for slimrom and you will see what changes are needed.
walter79 said:
You can use it for slimrom but you need to edit /device/htc/leo/cm.mk. Check working devices for slimrom and you will see what changes are needed.
Click to expand...
Click to collapse
Many thannks. I will try i now! I'm beginner so i will learn and learn so much more, i hope you can help me in the next time!
walter79 said:
Problems with this Android builds:
- auto select GSM network
- mobile data not working well
- switch between wifi and mobile data
- AGPS (GPS works)
You can fix this problems by using files from tytungs NexusHD2 rom.
(AGPS, auto select GSM network)
Auto select GSM network is a telephony_common.jar framework problem.
But there are no source how it was fixed in tytungs rom. Maybe someone find a way to fix it again.
If you like to use 3.x kernel change this in local_manifest.xml:
Code:
<project path="kernel/htc/leo" name="walter79/android_kernel_htc_leo_2.6.35-mark1706-based" remote="github" revision="cm-10.2" />
to
<project path="kernel/htc/leo" name="walter79/android_kernel_htc_leo" remote="github" revision="cm-10.2" />
Click to expand...
Click to collapse
I havent tried in 4.3.1 but in 4.2.2 I merge evervolvs telephony-common.jar. It was ril.java.. use meld-diff software to compare everolvs ril.java with your own. and merge required codes.. (Note I also used hardware/ril from evervolv)
big thanks. will check ril.java
Nice thread @walter79 !
I was wondering wether you ever had a similar error:
Code:
target thumb C: libhardware_legacy <= hardware/libhardware_legacy/power/power.c
target thumb C: libhardware_legacy <= hardware/libhardware_legacy/uevent/uevent.c
arm-linux-androideabi-gcc: error: ": No such file or directory
make: *** [/home/adam/android/pa43/out/target/product/leo/obj/SHARED_LIBRARIES/libhardware_legacy_intermediates/power/power.o] Error 1
make: *** Waiting for unfinished jobs....
arm-linux-androideabi-gcc: error: ": No such file or directory
make: *** [/home/adam/android/pa43/out/target/product/leo/obj/SHARED_LIBRARIES/libhardware_legacy_intermediates/uevent/uevent.o] Error 1
It has been bugging me for a week and I cannot find a solution... Do you have any idea about it? (I'm building PA 4.3)
Maybe this help try the carbon rom version.
/device/htc/qsd8k-common/BordConfigCommon.mk
Code:
# only for cyanogenmod
TARGET_KERNEL_CUSTOM_TOOLCHAIN := arm-eabi-4.4.3
# only for carbon rom
# TARGET_KERNEL_CUSTOM_TOOLCHAIN := arm-eabi-4.4.3/bin/arm-eabi-
walter79 said:
Maybe this help try the carbon rom version.
/device/htc/qsd8k-common/BordConfigCommon.mk
Code:
# only for cyanogenmod
TARGET_KERNEL_CUSTOM_TOOLCHAIN := arm-eabi-4.4.3
# only for carbon rom
# TARGET_KERNEL_CUSTOM_TOOLCHAIN := arm-eabi-4.4.3/bin/arm-eabi-
Click to expand...
Click to collapse
Thanks! Unfortunately, it's still the same. I tried it with nearly all possible toolchains...
NxStep said:
Nice thread @walter79 !
I was wondering wether you ever had a similar error:
Code:
target thumb C: libhardware_legacy <= hardware/libhardware_legacy/power/power.c
arm-linux-androideabi-gcc: error: ": No such file or directory
It has been bugging me for a week and I cannot find a solution... Do you have any idea about it? (I'm building PA 4.3)[/QUOTE]
i'd open hardware/libhardware_legacy/power/power.c to find out if any dependancy is unmet (any missing file). i've never compiled a rom myself (hoping soon i will) but for the error you're getting (i'm not sure if it's from toolchain or because of missing toolchain), maybe see if the toolchain path is hardcoded somewhere and try to change it:confused:
Click to expand...
Click to collapse
NxStep said:
Nice thread @walter79 !
I was wondering wether you ever had a similar error:
Code:
target thumb C: libhardware_legacy <= hardware/libhardware_legacy/power/power.c
target thumb C: libhardware_legacy <= hardware/libhardware_legacy/uevent/uevent.c
arm-linux-androideabi-gcc: error: ": No such file or directory
make: *** [/home/adam/android/pa43/out/target/product/leo/obj/SHARED_LIBRARIES/libhardware_legacy_intermediates/power/power.o] Error 1
make: *** Waiting for unfinished jobs....
arm-linux-androideabi-gcc: error: ": No such file or directory
make: *** [/home/adam/android/pa43/out/target/product/leo/obj/SHARED_LIBRARIES/libhardware_legacy_intermediates/uevent/uevent.o] Error 1
It has been bugging me for a week and I cannot find a solution... Do you have any idea about it? (I'm building PA 4.3)
Click to expand...
Click to collapse
Check you local.xml
I used wrong repo for toolchain. Replace it
Code:
<!-- Toolchain -->
<project path="prebuilts/gcc/linux-x86/arm" name="walter79/toolchains" remote="github" revision="master" />
I will upload later a new local.xml
mistake since two days
since yesterday i we have a compiling mistake and have no idea for this problem.
Code:
[COLOR="DarkRed"]target thumb C: wpa_supplicant <= external/wpa_supplicant_8/wpa_supplicant/src/drivers/driver_wext.c
target thumb C: wpa_supplicant <= external/wpa_supplicant_8/wpa_supplicant/src/l2_packet/l2_packet_linux.c
external/wpa_supplicant_8/wpa_supplicant/src/drivers/driver_wext.c: In function 'wpa_driver_wext_set_key_ext':
external/wpa_supplicant_8/wpa_supplicant/src/drivers/driver_wext.c:1708:14: error: 'IW_ENCODE_ALG_AES_CMAC' undeclared (first use in this function)
external/wpa_supplicant_8/wpa_supplicant/src/drivers/driver_wext.c:1708:14: note: each undeclared identifier is reported only once for each function it appears in
external/wpa_supplicant_8/wpa_supplicant/src/drivers/driver_wext.c: In function 'wpa_driver_wext_associate':
external/wpa_supplicant_8/wpa_supplicant/src/drivers/driver_wext.c:2135:11: error: 'IW_AUTH_MFP_DISABLED' undeclared (first use in this function)
external/wpa_supplicant_8/wpa_supplicant/src/drivers/driver_wext.c:2138:11: error: 'IW_AUTH_MFP_OPTIONAL' undeclared (first use in this function)
external/wpa_supplicant_8/wpa_supplicant/src/drivers/driver_wext.c:2141:11: error: 'IW_AUTH_MFP_REQUIRED' undeclared (first use in this function)
external/wpa_supplicant_8/wpa_supplicant/src/drivers/driver_wext.c:2144:42: error: 'IW_AUTH_MFP' undeclared (first use in this function)
make: *** [/home/pixelfreak/htc-leo/carbon/4.3/out/target/product/leo/obj/EXECUTABLES/wpa_supplicant_intermediates/src/drivers/driver_wext.o] Error 1
make: *** Waiting for unfinished jobs....[/COLOR]
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
target StaticLib: libc_nomalloc (/home/pixelfreak/htc-leo/carbon/4.3/out/target/product/leo/obj/STATIC_LIBRARIES/libc_nomalloc_intermediates/libc_nomalloc.a)
[email protected] ~/htc-leo/carbon/4.3 $
pixelfreak
Because now we have ION Kernel, why dont you guys compile a Rom that use ION????
re
aazzam16661 said:
Because now we have ION Kernel, why dont you guys compile a Rom that use ION????
Click to expand...
Click to collapse
the ion system not work 100%... we have test the ion and we go back to Linux kernel version: 2.6.35.14....
pixelfreak
-pixelfreak- said:
the ion system not work 100%... we have test the ion and we go back to Linux kernel version: 2.6.35.14....
pixelfreak
Click to expand...
Click to collapse
There is no ION for HD2 2.6 kernel, its only available in 3.0 kernel
and what do you mean by ion system not work 100%
re
aazzam16661 said:
There is no ION for HD2 2.6 kernel, its only available in 3.0 kernel
and what do you mean by ion system not work 100%
Click to expand...
Click to collapse
no we have test the 3.xx kernel with ion and this not work. so we go back to 2.6
pixelfreak
aazzam16661 said:
Because now we have ION Kernel, why dont you guys compile a Rom that use ION????
Click to expand...
Click to collapse
3.x kernel does not support working bluetooth yet. Display did not work with ion yet.
If you have working display for ion you can tell how to enable it.
walter79 said:
Display did not work with ion yet.
Click to expand...
Click to collapse
And how i'm i using Sense 5 Right Now on my HD2.....It Use ION man...The ION kernel for HD2 Was created for The Sense 5
And yes, the display works
OR, your taking about cm10.2 build have display not working????
walter79 said:
3.x kernel does not support working bluetooth yet. Display did not work with ion yet.
If you have working display for ion you can tell how to enable it.
Click to expand...
Click to collapse
I think more and more people use Bluetooth...but want more smooth....
so i also suggest Kernel 3.0 and it support NativeSD better!
Thanks!

Kernel Compilation ERROR

[email protected]:~/android/kernel$ make zImage
CHK include/linux/version.h
CHK include/generated/utsrelease.h
make[1]: `include/generated/mach-types.h' is up to date.
CALL scripts/checksyscalls.sh
CHK include/generated/compile.h
CC drivers/input/touchscreen/ft5x06_ts.o
drivers/input/touchscreen/ft5x06_ts.c: In function 'ft5x06_get_factory_id':
drivers/input/touchscreen/ft5x06_ts.c:432:45: warning: 'ft5336_bootloader_ver' may be used uninitialized in this function [-Wuninitialized]
error, forbidden warning: ft5x06_ts.c:432
make[3]: *** [drivers/input/touchscreen/ft5x06_ts.o] Error 1
make[2]: *** [drivers/input/touchscreen] Error 2
make[1]: *** [drivers/input] Error 2
make: *** [drivers] Error 2
DevendraMilmile121 said:
[email protected]:~/android/kernel$ make zImage
CHK include/linux/version.h
Click to expand...
Click to collapse
its toolchain error..use Linaro 4.6 toolchain
Luffy.d said:
its toolchain error..use Linaro 4.6 toolchain
Click to expand...
Click to collapse
Thanks Bro Problem Now solved now another problem presist
Code:
CC drivers/video/msm/mdss/mdss_mdp_overlay.o
drivers/video/msm/mdss/mdss_mdp_overlay.c: In function ‘mdss_mdp_overlay_ioctl_handler’:
drivers/video/msm/mdss/mdss_mdp_overlay.c:2273:1: warning: the frame size of 1280 bytes is larger than 1024 bytes [-Wframe-larger-than=]
error, forbidden warning: mdss_mdp_overlay.c:2273
make[4]: *** [drivers/video/msm/mdss/mdss_mdp_overlay.o] Error 1
make[3]: *** [drivers/video/msm/mdss] Error 2
make[2]: *** [drivers/video/msm] Error 2
make[1]: *** [drivers/video] Error 2
make: *** [drivers] Error 2
DevendraMilmile121 said:
Thanks Bro Problem Now solved now another problem presist
Code:
CC drivers/video/msm/mdss/mdss_mdp_overlay.o
drivers/video/msm/mdss/mdss_mdp_overlay.c: In function ‘mdss_mdp_overlay_ioctl_handler’:
drivers/video/msm/mdss/mdss_mdp_overlay.c:2273:1: warning: the frame size of 1280 bytes is larger than 1024 bytes [-Wframe-larger-than=]
error, forbidden warning: mdss_mdp_overlay.c:2273
make[4]: *** [drivers/video/msm/mdss/mdss_mdp_overlay.o] Error 1
make[3]: *** [drivers/video/msm/mdss] Error 2
make[2]: *** [drivers/video/msm] Error 2
make[1]: *** [drivers/video] Error 2
make: *** [drivers] Error 2
Click to expand...
Click to collapse
this also seem toolchain error bro....do one thing bro use sabermod toolchain
i successfully compile the kernel with saber toolchain
Luffy.d said:
this also seem toolchain error bro....do one thing bro use sabermod toolchain
i successfully compile the kernel with saber toolchain
Click to expand...
Click to collapse
Im using 64bit os any problem with this and can u give me saber toolchain link
DevendraMilmile121 said:
Im using 64bit os any problem with this and can u give me saber toolchain link
Click to expand...
Click to collapse
os is ok....try this toolchain
https://github.com/SaberMod/arm-eabi-4.9
Luffy.d said:
os is ok....try this toolchain
https://github.com/SaberMod/arm-eabi-4.9
Click to expand...
Click to collapse
4.9 won't work, you'll need 4.7(i use linaro)
CoreWolf said:
4.9 won't work, you'll need 4.7(i use linaro)
Click to expand...
Click to collapse
i use linaro 4.6 no luck i will try 4.7 and tell u tomorrow
CoreWolf said:
4.9 won't work, you'll need 4.7(i use linaro)
Click to expand...
Click to collapse
i tried it work...getting one or two error but compile successfully
I downloaded both tool chain Im trying today
@DevendraMilmile121 have you solved compilation errors? which toolchain you are using ??
Used linero 4.7 2014 build. compile kernel but some problem in display driver it show only mi logo
DevendraMilmile121 said:
Used linero 4.7 2014 build. compile kernel but some problem in display driver it show only mi logo
Click to expand...
Click to collapse
how did you repack kernel? did you generate a dt.img?
thewisenerd said:
how did you repack kernel? did you generate a dt.img?
Click to expand...
Click to collapse
same question wat i have did you get the DT.img ???? m stuck there :crying:
Tarun93 said:
same question wat i have did you get the DT.img ???? m stuck there :crying:
Click to expand...
Click to collapse
p.s. compiled kernel, added s2w, dt2w (by showp1984) (thx showp1984)
thewisenerd said:
p.s. compiled kernel, added s2w, dt2w (by showp1984) (thx showp1984)
Click to expand...
Click to collapse
i wanna get my carbon rom kicked up with the kernel source i have the kernel ready with a couple of governors n schedulers n working on other things too but i wanna have a stock kernel kicked in n booted first for the rom tried everything i could but cant get it started @thewisenerd do you have any idea how do i get around this ??
I pack kernel on windows I have two system .kernel booted but only show mi logo how to solve this
How to solve milogo bug
DevendraMilmile121 said:
How to solve milogo bug
Click to expand...
Click to collapse
What you had done with source code?
DevendraMilmile121 said:
How to solve milogo bug
Click to expand...
Click to collapse
the kernel wont work on old cm and old rom....try it on latest cm11 r15 and see the magic

[Q] D850 CM12 Local Manifest

I am trying to compile CM12 on my own for the D850 and I am curious what people are using for the Local Manifest file. I found one thread talking about building CM12 for the LG G3, but it seemed to be for the D855 and it seemed like it might be using 3rd party sources on Github.
So I'm trying to find out what the full local manifest should be for my D850 CM12 build. I am a compile noob, so being able to tell me/show me what the full manifest file should contain would be greatly appreciated. Also, if you could tell/show me how you found out this information, so I can figure it out for myself in the future, that would be awesome
I found this on the CM website - http://wiki.cyanogenmod.org/w/Local_manifest
It tells me to grab this file on the LG G3 that I have CM12 on already "/system/etc/build-manifest.xml", but when I look at that file, it has HUGE. the local_manifest.xml file for the N5 that I'm building only has like 3-4 entries.
Is this huge file really the local_manifest that I need to use to build CM12 for the D850 LG G3?
Here's mine (edited for you), cyanogenmod doesnt seem to have "proprietary_vendor_lge", so i left it how I have mine.
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project path="device/lge/g3-common" name=CyanogenMod/android_device_lge_g3-common" remote="github" revision="cm-12.0" />
<project path="device/lge/d850" name="CyanogenMod/android_device_lge_d850" remote="github" revision="cm-12.0" />
<project path="kernel/lge/g3" name="CyanogenMod/android_kernel_lge_g3" remote="github" revision="cm-12.0" />
[B]<project path="vendor/lge" name="ResurrectionRemix/proprietary_vendor_lge" remote="github" revision="lollipop" />[/B]
<project path="device/qcom_common" name="CyanogenMod/android_device_qcom_common" remote="github" revision="cm-12.0" />
</manifest>
Thank you for the response. I did just find this in CM's github
- https://github.com/CyanogenMod/android_device_lge_g3-common
and this
- https://github.com/CyanogenMod/android_kernel_lge_g3
rhystagram said:
Here's mine (edited for you), cyanogenmod doesnt seem to have "proprietary_vendor_lge", so i left it how I have mine.
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project path="device/lge/g3-common" name=CyanogenMod/android_device_lge_g3-common" remote="github" revision="cm-12.0" />
<project path="device/lge/d850" name="CyanogenMod/android_device_lge_d850" remote="github" revision="cm-12.0" />
<project path="kernel/lge/g3" name="CyanogenMod/android_kernel_lge_g3" remote="github" revision="cm-12.0" />
[B]<project path="vendor/lge" name="ResurrectionRemix/proprietary_vendor_lge" remote="github" revision="lollipop" />[/B]
<project path="device/qcom_common" name="CyanogenMod/android_device_qcom_common" remote="github" revision="cm-12.0" />
</manifest>
Click to expand...
Click to collapse
Very awesome. Thank you for your help. Is there anything wrong/bad about using Resurrection's proprietary vendor one for my vanilla CM12 build for the d850?
I've seen someone using this one. . .
<project path="vendor/lge" name="sooti/proprietary_vendor_lge" remote="github" revision="cm-12.0" />
but it was for the D855. I don't know if these will mess up my build since I'm compiling for the D850 instead.
Again, thank you for the help. It is greatly appreciated.
view step 3 here, it has the local_manifest details, they're from sooti, which was before CM official builds..
maybe use his vendor, but official cm repostories for others.
http://forum.xda-developers.com/lg-g3/development/guide-how-to-build-cyanogenmod-12-t2953132
just noticed you replied, pretty sure as long as you have the d850 files, and run the "brunch d850" the vendor will still run correctly, as it's a vendor for LGE.
rhystagram said:
view step 3 here, it has the local_manifest details, they're from sooti, which was before CM official builds..
maybe use his vendor, but official cm repostories for others.
http://forum.xda-developers.com/lg-g3/development/guide-how-to-build-cyanogenmod-12-t2953132
just noticed you replied, pretty sure as long as you have the d850 files, and run the "brunch d850" the vendor will still run correctly, as it's a vendor for LGE.
Click to expand...
Click to collapse
Awesome. Thank you again, sooooo very much. It's running a repo sync now :fingers-crossed:
I'm used to running "time brunch <codename>"
is that the same as the "brunch <codename>" that you just suggested? I'm not sure what the difference between time brunch and just brunch
Enddo said:
Awesome. Thank you again, sooooo very much. It's running a repo sync now :fingers-crossed:
I'm used to running "time brunch <codename>"
is that the same as the "brunch <codename>" that you just suggested? I'm not sure what the difference between time brunch and just brunch
Click to expand...
Click to collapse
time brunch shows you how long it takes to build (i think), brunch just builds .
rhystagram said:
time brunch shows you how long it takes to build (i think), brunch just builds .
Click to expand...
Click to collapse
Well, it all seemed to work but then I got an error toward the end
Code:
/bin/sh: 1: lz4c: not found
make[4]: *** [arch/arm/boot/compressed/piggy.lz4] Error 1
make[3]: *** [arch/arm/boot/compressed/vmlinux] Error 2
make[2]: *** [zImage] Error 2
make[1]: *** [sub-make] Error 2
make[1]: Leaving directory `/home/doug/lgg3/kernel/lge/g3'
make: *** [TARGET_KERNEL_BINARIES] Error 2
make: *** Waiting for unfinished jobs....
real 52m2.413s
user 204m32.365s
sys 21m4.082s
I found a thread talking about that error and someone suggested to do a sudo apt-get install lzop, but it says I already have that
Code:
sudo apt-get install lzop
[sudo] password for doug:
Reading package lists... Done
Building dependency tree
Reading state information... Done
lzop is already the newest version.
The following packages were automatically installed and are no longer required:
libgpds0 linux-headers-3.13.0-32 linux-headers-3.13.0-32-generic
linux-headers-generic linux-image-3.13.0-32-generic
linux-image-extra-3.13.0-32-generic linux-image-generic python-pyudev
Use 'apt-get autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Found a suggestion to run "sudo apt-get install liblz4-tool", I installed that and am trying the process over again
Enddo said:
Well, it all seemed to work but then I got an error toward the end
Code:
/bin/sh: 1: lz4c: not found
make[4]: *** [arch/arm/boot/compressed/piggy.lz4] Error 1
make[3]: *** [arch/arm/boot/compressed/vmlinux] Error 2
make[2]: *** [zImage] Error 2
make[1]: *** [sub-make] Error 2
make[1]: Leaving directory `/home/doug/lgg3/kernel/lge/g3'
make: *** [TARGET_KERNEL_BINARIES] Error 2
make: *** Waiting for unfinished jobs....
real 52m2.413s
user 204m32.365s
sys 21m4.082s
Click to expand...
Click to collapse
can't help here man, it's happened to me, only solution i found to fix it for me was to make a new directory & download all sources again & build from there. (didn't try the solution you are, let me know how it goes?)
rhystagram said:
can't help here man, it's happened to me, only solution i found to fix it for me was to make a new directory & download all sources again & build from there. (didn't try the solution you are, let me know how it goes?)
Click to expand...
Click to collapse
After doing a "sudo apt-get install liblz4-tool", I did the whole compile process over, didn't even do a make clean(but I might if there is something wrong with the flash), and it seemed to compile perfectly.
I had to let it run while I was sleeping so I didn't get a chance to flash it yet. Do you know if these are already 'bumped', or if I have to do something special to them now that they have been compiled? I'm almost certain the CM repos have the Bump code in them, but I just wanted to double check in case anyone else knows for sure
and thank you again for all the help. I just have no idea how to get the local manifest information for these builds. I've had help with both the N5 and now the G3. I would love to know how to figure out this on my own so I don't have to keep bothering the community
Do you know how to do this? How to know when you have enough items in the manifest and where to get them. It seems like most come from CM but on both the G3 and the N5, there's one that comes from somewhere else.
Like with the N5, it was the proprietary one that came from somewhere else
"<project name="TheMuppets/proprietary_vendor_lge" path="vendor/lge" remote="github" revision="cm-12.0"/>"
I just flashed it and it worked perfectly! Well, I had a force close error on a google app, so I uninstalled the updates, and updated it from Google Play and it launched. This was probably something to do with the dirty flash more than the compile
Thanks again @rhystagram !
I couldn't be more grateful
image is bumped yes
Target boot image: /home/rhys/newrr/out/target/product/d855/boot.img
/home/rhys/newrr/out/target/product/d855/boot.img maxsize=17031168 blocksize=135168 total=7329792 reserve=270336
bumped image: /home/rhys/newrr/out/target/product/d855/boot.img
Made boot image: /home/rhys/newrr/out/target/product/d855/boot.img
glad i could help & glad you got it working!!

Resurretion remix build help

I know there is already a working build posted on some of the russian forums, but.... I really wanted to try a build out myself
can anyone help with his error
Import includes file: /home/x/out/target/product/crackling/obj/EXECUTABLES/wpa_cli_intermediates/import_includes
make: *** No rule to make target '/home/x/out/target/product/crackling/obj/SHARED_LIBRARIES/libwpa_qmi_eap_proxy_intermediates/export_includes', needed by '/home/x/out/target/product/crackling/obj/EXECUTABLES/wpa_supplicant_intermediates/import_includes'. Stop.
make: *** Waiting for unfinished jobs....
Export includes file: external/wpa_supplicant_8/wpa_supplicant/eap_proxy_qmi.mk -- /home/x/out/target/product/crackling/obj/EXECUTABLES/wpa_cli_intermediates/export_includes
make: Leaving directory '/home/x'
and yeah a build noob so pls be a little gntle :good:
ok ignore... past that error and onto the next
The some error when i try compile Nextbit ether
ake: *** Brak reguł do zrobienia obiektu `/home/ciachoo/CyanogenMod/out/target/product/ether/obj/SHARED_LIBRARIES/libwpa_qmi_eap_proxy_intermediates/export_includes', wymaganego przez `/home/ciachoo/CyanogenMod/out/target/product/ether/obj/EXECUTABLES/wpa_supplicant_intermediates/import_includes'. Stop.
poncz3k said:
The some error when i try compile Nextbit ether
ake: *** Brak reguł do zrobienia obiektu `/home/ciachoo/CyanogenMod/out/target/product/ether/obj/SHARED_LIBRARIES/libwpa_qmi_eap_proxy_intermediates/export_includes', wymaganego przez `/home/ciachoo/CyanogenMod/out/target/product/ether/obj/EXECUTABLES/wpa_supplicant_intermediates/import_includes'. Stop.
Click to expand...
Click to collapse
for me it was the proprietary files..... I was literally being a 'Muppet' by not setting up

Categories

Resources