Develop Bugs

[Q] yaffs2 corruption (directory hardlinks pointing to parent)

Hi!
I am experiencing yaffs2 filesystem corruption on the data partition of my Desire.
The errors are always quite similar: Directory entries with empty names that point to the parent directory:
Code:
# ls -lia /data/data/com.android.providers.contacts/lib/databases
total 6
2006 drwxr-xr-x 1 10006 10006 2048 Apr 8 22:30
2006 drwxr-xr-x 1 10006 10006 2048 Apr 8 22:30 .
1737 drwxr-xr-x 1 1000 1000 2048 Apr 9 07:49 ..
It looks very similar to this report.
I've already tried several ROMs (most recently AceSMod007 and RevolutioN v3.0) but both use kernel 2.6.35.14-gingercakes-0.9-avs that maybe doesn't contain the fix.
Can anyone recommend a kernel that includes this patch?

Auto-Debloat S4 Flashable Zip! [16 Jun 2013]

Now you can auto-debloat your Galaxy S4 beauty using my new Auto-Debloat S4 flashable zip!
Link: http://www.mediafire.com/download/awabu8cg5a19lj4/Debloat-SGS4.zip
This is tested working on my rooted, unlocked (bootloader) SGH-I337 (AT&T) running Stock AT&T JB 4.2.2 I337UCUAMDL and TWRP Recovery 2.5.0.2.
But it should work on just about any S4 ROM though the primary target is JB 4.2.2.
Now of course there are many ways to debloat your rooted S4. But you may find this one very useful.
By default, my flashable zip frees up 600MB of precious space in your 2.7GB /system partition by removing approximately 90 bloatware apks and their corresponding odex files! Run time is just over 30 seconds.
And the customizable database file (bloatware-apk-sorted.txt) is sorted by file size to help you focus on big bloats like Samsung’s Health app “SHealth2.apk” (88 MB).
Thus you can debloat even more by extracting the database “bloatware-apk-sorted.txt” from zip, changing filename suffixes from “.KEEP” to “.apk”, reinserting database and reflashing. Run time is shorter on the second and subsequent passes.
Want to "rebloat"? No problem: All bloatware is safely moved to a special directory: /sdcard/Download/Bloatware for quick recovery.
As usual, “I will let YOU DECIDE whether to wipe data!”
Here’s a clip of my original database “bloatware-apk-sorted.txt” showing some of the worst offenders --- at least in terms of file size:
-rw-r--r-- 1 root root 88540395 Apr 27 2013 SecSettings.KEEP
-rw-r--r-- 1 root root 87854416 Apr 27 2013 SHealth2.apk
-rw-r--r-- 1 root root 39695494 Apr 27 2013 Episodes.apk
-rw-r--r-- 1 root root 39428223 Apr 27 2013 SecGallery2013.KEEP
-rw-r--r-- 1 root root 36196565 Apr 27 2013 GroupPlay_20.apk
-rw-r--r-- 1 root root 33781912 Apr 27 2013 InteractiveTutorial.apk
-rw-r--r-- 1 root root 28792764 Apr 27 2013 SecContacts.KEEP
-rw-r--r-- 1 root root 27349911 Apr 27 2013 S-Voice_Android_phone_J.apk
-rw-r--r-- 1 root root 26746285 Apr 27 2013 Match3VS.apk
-rw-r--r-- 1 root root 25549401 Apr 27 2013 SMemo2.apk
-rw-r--r-- 1 root root 25440434 Apr 27 2013 Peel.apk
-rw-r--r-- 1 root root 23676201 Apr 27 2013 SamsungBooks.apk
-rw-r--r-- 1 root root 23168685 Apr 27 2013 AllSharePlay15.apk
-rw-r--r-- 1 root root 22967881 Apr 27 2013 ChatONV_J.apk
-rw-r--r-- 1 root root 22829640 Apr 27 2013 ClockPackage.KEEP
-rw-r--r-- 1 root root 22407406 Apr 27 2013 PolarisOffice5.KEEP
Click to expand...
Click to collapse
And here’s the script engine: auto-debloat.sh
#!/sbin/sh
echo " "
echo "Auto-Debloat for Samsung S4!"
echo "Initial Release (16 Jun 2013)"
echo "sendust7 @ xda developers"
bloatdir="/sdcard/Download/Bloatware"
bloatfile="/tmp/bloatware-apk-sorted.txt"
echo " "
echo "All bloatware files are suffixed by .apk in $bloatfile"
echo "System apps to be retained are suffixed by .KEEP in $bloatfile"
echo "All bloatware (apk and odex) will be moved to $bloatdir"
if [ -d $bloatdir ]; then
echo " "
else
echo " "
mkdir $bloatdir
fi
while read line; do
apkname=$(echo $line | cut -d" " -f9)
apkprefix=$(echo $apkname | cut -d"." -f1)
apkodex=$apkprefix.odex
if [ -f /system/app/$apkname ]; then
echo "Moving /system/app/$apkname to $bloatdir ..."
mv /system/app/$apkname $bloatdir
if [ -f /system/app/$apkodex ]; then
echo "Moving /system/app/$apkodex to $bloatdir ..."
mv /system/app/$apkodex $bloatdir
fi
fi
done < $bloatfile
Click to expand...
Click to collapse
Blessings Enjoy

Boom.

Can i use your application to debloat my Samsung Galaxy S4 Active SGH-i537. Running android 4.2.2. Its branded by AT&T and want to get rid of these crapy apps of AT&T. Kindly let me know.
Regards,

[Q] I want to build CM12 for my D859(ChinaTelecom)

D859 has 2sims, I can't use other g3 template, right
I already read a loi of information from cm wiki about hout to build a cm,
but I still have any clue yet,
I got D859 official rom scr code yesterday from opensource.lge.com,
I don't know how can I start for building cm,
I need some help, thank you!:laugh:
Here is the list of the files
LGD859_Lollipop_LGD859_V20a_Android_opensource/android/external: $ ls -al
drwxr-xr-x 17 578 brctl
drwxr-xr-x 21 714 dnsmasq
drwxr-xr-x 44 1496 e2fsprogs
drwxr-xr-x 7 238 ebtables
drwxr-xr-x 12 408 gcc-demangle
drwxr-xr-x 25 850 iproute2
drwxr-xr-x 21 714 iptables
drwxr-xr-x 31 1054 iputils
drwxr-xr-x 15 510 junit
drwxr-xr-x 41 1394 libexif
drwxr-xr-x 20 680 libnetfilter_conntrack
drwxr-xr-x 16 544 libnfnetlink
drwxr-xr-x 18 612 libnl
LGD859_Lollipop_LGD859_V20a_Android_opensource/android/vendor/lge: $ ls -la
drwxr-xr-x 3 102 apps
drwxr-xr-x 3 102 build
drwxr-xr-x 5 170 external
drwxr-xr-x 3 102 factory
drwxr-xr-x 4 136 frameworks
drwxr-xr-x 3 102 prebuilt
drwxr-xr-x 4 136 system
LGD859_Lollipop_LGD859_V20a_Android_opensource/kernel: $ ls -al
-rw-r--r-- 1 5935 AndroidKernel.mk
-rw-r--r-- 1 18693 COPYING
-rw-r--r-- 1 94984 CREDITS
drwxr-xr-x 237 8058 Documentation
-rw-r--r-- 1 2536 Kbuild
-rw-r--r-- 1 252 Kconfig
-rw-r--r-- 1 210475 MAINTAINERS
-rw-r--r-- 1 53855 Makefile
-rw-r--r-- 1 364155 Module.symvers
-rw-r--r-- 1 17459 README
-rw-r--r-- 1 3371 REPORTING-BUGS
drwxr-xr-x 31 1054 arch
drwxr-xr-x 38 1292 block
drwxr-xr-x 89 3026 crypto
drwxr-xr-x 112 3808 drivers
drwxr-xr-x 55 1870 firmware
drwxr-xr-x 149 5066 fs
drwxr-xr-x 26 884 include
drwxr-xr-x 14 476 init
drwxr-xr-x 17 578 ipc
drwxr-xr-x 133 4522 kernel
drwxr-xr-x 150 5100 lib
drwxr-xr-x 79 2686 mm
drwxr-xr-x 62 2108 net
drwxr-xr-x 14 476 samples
drwxr-xr-x 91 3094 scripts
drwxr-xr-x 18 612 security
drwxr-xr-x 28 952 sound
drwxr-xr-x 14 476 tools
-rw-r--r-- 1 37204 tuxera_update.sh
drwxr-xr-x 9 306 usr
drwxr-xr-x 3 102 virt
and its readme file said
1. Android build
- Download original android source code ( L 5.0 ) from source.android.com
- Untar opensource packages of LGD859_L_V20a_Android.tar.gz into downloaded android source directory
a) cat LGD859_L_V20a_Android.tar.gza* | tar zxvpf -
- And, merge the source into the android source code
- Run following scripts to build android
a) source build/envsetup.sh
b) lunch 1
c) make -j4
- When you compile the android source code, you have to add google original prebuilt source(toolchain) into the android directory.
- After build, you can find output at out/target/product/generic
2. Kernel Build
- Uncompress using following command at the android directory
tar xvzf LGD859_L_V20a_Kernel.tar.gz
- When you compile the kernel source code, you have to add google original prebuilt source(toolchain) into the android directory.
- Run following scripts to build kernel
a) cd kernel
1) D859
b) make ARCH=arm CROSS_COMPILE=../prebuilts/gcc/linux-x86/arm/arm-eabi-4.8/bin/arm-eabi- g3-ctc_cn-perf_defconfig zImage -j4
* "-j4" : The number, 4, is the number of multiple jobs to be invoked simultaneously.
- After build, you can find the build image(zImage) at arch/arm/boot
3. how to build chromium34_lge (vendor\lge\external\chromium34_lge\src),
please refer to README.txt at the folder mentioned above.

Pixel XL AOSP Build: No Modem? [Solved]

I built AOSP 9.0.0_r2, targeting aosp_marlin-user to try and make a custom ROM for my phone. When I flashed it and booted into Android my cell service was not working, so I figured it must be some sort of mis-configuration or missing files.
I did download and run the extract scripts and I flashed with `fastboot flashall`.
The files in the root of my build directory:
Code:
$ ls -la
total 219148
drwxr-xr-x 30 gudenau gudenau 4096 Aug 28 16:18 .
drwxr-xr-x 6 gudenau gudenau 4096 Aug 27 21:11 ..
lrwxrwxrwx 1 gudenau gudenau 19 Aug 27 13:29 Android.bp -> build/soong/root.bp
drwxr-xr-x 30 gudenau gudenau 4096 Aug 27 13:29 art
drwxr-xr-x 13 gudenau gudenau 4096 Aug 27 13:29 bionic
drwxr-xr-x 3 gudenau gudenau 4096 Aug 27 13:29 bootable
lrwxrwxrwx 1 gudenau gudenau 26 Aug 27 13:29 bootstrap.bash -> build/soong/bootstrap.bash
drwxr-xr-x 6 gudenau gudenau 4096 Aug 27 13:29 build
drwxr-xr-x 3 gudenau gudenau 4096 Aug 27 13:29 compatibility
drwxr-xr-x 12 gudenau gudenau 4096 Aug 27 13:29 cts
drwxr-xr-x 10 gudenau gudenau 4096 Aug 27 13:29 dalvik
drwxr-xr-x 5 gudenau gudenau 4096 Aug 27 13:29 developers
drwxr-xr-x 20 gudenau gudenau 4096 Aug 27 13:29 development
drwxr-xr-x 7 gudenau gudenau 4096 Aug 27 13:29 device
drwxr-xr-x 289 gudenau gudenau 12288 Aug 27 13:32 external
-rwxr-xr-x 1 gudenau gudenau 109763273 Jul 25 13:15 extract-google_devices-marlin.sh
-rwxr-xr-x 1 gudenau gudenau 8633919 Jul 25 13:15 extract-qcom-marlin.sh
drwxr-xr-x 17 gudenau gudenau 4096 Aug 27 13:33 frameworks
drwxr-xr-x 14 gudenau gudenau 4096 Aug 27 13:33 hardware
drwxr-xr-x 4 gudenau gudenau 4096 Aug 27 13:33 kernel
drwxr-xr-x 20 gudenau gudenau 4096 Aug 27 13:33 libcore
drwxr-xr-x 8 gudenau gudenau 4096 Aug 27 13:33 libnativehelper
-r--r--r-- 1 gudenau gudenau 92 Aug 27 13:29 Makefile
drwxr-xr-x 9 gudenau gudenau 4096 Aug 28 15:41 out
drwxr-xr-x 9 gudenau gudenau 4096 Aug 27 13:33 packages
-rw-r--r-- 1 gudenau gudenau 31047680 Aug 28 16:05 patched_boot.img
drwxr-xr-x 6 gudenau gudenau 4096 Aug 27 13:33 pdk
drwxr-xr-x 9 gudenau gudenau 4096 Aug 27 13:33 platform_testing
drwxr-xr-x 27 gudenau gudenau 4096 Aug 27 13:38 prebuilts
drwxr-xr-x 7 gudenau gudenau 4096 Aug 27 21:58 .repo
drwxr-xr-x 25 gudenau gudenau 4096 Aug 27 13:39 sdk
drwxr-xr-x 29 gudenau gudenau 4096 Aug 27 13:39 system
drwxr-xr-x 7 gudenau gudenau 4096 Aug 27 13:39 test
drwxr-xr-x 5 gudenau gudenau 4096 Aug 27 13:40 toolchain
drwxr-xr-x 13 gudenau gudenau 4096 Aug 27 13:40 tools
drwxr-xr-x 4 gudenau gudenau 4096 Jul 25 13:15 vendor
Did I miss something stupid, or can I just not use the modem with AOSP?
(I do plan on making releases at some point if I get it working and get the things I want in)

gudenau said:
I built AOSP 9.0.0_r2, targeting aosp_marlin-user to try and make a custom ROM for my phone........
Click to expand...
Click to collapse
I don't have this device but, you should be able to obtain some member guidance within the following Q&A thread that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=3489005
Good Luck!
~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my SM-G900V device.

Ibuprophen said:
I don't have this device but, you should be able to obtain some member guidance within the following Q&A thread that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=3489005
Good Luck!
~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my SM-G900V device.
Click to expand...
Click to collapse
Woops, could you move this? That is my bad.

gudenau said:
Woops, could you move this? That is my bad.
Click to expand...
Click to collapse
I'm not able to move threads but, a Moderator would be more than happy to move it for you.
~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my SM-G900V device.

Does nobody have any idea about this issue?

Why did you build from the r2 revision? If you look at the factory images, you can see build PPR1.180610.010 is for Telus, and PPR1.180610.009 is for other carriers. When you compare this to the Android release tag list, you will see the correct revision (if not targeting Telus) is the android-9.0.0_r1.
In addition, did you include proprietary vendor files (typically in vendor/google_devices/marlin) in your build? You can pull these from a factory image, or just clone from another developers repos (for example from BenzoRom repo).

jisoo said:
Why did you build from the r2 revision? If you look at the factory images, you can see build PPR1.180610.010 is for Telus, and PPR1.180610.009 is for other carriers. When you compare this to the Android release tag list, you will see the correct revision (if not targeting Telus) is the android-9.0.0_r1.
In addition, did you include proprietary vendor files (typically in vendor/google_devices/marlin) in your build? You can pull these from a factory image, or just clone from another developers repos (for example from BenzoRom repo).
Click to expand...
Click to collapse
I used that one because it was the latest that said "Pixel XL". I did use the vendor scripts they had the Google and QCom blobs.
I'll have to try r1.

I tried r1 and I still have no cell modem access.

gudenau said:
I tried r1 and I still have no cell modem access.
Click to expand...
Click to collapse
Ok, what about the blobs then? How are you extracting these, there may be bits missing.
Also could be a selimux issue. One thing I like to do is turn selinux permissive until I've got the main bugs cleared up and phone in a usable state.

jisoo said:
Ok, what about the blobs then? How are you extracting these, there may be bits missing.
Also could be a selimux issue. One thing I like to do is turn selinux permissive until I've got the main bugs cleared up and phone in a usable state.
Click to expand...
Click to collapse
These Google ones and these Qualcomm ones from Google Developers.

gudenau said:
These Google ones and these Qualcomm ones from Google Developers.
Click to expand...
Click to collapse
Google lies. Those blobs don't have everything you need.
You really need to use blobs which have been extracted from the actual factory images.
I suggest either the ones Lineage or BemzoRom uses.
Just make sure you use the correct branch.

jisoo said:
Google lies. Those blobs don't have everything you need.
You really need to use blobs which have been extracted from the actual factory images.
I suggest either the ones Lineage or BemzoRom uses.
Just make sure you use the correct branch.
Click to expand...
Click to collapse
That's ridiculous, how could I use the ones that come from the factory images? I'd prefer to use those over some on GitHub with some instructions on how to set it up when I eventually do more with this.

gudenau said:
That's ridiculous, how could I use the ones that come from the factory images? I'd prefer to use those over some on GitHub with some instructions on how to set it up when I eventually do more with this.
Click to expand...
Click to collapse
He's right, the ones from google doesn't have everything you need (ridiculous ) The repos he linked are extracted from the factory image.
These are the blobs that are missing that cause no ril (thank you @xanaxdroid for pointing this out to me)
I would use benzo's if I were you, since aosp requires a patch if you don't include the entire vendor

shagbag913 said:
He's right, the ones from google doesn't have everything you need (ridiculous ) The repos he linked are extracted from the factory image.
These are the blobs that are missing that cause no ril (thank you @xanaxdroid for pointing this out to me)
I would use benzo's if I were you, since aosp requires a patch if you don't include the entire vendor
Click to expand...
Click to collapse
Where would I put these?

gudenau said:
Where would I put these?
Click to expand...
Click to collapse
vendor/google_devices/marlin is the path where the device tree looks for the relevant makefile, so make sure you have the same directory structure.

jisoo said:
vendor/google_devices/marlin is the path where the device tree looks for the relevant makefile, so make sure you have the same directory structure.
Click to expand...
Click to collapse
Code:
[936/936] including vendor/google_devices/sailfish/Android.mk ...
build/make/core/tasks/vendor_module_check.mk:82: error: Error: Product "aosp_marlin" cannot have overlay in vendor tree: vendor/google_devices/marlin/overlay.
Any idea how to fix this?

gudenau said:
Code:
[936/936] including vendor/google_devices/sailfish/Android.mk ...
build/make/core/tasks/vendor_module_check.mk:82: error: Error: Product "aosp_marlin" cannot have overlay in vendor tree: vendor/google_devices/marlin/overlay.
Any idea how to fix this?
Click to expand...
Click to collapse
It was one of the below 3 commits for android_build which fixes that error, but I am honestly not smart enough to know which one...
add support for overriding build.prop settings
Add support for PRODUCT_COPY_FILES_OVERRIDES
Allow prebuild APK's in Vendor
I'm not a real dev, so you want to review the commits and determine yourself.

jisoo said:
It was one of the below 3 commits for android_build which fixes that error, but I am honestly not smart enough to know which one...
add support for overriding build.prop settings
Add support for PRODUCT_COPY_FILES_OVERRIDES
Allow prebuild APK's in Vendor
I'm not a real dev, so you want to review the commits and determine yourself.
Click to expand...
Click to collapse
I applied all of them and they don't seem to have done anything. :-/

gudenau said:
I applied all of them and they don't seem to have done anything. :-/
Click to expand...
Click to collapse
I think you need to comment this out, but I can't remember if that's the one it checks for overlays..

shagbag913 said:
I think you need to comment this out, but I can't remember if that's the one it checks for overlays..
Click to expand...
Click to collapse
{
"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"
}
Well, that is an interesting thing to have happen.

Problem with Lineageos 16.0 Build for pme with proprietary blobs

Hello,
I just want to compile Lineageos 16.0 for my old HTC10 (PME).
I followed the guide at wiki.lineageos.org/devices/pme/build
I have synced the repo without issues.
Now I have the problem to integrate the proprietary blobs into the source tree.
I have extracted the files from an available ROM.
The files are now stored under
/android/system_dump/system
Code:
[email protected]:~/android/system_dump/system$ ls -al
insgesamt 2720
drwxr-xr-x. 20 root root 4096 Jan 1 2009 .
drwxrwxr-x 6 lineageos lineageos 4096 Sep 14 22:15 ..
drwxr-xr-x. 2 root root 4096 Jan 1 2009 addon.d
drwxr-xr-x. 55 root root 4096 Jan 1 2009 app
drwxr-xr-x. 3 root 2000 8192 Jan 1 2009 bin
-rw-------. 1 root root 7409 Jan 1 2009 build.prop
-rw-r--r--. 1 root root 116235 Jan 1 2009 compatibility_matrix.xml
drwxr-xr-x. 3 root root 4096 Jan 1 2009 customize
drwxr-xr-x. 21 root root 4096 Jan 1 2009 etc
drwxr-xr-x. 2 root root 4096 Jan 1 2009 fake-libs
drwxr-xr-x. 2 root root 4096 Jan 1 2009 fake-libs64
drwxr-xr-x. 2 root root 12288 Jan 1 2009 fonts
drwxr-xr-x. 5 root root 4096 Jan 1 2009 framework
drwxr-xr-x. 6 root root 16384 Jan 1 2009 lib
drwxr-xr-x. 6 root root 16384 Jan 1 2009 lib64
drwx------. 2 root root 16384 Jan 1 2009 lost+found
drwxr-xr-x. 3 root root 4096 Jan 1 2009 media
drwxr-xr-x. 62 root root 4096 Jan 1 2009 priv-app
drwxr-xr-x. 2 root root 4096 Jan 1 2009 product
-rw-r--r--. 1 root root 2524803 Jan 1 2009 recovery-from-boot.p
drwxr-xr-x. 8 root root 4096 Jan 1 2009 usr
drwxr-xr-x. 15 root 2000 4096 Jan 1 2009 vendor
drwxr-xr-x. 2 root 2000 4096 Jan 1 2009 xbin
Code:
[email protected]:~/android/system_dump/system/vendor$ ls -al
insgesamt 124
drwxr-xr-x. 15 root 2000 4096 Jan 1 2009 .
drwxr-xr-x. 20 root root 4096 Jan 1 2009 ..
drwxr-xr-x. 3 root 2000 4096 Jan 1 2009 app
drwxr-xr-x. 3 root 2000 4096 Jan 1 2009 bin
drwxr-xr-x. 2 root 2000 4096 Jan 1 2009 bt_firmware
-rw-------. 1 root root 6135 Jan 1 2009 build.prop
-rw-------. 1 root root 145 Jan 1 2009 default.prop
drwxr-xr-x. 2 root 2000 4096 Jan 1 2009 dsp
drwxr-xr-x. 14 root 2000 4096 Jan 1 2009 etc
drwxr-xr-x. 2 root 2000 4096 Jan 1 2009 firmware
drwxr-xr-x. 2 root 2000 4096 Jan 1 2009 firmware_mnt
drwxr-xr-x. 2 root 2000 4096 Jan 1 2009 framework
drwxr-xr-x. 8 root 2000 20480 Jan 1 2009 lib
drwxr-xr-x. 7 root 2000 12288 Jan 1 2009 lib64
drwxr-xr-x. 5 root 2000 4096 Jan 1 2009 overlay
drwxr-xr-x. 3 root 2000 4096 Jan 1 2009 radio
drwxr-xr-x. 3 root 2000 4096 Jan 1 2009 rfs
-rw-r--r--. 1 root root 23343 Jan 1 2009 ueventd.rc
Which files do I need? To which location must I copy the files so breakfast recognizes them?
Extract script did not work. It's for the old CyanogenMod 14.1. I have tried to edit the path variable to my lineageos source but it is still not working.
./extract-files.sh ~/android/system_dump/
(The extract script wasn't in the source tree so I copied it from github.com/LineageOS/android_device_htc_pme
But it's from the "cm14-1" source tree. I also copied the "setup-makefiles.sh" file)
Launching "breakfast pme" fails.
Code:
[email protected]:~/android/lineage$ source build/envsetup.sh
including device/generic/car/vendorsetup.sh
including device/generic/mini-emulator-arm64/vendorsetup.sh
including device/generic/mini-emulator-armv7-a-neon/vendorsetup.sh
including device/generic/mini-emulator-x86_64/vendorsetup.sh
including device/generic/mini-emulator-x86/vendorsetup.sh
including device/generic/uml/vendorsetup.sh
including vendor/lineage/vendorsetup.sh
including sdk/bash_completion/adb.bash
[email protected]:~/android/lineage$ breakfast pme
including vendor/lineage/vendorsetup.sh
build/make/core/product_config.mk:234: error: Can not locate config makefile for product "lineage_pme".
13:17:58 dumpvars failed with: exit status 1
Device pme not found. Attempting to retrieve device repository from LineageOS (Github github.com/LineageOS).
Found repository: android_device_htc_pme
Default revision: lineage-16.0
Checking branch info
Default revision lineage-16.0 not found in android_device_htc_pme. Bailing.
Branches found:
cm-13.0
cm-14.1
Use the ROOMSERVICE_BRANCHES environment variable to specify a list of fallback branches.
build/make/core/product_config.mk:234: error: Can not locate config makefile for product "lineage_pme".
13:18:00 dumpvars failed with: exit status 1
build/make/core/product_config.mk:234: error: Can not locate config makefile for product "lineage_pme".
13:18:01 dumpvars failed with: exit status 1
** Don't have a product spec for: 'lineage_pme'
** Do you have the right repo manifest?
What must I do that the proprietary blobs/ firmware filles are working with the "breakfast pme" command?
I would appreciate any help so I could start compiling lineageos 16.0 for my HTC10.
Thank you in advance.
regards
starbuck28